Database Users

[Q] Unlock without wipe?

Has anyone figured out a way to unlock this device without having it do a factory reset?
What's the reason for the wipe anyways? I don't understand why this has to happen.

I guess it's impossible, but you can try Carbon Backup to backup your apps+data, it works without root
Sent from my Nexus 7 running Android 4.2.2

I actually have root and titanium backup but it's a pain to backup and restore. Would be nice if the device simply didn't rest itself when unlocked.

Maybe one day the app "Boot Unlocker for Nexus Devices" will support the Nexus 7
Sent from my SK17i running Android 4.1.2

Yeah, something like that is what I'm looking for.
I wonder what method the app uses to unlock other devices.

xxbeanxx said:
I actually have root and titanium backup but it's a pain to backup and restore. Would be nice if the device simply didn't rest itself when unlocked.
Click to expand...
Click to collapse
Weird question how did you root without unlocking bootloader? and why do you need to unlock the bootloader, if you're already rooted?

clockcycle said:
Weird question how did you root without unlocking bootloader? and why do you need to unlock the bootloader, if you're already rooted?
Click to expand...
Click to collapse
I relocked after flashing su (for security reasons). I don't have a need to unlock again right now but wanted to know if it was possible just in case I wanted to flash a zip in the future.

xxbeanxx said:
I relocked after flashing su (for security reasons). I don't have a need to unlock again right now but wanted to know if it was possible just in case I wanted to flash a zip in the future.
Click to expand...
Click to collapse
Ok, makes sense. I did the same thing and couldn't find a way either, and just went at it the same way as initially, wiping.

I've heard that the rationale for forcing a memory wipe when unlocking the bootloader was to protect your data in case your device fell into the wrong hands. If someone steals it and can't get past your lockscreen, they won't be able to get to your device's memory via usb. They can try unlocking the bootloader, but that will wipe the device's memory clean. The thief will be able to use your device but the data is safe. If the bootloader is unlocked, the thief can plug in the phone or tablet, go mucking around in your files, and steal your identity as well as your device.
This is why using a device with an unlocked bootloader is not as safe as using one that is locked. It is also why a new security feature was added to 4.2.2 and adb, although I haven't plugged in my Nexus 7 to find out how it works.

getoffmylawn said:
I've heard that the rationale for forcing a memory wipe when unlocking the bootloader was to protect your data in case your device fell into the wrong hands. If someone steals it and can't get past your lockscreen, they won't be able to get to your device's memory via usb. They can try unlocking the bootloader, but that will wipe the device's memory clean. The thief will be able to use your device but the data is safe. If the bootloader is unlocked, the thief can plug in the phone or tablet, go mucking around in your files, and steal your identity as well as your device.
This is why using a device with an unlocked bootloader is not as safe as using one that is locked. It is also why a new security feature was added to 4.2.2 and adb, although I haven't plugged in my Nexus 7 to find out how it works.
Click to expand...
Click to collapse
Thats a good reason.
4.2.2 on my nexus 4, when I plugged it into the pc, a box poped up on the n4 asking perrmission showing the pc's key..

FWIW, I found this.. http://forum.xda-developers.com/showthread.php?t=2068207

Just an FYI for unlocking the bootloader

Two things first while this has been said already make sure to go into developer settings and enable the OEM unlock option. Secondly it's going to have a screen saying erasing when you reboot after unlock. It will take a while and you'll want to reboot thinking its stuck but it seems like encryption makes the wipe take like 5 or 6 minutes. YMMV but I accidentally let it download stuff before I unlocked the bootloader so I'm sure that made it take longer.

hungmung said:
Two things first while this has been said already make sure to go into developer settings and enable the OEM unlock option. Secondly it's going to have a screen saying erasing when you reboot after unlock. It will take a while and you'll want to reboot thinking its stuck but it seems like encryption makes the wipe take like 5 or 6 minutes. YMMV but I accidentally let it download stuff before I unlocked the bootloader so I'm sure that made it take longer.
Click to expand...
Click to collapse
Thanks for this.
I am hesitant to unlock the bootloader until I can confirm that it's being done safely by many...already saw someone brick their device by not checking OEM unlock and/or rebooting too soon!
However, I'd like to get it done so I don't have to worry about erasing my data again!

