Re-unlocking bootloader problem - OnePlus 2 Q&A, Help & Troubleshooting

I have a OnePlus 2 phone which has its boot-loader unlocked at some point and I accidentally re-locked the bootloader and was unable to flash through fast-boot and I'm now unable to root the phone.
I have TWRP ready because I flashed it earlier before i re-locked the bootloader.
I am able to boot to the OS, fastboot and TWRP recovery mode.
However rooting seems impossible for now.
Whenever I tried to unlock bootloader it shows:
C:\adb>fastboot oem unlock
...
OKAY [ 0.122s]
finished. total time: 0.122s
However, after trying to check if the device is unlocked, it shows that I didn't actually unlocked the device, rather:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(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.063s]
finished. total time: 0.063s
This is the only problem that I've received from my other phone, I used to root my 1+1 and it went well without a single problem.
And this is my first post (not like you guys care anyways) and I don't really know where to post my troubles so I apologize if I posted this in the wrong place.
Any suggestions / help would be very much appreciated.
Thanks in advance~
Kev.
[EDIT]
I have tried various methods to restore the phone when soft-bricked with SuperSU, and it works, however it doesn't allow me to reset the bootloader's status and I'm not capable of doing so.

Did you enable OEM unlocking in Developer settings?

Related

Locked out of OP2 A2003: recovery mode failed, developer options diasbled

I forgot my new Pattern lock. I had TWRP but it is not working now. Volume Down + Power button just gives a blank screen. After the Oxygen OS latest update, the developer options have been disabled which means OEM unlock and USB debugging are disabled.
Android Device Manager is not helping. I try erasing from the ADM but phone says rebooting and just switches off.
This is what happens when I boot into fastboot using volume up + power:
Code:
fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.016s
fastboot oem 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.08s]
finished. total time: 0.078s
Code:
adb devices
List of devices attached
adb does not detect any devices either.
What do I do?
The procedure mentioned in Technobuzz Unbrick oneplus 2 is not working either. Nothing seems to be happening after step 8. (Cannot post outside link as I am newbie)
http://forum.xda-developers.com/one...k-to-solve-t3325419/post65579304#post65579304
Similar case, refer to solutions posted
ciber05 said:
http://forum.xda-developers.com/one...k-to-solve-t3325419/post65579304#post65579304
Similar case, refer to solutions posted
Click to expand...
Click to collapse
Found this method in the above quoted post which worked like a charm.
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks

Possible Bricked?

Hi,
Earlier on today I was trying to root my phone (Well at least put TWRP on so I could mount a rom) and somehow the bootloader got locked during the process this has prevented me to install any roms....
I know it's locked because of -
(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.079s]
finished. total time: 0.080s
I've tried to recover it back to normal during the "Fastboot Mode" state but not had any luck I believe the phones bricked? -
C:\Users\Liam\Desktop\One Plus Recovery\A2001_14_A.03_150805>fastboot flash user
data userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
I need this sorting as I don't have a phone to use, and would really apreiciate if someone could help me as i've spent like 8 hours today trying to sort it but not had any luck i've downloaded drivers (Qualcom), Android SDK, this Qualcom-download-tool for recovery and nothing seems to work
It will only boot into "Fastboot Mode"
i recommand you to ask this on OnePlus forums there is more people that answer
otherwize did you tried fastboot oem unlock and is your phone recognize by your computer ?
Use the Qualcomm recover method mentioned many times over in this forum.
try fastboot oem unlock.
did u enabled oem unlock option in dev settings while unlocking bl?
what exactly steps you followed?

OnePlus Two - Unable to unlock OEM

