Related
Hi all,
Running into issues with the new 5.1 factory image. After flashing, booting up, setting up my google account, and enabling the new Allow OEM Unlock setting in dev options, I jump to the bootloader to relock. I've tried running the lock from both fastboot and mfastboot. In either case, it says locking was successful, sets the lock status to (2). I hit Start (or fastboot reboot, etc.) and it hits the Google splash (no unlock icon at the bottom), quickly reboots, goes to Google splash, and then sits at the system update screen... the one with the green android/open chest/blue spinning wireframe. It never passes this. If I erase the cache, it hangs at the spinning colored dots splash screen forever. If I unlock, erase userdata and cache, it'll boot fine, but I'm back to where I was in the first place... data reset, unable to lock the bootloader.
I *have to* lock the bootloader because of stupid Mobile Iron requirements from work. Any ideas? My goal is to have a full factory install, unrooted, locked, on 5.1 so I can install Mobile Iron.
Thanks!
Have you tried flashing the full factory image a second time? Maybe do each part separately
rootSU said:
Have you tried flashing the full factory image a second time? Maybe do each part separately
Click to expand...
Click to collapse
Yeah, I've tried multiple times with flash-all (both latest fastboot and modified to use mfastboot) and got the "error: update package missing system.img" error so I used mflashboot to flash the bootloader, radio, recovery, boot, system, cache, and userdata partitions.
I have not tried an OTA.
So full history: device was brand new about 2 weeks ago (t-mobile), came with 5.0.1. I never unlocked it or rooted or anything up until yesterday when I tried to flash the full factory 5.1 from google as described above. I downloaded the full 5.1 image, booted into fastboot, did "fastboot oem unlock", tried flash-all, hit that error, individually flashed everything. Unlocked dev options, enabled oem unlock setting, back into fastboot, 'mfastboot oem lock', this issue.
Trying to go back to 5.0.1 right now to see if I can at least get it back up and running with Mobile Iron.
negativefx said:
Trying to go back to 5.0.1 right now to see if I can at least get it back up and running with Mobile Iron.
Click to expand...
Click to collapse
Same problem on 5.0.1. Sigh.
Interesting though, if I try the lock, reboot, get the system update screen, and force it back into bootloader (vol down+power) and run oem unlock, I still get the system update screen. Have to blow away the cache to get it to boot.
Not sure if it matters but when unlocked, status code is 3, when locked, it goes to 2. I didn't pay attention to what the code value was prior to unlocking the first time.
The codes are accurate
rootSU said:
The codes are accurate
Click to expand...
Click to collapse
Any idea beyond this? Could it have something to do with the encrypted storage?
I might try flashing another rom and recovery and working from there.
Strange... the OEM unlocking setting in dev options doesn't seem to stick between restarts. I have to set it each time. Is that expected behavior?
negativefx said:
Strange... the OEM unlocking setting in dev options doesn't seem to stick between restarts. I have to set it each time. Is that expected behavior?
Click to expand...
Click to collapse
On 5.1 it is.
No idea though ultimately
I managed to get it to lock finally. I don't remember the exact combination but it eventually prompted me during reboot to provide my pass for the encrypted storage and I tried my PIN, that didn't work. Went in to fastboot, reflashed userdata and cache, went to android device manager on my PC and did a remote wipe. After that, it let me lock.
negativefx said:
Hi all,
Running into issues with the new 5.1 factory image. After flashing, booting up, setting up my google account, and enabling the new Allow OEM Unlock setting in dev options, I jump to the bootloader to relock. I've tried running the lock from both fastboot and mfastboot. In either case, it says locking was successful, sets the lock status to (2). I hit Start (or fastboot reboot, etc.) and it hits the Google splash (no unlock icon at the bottom), quickly reboots, goes to Google splash, and then sits at the system update screen... the one with the green android/open chest/blue spinning wireframe. It never passes this. If I erase the cache, it hangs at the spinning colored dots splash screen forever. If I unlock, erase userdata and cache, it'll boot fine, but I'm back to where I was in the first place... data reset, unable to lock the bootloader.
I *have to* lock the bootloader because of stupid Mobile Iron requirements from work. Any ideas? My goal is to have a full factory install, unrooted, locked, on 5.1 so I can install Mobile Iron.
Thanks!
Click to expand...
Click to collapse
I see you got it to work :good:, but just a little explanation:
The N6 forces a wipe when you lock the bootloader. And sometimes it hangs. What you need to do is boot into the stock recovery after you have locked your bootloader and do a factory reset. Then you should be able to boot normally with a locked bootloader.
I unlocked the bootloader and rooted my device but then recovery mode wouldn't load; it just gave me the exclamation mark android and wouldn't go into recovery. So, I downloaded TWRP to have a recovery that would load. I then attempted to let the system update itself to 5.1 and it went into TWRP recovery and didn't update. I decided to download the shamu 5.1 from google dev and flash it from the bootloader. I kept getting the error "could not allocate ######### bytes" so I thought I must need to erase all the partitions and load them back one by one. I flashed boot, cache, recovery, and user data, but got the same error on the system partition. I tried to enter recovery to attempt to wipe the data and just got the exclamation mark android so I thought I should lock and unlock the bootloader to force it to clear its data. I locked the bootloader but it will not unlock now; it says "Check 'Allow OEM Unlock' in Developer Options" but the phone will not boot past the google logo. Any advise?
Jesus, error after error there. You should have stopped and asked advice before carrying on.
Well if you haven't got TWRP anymore, you're screwed. You'll have to send it back to moto/google for repair. There's no way out if you haven't got TWRP.
In regards to the mistakes...
- standard recovery gives exclamation mark. Press volume up and power to get to the menu
- you cannot update officially OTA if you are modified at all, including custom recovery
- the error about system was because your fastboot is out of date
- once you lock the boot loader, you can not unlock without a booting OS.
- if you have a broken OS and stock recovery, you can not fix the OS.
Ouch. Yes, this is pretty much a prime example of what not to do in each situation.
As @cam30era always notes, to enter stock recovery, when dead Android appears with red exclamation point, HOLD power and press volume up once.
Sorry you lost your device but if you had read a little before jumping into bad decisions, this could have been avoided. Hope you get a working device soon and next time, ask for help.
ouch..
yea, time to try and RMA it.
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?
Trying to recover data after XT1096 5.1 black screen bug
So I encountered this bug about 2 days ago. It's basically a bug that results in an un-responsive black screen for no apparent reason. I tried all the standard support protocols to save my data (i.e. copy files to pc via USB, and using Cellebrite to pull them off) but without MTP or USB Debugging enabled none of these options worked. Both Verizon and Motorolla tech support advised me to factory reset my phone. However being that a reset will wipe all my data, I've refused to go down that path (yet). So after doing some of my own research I came up with the following ideas, which so far have not been successful.
Idea 1 - use adb to sideload an OTA update with a fresh image that will hopefully resolve the black screen bug but not wipe my data. I followed this thread with partial luck. I got about 47% through the sideload process before it crashed complaining about an invalid full image check
Idea 2 - use fastboot to flash all the images except user data (again with the hopes of resolving the black screen bug without losing data) - But I can't seem to find a compatible set of stock images that will play nicely with my unrooted and locked bootloader phone.
Idea 3 - root my phone, load a custom rom (with no black screen bug) and preserve my user data - unfortunately mofo doesn't support an XT1096 root since I've already accepted the 5.1 OTA.
So my question are:
1 - Are there a set of verizon stock digitally signed images anywhere out there that will work with my XT1096 with 5.1 already installed?
if not
2 - Is there any way to root my phone or unlock the bootloader so that I can accept non-factory images without the use of Mofo?
Any help with this is greatly appreciated.
rushramia said:
So I encountered this bug about 2 days ago. It's basically a bug that results in an un-responsive black screen for no apparent reason. I tried all the standard support protocols to save my data (i.e. copy files to pc via USB, and using Cellebrite to pull them off) but without MTP or USB Debugging enabled none of these options worked. Both Verizon and Motorolla tech support advised me to factory reset my phone. However being that a reset will wipe all my data, I've refused to go down that path (yet). So after doing some of my own research I came up with the following ideas, which so far have not been successful.
Idea 1 - use adb to sideload an OTA update with a fresh image that will hopefully resolve the black screen bug but not wipe my data. I followed this thread with partial luck. I got about 47% through the sideload process before it crashed complaining about an invalid full image check
Idea 2 - use fastboot to flash all the images except user data (again with the hopes of resolving the black screen bug without losing data) - But I can't seem to find a compatible set of stock images that will play nicely with my unrooted and locked bootloader phone.
Idea 3 - root my phone, load a custom rom (with no black screen bug) and preserve my user data - unfortunately mofo doesn't support an XT1096 root since I've already accepted the 5.1 OTA.
So my question are:
1 - Are there a set of verizon stock digitally signed images anywhere out there that will work with my XT1096 with 5.1 already installed?
if not
2 - Is there any way to root my phone or unlock the bootloader so that I can accept non-factory images without the use of Mofo?
Any help with this is greatly appreciated.
Click to expand...
Click to collapse
1) Yes there are stock signed images for the xt1096. They won't fix your problem. The problem is the data partition is corrupt. Flashing a stock image does not change nor fix the data partition, so it won't help.
2) No, there is no other way.
I am sorry to say, but there is only one solution, which is factory reset. The reason factory reset works is because it will erase the corrupted data partition. Sorry, but you will lose your data, there is no way to recover now. Since you have 5.1 installed, it is also impossible to use mofo and sunshine, so no root and no bootloader unlock neither.
I'm in the same boat except I'm on vacation with out my computer. Can I factory reset from fastboot?
Yes you can. Once you are in fastboot select recovery. Once you are in recovery and see the dead android press power and volume down to open the menu, then select factory reset.
Sent from my XT1095 using Tapatalk
AGISCI said:
1) Yes there are stock signed images for the xt1096. They won't fix your problem. The problem is the data partition is corrupt. Flashing a stock image does not change nor fix the data partition, so it won't help.
2) No, there is no other way.
I am sorry to say, but there is only one solution, which is factory reset. The reason factory reset works is because it will erase the corrupted data partition. Sorry, but you will lose your data, there is no way to recover now. Since you have 5.1 installed, it is also impossible to use mofo and sunshine, so no root and no bootloader unlock neither.
Click to expand...
Click to collapse
Thanks Chris,
I appreciate the response. Do you know where I might find the stock signed images for xt1096? I've somehow hosed my system img so now I can't even get into recovery to do a factory reset (keeps complaining 'failed to validate system image'). I'm hoping to re-flash the stock system.img to fix this problem. Let me know.
Thanks!
Sure here it is:
download
Sent from my XT1095 using Tapatalk
AGISCI said:
Sure here it is:
Click to expand...
Click to collapse
Thanks!
That got me back to where I started. System is no longer 'invalid' and my phone boots up to a black screen. The notifications still work and I can boot into fastboot or recovery modes. I guess my only option now is to bite the bullet and factory reset now (and loose my data). :crying:
Thanks again for all your help!
AGISCI said:
Yes you can. Once you are in fastboot select recovery. Once you are in recovery and see the dead android press power and volume down to open the menu, then select factory reset.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
weird. I go into fastboot and got the options: normal boot, recovery, factory and some others and i can cycle through with vol down. vol up is select but no matter what i select it just boots normally (still have black screen)
do i need to unlock something?
I need some more info. Are you on stock rom? What version(4.4.4, 5.0, or 5.1)? Have you unlocked your bootloader with sunshine? Have you rooted woth mofo or kingroot?
Sent from my XT1095 using Tapatalk
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'.