Database Info

[Q] OnePlus One - Unable to unlock bootloader again after relocking

Hi Guys,
Hope to get some help here.
So i unlocked the bootloader of my one plus one and installed supersu + Twrp recovery. All worked fine until i decided to relock the bootloader.
I've put the device into fastboot mode and executed "fastboot oem lock" with twrp recovery still in there.
Now i am trying to unlock the bootloader again using "fastboot oem unlock" to be able to flash the stock recovery and having issues.
output of commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>
After this it boots straight to twrp recovery. I then hit reboot system and go back to fastboot mode and run the below:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (12260 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.404s
Anyone has an idea how i can unlock the bootloader again ?
Thanks
Vik

Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out

I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
Thanks i'll give that a try as soon as am home..

YrrchSebor said:
Would it let you reflash the stock factory image thru fastboot? Maybe if you could do that it would let you unlock again. And it would give you stock recovery.
Or else what about the option in developer settings to update the stock cm recovery when installing an update. Maybe you could install an official update thru TWRP and get stock recovery back?
Just throwing out ideas, hope you figure it out
Click to expand...
Click to collapse
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks

Vikmeister said:
Hi YrrchSebor,
Thanks for the reply.. I already tried all that, even using adb sideload and keep getting same error as mentioned above. I'll try the solution lemonspeakers suggested later today and post the outcome.
Thanks
Click to expand...
Click to collapse
Be careful if you updated your phone to XNPH30O OTA,
!!! Warning !!!
In the NEW OTA CM11S XNPH30O, the bootloader (aboot) img size changed....
We request all not to apply the unlocker scripts on the new bootloader , until we confirm/find the new bit position.
It might brick your phone and corrupt bootloader...
Click to expand...
Click to collapse
It won't work.. do not try it if you updated to XNPH30O using the OTA.

zephiK said:
Be careful if you updated your phone to XNPH30O OTA,
It won't work.. do not try it if you updated to XNPH30O using the OTA.
Click to expand...
Click to collapse
Thanks for letting me know ZephiK i haven't updated to that version yet. I still have XNPH25R. I should all good.

Fantastic.. Thanks a lot guys.. That worked like a treat.. Bootloader is now unlocked.
:laugh::good:

lemonspeakers said:
I've documented ths same issue describe here: http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-twr-rooted-t2820341
The solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Download and flash that script.
Click to expand...
Click to collapse
I ran this command:
Code:
fastboot.exe boot TWRP-2.7.1.0.img
But the next step does not work:
Code:
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or from sdcard...
I got:
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.487s

That's because you can't boot a recovery with the recent bootloader unless you're unlocked.
Transmitted via Bacon

Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo

Im have the same issue but I have no recovery installed..Anyway to do this

i have same issue plz give me any solution if you found any???plz let me know plzzzzz
​
piriri007 said:
Hello,
so how to unlock the bootloader when:
- i can only access to fastboot and i have connectivity to pc;
- command 'fastboot oem unlock' doesn't work( FAILED (remote: oem unlock is disabled) )
- command 'fastboot flash recovery firmware.zip' doesn't work (FAILED (remote: Device not unlocked cannot flash or erase))
- all adb commands say: "error: device not found"
- i can't access recovery for use adb sideload (phone freezes with 1+ icon in screen)
- i can't access Android (phone freezes with 1+ icon in screen)
What can i do?
Thanks in advance!
Gustavo
Click to expand...
Click to collapse
plz help same issue

Original Shield Tablet Issues: ADB, Boot.img, and TWRP Recovery (for MM 6.0)

Ring. Towel: I give up!
Can't figure this out. I want to throw a new ROM onto my Original Nvidia Shield Tablet, RoW LTE. It's currently on Stock MM 6.0 unrooted. The bootloader is unlocked. I have at least three problems with this project:
ADB doesn't seem to work.
Can't connect at all using ADB. You'll say I need to update the USB drivers, but how come Fastboot works and ADB does not?
EDIT: ADB still doesn't work.
The boot.img doesn't seem to work.
Every time I flash an alternative bootloader using fastboot, Wifi disappears after the flash. The only solution seems to be to flash the stock boot. Should I be using a different image or can I get root on the stock boot image? What works for you?
Booting to TWRP recovery doesn't seem to work.
With fastboot I can flash both boot and recovery. However, booting to recovery remains impossible. The tablet will try, but give up, restart via the Nvidia logo and then boot to system. Should I be using a specific TWRP for the Nvidia Shield on MM - and does it matter which boot.img I use?
EDIT: Finally flashed an old TWRP 2.8.7.0 and THAT worked. That got root and removed the need for ADB.
This post has been most helpful of all:
http://nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/
Any help is very welcome!!

Probably need to add that the kernel is Buildbrain 3.10.67+
Sent from my SM-G920F using XDA-Developers mobile app

Hi, I've got some problems to, I cant get into TWRP recovery to flash the superSU.
I even went back to stock v1.1.1 and then udated to a fresh copy of 1.2.0.
Then I followed step by step the instructions from http://nvidiashieldzone.com/shield-tablet/shield-tablet-k1/root-shield-tablet-v1-marshmallow-2/
but I'm still, unable to enter TWRP recovery? (twrp-multirom-20160410-UNOFFICIAL-shieldtablet_m)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (14936 KB)...
OKAY [ 0.720s]
writing 'recovery'...
OKAY [ 0.624s]
finished. total time: 1.344s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery
cannot load 'recovery': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>
What can be the problem???
Is there an other recovery available (TWRP-CWM---)?

ierkens said:
Hi, I've got some problems to, I cant get into TWRP recovery to flash the superSU.
I even went back to stock v1.1.1 and then udated to a fresh copy of 1.2.0.
Then I followed step by step the instructions from http://nvidiashieldzone.com/shield-tablet/shield-tablet-k1/root-shield-tablet-v1-marshmallow-2/
but I'm still, unable to enter TWRP recovery? (twrp-multirom-20160410-UNOFFICIAL-shieldtablet_m)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (14936 KB)...
OKAY [ 0.720s]
writing 'recovery'...
OKAY [ 0.624s]
finished. total time: 1.344s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery
cannot load 'recovery': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>
1- What can be the problem???
2- Is there an other recovery available (TWRP-CWM---)?
Click to expand...
Click to collapse
Found Answers:
1- Recovery is not flashed, don't know why but flashed romrunner 3.0.2-0 4times and rebooted directly in recovery whitout rebooting the device, that worked. :good:
2- Yes there is: [RECOVERY] [unofficial] TWRP 3.0.2-0 (2.8.7.1 for Lollipop) [2016-04-05]:good::good::fingers-crossed:

ierkens said:
Found Answers:
1- Recovery is not flashed, don't know why but flashed romrunner 3.0.2-0 4times and rebooted directly in recovery whitout rebooting the device, that worked. :good:
2- Yes there is: [RECOVERY] [unofficial] TWRP 3.0.2-0 (2.8.7.1 for Lollipop) [2016-04-05]:good::good::fingers-crossed:
Click to expand...
Click to collapse
The "fastboot boot recovery" command is trying to boot a file named recovery from your PC, that's why it wasn't found. You were using the wrong command. If you did "fastboot boot recovery.img" that would work too boot the recovery image from your PC without actually flashing recovery.
Sent from my SHIELD Tablet K1 using Tapatalk

This is as much a note to self as anyone else about what worked...
gubbe said:
ADB doesn't seem to work.
Can't connect at all using ADB. You'll say I need to update the USB drivers, but how come Fastboot works and ADB does not?
Click to expand...
Click to collapse
Alright, so ADB never worked , but fastboot did, so it's possible to just flash the right recovery with fastboot, using the latest nvidia USB drivers here: https://developer.nvidia.com/gameworksdownload.
gubbe said:
The boot.img doesn't seem to work.
Every time I flash an alternative bootloader using fastboot, Wifi disappears after the flash. The only solution seems to be to flash the stock boot. Should I be using a different image or can I get root on the stock boot image? What works for you?
Click to expand...
Click to collapse
Flashed all the back to stock using files from https://developer.nvidia.com/gameworksdownload. :crying:
gubbe said:
Booting to TWRP recovery doesn't seem to work.
With fastboot I can flash both boot and recovery. However, booting to recovery remains impossible. The tablet will try, but give up, restart via the Nvidia logo and then boot to system. Should I be using a specific TWRP for the Nvidia Shield on MM - and does it matter which boot.img I use?
Click to expand...
Click to collapse
Then used fastboot to flash the recovery mentioned here: http://nvidiashieldzone.com/download/twrp-tab-experimental/. It's v 2.8.7, but if it works who cares... Anyway, that got the recovery working and allowed for doing an "advanced wipe" of system, data, dalvik cache.
Following that I flashed the following IN ONE OPERATION without reboot: :laugh::laugh:
1) Bliss 6.3 for nVidia Shield Tablet
2) Most recent Google Apps, Pico Build
As a precaution I wiped dalvik again before first boot and THEN rebooted.
Without the advanced wipe I had all sorts of Google Play Services and Google Play Store errors.
Everything is fine now. Running on Bliss 6.3 with most recent Google Apps. So far seems faster and more responsive than the nVidia stock ROM I was using. :good::good:
This post has been most helpful of all:
http://nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/

