[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS

Search This thread

BillGoss

Senior Member
Sep 2, 2010
5,292
4,654
Sydney
OnePlus 8T
This was working, however, when you press start in MSM, connect the phone after, THEN press and hold both vol buttons and power, let go of power after a few secs, but don't let go the vol buttons until you see in MSM it started to download.

I just held the two vol buttons and connected like that, but nothing happened that way.
You need to hold down Vol up+Vol down before connecting the phone to the PC. After that you can release them.
 
  • Like
Reactions: azoller1

BillGoss

Senior Member
Sep 2, 2010
5,292
4,654
Sydney
OnePlus 8T
Tl, dr:
  • Getting Firehose communication handshake failed is not the end of the world
  • I've always (to date) been able to use the MSM Tool to get me out of a mess where I couldn't use TWRP or bootloader to fix things
  • I've never needed to reinstall the Qualcomm driver
  • The MSM Tool can take numerous attempts to get it working (depending on the state the phone is in)
  • I'm sooo glad we have the MSM Tool

The long story
I've used the MSM Tool lots of times after screwing things up flashing roms or rooting the phone. And I've always followed the OP instructions and they've worked flawlessly.

But then I started testing out the OOS 12 Open Beta 1 (OB1). To my dismay I discovered that I could not boot into recovery with TWRP installed.
To be more precise, if OB1 is installed on the active slot, OOS 11 was installed on the inactive slot, and TWRP is installed on both slots, then booting recovery from OB1 boots TWRP on the inactive slot! And changing slots in TWRP and rebooting recovery will return to the inactive slot.

So I started to see what might be causing this. Clearing out the OB1 boot, DTBO, or super partitions message no difference. So this issue was clearly not related to the weird changes made in OB1 to the system partitions.
I then decided to systematically go through the other partitions and one-by-one replace them with the OOS 11 equivalent, booting recovery on the OB1 slot after each change.

But doing this left me either in CrashDump mode with its splash screen but no error message or, worse still, on a black screen that I assume was CrashDump because it responded to Pwr + Vol Up just like CrashDump does. And I was, at this point, unable to power off the phone or boot into bootloader.

But when I then connected the phone to the MSM Tool it would connect but then stop with Firehose communication handshake failed.

I googled this but didn't come across anything that I found at all helpful. The closest I saw that was worth trying was https://forum.xda-developers.com/t...-hard-bricked-oneplus-3.3405700/post-72135723 where it suggested holding Pwr + Vol up whilst connected to MSM Tool.

I tried that and lots of other permutations but nothing seemed to help. And then, all of a sudden the MSM Tool worked as normal and successfully restored my phone. And this happened after giving up and shutting down the tool but then deciding to give it one more go.

Unfortunately I can't provide a definite process to get around the "Firehose" error other than to try repeatedly and to try restarting the MSM Tool.
But the good news is that you can get past the "Firehose" error using the MSM Tool.

A few other things that I learnt in the process (yes, I ended up in this mess a number of times!) are:
  • Pressing Start in the MSM Tool before you connect the phone to the PC let's you take as long as you need to connect. MSM will stay waiting indefinitely.
  • You can simply connect the phone to the PC whilst it's still in CrashDump mode and then press Pwr + Vol Up until the phone buzzes and then hold Vol Up + Vol Dn and MSM will then connect.
 
  • Like
Reactions: Achi Shukuteki

Rootk1t

Senior Member
Jun 2, 2013
1,695
724
So I started to see what might be causing this. Clearing out the OB1 boot, DTBO, or super partitions message no difference. So this issue was clearly not related to the weird changes made in OB1 to the system partitions.
I then decided to systematically go through the other partitions and one-by-one replace them with the OOS 11 equivalent, booting recovery on the OB1 slot after each change.
Did you find a reason of this behaviour in the end?
 

Achi Shukuteki

Senior Member
Jan 17, 2017
97
29
OnePlus 8T
I can't, for the life of me, get the MSM tool to operate properly. Sahara errors, DDR errors, etc. Trying different firmwares. I'm doing everything by the book. Drivers are installed. So I'm at a loss right now.
 

D Miller

Senior Member
Mar 15, 2018
50
9
Google Pixel 5
Having just purchased a brand new 8t, I want to clarify, are international devices (KB2005) also effected if manufactured after March 9th 2021, or is it just the variant for china (KB2000)? Will I need to figure out how to get a newer MSM tool for OxygenOS or can i use the ones in the OP?
 

D Miller

Senior Member
Mar 15, 2018
50
9
Google Pixel 5
Having just purchased a brand new 8t, I want to clarify, are international devices (KB2005) also effected if manufactured after March 9th 2021, or is it just the variant for china (KB2000)? Will I need to figure out how to get a newer MSM tool for OxygenOS or can i use the ones in the OP?
Update to this, I finally recevied it and it booted up to 11.0.7.10. do i need to find the msm tool for 11.0.7.10 or should the old ones work?
 

ewong3

Senior Member
May 28, 2015
201
38
just a tip for those who run into similar issues:
1) on latest win11 with usb3 (not sure which!) the qualcomm driver shows with exclamation mark in device driver - so will not recognise the phone;
2) once moved to flash on older laptop on win10 on usb2 port, all worked fine

