Database Info

Bootloop, only fastboot and EDL mode no system boot please help Axon 10 Pro

hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop:crying::crying::crying::crying:

the Axon 10 pro is back because he had no backup of all we had from my Axon 10 pro made a backup with the edl tool (Backup all) and have then copied his efs backup purely and then this with then on the Axon 10 flashed the Axon 10 pro is now back

Where did you get the twrp from?

From udev
On his donload page
https://forum.xda-developers.com/showpost.php?p=80156866&postcount=3

I had a bootloop issue as well and even though I reflashed using the EDL tool, it doesn't erase and the errors remained, but when I entered EDL mode and reflashed using the Xiaomi Flash Tool, storage was completely erased and the device was flashed cleanly and booted correctly.

I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success

jbeaulieu said:
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
Click to expand...
Click to collapse
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.

jim262 said:
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
Click to expand...
Click to collapse
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?

jbeaulieu said:
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
Click to expand...
Click to collapse
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.

jim262 said:
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
Click to expand...
Click to collapse
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?

jbeaulieu said:
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
Click to expand...
Click to collapse
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.

jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Ah, okay. I have the US version - A2020U. Unless I'm mistaken, it looks like there isn't a full EDL zip file available for my version yet, so I might be stuck

There were EDL files up, but apparently they were taken down for some reason.

in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431

Chris axon 7 said:
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Click to expand...
Click to collapse
Thanks for sharing these. @Unjustified Dev do you happen to know if the 1.6 2020G EDL would be able to be flashed to a 2020U model to recover from a brick? Or if not, is there a place to obtain the proper files, either here on the forums or via PM?

jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Please share us the EDL file for the Chinese version.

has anyone found the US EDL file yet?

Futility's Forgotten Soldier said:
has anyone found the US EDL file yet?
Click to expand...
Click to collapse
Still waiting. I'm stuck on the EU version.

OP6 stuck in FastBoot

I was trying to install OOS 10.3.2 but it didnt really work as expected so it did boot to the fastboot.
I can't boot in to the recovery because thats not working, OS either because I did wipe Data/System before I did flash OOS10.
I was trying in powershell ADB devices, it did find my OP6. But when I do : Fastboot boot twrp.img it says Failed to load/authenticate boot image: Load Error
Fastboot flash twrp doesnt work either.
Can someone help me out ?

Ghost123NL said:
I was trying to install OOS 10.3.2 but it didnt really work as expected so it did boot to the fastboot.
I can't boot in to the recovery because thats not working, OS either because I did wipe Data/System before I did flash OOS10.
I was trying in powershell ADB devices, it did find my OP6. But when I do : Fastboot boot twrp.img it says Failed to load/authenticate boot image: Load Error
Fastboot flash twrp doesnt work either.
Can someone help me out ?
Click to expand...
Click to collapse
If you search there is a version than can be flashed from fastboot / ADB.
Otherwise I'd look at wiping the device using the MSM tool and flashing back to 9.0 (only version that consistently works for me).

Amos91 said:
If you search there is a version than can be flashed from fastboot / ADB.
Otherwise I'd look at wiping the device using the MSM tool and flashing back to 9.0 (only version that consistently works for me).
Click to expand...
Click to collapse
Do you have a link or something I downloaded MSM tool but when I hit start it says "Waiting for devices"
Which twrp is it ?
I tryed twrp-3.2.1-0-enchilada.img

Ghost123NL said:
Do you have a link or something I downloaded MSM tool but when I hit start it says "Waiting for devices"
Which twrp is it ?
I tryed twrp-3.2.1-0-enchilada.img
Click to expand...
Click to collapse
With msm tool did you follow all the instructions? Windows 10 in test mode installing the Qualcomm drivers etc?

Amos91 said:
With msm tool did you follow all the instructions? Windows 10 in test mode installing the Qualcomm drivers etc?
Click to expand...
Click to collapse
Got it working by reinstalling the qualcomm drivers.
But the windows 10 test mode keeps failing however at the end the MSM did work.
Im gona unlock the bootloader in the next hour.
Let's see if fasboot twrp will work this time.

[PRELOADER][IMG][STOCK] PRELOADER Partition Binary for MERLIN (Xiaomi Redmi 10X 4G / Xiaomi Redmi Note 9)

