I'm using this method:
http://forum.xda-developers.com/showthread.php?t=1182871&page=61
The phone rebooted and said "Failed to boot 0x1000
No OS detected, going into RSD mode in 5 seconds
Press a key to stop countdown... etc."
I accidentally pressed a key or two...
EDIT: Never mind. I fixed it
How did you fix it? I had the same thing happen to me and I haven't been able to find a fix.
Thanks!
LOL -- your post reminded me of this:
Anyway, I just unlocked this week but didn't use this script. I did, however, end up at exactly this place... I didn't notice my phone had rebooted and pretty sure I missed the 5-second window. My phone listed several different modes (RSD, recovery, etc.) but when I looked carefully, it also said "Starting fastboot protocol support" at the bottom -- that is, it automatically chose fastboot when I didn't make a selection.
If that's what yours is doing, try issuing the "fastboot oem unlock" command (this is assuming your phone is still plugged into the computer at this stage) and proceeding from there. It worked when I did it.
I'll go ahead and note that my phone froze on the splash screen (with "Unlocked" at top left" at the next reboot; a battery-pull and second reboot solved that problem.
First time I tried to do bootloader unlock same thing happened. Got stuck at fastboot while flashing sbf because drivers took a while to install. I just did fastboot oem unlock and then reset, that did it.
Sent from my MB860 using XDA App
I got this message after trying to unlock bootloader using this guide:
http://forum.xda-developers.com/showthread.php?t=1202883
The RSD program got stuck at 96% and them eventually said failed. I took out the battery and put it back in and got the same message. Even though the program said failed, the Atrix has actually been unlocked because if you try to unlock again, it'll say failed instantly. So after that you can continue on with the fastboot & cmd part.
Use the volume keys to select fastboot and keep going.
My Nexus 7 2012 WiFi 4.4.2 started acting flaky a couple of weeks ago, randomly shutting down,etc. Anyway, it finally got to the point that I decided to just go back to factory settings. This resulted in it not booting past the "Google". Long story short I am now at the point of trying to flash it from my PC.
Nothing I do will get it to unlock the bootloader. I'm not even sure why I'm posting this as I have read every thread on this and nothing works, I just find myself going in circles. I have also read where one does not have to unlock the bootloader to flash it, but I have come to the conclusion that is just not so. Or at least I have not found a post that describes how to do that. When I try to unlock it it say in the upper right on the device "unlocking bootloader......" That's it.
I should also mention that I don't remember if USB debugging is on or off. Of course it dosn't matter 'cause I can't set it now anyway.
So I guess my question is, could there be a hardware issue that would put it in this state? I hate to just drop it in the trash without doing due diligence.
-Jim
Hey guys,
I've got a device from a friend with the exact same problem.
I would like to try to flash stock fresh with the nexus tool kit.
The problem is, this old nexus 7 (2012) is still with a locked bootloader.
I cannot start the device, it won't go past "Google", I can access fast boot, and the Toolkit can find the device and all.
I also get the "Unlocking now..." in the top left corner after I accepted the unlock with the power button, the device shuts down a few seconds later. According to the Nexus Toolkit I need to boot the device and finish the unlock in the developer options, and there goes my problem... I cannot start and finish the script as the device is not booting at all, apart from the fastboot ofc.
Is there ANY way to unlock the device without being able to boot up the device?
One more thing, when the Nexus toolkit sent a restart command, the device will just shut down, I have to start it manually again.
So I cant boot my phone and am COMPLETELY stuck and freaking out so hard.
I did a clean install of the validus rom and bean gapps. During set up, I made a pattern lock and made it required for boot up.
First time after restarting, i go into twrp and see the pattern prompt. I enter the correct pattern, and it says its wrong. I am able to get into twrp by entering anything other than the right pattern. I CANNOT boot into and rom even after flashing a new EDL image. I need my phone for work in a few hours my boss would kill me if he didnt live on the other side of the country I am extremely desperate for help.
Whenever i try to look up how to bypass the pattern, it only shows ways for patterns that are not required during boot up.
How do I get rid of secure startup on A2017U B25 unlocked bootloader?
UPDATE: After flashing EDL I was able to remove Patter Secure Startup using the STOCK recovery, lol wish I tried that hours ago
Hi,
I am trying to fix a friends Asus Nexus 7 WiFi tablet, the issue being that they tried to do an update, and now it doesn't boot, it just shows the google logo, then goes to "no command" for a second, then reboots. I have decent knowledge when it comes to fixing this type of thing as I have rooted and customised pretty much every device I have, however I cannot get into bootloader mode/menu and cannot access recovery, is there anythihng I can try or this unit completely dead? I am not sure which update they were trying to do but at this point I do not think there is any ROM on the device itself.
Any advice would be appreciated.
Many thanks,
EDIT: Can get to bootloader, but when selecting reboot to recovery gives me the "boot failed.." error. Cannot unlock bootloader either, it just stick on "unlocking bootloader..." for a while then stays saying locked, even if I reboot
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?