This is my Situation:
I was using a ROM Based in Android 5.1.1 in specific ([5.1.1_r29] Team Razor), everything was good but I read that I had to update bootloader and radio but never saw a link, looking for internet for help found this GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip version to install via RSD Lite, everything was good, but when I tried to flash the recovery I get that I couldnt flash it 'cuz is not compatible:
Code:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
My device start normally, but I want too install the Recovery and root it, I couldnt find any information about my problem or a real solution.
I've read about flash a system.img but what "system.img"?, I'm looking for some help, if anyone pass thru this and have the answer would be awesome if you share it.
Thank you in advance.
[SOLVED]
Unzip mfastboot.exe into \platform-tools\
flashing: mfastboot flash recovery recovery.img
done!
The info in your post is kind of confusing. What does ghost_retail*.xml.zip have to do with looking for a custom recovery which is what I am guessing you want on your "working" device? All you could get out of the .xml.zip file would be something like stock_recovery.img which wouldn't allow you do recoveries. Sounds like you want to download TWRP (or Philz) from somewhere and boot into fastboot mode, then use "fastboot flash recovery {whatever_recovery.img}" to flash the custom recovery.
If that's not your intent then post back and try to explain better. It seems like you had things "working well" on TR511 but still decided to update BL & Rad anyway. There's no need to update anything if it's all working OK and there's no new features (like a working speakerphone or something) in there for you.
Also: the 'reported output' in your
Code:
section is pretty inconclusive for troubleshooting. It almost sounds as if you tried to flash (or RSDLite) something huge like the entire image (805,306,368 bytes?). I've built lots of recoveries and they average more like 5-10MB. , not 800MB. Also it says something about "battery low" in there. I'm lost on that output ;;)
And another note: System.img has little or nothing to do with getting recovery back together. It's just the packed up version of /system/.... in the "SYSTEM" partition.
Maybe for starters: tell us once again what ROM is working right now including version. Then tell us what recovery you want to flash. Someone can likely help out if we know those things. You appear to have unlocked BL since you're flashing ROMs so there's hope.
Anyway, good luck.
[QUOTE="Mexickano, post: 64350799, member: 4488447"]This is my Situation:
I was using a ROM Based in Android 5.1.1 in specific ([5.1.1_r29] Team Razor), everything was good but I read that I had to update bootloader and radio but never saw a link, looking for internet for help found this[B] GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip[/B] version to install via RSD Lite, everything was good, but when I tried to flash the recovery I get that I couldnt flash it 'cuz is not compatible:
[code](bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
My device start normally, but I want too install the Recovery and root it, I couldnt find any information about my problem or a real solution.
I've read about flash a system.img but what "system.img"?, I'm looking for some help, if anyone pass thru this and have the answer would be awesome if you share it.
Thank you in advance.[/QUOTE]
I was on 5.1.1 and downgraded to 5.1 stock, everything ok till now?
when I'm trying to flash TWRP this appears
Code:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
Mexickano said:
I was on 5.1.1 and downgraded to 5.1 stock, everything ok till now?
when I'm trying to flash TWRP this appears
Code:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
Click to expand...
Click to collapse
Thanks. I'm assuming the battery low message is just a confused response and not really true? Also, I see that the recovery.img (whatever you are calling TWRP) is ~8.5MB which seems fine. It looks like fastboot on the PC (whatever) isn't happy talking to the xt1053 booted into fastboot/bootloader. Could you try doing a "fastboot devices" and show the output back here? If it's anything other than an OK ID number for the device, then it might be interesting.
I'll attach a version of fastboot I just recently used to flash a recovery in case you want to try it.
Another thing: I've never had this happen myself, but have heard about it a few times: When booted, use some explorer to look in your /system folder for a file with a name like this "recovery-from-boot.p". If it's there, supposedly it will keep forcing the default non-custom recovery to be written regardless of what you do. I'm sure there's a work-a-round for that like ..
What about using the "Fastboot boot "your-custom-recovery.img" if you have that "recovery-from-boot.p" problem? It should take you into the recovery you're trying to write without bothering to write it to the recovery partition. From there, you would be root if you can open the TWRP console, and get rid of the recovery-from-boot.p file, install root, etc, then finally, flash recovery with whatever combination of stuff ^^ it takes.
hachamacha said:
Thanks. I'm assuming the battery low message is just a confused response and not really true? Also, I see that the recovery.img (whatever you are calling TWRP) is ~8.5MB which seems fine. It looks like fastboot on the PC (whatever) isn't happy talking to the xt1053 booted into fastboot/bootloader. Could you try doing a "fastboot devices" and show the output back here? If it's anything other than an OK ID number for the device, then it might be interesting.
The battery message is because the Battery is low, that's it, no big deal.
I can boot into fastboot w/o issues and I will post back the result of "fastboot devices".
I'll attach a version of fastboot I just recently used to flash a recovery in case you want to try it.
how can I use it, excuse my ignorance, but I see a .exe inside a .zip
Another thing: I've never had this happen myself, but have heard about it a few times: When booted, use some explorer to look in your /system folder for a file with a name like this "recovery-from-boot.p". If it's there, supposedly it will keep forcing the default non-custom recovery to be written regardless of what you do. I'm sure there's a work-a-round for that like ..
What about using the "Fastboot boot "your-custom-recovery.img" if you have that "recovery-from-boot.p" problem? It should take you into the recovery you're trying to write without bothering to write it to the recovery partition. From there, you would be root if you can open the TWRP console, and get rid of the recovery-from-boot.p file, install root, etc, then finally, flash recovery with whatever combination of stuff ^^ it takes.
Click to expand...
Click to collapse
There's a "recovery-from-boot.p" but I cant delete it or change the name because I'm not root, can I be root without installing Recovery?
Mexickano said:
There's a "recovery-from-boot.p" but I cant delete it or change the name because I'm not root, can I be root without installing Recovery?
Click to expand...
Click to collapse
Should be able to work around that, but the workaround is to find a way to become root, so I was mentioning this in the last post of mine:
What about using the "Fastboot boot "your-custom-recovery.img" if you have that "recovery-from-boot.p" problem? It should take you into the recovery you're trying to write without bothering to write it to the recovery partition. From there, you would be root if you can open the TWRP console, and get rid of the recovery-from-boot.p file, install root, etc, then finally, flash recovery with whatever combination of stuff ^^ it takes.
Click to expand...
Click to collapse
I'm trying to think of ways to do this above and I think that is actually one of them and there should be another way as well.
Way one: There's a fastboot command "fastboot boot "{name-of-your-recovery-img-for-twrp}". That command causes it to boot (well, if all goes well) into recovery without writing recovery. If it works, you're a root user because that's how recovery is. In TWRP, I'm sure there's a console command as well as a file explorer or some kind. You'll have to remount as read-write /system partition. From a console it'd look like this "sudo mount -o remount,rw /system" (I'm pretty sure that's it). You can look it up or try it with a w where the rw is right now. Also you can just do a plain "mount" command and look at the output to see what it's mounted as in case you need it.
If you get into whatever file explorer twrp has available, then navigate to that file 'recovery_from_boot.p' and see if the file system is in read-write mode by trying to rename it (like to recovery_from_boot.p.orig). If that doesn't work, then go to the special commands or advanced (sorry, not recalling twrp that well) and mount /system as read-write whatever that takes, like an unmount & a mount. Then go back to file explorer and do the rename. I hate deleting files I'm not 100% sure about, but you can do what you like there.
Way two: If you can boot into the version of twrp.img on your PC, then I'm not seeing why you can't install root from it too. Worth a try. You might have some other remaining problem between whatever fastboot you've got on the pc and the bootloader, but it's worth a shot. There's a number of write-ups on how to do this if you google it. Anyway, once you've rooted you can reboot and you should only lose recovery, not root. Once booted, install supersu, etc. usual stuff, then if it all checks out, flash the recovery and it should stay once you've dumped that file.
Way two and a half: If I understand how the normal boot works on androids, then you should be able to avoid having recovery erased at least one time by using the buttons either to go directly to recovery (volume_up + power) or (volume_down+volume_up + power) RIGHT after you flash recovery. I'm just thinking that /system isn't going to execute if you pick the right combo of buttons to get into recovery but it'll be a pita because you have to burn recovery then hit it on the first boot after or it's gone.
Cheers.
hachamacha said:
Way one: There's a fastboot command "fastboot boot "{name-of-your-recovery-img-for-twrp}". That command causes it to boot (well, if all goes well) into recovery without writing recovery. If it works, you're a root user because that's how recovery is. In TWRP, I'm sure there's a console command as well as a file explorer or some kind. You'll have to remount as read-write /system partition. From a console it'd look like this "sudo mount -o remount,rw /system" (I'm pretty sure that's it). You can look it up or try it with a w where the rw is right now. Also you can just do a plain "mount" command and look at the output to see what it's mounted as in case you need it.
there is a "recovery-from-bot.p", I cant delete it, rename it or anything else since I aint get root privileges.
I can get into fastboot and when I type fastboot devices I get:
TA0000143X fastboot
If you get into whatever file explorer twrp has available, then navigate to that file 'recovery_from_boot.p' and see if the file system is in read-write mode by trying to rename it (like to recovery_from_boot.p.orig). If that doesn't work, then go to the special commands or advanced (sorry, not recalling twrp that well) and mount /system as read-write whatever that takes, like an unmount & a mount. Then go back to file explorer and do the rename. I hate deleting files I'm not 100% sure about, but you can do what you like there.
Way two: If you can boot into the version of twrp.img on your PC, then I'm not seeing why you can't install root from it too. Worth a try. You might have some other remaining problem between whatever fastboot you've got on the pc and the bootloader, but it's worth a shot. There's a number of write-ups on how to do this if you google it. Anyway, once you've rooted you can reboot and you should only lose recovery, not root. Once booted, install supersu, etc. usual stuff, then if it all checks out, flash the recovery and it should stay once you've dumped that file.
I cant boot into recovery because I can't flash the Recovery, that's the reason why I created this topic because I CANT flash recovery.
Way two and a half: If I understand how the normal boot works on androids, then you should be able to avoid having recovery erased at least one time by using the buttons either to go directly to recovery (volume_up + power) or (volume_down+volume_up + power) RIGHT after you flash recovery. I'm just thinking that /system isn't going to execute if you pick the right combo of buttons to get into recovery but it'll be a pita because you have to burn recovery then hit it on the first boot after or it's gone.
I cant get into Recovery because there is no Recovery flashed.
What about that fastboot.zip, how I flash it or install it because I see a fastboot.exe inside the zip.
Cheers.
Click to expand...
Click to collapse
I need to know if there's a way to flash another bootloader or anything else?
If I try to delete the "recovery-from-boot.im" in fastboot this message appear:
X:\Android\sdk\platform-tools>fastboot erase /system/recovery-from-boot.img
(bootloader) Variable not supported!
erasing '/system/recovery-from-boot.img'...
(bootloader) Invalid partition name /system/recovery-from-boot.img
FAILED (remote failure)
finished. total time: 0.094s
FINALLY!!
I solved putting mfastboot.exe into /platform-tools/ and typing
mfastboot flash recovery [recovery].img
Thank you for your effort and time.
Mexickano said:
I need to know if there's a way to flash another bootloader or anything else?
If I try to delete the "recovery-from-boot.im" in fastboot this message appear:
X:\Android\sdk\platform-tools>fastboot erase /system/recovery-from-boot.img
(bootloader) Variable not supported!
erasing '/system/recovery-from-boot.img'...
(bootloader) Invalid partition name /system/recovery-from-boot.img
FAILED (remote failure)
finished. total time: 0.094s
FINALLY!!
I solved putting mfastboot.exe into /platform-tools/ and typing
mfastboot flash recovery [recovery].img
Thank you for your effort and time.
Click to expand...
Click to collapse
Cool! I think I also was trying to say "try other versions of fastboot" (like mfastboot). Good deal.
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