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

[Ashish.akc]

All the links are working well

No. Am not able to download the msm tool from the link given. There just so many "Download" buttons and clicking each one of them takes to a different ad site. The page itself fills the whole screen with ads :good:

I guess it's because of people like you, that we users are forced to use ad-blockers. Shame one you. It's good that XDA is dying slowly, as people like you will always give a bad experience to the users. Happy money making from that ad infested site

 

[Moonheart]

Hi guys,

I went through the whole process and finished it successfully and it shows "Download Completed" but then nothing happens and when I try to boot it up, it shows the One+ logo with "Powered by Android" screen and then it goes all dead again. What could be the issue here?

 

[ScRuFFy7]

Hi guys,

I went through the whole process and finished it successfully and it shows "Download Completed" but then nothing happens and when I try to boot it up, it shows the One+ logo with "Powered by Android" screen and then it goes all dead again. What could be the issue here?

All I can suggest is try a different firmware.

Otherwise need more information:
- Why do you need the hard-brick recovery? What happened?
- Do you have a OP5 or OP5T? If you have a OP5T you're on the wrong thread.
- What version of recovery are you trying?
- The recovery will not help in the event of hardware failure.

Good luck! ?

 

[Moonheart]

All I can suggest is try a different firmware.

Otherwise need more information:
- Why do you need the hard-brick recovery? What happened?
- Do you have a OP5 or OP5T? If you have a OP5T you're on the wrong thread.
- What version of recovery are you trying?
- The recovery will not help in the event of hardware failure.

Good luck! ?

Thanks for the reply!

- So I never really experimented with this phone (all stock no root - i never tinkered with it) and it ran flawlessly for 3 years. A few days ago, while I was reloading a page on chrome, it hung up and after a while, just shut down. No response whatsoever then, it just went into fastboot mode and showed the Qualcom 9008 driver when I plugged it into PC. So I thought it was hard bricked and used the MSM tool

- OP5

- Do I have to flash recovery separately - if it says 'Download Complete' on the MSM tool, isn't that enough?

- I hope its not that

 

[ScRuFFy7]

Thanks for the reply!

- So I never really experimented with this phone (all stock no root - i never tinkered with it) and it ran flawlessly for 3 years. A few days ago, while I was reloading a page on chrome, it hung up and after a while, just shut down. No response whatsoever then, it just went into fastboot mode and showed the Qualcom 9008 driver when I plugged it into PC. So I thought it was hard bricked and used the MSM tool

- OP5

- Do I have to flash recovery separately - if it says 'Download Complete' on the MSM tool, isn't that enough?

- I hope its not that

If it completed successfully that's a good sign at least. Your phone should reboot automatically once completed. Please note, first boot takes longer than normal.

My best suggestion is to try different versions of the hard-brick recovery tool. I find some work better than others for me at least. I'd try 9.0.11 (which it sounds like you already have), 9.0.9, and whatever the last Oreo version was.

Have you tried going into the phone's recovery to factory reset and wipe cache? Sometimes that could help.

 

[Moonheart]

If it completed successfully that's a good sign at least. Your phone should reboot automatically once completed. Please note, first boot takes longer than normal.

My best suggestion is to try different versions of the hard-brick recovery tool. I find some work better than others for me at least. I'd try 9.0.11 (which it sounds like you already have), 9.0.9, and whatever the last Oreo version was.

Have you tried going into the phone's recovery to factory reset and wipe cache? Sometimes that could help.

I have tried 9.0.11 and I think 9.0.9 too. I'll check with Oreo again. Ok so after using the MSM tool, I'll have the stock recovery on it automatically right? And i'll just need to get to it by pwr + vlm down?

 

[ScRuFFy7]

I have tried 9.0.11 and I think 9.0.9 too. I'll check with Oreo again. Ok so after using the MSM tool, I'll have the stock recovery on it automatically right? And i'll just need to get to it by pwr + vlm down?

Maybe? I forget offhand. I usually do volume up and power for the fastboot menu and select recovery from there. If you can get into the phone's recovery that's another good sign.

Have you tried a different USB cable? I know it seems odd but sometimes that helps.

Feel free to PM me if you'd like.

 

[Moonheart]

Maybe? I forget offhand. I usually do volume up and power for the fastboot menu and select recovery from there. If you can get into the phone's recovery that's another good sign.

Have you tried a different USB cable? I know it seems odd but sometimes that helps.

Feel free to PM me if you'd like.

Ok cool, have PMed you!

 

[gitanshu]

Thanks for the reply!

- So I never really experimented with this phone (all stock no root - i never tinkered with it) and it ran flawlessly for 3 years. A few days ago, while I was reloading a page on chrome, it hung up and after a while, just shut down. No response whatsoever then, it just went into fastboot mode and showed the Qualcom 9008 driver when I plugged it into PC. So I thought it was hard bricked and used the MSM tool

- OP5

- Do I have to flash recovery separately - if it says 'Download Complete' on the MSM tool, isn't that enough?

- I hope its not that

Hey, I am in the exact same situation as you. Did you find a solution?

Phone suddenly went off when I opened Google Pay (US version), then it wouldn't do anything. Fastboot and recovery still opened, but no booting. It was fully stock, not even bootloader unlocked. So when factory reset and wiping everything didn't work, I tried this tool. It manages to complete the whole thing, shows download complete, auto reboots, shows one plus logo and then nothing for a few seconds, and then the LED turns light blue. I don't know what to do anymore.

I've also been trying to figure out how to use this tool: https://github.com/bkerler/edl but I don't know what they mean by an edl loader file that I am supposed to find by myself.

 

