Hello,
I have a stock Nexus 6, not rooted, with apps only from Google Play. Today I received the November security patch and was asked to reboot. After that the phone worked fine for 2 hours, and then froze. Unfortunately I was not able to boot it. Fastboot is loading but is unable to load the recovery image: "failed to validate recovery image: ret=-1" or "failed to validate boot image: ret=-1".
I then installed fastboot and adb. fastboot detects the phone, but I'm unable to unlock it:
Code:
$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.044s
adb is not detecting any device, so I don't know how to check the "Allow OEM Unlock" option - which is for some reason unchecked by default.
Is there any way around this or should I just give up?
Thanks!
Tomer Morad said:
Hello,
I have a stock Nexus 6, not rooted, with apps only from Google Play. Today I received the November security patch and was asked to reboot. After that the phone worked fine for 2 hours, and then froze. Unfortunately I was not able to boot it. Fastboot is loading but is unable to load the recovery image: "failed to validate recovery image: ret=-1" or "failed to validate boot image: ret=-1".
I then installed fastboot and adb. fastboot detects the phone, but I'm unable to unlock it:
Code:
$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.044s
adb is not detecting any device, so I don't know how to check the "Allow OEM Unlock" option - which is for some reason unchecked by default.
Is there any way around this or should I just give up?
Thanks!
Click to expand...
Click to collapse
you have to boot up, then enable the developer options(tap omn build number in about phone three times), then head back into system options, scroll down to developer options, then enable oem unlocking. now, boot into your bootloader, connect your phone via usb to your computer, start fastboot on your computer, then fastboot oem unlock. notice i never said adb? thats because adb is not involved here, fastboot is involved.
simms22 said:
you have to boot up, then enable the developer options(tap omn build number in about phone three times), then head back into system options, scroll down to developer options, then enable oem unlocking. now, boot into your bootloader, connect your phone via usb to your computer, start fastboot on your computer, then fastboot oem unlock. notice i never said adb? thats because adb is not involved here, fastboot is involved.
Click to expand...
Click to collapse
I think he is saying that the phone will not boot up. So he can't get to the dev options.
I'm afraid you'll need to send to the repair centre your mobile phone.
If you can't enable OEM UNLOCK option in the Developer Settings in android, you won't be able to unlock te bootloader.
Rektifying said:
I think he is saying that the phone will not boot up. So he can't get to the dev options.
Click to expand...
Click to collapse
Quetzalcoalt_Lp said:
I'm afraid you'll need to send to the repair centre your mobile phone.
If you can't enable OEM UNLOCK option in the Developer Settings in android, you won't be able to unlock te bootloader.
Click to expand...
Click to collapse
i wasnt even going to say repair center, as there isnt much they can try. an rma(factory replacement) might be your only option.
Yes, but what I mean is that he can't do anything. He is going to need to use his warranty.
Quetzalcoalt_Lp said:
Yes, but what I mean is that he can't do anything. He is going to need to use his warranty.
Click to expand...
Click to collapse
well, chances are that he bought the phone after it was released on oct 29 2014, so his phone should still be under warranty. so yup, and i wish him luck
simms22 said:
well, chances are that he bought the phone after it was released on oct 29 2014, so his phone should still be under warranty. so yup, and i wish him luck
Click to expand...
Click to collapse
Indeed I haven't found any key or menu combination that would allow me to boot and change this option
I hope T-Mobile will replace it under the warranty.
Thanks for the replies!
I know it doesn't help now... But for anyone reading this...
Unless your never going to attempt to fix anything, and will always just RMA...
ALWAYS ALWAYS ALWAYS unlock and leave your bootloader unlocked. By the time you decide otherwise, it may likely be too late.
Try plugging into the charger and leaving it for like 5 to 10 minutes then try and get to recovery to do a reset from there?
While it would stuck to set it up again, I'd try to factory reset and get the phone to start up before sending it in. It'll take 5 minutes at most, and may get you a working phone again.
Sent from my Nexus 6
MysticKing32 said:
Try plugging into the charger and leaving it for like 5 to 10 minutes then try and get to recovery to do a reset from there?
Click to expand...
Click to collapse
Hi, I tried what you suggested and it had no effect - I still can't enter recovery mode (image is unverified).
imnuts said:
While it would stuck to set it up again, I'd try to factory reset and get the phone to start up before sending it in. It'll take 5 minutes at most, and may get you a working phone again.
Sent from my Nexus 6
Click to expand...
Click to collapse
I would have loved to be able to do that, but I can't run any image on the device. I can't leave the fastboot menu.
Try a factory reset in the stock recovery: https://support.google.com/nexus/answer/4596836?hl=en
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
I have a Nexus 6. I've been on build LMY47D. My storage was showing as 32GB when I have a 64GB version. I read this post for a fix. I did a fresh install of adb, checked the OEM unlock, removed security (PIN) and turned on USB debugging from developer settings. I used "adb reboot bootloader" to reboot to the bootloader and then typed the commands from the post I linked above:
fastboot format userdata
fastboot format cache
I was wanting to take the OTA update so I was planning on flashing the LRX22C image and wanted to make sure I was OEM unlocked so before rebooting I also did:
fastboot oem unlock
The result said:
<bootloader> device already unlocked!
FAILED <remote failure>
finished. total time 0.002s
I figured I was unlocked and essentially factory reset, so I entered:
fastboot reboot
It was on the spinning dots for about an hour. I read somebody with something similar rebooting after such a long time and everything being ok, so I tried it with no luck.
I can get boot to the bootloader. The lock is unlocked. When I try to go to recovery I just see the dead android with the red sign and exclamation. My PC no longer sees the phone, I think because I'm no longer in USB debugging? Is there any way to fix this? I've tried selecting "factory" from the bootloader, but get the same result--endless bootloop. Any help is appreciated!
EDIT: Thought I'd add, at the bottom of the bootloader screen it shows "Device is Unlocked. Status Code: 3"
EDIT 2: While waiting for feedback, I downloaded wugfresh's nexus toolkit and selected the softbrick/bootloop option. It's downloading a factory image atm, so we'll see how this goes.
Marcellus1 said:
I have a Nexus 6. I've been on build LMY47D. My storage was showing as 32GB when I have a 64GB version. I read this post for a fix. I did a fresh install of adb, checked the OEM unlock, removed security (PIN) and turned on USB debugging from developer settings. I used "adb reboot bootloader" to reboot to the bootloader and then typed the commands from the post I linked above:
fastboot format userdata
fastboot format cache
I was wanting to take the OTA update so I was planning on flashing the LRX22C image and wanted to make sure I was OEM unlocked so before rebooting I also did:
fastboot oem unlock
The result said:
<bootloader> device already unlocked!
FAILED <remote failure>
finished. total time 0.002s
I figured I was unlocked and essentially factory reset, so I entered:
fastboot reboot
It was on the spinning dots for about an hour. I read somebody with something similar rebooting after such a long time and everything being ok, so I tried it with no luck.
I can get boot to the bootloader. The lock is unlocked. When I try to go to recovery I just see the dead android with the red sign and exclamation. My PC no longer sees the phone, I think because I'm no longer in USB debugging? Is there any way to fix this? I've tried selecting "factory" from the bootloader, but get the same result--endless bootloop. Any help is appreciated!
EDIT: Thought I'd add, at the bottom of the bootloader screen it shows "Device is Unlocked. Status Code: 3"
EDIT 2: While waiting for feedback, I downloaded wugfresh's nexus toolkit and selected the softbrick/bootloop option. It's downloading a factory image atm, so we'll see how this goes.
Click to expand...
Click to collapse
When you see the dead android (recovery) just press volume up + power simultainiously and do a data factory reset, after that the phone should boot up fine.
PS: don`t use toolkits, they cause more harm then good if used by unexperienced users and experienced users don`t use it anyway
gee2012 said:
When you see the dead android (recovery) just press volume up + power simultainiously and do a data factory reset, after that the phone should boot up fine.
PS: don`t use toolkits, they cause more harm then good if used by unexperienced users and experienced users don`t use it anyway
Click to expand...
Click to collapse
Thanks for your response. I actually tried pressing volume up + power simultaneously several while at recovery and nothing happened. After that I tried other key combinations, wondering if I got it wrong, and nothing happened with those either.
I ended up using the toolkit (before I saw your response) and my phone is back in business *HUGE sigh of relief*
Marcellus1 said:
Thanks for your response. I actually tried pressing volume up + power simultaneously several while at recovery and nothing happened. After that I tried other key combinations, wondering if I got it wrong, and nothing happened with those either.
I ended up using the toolkit (before I saw your response) and my phone is back in business *HUGE sigh of relief*
Click to expand...
Click to collapse
FWIW: to enter the recovery menu in stock recovery, the combo is - press and hold power, and press and release volume up.
Thank You seniors for supporting me for the last few days.
This thread is about my discussions with you http://forum.xda-developers.com/nex...6-recovery-flashable-fastboot-t3066052/page54 and the following pages.
I have to move here as my issue was off topic in that thread.
When i type fastboot oem unlock command it says check OEM unlock option is developer settings.
But my problem is i cant boot my phone to go there.
I erased everything and locked boot loader by mistake.
I can boot my phone to bootloader and recovery i cant flash anything via fastboot as my bootloader is locked.
But i can do adb sideload in recovery.
I am now on lmy48i recovery i tried lmy48i from lmy47z it says the file is incorrect and i am already on lmy48i.
Kindly help.
openbook said:
Thank You seniors for supporting me for the last few days.
This thread is about my discussions with you http://forum.xda-developers.com/nex...6-recovery-flashable-fastboot-t3066052/page54 and the following pages.
I have to move here as my issue was off topic in that thread.
When i type fastboot oem unlock command it says check OEM unlock option is developer settings.
But my problem is i cant boot my phone to go there.
I erased everything and locked boot loader by mistake.
I can boot my phone to bootloader and recovery i cant flash anything via fastboot as my bootloader is locked.
But i can do adb sideload in recovery.
I am now on lmy48i recovery i tried lmy48i from lmy47z it says the file is incorrect and i am already on lmy48i.
Kindly help.
Click to expand...
Click to collapse
If you have TWRP installed, there may be hope. If not, RMA is the only option.
Evolution_Tech said:
If you have TWRP installed, there may be hope. If not, RMA is the only option.
Click to expand...
Click to collapse
On the Motorola Website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
It says i have to type $ fastboot oem get_unlock_data
How do i get $ prompt when i type that it says $ is not recognized.
And when i type fastboot oem get_unlock_data i get
C:\Users\RAO\AppData\Local\Android\sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.000s]
finished. total time: 0.000s
When i type fastboot oem unlock it says check allow OEM unlock under developer options.
What do i do?
openbook said:
On the Motorola Website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
It says i have to type $ fastboot oem get_unlock_data
How do i get $ prompt when i type that it says $ is not recognized.
And when i type fastboot oem get_unlock_data i get
C:\Users\RAO\AppData\Local\Android\sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.000s]
finished. total time: 0.000s
When i type fastboot oem unlock it says check allow OEM unlock under developer options.
What do i do?
Click to expand...
Click to collapse
As @Evolution_Tech told you, IF you have TWRP installed you can boot into recovery and move a flashable ROM.zip from your PC to your phone.
If you do not have TWRP Recovery installed, you are out of options. You will have to return it for repair or replacement.
You don't type $.
Anyway, as above, no TWRP recovery, nothing you can do
seems like you could flash a factory image in Wug's toolkit if you can into bootloader mode. (power off/ hold vol down + power button at the same time)
then flash a factory image in "soft brick" mode.
norwoodesteel said:
seems like you could flash a factory image in Wug's toolkit
Click to expand...
Click to collapse
No. Did you read the thread? Bootloader is locked.
danarama said:
No. Did you read the thread? Bootloader is locked.
Click to expand...
Click to collapse
doesn't matter, you can do it with a locked bootloader. it asks if your bootloader is locked and then flashes.
norwoodesteel said:
doesn't matter, you can do it with a locked bootloader. it asks if your bootloader is locked and then flashes.
Click to expand...
Click to collapse
It does matter. It can only unlock the bootloader if the bootloader can be unlocked. It cannot unlock the bootloader if the bootloader cannot be unlocked, which is the case here.
danarama said:
No. Did you read the thread? Bootloader is locked.
Click to expand...
Click to collapse
sorry, it's the sideload function where you don't have to be unlocked
norwoodesteel said:
sorry, it's the sideload function where you don't have to be unlocked
Click to expand...
Click to collapse
Yep, unfortunately there is nothing to do here. All he can do is send it in for repair
danarama said:
Yep, unfortunately there is nothing to do here. All he can do is send it in for repair
Click to expand...
Click to collapse
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
openbook said:
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
Click to expand...
Click to collapse
No! Stop clutching at straws. We've already told you what the only thing you can do is.
openbook said:
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
Click to expand...
Click to collapse
nothing can fix your phone unfortunately. only thing you can try to do is a RMA.
I have such operations
openbook said:
I dont care about any data inside my phone.
Let me explain how i messed my Nexus 6.
I wanted to flash a fresh lmy48i full version so i erased everything via fastboot.
Then i started flashing using flashall.bat it flashed everything except system it said the device cannot accept such a huge file.
I thought may be i was unlocked it doesn't wanna work so i typed fastboot oem lock the device said successfully locked and thats the end of my N6 i can't unlock it anymore because it says enable allow oem unlock which i cant do because i erased system. when i try to boot i see GOOGLE logo but nothing after that i even left it for more than an hour nothing happens no boot animations.
Now i cant flash anything via fastboot because my bootloader is locked.
But i can get into recovery and i have the option to do ADB Sideload.
When i try lmy48i from lmy47z ...zip my phone says expecting lmy47z release keys but device already has lmy48i ...relese keys etc...
So i am thinking the next update which google releases would be xyz from lmy48i .zip and that will solve my problem.
After reading forums i understood my mistake was not using the latest fastboot file that is why my system.img failed and it said the file is huge latest fastboot.exe uses sparse method if the file is big than the acceptable size of the phone.
Prior reading would have saved my Nexus 6.I leant a good lesson.
Do you thing xyz from lmy48i ...zip in future can fix my phone?
Click to expand...
Click to collapse
I have such operations, unlock, Brush unsuccessful, lock, then can not boot, how do ah
imtv said:
I have such operations, unlock, Brush unsuccessful, lock, then can not boot, how do ah
Click to expand...
Click to collapse
@ IMTV: Can you explain in detail.
openbook said:
@ IMTV: Can you explain in detail.
Click to expand...
Click to collapse
He isn't giving you a fix if that's what you're hoping, because there is no fix.
It looks like he is saying he has the same problem as you.
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
jamescable said:
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
Click to expand...
Click to collapse
Only works if you have TWRP installed. And IF you have TWRP installed, there are other, easier solutions....
Every Software Lock should have an unlock procedure.
That is what i am searching for.
@ Danarama:I am noticing your reply's for a while now.where ever i post you respond saying RMA is the only option. Please don't make conclusions.If you don't know unlock procedure then ignore my posts.
I live in Kuwait and i bought the phone from UAE paying customs duty delivered to me via DHL no local warranty.
So i am trying all options.Let other's respond.
For people living in US,UK or few other countries RMA might be an easy procedure so they just use that option.
There are Nexus lovers everywhere so don't talk about RMA or Direct Play Store return procedures here after.
I am using Android since 2010 and i have played, rooted, reinstalled etc... with lots of android phones. I was shocked when i ended up with a dead lock like this that too on a nexus.
How stupid is this Google's Anti Theft Feature with out a back door option even for genuine owners like me.I am not a theif.I know my google account credentials which i used on my nexus 6.
Atleast Google should give an option to genuine owners to prove themselves by logging into their website with the gmail ID used on the phone to request for an unlock procedure.
I was gifted a Nexus 6 after my 5X died. As far as I know the device has never been OEM unlocked, much less flashed with anything. I've unlocked developer options and allowed USB debugging and OEM unlock but when I try to use power+Vol(-) to get into fastboot mode nothing happens, the screen is just black. When I bridged the device using ADB I could see the serial number and tried using the boot into recovery mode command and it rebooted to the same black screen. When I used fastboot commands on the black screen I could see the device and tried running fastboot oem unlock, it did something but wasn't successful in unlocking it. I'm not prepared to just start running fastboot commands blind like that without being able to see what's happening on the device's screen.
It's a curious problem, has anyone ever heard of it happening before? I can't find anything similar when I google it.
All I really want to do is clear the Dalvik cache and flash the latest factory image because currently, even after doing a factory reset, the device is very slow and laggy.
Is there anyway I could clear all the caches etc without going into fastboot mode or does anyone know of any fixes I could use so I can see the recovery menu?
If you boot to bootloader mode, then "fastboot boot <TWRP.img>" you might be able run twrp on your pc and clear caches. If it works, I'd consider factory resetting. You can get twrp here: https://dl.twrp.me/shamu/
I have considered that. But that requires OEM unlock, no? I still haven't managed to unlock it yet. The first time I tried, I said yes to unlock (it involves using the rocker to select a response, which I can't see the options for) but in the command window it said it failed (can't remember the error message though). I was going to try again today but because I couldn't see the options when I tried it said I'd cancelled the operation and I was too scared to try again in case something went wrong.
But, do you think I should try the fastboot oem unlock command again? I definitely need OEM unlock to install TWRP, right?
connorjolley said:
I have considered that. But that requires OEM unlock, no? I still haven't managed to unlock it yet. The first time I tried, I said yes to unlock (it involves using the rocker to select a response, which I can't see the options for) but in the command window it said it failed (can't remember the error message though). I was going to try again today but because I couldn't see the options when I tried it said I'd cancelled the operation and I was too scared to try again in case something went wrong.
But, do you think I should try the fastboot oem unlock command again? I definitely need OEM unlock to install TWRP, right?
Click to expand...
Click to collapse
To install twrp yes, you need an unlocked bootloader. This doesn't install twrp on the device. I believe it should work. It certainly shouldn't hurt. I've been unlocked since the N6 came out so I can't double check for you.
If it doesn't work, I'd be a bit inclined to just flash a factory image thus ensuring everything is stock and current. You might want to wait for others to chime in, but it's what I would do.
You may consider downloading Nexus Root Toolkit, works like a charm : ).
I can't just flash the stock bootloader without OEM unlock, right?
connorjolley said:
I can't just flash the stock bootloader without OEM unlock, right?
Click to expand...
Click to collapse
Correct, you need to be unlocked to flash a factory image, that includes the bootloader. See Google's instructions. Don't get confused by the "fastboot oem unlock"
vrs "fastboot flashing unlock" we are an older device and use oem unlock. The other is for the 6P and newer devices.
ktmom said:
Correct, you need to be unlocked to flash a factory image, that includes the bootloader. See Google's instructions. Don't get confused by the "fastboot oem unlock"
vrs "fastboot flashing unlock" we are an older device and use oem unlock. The other is for the 6P and newer devices.
Click to expand...
Click to collapse
Successfully unlocked. TWRP didn't help, still can't see the bootloader menu to access the recovery. I'm flashing the factory image now, hopefully a new bootloader will fix it. If not, is there anyway to clear the Dalvik cache using fastboot commands now the phone is unlocked?
UPDATE
Still a black screen even with a new bootloader flash. I'm assuming now this must be a hardware problem
connorjolley said:
Successfully unlocked. TWRP didn't help, still can't see the bootloader menu to access the recovery. I'm flashing the factory image now, hopefully a new bootloader will fix it. If not, is there anyway to clear the Dalvik cache using fastboot commands now the phone is unlocked?
Click to expand...
Click to collapse
I think the command is "fastboot erase cache". Also, unlocking will have wiped the device.
connorjolley said:
UPDATE
Still a black screen even with a new bootloader flash. I'm assuming now this must be a hardware problem
Click to expand...
Click to collapse
Why not just flash the entire factory image you got the bootloader from? What can it hurt? It would be really odd for this to be hardware if you can boot into the ROM and the screen works.
Hey guys, i have MI A2 cellphone, and after auto update programmed to three hours the smartphone show "AndroidONE" logo and then shutdown, i tried "Fastboot oem unlock", but it is my output:
PHP:
C:\Users\Lucas Daniel>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.000s
. I'm desperate, I do not know what to try anymore, I believe I do not have unlock OEM activated, someone can help me?
Sorry for bad english, i'm from brazilian.
@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.
sas.mar said:
@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.
Click to expand...
Click to collapse
Thanks, looks that, unfortunately, my unique solution is test-point for activate EBL Mode... I will leave the topic open for the case of i get other solutions... after 3 days, if not get, i will close and the unique solution will really test-point.
Try rebooting it a couple of times and see if it boots. Or plug it to a charger and try booting it once it starts to charge successfully. If all fails, flashing via EDL might be your only option.
Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).
Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?
Tianhe said:
Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?
Click to expand...
Click to collapse
What is it command?
Aerobatic said:
Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).
Click to expand...
Click to collapse
How can I do it? I leave the phone in the charger for a long time? Or do you need the power button for a long time?
I tried to press the power button for 2 minutes and nothing happened.
When i leave the smartphone on the charge, after 50 minutes, show for me 100% percent, so, i pressed power button and the screen stayed lock in "AndroidONE", nothing happened, until try again press power button.
The problem original comebacked to me
LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
I tried, the same ploblem happenned... don't work, unfortunely... :/
LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)
Phil_Smith said:
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)
Click to expand...
Click to collapse
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.
LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
Do as tabun1994 said.
This will hopefully get the system up again.
The commands I wrote would unlock the bootloader. What else could I have meant?
If you succeeded with tabun's method, then you probably would only need to enable "USB debugging" and "OEM unlocking" in the ROM's developer options (which you'll enable by hitting "build number" in settings like 10 times or so).
Then you would connect the device and accept the 'trust this device' warning.
After booting to fastboot now, the commands I wrote should work and unlock the bootloader (if you even want that when your system is running again).
tabun1994 said:
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.
Click to expand...
Click to collapse
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl
The test point method is actually easy , you have to dissasemble the display , easy procedure , remove the battery and short the two test points with tweezerz or something ,and in the meantime you plug the usb cable into the computer. It should install the Qusb_Hub drivers , and with miFlash you should be able to reflash the firmware . I bought a phone that was in this state and fixed it using these steps.
No more solutions, I will do the test point method, thanks to everyone who tried to help otherwise.
LukeSkyPTBR said:
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl
Click to expand...
Click to collapse
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!
LukeSkyPTBR said:
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!
Click to expand...
Click to collapse
I execute bat archive but nothing happens in Mi A2 .-
tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
What is your smartphone?