Oneplus Two - Solution for Hard Bricked Device

[andip71]

unbricked !

Hi all,

ok, so finally I was able to fully recover my OP2 now.

Remember, I had the issue described: recovery completely broken, bootloader locked, Enable OEM option in developer options not available.
So, I was at a dead end. Phone working, but without recovery no chance to take backups, flash something etc.

So this is what I did now:
1) Downloaded the USB drivers linked in the OP (or from here:
https://mega.nz/#!mRgH0KJS!rCo7tgzXLUDQOUxXxtBpwPXk8Bw3JITbozZelmsKEPE )

2) Used my own, modified recovery tool (which has Hydrogen recovery built in instead of twrp, as twrp continued to be broken). Download my version from here:
https://mega.nz/#!uBYGHLJD!w-ByaqFeHuUrzJXPuDRXNu4HYcCBKqVAEe7W1xzrY8k

3) Powered off phone, plugged usb cable into PC

4) Pressed Vol+ and Power key until I got the mysterios QUALCOMM device as unknown device in windows device manager (just slightly named differently than in the OP)

5) installed the driver as described in the op

6) started the recovery tool as decribed in the op (my version) and flashed it

7) Phone restarted into OOS

8) I restarted the phone into recovery and voila - HydrogenOS recovery was back

9) I wiped data and cache in that recovery

10) I flashed OxygenOS 2.0.0 full version (around 1 GB size)

11) I flashed without reboot directly after the full version the OTA update of today (40MB size)

12) Rebooted and I had the "Enable OEM" switch in developer options, which I enabled

13) Went into fastboot mode and flashed TWRP

14) ... yes, the rest is as it was before, flashing SuperSu to root the phone etc.

Finally I am fully functional again. Horray.

Many thanks to @Zyxxeil who had the idea to try with HydrogenOS recovery instead of TWRP - which helped.

Hope this is helpful for you guys with the same problem.

Although I think the full recovery package should help much more easy in future.

Cheers and have a nice day
Andi

 

[qwsdert4]

Very nice. Wait for it...
Is a Version with Oxygen OS also aviable?

Unfortunately no. So far the international team of OP are quite shy on releasing their internal package. However you can always flash the full Oxygen OS zip package while in recovery.

 

[Zyxxeil]

There will be with my toolkit

 

[qwsdert4]

full recovery package updated

 

[khr0n0s]

@Lord Boeffla Thanks. I now have the stock recovery flashed. I did just try and flash the 40MB incremental, but it failed. I am guessing due to me having rooted the device. I will flash the complete ROM later.

 

[xionix]

u did realy a great job maybe just update the full package with the english language automatical

great i'm unbricked too

 

[CoreGaming]

unbricked too! thanks!

 

[devon4786]

Hi all,

ok, so finally I was able to fully recover my OP2 now.

Remember, I had the issue described: recovery completely broken, bootloader locked, Enable OEM option in developer options not available.
So, I was at a dead end. Phone working, but without recovery no chance to take backups, flash something etc.

So this is what I did now:
1) Downloaded the USB drivers linked in the OP

2) Used my own, modified recovery tool (which has Hydrogen recovery built in instead of twrp, as twrp continued to be broken). Download my version from here:
https://mega.nz/#!uBYGHLJD!w-ByaqFeHuUrzJXPuDRXNu4HYcCBKqVAEe7W1xzrY8k

3) Powered off phone, plugged usb cable into PC

4) Pressed Vol+ and Power key until I got the mysterios QUALCOMM device as unknown device in windows device manager (just slightly named differently than in the OP)

5) installed the driver as described in the op

6) started the recovery tool as decribed in the op (my version) and flashed it

7) Phone restarted into OOS

8) I restarted the phone into recovery and voila - HydrogenOS recovery was back

9) I wiped data and cache in that recovery

10) I flashed OxygenOS 2.0.0 full version (around 1 GB size)

11) I flashed without reboot directly after the full version the OTA update of today (40MB size)

12) Rebooted and I had the "Enable OEM" switch in developer options, which I enabled

13) Went into fastboot mode and flashed TWRP

14) ... yes, the rest is as it was before, flashing SuperSu to root the phone etc.

Finally I am fully functional again. Horray.

Many thanks to @Zyxxeil who had the idea to try with HydrogenOS recovery instead of TWRP - which helped.

Hope this is helpful for you guys with the same problem.

Although I think the full recovery package should help much more easy in future.

Cheers and have a nice day
Andi

Hey, which model OP2 you have? I have the A2005 and I unlocked the bootloader and flashed twrp..however when i checked fastboot device info it said tampered=true but unlocked as false. Ran the command again, now the phone is in a bootloop if i plug the charger in, bootloop if i try to run that command again, and no response if i try to turn it on.

 

[Zyxxeil]

Hey, which model OP2 you have? I have the A2005 and I unlocked the bootloader and flashed twrp..however when i checked fastboot device info it said tampered=true but unlocked as false. Ran the command again, now the phone is in a bootloop if i plug the charger in, bootloop if i try to run that command again, and no response if i try to turn it on.

Try using @Lord Boeffla instructions and once you boot up into oxygen update to V2.0.1 and make sure you are able to toggle the switch "enable OEM unlock" in dev settings, then try unlocking bootloader.

 

[devon4786]

Will try now. However, the tool says A2001..but I have the A2005..it's safe to use?

 

[Zyxxeil]

