Related
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.
Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
bomba697 said:
Hi guys,
I tried to root my P9 today but now I'stuck with a bricked P9.
I can fastboot and use TWRP
The main problem is that I get always failed to mount /data (Invalid argument)
I've tried to Change the file system with TWRP and Format Data but nothing
I've tried the unbrick procedure with Multi-Tool and an old firmware but nothing
Code:
19:21:37: Unbricking started. Your computer may freezes during the process.
19:21:37: flash boot "C:\Users\franc\Desktop\Nuova cartella\boot.img"
19:21:37: The Boot image is flashing successfully
19:21:37: flash system "C:\Users\franc\Desktop\Nuova cartella\system.img"
19:21:53: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (449861 KB)...
OKAY [ 10.490s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.551s
19:21:53: Error#1
19:21:53: flash cust "C:\Users\franc\Desktop\Nuova cartella\cust.img"
19:21:58: Error! You are trying to flash the wrong image!
19:21:58: flash recovery "C:\Users\franc\Desktop\Nuova cartella\recovery.img"
19:22:00: The Recovery image is flashing successfully
19:22:00: Completed
19:22:00: Something went wrong (((
Click to expand...
Click to collapse
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP installations must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start, which steps did you perform and by which tools
Btw, rooting N by SuperSU or O by Magisk is pretty straightforward, but is important that proper, corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
zgfg said:
"P9" - EMUI 4 / Android MM, EMUI 5 / N or EMUI 8 / O
What was exacrly your full firmware name and number (like EVA-L09c532b505 or what)
"TWRP" - which/where from?
(diff TWRP builds must be used for MM, N or N), and if TWRP from TWRP site - that one is definitely not good for N and O
"root" - by SuperSU, Magisk or something else (hopefully not King.... tools or so)
So, from which Huawei firmware did you start which steps did you perform and by which tools
Btw, rooting N by SuperSU or M by Magisk is pretty straightforward, but it is important that proper corresponding TWRPs are used.
And if anything goes wrong (brick or so) stock Boot partition (N) or stock Ramdisk partition (O) can be easily flashed over to go back
Click to expand...
Click to collapse
I'm sorry for the poor description but I was in panic.
Starting from EVA-L09C432B3xx, don't remember the exact version, N 5.0.1
TWRP 3.1.0.-1
SuperSU, https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258. I had big trouble trying to root because every time the phone rebooted before finishing the procedure.
I didn't use any tool at all for unlocking bootloader, flash recovery and root. Just adb and fastboot in cmd + TWRP.
BTW, I recovered the phone! Used DC-Phoenix to reset the phone from fastboot and then made a downgrade to b182.
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
zgfg said:
PS: Why did you flash Cust?
For TWRP or to go back to stock Recovery, you only need to flash recovery (for N) or ramdisk_recovery (for O)
To flash root patch for SuperSU for N (or to restore back) you only need to flash boot partition, similarly for Magisk (O) ramdisk partution.
Click to expand...
Click to collapse
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
bomba697 said:
Because Multi-Tool 8 was asking to flash also CUST to apply unbrik procedure.
The problem was that I wasn't able to mount /data partition. Also from stock recovery I wasn't able to format /data, only wipe the cache
Click to expand...
Click to collapse
If you recovered and if you are on b182 now, you will hopefully receive OTA upgrades tp go back to N
Btw, working procedure for rooting N was described in thread
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Again, if TWRP was not able to mount Data, was it really proper TWRP from XDA Huawei Nougat threads (adapred to support Huawei N and its encryption), like
https://forum.xda-developers.com/p9/development/twrp-t3565703
Some other TWRP 3.1.x.x, even declared for Huawei, maybe good for EMUI 4 / MM but not for EMUI 5 / N
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
kazshizka said:
EDIT: ...DC-Phoenix. Do you have a link and how to use...
Click to expand...
Click to collapse
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
kazshizka said:
EDIT: noticed that you fixed it through DC-Phoenix. Do you have a link where you found it and how to use? I don't mind downgrading coz I'm just gonna use the phone as a backup phone
I got the same issue. If you find an answer please tag me. I think i was using EVA-L19C636B180 Quite sure about the C636 part. TWRP 3.1.0.-3 and using SU but I can't recall the version
Quick background on mine:
I bricked my phone when I did a factory reset and deleted internal storage and accidentally deleted important files while doing so. I flashed a stock update from the warehouse and completely deleted the system instead. I then flashed Lineage ROM which reinstalled the system but now causes me to get stuck in bootup. When I installed Lineage ROM, I got the following error.
Attached photo
https://imgur.com/a/nx6U5bC
Click to expand...
Click to collapse
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
zgfg said:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
bomba697 said:
I didn't use the method posted by @zgfg. What I did was: (this procedure is going to lock back your FRP setting and bootloader, so you can try it but at your own risk)
Use Multi-Tool 8 (https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923) to reinstall stock recovery and recovery2
Download https://www.dc-unlocker.com/downloads/get/jvObBBIo
Put the phone in fastboot
Use the FRP Erase option to recover/format /data (it cost you 15 credit, $15), it was successful
Take empty SD card formatted in NFTS
Put in dload folder the rollback UPDATE.APP file taken from http://download-c1.huawei.com/download/downloadCenter?downloadId=92765&siteCode=it and install it
Last, put in dload folder b182 UPDATE.APP file from http://download-c1.huawei.com/download/downloadCenter?downloadId=91783&siteCode=it
This functioned for me, you can try to skip step 5 and install directly b182.
Click to expand...
Click to collapse
Will check out both methods. I'll try it through TWRP first since it should be easier to use an open bootloader rather than a locked one.
@bomba697 will reinstalling stock recovery fix my deleted system issue? coz I'm not sure if I flashed the custom ROM properly anymore
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
kazshizka said:
UPDATE:
Tried @bomba697 method and fixed my system but I skipped the FRP Erase portion. I just installed the stock recovery straight (thus not paying 15 credits) from the multi tool then rollback using dload then update to b182. Though it did change my system to C900 from C636.
Thank you very very much!!
Click to expand...
Click to collapse
Happy that you found the solution! I tried directly flashing the rom but I wasn't able beacuse of the \data mount error.
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Or just use the MSM tool. Job done
All with varying levels of interpretation, steps, descriptions, and the solution. Not all are useful.
I had the same issue and this worked perfectly to get my device up and running again. Thanks again!!
Hi all!
Here is plan B!
First of all - BEFORE you do some upgrade - make OPSwitch backup and copy to PC !!!!!
If you stuck - it's mean that something is badly damaged and wrong. Some of the files reside in the areas where upgrade tools (including Fastboot!) can't change and repair them.
We don't have time, knowledge to sort out WHAT was damaged.
We make all straight from beginning:
1. MSM tools - make your phone like from the Factory with "clean" install (ver 9 for now)
2. "FlashAll" то ver 10E
3. If you need - install "global"
4. If you need - install TWRP and Magisk
5. Restore your backup from PC
At the end you will have "clean" phone with all programs working
EASY!!!
Same as OP, I wanted to flash twrp.img.
I had my OP7Pro stuck in 'fastboot mode', I thought. It wouldn't respond to any commands from console (device not found) and I couldn't turn it off with the power button any more.
For noobs, just like me, I learned that I just had to press the powerbutton + volume up button. My phone rebooted after this.
Now making a backup before rooting and such, phew.
vegatr0n
I was stuck in Fastboot after switching slots. Excelent stuf! 2,3 clicks , done! Thank you!
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Many people have found this problem. Thank you, I am working again.
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
nitinvaid said:
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
Click to expand...
Click to collapse
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
vegatr0n said:
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
Click to expand...
Click to collapse
Nope...
I was able to reboot holding both vol+ and - and power
I bricked my tmobile oneplus 7 pro and dont know which file is safe to try can anyone please point me in the right direction?
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
moonbosques said:
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
Click to expand...
Click to collapse
Sounds like you're having problems with Windows Defender. I also got the same error messages suddenly once week ago. I did sfc /scannow and all that but all files were intact. After rebooting the PC two times the problem was gone, really strange.
Skickat från min GM1913 via Tapatalk
Anyone here know what fastboot rom i can use to fix my bricked tmobile oneplus 7 pro?
Can you explain this strange effect, please
pitrus- said:
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
Click to expand...
Click to collapse
After an update to Android Q twrp an root was lost.
I was going the normal way like this:
1. In fastboot boot twrp.img
2. In twrp install twrp.zip
3. Reboot to twrp
4. In twrp install magisk.zip
After this the phone stuck a while on this orange splash screen and then reboot to bootloader.
Reboot --> the same effect
Then:
1. Boot into twrp
2. install twrp.zip
3. Reboot system
Everything ok, but no root
Just one method is working for me:
1. Download the full package of OOS 10.x.x
2. Extract the boot.img
3. Patch boot.img with Magisk
4. Flash on fastboot boot magisk_patched.img
5. reboot
My phone is rooted now but without twrp.
Why can twrp an Magisk not work together?
And why I can´t find any information for this problem on the internet?
Well, since TWRP lives in the boot partition on this phone, you will have to boot TWRP using fastboot boot TWRP. Then you flash the unofficial TWRP build 74 installer zip downloaded from the link below (the one from twrp.me only works on OOS 9 and not 10). Reboot phone back into Magisk to switch slot, flash Magisk installer zip which will then install Magisk to both boot slot a and boot slot b. Reboot phone and you should have both Magisk root and working TWRP.
https://r.tapatalk.com/shareLink/to...2&share_fid=3793&share_type=t&link_source=app
Skickat från min GM1913 via Tapatalk
Fails anyway
Bricked my OnePlus and now I'm left with bootloader (no os, no twrp). Everything leads back to bootloader. Any attempts to apply fastboot boot lead to "Load Error". Now I tried with that tool and ended up with this:
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odb_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
P.S. Full log:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e434a4c8
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: я╗┐require product=msmnile
Setting current slot to 'b' OKAY [ 0.002s]
extracting boot.img (96 MB) to disk... took 0.776s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.389s]
Writing 'boot_b' OKAY [ 0.406s]
extracting dtbo.img (16 MB) to disk... took 0.151s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.393s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.395s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
I am getting this error, any ideas what is going wrong? (please see attachment)
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
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
Hi All,
After several years (since 2006) of playing with flashing and rooting the hardware, the day has finally come (I still hope not ...) - I broke my smartphone.
Don't ask me why it happened - I think I was rocking in the clouds by turning off USB debugging while I was still getting my stuff back from backups... Maybe I clicked this option by accident. But one by one:
1. I have downgraded the LineageOS for microG 18.1 ROM to the April 11 version (the newer one had huge connectivity problems :[).
2. Everything worked fine again, unfortunately I have restored too many files (some system files) using my root backup and after rebooting I have bootloop.
The above would not be a problem, but:
* USB debugging is disabled (I don't know if there is a hack method on Pixel 5 to enable it from PC (I'm using Linux)). Flashing recovery seems unavailable (Writing 'recovery' FAILED (remote: 'No such file or directory')), the same with adb sideload commands.
* adb shell is unavailable (I tried to send a ROM image file to the device) due to lack of any trusted device on Pixel 5.
(db: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.)
adb kill-server/start-server and deleting my Linux adbkey doesn't work of course.
I can only add that I have root access and an unlocked bootloader, but I don't know if I can do anything on this basis.
Is there any magician on the forum who has an idea for my brick with bootlooping screen?
Maybe this can work for you? >> Deuces Flashing Script
It should work with any google factory image as stated in the post, don't download the wrong factory image tho.
Goodluck.
XDHx86 said:
Maybe this can work for you? >> Deuces Flashing Script
It should work with any google factory image as stated in the post, don't download the wrong factory image tho.
Goodluck.
Click to expand...
Click to collapse
Thank you very much! I have only recently been with Pixel and did not know about the existence of this script.
Interestingly, on my first try on Pixel 5 the script crashed, it requires fastbootd instead of the fastboot standard:
system
Sending 'system_b' (23660 KB) OKAY [ 0.700s]
Writing 'system_b' FAILED (remote: 'Partition should be flashed in fastbootd')
as a result, the system did not rise.
Quickly switched to recovery and then fastbootd on the second attempt was successful.
Michu_z said:
Thank you very much! I have only recently been with Pixel and did not know about the existence of this script.
Interestingly, on my first try on Pixel 5 the script crashed, it requires fastbootd instead of the fastboot standard:
system
Sending 'system_b' (23660 KB) OKAY [ 0.700s]
Writing 'system_b' FAILED (remote: 'Partition should be flashed in fastbootd')
as a result, the system did not rise.
Quickly switched to recovery and then fastbootd on the second attempt was successful.
Click to expand...
Click to collapse
No need for a magician then I guess, haha.
Glad it worked out mate, don't brick your phone again. I think pixel phones are one of the hardest to fix.