i thought it was supposed to be checked to begin with (as opposed to the N9 which was not checked)
http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
it's old news, but thanks for the reminder

For what it's worth, when I unlocked the bootloader on my Moto X, the factory reset portion seemed to take a very long time there, too. Not sure if it was because there was no status updates on the screen like other methods show (SBF shows each step, from recovery shows steps in yellow (from what I remember), etc). I think it -feels- like it takes longer because of that. It just said "wiping" or "resetting" or something like that when I did it.

This is how I unlocked the BL on my N6,
enable developer options
make sure enable oem unlock is checked
adb reboot bootloader
fastboot oem unlock
once this happens the phone will reboot, for me it didnt wipe data automatically, it just put me at the recovery screen (stock) if this happens you need to wipe data manually or the phone will not boot.
power + vol up then choose wipe data/factory reset
wait for it to complete will take about 5 minutes
reboot system

djkinetic said:
This is how I unlocked the BL on my N6,
enable developer options
make sure enable oem unlock is checked
adb reboot bootloader
fastboot oem unlock
once this happens the phone will reboot, for me it didnt wipe data automatically, it just put me at the recovery screen (stock) if this happens you need to wipe data manually or the phone will not boot.
power + vol up then choose wipe data/factory reset
wait for it to complete will take about 5 minutes
reboot system
Click to expand...
Click to collapse
If you click the start option after it returns you to the bootloader screen it will wipe itself and you get the erasing message.

I'm gonna be completely stock for a couple of weeks to have a baseline of the device and 5.0 when chainfire and TWRP roll out their magic I will unlock bootloder/flash root/install custom recovery. Taking my sweet time for now

My phone actually got stuck on the android screen after it erased everything. I got scared and started looking for a factory image after 30 minutes. Google didn't release it yet so I ended up holding the power button and itnjuat rebooted fine. I thought I caught a brick before I could use the phone

sgloki77 said:
I'm gonna be completely stock for a couple of weeks to have a baseline of the device and 5.0 when chainfire and TWRP roll out their magic I will unlock bootloder/flash root/install custom recovery. Taking my sweet time for now
Click to expand...
Click to collapse
unlocking the bootloader doesn't affect performance, so why wait if you're going to root later on? seems like extra work to unlock/wipe data after using for a while.

not sure how it happened but i ran "fastboot oem unlock" even without selecting the checkbox in developer options and it still ran the process. maybe it's only necessary if you had a pin to lock your phone.

tflogic said:
not sure how it happened but i ran "fastboot oem unlock" even without selecting the checkbox in developer options and it still ran the process. maybe it's only necessary if you had a pin to lock your phone.
Click to expand...
Click to collapse
yea what checkbox are you guys talking about? for every nexus device ive ever unlocked its dev options-->enable usb debugging-->adb reboot bootloader-->fastboot oem unlock. done. are there additional steps w nexus 6?

indianajonze said:
yea what checkbox are you guys talking about? for every nexus device ive ever unlocked its dev options-->enable usb debugging-->adb reboot bootloader-->fastboot oem unlock. done. are there additional steps w nexus 6?
Click to expand...
Click to collapse
Yes, on the Nexus 6 and Nexus 9, you need to check "Enable OEM Unlock" in the developer options.
http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/

indianajonze said:
yea what checkbox are you guys talking about? for every nexus device ive ever unlocked its dev options-->enable usb debugging-->adb reboot bootloader-->fastboot oem unlock. done. are there additional steps w nexus 6?
Click to expand...
Click to collapse
There is a new option in the Developer Options menu in 5.0
http://www.droid-life.com/2014/11/0...nable-oem-unlock-option-in-developer-options/
I don't see it on my N7, but that might be because my bootloader is already unlocked.

