[GUIDE] Unbrick Tool for OnePlus 5 with OOS 9.0.9 & OOS 9.0.11 (Untouched full stock)

[djnim]

Is there any updated tool for 9.0.6?
Thank you

not yet. will update when available.

 

[RowBan]

Where is the download link for the tool.. Exactly?

 

[strongst]

Where is the download link for the tool.. Exactly?

Whitin the first post DOWNLOADS

 

[RowBan]

Whitin the first post DOWNLOADS

I found it eventually, I for some reason thought those were just roms. I just opened the tool and it started doing **** on it's own and my phone is now unbricked.. Guess I had all the drivers that was necessary or some such. Going to try OTA to 9.0.6 now, which is what I've been trying to do all day unsuccessfully.

 

[DarkDragon29]

Hi,
My phone was bricked during the OTA update. (didn't know it was even possible) . I tried the instructions in the OP and have reached the step until I get the phone to show up as QC 9008. However, when I run the tool nothing happens. Taskbar shows as Running: Upgrade, but nothing moves. Can anyone please let me know if I am missing something.

Thanks in advance.

 

[djnim]

Guyss.. quick update MSM TOOL with OOS 9.0.7 will be uploaded soon. Stay tuned.

 

[Pierre02]

Thank you!

 

[Ashish.akc]

Guyss.. quick update MSM TOOL with OOS 9.0.7 will be uploaded soon. Stay tuned.

MSM tool in 9.0.7 zip doesn't work. Stucks at Param Processing. You should change it in the zip IMO

If anyone else has the MSM tool exe file from 5.1.7 (or that works), could you please attatch it ASAP. Am sitting here with a bricked phone boy @poran123 @Some_Random_Username

 

[djnim]

I personally used MSM 9.0.7 and there was no issue.

 

[hadiyalkishan]

Deleted

 

[rodicaplotnic]

deleted

 

[djnim]

Tool Updated to 9.0.8. Enjoy

 

[Cafofo]

Hi all, I need some help trying to fix my bricked phone.

Yesterday I woke up with my phone dead when charging and I figured out that it was bricked reading the foruns.

My OP5 seems to be with drivers ok and communication on Device manager showing as " Qualcomm HS-USB QDLoader 9800(COMXXX) "

I tried more than one version of recovery and each one I got a diferent behavior/error and I'm listing its to you bellow (Tried on another computer as well):



cheeseburger_23_J.40_181105 -> Status of communication says : Memory Size: 119.187500G and time freezes on 20s

cheeseburger_23_J.51_190731 -> FileHoseReadData Failed, Errno: 258 and 8s time ( Param Preprocessing )

enchilada_22_O.09_180517 -> Firehose communication HandShake Failed ( 10s//16s time )



"best try" both versions cheeseburger_23_H.09_170703 and cheeseburger_23_O.13_170803 got the same result
-> only versions to show " Downloading cache.img " and starts download progress bar.
But it fails when time is 928s -- Communication status " FirehoseCheckRSP Failed, Errno: 258 "
Downloading cache.img Failed

I live in Brazil so sending to OnePlus to fix is not an option =( or I fix it myself or send it to trash.
Hope any hint ! Thx

 

[ScRuFFy7]

Try a different USB cable. I have found that some USB cables that work just fine for charging and transferring files don't work with the unbrick tool. Unfortunately, I can't offer any specifics or reasons why. Hopefully a different cable will fix your issue.

You may also want to try uninstalling the Qualcomm driver and reinstalling, it may be a driver issue.

Cheers and good luck! ?

 

[Cafofo]

Try a different USB cable. I have found that some USB cables that work just fine for charging and transferring files don't work with the unbrick tool. Unfortunately, I can't offer any specifics or reasons why. Hopefully a different cable will fix your issue.

You may also want to try uninstalling the Qualcomm driver and reinstalling, it may be a driver issue.

Cheers and good luck!

Tried already =(
4 different cables, different drivers with and withouse signature.... made no difference =(

 

[ScRuFFy7]

Tried already =(
4 different cables, different drivers with and withouse signature.... made no difference =(

Have you uninstalled the Qualcomm drivers and gone through trying each one systematically from the OP?

Also, have you rebooted? You probably have but sometimes a reboot is necessary, especially when using the different versions of the tool.

 

[Cafofo]

Try a different USB cable. I have found that some USB cables that work just fine for charging and transferring files don't work with the unbrick tool. Unfortunately, I can't offer any specifics or reasons why. Hopefully a different cable will fix your issue.

You may also want to try uninstalling the Qualcomm driver and reinstalling, it may be a driver issue.

Cheers and good luck!

Have you uninstalled the Qualcomm drivers and gone through trying each one systematically from the OP?

Also, have you rebooted? You probably have but sometimes a reboot is necessary, especially when using the different versions of the tool.

Positive for all your questions.

Only different thing that I'm doing is : When it says " Hold Volume UP for 10 seconds and then connect to pc... " if I do this nothing happens, never. I have to hold VolumeUP+Power for 10 seconds and then the Qualcomm driver appears as it should be.

 

[Cafofo]

Well, after 2 days trying i'm almost giving up. Tried lot of drivers but no good results. I Tried even in SMT mode and I got "provisioning UFS failed".

 

[vdbhb59]

Hi all, I need some help trying to fix my bricked phone.

Yesterday I woke up with my phone dead when charging and I figured out that it was bricked reading the foruns.

My OP5 seems to be with drivers ok and communication on Device manager showing as " Qualcomm HS-USB QDLoader 9800(COMXXX) "

I tried more than one version of recovery and each one I got a diferent behavior/error and I'm listing its to you bellow (Tried on another computer as well):

cheeseburger_23_J.40_181105 -> Status of communication says : Memory Size: 119.187500G and time freezes on 20s

cheeseburger_23_J.51_190731 -> FileHoseReadData Failed, Errno: 258 and 8s time ( Param Preprocessing )

enchilada_22_O.09_180517 -> Firehose communication HandShake Failed ( 10s//16s time )

"best try" both versions cheeseburger_23_H.09_170703 and cheeseburger_23_O.13_170803 got the same result
-> only versions to show " Downloading cache.img " and starts download progress bar.
But it fails when time is 928s -- Communication status " FirehoseCheckRSP Failed, Errno: 258 "
Downloading cache.img Failed

I live in Brazil so sending to OnePlus to fix is not an option =( or I fix it myself or send it to trash.
Hope any hint ! Thx

Try couple of things.
1. Charge your phone for an hour at least. Do not try to turn it on.
2. Once done, try going to bootloader (charger connected).
3. Once in bootloader, check if you are unlocked or locked. If locked, unlock. If unlocked, lock and unlock again. You ay reach a RED BOOT screen saying device is corrupted. Do NOT worry.
4. If you get RED BOOT text as above, then turn off the phone and wait for 3-4 minutes. Now retry to go to bootloader. Unlock, and reboot from bootloader via volume keys to recovery.

You should be able to get access.

N.B.: Once you unlock the bootloader (finally), then install recovery and try any OOS ROM from there.

This will take time, and moreover patience. So, do NOT fret or negate any thing, just try these. Should work. Also, do not try any MSM tool as now. Just install OOS via ADB if need be.

N.B1: For MSM to recognise, one has to press VolUp+Power button, while in EDL/Modem/Odin mode.
1.Shut down the OnePlus 5
2. Open up Device Manager from within Windows
3. Press and hold the Volume Up button for about 10 seconds
4. While holding the Volume Up button, connect the OnePlus 5 to the PC with a USB cable
5. Continue holding the Volume Up button for a few more seconds until a new device shows up in Device Manager

---------- Post added at 13:23 ---------- Previous post was at 13:18 ----------

And @Cafofo, if it still does not work, check with help center, and they will connect via remote and give you few files, which will restore the phone. However, you will lose any data in the phone (data anyways is gone as of now). That would be the last resort, as they will take 7 days time to revert to your call. Also, since you are in Brasil, they may say NO for remote, so persist on getting the remote. Just ensure you allow access only to the file system you need, or rather they need, as they will take remote via TeamViewer, and that shucky thing grants access to all file system by default. That is one reason, why last resort.

 

[Cafofo]

Try couple of things.
1. Charge your phone for an hour at least. Do not try to turn it on.
2. Once done, try going to bootloader (charger connected).
3. Once in bootloader, check if you are unlocked or locked. If locked, unlock. If unlocked, lock and unlock again. You ay reach a RED BOOT screen saying device is corrupted. Do NOT worry.
4. If you get RED BOOT text as above, then turn off the phone and wait for 3-4 minutes. Now retry to go to bootloader. Unlock, and reboot from bootloader via volume keys to recovery.

You should be able to get access.

N.B.: Once you unlock the bootloader (finally), then install recovery and try any OOS ROM from there.

This will take time, and moreover patience. So, do NOT fret or negate any thing, just try these. Should work. Also, do not try any MSM tool as now. Just install OOS via ADB if need be.

N.B1: For MSM to recognise, one has to press VolUp+Power button, while in EDL/Modem/Odin mode.
1.Shut down the OnePlus 5
2. Open up Device Manager from within Windows
3. Press and hold the Volume Up button for about 10 seconds
4. While holding the Volume Up button, connect the OnePlus 5 to the PC with a USB cable
5. Continue holding the Volume Up button for a few more seconds until a new device shows up in Device Manager

---------- Post added at 13:23 ---------- Previous post was at 13:18 ----------

And @Cafofo, if it still does not work, check with help center, and they will connect via remote and give you few files, which will restore the phone. However, you will lose any data in the phone (data anyways is gone as of now). That would be the last resort, as they will take 7 days time to revert to your call. Also, since you are in Brasil, they may say NO for remote, so persist on getting the remote. Just ensure you allow access only to the file system you need, or rather they need, as they will take remote via TeamViewer, and that shucky thing grants access to all file system by default. That is one reason, why last resort.

Thanks for your answer vdbhb59.

1st : I Tried first method but I cannot. My screen is full black I dont get even any signal from lights on top left corner.

That's why I went to method using MSM. I can find the device on MSM but I got the problems as I mentioned above.

I'll try to contact OP support chat. I dont have much hope they will help but I`ll give a try !