Database Develop

[REF][GUIDE][11/03/2012] Unlocking the Bootloader

-This guide is going to help you with step-by-step instructions that will get you an unlocked bootloader on your Nexus 4.
-Keep in mind that unlocking the bootloader will erase all the data on your phone (every single thing, including internal storage), hence it is preferable to unlock the bootloader when the phone is new, as then you don’t have to go through the hassle of re-installing everything.
Compatibility
This guide is applicable only for the LG Nexus 4. Do not try this on any other device.
Warning!
The methods and procedures discussed here are considered risky and you should not attempt anything if you don’t know completely what it is. If any damage occurs to your device, I won’t be held liable.
How to Unlock Bootloader on Nexus 4
1. Backup everything on your phone, including the data on the internal storage, as unlocking the bootloader will erase every single thing on the phone.
2. Download and install the Android SDK → from here. This will install the necessary drivers for the phone on your computer. ( The drivers for your phone can be installed manually by other methods too, they are mandatory ) For the fastboot driver to install (and for fastboot commands to work), your device must be booted in fastboot mode.
3. Download Fastboot, which will be used for unlocking the bootloader.
Download Fastboot here .
4. Extract the Fastboot.zip file on your computer to get a folder named Fastboot with four files inside it. To keep things easy, extract the Fastboot folder to your C: drive.
5. Turn off your Nexus 4. Then, boot into fastboot mode by holding down the Volume down and Power buttons together till the screen turns on and shows “Start” written in big green letters.
6. Then, connect your Nexus 4 to the computer with your USB cable, then wait for Windows to finish installing the drivers (drivers will be installed only the first time). For reliability, ensure that you use a USB port at the back if you are using a desktop computer, as the front panel ports can be loose and cause problems.
7. Click on Start menu » All Programs » Accessories » right-click on Command Prompt and click on Run as administrator. If you are using Windows 8, this can be done by right-clicking on the extreme bottom left corner of the taskbar, then selecting “Command Prompt (admin)”
8. Now, perform the following steps in the command prompt to unlock the bootloader (check the screenshot after step 8.3 for reference)
8.1. Navigate to the Fastboot folder which you obtained in step 4. For example, if the Fastboot folder is in drive C on your computer, enter cd C:\Fastboot in command prompt (and press Enter) to navigate to the folder.
8.2. Then, enter fastboot devices. If your Nexus 4 has been detected properly, you will see a device ID show up in command prompt. If nothing comes up, make sure you have installed the drivers (step 2).
8.3. Finally, to unlock the bootloader, enter fastboot oem unlock in command prompt. You will get a prompt on the phone asking whether you want to unlock the bootloader. Just select Yes. Remember that this will wipe all your data, so make sure you took a backup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9. The phone will then reboot, and once it starts up, you can set up your phone.
10. To re-lock the bootloader, simply follow the entire procedure again from step 5 to 8, but in step 8.3, enter fastboot oem lock. This will re-lock the bootloader.
The bootloader on your Nexus 4 is now unlocked, and you can start installing custom ROMs and make other modifications to the phone. Have fun!
SOURCE

. . .anticpating the release date for purchasing . .

