Related
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.
Have the same problem and try to solve it with Motorola. No luck at the moment.
lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot
simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.
rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).
You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.
beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...
You're all using the newest fastboot?
flash the factory img
edit.. nevermind, i see ive already said that
Hi, I wanted to flash the 5.1 update to my new Nexus 6.
I went all over the basic steps.
After I unlocked the bootloader I tried to flash the image with the flash-all command.
It failed, so I remembered maybe I forgot to click on USB debugging? (This confuses me because I think I shouldn't be able to unlock bootloader without this).
When I wanted to start android I locked it first, so I would unlock it afterwards and erase everything to start as new.
Whan I locked it, I could not unlock it again. I can't access Android, neither do anything else like factory reset nor Recovery Mode. I return to the bootloader as soon as I press anything.
There are red words at the top: AP Fastboot Flash Mode (Secure). Does this means anything?
Is there any way to force unlocking the bootloader? When I try it, the phone tells me to go to Developer Options but I can't access Android.
Please HELP! Is there any way to flash a rom or android again in locked state? Recovery?
Thanks for reading this and thinking about a solution! I really hope I won't be stuck forever in bootloader.
Uh oh... Were you trying to downgrade back to LRX22C from LMY47D so that you could upgrade to LMY47M, by any chance?
If so you might be fooked.
Actually no. I was trying to upgrade from 5.01 to 5.1. I'm really scared of having my Nexus 6 bricked. I can't do anything to unlock the bootloader. Maybe I could sideload a recovery? But do I need to be unlocked?
Sent from my Nexus 7 using XDA Free mobile app
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
I hope you get it sorted out. I have read SO many bad things regarding this topic and people being screwed that they cant get back in to re-unlock after relocking
toknitup420 said:
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
I think you are 100% right. I am in panic mode, thanks. I'll do it again following every step. I'll let you know.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
toknitup420 said:
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
Click to expand...
Click to collapse
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
sotnasnauj said:
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
Click to expand...
Click to collapse
Did utry fastboot devices to see your device is connected...then fastboot oem unlock?
Also, I'm the one who has found a fix for the bricked issues when it comes to locking and unlocking the boot loader...in boot loader...when u go to recovery....what happens?
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
Now I've tried everything in that thread, when I was reading I thought flashing gpt.bin would be the solution but I can't do it, I can't flash it.. It says "Unlock before flashing". Supposedly flashing gpt.bin would allow me to flash without unlocking.
My last resource is trying this on a mac, I've read you don't need drivers so maybe it is a driver thing. I HOPE SO..
Can't access adb with my pc.
You don't need adb.
sotnasnauj said:
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
Click to expand...
Click to collapse
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
jamescable said:
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
Click to expand...
Click to collapse
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
sotnasnauj said:
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
Click to expand...
Click to collapse
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
rootSU said:
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
Click to expand...
Click to collapse
I agree because op is somehow confused.....fastboot has nothing to do with develope settings USB enabled
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
hlxanthus said:
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes.
Running
Code:
fastboot format cache
fastboot format userdata
Make sure it's FORMAT not erase.
Then walk away, watch some T.V. and don't check it for a while. (Panic mode will make it seem forever, trust me! I did the same thing as you!)
Ok so, this is my first post on xda, and because my (sprint) Nexus 6 is stuck on a boot loop. When powered on, goes to googles boot animation, then says "Android is starting... optimizing apps # of 127, and then once it reaches the end, it just goes into the animation again. I somehow have usb debugging disabled, and oem locked. I have no idea what i did to cause this, but esentially I unlocked the phone, and rooted it, and then i tried to disable encryption, and thats where things went south. clearing chache does not help, niether does factory reset. Attempts at flashing factory images are fails. even the guy at sprint cant do it. Besides fixing it, my only other option is to send it in to google and get a reaplacement...for $200. PLease help me solve this issue and i will be eternally grateful :3
SorryLols said:
Ok so, this is my first post on xda, and because my (sprint) Nexus 6 is stuck on a boot loop. When powered on, goes to googles boot animation, then says "Android is starting... optimizing apps # of 127, and then once it reaches the end, it just goes into the animation again. I somehow have usb debugging disabled, and oem locked. I have no idea what i did to cause this, but esentially I unlocked the phone, and rooted it, and then i tried to disable encryption, and thats where things went south. clearing chache does not help, niether does factory reset. Attempts at flashing factory images are fails. even the guy at sprint cant do it. Besides fixing it, my only other option is to send it in to google and get a reaplacement...for $200. PLease help me solve this issue and i will be eternally grateful :3
Click to expand...
Click to collapse
OK. So...do u know how to use fastboot? If yes...do a fastboot format data and fastboot format cache..also...do u have stock recovery or twrp?
I got that bootloop when I flashed a bad boot image. Easily fixed by flashing a good one...
But, let's clarify a couple of things:
Did you relock your bootloader while flashing?
Do you have a custom recovery (TWRP)?
If the answer to both of those are "yes", you might get out of this by using these commands:
fastboot format userdata
fastboot format cache
This will allow you to enter TWRP and restore a backup or flash a ROM.
If you didn't relock your bootloader you shouldn't have any problems flashing. Clarify what your trying to do, please (are you using a toolkit, etc).
If the answers are 1-yes and 2-no, then your probably SOL.
Didgeridoohan said:
I got that bootloop when I flashed a bad boot image. Easily fixed by flashing a good one...
But, let's clarify a couple of things:
Did you relock your bootloader while flashing?
Do you have a custom recovery (TWRP)?
If the answer to both of those are "yes", you might get out of this by using these commands:
fastboot format userdata
fastboot format cache
This will allow you to enter TWRP and restore a backup or flash a ROM.
If you didn't relock your bootloader you shouldn't have any problems flashing. Clarify what your trying to do, please (are you using a toolkit, etc).
If the answers are 1-yes and 2-no, then your probably SOL.
Click to expand...
Click to collapse
The answers are indeed 1-yes and 2-no. What is SOL an is there any way of fixing it?
SorryLols said:
The answers are indeed 1-yes and 2-no. What is SOL an is there any way of fixing it?
Click to expand...
Click to collapse
SOL = "S**t Out of Luck".
There is currently no know way of fixing it.
Your only avenue is to RMA it.
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
Any help, advice etc would be hugely appreciated. Thanks
Markh2001 said:
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
Any help, advice etc would be hugely appreciated. Thanks
Click to expand...
Click to collapse
Read the guide on how to fastboot flash a factory image. No toolkit necessary.
Would you mind posting a link to a guide? I forgot to add that I don't want my phone to become rooted by trying to fix this issue, I want to keep it stock like it was, also does not have developer options enabled stop me from going further.
Sorry for the questions I'm a noob to this and quite anxious.
AndroidSlave said:
Read the guide on how to fastboot flash a factory image. No toolkit necessary.
Click to expand...
Click to collapse
Would you mind posting a link to a guide? I forgot to add that I don't want my phone to become rooted by trying to fix this issue, I want to keep it stock like it was, also does not have developer options enabled stop me from going further.
Sorry for the questions I'm a noob to this and quite anxious.
Can anyone still please help! I'm a noob and so need instructions on what to do! Please!
Markh2001 said:
Can anyone still please help! I'm a noob and so need instructions on what to do! Please!
Click to expand...
Click to collapse
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
gee2012 said:
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
Click to expand...
Click to collapse
All foreign language to me what your saying, trying my best to self learn right now. I'm downloading the adroid SDK and extracting the files, really want to sort this myself. Any pointers to getting into bootloader mode? And adb on the PC?
Markh2001 said:
All foreign language to me what your saying, trying my best to self learn right now. I'm downloading the adroid SDK and extracting the files, really want to sort this myself. Any pointers to getting into bootloader mode? And adb on the PC?
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2588979 for easy adb installation. Read this too http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481.
To get into bootloader mode power down the device and after that press volume down + power. Here`s a guide to setup the sdk/adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/.
gee2012 said:
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
Click to expand...
Click to collapse
I've made the fastboot adb folder on my PC and attached my phone whilst it was in bootloader mode, I types in the command box adb devices and there is no list of attached devices.
I presume this is because I didn't enable developer options or USB debugging?
Markh2001 said:
I've made the fastboot adb folder on my PC and attached my phone whilst it was in bootloader mode, I types in the command box adb devices and there is no list of attached devices.
I presume this is because I didn't enable developer options or USB debugging?
Click to expand...
Click to collapse
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
gee2012 said:
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
Click to expand...
Click to collapse
Sorry to be a noob but how do I do this? Is this on the PC I presume?
Markh2001 said:
Sorry to be a noob but how do I do this? Is this on the PC I presume?
Click to expand...
Click to collapse
There is nothing you can do with a locked bootloader, claim warranty/RMA
gee2012 said:
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
Click to expand...
Click to collapse
Thought this would be the case, I went into adb fastboot and typed in fastboot devices and its showing some letters and numbers next to fastboot on screen if that helps.
In the future I presume I should make sure to enable developer options first so I can get out if this mess?
Also would it be best when I get my new n6 just to sideload the latest update marsmellow by getting the factory image from the Google website? Last question can I skip from 5.0 straight to 6.0 sideloading or do I have tobdo it one at a time?
Thanks for trying to help matey
Markh2001 said:
Thought this would be the case, I went into adb fastboot and typed in fastboot devices and its showing some letters and numbers next to fastboot on screen if that helps.
In the future I presume I should make sure to enable developer options first so I can get out if this mess?
Also would it be best when I get my new n6 just to sideload the latest update marsmellow by getting the factory image from the Google website? Last question can I skip from 5.0 straight to 6.0 sideloading or do I have tobdo it one at a time?
Thanks for trying to help matey
Click to expand...
Click to collapse
Next time enable usb debugging and ENABLE OEM UNLOCK, both in developer options. You can flash the latest firmware available directly in fastboot by flashing the individual img files.
Here is a link to setup adb/platform-tools https://www.google.nl/url?sa=t&rct=...orial/&usg=AFQjCNGolazOWoMssTikMpokJ6TtwEND5A.
gee2012 said:
There is nothing you can do with a locked bootloader, claim warranty/RMA
Click to expand...
Click to collapse
This is getting very weird now as I just typed into the adb fastboot window : fastboot oem unlock and its giving me a message on my screen to click yes and unlock the bootloader?
Markh2001 said:
This is getting very weird now as I just typed into the adb fastboot window : fastboot oem unlock and its giving me a message on my screen to click yes and unlock the bootloader?
Click to expand...
Click to collapse
Well click the power button and in the next screen scroll down with the volume button to select yes and push power.
gee2012 said:
There is nothing you can do with a locked bootloader, claim warranty/RMA
Click to expand...
Click to collapse
It says this on my Nexus 6 phone screen.
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone (a "factory data reset".)
Press the volume up/down buttons to select yes or no. Then press power button to continue.
Yes (Unlock bootloader, may void warranty)
No. ( Do not unlock bootloader and restart phone)
Markh2001 said:
It says this on my Nexus 6 phone screen.
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone (a "factory data reset".)
Press the volume up/down buttons to select yes or no. Then press power button to continue.
Yes (Unlock bootloader, may void warranty)
No. ( Do not unlock bootloader and restart phone)
Click to expand...
Click to collapse
Click yes, see my above post
gee2012 said:
Click yes, see my above post
Click to expand...
Click to collapse
Okay but will I be able to relock and put it back to the way it was? Can you please stay around to help me do this step by step?! I'd appreciate it a million
Markh2001 said:
Okay but will I be able to relock and put it back to the way it was? Can you please stay around to help me do this step by step?! I'd appreciate it a million
Click to expand...
Click to collapse
Sure, but first we have to get the phone working again,
Hello, I need help! my nexus 6 has never been rooted or unlocked, never had to used debugging option, but today my phone rebooted and it wont pass the animated startup screen, I am trying to flash the factory image from google but I need to unlock the bootloader to do that, and to do that I need debugging on, but I cannot access that option since the phone wont boot to the os, how can I solve this issue? thanks for your help in advance
jorge3687 said:
Hello, I need help! my nexus 6 has never been rooted or unlocked, never had to used debugging option, but today my phone rebooted and it wont pass the animated startup screen, I am trying to flash the factory image from google but I need to unlock the bootloader to do that, and to do that I need debugging on, but I cannot access that option since the phone wont boot to the os, how can I solve this issue? thanks for your help in advance
Click to expand...
Click to collapse
have you tried going into your stock recovery and just do a regular factory reset?
@jorge3687: First try a factory reset as suggested by Arju. If that doesn't work, sideload an OTA image to restore your device. The OTA images don't require an unlocked bootloader.