fury683 said:
There is a new option in the Developer Options menu in 5.0
http://www.droid-life.com/2014/11/0...nable-oem-unlock-option-in-developer-options/
I don't see it on my N7, but that might be because my bootloader is already unlocked.
Click to expand...
Click to collapse
its not on my N5 with 5.0 either. must be unique to N6 and N9. interesting...

indianajonze said:
its not on my N5 with 5.0 either. must be unique to N6 and N9. interesting...
Click to expand...
Click to collapse
Is your bootloader already unlocked?

fury683 said:
Is your bootloader already unlocked?
Click to expand...
Click to collapse
sure. since the day it was born

indianajonze said:
sure. since the day it was born
Click to expand...
Click to collapse
Guessing it may not show up if the BL is already unlocked, since it wouldn't prevent anything from happening.

My "OEM unlock" was checked when I took the phone out of the box. Had no issues unlocking the bootloader or wiping data. Works like a charm with an unlocked bootloader (as a Nexus should).

Acrono said:
My "OEM unlock" was checked when I took the phone out of the box. Had no issues unlocking the bootloader or wiping data. Works like a charm with an unlocked bootloader (as a Nexus should).
Click to expand...
Click to collapse
My OEM Unlock was not checked. Received my Nexus 6 from Google Play today and installed the 191MB OTA before going into developer options.

Lucke said:
unlocking the bootloader doesn't affect performance, so why wait if you're going to root later on? seems like extra work to unlock/wipe data after using for a while.
Click to expand...
Click to collapse
I don't mind restoring data/settings after a wipe, I do that all the time when switching ROMs, and now you can restore your user apps through NFC from another device so you don't need root/tibu on the initial install
development is going to take some time to kick into gear so I will enjoy the device as a regular user , I hope xposed get support for 5.0 asap though

/!\ WARNING /!\ Do NOT relock your bootloader around the time of updating to 5.1!

Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootloader is not a good idea
Please also see the below link provided by @efrant
https://support.google.com/nexus/answer/6172890?hl=en
This goes into more detail about how google have enhanced device security with 5.1 and some other pitfalls that you may wish to avoid. This is pretty salient information, so do give it a read.

Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER. ???
Sent from my Nexus 9 using XDA Free mobile app

ChristianJay said:
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.

So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device protection a locked bootloader would serve a purpose. Preventing someone from just flashing a custom rom and keeping your device.

:thumbup:

I thought I really #$# up
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...

xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..

rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
Click to expand...
Click to collapse
Hi root,
I saw that thread yesterday ...
I thought this was already covered when the N6 came out, to get the bootloader unlocked you had to do a 1st boot of the device and ENABLE OEM Unlock, then you were good to go to get into fastboot and unlock.
The reason was google put the option there for 5.0, vice all our previous versions which had no toggle for it.
I think it was people jumping the gun and not doing that first boot, but immediately jumping into fastboot and flashing, and that caused it, yes? Because the BL wasn't unlocked, they couldn't flash the OTA and boot img ...

daijizai said:
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
Click to expand...
Click to collapse
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.

xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
kng60ft said:
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
Click to expand...
Click to collapse
There is no need to lock the device to take an OTA. You can keep it unlocked and do an ota

doitright said:
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
Click to expand...
Click to collapse
Not nonsense. Yes you need physical access to carry out the attack, but with a locked bootloader and the new precautions against unlocking and fastboot it makes locked bootloaders fairly bulletproof.
I cannot recommend unlocked bootloaders to anyone that works SCIF'd and leaves their phone in a shared box during the day, anyone that crosses international borders, or anyone whose phone might contain IP or trade secrets and could be a target of theft.
This is as much about trusting the phone afterwards as it is about protecting your data on the phone - even when encrypted.

y2whisper said:
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device detection a locked bootloader would serve a purpose.
Click to expand...
Click to collapse
Just keep it unlocked

rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootlaoder is not a good idea
Click to expand...
Click to collapse
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.

nyteryder79 said:
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
Click to expand...
Click to collapse
Thats good.

http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
This may help if you got stuck in a bootloop.

is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?

darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.

Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
should help

darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
Factory reset?
Not really the thread to ask this though.

rootSU said:
Factory reset?
Not really the thread to ask this though.
Click to expand...
Click to collapse
Thanks, and sorry

[WARNING] Do NOT lock your bootloader when on Android 5.1

The new Device Protection features of Android 5.1 on the Nexus 9 and Nexus 6 can, in certain cases, cause you to have a bootloader which can not be unlocked.
Please have a read of the following links:
https://support.google.com/nexus/answer/6172890?hl=en
http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497

What a pita
Sent from my Nexus 5 using XDA Free mobile app

i would never relock my bootloader
people unlock there bootloader for a reason
but to relock it after thats just wrong...
thats one of the things i hate about CM
they recommend you to relock your bootloader...

Agreed, why would you lock your bootloader unless sending in for repairs maybe?
But Google is really messing up the flow. The nexus 6 5.1 OTA is a mess right now but I will leave that for another thread.

Android 5.1 for Nexus 9? You must be joking.

So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?

disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
No no you can still unlock it
But if you relock it that's the problem

disturbd1 said:
So, I just purchased a Nexus 9 via the 4-hour online-only sale at Best Buy. It was $100 off, couldn't pass it up. My question is: is this likely going to be shipped in such a condition as to prevent me from permanently unlocking the bootloader? Or is a permanent lock something one must deliberately do?
Click to expand...
Click to collapse
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.

efrant said:
As USBhost said, you'll be able to unlock it. However, when you are first setting it up and are running through the set-up wizard, there will be an option to "Protect Device" or something like that. If you enable it, and re-lock the bootloader, it will put you in a situation where you can only unlock the booloader in certain situations -- and if you happen to have a bootloop with a locked bootloader, that's when you are in trouble.
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
Considering this is a tablet, hopefully I won't lose or misplace it
Thanks, guys! Glad I stumbled across this thread before the thing arrived.

Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.

doitright said:
Locking the bootloader doesn't protect you from anything. If the device leaves your physical control in a potentially hostile environment, whatever is on the system or boot partition becomes suspect, regardless of whether the bootloader is locked or unlocked.
Click to expand...
Click to collapse
Example: I have a device running a stock ROM with no encryption, the stock recovery and a lock screen password. I happen to lose my phone. What happens to the photos of me dancing to Old Time Rock & Roll in my underwear that are stored on the device? If the bootloader is unlocked, someone just plugs it into a PC, boots TWRP and pulls them off. If the bootloader is locked, there is no easy way to see or get the photos off the device.
That is all I was saying about security. Nothing to do with you leaving your device somewhere or losing it, and then finding it again. Strictly about the personal content on the device.

efrant said:
EDIT: On Nexus devices, I personally unlock the bootloader as soon as I take it out of the box, without first booting into Android, and then leave it unlocked. But of course, you give up some security by doing that.
Click to expand...
Click to collapse
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?

bailyc said:
I thought Lollipop always requires you to go in and check the Enable OEM Unlock box? Or is that not true if you never booted into Android even once?
Click to expand...
Click to collapse
If you have never booted into Android, then you don't need to check that setting. As I said, that's the way I did it on my N6: take out of box -> charge -> boot directly into bootloader -> "fastboot oem unlock". No other steps required if you don't boot into Android first.

can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302

lilliput222 said:
can i use this guide for safely relock my Bl on Nexus 9 ..... Relocking coz of RMA and warranty purpose as bought from amazon India instead of Play Store
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Click to expand...
Click to collapse
Yes, that should work for the N9 as well.

The bootloader on my Nexus 9 Android 5.1.1 is locked forever due to my mistake
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to check "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9

quekl84 said:
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
Not possible. You will have to return it to HTC for repair or replacement.

