WSAGAScript
WSAGAScript copied to clipboard
sed: * No space left on device (apply.sh)
sed: couldn't write 80 items to /mnt/system/system/sedv8dMt1: No space left on device sed: couldn't write 80 items to /mnt/system/system/sed9uR3ya: No space left on device sed: couldn't write 80 items to /mnt/system/system/sedP0Qa7k: No space left on device sed: couldn't write 80 items to /mnt/system/system/sed3qWBiv: No space left on device sed: couldn't write 80 items to /mnt/system/system/sed6SyMKE: No space left on device sed: couldn't write 80 items to /mnt/system/system/sedqX1x0L: No space left on device sed: couldn't write 80 items to /mnt/system/system/sedzb7zYx: No space left on device sed: couldn't write 101 items to /mnt/system/system/seddGQgQG: No space left on device sed: couldn't write 80 items to /mnt/system/system/sedZ1IsPO: No space left on device
...
sed: couldn't flush /mnt/vendor/sedbsFly0: No space left on device sed: couldn't flush /mnt/vendor/sedn5Hyt8: No space left on device sed: couldn't flush /mnt/vendor/sed5q3Omi: No space left on device sed: couldn't flush /mnt/vendor/sedh0w8Yp: No space left on device sed: couldn't flush /mnt/vendor/sedDU6KEz: No space left on device sed: couldn't flush /mnt/vendor/sedePI5Jy: No space left on device
after editing the resized size in ./extend_and_mount_images.sh, the error disappear
and after running all the step listed, when I open play store and try to log in, it still says "The device isn't Play Protect certified"
encountered the same thing just now. no space left on device. i assume the vendor.img was not properly patched. also got the device isnt playstore certified. hope there's a fix for this.
Same errors here. Got the Google Play apps on here after seeing the 'No space left on device' errors, but when signing into any of them it always says, 'This device isn't Play Protect certified'.
This is caused by the file size set by extend_and_mount_images.sh, which is smaller than the original size of the two files, leaving no space left for editing operations after mounting. Just edit extend_and_mount_images.sh and set the file size properly.
For the benefit of everyone experiencing this issue, what size did you set?
I set the values to 140M for the system_ext.img and 400M for the vendor.img. I checked the file sizes in windows before and left a little buffer. I didn´t get the error after the adjustment
I set the values to 140M for the system_ext.img and 400M for the vendor.img. I checked the file sizes in windows before and left a little buffer. I didn´t get the error after the adjustment
thanks, fixed the problem for me too