TheDarkDefender said:
-This guide is going to help you with step-by-step instructions that will get you an unlocked bootloader on your Nexus 4.
-Keep in mind that unlocking the bootloader will erase all the data on your phone (every single thing, including internal storage), hence it is preferable to unlock the bootloader when the phone is new, as then you don’t have to go through the hassle of re-installing everything.
Compatibility
This guide is applicable only for the LG Nexus 4. Do not try this on any other device.
Warning!
The methods and procedures discussed here are considered risky and you should not attempt anything if you don’t know completely what it is. If any damage occurs to your device, I won’t be held liable.
How to Unlock Bootloader on Nexus 4
1.Backup everything on your phone, including the data on the internal storage, as unlocking the bootloader will erase every single thing on the phone.
2.Download and install the Android SDK → from here. This will install the necessary drivers for the phone on your computer.
3.Download Fastboot, which will be used for unlocking the bootloader.
Download Fastboot here
4.Extract the Fastboot.zip file on your computer to get a folder named Fastboot with four files inside it. To keep things easy, extract the Fastboot folder to your C: drive.
5.Turn off your Nexus 4. Then, boot into fastboot mode by holding down the Volume down and Power buttons together till the screen turns on and shows “Start” written in big green letters.
6.Then, connect your Nexus 4 to the computer with your USB cable, then wait for Windows to finish installing the drivers (drivers will be installed only the first time). For reliability, ensure that you use a USB port at the back if you are using a desktop computer, as the front panel ports can be loose and cause problems.
7.Click on Start menu » All Programs » Accessories » right-click on Command Prompt and click on Run as administrator. If you are using Windows 8, this can be done by right-clicking on the extreme bottom left corner of the taskbar, then selecting “Command Prompt (admin)”
8.Now, perform the following steps in the command prompt to unlock the bootloader (check the screenshot after step 8.3 for reference)
8.1.Navigate to the Fastboot folder which you obtained in step 4. For example, if the Fastboot folder is in drive C on your computer, enter cd C:\Fastboot in command prompt (and press Enter) to navigate to the folder.
8.2Then, enter fastboot devices. If your Nexus 4 has been detected properly, you will see a device ID show up in command prompt. If nothing comes up, make sure you have installed the drivers (step 2).
8.3Finally, to unlock the bootloader, enter fastboot oem unlock in command prompt. You will get a prompt on the phone asking whether you want to unlock the bootloader. Just select Yes. Remember that this will wipe all your data, so make sure you took a backup.
9.The phone will then reboot, and once it starts up, you can set up your phone.
10.To re-lock the bootloader, simply follow the entire procedure again from step 5 to 8, but in step 8.3, enter fastboot oem lock. This will re-lock the bootloader.
The bootloader on your Nexus 4 is now unlocked, and you can start installing custom ROMs and make other modifications to the phone. Have fun!
SOURCE
Click to expand...
Click to collapse
Exact same as Nexus S and GNex: Go to bootloader, run "fastboot oem unlock"

Waiting to get my hands on the new Nexus 4. I'll be back soon. \m/
Sent from my GT-N7000 using xda premium

Guides go in the "General" section

jacklebott said:
Guides go in the "General" section
Click to expand...
Click to collapse
what? this is development related. I did check a few other device forums before I posted here. Guides like rooting,unlocking,etc. always are in the dev section. Let the moderator decide that.

this is awesome, but any way for a mac version?
thanks

I'm going to be doing this as soon as I get my N4. Hopefully they get sold out so I can wait a few days and CM will be released so I won't have to worry about setting everything up coming from stock

