Database Info

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.

bump

xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.

robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?

Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now

xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.

Can't fastboot boot TWRP

So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,

Ph0enix_216 said:
So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,
Click to expand...
Click to collapse
With MSM tool your oneplus 6 is locked again...Maybe you should look if bootloader is locked!

Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp

whizeguy said:
Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp
Click to expand...
Click to collapse
My bootloader is unlocked. Still can't get into TWRP.

Ph0enix_216 said:
My bootloader is unlocked. Still can't get into TWRP.
Click to expand...
Click to collapse
Did you enable debug?

Sounds like you may have the active slot set to an unbootable OS. Check the active slot with fastboot getvar all, then use this to change to the other slot.
fastboot --set_active=[a or b depending on which is inactive]

Was this the end of this? I'm in the same boat. I was recovering from a google account remove device wipe and so I went to restore my TWRP back-up and it succeeds so I reboot. Device is bricked into fastboot mode only. So I msm restore and boot system, enable debugging, unlock bootloader, still can't get into TWRP or versions that worked before, just that taunting blue light.. I found this and changed my active slot but the issue is the same and I'm kind of at a dead end, any help would be appreciated. I can boot into 5.1.5 OOS and stock recovery fine.

Nevermind I had to incrementally update the ROM

angelsenvy said:
Nevermind I had to incrementally update the ROM
Click to expand...
Click to collapse
You can download both twrp zip & img from here: https://drive.google.com/drive/folders/1bnGBrkL5XE3yt7DmIRSDD2v4J6MzFOsH?usp=sharing
fastboot flash boot twrp-3.4.0-1-enchilada-Q-mauronofrio.img instead of fastboot boot .
That will work

leagoo t5 wont boot after unlocking bootloader

Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks

pcfreeze said:
Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks
Click to expand...
Click to collapse
Have you tried factory resetting in recovery?

ktmom said:
Have you tried factory resetting in recovery?
Click to expand...
Click to collapse
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?

What your are describing is a bootloop. It sounds like the device can not find the system kernel to boot to. Did you boot the device after unlocking but before doing anything else?
Where did you get the TWRP recovery from?
Isn't this a mediatek chipset? If so, I think you need to use SP Flash Tool*to install.
I would look for a stock ROM for this device to revert to.
I'm not experienced on mediatek devices, but maybe @SubwayChamp could help.

pcfreeze said:
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?
Click to expand...
Click to collapse
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.

SubwayChamp said:
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.
Click to expand...
Click to collapse
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?

pcfreeze said:
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?
Click to expand...
Click to collapse
Ok, then to relock bootloader I guess that you did successfully boot to system again, right?
When you unlocked bootloader first then device is formatted to avoid a new user can access to the user´s data and when you relock it again the same happens.
As for DM-verity, newer devices strictly since nougat can´t boot to system after any partition was modified like happened when you flashed a custom recovery on it, here is when DM-verity can be useful, is used to avoid bootloader checks the integrity and allow a modified device can perform a reboot and more custom actions not officially permitted. You had to flash it through a custom recovery, sometimes flashing only Magisk is enough but not always.

You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.

ktmom said:
You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.
Click to expand...
Click to collapse
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!

@pcfreeze you quoted me, but as I said earlier, I'm not experienced with mediatek devices. You'd be better off quoting @SubwayChamp

pcfreeze said:
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!
Click to expand...
Click to collapse
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.

SubwayChamp said:
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.
Click to expand...
Click to collapse
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode

pcfreeze said:
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode
Click to expand...
Click to collapse
Sorry, just realised that this is the wrong app! nothing to do with cds in engineering mode! I triedhttps://apkcombo.com/common-data-service/com.mediatek.connectivity/
but got message that the file was corrupted and it would not install

the current image(boot/recovery) have been destroyed

I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip.
After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g network icon .
Istupidly tried to boot to twrp-3.6.1_11-0-kebab.img using fastboot in order to install the zip once more and thats when the things went south.
It intially was stuck in bootloader mode and after multiple retries it is now showing the following error message
"the current image(boot/recovery) have been destroyed"
Any advice to restore back to stock from here?