quekl84 said:
Short backstory:
- I wanted to install the Android M developer Preview for the Nexus 9 but I forgot to uncheck "Enable OEM unlock" in developer options (worst mistake).
- I used adb command to flash the new image but failed somehow
- I carelessly type # fastboot oem lock
- I tried to factory reset from bootloader to bring it back to Stock. Now it couldn't factory reset and my Nexus 9 hangs in a nice boot loop.
- I try # fastboot oem unlock but failed with permission denied error
I tried some ways to save my device but no hopes
- I used Nexus Root Tookit to unlock bootloader or restore image with force mode but failed,
- I follow instruction in HTC dev forum to get identifier token in order to receive your unlock code binary file but failed
- Unluckily, I don't installed any custom recovery.
Please help if you know a way unlock the bootloader or flash the factory ROM to save the nexus 9
Click to expand...
Click to collapse
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol

cobyman7035 said:
u mean u forgot to CHECK to box to allow oem UNLOCK? im confused lol
Click to expand...
Click to collapse
Yes, I forgot to check the box to allow oem UNLOCK. And now my device is locked forever.

A quick question: A lot of N9 ROMs require flashing an updated bootloader from the factory image. Aren't these bootloaders locked by default? Can we flash a factory bootloader over a custom ROM?
It seems that we might bork our Nexus 9s if we flash a locked bootloader in.

[GUIDE] [HOW TO] Safely re-lock bootloader on Android 5.1

This guide is for the safe procedure for re-locking your bootloader with the new security features of Android 5.1 on the Nexus 6
The purpose of re-locking your bootloader should solely be used for RMA or resale of your device. Also if you have flashed a factory image and want the added security of a locked bootloader. Or possibly it is required by your employer. If you're required by your employer, then I suggest you reconsider unlocking in the first place. If you're returning to stock, to simply fix problems on your device, then I also strongly suggest leaving the bootloader unlocked. To put it in simple terms, if you want to keep a custom recovery and ROM, mod, root, etc, then leave your bootloader unlocked. Re-locking the bootloader on the Nexus 6 will cause your device to be wiped.
Please read this post by @efrant for more clarification:
http://forum.xda-developers.com/showthread.php?p=60128929
Thanks @efrant @cam30era @rootSU @clairez for collaboration and advice.
This is based on a 100% stock, encrypted, un-modded Nexus 6
Due to significant security changes in Android 5.1, there are some specific steps that must be taken in order to safely re-lock your bootloader during and after installing a factory image.
WARNING! These steps are confirmed working but there is still risk involved. If you do not ABSOLUTELY need to re-lock then I strongly suggest leaving the bootloader unlocked.
FOLLOWING THESE STEPS WILL WIPE YOUR DEVICE SO BACKUP YOUR DATA!
This is based on you (the user) having already read and followed instructions on downloading the factory image and having it ready to install.
STEP 1
Disable all security locks on your phone.
On your phone, go into your settings, click Security. In Screen security, click on Screen lock, enter your passcode/pin/pattern then select none.
You will get a prompt that Device protection features will no longer work. Click OK.
STEP 2
**OPTIONAL**
Thanks @gee2012
This step is optional because successful installation of the factory image will remove this info anyway.
Remove your Google account.
In settings, click Accounts, click Google then click on your account name. (your gmail address)
Click the 3 dot menu button in top right of screen and select Remove account. You will get a prompt That this will delete all messages, contacts and other data from your phone. Click REMOVE ACCOUNT.
STEP 3
This step is optional and may or may not be needed but I recommend doing this.
Preform a factory reset from your phone settings.
Open settings and click on Backup & reset. Click Factory data reset.
You will receive a prompt stating that this will erase all data from your phone's internal storage, click RESET PHONE.
The reset takes quite a while to complete, approximately 10 to 15 or more minutes for a 32gb model and 20 minutes or more for a 64gb model, so BE PATIENT!
Your phone will reboot when completed.
STEP 4
IMPORTANT!!
When your phone reboots, you will have to skip all account set up and ABSOLUTELY do not set any security features up. Skip EVERYTHING!
Go to settings and enable Developer options. (About phone>tap build number 7 times)
Once you have developer options enabled, enable USB Debugging and tick the box to allow OEM unlock.
I suggest preforming a reboot here to verify that OEM unlock sticks. After the reboot enter developer options to verify OEM unlock is still ticked.
If it is, we will proceed. If not, ensure you have followed the previous steps correctly. If you have and for some reason the setting won't stick, DO NOT PROCEED OR YOU MAY END UP STUCK IN A BOOT LOOP WITH NO CURRENT WAY TO FIX!
STEP 5
If setting has stuck, you are ready to unlock your bootloader and install the factory image using one of the ways outlined elsewhere in this forum.
After installation is complete, reboot to recovery and again preform a factory reset. Reboot to Android.
STEP 6
IMPORTANT!
Upon completion of factory reset from recovery and reboot to Android, it is important to follow this procedure so you may now safely lock your bootloader.
SKIP ALL ACCOUNT AND SECURITY SET UP AGAIN! Go to settings and enable developer options again. Enable USB debugging and tick allow OEM unlock.
Again, I recommend a reboot at this point to verify the settings stick.
Use the button combo or ADB to reboot to bootloader.
Use the command fastboot oem lock
Your device will wipe again and reboot.
CONGRATULATIONS! You now have a locked bootloader and you may proceed to restore your phone.
See here for info from Google about the new security features:
https://support.google.com/nexus/answer/6172890?hl=en
Thanks @efrant for finding this link.
Thanks also to all of those who helped to confirm this process works consistently.
Thanks to @clairez for this thread: http://forum.xda-developers.com/nexus-6/help/update-to-5-1-lock-bootloader-t3058480
*Disclamer*
I am not responsible if your device bricks, loops or causes mass world hysteria.