killman2659 said:
I'm going to be doing this as soon as I get my N4. Hopefully they get sold out so I can wait a few days and CM will be released so I won't have to worry about setting everything up coming from stock
Click to expand...
Click to collapse
How can you be sure that the CM devs got their phones? I don't think they have special channels do they?
On a separate note,
Awesome. First thing to do when I get that thing delivered. (and hopefully don't brick it.)

Correct me if I'm wrong, but you can root without unlocking the bootloader, right? If so, why the need?

eep2378 said:
Correct me if I'm wrong, but you can root without unlocking the bootloader, right? If so, why the need?
Click to expand...
Click to collapse
Only if the security isn't good enough.

FISKER_Q said:
Only if the security isn't good enough.
Click to expand...
Click to collapse
An example being.....? I guess I'm just looking for clarification. Why not just root then flash custom roms, kernels, etc? I've never owned a Nexus device so never really needed to unlock bootloader.

eep2378 said:
An example being.....? I guess I'm just looking for clarification. Why not just root then flash custom roms, kernels, etc? I've never owned a Nexus device so never really needed to unlock bootloader.
Click to expand...
Click to collapse
To get root you need root access, this does not come standard with Android, therefor the only supported way to get root access is by unlocking the bootloader, flashing an insecure boot image and installing the superuser files manually. A locked bootloader should prevent flashing of the insecure boot image, and Linux should prevent unauthorized users from becoming root, in the case of Android that means everybody.
However that is of course far from the reality, there are various vulnerabilities in the Linux Kernel and Android that can allow elevation which in turn then allows installation of the superuser binaries and the superuser android app. That in turn will usually allow flashing of custom recoveries, but a properly locked/secure bootloader can actually prevent changes to those partitions regardless of root access, i believe there's been a few of such devices in the past.

That's what I figured. Thanks. My current device(s2) there was no need to unlock bootloader to gain root access.

This should be stickied.

Ajfink said:
This should be stickied.
Click to expand...
Click to collapse
I have requested the moderator. I haven't received a reply yet.

What do you suggest I backup with? I thought a full nandroid backup could only be done once rooted?
Sent from my Galaxy Nexus using xda premium

*** Please remove***

TheDarkDefender said:
well..for starters,you could use titanium backup. And you can take a nand backup after rooting,which doesn't require unlocking.
Click to expand...
Click to collapse
That post is confusing since you need to be unlocked to gain root.
Sent from my Galaxy Nexus using Tapatalk 2

*** Disregard ***

Official bootloader unlock procedure from LG AND the one that works for everyone ;)

I just checked my emails and saw a reply from LG, containing the official unlocking procedure
alright, so here you go:
Requirements
- Linux: no drivers, only adb and fastboot (Linux is preferable, because drivers can't mess something up I've used Xubuntu 12.10 BTW)
- Windows: all drivers (including fastboot drivers) installed and functioning
- a working and updated ADB (for installing ADB, search for tuts here on xda )
- a unlockable firmware which is flashed several hours before trying to unlock the bootloader (and also being connected to the network)
- be willing to recycle all your warranty papers
- and most important: a brain with the ability to read
The Steps
1) charge your phone to 100% (not mentioned by LG, but it helped for me)
2) connect your phone in LG software mode (every mode with an activated adb should work, too)
3) if you have the path to your adb defined, then goto 3a). if not, then goto 3b)
3a) open a terminal and type
Code:
adb reboot oem-unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3b) open a terminal and type
Code:
cd ~/android-sdk/platform-tools
in Linux or
Code:
cd C:\...
on windows (if you've installed the android-sdk in your home directory under "android-sdk". if not, change it to the directory you've installed it)
then type
Code:
adb reboot oem-unlock
4) now you should see this on your phone:
do i wanna unlock it? of course i do so press the vol + button ATTENTION: there is no further warning, your whole /data/ partition will be formatted!!!
5) now you should see this, and your BL is unlocked and your /data/ partition is wiped
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
Some people still think that
Code:
adb reboot bootloader
fastboot oem unlock
is the right command, but guess what: it isn't so please don't use it
Please follow below directions to unlock bootloader.
1. Turn on the phone with SIM card, and wait for connection to the real network.
2. Wait for couple of hours.
3. Connect your handset to local PC with USB cable.
4. Enter "adb reboot oem-unlock" in DOS command window.
5. Reboot handset and you can see the bootloader unlock guide on your phone.
6-1. If you press volume up key, handset is bootloader unlock status.
You can download custom image using fastboot command.
6-2 If you press power on key, user doesnot accept unlock bootlaoder and handset normally power on.
Click to expand...
Click to collapse
so this was the official way now we're gonna take a look into the way, that can unlock every bootloader (at least we've heard nothing opposite )
download this attatched BL_unlock file and extract it
execute the BL-unlock.bat
your bootloader is now unlocked
so what it does:
it copys the calue of the fuse "odm_reserved" to a temporary folder in /data/local
changes the value to an "unlocked" one
and it pushes the changed value back to the fuse
Be aware, that whatever you do, you do it on your own responsibility. I am not responsible for any damage that might occur.
Also keep in mind, that there is no way to relock it. So think before doing anything.