samjoandco said:
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip.
After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g network icon .
Istupidly tried to boot to twrp-3.6.1_11-0-kebab.img using fastboot in order to install the zip once more and thats when the things went south.
It intially was stuck in bootloader mode and after multiple retries it is now showing the following error message
"the current image(boot/recovery) have been destroyed"
Any advice to restore back to stock from here?
Click to expand...
Click to collapse
TWRP will not boot up on OOS 12. Worse, it sometimes switches slots in the process (trying to fall back to the previous slot).
So, if you can get to bootloader, try changing slots and booting system (NOT recovery).
If that doesn't work, MSM is your friend.

BillGoss said:
TWRP will not boot up on OOS 12. Worse, it sometimes switches slots in the process (trying to fall back to the previous slot).
So, if you can get to bootloader, try changing slots and booting system (NOT recovery).
If that doesn't work, MSM is your friend.
Click to expand...
Click to collapse
MSM has been failing for me with sahara communication failed. i have been able to extract boot.img from stock image of 12 beta using dumper and flash it and it is not stuck on bootloader or recovery anymore, i can even adb shell and see directories but its is not completely up. need a way to dirty flash the zip again for whihc i think i need to wait for TWP of OOS 12. or keep trying the MSM

samjoandco said:
MSM has been failing for me with sahara communication failed. i have been able to extract boot.img from stock image of 12 beta using dumper and flash it and it is not stuck on bootloader or recovery anymore, i can even adb shell and see directories but its is not completely up. need a way to dirty flash the zip again for whihc i think i need to wait for TWP of OOS 12. or keep trying the MSM
Click to expand...
Click to collapse
Glad to hear that.
You can't afford to wait for TWRP 12 - it could be a very long wait.
So you can actually boot OOS 12 beta? What do you mean by "it is not completely up"?
You could try to install the apk mentioned in the https://forums.oneplus.com/threads/oxygenos-12-open-beta-1-for-the-oneplus-8t.1548475/ and use it to try to flash the beta zip again.
Also, if you can get into bootloader, you can always try to flash the files you get from payload dumper using the process described in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/ - just make sure you include all the my_* partitions (they are all logical partitions) as well.
Note also the process hidden in the "Spoiler" button which is where the my_* partitions need to be included.

Bill thanks for the udpaye
after restoring the boot.img and wiping out data i was able to get up to new setup screen and accept OP agreement screen and it would then hang.
subsequently
i tried to flash all the imgs as per the instructions you shared above.
almost all of them failed with either of these errors
remote: 'Flashing is not allowed for Critical Partitions'
OR
'fastboot: error: Could not check if partition abl has slot all'
After a few images that i could flash to slot a and b now the phone can only be in bootloader or recovery mode cant go beyond that.

samjoandco said:
Bill thanks for the udpaye
after restoring the boot.img and wiping out data i was able to get up to new setup screen and accept OP agreement screen and it would then hang.
subsequently
i tried to flash all the imgs as per the instructions you shared above.
almost all of them failed with either of these errors
remote: 'Flashing is not allowed for Critical Partitions'
OR
'fastboot: error: Could not check if partition abl has slot all'
After a few images that i could flash to slot a and b now the phone can only be in bootloader or recovery mode cant go beyond that.
Click to expand...
Click to collapse
You only flash boot, recovery, and dtbo in bootloader mode. All the others must be flashed in fastbootd mode.
Given the errors you had I don't think you did that, right?

BillGoss said:
You only flash boot, recovery, and dtbo in bootloader mode. All the others must be flashed in fastbootd mode.
Given the errors you had I don't think you did that, right?
Click to expand...
Click to collapse
Bill Many thanks , you are a genius!
I missed the fastbootd part. After trying again, I was able to quickly flash everything except the LPDDR4X / LPDDR5 memory chip flash because i didnt know which memory was there.
it is now up and running fine.
I owe you a coffee , thanks again
one more thing i noticied after upgrade is that executing the following command to find the memory type does not return anything. its blank , neither 0 nor 1 . i am not sure what is wrong.
adb shell getprop ro.boot.ddr_type
Click to expand...
Click to collapse
i still dont have 5G or mobile data with OO12. i want to flash the OOS12 again but dont see an option
----

