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?
Got the device to show up as 9008, I tried method 2 first, but the downloader tool fails during/right after the system.img dowlnoad. It says FirehoseCheckRSP failed Errno: 258, and the device disconnects. So then I tried method 1 and it worked, but I got the md5 checksum bootloop and was unable to boot into recovery or bootloader. Should I just keep trying method 2 until it works? Thanks for all your help so far.
Edit: Got the Full Downloader to complete, and running into the same md5 checksum error. With the error I can get into fastboot but I can't flash a recovery to boot to.
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 :-
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 :- Extract the Recovery Tool.
Step 2 :- Open all rawprogram...........xml through Notepad++
Step 3 :- Delete all userdata........ lines from the xml file.
DONE !!!
A3000
first method - the problem similar to mstrub
second method - work, but not updated on Oxygen or Hydrogen newest. Again brick.
At the same time flashing any custom base on Cyan successfully installed
Got the device to show up as 9008, I tried method 2 first, but the downloader tool fails during/right after the system.img dowlnoad. It says FirehoseCheckRSP failed Errno: 258, and the device disconnects. So then I tried method 1 and it worked, but I got the md5 checksum bootloop and was unable to boot into recovery or bootloader. Should I just keep trying method 2 until it works? Thanks for all your help so far.
Edit: Got the Full Downloader to complete, and running into the same md5 checksum error. With the error I can get into fastboot but I can't flash a recovery to boot to.
I've got solution for you mate.
1. Download full recovery tool from method 2
2. Extract
3. reboot to fastboot mode
4. fastboot flash command the file in red on your md5 checksum.
5. fastboot reboot.
6. voila
Got the device to show up as 9008, I tried method 2 first, but the downloader tool fails during/right after the system.img dowlnoad. It says FirehoseCheckRSP failed Errno: 258, and the device disconnects. So then I tried method 1 and it worked, but I got the md5 checksum bootloop and was unable to boot into recovery or bootloader. Should I just keep trying method 2 until it works? Thanks for all your help so far.
Edit: Got the Full Downloader to complete, and running into the same md5 checksum error. With the error I can get into fastboot but I can't flash a recovery to boot to.
I've got solution for you mate.
1. Download full recovery tool from method 2
2. Extract
3. reboot to fastboot mode 4. fastboot flash command the file in red on your md5 checksum.
5. fastboot reboot.
6. voila
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
Hello,, i have problem with op3. When i upgrade oxygen i failed and reboot. Now I stuck on op logo..
I stucked in steps 8. Click start and nothing.. Only no devices etc..
In both methods the same.. Any ideas?
If your PC can't detect the device at all you need to return it. Its most likely completely ****ed if Linux can't talk to your device either. This is common android knowledge 101 and I don't get why OP called it hardbrick. There's different levels of soft brick and this is defiantly still soft brick.
If your PC can't detect the device at all you need to return it. Its most likely completely ****ed if Linux can't talk to your device either. This is common android knowledge 101 and I don't get why OP called it hardbrick. There's different levels of soft brick and this is defiantly still soft brick.
Return? i dont have recovery file... And i dnot have linux
Factory reset does nothing ;<. I can boot to fastboot and to recovery mode. But this is all..
Sorry for my bad eng
Guys i have solution... New windows ! And i have new oxygen..
Always do backup your pc and phone!
I'm trying to follow this guide because my OnePlus 3 is not detected when I connect it to my computer (whenever it's switched on, in recovery or in fastboot).
The thing is that my phone is not detected even when I use the "push up button while connecting the phone" trick.
Does that mean I will have to RMA the phone ?
What I don't get is that it's already the second OnePlus 3 I have that has this problem. Is it possible that one of my accessorry is killing the OP3 data part of its USB port ???
I have a Xiaomi PowerBank, RAVPower 6-ports charger and a Spigen 2-ports car charger...
This thread makes me even more terrified to root my brand new OP3!!! Of course I want root access and Xposed but I also want a functional device and there's no way OnePlus will replace something hard bricked by user fault... I'm torn