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.
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!)
Hi
I've been so stupid that i locked the oem setting, without any OS an recovery.
By all that, i've been searching online for a solution for days, without any luck...
So now im back with a phone that's oem locked and can't unlock it because i can't allow oem unlocking in developer settings, and can't do adb push because i do not have any recovery on the phone.
Is there anybody that can help me?
Recyclebin. said:
Hi
I've been so stupid that i locked the oem setting, without any OS an recovery.
By all that, i've been searching online for a solution for days, without any luck...
So now im back with a phone that's oem locked and can't unlock it because i can't allow oem unlocking in developer settings, and can't do adb push because i do not have any recovery on the phone.
Is there anybody that can help me?
Click to expand...
Click to collapse
Can't you get to the bootloader and fastboot the stock google images? This is a N6, right?
@ktmom: He can get to the bootloader, but it's locked, which means fastboot is not an option. Worse, he apparently has no recovery installed so he can't sideload an OTA.
The OP is screwed.
Strephon Alkhalikoi said:
@ktmom: He can get to the bootloader, but it's locked, which means fastboot is not an option. Worse, he apparently has no recovery installed so he can't sideload an OTA.
The OP is screwed.
Click to expand...
Click to collapse
Yeah, spaced
What about running recovery on the pc? I've never done that. I guess it requires an unlocked bootloader also.
I dunno, this is an N9 thread as is this one, but if I was in this position, I think I'd read through these.
I didn't think of that. It may work. Then he can sideload.
Recyclebin. said:
Hi
I've been so stupid that i locked the oem setting, without any OS an recovery.
By all that, i've been searching online for a solution for days, without any luck...
So now im back with a phone that's oem locked and can't unlock it because i can't allow oem unlocking in developer settings, and can't do adb push because i do not have any recovery on the phone.
Is there anybody that can help me?
Click to expand...
Click to collapse
Power up arrow to get into bootloader mode
might have to unlock bootloader at this point (dont remember the exact process you can google it) should be another fastboot command
fastboot flash recovery preferably twrp
then you should be able to load up a rom
ktmom said:
Yeah, spaced
What about running recovery on the pc? I've never done that. I guess it requires an unlocked bootloader also.
I dunno, this is an N9 thread as is this one, but if I was in this position, I think I'd read through these.
Click to expand...
Click to collapse
How can i make a running recovery on a pc?
Tried to search for it, but i cant find anything on it
Code:
fastboot boot recovery.img
The above command sends the device into recovery mode using an image stored on a PC's hard drive. From there the owner of the device can use the recovery just as if it were installed in the /recovery partition of the device's internal storage. Files that the owner of the device wishes to use are stored in the device's internal storage.
It won't help the OP however. An unlocked bootloader is one of the pre-requisites.
Cant boot up a live recovery either, because of tge locked bootloader...
Anyone got other ideas? Im really lost with this one
Contact Lenovorola and pay for the privilege of having your device serviced. You're totally screwed.
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.
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
sprays said:
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
Click to expand...
Click to collapse
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
sprays said:
You should be able to reflash the firmware
Use
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
Click to expand...
Click to collapse
have you tried unlocking your bootloader again?
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
kewlzter said:
have you tried unlocking your bootloader again?
Click to expand...
Click to collapse
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
sprays said:
You should be able to reflash the firmware
Use
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
Click to expand...
Click to collapse
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
kewlzter said:
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
Click to expand...
Click to collapse
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
sprays said:
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
Click to expand...
Click to collapse
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
?
kewlzter said:
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
Click to expand...
Click to collapse
Ty for the advice... I will do that.
Yea, i can wipe data/factory reset, but its the same. Bootloop until stuck to "fastboot reason: fall-through from normal boot mode."
I've read about this scenario for months on several different model forums and I imagine my best chance is to use the blankflash in edl mode but i can't boot into edl mode. Wherever I connect it is always recognized as a Motorola PCS or Motorola ADB device. I'm thinking of buying the deep flash cable and see if it works ...
$ fastboot getvar current-slot
//Getting and setting the slot should not cause any harm, but you never know.
$ fastboot --set-active=<a/b - whichever "current-slot" isn't.>
$ fastboot reboot
EDIT0:
In addition, you should plan ahead if you do get in. Like doing everything it takes to allow you to unlock/flash (adb).
You don't want to miss anything critical and screw up that other slot too.
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Hazardous2u said:
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Click to expand...
Click to collapse
Aún no hay solución
To everyone who is having this problem, just run the command multiple times in a row and it works! I don't know why, but just running it a few times in a row (I had to do like 9 times) gave me the unlock code.
Same thing for applying the code after getting it from Moto. Had to do it like 9 times in a row again, but it worked.