ierkens said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery
cannot load 'recovery': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>
What can be the problem???
Click to expand...
Click to collapse
I had a look at the comments section on the guide you're using. Looks like others have had the problem you're facing. Did you try the provided tips?

Exile1975 said:
The "fastboot boot recovery" command is trying to boot a file named recovery from your PC, that's why it wasn't found. You were using the wrong command. If you did "fastboot boot recovery.img" that would work too boot the recovery image from your PC without actually flashing recovery.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Ooh-kay!!
[emoji15]
Sent from my HTC One M9 using XDA-Developers mobile app
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
gubbe said:
I had a look at the comments section on the guide you're using. Looks like others have had the problem you're facing. Did you try the provided tips?
Click to expand...
Click to collapse
Used a different recovery, problem solved..
Thanks 4 your reply.
Sent from my HTC One M9 using XDA-Developers mobile app

Razer bootloader unlock

Hi,
I'v got used Razer phone today with Oreo 8.1, tried to unlock boot but it failed. Commands I've ran so far (debug and oem unlock both on)
adb reboot bootloader
got the download mode
android bootloader interface version 11 driver from google.
fastboot -i 0x1532 devices
xxx40xxxx fastboot (xx are numbers)
then
fastboot -i 0x1532 flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
on the phone download mode words disappeared and no driver appear in the PC
also tried another root method with posted here in XDA for Oreo but still not working.
Please I need help as I bought the phone to root and enjoy it
Majed

