[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3

Jun 26, 2016 02:39Last edit: Jun 26, 2016 06:17
173
574
322.8k
Hello Everyone !!

A hard bricked OP3 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP3 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP3 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.

The solution for OP3 hardbrick is similar to OPO - you just need a Qualcomm driver and a recovery package. A very very big thanks to some guys at XDA who got these files (don't know how) (I have modified the Method 1 file but Method 2 file remains exact from OnepLus) and helped all of us to get out from one of the most weird state of the phone. Thanks guys ( @CyberCROC and 1 more)

METHOD 1

This method is the best method and will not wipe your data at all and will give you stock recovery+latest OxygenOS (or the ROM you were on) and bootloader will remain in the state it was earlier.It *might* not work if some other partitions were also corrupted.

Spoiler: Instructions
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753
2.) Recovery Tool :- https://www.androidfilehost.com/?fid=24591000424942611
3.) [OPTIONAL :- Will be required only if you don't have a working system] Latest OxygenOS :- https://www.androidfilehost.com/?fid=24591020540821926
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
........................NEXT STEPS ARE TO BE FOLLOWED ONLY IF YOUR OP2 DOESN'T BOOT INTO SYSTEM STILL BUT IS STUCK ON ONEPLUS LOGO..............................
Step 10 :- Boot your phone into recovery (Power+Volume Down).
Step 11 :- Click on Install Update.
Step 12 :- Install adb for windows system-wide if not already installed :- http://forum.xda-developers.com/showthread.php?p=48915118
Step 13 :- Navigate to the folder containing Latest OxygenOS Zip. Shift+Right Click anywhere in the folder and Open Command Window.
Step 14 :- In the command window,type :-

OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zipand wait for it to finish.Then reboot into system.

METHOD 2

This method is easy to use and flashes OxygenOS 3.1.2 on your phone. It wipes all your data (See end of post on how to not wipe data) and restores all partitions to stock. It will work in any condition unless it is a hardware damage.

Spoiler: Instructions
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753
2.) Recovery Tool :- https://www.androidfilehost.com/?fid=24591000424942573

------------------Follow Step 2 to Step 9 from Method 1 --------------------



How to Prevent Data Wipe in Method 2


Spoiler: Instructions
Step 1 :- Extract the Recovery Tool.
Step 2 :- Open all rawprogram...........xml through Notepad++
Step 3 :- Delete all userdata........ lines from the xml file.
DONE !!!


How to Make the device show as Qualcomm 9008

Spoiler: Tricks
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)

  • Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
  • Keep phone disconnected from PC.
  • Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
  • Run the Qualcomm setup wizard (also located in the qc folder)
  • When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
  • The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.

OnePlus 3/3T
Join
Add a comment
All comments(574)
Naman Bhalla
BTW The files got us almost everything needed to get unofficial fastboot images. Will build tomorrow and upload on Mirrors thread. kthxbye
Jun 26, 2016 02:4012 LikesReply
Funk Wizard
Bravo
Jun 26, 2016 02:439 LikesReply
pablofg1978
Awesome work!
Jun 26, 2016 04:065 LikesReply
meatandy
#NoBricksHere
Jun 26, 2016 04:025 LikesReply
Jitesh Saitawadekar
Life Saviour strikes back for OP3 users
Jun 26, 2016 03:055 LikesReply
SoniaB
Great work again Naman.
Jun 26, 2016 05:024 LikesReply
Tobikage
@meatandy said:
.. nope

Atleast you have a 3 that you can potentially brick
Jun 26, 2016 04:254 LikesReply
meatandy
@Tobikage said:
For now.....

.. nope
Jun 26, 2016 04:154 LikesReply
Tobikage
@meatandy said:
#NoBricksHere

For now.....
Jun 26, 2016 04:094 LikesReply
Shadeone
Dear all,

received my new oneplus 3 yesterday after work, synchronized contacts and apps with my google account ... fully charged the phone and then go out for diner.

Less than one hour later, the phone was "dead".

After looking forward i was happy to discover that my device is bricked and not dead at all.

I've installed the USB drivers without any problem, i'm using the "OnePlus3_Unbrick_Tool_Full" package. When i start the program, after a few seconds i have "Firehose communication handshake failed" or "Sahara communication failed"
red error message.

i'm using windows 10

I've seen some people had the same problem, but stopped talking about it without any clear solution given, so i supose that maybe they've found the solution and did not take time to post it here ?

S O S !
Jun 28, 2016 15:493 LikesReply
harlekinwashere
I used the stock firmware you linked to unbrick a softbricked Oneplus 3 (fastboot and stock recovery still working, but OS in a bootloop) - so I had not to fiddle around with the Qualcomm driver and the rescue tool - but never the less here are a few findings.

