Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?
It's stock, locked and unrooted. All you did was try to install their OTA right? Sounds like their fault to me.
Calleja said:
Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?
Click to expand...
Click to collapse
you are going to have to flash a factory image
simms22 said:
you are going to have to flash a factory image
Click to expand...
Click to collapse
But how if the Rootkit can't? I can't seem to be able to flash anything to the device :/
Calleja said:
But how if the Rootkit can't? I can't seem to be able to flash anything to the device :/
Click to expand...
Click to collapse
rootkit is nothing official and only has in it whatever the developer has in it, flashing a factory image is why we have fastboot. if the rootkit cant do it, fastboot can. anyways, new users, newbs, should never be using root toolkits.
simms22 said:
rootkit is nothing official and only has in it whatever the developer has in it, flashing a factory image is why we have fastboot. if the rootkit cant do it, fastboot can. anyways, new users, newbs, should never be using root toolkits.
Click to expand...
Click to collapse
I wouldn't consider myself a newb, I've used fastboot and adb to flash factory images before. I used the toolkit in this instance because googling around made the toolkit's Soft Brick option seem like my best bet. It did not work.
How do I do that if the Fastboot Flash Mode seems to be borked/soft bricked and I can't seem to unlock the bootloader?
Calleja said:
I wouldn't consider myself a newb, I've used fastboot and adb to flash factory images before. I used the toolkit in this instance because googling around made the toolkit's Soft Brick option seem like my best bet. It did not work.
How do I do that if the Fastboot Flash Mode seems to be borked/soft bricked and I can't seem to unlock the bootloader?
Click to expand...
Click to collapse
because before unlocking the bootloader, you have to enable the developer setting. if your bootloader is still locked, then there is nothing that you can do except try to get a rma, sorry.
simms22 said:
because before unlocking the bootloader, you have to enable the developer setting. if your bootloader is still locked, then there is nothing that you can do except try to get a rma, sorry.
Click to expand...
Click to collapse
The developer setting WAS unlocked before all this started.... the problem seems to be with the partition table? Does anyone have any ideas?
Calleja said:
The developer setting WAS unlocked before all this started.... the problem seems to be with the partition table? Does anyone have any ideas?
Click to expand...
Click to collapse
oh, it was unlocked? and you tried unlocking the bootloader?
simms22 said:
oh, it was unlocked? and you tried unlocking the bootloader?
Click to expand...
Click to collapse
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?
Calleja said:
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?
Click to expand...
Click to collapse
Have you tried doing fastboot oem unlock? The cammands you're using are for the 6P
nms247 said:
Have you tried doing fastboot oem unlock? The cammands you're using are for the 6P
Click to expand...
Click to collapse
Yeah, fastboot oem unlock brings up:
FAILED (command write failed (Unknown error))
The funny thing is I get the same exact error when I try "fastboot oem device-info", is that a driver/fastboot installed wrong thing, maybe? (I had only used fastboot from OSX before, now on Win10, although "fastboot devices" does seem to work)
Calleja said:
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?
Click to expand...
Click to collapse
you are missing the one and only command that you can unlock the bootloader with.. fastboot oem unlock. if it gets unlocked, then you can flash a factory image.
simms22 said:
you are missing the one and only command that you can unlock the bootloader with.. fastboot oem unlock. if it gets unlocked, then you can flash a factory image.
Click to expand...
Click to collapse
Ok, so if "fastboot oem unlock" returns "FAILED (remote failure) there's nothing whatsoever I can do? RMA is the only option?
The first android device I don't root and leave completely stock and it's the only one I've ever bricked..... sigh
No, Google bricked it, with his stupid OEM unlocking switch, which is totally stupid. But they'll give you a new one.
istperson said:
No, Google bricked it, with his stupid OEM unlocking switch, which is totally stupid. But they'll give you a new one.
Click to expand...
Click to collapse
Anyone know how trustworthy Motorola's RMA service is in Mexico? Bought the N6 through motorola.com.mx, kinda regretting that decision now.
help
Calleja said:
Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?
Click to expand...
Click to collapse
How do you overcome? can show me the
thanks !
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!)
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.
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
Howdy XDA peoples.
I'm hoping someone can help me. I had a Nexus 6, unrooted (atlhough the bootloader was unlocked when I purchased it). I had been recieving the official beta Android updates, but am not sure what version I got up to. Recently, while listening to some music on my drive home, the phone stopped. When I arrived home, I saw that it had put itself into Fastboot Mode, although it all looked slightly different (more 8-bit I guess). If I try and boot Android normally, whether from a powered off state, or from Fastboot etc, it fails, every time, and just boots into this 8 bit fastboot. (Although if I boot into Fastboot from a powered off state, it shows the usual Fastboot you would expect on the nexus 6. The 8 bit style one has the exact same functionality and control, just looks different). I have tried hooking it up to the Nexus Toolkit, which seems to behave normally and says its doing whatever I ask it to do, but still, nothing. I simply cannot boot into Android. In the Fastboot menu, Under bootloader logs, it displays the following message: "failed to validate boot image: ret=-1. Fastboot Reason: Fall-through from normal boot mode." The same happens if I try to boot into recovery.
If someone could nudge me in the right direction (or perhaps direct me to a forum where this issue has been dealt with, I have searched...), I would be immensely grateful.
Can you post a picture or type out the contents of this 8bit fastboot screen?
geokhentix said:
Can you post a picture or type out the contents of this 8bit fastboot screen?
Click to expand...
Click to collapse
I can type it.
So on the first screen that pops up.
Start
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.21 (sha-f12f8c2, 2016-05-10 11:30:37)
Baseband:
Product/Variant: shamu XT1100 32GB P3A0
Serial Number: ZX1G423NQB
CPU: APQ8084 ES1.1
eMMC: 32GB Sandisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix S8 SDRAM DIE=6GB
Console (NULL): null
Battery OK (Charging)
Device is UNLOCKED. Status Code: 3
Transfer Mode: USB Connected
The colours are accurate (except what is typed in black above is white on the phone screen). On the bootloader screen:
Bootloader logs
Fastboot Reason: Reboot mode set to fastboot
USB connected
failed to validate recovery image: ret=-1
Boot up failed
Just like what had happened to you, mine bootlooped today, was listening to some music, the phone just restarted itself and went into an endless bootloop, any help or fix for that ? (Also, I've been running android N beta for almost a month now, and this was the first "bug/something" to happen to me)
looks like we are in same.boat
http://forum.xda-developers.com/nexus-6/help/how-to-flash-nexus-6-xt1103-rom-t3444017
Factory Image
Do You try to manually flash a Factory Image? Maybe not one from the N Preview? Otherwise to flash a Custom Recovery and try to flash a random Custom ROM?
James Bartlett said:
failed to validate recovery image: ret=-1
Click to expand...
Click to collapse
Unfortunately, I currently get the very same message for my Nexus 6 device.
It had also began 'all of a sudden', ie. without any attempts to root or whatever.
Given this applies to recovery mode as well, I fear adb sideload method with OTA is not possible.
Did you somehow manage to rescue your device?