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

[Rony John]

i think i had a corrupted system partition.. but i tried the first method and all went good. when the green text appeared i disconnected and tried to boot..nothing happend. not even a single thing..no fastboot, no recovery. its not even detecting by the pc. now downloading the second method.. will the phone gets detected in the method 2.. ??
Edit: revived from full brick using method 2. ????

 

[jithuelad]

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

Man this is a life saver!
OP should add this to main post.

I was in the same situation, that fastboot works but nothing else (system, boot, boot_aging went missing). This saved me.

 

[oopstairs]

Man this is a life saver!
OP should add this to main post.

I was in the same situation, that fastboot works but nothing else (system, boot, boot_aging went missing). This saved me.

Glad I could help.

Sent from my ONEPLUS A3000 using Tapatalk

 

[Rony John]

After I hold the volume up button for 10 seconds and plug the phone in, it shows up in my computer as Qualcomm HS-USB Diagnostics 900E (COM3), I have tried all the drivers/methods listed in the guide and none of them update it too the 9008 that should be listed. Anyone have any ideas?

I had the same issue..but i read some where that its not the volume up+power button combo..instead plug in the device.it will detect as diagnostics 900E. press vol up+down+power until it changes to download mode. Then only your msm download detects the device. I recovered by using the method 2..method 1 fully destroyed my device since i had system partition corrupted.

---------- Post added at 10:29 AM ---------- Previous post was at 10:26 AM ----------

Thank you soooooooooooooo much for this!
Being new to rooting (and an all round moron) I relocked my bootloader when the device wasn't anything close to being stock. This guide was so helpful in correcting my mistake.

At first I was stuck because 900E looks a lot like 9008 -.-
But the real issue was with step 7 and trying to get the MSM Download Tool to work. It just wouldn't find my device even though I was sure I had everything necessary installed.

In any case; this allowed the computer to find it, so if you're in the same boat as me I hope this helps.
Perhaps in the long run this post might save the support team more time than I wasted for them... although I doubt it...

Anyway, good luck and have a great day!

When the device detects as 900E press and hold vol up+down+power button until it changes to 9008 download mode.

 

[MouraGiovanni]

mega unbrick OP3

in my partition it appears flashing is not allowed what should I do, it goes into fastboot mode is recognized, but it appears this error on failed when I try to flash any of the files.

 

[lrpvo]

Hey guys.
Came from latest OxygenOS, rooted and xPosed running. All of a sudden, phone died.

Managed to use this guide and (seemingly) succesfully flashed (using method 2). Still however, an issue persists. I've been able to boot into system exactly once, allowing me to go through set-up. When trying to reboot, I bricked it again.

Anyone seen this before? Any thoughts?
Kind regards,
Laurens

 

[solidoblu]

OP3 hardbricked