Original Stock PRELOADER_MERLIN.BIN for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.8.0.QJOMIXM (FLASHING EDL only.)
- V12.0.7.0.QJOMIXM (FLASHING EDL only.)
- V12.0.6.0.QJOMIXM (FLASHING EDL only.)
- V12.0.5.0.QJOMIXM (FLASHING EDL only.)
- V12.0.4.0.QJOMIXM
- (China) V12.0.4.0.QJOCNXM
- V12.0.3.0.QJOMIXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
- V11.0.2.0.QJOMIXM
How to flash it?
Code:
fastboot flash preloader preloader_merlin.bin
MD5 hashes:
AL2522-Merlin-V039-Q-0513: bc7ebc0c2ca06b0d99856d595949e215
AL2522-Merlin-V044-Q-0920: d2c78e614adf75b98b2b6de74dfb4675
V12.5.1.0.RJOMIXM: 5db0756e0c2c0af508e5a823f204a6f1
V12.0.1.0.RJOMIXM: 1871c0dc6d8de2060175f8c90b133012
V12.0.8.0.QJOMIXM: d9a5ed36161265b61176178bebed8281
V12.0.7.0.QJOMIXM: 2124bb907077b745b8ada8d7108802f9
V12.0.6.0.QJOMIXM: 8c5d38f293d1609da6f79aa7d43b5c0b
V12.0.5.0.QJOMIXM: 27349a358cfd49f73ed3d31d423ca7fd
V12.0.4.0.QJOMIXM: 61ec78ae4a096c0b9f46cf814e5988c3
(China) V12.0.4.0.QJOCNXM: d06b365a15bc622327772586d3c54b18
V12.0.3.0.QJOMIXM: 9a14afee8301b12848ff8ec56c5aebbf
V11.0.5.0.QJOMIXM: 6fb0758e03bf1e43794f5a5273b627b8
V11.0.4.0.QJOMIXM: ea0e773af461a339b76907f94eff73c9
V11.0.2.0.QJOMIXM: d7d5c5b53817b4cc62accfe0eb0cabe3
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?

p233 said:
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
Click to expand...
Click to collapse
No.
It will works perfectly.
I've attached preloader of V12.0.4.0.QJOCNXM (China) too.
Enjoy

How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there

briangwapo81 said:
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
Click to expand...
Click to collapse
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

VD171 said:
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Click to expand...
Click to collapse
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.

p233 said:
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
Click to expand...
Click to collapse
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

VD171 said:
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Click to expand...
Click to collapse
I flash magisk using TWRP.

p233 said:
I flash magisk using TWRP.
Click to expand...
Click to collapse
Try patching boot.img using magisk manager.
And then, flashing the magisk patched boot.img to boot partition.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?

Gardlok said:
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Click to expand...
Click to collapse
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.

VD171 said:
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
Click to expand...
Click to collapse
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...

Gardlok said:
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Click to expand...
Click to collapse
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.

VD171 said:
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
Click to expand...
Click to collapse
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...

Gardlok said:
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Click to expand...
Click to collapse
May you attach the screenshot, please?

VD171 said:
May you attach the screenshot, please?
Click to expand...
Click to collapse
Ok. In the settings, I put UART, 921600.

Gardlok said:
Ok. In the settings, I put UART, 921600.
Click to expand...
Click to collapse
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?

VD171 said:
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
Click to expand...
Click to collapse
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...

Gardlok said:
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Click to expand...
Click to collapse
You just applied some change to the device, causing some brick.
SP Flash Tool is your best friend, certainly it can solve your problems.

Please help me, my phone comes with miui 12.5.X, I have unlocked the bootloader with "MediatekBootloaderUnlock" and I can use "MTK-bypas" to flash it using SP - TOOL, apparently the flashing is always successful, however the system won't boot , it only shows the android logo and I can't access the recovery menu, only fastboot. I tried with MIU 13, MIU 12.5.3 with the same results.
In the end I tried with MIU 12.0.1 (merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global):
1- Use EDL bypass and SPFLASH, it was successful, because fastboot now shows a different logo, but the system does not start and I cannot access the recovery menu either.
2- Use Mediatek Bootloader Unlock
3- Start fastboot and use: "fastboot flash preloader preloader_merlin--V12.0.1.0.RJOMIXM.bin" with apparent success.
4- I go back to SP-Flash and try to flash again MIU 12.0.1 (in theory it should no longer need EDL bypass), uncheck "preloader", I press download and connect my phone and it starts to turn itself on, if I press a key then I receive the authentication error.
If someone could give me a better guide on what to do, I would greatly appreciate it. I have tried formatting using SP-Flash and tried to flash by changing the preloader from "merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global" to "preloader_merlin--V12.0.1.0.RJOMIXM.bin", using "DA_VD171--3.3001 .2020-07-02020-07-14.bin" and "MT6768_Android_scatter--V12.0.1.0.RJOMIXM.txt" but I get the error, the screenshot is from this attempt.
Please help me

