Cannot load system.img : not enough space - Moto X Q&A

So i was flashing manually ATT 5.1 Zip firmware(Source) with cmd, but i'm stuck on flashing system.img :crying:
E:\Bootloader Tool Kits>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1482130164 bytes
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
And after trying several times and it gives same result, i decided to skip that one. And then i tried to flash TWRP, it successful. I tried to restore my CM12 backup, it's going though but i can't reboot to system. When i reboot to system it keep going back to fastboot :crying:
How i can flash system.img or at least restore my CM12 backup?
EDIT:Now i can reboot to system with CM12 installed (backup) but it could not recognize my sim card
EDIT2:Now it can recognize my sim card. so for now, i ended up just updating my bootloader version hahaha

Solution to "cannot load 'system.img': Not enough space"
LuthfiKun said:
...
Click to expand...
Click to collapse
SOLUTION
I had the same issue using the official 5.1 from Motorola and KidJoe's guide. I saw in the options section that -P "enable parallel loading for multi-flash if there is no [sic] enough memory on host to load whole image."
Thus, using mfastboot flash system system.img -P loaded it in 256MB chunks which worked. It did sit on the moto logo for just long enough to strike fear, but is running beautifully now.
This was on a system with 13.9GB free of 16GB RAM....

I faced this issue just the last day, when I was trying to flash through mfastboot. I tried to flash with rsdlite and it worked fine. I guess the -P switch must be automatic in rsdlite!

-P worked thank you very much

Related

[Q] Possible soft brick. When attempting to flash, gets error can't mount /system

