the current image(boot/recovery) have been destroyed

[samjoandco]

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?

 

[BillGoss]

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?

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.

 

[samjoandco]

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.

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

 

[BillGoss]

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

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.

 

[samjoandco]

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.

 

[BillGoss]

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.

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?

 

[samjoandco]

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?

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

i still dont have 5G or mobile data with OO12. i want to flash the OOS12 again but dont see an option
----

 

[BillGoss]

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

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.

 

[samjoandco]

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.

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

 

[coebisho]

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...

 

[samjoandco]

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...

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.

 

[BillGoss]

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...

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

 

[magbrave]

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?

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 ..

 

[Rootk1t]

please help ....... i have no idea what to try ..

Did you try MSM tool?

 

[magbrave]

Did you try MSM tool?

yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting

 

[waseemv]

yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting

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

 

[LinhBT]

yeah..... but device cant be detected cause it boots into fastboot only .....nothing else . it keeps showing waiting

Boot to EDL using hard keys!

 

[Blazekitten]

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?

 

[BillGoss]

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

 

[Blazekitten]

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

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