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
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
claytonjn said:
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you lock the bootloader just to be clear?
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
gee2012 said:
Did you lock the bootloader just to be clear?
Click to expand...
Click to collapse
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
simms22 said:
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
Click to expand...
Click to collapse
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
have you tried fastboot oem unlock again ?
uicnren said:
have you tried fastboot oem unlock again ?
Click to expand...
Click to collapse
Yes, it says it needs to be enabled in developer options
Sent from my Developer Edition Galaxy S5 using Tapatalk
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
uicnren said:
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
Click to expand...
Click to collapse
It says it will reboot in 5 seconds, but after 5 seconds the screen just goes blank. It appears the device is off, but maybe not.
Do you know what adb commands I would need to use to recover from this state?
Sent from my Developer Edition Galaxy S5 using Tapatalk
claytonjn said:
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
Click to expand...
Click to collapse
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
simms22 said:
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
Click to expand...
Click to collapse
Unfortunately that is not working for me (Not allowed in locked state!)
uicnren said:
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
Click to expand...
Click to collapse
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
claytonjn said:
Unfortunately that is not working for me (Not allowed in locked state!)
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Click to expand...
Click to collapse
If you have TWRP, boot to bootloader and use the following fastboot commands:
fastboot format userdata
fastboot format cache
Then boot to TWRP, connect to PC. Download a ROM to your PC and drag and drop in the root of internal storage. Then flash the ROM from TWRP, boot up, enable OEM unlock. Then boot back to bootloader and:
fastboot oem unlock
You should be good after that.
holeindalip said:
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
Click to expand...
Click to collapse
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
claytonjn said:
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
Click to expand...
Click to collapse
Follow my instructions listed above.
Evolution_Tech said:
Follow my instructions listed above.
Click to expand...
Click to collapse
II'm attempting that now.but fastboot format userdata and fastboot format cache fail. after booting into twrp the Nexus shows up in My Computer, but internal storage does not. I can push a ROM zip to the device with adb, but haven't figured out how to flash it yet because touch doesn't work...
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
claytonjn said:
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
Click to expand...
Click to collapse
glad you got it back, persistence pays off.
Lesson learned today? QUIT RE-LOCKING YOUR BOOTLOADER!
You can lock boot loader, you just have to make sure your phone boots first before locking it
So this morning i tried this. Kingroot didn't complete the root, some error happened, i didn't mind since i was just testing to see if i could root my phone for the first time [i've never done it before and it seemed simple enough].
I quit the app, a bunch of errors showed up, one after the other [i didn't register what exactly the windows said, i'm pretty sure it was a google application that stopped working]. The phone turned itself off.
i booted it up again, and it showed me the AP Fastboot Flash Mode screen. i know this from previously doing a factory reset, so i tried doing it again. After it wiped all of my data and custom, i tried rebooting it.
it showed me the motorola icon, but a few seconds later, i was back at the fastboot screen. i'm pretty desperate right now since this is my only phone. i tried selecting the "normal powerup" command, it didn't work. this is my screen right now:
"hab check failed for boot
failed to validate boot image
fastboot reason: fall-through from normal boot mode
USB conected
hab check failed for boot
failed to validate boot image
boot up failed"
none of the other commands, aside from Recovery, work. it takes me to the no command screen and all of the known options once i use the power+volume up command: reboot system now, reboot to bootloader, apply update from ABD, etc.
sorry if this thread reads weird, i'm sort of freaking out right now and english isn't my main language. thanks in advance to anyone who might help!
Check here
If you have questions PM me I will try to help. I got the same problem on Monday and solved it yesterday.
I've followed all of the steps from this guide: http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
I've got to the end where I am running the code snippets to flash everything, but everything fails. The error stated is FAILED: remote failure. I am not sure if this is related to my developer options being turned off, but I think it might be.
Is there a way to turn developer options on while in fastboot mode or perhaps a way around this error? The reason I am stuck in the fastboot is because the boot image can't be validated, I am not at the fastboot by choice, haha.
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Strephon Alkhalikoi said:
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Click to expand...
Click to collapse
I apologize for my ignorance since this is all new to me, but could you explain a few things to me.
Is this what you're referring to when you say Android N Preview 1 OTA: 'https://developer.android.com/preview/download.html'
Secondly, in order to flash these, am I still following the steps I was before, or should I be following a new set of steps?
You don't need the N Preview anymore. Download your Android 6.0.1 image from the Google page and flash using the instructions given on that page.
I went to the page and followed the directions. Still doesn't work. The flash-all script reboots after the first two commands, which lock the phone. But even then, it is still giving the error FAILED:remote failure.
me too!
I seem to be having the exact same issue! i just bought a Nexus 6 online that wasn't booting, it would only show a green led when plugged in. so here I am doing everything I can think of to fix the issue but then I get hit with the "remote failure" when i try to oem unlock the bootloader! (and since the phone wont't boot i can't check the "unlock bootloader" box in the developer options) so yeah I am going to keep researching this but if anyone has any good ideas about to get around the bootloader being locked please jump right in.
anyways I may have deeper issues, the battery will not charge. i know this because when i load up the fastboot menu, which i have to do by holding the buttons while plugging it in, it should say battery charging but all it says is battery ok
I also can't load recovery because when im in the fastboot menu and i choose recovery the phone freezes and the green led comes back on... *sigh*
They have the full ota packages posted on Google site now you can and push through the stock recovery
Here just make sure you get the shame version
https://developers.google.com/android/nexus/ota#hammerhead
Sent from my Nexus 6 using XDA-Developers mobile app
I have the OTA. I also installed Wugs toolkit.
My phone is in fastboot mode due to the boot image not being able to be validated. I didn't voluntarily open up fastboot using the shortcut.
The phone is UNLOCKED until bootloader is rebooted, then it is LOCKED. If I click start, it becomes UNLOCKED again. Wug's toolkit tries to UNLOCK the phone even while the phone says it is UNLOCKED. I don't think the phone is actually UNLOCKED, however whenever it tells me it is UNLOCKED, I try to proceed with flashing and it gives me a remote failure message on each command.
The next thing I am going try is the drivers and Wug's toolkit has a driver option, so I will try that. Besides the drivers, any other ideas?
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Strephon Alkhalikoi said:
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Click to expand...
Click to collapse
I am inexperienced, I stated that earlier. I have check a bunch of different forum posts and a bunch of different guides. Nothing seems to be helping and it seems like such a simple problem, a boot image that can't be validated. I am not trying to do anything special with my phone, I am just trying to get it to work. I woke up and it was stuck in this 'AP Fastboot Flash Mode (Secure)' mode. It is very bare bones, not even similar to the screens within videos I have seen. One moment the phone says it's UNLOCKED, the next it's LOCKED.
You are the expert, I am not. I am merely following your directions and they don't seem to be working. I did some outside research, came to a toolkit. Toolkits are great for beginners, especially since they are UI built, are built by someone who knows the area of interest, which makes researching easier and more efficient, but on top of that, it seems to be getting me much farther than your advice, although nothing is successful at this moment.
Here is a little more context into my situation. My phone seems to be recognized by Fastboot, but not ADB (From what I found, fastboot will find devices in fastboot, and adb will find devices functioning normally, don't know how true that is.). In addition, my phone seems to switch from UNLOCKED TO LOCKED after reboots, but can become UNLOCKED again if I push ANY button. Every command I issue (i.e flash bootloader, flash radio, flash system, flash userdata) result in the message, FAILED:remote failure, which I am not sure how to avoid (I have googled, checked these forums, checked other forums and there doesn't seem to be much, if any documentation on the error), but I think it is related to the fact my developer options are turned OFF. My next course of action is to install new drivers (I checked my drivers which are said to be up to date, I also installed google USB driver through the sdk, but now I am going to look into an adb or universal driver?) and attempt to rerun everything successfully.
If you have any other ideas, or don't think its the drivers, feel free to bring it up.
As a couple of fellows said before, try this:
https://developers.google.com/android/nexus/ota
Flash a FULL OTA from the link above, not a factory image. To flash any OTA you don't need to be unlocked. I think you might be confusing the terms (with the OTA you don't have to flash anything using fastboot)
In the link there are the instructions, it's pretty straight forward and easy if you have the correct drivers installed.
OTA requires that u can startup into recovery, I cannot I can startup fastboot through key combo but when I go to select recovery the green led comes back on and the screen displaying the fastboot options remains static
I think the phone freezes because it does not appear to be able to use the battery. though there is a firm battery connection it will not charge or power on without being plugged in. maybe when I select recovery I can quickly unplug and replug the USB and maybe hold the power button to try to simulate a successful reboot.. idk just thinking aloud and working with what I got..
I also can not start in recovery mode and the OTA requires ADB, which isn't recognizing my device. I have also stated that I have followed those instructions, and nothing resulted from them, except the same messages I have been stating these last few posts.
I will try this first chance I get later tonight..
http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Qwertyismypw said:
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Click to expand...
Click to collapse
The first two pictures are when the phone is 'UNLOCKED'. The second two pictures are when the phone is 'LOCKED'. The moment I press anything in 'LOCKED' mode, the little android man goes away, and it becomes the first two pictures. WHENEVER I push a button in 'UNLOCKED' mode, nothing happens, except in the bootloader logs screen says, 'FAILED TO VALIDATE BOOT IMAGE RET -1'. I have done everything on that OTA page in every way possible. It has done me no good.
Ok, I made a little progress I think. Wugs toolkit allowed me to use TWRP on my phone and ADB is recognizing my phone now. There are a lot of options within TWRP though, so I am going to look through them all for anything relevant. Anything I should keep an extra eye out for?
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't have an SD card, can I move it to the internal storage? And how exactly do I do this? I can't copy/paste anything into the phone (it says the phone doesn't actually exist, even though adb is recognizing it as in recovery) or do I sideload it? When I try to sideload it though, the device disappears (and device manager sees nexus 6 under other devices, but the driver isn't up to date and no drivers seem to work. I've tried the google usb driver with no luck.) and it won't allow me to sideload it.
Hello XDA,
Ok, so I'm going to try to explain the best I can. My roommate has a Nexus 6 (Project Fi if that matters). She went to install an update, although I'm not sure which one. She said she thinks it was "7 something". I'm assuming it was 7.1.1 since that is the one that I was last notified about on my phone and she said the notification appeared only a few days ago. After she installed it the phone was stuck in a bootloop (the spinning colored balls screen).
I Googled solutions and tried wiping system cache from recovery mode. That didn't work, so I asked if she had anything important on the phone and if I could do a factory reset. She said I could go ahead and do it, however that did not work either. So then I plugged the phone into my computer and fired up a terminal session to flash a factory image to the phone. I entered "fastboot oem unlock" so I could proceed . It came back with the "see developer options" message. Ok, cool, but I can't get into the settings app to enable OEM unlocking.
So since I did the factory reset and can't boot into the OS, is there any way to enable OEM unlocking from the bootloader? I'll keep looking for answers in the mean time.
Thanks in advanced.
EDIT:
Found a thread with the OP having similar issues. I tried "fastboot format cache" and "fastboot format userdata" which both failed with "Not allowed in locked state!". Even though I got the errors I tried (out of desperation) to boot to TWRP with "fastboot boot ~/Downloads/twrp-3.1.0-0-shamu.img" which failed with "FAILED (remote failure)".
EDIT2:
Tried downloading 7.1.1 OTA image and sideloading via "adb sideload shamu-ota.zip" from the bootloader recovery mode. Failed with "error: no devices/emulators found".
Sideload an OTA image. That should resolve the bootloop so you can enter Android to unlock the bootloader.
Strephon Alkhalikoi said:
Sideload an OTA image. That should resolve the bootloop so you can enter Android to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the reply. I tried it and it failed with "no device found". The command "adb devices" gives me an empty list. Not even ????????.
If ADB isn't seeing the device you potentially have a hardware issue.
i got same problem.
no oem unlock cuz is in bootloop
locked
erasing
@luisq93: Yours is a different issue. The solution for you is to do...nothing.
The erase part of the factory reset MUST complete, or you may end up with unusable internal storage until an uninterrupted factory reset is completed. So all you can do is be patient.
Strephon Alkhalikoi said:
@luisq93: Yours is a different issue. The solution for you is to do...nothing.
The erase part of the factory reset MUST complete, or you may end up with unusable internal storage until an uninterrupted factory reset is completed. So all you can do is be patient.
Click to expand...
Click to collapse
like 2 month and half patient?
cuz the erasing changed language 2 months ago and nothing more... from italian to English, maybe i should just wait... thanks for the advice.
@luisq93: How long did you leave the N6 running the very first time the device started erasing? I'm willing to bet you only gave it a few minutes, became impatient, shut the device down to restart it and upon restarting encountered the erase mode again. Consequently you thought it bootlooped and put it in your drawer.
Until you let erase mode complete, every time the device boots it will immediately enter erase mode, because the erase must complete to avoid corrupting the internal storage. Erase mode, especially on an encrypted phone, may take a while. I had one instance on another of my devices take an hour.
So the solution to the erasing "bootloop" is to do nothing except plug the N6 into its charger and leave it alone.