Question OnePlus 9 LE2110 256GB No OS No Recovery

As the title says, I have no OS and only have fastboot available.
I unlocked the bootloader and pushed TWRP 3.5.1_10-Nebrassy so that I could root with Magisk.
fastboot boot twrp.img
All went well to that point. Then I tried to flash TWRP.
fastboot flash recovery twrp.img
Then I had no OS. I tried to download the latest stock ROM, 11.2.9.9.LE25DA.
https://www.oneplus.in/support/softwareupgrade/details?code=PM1617074715494
I extracted the payload.bin and successfully flashed the files to fastboot.
https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Then I try to boot into fastbootd to install the other files.
fastboot reboot fastboot
Once in fastbootd, I have to choose a language from (I presume) Mandarin, Cantonese, and English. I choose English.
Then it says "fastbootd" across the top, but the cmd window is unresponsive, "< waiting for any device >"
I have to choose Advanced, or Exit.
I choose Advanced.
I have to choose "Reboot to fastboot," "Reboot to recovery," or "Ver 2.0"
I choose Reboot to fastboot because there is no recovery.
cmd is responsive, but I'm in fastboot, not fastbootd.
I try to flash the remaining files.
fastboot flash abl abl.img
I get the following message from the cmd window.
FAILED: <remote: 'Flashing is not allowed for Critical Partitions'>
fastboot error: error: Command failed
Obviously, because I'm not in fastbootd. Except I can't get a responsive cmd prompt in fastbootd.
I have also tried to flash TWRP again. It does not flash. I can push it over and it will boot up, but the touch screen is not responsive, so I have to hard reset to get back to fastboot.
fastboot boot twrp.img
So, at this point, all I have is fastboot and a bootloop.
Would someone please either direct me to a forum where this has been addressed (that I have obviously missed in my search), or please advise how to proceed? I would very much appreciate whatever guidance anyone can offer.

DoktorNo said:
As the title says, I have no OS and only have fastboot available.
I unlocked the bootloader and pushed TWRP 3.5.1_10-Nebrassy so that I could root with Magisk.
fastboot boot twrp.img
All went well to that point. Then I tried to flash TWRP.
fastboot flash recovery twrp.img
Then I had no OS. I tried to download the latest stock ROM, 11.2.9.9.LE25DA.
https://www.oneplus.in/support/softwareupgrade/details?code=PM1617074715494
I extracted the payload.bin and successfully flashed the files to fastboot.
https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Then I try to boot into fastbootd to install the other files.
fastboot reboot fastboot
Once in fastbootd, I have to choose a language from (I presume) Mandarin, Cantonese, and English. I choose English.
Then it says "fastbootd" across the top, but the cmd window is unresponsive, "< waiting for any device >"
I have to choose Advanced, or Exit.
I choose Advanced.
I have to choose "Reboot to fastboot," "Reboot to recovery," or "Ver 2.0"
I choose Reboot to fastboot because there is no recovery.
cmd is responsive, but I'm in fastboot, not fastbootd.
I try to flash the remaining files.
fastboot flash abl abl.img
I get the following message from the cmd window.
FAILED: <remote: 'Flashing is not allowed for Critical Partitions'>
fastboot error: error: Command failed
Obviously, because I'm not in fastbootd. Except I can't get a responsive cmd prompt in fastbootd.
I have also tried to flash TWRP again. It does not flash. I can push it over and it will boot up, but the touch screen is not responsive, so I have to hard reset to get back to fastboot.
fastboot boot twrp.img
So, at this point, all I have is fastboot and a bootloop.
Would someone please either direct me to a forum where this has been addressed (that I have obviously missed in my search), or please advise how to proceed? I would very much appreciate whatever guidance anyone can offer.
Click to expand...
Click to collapse
Try:
fastboot flashing unlock
then
fastboot flashing unlock_critical

