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

[BillGoss]

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.

 

[cabagekiller]

I am trying to downgrade my firmware but I keep getting a param preload failed error. anyone run into this issue and found a resolution? thank you

 

[Achi Shukuteki]

I am trying to downgrade my firmware but I keep getting a param preload failed error. anyone run into this issue and found a resolution? thank you

You need the Qualcomm drivers.

 

[cabagekiller]

You need the Qualcomm drivers.

Yes. That was my first issue. I got that resolved. Just baby steps.

 

[BillGoss]

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.

 

[Rootk1t]

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?

 

[BillGoss]

Did you find a reason of this behaviour in the end?

Sadly, no. Every time I swapped out a partition I ended up in CrashDump.

 

[Achi Shukuteki]

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]

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]

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?

 

[maitpatni]

Links for the international firmware are dead, can someone please share.

 

[Tamiriz]

Links for the international firmware are dead, can someone please share.

following on this - same request.

 

[Tamiriz]

following on this - same request.

also no download link for the MSMdownloadtools

 

[Chiranz]

Help!

So ive used the MSM tool, and the tool has flashed it successfully too. it also shows download complete, but my phone is still not booting into recovery or fastboot.

 

[Chiranz]

Help!

So ive used the MSM tool, and the tool has flashed it successfully too. it also shows download complete, but my phone is still not booting into recovery or fastboot or the system.

 

[ewong3]

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]

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!

 

[BDProductions]

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

 

[Achi Shukuteki]

See if you can switch the DDR to 4. And try again.

Otherwise, see if you use the earliest firmware possible (if that's not the earliest one.)

 

[BillGoss]

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