Ok, so I was running a custom ROM (I don't even recall which specific one at the moment....one of the Cromi ROMs). I tried to wipe it and install a new version, and the install didn't go as smoothly as planned. I can still load the TWRP recovery system, and begin attempting to install any ROM, but when it gets to the point where it says it's installing, the bar across the bottom that should show progress disappears almost instantly and the next button becomes available. When I go to reboot, it warns that there is no OS installed. Of course if I continue anyway, it won't boot beyond the Asus splash screen. There are errors in multiple places saying that it can't mount /system. I saw this error in the log file generated, I saw it during reboot, and there was some point in the TWRP screens where I saw it, but can't recall where at this moment. If I go into the Mounts section, System is not checked and I cannot check it.
I tried following the instructions on the unbricking thread and got stuck. I fear this has likely only made matters worse.
Following these steps:
Code:
fastboot erase boot
fastboot erase staging
fastboot format system
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery.img
fastboot reboot-bootloader
I was able to successfully erase the partitions mentioned, then when I tried to flash the first time, I actually screwed up and didn't have the blob file I needed, so now I go back, and obviously I can't re-erase the other files, but formatting system still works, so I know I'm getting good communication with the device. Then trying to flash the blob to staging, I get:
sending 'staging' (1379 KB)...
FAILED (command write failed (No such device or address))
Any thoughts or suggestions would be greatly appreciated. I've currently got an expensive paperweight.

error flashing system mfastboot xt1052 uk 4.4.4 firmware

edited my build.prop, pasted back my original build.prop,tried reboot ,wouldnt reboot flash moto globe then vibrate then black screen,
booted to bootloader to flash stock firmware, every other file flashed except system .img.
formatted sytem but stil a no go.
this is what i get in command prompt.
when restoring my moto x to stock 4.4.4. retail-gb firmware everything else flashes except the system.img file i get this error : c:\android>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 968495348 bytes
error: cannot load 'system.img': Not enough space
i dont know what to do.
You typed sysytem instead of system, but that's probably just a typo in your post. I can't help you with why mfastboot won't flash the system.img when that's what it was created to do.
nhizzat said:
You typed sysytem instead of system, but that's probably just a typo in your post. I can't help you with why mfastboot won't flash the system.img when that's what it was created to do.
Click to expand...
Click to collapse
in command prompt i typed system
i dont get it,its like the system partition doesnt have enough space to load it on, but ive had 4.4.4 running on it but i messed up my build.prop, well believe it or not i pasted my original build.prop back into system and then my phone wouldnt boot.
If you have the proper 4.4.4 sbf, try rsdlite . Your phone will be wiped though.
I solved it , in the unzipped file there was an XML file with a max download limit line and I erased it from the file in notepad and saved it ,then reflashed all parts again.

I think there is an issue with the factory image for 5.1

I downloaded the factory image from two places and was able to flash the boot image and the radio manually but when I go to flash the image itself I receive this.
I am rooted using the Nexus root tool kit with twrp recoovery
fastboot -w update [image file].zip, I receive
C:\Android\platform-tools>fastboot -w update image-shamu-lmy47d.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
??
I have flsh each manually and using the flash all plus used the tool kt
Any ideas
I tried the flash-all.bat and got the same error. I extracted all the files from the zip and flashed the images separately and it worked fine.
worldsoutro said:
I downloaded the factory image from two places and was able to flash the boot image and the radio manually but when I go to flash the image itself I receive this.
I am rooted using the Nexus root tool kit with twrp recoovery
fastboot -w update [image file].zip, I receive
C:\Android\platform-tools>fastboot -w update image-shamu-lmy47d.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
??
I have flsh each manually and using the flash all plus used the tool kt
Any ideas
Click to expand...
Click to collapse
Last time I had that error, it turned out I had an outdated version of fastboot. I was using the packaged version, adnroid-tools-fastboot, on Ubuntu and all was well after installing the latest version through the Android SDK. Not sure if the same would apply here but that was my experience.
Marcellus1 said:
I tried the flash-all.bat and got the same error. I extracted all the files from the zip and flashed the images separately and it worked fine.
Click to expand...
Click to collapse
Same thing here, when I got the error I flashed system, boot and recovery from the zip manually (I've kept my cache and userdata intact to avoid the factory reset).
It went all good but at the first boot the phone executed the encryption of the memory because I've had un-encrypted it when I was on 5.0.1
Yeah I end up flashing each file one by one. I was also getting the errors. All seem fine now
---------- Post added at 01:21 AM ---------- Previous post was at 01:19 AM ----------
This update was a nightmare took me 6 hours to update. I'm not a noib either. Lol

Bricked? Need Help!

I unlocked the bootloader and was going to install CM. Accidentally wiped the internal storage too using twrp. Tried to mount USB so that I could copy the CM and gapps zipps but it just wouldn't copy from the computer. Tried to reboot and now I'm stuck on the "warning bootloader unlocked" screen. It looks like there is no OS on the phone!
EDIT: I can't even switch it off. Every time I hold down the power button, it just reboots to the same screen. So, I don't see any way of being able to boot into recovery. ;(
EDIT 2: I've got my hands on the exact AsiaRetail firmware I was on earlier. Does that help in any way? I've been reading that it might.
EDIT3: I've managed to get the phone into fastboot. All that needed to be done was hold on to the volume down and power buttons for a bit after the screen turned off and then let go.
It turns out I only got the OTA update zip. Can't flash from that one right? Where can I get hold of lollipop firmware for XT1052 that I can flash using fastboot?
What can I do from here?
Please help!
Okay, I'm at my last straw here. Someone please help! This is where I'm stuck now.
C:\Users\Soumen\Downloads\XT1052_GHOST_RETASIA_5.1_LPA23.12-15.5_cid7_CFC.xml>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1431847344 bytes
error: cannot load 'system.img': Not enough space
soumen08 said:
Okay, I'm at my last straw here. Someone please help! This is where I'm stuck now.
C:\Users\Soumen\Downloads\XT1052_GHOST_RETASIA_5.1_LPA23.12-15.5_cid7_CFC.xml>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1431847344 bytes
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
I've got an xt1060 (Vzn US version) but have heard of and/or seen most of your "error" messages before. If you google all those things, you'll see everything from "you've got the wrong version of fastboot/mfastboot" to "OEM /system restores/installs can restore your /recovery partition to the system version" and more. Feel free to chase it down or you can just try to get the thing back to a working state and worry about things like custom recovery and root later. This might be important to you if you've gone to pains to root the phone, so if it's not rooted, it is probably less of a big deal than if it is.
I'm not sure you gave enough "context" before & after your error on /system flash (like whether you were following down a complete list as in one of the flash.xml files in that same folder), but it appears from your path that you've got a full factory image of 5.1 in the original .xml format. If that's so and you just want to restore and don't care about root or any data on the phone, then do something like this:
Download RSD Lite (version 6.2.4 would do) from somewhere and set it up. Get the phone back in fastboot. Make sure it shows up in a "fastboot devices" command. Run RSD (virus check the thing first) and open up the .xml file (or flashfile.xml from within if it wants that). Make sure the phone is attached in fastboot.
Run RSD on that and it should restore the everything. Meanwhile, don't forget that any data you had saved will be gone (from /sdcard/0 etc).
If that succeeds (should take 30 minutes or less) and another 5 for first boot then you can think about other stuff like custom recovery & root, but only if you've got an unlocked bootloader. I have no idea whether there's any current way to an unlocked bootloader. Mine is a DE model so it's unlocked and I'm not up on current 5.1-compatible methods.
----------------------
By the way: I jotted this reply down about 3 hours back, then had to go out to do some stuff for awhile and just am back now. If someone solved it or you've solved it, just disregard this reply. Cheers.
Well, I've got it back up now. Turns out the problem was that my system didn't have enough free RAM to load the entire thing to RAM, split it into parts and then transfer it (which is what it does on the inside). So, rebooting the system solved the problem.

One partition is dead.

I have pixel 4 xl in stock rom.
No matter what i do one partition stays corrupted.
I have flashed rom on partition A with wiping out whole device hoping it would restore but partition B was still corrupted. So i change partition in fastboot mode and tried to flash stock rom with flash all.sh without any kind of modification Hoping it would fix it and device booted but while doing so it corrupted partition A. Than i tried using googles online flashing tool with wiping my device but still experienced same issue. Anyone have any idea what might have gone wrong or how to restore both partition.
I can not use magisk update on inactive partition because i dont see that option, maybe because of this I'm also unable to use viper4android for some reason. Please if anyone have same issue or had same issue let me know how to solve it
Scytherblack said:
I have pixel 4 xl in stock rom.
No matter what i do one partition stays corrupted.
I have flashed rom on partition A with wiping out whole device hoping it would restore but partition B was still corrupted. So i change partition in fastboot mode and tried to flash stock rom with flash all.sh without any kind of modification Hoping it would fix it and device booted but while doing so it corrupted partition A. Than i tried using googles online flashing tool with wiping my device but still experienced same issue. Anyone have any idea what might have gone wrong or how to restore both partition.
I can not use magisk update on inactive partition because i dont see that option, maybe because of this I'm also unable to use viper4android for some reason. Please if anyone have same issue or had same issue let me know how to solve it
Click to expand...
Click to collapse
Without cat logs, errors, pics, or system clarity on what was done to the partitions to land you here, we cant really help. I suspect tho, you may have tried Android 12 preview, and you are stuck now?
If not, and 12 wasnt used, explain what's been done and how you feel the partition is broken.
GROOVYJOSHCLARK said:
Without cat logs, errors, pics, or system clarity on what was done to the partitions to land you here, we cant really help. I suspect tho, you may have tried Android 12 preview, and you are stuck now?
If not, and 12 wasnt used, explain what's been done and how you feel the partition is broken
Click to expand...
Click to collapse
GROOVYJOSHCLARK said:
Without cat logs, errors, pics, or system clarity on what was done to the partitions to land you here, we cant really help. I suspect tho, you may have tried Android 12 preview, and you are stuck now?
If not, and 12 wasnt used, explain what's been done and how you feel the partition is broken.
Click to expand...
Click to collapse
I was not using any other rom but i was trying to install twrp recovery by first booting into it, first thing i noticed was i couldn't decrypt my phone even though i put the right password, so i went back to bootloader and tried to flash stock boot img to see if i could get into twrp but same thing happened so i thought let me change to boot partition and try, but it wasn't even booting into partition B it shows me google logo and than boot back to bootloader and than no matter what i restart or power off it goes straight back to bootloader, unless i change back to partition A.
So i left twrp behind thinking i can still flash whatever i like using commands but to repair partition B i used command "fastboot --set-active=b" and than i flashed latest og stock file with flash-all.bat.
And phone booted into partition B but just to make sure i rebooted back to bootloader and tried changing partition again to A using "fastboot --set-active=a" and it booted into google logo and went back to bootloader and stuck.
So as you can see doen here i dont see option of updating using inactive partition,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So please let me know what logs so i can provide em here.
Thanks
Scytherblack said:
I was not using any other rom but i was trying to install twrp recovery by first booting into it, first thing i noticed was i couldn't decrypt my phone even though i put the right password, so i went back to bootloader and tried to flash stock boot img to see if i could get into twrp but same thing happened so i thought let me change to boot partition and try, but it wasn't even booting into partition B it shows me google logo and than boot back to bootloader and than no matter what i restart or power off it goes straight back to bootloader, unless i change back to partition A.
So i left twrp behind thinking i can still flash whatever i like using commands but to repair partition B i used command "fastboot --set-active=b" and than i flashed latest og stock file with flash-all.bat.
And phone booted into partition B but just to make sure i rebooted back to bootloader and tried changing partition again to A using "fastboot --set-active=a" and it booted into google logo and went back to bootloader and stuck.
So as you can see doen here i dont see option of updating using inactive partition, View attachment 5298203
So please let me know what logs so i can provide em here.
Thanks
Click to expand...
Click to collapse
Wait, back up, what are you trying to do now? Install MAGISK, or fix the partitions?
You noted the partition and slot issues, but then went into MAGISK. You do not need to select anything in MAGISK for boot or slots, you simply need to patch the boot.img (in the pic you posted), then patch the boot.img with magisk, then:
fastboot flash boot magisk_patched.img --> (whatever is saved to your download folder) FROM MAGISK app patching it.
You must use the patched boot.img (now renamed with MAGISK and the string it adds) and fastboot it, then boot normally and you are ROOT'd. Do not mess with slots when doing this process, just use the command I laid out once you patch it. MAGISK patching isnt the same as installing GAPPs and a ROM, you do not switch slots to install.
This is all assuming you are only trying to ROOT the device and not fix your issues with the partitions. If you want to fix the partition layout, use the flash-all with the -W left intact on both slots (I force it to reboot after it erases userdata), then boot into fastboot and change to slot B (first flash-all was done to slot A). Afterwards both slots are refreshed and you can go for it. Back EVETYTHING up first as you will lose everything but it will get you back in shape.
Dont bother installing TWRP, but I dont think its ready for 11 yet anyways (decryption) but I havent used TWRP in months. Fastboot it instead of installing it:
fastboot boot twrp-BLAHBLAHBLAH.img
GROOVYJOSHCLARK said:
Wait, back up, what are you trying to do now? Install MAGISK, or fix the partitions?
You noted the partition and slot issues, but then went into MAGISK. You do not need to select anything in MAGISK for boot or slots, you simply need to patch the boot.img (in the pic you posted), then patch the boot.img with magisk, then:
fastboot flash boot magisk_patched.img --> (whatever is saved to your download folder) FROM MAGISK app patching it.
You must use the patched boot.img (now renamed with MAGISK and the string it adds) and fastboot it, then boot normally and you are ROOT'd. Do not mess with slots when doing this process, just use the command I laid out once you patch it.
This is all assuming you are only trying to ROOT the device and not fix your issues with the partitions. If you want to fix the partition layout, use the flash-all with the -W left intact on both slots (I force it to reboot after it erases userdata), then boot into fasttboot and change to slot B (first flash-all was done to slot A). Afterwardss both slots are refreshed and you can go for it. BackEVETYTHING up first as you will lsoe everything but it iwll get you back in shape.
Dont bother installing TWRP, but I dont think its ready for 11 yet anyways (decryption) but I havent used TWRP in months. Fastboot it instead of installing it:
fastboot boot twrp-BLAHBLAHBLAH.img
Click to expand...
Click to collapse
I'm trying to fix my partition, but i show magisk because before this partition problem i had third method for monthly patch update for os NAMED INSTALL IN INACTIVE BOOT SLOT which have disappeared from my magisk
Scytherblack said:
I'm trying to fix my partition, but i show magisk because before this partition problem i had third method for monthly patch update for os NAMED INSTALL IN INACTIVE BOOT SLOT which have disappeared from my magisk
Click to expand...
Click to collapse
you are way past that now, when you flashed the boot.img manually from stock, you overwrote MAGISK TWRP and anything else you had in the boot partition. Patch the boot.img for your ROM (MAGISK), then fastboot it. Its the only way to get ROOT back with what you have done.
You F'd up the A partition when you tried to install TWRP, failed, then overwrote the boot partition manually.
To fix the partitions now, force SLOT A, factory firmware with -W left, then after A completes when erasing USERDATA, interrupt the boot (before SLOT A goes into OS), and switch to slot B, and redo.
GROOVYJOSHCLARK said:
Wait, back up, what are you trying to do now? Install MAGISK, or fix the partitions?
You noted the partition and slot issues, but then went into MAGISK. You do not need to select anything in MAGISK for boot or slots, you simply need to patch the boot.img (in the pic you posted), then patch the boot.img with magisk, then:
fastboot flash boot magisk_patched.img --> (whatever is saved to your download folder) FROM MAGISK app patching it.
You must use the patched boot.img (now renamed with MAGISK and the string it adds) and fastboot it, then boot normally and you are ROOT'd. Do not mess with slots when doing this process, just use the command I laid out once you patch it. MAGISK patching isnt the same as installing GAPPs and a ROM, you do not switch slots to install.
This is all assuming you are only trying to ROOT the device and not fix your issues with the partitions. If you want to fix the partition layout, use the flash-all with the -W left intact on both slots (I force it to reboot after it erases userdata), then boot into fastboot and change to slot B (first flash-all was done to slot A). Afterwards both slots are refreshed and you can go for it. Back EVETYTHING up first as you will lose everything but it will get you back in shape.
Dont bother installing TWRP, but I dont think its ready for 11 yet anyways (decryption) but I havent used TWRP in months. Fastboot it instead of installing it:
fastboot boot twrp-BLAHBLAHBLAH.img
Click to expand...
Click to collapse
I've been rooting my devices for 4-5 years amd been using magisk for last 3 years at least i remember how to do that but i just put magisk as example to show that there's something wrong with my boot partitions
GROOVYJOSHCLARK said:
you are way past that now, when you flashed the boot.img manually from stock, you overwrote MAGISK TWRP and anything else you had in the boot partition. Patch the boot.img for your ROM, then fastboot it. Its the only way to get ROOT back with what you have done.
Click to expand...
Click to collapse
So there is no way to get both of my partition back up and running??
Because now what happens is i cant update my phone with built in system update like normal phone, my phone always download the whole file of update like 2 GB instead of just the patch of few MBs.
Scytherblack said:
I've been rooting my devices for 4-5 years amd been using magisk for last 3 years at least i remember how to do that but i just put magisk as example to show that there's something wrong with my boot partitions
Click to expand...
Click to collapse
I am telling you exactly what happened and how to fix it, its not about how long anyone has been rooting anything. Pixels use A/B, so its much different than ever before. There is no recovery partition anymore, it now lives in the BOOT.
Redo the factory firmware on BOTH slots, and start over. Then you will be golden.
Scytherblack said:
So there is no way to get both of my partition back up and running??
Because now what happens is i cant update my phone with built in system update like normal phone, my phone always download the whole file of update like 2 GB instead of just the patch of few MBs.
Click to expand...
Click to collapse
No idea, because I have no idea what you truly did. I would redo both partitions, you mis-stepped with the manual flashing of the boot.img during the TWRP process so I have no idea how damaged it is now.
I also have no idea what ROM you are using, or if official, or even what internal updater you are using so its lacking info.
GROOVYJOSHCLARK said:
I am telling you exactly what happened and how to fix it, its not about how long anyone has been rooting anything. Pixels use A/B, so its much different than ever before. There is no recovery partition anymore, it now lives in the BOOT.
Redo the factory firmware on BOTH slots, and start over. Then you will be golden.
Click to expand...
Click to collapse
I have tried that in past so here's what i have tried to fix step by step.
1. I downloaded the latest Android 11 factory images from google developer site, unzip, connected my phone copied adb files to unzipped factory images and than used flash-all.bat
2.it flashed it on active slot A, since everything was wiped clean i had to boot device and enable developer options for adb support than rebooted back to bootloader.
3. Used command fastboot --set-active=B to change the boot slot and than install the factory images.
4. Booted enable developer options and rebooted back to bootloader to see if both boot A/B works and used command fastboot --set-active=A. tried to reboot it went to google logo for once and back to bootloader. Now whatever i do reboot or power off when it turns on it goes back to bootloader unless i switched back to Boot slot B
Now if i flash everything again on slot A it will work just fine but after slot A works fine slot B will be bricked or corrupted.
So i was thinking if i could manage to find EDL files for pixel 4 XL it would probably fix everything .
Scytherblack said:
I have tried that in past so here's what i have tried to fix step by step.
1. I downloaded the latest Android 11 factory images from google developer site, unzip, connected my phone copied adb files to unzipped factory images and than used flash-all.bat
2.it flashed it on active slot A, since everything was wiped clean i had to boot device and enable developer options for adb support than rebooted back to bootloader.
3. Used command fastboot --set-active=B to change the boot slot and than install the factory images.
4. Booted enable developer options and rebooted back to bootloader to see if both boot A/B works and used command fastboot --set-active=A. tried to reboot it went to google logo for once and back to bootloader. Now whatever i do reboot or power off when it turns on it goes back to bootloader unless i switched back to Boot slot B
Now if i flash everything again on slot A it will work just fine but after slot A works fine slot B will be bricked or corrupted.
So i was thinking if i could manage to find EDL files for pixel 4 XL it would probably fix everything .
Click to expand...
Click to collapse
Thats not how I laid it out. You are booting BEFORE doing slot B so its not repairing it to factory.
Why Emergency Download Mode? You replace the fastboot and all files needed to run and boot Android WITH the factory image. You do not need EDL, you are overthinking this a lot.
ALL you need to do is to successfully flash the FACTORY firmware with -W on BOTH slots before booting and its back to factory fresh. Do not use the web (chrome) version at all, that wont work to fix your issue, and do not use an OTA. ONLY use the factory firmware and reset both slots BEFORE the OS. Once slot B completes, let it boot, go through the OS, then prepare it for a ROM, or use ROOT with the stock OS.
Enabling ADB in dev options ONLY enables you to use ADB from a PC. You do NOT need to enable ADB in dev options to flash a firmware/TWRP/ROM.
Everything changed with A/B partitions, so a lot is different than how it used to be.
GROOVYJOSHCLARK said:
Thats not how I laid it out. You are booting BEFORE doing slot B so its not repairing it to factory.
Why Emergency Download Mode? You replace the fastboot and all files needed to run and boot Android WITH the factory image. You do not need EDL, you are overthinking this a lot.
ALL you need to do is to successfully flash the FACTORY firmware with -W on BOTH slots before booting and its back to factory fresh. Do not use the web (chrome) version at all, that wont work to fix your issue, and do not use an OTA. ONLY use the factory firmware and reset both slots BEFORE the OS. Once slot B completes, let it boot, go through the OS, then prepare it for a ROM, or use ROOT with the stock OS.
Enabling ADB in dev options ONLY enables you to use ADB from a PC. You do NOT need to enable ADB in dev options to flash a firmware/TWRP/ROM.
Everything changed with A/B partitions, so a lot is different than how it used to be.
Click to expand...
Click to collapse
Okay I'll try this Tonight thank you, I'll post the result
Scytherblack said:
Okay I'll try this Tonight thank you, I'll post the result
Click to expand...
Click to collapse
Trust me when I tell you this, I was VERY confused when I first got my Pixel 2XL with A/B (coming from an older HTC 10 that was a single slot). I was so used to having a recovery partition, single slot, and system (not system-less), that I knew all the ins and outs of Android, writing code / ROMs, ROOT, ETC., so I could advise from memory.
When A/B came along, I didn't have it until my 2XL, then 3XL, and now my 4XL so I had to learn it.
At first, I kept screwing up the device (almost exactly the scenario you are in). 1 slot worked, the other slot was F'd. It wasn't until I figured out how they actually worked, then it all made sense and why I kept damaging one or the other (or both slots). The slots are great for updates, but terrible for ROM development, and firmware flashing due to issues like this. It is no longer a simple, easy peasy process that is once was, BUT there is a light at the end of tunnel. Once you familiarize yourself with the A/B partitions, and how to recover from mistakes, or failed updates, or ROM install issues, you will become an Android A/B genius. It will make sense the more you use it, but there is a decent amount of changes to re-learn if/when coming from an older device so don't give up. You can recover from this with a factory firmware (assuming BOOTLOADER is truly unlocked which it sounds like it is), so keep at it.
I have had my 2XL and 4XL so bad, it wouldn't boot at times, but eventually you will figure it out and fix it. Factory images are a saving grace, they will undo the damage. My 3 XL is a verizon piece of junk (LOCKED BOOTLOADER) so it doesnt get used and sits brand new in the box waiting to be off lease and sold for the garbage it is. My 2XL/4XL were both bought outright from Google, my 3XL was a lease package my wife needed to sign up her daughter so I got a free 3XL I dont use (and wont use). I REFUSE to use anything from verizon with a locked BL. Its the main reason for Android, so why cripple it? F verizon, I hate them!
GROOVYJOSHCLARK said:
Trust me when I tell you this, I was VERY confused when I first got my Pixel 2XL with A/B (coming from an older HTC 10 that was a single slot). I was so used to having a recovery partition, single slot, and system (not system-less), that I knew all the ins and outs of Android, writing code / ROMs, ROOT, ETC., so I could advise from memory.
When A/B came along, I didn't have it until my 2XL, then 3XL, and now my 4XL so I had to learn it.
At first, I kept screwing up the device (almost exactly the scenario you are in). 1 slot worked, the other slot was F'd. It wasn't until I figured out how they actually worked, then it all made sense and why I kept damaging one or the other (or both slots). The slots are great for updates, but terrible for ROM development, and firmware flashing due to issues like this. It is no longer a simple, easy peasy process that is once was, BUT there is a light at the end of tunnel. Once you familiarize yourself with the A/B partitions, and how to recover from mistakes, or failed updates, or ROM install issues, you will become an Android A/B genius. It will make sense the more you use it, but there is a decent amount of changes to re-learn if/when coming from an older device so don't give up. You can recover from this with a factory firmware (assuming BOOTLOADER is truly unlocked which it sounds like it is), so keep at it.
I have had my 2XL and 4XL so bad, it wouldn't boot at times, but eventually you will figure it out and fix it. Factory images are a saving grace, they will undo the damage. My 3 XL is a verizon piece of junk (LOCKED BOOTLOADER) so it doesnt get used and sits brand new in the box waiting to be off lease and sold for the garbage it is. My 2XL/4XL were both bought outright from Google, my 3XL was a lease package my wife needed to sign up her daughter so I got a free 3XL I dont use (and wont use). I REFUSE to use anything from verizon with a locked BL. Its the main reason for Android, so why cripple it? F verizon, I hate them!
Click to expand...
Click to collapse
i got error saying failed! partition should be flash in fastbootd
and now my phone is stuck on bootloop
Scytherblack said:
i got error saying failed! partition should be flash in fastbootd
and now my phone is stuck on bootloop
Click to expand...
Click to collapse
Again, we need more info. You did something wrong because it automatically reboots into fastboot during the process to update the firmware.
We need to find out why it didn't it reboot into fastboot so if you prevented that from happening, don't. Start over and let it go through the process. The batch file automatically reboots to fastboot during the system image push (so if it didnt do that), then its your reason for the boot failure.
GROOVYJOSHCLARK said:
Again, we need more info. You did something wrong because it automatically reboots into fastboot during the process to update the firmware.
We need to find out why it didn't it reboot into fastboot so if you prevented that from happening, but don't. Start over and let it go through the process.
Click to expand...
Click to collapse
Update i did manage to get it all installed without me interfering. But still the same issue only one partition works.
And you did both slots A/B with the firmware? Can you confirm you are on the absolute latest ADB and drivers? Also run this command to see if you are stuck in a snapshot update and cant write:
fastboot snapshot-update cancel
Then try to redo the slot thats failing. I have had something like this happen a long time ago but not quite the same. It was due to the snapshot. I cant remember if this needs to be run after switching slots so try it, and if it doesnt do anything, then switch to A, run it, switch to B, and run it, then try the firmware over again on the failed slot.
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8833 KB)...
OKAY [ 0.327s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version c2f2-0.3-7062597
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition logfs
OKAY [ 0.269s]
finished. total time: 0.597s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
target reported max download size of 268435456 bytes
sending 'radio_a' (82708 KB)...
OKAY [ 2.127s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g8150-00082-210106-B-7065218
(bootloader) Flashing partition modem_a
OKAY [ 0.487s]
finished. total time: 2.617s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.396s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.040s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (782 MB) to disk... took 8.684s
archive does not contain 'system.sig'
extracting system_other.img (23 MB) to disk... took 0.162s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.006s
archive does not contain 'vbmeta.sig'
extracting vendor.img (730 MB) to disk... took 7.530s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: c2f2-0.3-7062597
Baseband Version.....: g8150-00082-210106-B-7065218
Serial Number........: 9A231xxxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.070s]
checking version-bootloader...
OKAY [ 0.069s]
checking version-baseband...
OKAY [ 0.069s]
sending 'boot_a' (65536 KB)...
OKAY [ 1.549s]
writing 'boot_a'...
OKAY [ 0.336s]
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.292s]
writing 'dtbo_a'...
OKAY [ 0.107s]
sending sparse 'system_a' 1/4 (262140 KB)...
OKAY [ 5.982s]
writing 'system_a' 1/4...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.839s
this is what i get when i tried to install factory images using flash-all.bat
GROOVYJOSHCLARK said:
And you did both slots A/B with the firmware? Can you confirm you are on the absolute latest ADB and drivers? Also run this command to see if you are stuck in a snapshot update and cant write:
fastboot snapshot-update cancel
Then try to redo the slot thats failing. I have had something like this happen a long time ago but not quite the same. It was due to the snapshot. I cant remember if this needs to be run after switching slots so try it, and if it doesnt do anything, then switch to A, run it, switch to B, and run it, then try the firmware over again on the failed slot.
Click to expand...
Click to collapse
fastboot: usage: unknown command snapshot-update this is what i got for snap shot

Categories

Resources