Solving remote: 'Not enough space to resize partition' #36
-
I followed the instructions and everything worked fine, my bootslot is A so i deleted b, worked fine. then i did .\fastboot flash system aosp-arm64-ab-gapps14.0-20240725.img and first it told me FAILED (remote: 'Not enough space to resize partition'), i looked up a video on youtube and the guy said you have to delete your actual bootslot, in my case bootslot a. I did that, now it says FAILED (remote: 'No such file or directory'). I also tried the second newest build, it resulted in the same issue. |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 3 replies
-
this is also the second time i tried this, on my first try i thought i was doing something wrong so i flashed firmware again and started all over, but it doesn't seem like it worked. |
Beta Was this translation helpful? Give feedback.
-
Looks like your partition order is messed up currently. I assume your device is unlocked, If that is the case, the following steps may work. ./fastboot delete-logical-partition system_ext_a
./fastboot delete-logical-partition system_ext_b
./fastboot delete-logical-partition product_a
./fastboot delete-logical-partition product_b
./fastboot flash system aosp-arm64-ab-gapps14.0-20240725.img Let me know the results. |
Beta Was this translation helpful? Give feedback.
-
what will the command ./fastboot create-logical-partition system 0 do? will it create a virtual partition? I have more time tomorrow, ill try it out and keep you updated! |
Beta Was this translation helpful? Give feedback.
-
I have changed the above answer, first try with the new commands, let's not touch the system partition. We just need to make enough space for the new image, so that the system partition can expand. BTW what is the exact boot partition you deleted? |
Beta Was this translation helpful? Give feedback.
-
i did the instructions like you put on the side, i have unlocked the bootloader before, then set up the device and enabled usb debugging again, adb reboot fastboot, fastboot devices to see if its connected properly, then i deleted system_ext, and product, then i got my bootslot, it was a, i deleted b then i tried to flash and it said there was too little space, then i deleted a aswell and then it didn't find the file / directory do you have a telegram, maybe i could send you a video of me trying :0 also rn i reflashed firmware so i can try again |
Beta Was this translation helpful? Give feedback.
-
ok i tried the commands and it works now, it is booting! interestingly i lost no userdata when installing this |
Beta Was this translation helpful? Give feedback.
-
Hi I came across this thread after spending nearly 5 hours installing and reinstalling to try to get this to work… I promise I followed all your instructions - my SD1 128gb takes the flash on the system but when I type flashboot reboot - it just goes to the bootloader. (I have also tried “fastboot reboot -w”. I have reinstalled the recovery image several times too. I followed the instructions on the home page and the instructions above. I am not sure what I am going wrong …. Any pointers / help really appreciated thanks for all your hard work. |
Beta Was this translation helpful? Give feedback.
-
Hello, can you put the commands? I am never able to install, I always get an error, what I execute: ./fastboot delete-logical-partition system_ext_a ./fastboot flash system aosp-arm64-ab-gapps14.0-20240725.img Console: |
Beta Was this translation helpful? Give feedback.
Looks like your partition order is messed up currently.
I assume your device is unlocked, If that is the case, the following steps may work.
Let me know the results.