No matter which version?

I asked for the official unlock method, and lg said that only euro-open would be unlockable. But i guess it will work on some other firmwares too.
Sent from my LG-P880 using xda premium

Ask about uk too? Since you got a response and I didn't. Or make a modded kdz that always flashes to eur-xxx since you have mad skills lol
Sent from my rooted P880

@non4 said:
Ask about uk too? Since you got a response and I didn't. Or make a modded kdz that always flashes to eur-xxx since you have mad skills lol
Sent from my rooted P880
Click to expand...
Click to collapse
It is not kdz that should be moded it is the kdz flash program...

There must be something which controls the device ID or IMEI, because it is no longer possible to unlock. Allways stack on [LGE_SECURITY] Unlock permission denied. I did tried already all possibility including drivers, differen adb versions, downgrading, updating e.g.

It is done on Optimus G...maybe someone could contact developer of that app.
https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=hr
Also XDA dev.
http://forum.xda-developers.com/showthread.php?t=2094696

Doesn't work on 234. Security error.

On 232.14 - Unlock Permission Denied.
So with a branding you cannot unlock your boot loader. Maybe someone can find a workaround.
i have tried it on kubuntu with ADB.

nedooo said:
It is not kdz that should be moded it is the kdz flash program...
Click to expand...
Click to collapse
Yeah I'm thinking that, maybe we can spoof the region to lg flashtool or something, if its just flags in the kdz that are read by the flashtool it shouldn't be too hard to patch. Hopefully someone can :thumbup:
Sent from my rooted P880

@non4 said:
Yeah I'm thinking that, maybe we can spoof the region to lg flashtool or something, if its just flags in the kdz that are read by the flashtool it shouldn't be too hard to patch. Hopefully someone can :thumbup:
Sent from my rooted P880
Click to expand...
Click to collapse
German, Euro Open and Czech fw have same size and I don't think so, that they released difeffrent versions for several countries. But what I think is somewhere some specific RIL's region list what BL check before unlocking process.

In cmd.exe when i enter 'adb reboot oem-unlock' it returns 'adb' is not a valid command.
Sorry for being a noob

mastershefis said:
German, Euro Open and Czech fw have same size and I don't think so, that they released difeffrent versions for several countries. But what I think is somewhere some specific RIL's region list what BL check before unlocking process.
Click to expand...
Click to collapse
that's what i'm thinking too. i guess there's the same BL on every firmware version. when trying to unlock the phone, the bootloader checks a file and "decides" then if it's unlockable or not...
Emin3ms said:
In cmd.exe when i enter 'adb reboot oem-unlock' it returns 'adb' is not a valid command.
Sorry for being a noob
Click to expand...
Click to collapse
you need to execute the command in a folder, where your adb is

Emin3ms said:
In cmd.exe when i enter 'adb reboot oem-unlock' it returns 'adb' is not a valid command.
Sorry for being a noob
Click to expand...
Click to collapse
Sounds like you havent installed it to CMD. Instead you can type cd C:/(name of adb directory) and hit enter, now adb commands should work. If you don't know what adb is do some research before messing with it
Sent from my rooted P880

I think that I need a little help with this process. I've entered the "Bootloader unlock mode" where I can see the warranty disclaimer etc, pressed "Vol Up" key to accept the terms and to continue with the process...after that, a red text appeared - "Download mode !!!". What should I do now, enter some commands in adb or...?