samjoandco said:
Bill Many thanks , you are a genius!
I missed the fastbootd part. After trying again, I was able to quickly flash everything except the LPDDR4X / LPDDR5 memory chip flash because i didnt know which memory was there.
it is now up and running fine.
I owe you a coffee , thanks again
Click to expand...
Click to collapse
If you run getprop | grep ddr you'll see the ddr type of your device: 0 is ddr4, 1 is ddr 5.
Remember this so that next time you know which xbl files to flash.

BillGoss said:
If you run getprop | grep ddr you'll see the ddr type of your device: 0 is ddr4, 1 is ddr 5.
Remember this so that next time you know which xbl files to flash.
Click to expand...
Click to collapse
that entry is missing in getprop. there is no entry for ddr is what i am saying.
===edit====
I rolled back to OOS 11 using the APK you shared earlier from oneplus and have everything working back now.
apparently getprop | grep ddr =0 so i have LPDDR4X ( this is a more common chip for OP8T anyway)
all good. it was a good roller coaster ride for a day
Bill Thanks again

I went through the same problem, I did the same processes (I flashed the entire rom through fastboot) but my phone now doesn't turn on any screen, black screen completely... I think it was because I flashed the xbl without knowing what my memory would be (4 or 5)
when I plug the cell phone into the pc, it infinitely connects and disconnects the Qualcomm HS-USB QDLoader 9008, without any other signal... any help, I'm desperate...

coebisho said:
I went through the same problem, I did the same processes (I flashed the entire rom through fastboot) but my phone now doesn't turn on any screen, black screen completely... I think it was because I flashed the xbl without knowing what my memory would be (4 or 5)
when I plug the cell phone into the pc, it infinitely connects and disconnects the Qualcomm HS-USB QDLoader 9008, without any other signal... any help, I'm desperate...
Click to expand...
Click to collapse
I am not sure but I read in a few places that flashing the wrong version will damage the phone.
What did you flash 4 or 5?
Which rom did you extract to imgs?
Was it the the same rom / version that you originally had?
Did you try reaching out to OnePlus support? You can try for repair.

coebisho said:
I went through the same problem, I did the same processes (I flashed the entire rom through fastboot) but my phone now doesn't turn on any screen, black screen completely... I think it was because I flashed the xbl without knowing what my memory would be (4 or 5)
when I plug the cell phone into the pc, it infinitely connects and disconnects the Qualcomm HS-USB QDLoader 9008, without any other signal... any help, I'm desperate...
Click to expand...
Click to collapse
You're probably in CrashDump mode but with no error displayed (I've been there also)
You should be able to get back to bootloader by:
- hold down Pwr+Vol Up until the phone buzzes
- immediately hold Pwr+Vol Down (or Pwr+Vol Up+Vol Down) and you should boot into bootloader
You can then flash the correct xbl* image files