*How to prepare your Nexus 6 for resale*
Since the onset of Android 5.1, there are some specific steps needed to ensure you can sell your device and not have the seller need your Google password when they receive your device. Please read this guide provided by @PatimusXPrime
http://forum.xda-developers.com/showpost.php?p=60455167&postcount=43
TWRP RECOVERY INSTALLED ONLY
The following info is for users who have TWRP installed and are stuck in bootloop (soft brick) after wiping OS with a locked bootloader.
Credit to this thread:
Thanks @ixa20
http://forum.xda-developers.com/showthread.php?t=3053783
STEP 1
Boot into bootloader.
STEP 2
Use fastboot and issue the commands:
fastboot format userdata
fastboot format cache
This should allow you to boot back into TWRP.
Flash a ROM and get up and running.
Unlock your bootloader and leave it that way.
Thanks also to @rootSU for posting this solution many, MANY times.

I hear a lot about locking the boot loader, but what exactly am I missing out on in terms of security with an unlocked boot loader, and rooted

productofusa said:
I hear a lot about locking the boot loader, but what exactly am I missing out on in terms of security with an unlocked boot loader, and rooted
Click to expand...
Click to collapse
I think, primarily, if you are unencrypted you run the risk of your data being compromised if your phone is lost or stolen. Plus, the new security features are not proven to work 100% when bootloader is unlocked. Simply by rooting, you've opened your device to be more vulnerable to malicious attacks. I'm sure you already know that.

Evolution_Freak said:
I think, primarily, if you are unencrypted you run the risk of your data being compromised if your phone is lost or stolen. Plus, the new security features are not proven to work 100% when bootloader is unlocked. Simply by rooting, you've opened your device to be more vulnerable to malicious attacks. I'm sure you already know that.
Click to expand...
Click to collapse
I see, nothing I wasn't already aware of! It seems that a significant amount of people that are used to an unlocked rooted handset are quick to jump on the relock the bootloader omg security bandwagon regardless of the consequences. Having said that thanks to folks such as yourself most of the kinks seem to be worked out at this point.
Thanks

