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

Search This thread

TNSMANI

Senior Moderator / RC-RT Committee
Staff member
Jan 8, 2014
6,440
2
10,451
Chennai
OnePlus 9 Pro
i try another pc and everything good but last step msmtool said (sahara communication failed please try again after power off phone)

i try this solution volume+ and power but not Success
When connecting, does the Device Manager recognise the phone as Qualcomm HS USB? Or as QHUSB_BULK? Are you trying Method 2? Try downloading the Tool and the OS again.
Did you try the later Tools? If they too fail, you may have a hardware issue.
 
Last edited:

njumh

New member
Nov 8, 2013
1
0
{Mod edit: Quoted OP shortend for better reading experience!}


i was trying over and over again but no result

stuck on black screen and white notification light up
but stay can connect to my pc with HS-USB QDloader 9008 at com 11
and last trying after flash using msmdownload tools stuck on black screen and red notification light up


anyone can you help me ?
 
Last edited:

duhhhst

New member
Jul 31, 2016
2
0
Sorry to bring back a dead thread but..

Found my old OP3 I wanted to restore for my daughter to use (shes only 5) but the phone is hard bricked. I dont know what the hell I was doing or how it happened but I do remember playing around with ROMs and I somehow deleted the ROM and now the phone wont boot into anything. I can try to boot into TWRP but just freezes on the TWRP logo. If I boot normally it shows the normal screen to press the power button to power on normally but almost instantly goes to another start up screen that says "DM-Verity is not started in enforcing mode and may not work properly" then tried to boot and gets stuck on the OP logo.

I've download all the drivers and installed them (at least to my knowledge its installed correctly), I have rebooted the computer with Driver Signature disabled, and no luck getting the phone recognized by computer (Held Volume up 10s, plugged into computer and nothing happens. I held volume up for easily 10mins while plugged in.)

Help?? I'm completely lost and we're looking to do a 10 hour roadtrip and I'd rather not have to buy a new phone/tablet.... PLEASE HELP ME!! hahah
 

itrystuff

Member
Jul 27, 2016
10
2
Maybe just wait some minutes when TWRP screen is displayed. On my device it took longer and longer too load when the internal storage is full of data. I think it took 2-3 minutes. Maybe you gave up too early, I don't know.
 

duhhhst

New member
Jul 31, 2016
2
0
Maybe just wait some minutes when TWRP screen is displayed. On my device it took longer and longer too load when the internal storage is full of data. I think it took 2-3 minutes. Maybe you gave up too early, I don't know.

Tried it before but just for kicks I'm trying it again. Currently at 16mins and still at the TWRP screen...
 

Oswald Boelcke

Senior Moderator / Moderator & RC-RT Committees
Staff member
Bro the driver is coming and disappearing what to do
I've removed all the duplicate posts that you've made though different threads within a few minutes.

XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
  • You can bump your unanswered question once every 24 hours
  • Duplicate threads and posts will be removed
  • Always post in an existing thread if a topic already exists, before creating a new thread.
  • Use our search function to find the best forum for your device.
  • Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
  • Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
 

IW4

Member
May 22, 2010
12
7
Man, I really didn't want to have to write this, but maybe someone has a better idea than me.
I've been using method 2 for days on my softbricked OP3, since I don't care about the data on it, but universally get the Sahara error. What I'm noticing is that when I get it connected in EDL and press Start, it does the Firehose download, then immediately disconnects and reconnects thrice; I can see the status go from Connected to N/A and back, and it likewise disappears from Device Manager and gives the disconnected sound. 15 seconds later, it errors out. I've done this on five different PCs, with four different types of cables, on six different software versions, but the end result is always the same. It seems like the common denominator is either the phone or me, and I'm not about to count either out.
 

TNSMANI

Senior Moderator / RC-RT Committee
Staff member
Jan 8, 2014
6,440
2
10,451
Chennai
OnePlus 9 Pro
Man, I really didn't want to have to write this, but maybe someone has a better idea than me.
I've been using method 2 for days on my softbricked OP3, since I don't care about the data on it, but universally get the Sahara error. What I'm noticing is that when I get it connected in EDL and press Start, it does the Firehose download, then immediately disconnects and reconnects thrice; I can see the status go from Connected to N/A and back, and it likewise disappears from Device Manager and gives the disconnected sound. 15 seconds later, it errors out. I've done this on five different PCs, with four different types of cables, on six different software versions, but the end result is always the same. It seems like the common denominator is either the phone or me, and I'm not about to count either out.
Hopefully the PCs were Intel and not AMD Ryzen. And by saying different software versions, you mean different versions of the Tool. If not, try the other versions available in a link in post no.766 above.

And on you being one of the common denominators, your role is very limited. If the download starts, then it is automatic. So you can count you out.

If all that has been done, I have nothing more to offer. I am also stumped.

EDIT: You are on Win 10 right? Also check THIS article, if you have not so far seen it.
 
Last edited:

nighthawk658

Member
Oct 1, 2015
43
3
Hi there
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 though the method 2 file is exact file 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.

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 OP3 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 :-
Code:
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
and 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.

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


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


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.




an interesting post ....

i have an asus Zenfone 5 ZC600KL X017DA currently stuck on the Asus logo have attempted to run the recovery via the volume and power buttons but nothing coes up i only get CSC fastboot displayed

have come across some fastboot commands also was included in one of the firmware i downloaded and phone is seen by ADB fastboot as its S/N appears following instructions from the Rom all i get is permission denied and partitition is write protected so from what i understand is the bootloader is locked

most research i have done so far has always kept pointing to needing debugging enabled or commands to unlock bootloader that always keeps being denied

but since the phone wont boot i am kinda screwed and being a Qualcomm chipset its rather frustratingly new to me as i am ok flashing MTK cipsets using SPFT

and before i forget i have tried using the Qfil flashtool but i kept getting errors on that such as failed firehose and another Sarah error or something of that nature

so is there anything you can suggest maybe what you mentioned in your post but for the Asus

many thanks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 170
    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 though the method 2 file is exact file 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.

    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 OP3 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 :-
    Code:
    OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
    and 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.

    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​


    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​


    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.


    10
    i am having the same issue.. glad to hear you got the solution.. can you please explain step 4 in your solution
    which file are you talking about?

    On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
    - download this : https://www.androidfilehost.com/?fid=24591000424942573
    and then extract.
    - download platform tools attached below. extract in the same folder with first file you've downloaded.
    - Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
    - on the folder, hold shift and right click, click open command here
    - type fastboot devices
    - make sure your serial number appear.
    - now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
    - e.g. "fastboot flash boot_aging boot_aging.img.
    - make sure you flash all the missing partition.
    - type fastboot reboot.
    this will boot you to oos 3.1.2.
    unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA


    goodluck mate. sorry for my english
    6
    I just re-followed Method 2 and it worked flawlessly with the new upload :)

    Thanks!
    Good to know .

    Would be great if someone can confirm new method 1 to also work. The missing loop has been added. It should work, but, who knows .

    EDIT :- Confirmed that it works by another guy. So, we are all set now.

    Sent from my OnePlus2 using XDA Labs
    4
    Phone is now completely bricked and won't even go to Fastboot after following this guide. No lights, nada.
    Definitely not possible. I have tested it myself on a friend's device. What was the status of the phone before ?

    Sent from my OnePlus2 using XDA Labs
    4
    A screenshot of the errors please.

    Sent from my OnePlus2 using XDA Labs