samjoandco said:
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip.
After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g network icon .
Istupidly tried to boot to twrp-3.6.1_11-0-kebab.img using fastboot in order to install the zip once more and thats when the things went south.
It intially was stuck in bootloader mode and after multiple retries it is now showing the following error message
"the current image(boot/recovery) have been destroyed"
Any advice to restore back to stock from here?
Click to expand...
Click to collapse
same problem ....tried solution mentioned earlier but after first 3 commands same problem is there.... please help... tried erasing cache ...and recovery and tried flashing recovery again...but nothing is working
{Mod edit: Quotation fixed}
i am having the same problem "
the current image(boot/recovery) have been destroyed"
no solution has worked.
erase cache (​Erasing 'cache' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
same problem presists with other erase commands
booting into recovery says
Sending 'boot.img' (102400 KB) OKAY [ 2.343s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
please help ....... i have no idea what to try ..

magbrave said:
please help ....... i have no idea what to try ..
Click to expand...
Click to collapse
Did you try MSM tool?

Rootk1t said:
Did you try MSM tool?
Click to expand...
Click to collapse
yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting

magbrave said:
yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting
Click to expand...
Click to collapse
same issue here fastboot not not detecting my device after crashing recovery. i even downloaded and installed driver from android studio which worked earlier now its not. it keep shows waiting for device

magbrave said:
yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting
Click to expand...
Click to collapse
Boot to EDL using hard keys!

i have same issue. corruption of boot img recovery happens when i boot into recovery on latest c20 update on kb2005. does anyone elses phone get destroyed on c20 when booting into recovery?

Which recovery did you use when you tried to boot into recovery when on OOS 12?

BillGoss said:
Which recovery did you use when you tried to boot into recovery when on OOS 12?
Click to expand...
Click to collapse
was on normal recovery that flashes when upgrading to oos12, stock recovery worked on c16 but when on c21 when boot into stock recovery my phone gets boot img destroyed

Question No OS even after flashing stock

So I've been pulling hair for 2 days. I can flash everything fine recovery boots fastboot. But it consistently says no OS on either slots. Tried flashing stock to both went all the way through loading lineage and same thing. I'm at wits end. Also not a single password I put in decrypts data.

Also Metro/Tmob variant xt2131-1 bootloader unlocked.

Have you tied fastboot -w? It sounds like the partitions are messed up.

I have. I've done all of the above just still a persistent boot loop.

Fandroid Tech said:
Have you tied fastboot -w? It sounds like the partitions are messed up.
Click to expand...
Click to collapse
Currently retrying to flash stock firmware with a Motorola flashing program. Will let you know here in about 2 min.

Fandroid Tech said:
Have you tied fastboot -w? It sounds like the partitions are messed up.
Click to expand...
Click to collapse
Yep. Again boot loop. Says no OS. Stock recovery says last installation failed. Flashing the service flash package to see if that makes a difference. Hopefully because it says it reflashed my bootloader and stock recovery.

Spedwardo said:
Yep. Again boot loop. Says no OS. Stock recovery says last installation failed. Flashing the service flash package to see if that makes a difference. Hopefully because it says it reflashed my bootloader and stock recovery.
Click to expand...
Click to collapse
The motorola program formats the partitions before flash unlike an automated fastboot flash. The only issue I can see is a physical issue with the UFS/EMMC 5.1 chip, maybe even the ram(very unlikely). Had there been any warning signs such as the phone rebooting randomly or freezing? Motorola has a one year warranty for all devices.

No nothing of the sort. I did a factory reset because I was gonna try out lineage and this is where I'm at now. Still no OS. Even after flashing 3 times. I did have a remote access trojan that rewrote my partition data and resized one and added one and used the root hidden partition to store the data in while it was being transferred.

This drive folder has the system, system_ext, vandor and product of the xt2131-1 that can be flashed in twrp or orangefox. Make sure you make the partitions rw in twrp or OF using 100 rw zip (search for it) then mount as rw in terminal. Flash these images or image,whichever you believe to be needing. Then try and reboot. If all else fails then download the firmware from LMSA and use tinyfastboot tools to flash it. Always worked for me. Let me know how it goes. Heres the link to the files.
XT2131-1_Denver-Osaka_04-2022_RRE31.60-47-2-2 - Google Drive
drive.google.com
!!!!!Make Sure you have verity and verification disabled before trying to flash these. Hence the 100 rw zip is necessary. And must be flashed correctly. 73 error can be flashed with Ubuntu!!!!!!!!
**Edit**
Make sure you always
Fastboot -w then
Factory reset in recovery then format data for a full clean install. This vendor build is made for the boost mobile variant but it is universal. The firmware is incremental based as well so it knows which build to install or activate on the tmo/metro variant. I have all the apps and files for all carriers that have this model.

sosthenisRR said:
This drive folder has the system, system_ext, vandor and product of the xt2131-1 that can be flashed in twrp or orangefox. Make sure you make the partitions rw in twrp or OF using 100 rw zip (search for it) then mount as rw in terminal. Flash these images or image,whichever you believe to be needing. Then try and reboot. If all else fails then download the firmware from LMSA and use tinyfastboot tools to flash it. Always worked for me. Let me know how it goes. Heres the link to the files.
XT2131-1_Denver-Osaka_04-2022_RRE31.60-47-2-2 - Google Drive
drive.google.com
!!!!!Make Sure you have verity and verification disabled before trying to flash these. Hence the 100 rw zip is necessary. And must be flashed correctly. 73 error can be flashed with Ubuntu!!!!!!!!
**Edit**
Make sure you always
Fastboot -w then
Factory reset in recovery then format data for a full clean install. This vendor build is made for the boost mobile variant but it is universal. The firmware is incremental based as well so it knows which build to install or activate on the tmo/metro variant. I have all the apps and files for all carriers that have this model.
Click to expand...
Click to collapse
If this doesnt work you can try a blankfile flash via edl, if that does not work nothing will.

Fandroid Tech said:
The motorola program formats the partitions before flash unlike an automated fastboot flash. The only issue I can see is a physical issue with the UFS/EMMC 5.1 chip, maybe even the ram(very unlikely). Had there been any warning signs such as the phone rebooting randomly or freezing? Motorola has a one year warranty for all devices.
Click to expand...
Click to collapse
Not at home. Staying the night at my mom's. Get home early tomorrow and I will try the advised steps. I went through my previous flashing steps and am now just missing the persist partition. I'll report back as for the edl mode and I have 2 blank flash files just cannot get into edl mode. Have qfil rsd and motoflashpro

Spedwardo said:
just cannot get into edl mode.
Click to expand...
Click to collapse
What have you tried thus far? Have you tried fastboot commands to get into edl, I think it may also also a boot menu option in twrp but I don't remember. Also now that I think about, after flashing the firmware(to both lots as you say) have you tried fastboot set_active a (or) b? Also where did you find the firehose file for it, I could not find one on other forums?

So far im downloading the files and will try what you suggested now. I'll let you know in 30 min. But I've tried factory reset. Flash. Formatting then flashing. Blank flash. Formatting then flashing. I've also used fastboot --force -slot=all flash ***. *****. Etc. Tried flashing. Flashing the copy partitions and tried flashing a gsi an aosp. Got to lineages recovery but still the same issue. Some partition are unmountable. At this point now it refuses to charge while off.. and if I do plug it in while off it continues to boot loop from the battery/charging screen.

Spedwardo said:
At this point now it refuses to charge while off.. and if I do plug it in while off it continues to boot loop from the battery/charging screen.
Click to expand...
Click to collapse
Sorry to tell you this but the phone is definitely ****ed on a hardware level, no amount of reflashing the firmware will fix that. The partition issue is likely caused by the EMMC/UFS malfunctioning, however the charging issue is definitely not caused by software as the battery has a separate controller. Your best bet would be to replace the motherboard, your phone's warranty is however void anyways since you unlocked the bootloader so you would have to do it yourself.

Fandroid Tech said:
Sorry to tell you this but the phone is definitely ****ed on a hardware level, no amount of reflashing the firmware will fix that. The partition issue is likely caused by the EMMC/UFS malfunctioning, however the charging issue is definitely not caused by software as the battery has a separate controller. Your best bet would be to replace the motherboard, your phone's warranty is however void anyways since you unlocked the bootloader so you would have to do it yourself.
Click to expand...
Click to collapse
How do I disable anti-rollback???? Might be the issue with it not flashing vb* files. Assuming those control vendor persiste etc

Spedwardo said:
How do I disable anti-rollback???? Might be the issue with it not flashing vb* files. Assuming those control vendor persiste etc
Click to expand...
Click to collapse
You can't, the manufacture prevents you from doing so due to "security issues". Make sure you get the latest firmware at https://mirrors.lolinet.com/firmware/moto/denver/official/. This will restore all partitions including vendor and persist as it generates from the modem partition, also android 11 and up does not use regular persist partitions anymore, it is now in the "super" images so don't worry about it. When you extract the latest firmware from this site there will be an XML file, go to https://forum.xda-developers.com/t/...e-with-motorola-devices.4042039/post-82186933 and follow the instructions, before flashing made sure to select slot A, after you are done flashing slot A set it to slot B and flash again, then reboot regularly. To set the slot run the fastboot command before flashing, for example fastboot set_active a, flash firmware, fastboot set_active b, flash firmware, reboot.