Okay, so I'm new to the whole unlocking/flashing thing.... I bought a nexus 6 from Verizon which obviously came with 5.1 out of the box. I was using stock with my google account attached and a pin lock. I successfully unlocked by bootloader and rooted with twrp and the nexus toolkit. I have also since flashed chroma. Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!

Cannibal Oxen said:
Okay, so I'm new to the whole unlocking/flashing thing.... I bought a nexus 6 from Verizon which obviously came with 5.1 out of the box. I was using stock with my google account attached and a pin lock. I successfully unlocked by bootloader and rooted with twrp and the nexus toolkit. I have also since flashed chroma. Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Click to expand...
Click to collapse
The first post explains how to lock the bootloader safely. If you're going g back to stock, simply follow the steps

Cannibal Oxen said:
Okay, so I'm new to the whole unlocking/flashing thing.... I bought a nexus 6 from Verizon which obviously came with 5.1 out of the box. I was using stock with my google account attached and a pin lock. I successfully unlocked by bootloader and rooted with twrp and the nexus toolkit. I have also since flashed chroma. Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Click to expand...
Click to collapse
No, not at all. You can flash a factory image and return to stock at anytime. However, if you plan on flashing ROMs again, there's no need to relock the bootloader. For instance, if you wanted to return to stock to say, get an OTA, the bootloader being unlocked wouldn't affect that negatively.
If you did desire to relock, following this guide, as far as disabling the security and Google account, you should be able to relock. The important thing is making sure that pesky "allow OEM unlock" option remains checked after a reboot.

Cannibal Oxen said:
Am I to understand that I can not ever go back to unrooted stock and locked booloader, now?
I'm really sorry for what is probably a stupid noob question, but I'm really paranoid now. TIA!!
Click to expand...
Click to collapse
You can go back to stock. And then, subsequently relock the bootloader.
And the question is not "stupid". Noob questions are encouraged here. That's how you learn.

rootSU said:
The first post explains how to lock the bootloader safely. If you're going g back to stock, simply follow the steps
Click to expand...
Click to collapse
Fair enough. The part that confused me was the first five steps appear to address steps required to unlock the bootloader. I was afraid since I already unlocked mine without first disabling security and removing my account that it would somehow preclude me from ever being able to relock the bootloader should that need ever arise in the future.
I really appreciate the help!