[vdbhb59]

Hey, I am in the exact same situation as you. Did you find a solution?

Phone suddenly went off when I opened Google Pay (US version), then it wouldn't do anything. Fastboot and recovery still opened, but no booting. It was fully stock, not even bootloader unlocked. So when factory reset and wiping everything didn't work, I tried this tool. It manages to complete the whole thing, shows download complete, auto reboots, shows one plus logo and then nothing for a few seconds, and then the LED turns light blue. I don't know what to do anymore.

I've also been trying to figure out how to use this tool: https://github.com/bkerler/edl but I don't know what they mean by an edl loader file that I am supposed to find by myself.

After all this, just install TWRP, do either a fastboot data format or normal data format. Reboot to recovery/fastboot. Do the format again, and reboot. Should load to system.

 

[gitanshu]

After all this, just install TWRP, do either a fastboot data format or normal data format. Reboot to recovery/fastboot. Do the format again, and reboot. Should load to system.

My bootloader is locked though, and I can't unlock it. It says "Flashing Unlock is not allowed". Is there any way to unlock it or install twrp in my situation?

 

[ScRuFFy7]

My bootloader is locked though, and I can't unlock it. It says "Flashing Unlock is not allowed". Is there any way to unlock it or install twrp in my situation?

You have to enable unlocking in developer options before you can unlock the bootloader and begin flashing.

Edit: Ok, I should have read back a little further first... You need to get OOS to boot. Have you tried wiping cache and factory reset in stock recovery? If it still doesn't boot try a different version of OOS. Good luck! ?

Cheers! ?

 

[vdbhb59]

My bootloader is locked though, and I can't unlock it. It says "Flashing Unlock is not allowed". Is there any way to unlock it or install twrp in my situation?

Please flash an earlier version (Android 9 last or Android 10.0.Hotfix) and you will boot up. Then you can do the rest of the stuff.

 

[gitanshu]

You have to enable unlocking in developer options before you can unlock the bootloader and begin flashing.

Edit: Ok, I should have read back a little further first... You need to get OOS to boot. Have you tried wiping cache and factory reset in stock recovery? If it still doesn't boot try a different version of OOS. Good luck!

Cheers!

I tried that but it didn't help.

Please flash an earlier version (Android 9 last or Android 10.0.Hotfix) and you will boot up. Then you can do the rest of the stuff.

I tried flashing Oxygen OS 10 using adb sideload in recovery. It failed at 92% - "can't read from device: no error" and now it won't go to recovery anymore. I tried flashing through the msm download tool again, it completes but still can't get into recovery

 

[ScRuFFy7]

I tried that but it didn't help.



I tried flashing Oxygen OS 10 using adb sideload in recovery. It failed at 92% - "can't read from device: no error" and now it won't go to recovery anymore. I tried flashing through the msm download tool again, it completes but still can't get into recovery

All I can suggest is trying a different hard-brick recovery version. There's a large assortment here:
https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870/
Unfortunately, if the hard-brick recovery tool is not working it may be an indication of an actual hardware failure. Hopefully not. If you have to go back as far as nougat to get back up and running, do it.

Cheers! ?

 

[gitanshu]

All I can suggest is trying a different hard-brick recovery version. There's a large assortment here:
https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870/
Unfortunately, if the hard-brick recovery tool is not working it may be an indication of an actual hardware failure. Hopefully not. If you have to go back as far as nougat to get back up and running, do it.

Cheers!

There's won't be a problem related to treble if i go back to nougat, right? In that case, i'll try that

 

[ScRuFFy7]

There's won't be a problem related to treble if i go back to nougat, right? In that case, i'll try that

One problem at a time... You need to get your device to a functioning state. Going back to Nougat would mean no more treble (temporarily), but once you're up and running you should be able to upgrade.

 

[gitanshu]

One problem at a time... You need to get your device to a functioning state. Going back to Nougat would mean no more treble (temporarily), but once you're up and running you should be able to upgrade.

Okay. I have tried multiple versions now (8.1.x, 9.0.x, 10.0.x), couldn't try nougat because decrypted versions are not available here
The common theme is that I first flash it using the Msm tool, then factory reset using recovery, then it starts booting but freezes on the boot animation and then reboots, this happens twice, and third time it's a blank screen and a light blue LED.
Also when it freezes, whatever graphic is on the screen gets distorted.

Does this mean it's a hardware issue?

 

[ScRuFFy7]

Okay. I have tried multiple versions now (8.1.x, 9.0.x, 10.0.x), couldn't try nougat because decrypted versions are not available here
The common theme is that I first flash it using the Msm tool, then factory reset using recovery, then it starts booting but freezes on the boot animation and then reboots, this happens twice, and third time it's a blank screen and a light blue LED.
Also when it freezes, whatever graphic is on the screen gets distorted.

Does this mean it's a hardware issue?

Possibly. Definitely, not normal operating behaviour.

If available, you could try taking it to a repair shop. Unfortunately due to the age of the phone it may not be worth it to repair.

Sorry, I'm out of suggestions.

 

[gitanshu]

Possibly. Definitely, not normal operating behaviour.

If available, you could try taking it to a repair shop. Unfortunately due to the age of the phone it may not be worth it to repair.

Sorry, I'm out of suggestions.

Okay so looks like the problem was the battery. I opened the phone and changed battery. The first couple times, it did the same **** as before, but booted the 3rd time. Worked fine for an hour before running out of battery. Charging the new battery now to calibrate it. Hopefully it's fixed for good.

Thanks for all suggestions!