teddyxfire said:
I think that I need a little help with this process. I've entered the "Bootloader unlock mode" where I can see the warranty disclaimer etc, pressed "Vol Up" key to accept the terms and to continue with the process...after that, a red text appeared - "Download mode !!!". What should I do now, enter some commands in adb or...?
Click to expand...
Click to collapse
just do nothing the phone is making a factory reset and will reboot when it's done.
if it doesn't reboot itself, but says that it's done, just pull the battery and boot it manually

Ok I got 'unlock permission denied' si I cannot unlock or what i'm supposed to do?

laufersteppenwolf said:
just do nothing the phone is making a factory reset and will reboot when it's done.
if it doesn't reboot itself, but says that it's done, just pull the battery and boot it manually
Click to expand...
Click to collapse
Is it normal that this process takes a long time to complete? I think that it's been running for about 15 minutes now...

teddyxfire said:
Is it normal that this process takes a long time to complete? I think that it's been running for about 15 minutes now...
Click to expand...
Click to collapse
it was done in about 15 sec for me... try pulling the battery and boot it up. if it's unlocked, be happy, if not, try it again

Hello strange i have unlock denied message but i am on the Eur-xxx software non branded , ( polish software ) is there an option to open it ?:

motorola nexus 6 cant unlock boot loader please help

hello guys
i have moto nexus 6 xt1100 int i think its 6.0
i cant unlock boot loader i tried with SkipSoft ToolKit and with nexus root toolkit and with fastboot but not work
any help
thanx
:silly:

Questions that say effectively "I have a problem" but don't say what exactly you've done to resolve it have no chance of being answered.
Start with fastboot. What did you do?

dahawthorne said:
Questions that say effectively "I have a problem" but don't say what exactly you've done to resolve it have no chance of being answered.
Start with fastboot. What did you do?
Click to expand...
Click to collapse
hello sir
thanx to replay
i do
fastboot oem unlock
C:\Users\pc\Desktop\platform-tools>fastboot flashing unlock
...
FAILED (remote: Unknown command)
finished. total time: 0.002s
C:\Users\pc\Desktop\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\pc\Desktop\platform-tools>

The answer is in the output. You must go into Settings > Developer Options and select "Enable OEM Unlock" before you can unlock the bootloader.

i cant go to setting to open oem lock becuase pbone after upgrade ota 60 now cant open still hung google nexus screen plz hlp plz

any one help me plz

Can't you get into twrp and do a restore of made backup? Then after booting go to Developer Options and select "Enable OEM Unlock" then unlock the bootloader and leave it unlocked and leave the OEM Unlock setting in Developer options enabled.

TMG1961 said:
Can't you get into twrp and do a restore of made backup? Then after booting go to Developer Options and select "Enable OEM Unlock" then unlock the bootloader and leave it unlocked and leave the OEM Unlock setting in Developer options enabled.
Click to expand...
Click to collapse
im sorry to late phone is locked plz be fix and not open just google screen not work even after wip frm recvry

Do you have TWRP installed? If so, move a custom rom zip to the phone and flash it in TWRP. After that you can boot the phone and enable OEM unlock and proceed to unlock your phone (and then flash stock or whatever you would like to use). Your phone will be wiped (no way to save your data anyway, unless you have a previous backup), but it'll work.
If you only have stock recovery, you are out of luck and have a nice new desk ornament.

Didgeridoohan said:
Do you have TWRP installed? If so, move a custom rom zip to the phone and flash it in TWRP. After that you can boot the phone and enable OEM unlock and proceed to unlock your phone (and then flash stock or whatever you would like to use). Your phone will be wiped (no way to save your data anyway, unless you have a previous backup), but it'll work.
If you only have stock recovery, you are out of luck and have a nice new desk ornament.
Click to expand...
Click to collapse
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.

Harry44 said:
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Click to expand...
Click to collapse
True... Didn't think of that. That's a good workaround until N is released.

