Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?
Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?
Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.
Related
I factory reset my Glass today because it wouldn't connect to my phone (I switched roms so I needed to pair Glass again). After I did the reset it went into a boot loop. When it's on the "Glass is Updating" screen it can't be accessed via ADB, but I managed to figure out how to get it into the bootloader via the buttons.
From the bootloader I've tried erasing and flashing 16.2, 16.11, and 16.0 but it just returns to the same "Glass is Updating" screen when I reboot.
When I erase, I erase boot, recovery, system, userdata, and cache. When I flash, I flash boot, recovery, and system. I've tried with and without flashing userdata.
Does anyone have any ideas as to what could be wrong?
EDIT: Something really weird is going on. I ran the erase without flashing anything back on and did a reboot. I expected it to stop at the bootloader since there should be nothing to load, but instead it continues to go into the "Glass is Updating" boot loop.
EDIT 2: I've been doing a lot of reading and it sounds like there are more partitions than just the bootloader and the 5 that I have been erasing. My guess right now is that my device downloaded the 16.2 update into some other partition before I did the factory reset and now every time it boots it's running that update. I can't get much info from the device because I can't use adb.
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
davezack said:
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
Click to expand...
Click to collapse
That did it! I didn't try a version back that far because as far as I know mine had XE16 on it when I first got it.
Thanks!
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Starcruiser322 said:
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Click to expand...
Click to collapse
Was there ever a resolution to this?
I believe I might be having the same issue.
Sent from my LG-VS980
Well, it was sort of resolved for me. If you follow the steps in THIS THREAD, you better hope you have enough battery to last through the process. If you do, great, you'll have your phone back in running order soon enough. A bit of Linux experience helps with this.
After my battery died it refused to come back on, and I brought it to the Verizon store and told them I woke up one day and it wouldn't turn on.
They replaced it under warranty.
I assume other major carriers would do the same.
Is your phone still under warranty? What model and carrier?
After a bit of searching, I did confirm that the 26A update locks the bootloader and implements tighter security policies.
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.
did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.
Hello,
I did a reboot and now I can't use my phone anymore. I see the Boot animation but after the Boot up, the screen just turns black. I receive notifications and active display is working, also I can start my camera with the twist but I can't take picture because the touchscreen does not respond. On active display or the power off pop up, the touchscreen is working. So I did a cache partition wipe but this hasn't fixed my problem. The strange thing is that after a couple of frustrated reboots, the Boot animation changed to the old animation with the spinning world. I want to reset the phone via recovery but first I need to backup my data. I have very important Data on my phone like whatsapp log or Photos and videos.. I can't connect my phone to the computer because I have a pin... How I can Backup my data and what caused the black screen?
If your bootloader is unlocked you can flash TWRP. TWRP has the ability to decrypt userdata if you have the password. I don't know if it can decrypt the moto x or not, because TWRP only officially support ASOP type encryption, if motorola uses a different technique for encryption it will say the password is wrong. If it works you can browse and backup files from TWRP recovery.
If it says the password is wrong or you don't have the bootloader unlocked, then you are SOL and have lost everything.
In either case doing a factory reset will hopefully fix your issue.
Sent from my XT1095
So I did a factory reset now. But I stuck in Bootloop, i just see the M logo. How I can fix it? And no, my Moto X is stock like out of the Box.
rupro327 said:
So I did a factory reset now. But I stuck in Bootloop, i just see the M logo. How I can fix it? And no, my Moto X is stock like out of the Box.
Click to expand...
Click to collapse
After the factory reset bootup takes longer than normal, how long did you wait?
If that is not the case, what model moto x do you have? For example mine is xt1095. Also what version of android do you have? 5.0, 4.4.4, 5.0.2, 5.1, etc?
Sent from my XT1095
same issue today
also have the same issue, black screen after reboot. moto voice, active display/notifications are responsive, camera too when twisting the phone. moto voice says "unlock your phone to continue" but i currently don't have any screen locks or anything, just swipe. i have a pure edition running on 5.1. Skeptical about a reset since the phone is still responsive.. tried looking for other fixes, but looks like this issue is just coming up today...
This exact same thing happened to me. Updated to 5.1 about a week ago via the OTA. Wiping cache did nothing. Diagnosing it as a software issue, I attempted to sideload the official 5.1 OTA that's posted elsewhere in the forums. It came back as installation aborted, so I gave up on any hope of keeping my data and did a factory reset. Now all it does is bootloop, sometimes settling on the prone android no command screen for a little while. I can boot into recovery and the bootloader, but thats it. Really hoping someone can come up with a solution. XT1096.
AGISCI said:
After the factory reset bootup takes longer than normal, how long did you wait?
If that is not the case, what model moto x do you have? For example mine is xt1095. Also what version of android do you have? 5.0, 4.4.4, 5.0.2, 5.1, etc?
Sent from my XT1095
Click to expand...
Click to collapse
I've waited about 30 minutes, in this time my phone just bootet into the recovery by his self. I've contacted Motorola and I'll send my device to repair.
It's a xt1092 with 5.1 RETDE.
I personally think that this issue is caused by the Boot animation update.
swankylaxplayer said:
This exact same thing happened to me. Updated to 5.1 about a week ago via the OTA. Wiping cache did nothing. Diagnosing it as a software issue, I attempted to sideload the official 5.1 OTA that's posted elsewhere in the forums. It came back as installation aborted, so I gave up on any hope of keeping my data and did a factory reset. Now all it does is bootloop, sometimes settling on the prone android no command screen for a little while. I can boot into recovery and the bootloader, but thats it. Really hoping someone can come up with a solution. XT1096.
Click to expand...
Click to collapse
Flash the stock 5.1 logo, kernel, system, modem, baseband and recovery for the XT1096 - the full image files are available.
JulesJam said:
Flash the stock 5.1 logo, kernel, system, modem, baseband and recovery for the XT1096 - the full image files are available.
Click to expand...
Click to collapse
Thank you! I don't know how I missed that! Back in business now.
nrsmsn said:
also have the same issue, black screen after reboot. moto voice, active display/notifications are responsive, camera too when twisting the phone. moto voice says "unlock your phone to continue" but i currently don't have any screen locks or anything, just swipe. i have a pure edition running on 5.1. Skeptical about a reset since the phone is still responsive.. tried looking for other fixes, but looks like this issue is just coming up today...
Click to expand...
Click to collapse
I have the exact same problem. Any fix?
Edit: Can't get adb to recognize phone. Phone is rooted.
kunal_07 said:
I have the exact same problem. Any fix?
Edit: Can't get adb to recognize phone. Phone is rooted.
Click to expand...
Click to collapse
Have you tried reflashing the system image from the bootloader?
is that possible without adb? If so, can you tell me how?
kunal_07 said:
is that possible without adb? If so, can you tell me how?
Click to expand...
Click to collapse
You still do everything through terminal. You have to cd to your folder that has adb and fastboot enclosed, usually platform-tools. Instead of starting each command with "adb", you'll start with "fastboot" and you'll be flashing these while your phone is at the fastboot screen.
The full image files are in the forums, and all the commands you'll need, in order, are posted in this thread earlier
I have found that some time the fastboot from Moto wouldn't recognize the phone. I, then, use the mfastboot-v2 found somewhere around this forum works great.
Me too faced this problem few days back. Only option left to do was factory reset.
Read below just to go through of what i faced:
( I had gone through bunch of articles for restoring my data but i had a pin lock because of which while connecting to pc it couldnt detect phone.
Other things i tried includes flashing lockscreen bypass zip via stock recovery. There i faced signature verification failed error because i had done it through stock recovery where it doent let u toggle signature verification on/off as in CWM. )
And for those who wants their data back , i found many articles of data recovery after factory reset. But it needed your device to be rooted. All you have to do is after factory reset dont make use of phone and after rooting you can recover your phone by software as EASEUS android recovey, Dr fone android recovery. Thats all .
I am too facing this issue as of last night,, I have the verizon version (complete stock, no root, locked bootloader) and I am not sure how to go about fixing this without losing all my data.. I tried wiping cache but it did nothing.. Can anyone provide some kind of troubleshoot guide please? It would be much appreciated.
A friend of mine is also having the same issue.
I tried the 5.0 image and it won't flash.
I'm locked and without root. Is it even possible to flash even the factory images? (And yes, I've tried to go to the Customer Portal for the Moto X and that isn't giving me anything)
Edit: Finally got it to flash the stock image. Didn't help. Factory reset fixed things.
Note: I had this problem and was able to fix it through a factory reset, but I had to do it through minimal adb and fastboot. The bootloader factory reset option didn't work.
I am having the exact same issue. Has anybody had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a bunch people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
I had a rooted, unlocked, unencrypted stock firmware running lyz28j. I then sideloaded, and had it re-encrpyt with lyz28j. I then wanted to go back to lock the firmware, so I locked it via fastboot, rebooted, and now it's just doing the dancing balls boot thing. It has been for 2-3 hours. So i've tried googling, found a few with the same issue, but now I am stuck because the device is locked status code 2. I tried fastboot format and fastboot format userdata and rebooted, gave it a half hour, still dancing.
I also tried nexus root toolkit with no luck.
Not sure what else I can try? I do not care if I lose data, as I already backed up, so I am down to try anything.
vivithemage said:
I had a rooted, unlocked, unencrypted stock firmware running lyz28j. I then sideloaded, and had it re-encrpyt with lyz28j. I then wanted to go back to lock the firmware, so I locked it via fastboot, rebooted, and now it's just doing the dancing balls boot thing. It has been for 2-3 hours. So i've tried googling, found a few with the same issue, but now I am stuck because the device is locked status code 2. I tried fastboot format and fastboot format userdata and rebooted, gave it a half hour, still dancing.
I also tried nexus root toolkit with no luck.
Not sure what else I can try? I do not care if I lose data, as I already backed up, so I am down to try anything.
Click to expand...
Click to collapse
If have TWRP can move a rom from PC to Internal storage and flash it. That about only chance I think.
and if you have stock recovery, theres nothing that you can do except try to get a refurbished phone in exchange.
wow, I got kind of lucky this worked, but I went to recovery, power + up button at the lil ! dude and wiped device, rebooted, and it let me in.
It even barked about a few mounts not existing, or being able to write to them.