Yeah, I learned my lesson, DON'T PLAY WITH LOCKED BOOTLOADERS ON THIS DEVICE, EVER!
I had a locked bootloader, and no System (I had wiped it accidentally).
Luckily though I had the sense to keep TWRP installed, but I couldn't boot to it, it was just bootlooping to the TWRP splash screen.
I thought I had just lost a $650 investment, but here's what I did:
Boot to bootloader, then
Code:
fastboot erase cache
fastboot erase userdata
Then I could boot to TWRP! So I
Code:
adb push (ChromaOS zip here) /sdcard/
But when I tried to flash the Data and Cache partitions kept giving me errors, I couldn't flash anything!
I went to sleep (or tried to sleep, but couldn't) I was panicking!
When I woke up I tried one more thing:
From bootloader I did
Code:
fastboot format cache
fastboot format userdata
(Notice FORMAT instead of erase!)
I booted into TWRP and was able to flash ChromaOS, I was able to enable OEM Unlock, and flashed the full Factory Image, completely back to stock.
I booted once with unlocked bootloader to verify it was working, then locked it.
If I had the stock recovery, I would've had a $650 paperweight.
DO NOT MESS AROUND WITH LOCKED BOOTLOADERS! DON'T RISK IT!

gorei23 said:
Yeah, I learned my lesson, DON'T PLAY WITH LOCKED BOOTLOADERS ON THIS DEVICE, EVER!
I had a locked bootloader, and no System (I had wiped it accidentally).
Luckily though I had the sense to keep TWRP installed, but I couldn't boot to it, it was just bootlooping to the TWRP splash screen.
I thought I had just lost a $650 investment, but here's what I did:
Boot to bootloader, then
Code:
fastboot erase cache
fastboot erase userdata
Then I could boot to TWRP! So I
Code:
adb push (ChromaOS zip here) /sdcard/
But when I tried to flash the Data and Cache partitions kept giving me errors, I couldn't flash anything!
I went to sleep (or tried to sleep, but couldn't) I was panicking!
When I woke up I tried one more thing:
From bootloader I did
Code:
fastboot format cache
fastboot format userdata
(Notice FORMAT instead of erase!)
I booted into TWRP and was able to flash ChromaOS, I was able to enable OEM Unlock, and flashed the full Factory Image, completely back to stock.
I booted once with unlocked bootloader to verify it was working, then locked it.
If I had the stock recovery, I would've had a $650 paperweight.
DO NOT MESS AROUND WITH LOCKED BOOTLOADERS! DON'T RISK IT!
Click to expand...
Click to collapse
With the method I've outlined and personally tried, it can be safely done. The security settings are the issue and a safe way around that has been found.

Evolution_Freak said:
With the method I've outlined and personally tried, it can be safely done. The security settings are the issue and a safe way around that has been found.
Click to expand...
Click to collapse
I know, I'm just saying don't play around with it, if you're going to relock make sure that you KNOW it will work.

Can confirm that the outlined info here works flawlessly

I used this process to re-lock my phone after unlocking in the fastboot-enabled upgrade from OTA 5.1 "D" to stock 5.1 "E" an hour ago.
The easy part was unlocking/locking/rebooting in the correct order - the harrowing part was when my fastboot update of the radio failed, after which I figured out it was a transient USB issue with my system, so rebooted Windows and then everything went reasonably close to plan.
So, now I'm on "E" and with a locked bootloader (i.e., stock for Verizon). I'll be experimenting with custom ROMs after settling in with this for a bit, but wanted to test out VoLTE and other things before going the custom route.
Thanks again for this guide.
- ooofest

ooofest said:
I used this process to re-lock my phone after unlocking in the fastboot-enabled upgrade from OTA 5.1 "D" to stock 5.1 "E" an hour ago.
The easy part was unlocking/locking/rebooting in the correct order - the harrowing part was when my fastboot update of the radio failed, after which I figured out it was a transient USB issue with my system, so rebooted Windows and then everything went reasonably close to plan.
So, now I'm on "E" and with a locked bootloader (i.e., stock for Verizon). I'll be experimenting with custom ROMs after settling in with this for a bit, but wanted to test out VoLTE and other things before going the custom route.
Thanks again for this guide.
- ooofest
Click to expand...
Click to collapse
Word of caution, don't flash stuff with a locked bootloader. If you get a bad flash and you can't boot, you'll be screwed.

Doesn't the setting in developer optionsto allow OEM unlock of the bootloader reset every boot on the new firmware? I know mine does on meanpop and chroma both 5.1 roms
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2

pwned3 said:
Doesn't the setting in developer optionsto allow OEM unlock of the bootloader reset every boot on the new firmware? I know mine does on meanpop and chroma both 5.1 roms
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes

pwned3 said:
Doesn't the setting in developer optionsto allow OEM unlock of the bootloader reset every boot on the new firmware? I know mine does on meanpop and chroma both 5.1 roms
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
It does if you have "Device protection" enabled. If you do a factory reset and, while you are running through the set up wizard, do not enable "Device protection", then the " Allow OEM unlock" setting should stick.
Sent from my Nexus 6 using Tapatalk

rootSU said:
Word of caution, don't flash stuff with a locked bootloader. If you get a bad flash and you can't boot, you'll be screwed.
Click to expand...
Click to collapse
Before attempting to upgrade the stock level or going custom, I was planning to run through at least steps 1-4 again to enable me to safely unlock.
Or, do I only need to tick OEM Unlock, adb into stock recovery and then fastboot oem unlock without going through the suggested factory data reset step?
- ooofest