1. The oxygen firmware in the link is 3.1.3 and not 3.1.2
2. In my case I had issues getting the Google ADB drivers (the drivers should be installed as part of the "15 seconds adb and fastboot installer" that is linked in the "how to root your Oneplus 3" thread) to install for the "Android" device while trying to adb sideload the firmware in stock recovery. This is how I fixed it. Boot into stock recovery, select english (or your language), then select install new firmware over adb, then click along until the screen says that you should adb sideload now. At this point a device named "Android" should show up in your device manager. If it has issues being recognized, rightclick it, select install/update drivers (not sure if its called install or update - it was the first rightclick menu entry if I remember), then install drivers from folder, skip the folder part and select install from list then select "Android device" or "All devices" (if Android device doesnt show up like it was in my case), then choose the vendors list, scroll down to Google, and there should be two adb and one fastboot driver available, select the first adb driver and install the device. Test in a command window if adb devices works (a device is listed), if it does you are set - if it doesnt, you havent installed the right driver - so redo the process. You can also download and look through the howto_driver.zip in this thread: ( http://forum.xda-developers.com/showthread.php?t=2588979 ) if it helps - that said - I had to select all devices, then go through the vendor list and select google to find the respective drivers.
3. You can wipe data and cache from stock recovery (advanced menu) if you need to.
4. If your fastboot is still working AND you unlocked your bootloader prior to the "incident" you also can use Mauronofrios All in One Tool ( http://forum.xda-developers.com/one...ol-tool-one-driversunlocktwrpfactory-t3398993 ) to flash stock recovery if you should need to -- I tell you my softbrick story shortly to underline why. Disclaimer: The All in One Tool downloads the necessary files after the fact - which always is a bit risky, if you don't trust the dev.

My softbrick story goes as follows - I wanted to uninstall root revert to stock recovery and OEM lock the bootloader again - so I

- uninstalled SuperSU through its settings - there is a point saying uninstall/remove SU specifically - it will reboot your phone afterwards.
- after the reboot I made sure that OEM unlock, usb debugging and advanced reboot were enabled in developer options and rebooted to fastboot
- I used the All in One Tool to flash stock recovery in fastboot, then manually rebooted
- after the reboot I made sure that OEM unlock, usb debugging and advanced reboot were enabled in developer options and rebooted to recovery, to see if it had installed correctly - it did. I rebooted the phone (shut down by holding the power button)
- after the reboot I made sure that OEM unlock, usb debugging and advanced reboot were enabled in developer options and rebooted to fastboot, then locked the bootloader using the All on One Tool (you then have to confirm the process using onscreen options which you have to select on the phone).

After which the Oneplus 3 softbricked (bootloop, but both fastboot and (stock) recovery were still accessible).

I then went into stock recovery, wiped data/cache under "install new firmware/advanced" - and then adb sideloaded (adb sideload pathandnameofpackage.zip) the stock firmware linked in here - the firmware installed fine and the phone got unbricked.

Which brings me to point

5. The tutorial in here says to type the package name into a command prompt to sideload the firmware - but in my case I had to type in adb sideload pathandnameofpackage.zip - of course, so either this is a typo, or the command prompt window the OP talks about is one that gets opened by some of the debrick tools, and just wants you to input the package name...?

Anyhow - reverting to stock firmware, recovery and relocking the bootloader now is possible If you should want to do it.
Jun 26, 2016 14:573 LikesReply
Naman Bhalla
@masaga91 said:
I tired method 1, after the green letters, tried to boot into system, nothing happended.Now i'm trying to try method 2 but i tried with every driver and i cant managed to get into qualcomm 9008, always says 900E

For method 1, did you do sidleoading too ? Because it is also required. And how was device in 9008 for method 1 but not in 2 ?
Jun 26, 2016 13:243 LikesReply
Naman Bhalla
Full tool up. Mini tool down. Making a new version of Mini. Thanks

EDIT :- New mini tool is up too
Jun 26, 2016 05:383 LikesReply
JorgeManuelSilva91
@Zachvlol said:
If my phone ever gets bricked I will refer to this; thanks!

It's always best to try not to brick it. Always read and understand any instructions and research if you have doubts, this will save you from hassle.
Feb 11, 2017 05:032 LikesReply
naboo
@naboo said:
I got same problem as @Desertknight and @crushedeis

SOLVED by using method 2 (full)
Jan 03, 2017 08:402 LikesReply
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 39
Go to
Naman Bhalla
404404