Hi guys,
yesterday, during the OTA update, unfortunately, i've hard-bricked my OP3 . Now I'm trying second method of this guide (first doesn't work) but I wuold like to have a clarification about the data wipe prevention. The guide says:

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 !!!

What does it means Delete all userdata?
That i have to erase ALL xml data or only the highlighted rows:

<?xml version="1.0" ?>
<data>
  <!--NOTE: This is an ** Autogenerated file **-->
  <!--NOTE: Sector size is 4096bytes-->
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="" label="ssd" num_partition_sectors="2" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="8.0" sparse="false" start_byte_hex="0x6000" start_sector="6"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="persist.img" label="persist" num_partition_sectors="8192" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="32768.0" sparse="true" start_byte_hex="0x8000" start_sector="8"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="cache.img" label="cache" num_partition_sectors="65536" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="262144.0" sparse="true" start_byte_hex="0x2008000" start_sector="8200"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="" label="misc" num_partition_sectors="256" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="1024.0" sparse="false" start_byte_hex="0x12008000" start_sector="73736"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="" label="keystore" num_partition_sectors="128" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="512.0" sparse="false" start_byte_hex="0x12108000" start_sector="73992"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="devcfg.mbn" label="devcfg" num_partition_sectors="32" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="128.0" sparse="false" start_byte_hex="0x12188000" start_sector="74120"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="devcfg.mbn" label="devcfgbak" num_partition_sectors="32" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="128.0" sparse="false" start_byte_hex="0x121a8000" start_sector="74152"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="" label="frp" num_partition_sectors="128" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="512.0" sparse="false" start_byte_hex="0x121c8000" start_sector="74184"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="dynamic_nvbk.bin" label="oem_dycnvbk" num_partition_sectors="2560" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="10240.0" sparse="false" start_byte_hex="0x12248000" start_sector="74312"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="static_nvbk.bin" label="oem_stanvbk" num_partition_sectors="2560" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="10240.0" sparse="false" start_byte_hex="0x12c48000" start_sector="76872"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="param.bin" label="param" num_partition_sectors="256" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="1024.0" sparse="false" start_byte_hex="0x13648000" start_sector="79432"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="reserve1.bin" label="reserve1" num_partition_sectors="2024" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="8096.0" sparse="false" start_byte_hex="0x13748000" start_sector="79688"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="reserve2.bin" label="reserve2" num_partition_sectors="4048" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="16192.0" sparse="false" start_byte_hex="0x13f30000" start_sector="81712"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="config.bin" label="config" num_partition_sectors="128" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="512.0" sparse="false" start_byte_hex="0x14f00000" start_sector="85760"/>
  [B]<program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="userdata.img" label="userdata" num_partition_sectors="0" partofsingleimage="false" physical_partition_number="0" readbackverify="false" size_in_KB="0" sparse="true" start_byte_hex="0x14f80000" start_sector="85888"/>[/B]
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="gpt_main0.bin" label="PrimaryGPT" num_partition_sectors="6" partofsingleimage="true" physical_partition_number="0" readbackverify="false" size_in_KB="24.0" sparse="false" start_byte_hex="0x0" start_sector="0"/>
  <program SECTOR_SIZE_IN_BYTES="4096" file_sector_offset="0" filename="gpt_backup0.bin" label="BackupGPT" num_partition_sectors="5" partofsingleimage="true" physical_partition_number="0" readbackverify="false" size_in_KB="20.0" sparse="false" start_byte_hex="(4096*NUM_DISK_SECTORS)-20480." start_sector="NUM_DISK_SECTORS-5."/>
</data>

Thanks in advance.

 

[MarcoLK]

omg thx!!!!!!
i unbricked my phone
i got only to fastboot mode and flashing recovery was not working.
i started this tool and it worked!!!! thx very much!
saved my life!

 

[PlayingLikeAGenius]

I can just say THANK YOU <3. You saved my life man this solved all my problems of the new community build

 

[m1s3rys1gn4l]

this man is awesome, method 2 worked for me bhai take love from Bangladesh

 

[MarcoLK]

I can just say THANK YOU <3. You saved my life man this solved all my problems of the new community build

If you had the black Screen Bug you easily had to Flash a special twrp Version
I had the same Problem

 

[CeruleanSky]

Works, thanks!

I followed this guide after my recovery partition became corrupted, and now my phone is working as if it were stock again!

 

[Eagle-no1]

How long time is going to change the color green?
Does not change either method.
I've been waiting for one hour, and nothing happens.
The phone is displayed windows device manager, Win Enterprise 64bit


I introduced the 32 bit Windows as now managed immediately.

Many thanks to great help.

 

[syl2002lys]

Thanks for the guide ! method 1 doesn't work for me but the 2d yes (without erase userdata !)

 

[gelomc]

I tried the tutorial and with the method two are able to restore my phone after having encounter any difficulties with the community build 3.5.2 butnow any rom or OTA I try to install the phone goes into bootloop and I'm no longer the recovery . how can I fix ? sorry for my bad english

 

[Suppeman]

THANK YOU SO MUCH!!!! After 3 hours of messing with these things I got it to work... Btw if someone gets problems in MsmDownloadtool like I had. Then try to diconnect ur phone from pc and put it to bootloader mode (Power+volume) and from there select power off and after that connect to pc again pressin volume up and it should work.

 

[synquall]

Thank you so much!!! this saved my phone. method 2 for me, was so anxious!

 

[martinezma99]

I'm on Community Build 3.5.2 trying to revert back to 3.2.1

I keep getting the following errors while in MSMDownload Tool Method 2

Sahara communication Failed.
FirehouseCheckRSP Failed

Any suggestions?

MSMDownload Tool Method 1
FirehoseCheckRSap Failed, Errno 258

Please help. I can't restart phone in recovery or bootloader after trying Method 1. Nothing. Plugging phone does not charge either.

What are my options?

Sent from my SM-G935U using XDA-Developers mobile app

 

[Rony John]

I'm on Community Build 3.5.2 trying to revert back to 3.2.1

I keep getting the following errors while in MSMDownload Tool Method 2

Sahara communication Failed.
FirehouseCheckRSP Failed

Any suggestions?

MSMDownload Tool Method 1
FirehoseCheckRSap Failed, Errno 258

Please help. I can't restart phone in recovery or bootloader after trying Method 1. Nothing. Plugging phone does not charge either.

What are my options?

May be its the driver issue.

 

[martinezma99]

May be its the driver issue.

Can you expand a little bit?

Sent from my SM-G935U using XDA-Developers mobile app