the above was despite the driver seemingly installing fine, and the download page somewhere said that this worked on win11...
 

ewong3

Senior Member
May 28, 2015
201
38
weird experience - oem unlock greyed out in dev options

after various tries to get it going, it turned out that the phone was set up without any wifi/phone connections, through random luck, i turned on wifi and suddenly the oem unlock switch was activated, if anyone had this error while executing 'fastboot oem unlock'
FAILED (remote: 'Flashing Unlock is not allowed')

turning on internet might cure it... but why, god knows!
 
When I get MSM to see the phone it fails after unable to detect DDR...

OnePlus cable that came with phone, and works fine to flash ROMs.

Hit a snag with DerpFest, and decided MSM back to OOS 11 would be a good starting point... no luck.

See image.

How is this resolved? Windows 10 Pro, 64 bit version, plenty of resources and no other issues including ADB and FASTBOOT work as expected.


Any help would be appreciated
 

Attachments

  • MSM-fails.jpg
    MSM-fails.jpg
    186.6 KB · Views: 41

BillGoss

Senior Member
Sep 2, 2010
5,292
4,654
Sydney
OnePlus 8T
When I get MSM to see the phone it fails after unable to detect DDR...

OnePlus cable that came with phone, and works fine to flash ROMs.

Hit a snag with DerpFest, and decided MSM back to OOS 11 would be a good starting point... no luck.

See image.

How is this resolved? Windows 10 Pro, 64 bit version, plenty of resources and no other issues including ADB and FASTBOOT work as expected.


Any help would be appreciated
See if this helps https://forum.xda-developers.com/t/...your-device-to-oxygenos.4180837/post-85053037
 
  • Like