Harry44 said:
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Click to expand...
Click to collapse
hello sir
again so sorry to late and thanx to replay
i think no bady undrstand my prob my brop is after update ota 60 phone was like photo under long time all day just like this photo oky i do wip data factory reset from recovery not work
and i tried to flash other fimrware from all toolkit nexus but need unlock boot but cant unlock
please can u help me
im here wating every bady
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

please brothers help me

------------------------------------------------------------------------------------
Follow the Instructions on the devices screen to Unlock your BootLoader.
Enable the developer options screen by going to the settings, about screen and
clicking on build number at the bottom 7 times. Then go to developer options and
tick USB debugging so the procedure to continue.
If you get stuck on 'Waiting for USB debugging to be enabled' and have already
enabled USB debugging then just unplug/replug the usb cable and it should proceed.
IF NOTHING HAPPENS TRY PULLING DOWN THE NOTIFICATION SCREEN AT THE TOP LEFT WITH
THE DEVICE CONNECTED, THEN CLICK ON 'CONNECTED AS' AND CHANGE TO PTP MODE.
On Android 4.2 or later when you replug the usb cable after enabling usb debugging
for the first time you will get a popup asking you to authenticate your pc.
Tick 'Always allow' then click 'ok' and everything should carry on as normal.
LASTLY BEFORE STARTING, LOOK IN DEVELOPER OPTIONS IF YOU NEED TO CHECK THE
'ENABLE/ALLOW OEM UNLOCKING' OPTION TO ALLOW THE DEVICE TO BE BOOTLOADER UNLOCKED.
------------------------------------------------------------------------------------
Are you ready to start? Type y[yes] or n[no]:y
Device detected in FASTBOOT MODE
Device Serial Number is: ZX1G4244LL
When prompted, Press the 'Volume up' button to highlight Yes on the screen, then
press the 'Power' button to select it and Unlock your Bootloader. If you are
already unlocked then this will just be skipped and your device will not be wiped.
ERROR: The device cannot be bootloader unlocked in its present state
You need to enable OEM Unlock in developer options in Developer options..
Once the device has rebooted to Android do this and the Unlock routine should work

any help

Ok... You need to stop trying to unlock your bootloader. You can't.
You have a couple of options:
1 - If you have TWRP recovery installed, flash a custom rom and you'll be good to go.
2 - If you do not have a custom recovery, try flashing the N OTA from here: http://developer.android.com/preview/download-ota.html. After that, go here https://www.google.com/android/beta and enroll and then unenroll your device. Soon after (up to a day, probably) you'll get an OTA for Marshmallow.
You might want to unlock your bootloader while you're in the N preview, so you won't have to go through this again...
Edit: Reading your post again I realised you probably don't have TWRP installed, since you wouldn't have gotten that far with an OTA in that case.

C:\android>adb sideload <ota-package>
The syntax of the command is incorrect.
C:\android>

thanx to replay
but not work with me cannot read update zip:crying:

I'm assuming you know the basics here, so I'm not going to go into much detail.
Before starting, make sure you have the ADB drivers installed and have ADB in a directory on the PC.
Rename the OTA file to something simple, e.g. n6ota.zip.
Go here and follow the steps, including the Option 2 instructions here to factory reset the device.
After the factory reset, enter recovery once again and make sure the recovery is set to adb sideload mode. If you don't have it set to this mode the OTA will not install.
Open a command prompt in the directory where ADB is located and type "adb sideload [filename.zip]", replacing filename.zip with the name of the OTA file. For example, using the name I gave above for the OTA file, the command would be "adb sideload n6ota.zip".

Strephon Alkhalikoi said:
I'm assuming you know the basics here, so I'm not going to go into much detail.
Before starting, make sure you have the ADB drivers installed and have ADB in a directory on the PC.
Rename the OTA file to something simple, e.g. n6ota.zip.
Go here and follow the steps, including the Option 2 instructions here to factory reset the device.
After the factory reset, enter recovery once again and make sure the recovery is set to adb sideload mode. If you don't have it set to this mode the OTA will not install.
Open a command prompt in the directory where ADB is located and type "adb sideload [filename.zip]", replacing filename.zip with the name of the OTA file. For example, using the name I gave above for the OTA file, the command would be "adb sideload n6ota.zip".
Click to expand...
Click to collapse
apply update from ADB
not work