Thank you for the reply.
The device is already unlocked, but I did as you suggested and tried both commands.
For both attempts I got the following message:
FAILED <remote : ' Device already : unlocked!'>
Fastboot: error: Command failed.

@DoktorNo you don't flash twrp that way anymore. You have to boot into twrp, then flash from inside twrp itelf.
So
fastboot boot twrp.img
Then once twrp starts up, go to the advanced tab, and flash the recovery.

mx597turbo said:
@DoktorNo you don't flash twrp that way anymore. You have to boot into twrp, then flash from inside twrp itelf.
So
fastboot boot twrp.img
Then once twrp starts up, go to the advanced tab, and flash the recovery.
Click to expand...
Click to collapse
Great suggestion, except when I boot into twrp, I cannot use the touch screen. So twrp will boot, but it is not responsive. Any thoughts on how to make that work? Then I'd be nearly set.

Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota

XxBigBuckxX said:
Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota
Click to expand...
Click to collapse
I haven't tried it. I'll give it a go when I'm home this evening and post my results.

DoktorNo said:
I haven't tried it. I'll give it a go when I'm home this evening and post my results.
Click to expand...
Click to collapse
Also, are you using the most updated version of twrp for the 9/9 pro? I'm sure you are, but just checking.

mx597turbo said:
Also, are you using the most updated version of twrp for the 9/9 pro? I'm sure you are, but just checking.
Click to expand...
Click to collapse
Great question and worth asking. I used twrp 3.5.1_lemonade-Nebrassy.
3.5.1-lemonadep-Nebrassy
Since there's no OS, there is no interface with the touchscreen, so I can't interact with it in that way. I can sideload twrp but then it's just an image on the screen.

There is a newer one TWRP-3.5.2-lemonadep-Nebrassy. If your unable to use twrp to flash or sideload MSM Tool is pretty simple. Use the original cable and put it EDL mode and run it.

DoktorNo said:
Great suggestion, except when I boot into twrp, I cannot use the touch screen. So twrp will boot, but it is not responsive. Any thoughts on how to make that work? Then I'd be nearly set.
Click to expand...
Click to collapse
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.

mx597turbo said:
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.
Click to expand...
Click to collapse
This works , mouse and keyboard

XxBigBuckxX said:
Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota
Click to expand...
Click to collapse
Msm will not download from the link you provided. GDrive scans the .exe and dll files before download and says there is a virus, so I am only able to download the other half of the files.

XxBigBuckxX said:
There is a newer one TWRP-3.5.2-lemonadep-Nebrassy. If your unable to use twrp to flash or sideload MSM Tool is pretty simple. Use the original cable and put it EDL mode and run it.
Click to expand...
Click to collapse
Got the new twrp. Still no touch screen.

mx597turbo said:
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.
Click to expand...
Click to collapse
I will have to buy an adapter.

Here , that was more of a guide. List of unbrick tools select your proper one from here. If you get errors try the One Plus 9 Pro IN version as that what worked with nothing else for a lot of people including me.

DoktorNo said:
Msm will not download from the link you provided. GDrive scans the .exe and dll files before download and says there is a virus, so I am only able to download the other half of the files.
Click to expand...
Click to collapse
Last thing you will need is the driver, here is the signed Microsoft version.
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
I Find it easier to have push start on msm tool at this point
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them. and it should connect and flash.

XxBigBuckxX said:
Here , that was more of a guide. List of unbrick tools select your proper one from here. If you get errors try the One Plus 9 Pro IN version as that what worked with nothing else for a lot of people including me.
Click to expand...
Click to collapse
Downloading now. I'll try this and report back. Thanks.

DoktorNo said:
Downloading now. I'll try this and report back. Thanks.
Click to expand...
Click to collapse
Okay and you might have to try it power cycle it a few times trying to get into edl mode especially if you do not already have working drivers. But windows update will pull working drivers as well if your not sure how to use a .cab file. There are guides everywhere even video if if you need. I've tested some weird things on the 7t pro McLaren and 9 pro and msm tool has always brought them back.

hj

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