Reactions: Achi Shukuteki

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    i am facing A problem with 8T ...
    On MSMDownloadtool i m having this msg " Automatic detection of DDR Failed "

    i tried to flash a stockrom then stuck into bootloop ( fastboot & recovery both working )... To solve this i tried to flash another rom in my device and stuck into hard brick mode .After this fastboot & recovery mode nothing is working . Only thing i am getting is in device manager on pc i see on port connection Qualcomm HS-USB QDLoader 9008 (COM6) . that means Only EDL is working
    Try this: https://forum.xda-developers.com/t/msm-tool-unroot-stuck-on-waiting-for-device.4448835/post-86932521
    1
    thanks for your suggestion ... it didnt work for me ...
    bt i have found a solution of my problem by trying various of roms and MSMDownloadtools .
    only thing that worked for me is Tmobile Rom and MSMdownload tool for tmobile ...
    i dont know bt it unbricked my hardbricked phone ....
  • 45
    Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.

    Hi everyone, similar to the previous threads for
    OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, OP8Pro and OP Nord here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 8T.

    You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware :)

    You can download the following versions:

    KB05AA tools (international firmware):
    ANDROID 11:


    KB05BA tools (european firmware):
    ANDROID 11:


    KB05DA tools (indian firmware):
    ANDROID 11:


    Tips:

    While crossflashing does not seem to break your /persist unlike on 8-series, it is advised that you back it up before attemting to do so as fingerprint reader may give an error related to enrollment issue. You can do so by using dd if=/mnt/vendor/persist of=/sdcard/persist.img (you must have root access, which is not something I'm going to explain here) and moving it to your computer/cloud.

    Instructions:

    Launch MsmDownloadTool V4.0.exe.
    Windows 7 users may use MsmDownloadTool V4.0_Win7.exe instead, but it hasn't been tested.


    On the login prompt select "Other" in the dropdown menu and click on Next.
    Wait a few seconds until main window shows up.
    Click on Target button and select O2 while using global tool or India while using indian tool or EU when using european tool.
    Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds)

    Power your device off.
    Let it cool down for one minute.
    Hold both volumes in to get in Qualcomm EDL mode and the screen will stay black. While holding, plug in the USB cable from your phone to your computer. Let volumes go alter plugged in.
    Wait some time (should not be longer than ~300 seconds).
    Enjoy your brand new device.

    FAQ:

    Does this work on Mac or on Linux?

    Unfortunately no, tool is Windows only. You should need at least Windows 7.

    Why is my antivirus freaking out when unzipping the archive or running the tool?

    In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.

    My device isn't detected when I click on "Enum" button

    Go to device manager and make sure your phone shows up as QDLOADER 9008.
    If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.

    MSM tool is stuck on "Param pre-processing"

    Ensure you're using the Qualcomm drivers linked above.

    MSM tool is stuck on "Sahara communication failed"

    Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.

    What is SMT Download mode?

    Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.

    How can I fix "SMT config not found" error?

    Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61, all credits to @Shadow12347 for finding it out.

    Why is my device getting in Qualcomm crashdump mode in spite of a successful download?

    Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.

    Credits:

    @viperbjk for KB05AA and KB05BA OOS 11.0 files
    @LLStarks for KB05AA OOS 11.0.1.2 file
    @FullOfHell for testing 11.0 KB05AA tool and downgrade possibility
    Votton for providing a server as an alternative mirror
    OnePlus for the device and OS
    9
    Finally, I just got the MSM Tool mentioned in that post and was able to get my phone back to H2OS!

    Here is the link for those who don't have a OnePlus account or Baidu account:
    (Note that this is for H2OS 11.0.7.12.KB05, not OxygenOS.)

    Hope this helps someone out there.

    I have also noticed few tips when using MSM Tools:
    - If you get a "packed image not exist" error, make sure that your downloaded path does not contain multi-byte characters
    - If downloading image to the phone fails in progress, you can try again by checking the "Use Firehose Lite" option (to use little slower and safer protocol)
    9
    Seeing "Automatic detection of DDR failed" and "Waiting for device" in a red font. Anything I should do? I believe I have the correct drivers installed as it's listed as Qualcomm HS-USB QLOADER 9008 (COM3) in device manager.

    ---------- Post added at 06:51 AM ---------- Previous post was at 06:34 AM ----------



    Did you end up finding a solution for the "Automatic Detection of DDR failed" issue?

    ---------- Post added at 06:54 AM ---------- Previous post was at 06:51 AM ----------



    Sorry to spam, did you find a solution?

    Nevermind! I think I fixed it but I'm not sure just yet.

    I had the same issue " automatic detection of ddr failed"

    I was not able to get into fastboot or recovery and the OS was constantly in a bootloop

    I was able to get the device working using the following steps:

    1. Boot the device (let it bootloop)
    2. Ensure the device shows up properly in Device manager. (might need to disable driver enforcement in win10 )
    3. Start the MSM tool and start and let it wait for device
    4. Connect the device using the Oneplus cable
    5. It should show as connected now.
    6. Boot to edl mode using Power button + Vol up +Vol down(with cable connected)
    7. Now the MSM tool should take care of the rest

    Took me literally 10 hours to get this right. Hope this helps someone.

    Cheers.
    6
    Added OOS 11.0.5.6 MSMs for all regions.
    4
    Finally, I just got the MSM Tool mentioned in that post and was able to get my phone back to H2OS!

    Here is the link for those who don't have a OnePlus account or Baidu account:
    (Note that this is for H2OS 11.0.7.12.KB05, not OxygenOS.)

    Hope this helps someone out there.

    I have also noticed few tips when using MSM Tools:
    - If you get a "packed image not exist" error, make sure that your downloaded path does not contain multi-byte characters
    - If downloading image to the phone fails in progress, you can try again by checking the "Use Firehose Lite" option (to use little slower and safer protocol)
    For those who had problem with oneplus 8t released after March 2021,this new version of MSM Tools will fix it can goes back to HydogenOS stock.After that if you prefer oxygen OS just download a update zip and update from there.