NeverMind, used another laptop and i was able to do it... I think AMD has some usb filters or something

Help please: adb devices no u11 listed? tried many times..

reboot to bootloader mode, tried lots of way to fix it but still no device listed, tried: drivers defferent, checked tcp port 5037, kill-server, start-server, restart many times, tried with diferent windows 10 OS, and diferent computer/laptops, device ID / VID loaded to .android folder as well,
as my u11 seemed encrypted you can see my previous post:
My u11 encrypted? lost wifi and mobile signal, after restore rom, it bricked
Please check the pictures: short story first: after reset the ROM with recovery mode, the u11 can go through the encrypting screen, then it will loop and stuck in the setup screen. I didn't really encrypt my phone ever, I only had a simple...
forum.xda-developers.com
But when I use command: adb devices
nothing listed, this what is look like:
-------------------------------------------------------------------------
C:\Windows\system32>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
--------------------------------------------------------------

Can I actually use adb with bootloader mode of u11? As I cannot boot into my android OS which stuck in setup screen with no wifi no mobile signal and I cannot switch android to debug mode, the only thing I can do: boot to bootloader/fast boot mode, but adb devices cannot find it. I want to keep my original ROM

Do you see you phone with fastboot devices ?

Thank you so much! sure I can see the device now with fastboot!
but i got this now: (should I unlock u11?)
C:\Windows\system32>htc-fastboot erase persist
erasing 'persist'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s

Thank you so much! sure I can see the device now with fastboot!
but i got this now: (should I unlock u11?)
C:\Windows\system32>htc-fastboot erase persist
erasing 'persist'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s
------------------------------------------------------
My u11 is encrypted by some reason, no wifi no mobile signal, stuck in setup mode,
do you still have chance to get the original rom back or i have to flash a downloaded rom now?
thanks

Having trouble unlocking bootloader

PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem unlock
< waiting for device >
Android v10, Developer options are enabled, USB debugging as well as OEM unlocking, I have installed the USB drivers, i follow everything as it suppose to, but i just cant pass through this step...
can you help me guys ?

mrpeev said:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem unlock
< waiting for device >
Android v10, Developer options are enabled, USB debugging as well as OEM unlocking, I have installed the USB drivers, i follow everything as it suppose to, but i just cant pass through this step...
can you help me guys ?
Click to expand...
Click to collapse
Update to latest ADB and Fastboot from here:
https://developer.android.com/studio#command-tools
The ones that come with Minimal ADB and Fastboot are incompatible/obsolete.

greyblue9 said:
Update to latest ADB and Fastboot from here:
https://developer.android.com/studio#command-tools
The ones that come with Minimal ADB and Fastboot are incompatible/obsolete.
Click to expand...
Click to collapse
that worked, Ive installed pixel experience ROM and its working, as long as i dont restart the device...then it goes bootloop in twrp lol