Will try now. However, the tool says A2001..but I have the A2005..it's safe to use?

Hmm, I don't have experience using this tool on other device models but if I were to guess nothing would be different. I would wait for confimation from another developer as I wouldn't want you to risk your device.

 

[devon4786]

Try using @Lord Boeffla instructions and once you boot up into oxygen update to V2.0.1 and make sure you are able to toggle the switch "enable OEM unlock" in dev settings, then try unlocking bootloader.

Will try now. However, the tool says A2001..but I have the A2005..it's safe to use?

Forgot to quote :/..Just wondering if it'd be safe to go this route although I have the A2005 while this is for the A2001

 

[dlhxr]

I am very glad to see my post is posted here~and i will upload another minimal version of the toolkit later on with stock recovery.
The reason why we can't use my minimal version to fix the recovery problem is that their booloaders are locked and my minimal version has unofficial twrp in it.~

 

[Naman Bhalla]

I have successfully used it on a2005... So it works.

From my Exodised lettuce with Sandy Kernel

 

[andip71]

I am very glad to see my post is posted here~and i will upload another minimal version of the toolkit later on with stock recovery.
The reason why we can't use my minimal version to fix the recovery problem is that their booloaders are locked and my minimal version has unofficial twrp in it.~

That is why I put another version of the toolkit up, which includes the official Hydrogen recovery instead.

Andi

 

[bwells88]

I'm not a toolkit sort of guy for the most part so I grabbed both files and flashed them In order then root... All seems well, went into development options and selected the "do not lock" switch... It's definitely 2.01 but it still wants to download a system update... Same date?.. Oh well it's working awesome thank you!

 

[yakuzlin]

Need help

Hey guys I need help with my OPO 2. I have the Chinese version and I tried to update from 2.0.0 to 2.0.1 update and then I tried unlocking the bootloader. Ever since then the device is stuck in a boot loop with the 1+ logo showing and then rebooting right after that. I cannot get into recovery and the only thing I can do is force it into fastboot, at that point I cannot lock or unlock the bootloader. fastboot oem device-info shows bootloader is locked but

I tried using the recovery tool and got it to show the QUALCOMM driver under device manager then used the QCOM tool and I can see that from the application that it loads the files till #2, not sure if all the numbers are supposed to be highlighted green when it loads it all or if it is supposed to stop at #2. However after #2 is turned green on the app the phone goes back into the boot loop.

Has anyone experienced this? If so how do I fix it?

Edit:

This is what it shows under fastboot device-info
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.086s]
finished. total time: 0.088s

 

[andip71]

Hey guys I need help with my OPO 2. I have the Chinese version and I tried to update from 2.0.0 to 2.0.1 update and then I tried unlocking the bootloader. Ever since then the device is stuck in a boot loop with the 1+ logo showing and then rebooting right after that. I cannot get into recovery and the only thing I can do is force it into fastboot, at that point I cannot lock or unlock the bootloader. fastboot oem device-info shows bootloader is locked but

I tried using the recovery tool and got it to show the QUALCOMM driver under device manager then used the QCOM tool and I can see that from the application that it loads the files till #2, not sure if all the numbers are supposed to be highlighted green when it loads it all or if it is supposed to stop at #2. However after #2 is turned green on the app the phone goes back into the boot loop.

Has anyone experienced this? If so how do I fix it?

Edit:

This is what it shows under fastboot device-info
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.086s]
finished. total time: 0.088s

Quite common thing.

Use the toolkit provided here to be back in business.
It really works.

Andi

 

[taki7610]

Hi all,

ok, so finally I was able to fully recover my OP2 now.

Remember, I had the issue described: recovery completely broken, bootloader locked, Enable OEM option in developer options not available.
So, I was at a dead end. Phone working, but without recovery no chance to take backups, flash something etc.

So this is what I did now:
1) Downloaded the USB drivers linked in the OP

2) Used my own, modified recovery tool (which has Hydrogen recovery built in instead of twrp, as twrp continued to be broken). Download my version from here:
https://mega.nz/#!uBYGHLJD!w-ByaqFeHuUrzJXPuDRXNu4HYcCBKqVAEe7W1xzrY8k

3) Powered off phone, plugged usb cable into PC

4) Pressed Vol+ and Power key until I got the mysterios QUALCOMM device as unknown device in windows device manager (just slightly named differently than in the OP)

5) installed the driver as described in the op

6) started the recovery tool as decribed in the op (my version) and flashed it

7) Phone restarted into OOS

8) I restarted the phone into recovery and voila - HydrogenOS recovery was back

9) I wiped data and cache in that recovery

10) I flashed OxygenOS 2.0.0 full version (around 1 GB size)

11) I flashed without reboot directly after the full version the OTA update of today (40MB size)

12) Rebooted and I had the "Enable OEM" switch in developer options, which I enabled

13) Went into fastboot mode and flashed TWRP

14) ... yes, the rest is as it was before, flashing SuperSu to root the phone etc.

Finally I am fully functional again. Horray.

Many thanks to @Zyxxeil who had the idea to try with HydrogenOS recovery instead of TWRP - which helped.

Hope this is helpful for you guys with the same problem.

Although I think the full recovery package should help much more easy in future.

Cheers and have a nice day
Andi

Tks so much, my phone brick recovery so i try follow solution it's live

 

[andip71]

Tks so much, my phone brick recovery so i try follow solution it's live

Great! Glad we could help.

Andi