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

Search This thread

thecapi

New member
Aug 22, 2022
2
0
My bad, kb2003 = KB05xx, then it seems it's dead. I took some water but since it still boot in fastboot I was thinking maybe it can be unbricked.

thx you for reply!
 

AxeKing

New member
Aug 29, 2022
2
0
unfortunately i don't know how. i followed the steps, i got the params preload failed message. tried installing qualcomm drivers and msm doesn't show a single device now. if anyone can help me fix my phone, i will pay 100€ via paypal

update: MSM shows the device again, but I get the param preload failed message. driver is installed.
i am facing the same issue msm doesnt showe anything can you help me ?
 

AxeKing

New member
Aug 29, 2022
2
0
hello guys i need some help i bricked my one plus 8t, the thing is i have installed drivers that were needed but the msm tool is not working it opens up but doesn't display coms, connection or anything just the normal screen with enum and start and other things please can anybody help me
 

Matthew69

New member
Jan 28, 2015
1
2
i am facing the same issue msm doesnt showe anything can you help me ?
Hey, I've got same issue and cannot installed drivers using the cab file. I solved it by plugging in device in EDL mode and going into windows settings - windows update and there was little link called optional updates. Under drivers there was something like qualcomm ports. I installed it and msm worked fine after that. I dont know if you need unnistall previous drivers for the update to appear (not sure at which point it appeared, I've experimented with differnt versions of the driver and only know it wasnt installed at that point).
 

mslezak

Senior Member
Dec 12, 2016
410
403
Houston
Google Pixel 2
OnePlus 8T
I bricked my OnePlus 8T Tmobile variant after installing an update to Android 12, setting up Magisk and Zygisk (?), SafetyNetFix (modded for GPay)... everything was working great until I tried rename Magisk and it went haywire. Then I didn't realize the TWRP backups on A12 are useless for Data, flashing them will brick your phone... Originally MSM'd to Tmobile A11 and realized how much I hate the carrier branded phone... then this worked no problem. If it doesn't work for you, ensure your Qualcomm 9008 driver is actually installed. Getting to EDL mode is a little tricky on a bricked phone. Sometimes the vol+ vol- works and other times it doesn't. Especially if your phone is rebooting constantly. Mine was showing some weird Chinese saying the boot or recovery partition was destroyed. Had to switch slots in Fastboot then boot TWRP, boot to EDL, finally worked. This doesn't pass Google Playstore verification in A11, but if you upgrade to A12, then it does, and everything works without Magisk or any of that complicated stuff. Root is gone too. I don't care at this point; I usually flash custom kernels, but I need my phone for business things so I'm okay with losing root and not having to setup Magisk / Zygisk / SafetyNetFix as I did earlier in the day. Everything works just fine now, just stock OS.
 
Last edited:

andonisu

Member
May 31, 2022
11
1
Hi, is there any newer version of MSM tool to install A12 automatically, or do I have to start in A11 and then update from there?
 

[email protected]

New member
Oct 11, 2022
2
0
boot image crash error for oneplus8t and I tried to unbrick following the process by downloading all the tools and when I connect the device it gives the below errors, please help.?
 

Attachments

  • usb.PNG
    usb.PNG
    8.9 KB · Views: 59
  • 12.PNG
    12.PNG
    16.7 KB · Views: 57
Last edited:

NewUsar

Member
Feb 7, 2015
20
1
Thank you for all involved here. Could get my phone back after a failed LOS update. Now I need to get back into how to get LOS on my phone. ;) Hopefully without having to come back here this week!
 

kairi033

Senior Member
Sep 3, 2012
60
3
can someone clarify if I can msm flash indian version to my kb2003 unit? I just want to test something thank you.
 

Kamigouki

Member
Dec 3, 2012
33
4
I converted my T-mobile version to EU with the modified MSM tool. Then I did local update using Global OTA file. Now, when I try to MSM using the global tool, it doesn't work. What do I need to do to use the global msm tool?
 

mlinca

New member
Dec 27, 2021
2
1
What solved it (Sahara communication failed, after 18s) for me finally was to check the -"Use Lite Firehose"- box in the MSM tool. After that the process was finally completed.

But after it was apparently successful, i couldn't boot into any mode(recovery, fastboot). I thought i finally buried it beyond any hope. I kissed it goodbye.

I just wanted to know if it makes any sound with the black screen when connected with usb, and to my surprise it made a connect sound and was recognized as Qualcomm HS-USB QDLoader 9008. So i tried the regular msmtool method without -"Use Lite Firehose"- box checked. And it spurred back into life. Crazy stuff...
 
  • Like
Reactions: BillGoss

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    What solved it (Sahara communication failed, after 18s) for me finally was to check the -"Use Lite Firehose"- box in the MSM tool. After that the process was finally completed.

    But after it was apparently successful, i couldn't boot into any mode(recovery, fastboot). I thought i finally buried it beyond any hope. I kissed it goodbye.

    I just wanted to know if it makes any sound with the black screen when connected with usb, and to my surprise it made a connect sound and was recognized as Qualcomm HS-USB QDLoader 9008. So i tried the regular msmtool method without -"Use Lite Firehose"- box checked. And it spurred back into life. Crazy stuff...
  • 49
    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
    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.