I'm Stuck with Nexus 6 locked Bootloader

I encrypted my phone while it was rooted and somehow I lost everything. The device magically locked the boot loader. I can't seem to find a solution.

Define everything? Can you get into recovery?
Sent from my Nexus 6 using XDA-Developers mobile app

No, I can't even get into recovery. I tried pressing power and volume +, but no lock. There is the android logo with "no command". I can't even unlock the bootloader as it appears that there is no rom so I can't go into developer option. "Device is Locked. Status Code: 2"

No guarantees, and I haven't read this thoroughly myself, but you may be lucky:
http://forum.xda-developers.com/showpost.php?p=66475726&postcount=4

The OP apparently doesn't have a recovery either, which makes flashing the Android N OTA impossible. If that is the case, the device is bricked.

Strephon Alkhalikoi said:
The OP apparently doesn't have a recovery either, which makes flashing the Android N OTA impossible. If that is the case, the device is bricked.
Click to expand...
Click to collapse
Yeah I tried on my windows using minimal adb and fastboot it keeps telling me "check 'allow OEM Unlock' in Developer Options." Now is there a way I can completely erase the phone? I remember on my oneplusone I did it before. I wiped the cache and userdata but no luck.

Thanks, Strephon - I had missed that.
Still, the OP mentions: "the android logo with "no command"".
This post:
http://forum.xda-developers.com/showpost.php?p=66467329&postcount=12
has these comments:
"Steps for solving your problem:
Connect your phone to the computer
On your phone go to the No Command screen and press the three buttons (Vol-UP + Vol-DOWN + POWER) simultaneously [it will take a couple of tries before you succeed]
You will now reach the Android Recovery screen
Select the option "Apply update through ADB"
From the computer execute "adb sideload <OTA_UPDATE_FILE_NAME>.zip"
Wait for a few minutes and you will see the update progress on adb"
Again, I haven't thought this one through (tiring day) but it's worth a shot...

If you have no system, then you've already erased the device. Give the advice by @dahawthorne a shot before calling it a day. You may actually have a recovery still, but it's just not easily accessed.

Oh No! Now it's just the android logo. Fastboot devices appears but no ADB in command prompt.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Maybe I'm misunderstanding this last post: " Fastboot devices appears"
ADB commands are for when the device is connected, switched on with USB debugging enabled. If you type "adb devices" in the CMD window you can expect to see "ZGST339FF6 device" or similar. From there you can type "adb reboot bootloader" and the phone will enter bootloader mode. [Edit: the Android image has just loaded on my screen now - that looks like stock recovery].
Once you're in bootloader mode you use fastboot commands. "adb devices" won't work. "fastboot devices" should show "ZGST339FF6 fastboot".
So are you saying that when you enter "fastboot devices" you get a response? Or nothing at all?
Have you done all the required background reading about installing drivers/ADB/fastboot and how to use them? Without actually sitting beside you watching what you're doing we're groping in the dark here...

dahawthorne said:
Maybe I'm misunderstanding this last post: " Fastboot devices appears"
ADB commands are for when the device is connected, switched on with USB debugging enabled. If you type "adb devices" in the CMD window you can expect to see "ZGST339FF6 device" or similar. From there you can type "adb reboot bootloader" and the phone will enter bootloader mode. [Edit: the Android image has just loaded on my screen now - that looks like stock recovery].
Once you're in bootloader mode you use fastboot commands. "adb devices" won't work. "fastboot devices" should show "ZGST339FF6 fastboot".
So are you saying that when you enter "fastboot devices" you get a response? Or nothing at all?
Have you done all the required background reading about installing drivers/ADB/fastboot and how to use them? Without actually sitting beside you watching what you're doing we're groping in the dark here...
Click to expand...
Click to collapse
I get a response when I enter "fastboot devices", and I see the device. However, I can't use the command fastboot oem unlock. It tells me that I have to select enable oem unlocking.