Hello all,
I recently bought a OnePlus 2 and attempted to root it. I can only remember trying to root it with a locked bootloader (which caused the OnePlus startup to hang). Eventually, I put the OS back in. Now, in a second attempt to root my phone, the first step was to unlock the bootloader. Every time I type "fastboot oem unlock" it brings me back to TWRP. When boot back into fastboot and check device info, I get this:
(bootloader) Device tampered: false
(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.070s]
finished. total time: 0.070s
Also, attempting to flash any recovery (or any other command) returns this:
target reported max download size of 536870912 bytes
sending 'recovery' (22032 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.742s
Any suggestions? I've tried searching so many different threads all over Google.
Files that I have available to use: stock recovery, TWRP recovery, latest full ROM from OPT
Follow this guide:
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
I already tried this guide. The phone is fully functional. I just cannot unlock the bootloader.
Every time I type "fastboot oem unlock" it brings me back to TWRP.
Click to expand...
Click to collapse
How did you install TWRP if the bootloader is locked? Did you install TWRP previously and re-lock the bootloader?
I have no idea. I think so. But it's fine I somehow managed to unlock the bootloader (finally). I just found out that OxygenOS 3.1.0 doesn't allow root.

Re-locking bootloader but is unlocked at each reboot

Hi everyone,
I went back to stock recovery and stock ROM (5.9.020S) in order to use Android Pay.
But I am facing one last issue for locking the device. Each time I go into fast boot mode, I lock the device, I check with device-info, it confirms it is locked. However after reboot I check again it has reverted back as unlocked.
How can I lock the persistently?
It is as if there is a script somewhere at boot that automatically unlock the device bootloader.
- flash the aboot from stock ROM
- flash the xbl from stock ROM
- do not reboot to keep the bootloader still unlocked
- boot in TWRP (do not flash)
- wipe, factory reset, format, reboot system
In order to do what you suggest, I flashed TWRP recovery first. Then I followed all the steps. Then I tried to flash the stock recovery back and tried to lock. Unfortunately, it did not help, still the same issue.
In fastboot, I do "fastboot flashing lock" or "fastboot oem lock". Then I check the status with "fastboot oem device-info". Right after, I always get "Device unlocked: false" which is good and confirm the lock has worked at first.
But if I reboot the bootloader and try again, then the status is back to "Device unlocked: true" and the device is unlocked again. It keeps unlocking after reboot if I attempt to lock.
I need to have the device NOT unlocked in order to use Android Pay. So now, I am not sure what to do to be able to lock the device...
You don't need to flash TWRP in fact sometimes you don't need it (if there is no encryption but do it to be sure) right after flashing
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
These were indeed the files I flashed previously for aboot and xbl.
I tried again to flash the files in fastboot mode, then lock the device with "fastboot oem lock". After reboot, it is unlocked again.
Did you extract those files from 20s or any official OTA zip? Flashing those files are guaranteed to lock the bootloader again. I've tried it many times already so not sure what else could be missing.
What is being displayed when you do right after the flashing and TWRP steps?
Like this?
fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.097s]
finished. total time: 0.098s
---------- Post added at 02:39 PM ---------- Previous post was at 02:37 PM ----------
See this thread if it will help...
https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
I got the files from 20S. It really does not work for me.
I do:
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
After this when I check, it is like this (before and after reboot):
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.110s]
finished. total time: 0.111s
Click to expand...
Click to collapse
Anyway, thanks for trying to help me!

HARD BRICKED MOTO G4 plus

my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
tried this too but device get recognise
Cooltango26 said:
my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:
Click to expand...
Click to collapse
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.
ADITYA_KUMAR said:
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.
Click to expand...
Click to collapse
after the official update from ....update in my device .......my device was struck in boot loop ...so i tries flashing the stock rom to repair that ....during flashing it giving the above mention error ........
Only other things I can think of is perhaps holding down your power button (for up to 2-3 minutes) to force a hard shutdown, and then try booting. Alternatively, hold down both the power and volume down key, see if you can boot into the bootloader (which it looks like you can, if you're trying to fastboot the stock ROM). If so, then try to boot into the stock recovery and try a cache wipe or a factory reset (the factory reset will obviously wipe your data).
If your device is under warranty (and you did not unlock your bootloader at any point), the service centre might be the best bet for you, as we can't do anything with a locked bootloader and you're unable to boot to get to OEM unlocking...
The new [Updated] blankflash file for Moto g4 plus [June security patch ]
Hello friends
here is the new [Updated] blankflash file for June security patch
i hope it will help you. here is complete guide https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
about how to install it.
if it's works for you please let me know:highfive:

Categories

Resources