You're not reading the posts that I pointed you to. You need to download the Android N preview OTA and sideload it in that recovery screen via the CMD window. Once you've got Android N on the device you may be able to unlock the bootloader, though I've seen comments about it being greyed out. If you manage to load Android N then at least you have a working device, no? And if you do manage to unlock the bootloader then you can flash whatever ROM you like.

Problem occurs at Step. 4 "Select the option "Apply update through ADB"
I do not get the list of options.....even after Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.

dahawthorne said:
You're not reading the posts that I pointed you to. You need to download the Android N preview OTA and sideload it in that recovery screen via the CMD window. Once you've got Android N on the device you may be able to unlock the bootloader, though I've seen comments about it being greyed out. If you manage to load Android N then at least you have a working device, no? And if you do manage to unlock the bootloader then you can flash whatever ROM you like.
Click to expand...
Click to collapse
Android N Preview 2 grays out the "Enable OEM Unlock" option, while Preview 1 doesn't. The reason the Preview 1 OTA works so well to recover bricked devices is that it is a full system image, signed by Google, and flashable through the stock recovery. The Preview 2 OTA zips are most likely deltas, and thus only include the changes made to the system, rather than the complete system image.

Problem solved. Uninstall all android drivers. Reinstall new ones via google usb installer. Make sure in recovery mode you hit power, volume +, and volume - continuously until you see the options. Thank you all!

So do we understand that you have a working device?

yessiirr!

If your stuck in a locked state and want to downgrade. (Android N grays out OEM unlocking) Go to https://www.google.com/android/beta and opt in using the email your using on the phone. Then opt out. Go to settings and a OTA downgrade will be given.

Question Stuck in FastBoot Mode loop , recovery and rescue mode give boot failure, bricked?

Hi!
I got this new Pixel 7 2 weeks ago, yesterday the battery went completly discharged and now the phone starts into Fastboot mode, with the Enter Reason being boot failure. Recovery mode and rescue mode both fail to load, and just send me back to the Fastboot Mode. I alredy tried a bunch of stuff to fix it, but the phone its still OEM lock so flashing via the Google flash tool its imposible, does anyone has any idea of what can i do to save it?

Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection

t-ryder said:
Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yes, Rescue Mode fails to load, so it gives me Unable to connect the Phone

There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases

t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
No, i am going to give it a go and update on results

t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
It failed, it gives me "Bootloader is locked, can't flash." and trying to unluck the bootloader with the fastboot commands gives me FAILED (remote: 'flashing unlock is not allowed')

And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?

t-ryder said:
And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?
Click to expand...
Click to collapse
adb its disabled and entering recovery mode also fails, the phone its pretty much new, so i didn't have time do much with it.

I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...

Lughnasadh said:
I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...
Click to expand...
Click to collapse
Even trying to get into recovery mode with Pixel Flasher fails.. looks like my only option its asking for warranty and i wanted to avoid that.

Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.

41rw4lk said:
Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.
Click to expand...
Click to collapse
Unfortunately their bootloader is locked so they won't be able to switch slots via fastboot commands. Even if they were able to switch slots they would then have to flash the OS to that slot before being able to boot into that slot since you can only boot into the slot where the OS was last flashed in this circumstance.

I can't get over the fact that you can't just flash an official image on a locked bootloader. I used to be a Moto fan and that was always the good thing about them, as long as it was officially signed, locked or not you could flash the same or updated firmware. Plus if it was qualcomm, when you bricked it would go into edl mode and you could blankflash your way back.
Yet a Google device, who also develops android, you're up a creek unless you unlock your bootloader.