I just got my Moto X 2014 Pure Edition in the mail yesterday and now I've gone and tried to root it.
I had already unlocked the bootloader and then being giddy I installed android 5 since I wanted to try it out. From here, I messed up. I tried to root it using the Superboot method. Unfortunately, I didn't realize this was for the 4.4.4 build.
After flashing the image, I was able to get back into the OS, but I wasn't able to install apps or get to the home screen. I could still browse still open chrome windows, but I couldn't get to home. Next, I tried CF Auto Root, as that was built for 5.0. Executed just fine, but when I got back into the phone, I kept having the same problem. Now when I boot, It gets past the moto animations and then sits on the moto logo that looks like water. It just stays there.
If I try to turn off the phone, it just repeats this. If I put it into fastboot mode, it can act in there just fine. So I tried getting into recovery, but when I got back to the android on it's back saying "NO COMMAND.", I tried holding down up and power, just like everyone says. Doing this, though, reboots the phone normally and it goes back to the same problem as it was before!
If anyone has any suggestions, I'd really appreciate it. I'm having a mild breakdown right now
afran646 said:
I just got my Moto X 2014 Pure Edition in the mail yesterday and now I've gone and tried to root it.
I had already unlocked the bootloader and then being giddy I installed android 5 since I wanted to try it out. From here, I messed up. I tried to root it using the Superboot method. Unfortunately, I didn't realize this was for the 4.4.4 build.
After flashing the image, I was able to get back into the OS, but I wasn't able to install apps or get to the home screen. I could still browse still open chrome windows, but I couldn't get to home. Next, I tried CF Auto Root, as that was built for 5.0. Executed just fine, but when I got back into the phone, I kept having the same problem. Now when I boot, It gets past the moto animations and then sits on the moto logo that looks like water. It just stays there.
If I try to turn off the phone, it just repeats this. If I put it into fastboot mode, it can act in there just fine. So I tried getting into recovery, but when I got back to the android on it's back saying "NO COMMAND.", I tried holding down up and power, just like everyone says. Doing this, though, reboots the phone normally and it goes back to the same problem as it was before!
If anyone has any suggestions, I'd really appreciate it. I'm having a mild breakdown right now
Click to expand...
Click to collapse
Easiest thing to do is to go to:
https://accounts.motorola.com/ssoau...edirect/standalone/bootloader/recovery-images
and log in then find the right link for Moto X Pure Edition and click the "Request Firmware" link. When you get the email giving you access to the link then following the instructions for flashing it via fastboot.
crpalmer said:
Easiest thing to do is to go to:
and log in then find the right link for Moto X Pure Edition and click the "Request Firmware" link. When you get the email giving you access to the link then following the instructions for flashing it via fastboot.
Click to expand...
Click to collapse
Thank you so much for this! I had eventually found a fix through a lot of tinkering, but thank you for replying with the link for the firmware. I was looking everywhere for it!
I had the same issue. I have no idea what I did to cause it. Eventually I found a fix somewhere to fastboot into twrp recovery from the computer, and fix the file system. Then I flashed kitkat and updated from there.
Sent from my Nexus 5 using XDA Free mobile app
Recovery image or fix?
can you guys post your fixes? I am stuck with the same issue and have been waiting for over an hour for Moto to send me the recovery image. Thanks!
Xtchico..look at solartrans guide to get on lollipop. You basically have to downgrade to 4.4.4...then you'll get the 5.0 ota ..then use the tools to unlock..root and install recovery.
That's what worked for me. I was stuck on the water ripple M .
Sent from my XT1095 using XDA Free mobile app
fastercon said:
Xtchico..look at solartrans guide to get on lollipop. You basically have to downgrade to 4.4.4...then you'll get the 5.0 ota ..then use the tools to unlock..root and install recovery.
That's what worked for me. I was stuck on the water ripple M .
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
This is exactly the guide that I used and the fix action which worked for me. Thank you sir for finding it! I'd been trying to find it to give him credit. It works wonders and I haven't had an issue since.
Rooted my phone, loaded my applications and tweaked it to my liking. Now all that's left is to activate it.
Related
As for the Moto X my issue seems isolated. Heres what happened.
1.After successfully gaining root access on 4.4, I notice one big problem. My touchless control wouldn't activate via saying ok google now unless I was google search. I tried everything I could to get it to work (check my recent post) but going back to 4.2.2 to re-slapmymoto was the only option.
2.Flashed to 4.2.2 using RSD Lite. Good news is touchless control worked again. Now the disappointing news...
3.Before slapping I wanted to see what was lost and what stuck after flashing, so I checked my write protection. It came back '0'. Check for root access, it showed su: not found or in other words, not rooted.
4.I was going through the rockmymoto process then hit a snag. After entering the dalvikvm code into puttytel/telnet, it took me straight to step 3 and did absolutely nothing (see picture). I waited for 1min anyways and checked root again...no dice. Adb rebooted the device, reconnected to puttytel and checked again...nothing.
I've searched for about 4hrs straight trying to figure this out. Is there really no way to root again???
Verizon Moto X (currently 4.2.2)
I've been reading that if you downgrade to 4.2.2 then receive OTA update you will brick the phone, be careful.
sent via tapatalk
SPACE-AGE-INC said:
As for the Moto X my issue seems isolated. Heres what happened.
1.After successfully gaining root access on 4.4, I notice one big problem. My touchless control wouldn't activate via saying ok google now unless I was google search. I tried everything I could to get it to work (check my recent post) but going back to 4.2.2 to re-slapmymoto was the only option.
2.Flashed to 4.2.2 using RSD Lite. Good news is touchless control worked again. Now the disappointing news...
3.Before slapping I wanted to see what was lost and what stuck after flashing, so I checked my write protection. It came back '0'. Check for root access, it showed su: not found or in other words, not rooted.
4.I was going through the rockmymoto process then hit a snag. After entering the dalvikvm code into puttytel/telnet, it took me straight to step 3 and did absolutely nothing (see picture). I waited for 1min anyways and checked root again...no dice. Adb rebooted the device, reconnected to puttytel and checked again...nothing.
I've searched for about 4hrs straight trying to figure this out. Is there really no way to root again???
Verizon Moto X (currently 4.2.2)
Click to expand...
Click to collapse
Lol,you won't brick.
To get phone rooted again since you already have write protection turned off, just use slapmymoto instead of rockmymoto. I know you said you were on 4.2.2 but the write protection turned off will not let rockmymoto complete.
Good luck and hope this helps!
eksasol said:
I've been reading that if you downgrade to 4.2.2 then receive OTA update you will brick the phone, be careful.
sent via tapatalk
Click to expand...
Click to collapse
Klown80 said:
Lol,you won't brick.
To get phone rooted again since you already have write protection turned off, just use slapmymoto instead of rockmymoto. I know you said you were on 4.2.2 but the write protection turned off will not let rockmymoto complete.
Good luck and hope this helps!
Click to expand...
Click to collapse
I love you
SPACE-AGE-INC said:
I love you
Click to expand...
Click to collapse
I'm having the exact same problem as OP doing the exact same thing WP 0 etc.. I used SlapMYMoto, after the reboot on step 2 I waited about 5 minutes installed Supersu and same error OP was getting, thoughts?
Well I am surprised I received the 5.0.1 update notification but after agreeing and letting device restart, it didn't happen and device claims that is up to date and still on 5.0
Did Google retired the OTA?
Your not alone im having the same issue. My 6 is on verizon and the same issue has happened that you described. Cleared data in the frame service. Phone claims up to date...still 5.0
Darn it....
At least AT&T and Verizon respect the "direct updates form Google" advantage of the Nexus brand.
Anyone able to help?
If you've flashed a custom recovery and/or are rooted, the OTA will fail. It will just reboot without doing anything, then the OTA disappears when back in Android and autoupdate says you're up to date.
You can download the image from the Nexus factory images site, extract the system and radio images, and flash them yourself with either fastboot or Nexus Root Toolkit.
This post gave me the idea:
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
And here's the link to the latest N6 image from Google:
https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
You'll need WinRAR or similar to extract the download from Google.
It failed for me too, bone stock. Connect your phone to a charger . it reappear and I was able to update
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Same here.... Verizon/Stock Nexus 6. Mine didn't even reboot. After I chose to accept the update, screen just flashed to up-to-date. Now claiming up-to-date each time.
Strange I'm in the UK and have the exact same problem. Got a notification thru last night for the 5.0.1 update, decided to leave it until this morning and it's gone. Must be something to do with Google.....
I am bone stock and have the same issue . Last night it said there was a new update and I said ok lets do it.. It said it was going to restart and then it never restarted or nothing and says its up to date even though its on 5.0 . I am on verizon !!!
StrangeTimes said:
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Click to expand...
Click to collapse
Immediately. I guess I was lucky
I did not root/installed custom ROM neither, which boost the upset. But again, I am glad that I should not worry for update delays due the device being from a carrier's branded, and evidently I am not the only one, I will give Google the opportunity before opting for manually flash the update which that means dealing with an 20+ GB backup first.
Sent from my Nexus 6 using XDA Free mobile app
Question
Hey i was wondering, I got my OTA update last night and of course my phone is unlocked and rooted but i still attempted to download and install it. I was successful in downloading the update and my device rebooted. I shortly got the error message so i rebooted the device and when i logged back on i was still on 5.0 and the OTA notification is now gone.
My question is, since i downloaded 5.0.1 and the device rebooted in the attempt to complete the install will this now cause my phone to no longer get the 5.0.1 update notification? I plan on unrooting once i get the notification so i can go ahead and OTA and when that is completed root the phone again. Or am I now forced to flash a factory reset in order to get that OTA update again?
ideally i would prefer to wait for the OTA so i dont have to factory reset.
ATT Stock
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
gleonard3 said:
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
Click to expand...
Click to collapse
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
You are correct! Thanks. Reading elsewhere had it backwards. This worked. Off to update now. Thanks again.
No worries bud
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Do I need to be rooted to flash update? On my one plus I could download update and the go to recovery and flash it.
Tia,
Ian B
Slorks said:
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just for literally a second or so..
Hi, I just got my new phone yesterday, and I"m having issues actually turning the thing on. Yesterday, everything was going fine. Since I got the pure edition, I went ahead and unlocked the bootloader, and then ran the Auto Root program I found in the general section. After that, I installed some apps that I needed. I downloaded some videos to watch later, I downloaded some music, and then I installed AdAway.
Here's where I probably screwed up big time: I disabled some applications from the app picker (Help, E-Mail, and a few others). I was having some trouble with the Inbox app searching properly, so I re-enabled Gmail at least, but I left the others disabled. Then I connected the phone to my Coolstream Duo, which is a bluetooth audio device, and then went to sleep.
When I woke up, I was able to unlock my phone, but I unlocked it to only the back button available and Google+ on the screen. Nothing functioned, so I force powered off. Now I can't turn the device on, it either is stuck on the "Warning, unlocked bootloader" screen, or gets to the Motorola globe boot screen, playing half the animation before the screen goes black. Once, I booted and it got past all that to the "Android is upgrading" screen, and it optomized 38 apps, but then after it got to the unlock screen, the pattern wouldn't show up. I followed these factory reset instructions: https://motorola-global-portal.cust...detail/a_id/101072/p/30,6720,9197/reg/2380937 and they didn't seem to do anything. I also attempted to download the stock image for Android 4.4.4 but it said I wasn't allowed to access the file.
If anyone could recognize what I did wrong to my phone, that would be great, and if anyone could provide a link to a factory image of the phone so I can attempt to restore it, that would be awesome as well.
Sounds like flashing the 4.4.4 system image may solve your problem. Here is a link where you can grab the fxz without asking for permission from Moto.
https://onedrive.live.com/?cid=227f...20267&ithint=folder,&authkey=!AMWPTB3ICDtezYs
Dark9781 said:
Sounds like flashing the 4.4.4 system image may solve your problem. Here is a link where you can grab the fxz without asking for permission from Moto.
https://onedrive.live.com/?cid=227f...20267&ithint=folder,&authkey=!AMWPTB3ICDtezYs
Click to expand...
Click to collapse
Oddly enough, directly after writing this post, I stepped out of class to find my phone had booted and was on the welcome screen. But if anything bad happens again, I'll be sure to have this link ready! Thanks for the help!
Dark9781 said:
Sounds like flashing the 4.4.4 system image may solve your problem. Here is a link where you can grab the fxz without asking for permission from Moto.
https://onedrive.live.com/?cid=227f...20267&ithint=folder,&authkey=!AMWPTB3ICDtezYs
Click to expand...
Click to collapse
Hi,
can this stock rom get flashed trough fastboot or rsd lite? Maybe you can solve my problem!
incrazyboyy said:
Hi,
can this stock rom get flashed trough fastboot or rsd lite? Maybe you can solve my problem!
Click to expand...
Click to collapse
Either. The only thing with rsd lite is that it does not like USB 3.0. Your computer will need a USB 2.0 slot.
Dark9781 said:
Either. The only thing with rsd lite is that it does not like USB 3.0. Your computer will need a USB 2.0 slot.
Click to expand...
Click to collapse
Great! I would prefer flashing trough fastboot. Could you give me the instructions please?
Hi all, I was running a CM ROM on my Droid Turbo and recently flashed back to stock using a backup I created with TWRP, because I was tired of not having GPS capabilities.
Now that I’m running stock (still rooted), I’ve been getting a notification to do an OTA update. When I allow the update to install, it restarts my phone and sends me straight to the TWRP recovery and does nothing else. Rebooting gets me stuck in a loop where it keeps sending me to recovery. Clearing out my cache got me out of the loop but after a day or so, the annoying install message comes back.
I noticed an error message when I looked at the log screen in TWRP. As best I can transcribe it, it says:
Package expects build fingerprint of motorola/quark_verizon/quark:5.1/SU4TL-44/44:user/release-keys or Motorola/quark…. ; this device has Motorola/omni_quark/quark:5.1.1/LYZ28E/1:eng/test-keys
Does anyone have any idea what’s going on with my phone – why I can’t take the OTA? Any advice on how to fix the problem or get this stupid upgrade notification to go away? The notification takes over the device every time you unlock the screen so it’s driving me crazy.
Thanks in advance for any help!
I think you need stock recovery and bootloader.
GPS issues have long been solved, using the "clear modem" file. You sent back to stock for nothing.
If you really want SUTL-49 there's plenty of downloads to manually flash it. You don't need the OTA.
Thanks for the replies. I think I'm going to stick with stock now. Have been enjoying the Motorola features like the hands-free driving thing and I wasn't seeing any advantage running CM anymore. Can I flash SUTL-49 using TWRP or do I have to hook to a PC and use ADB?
shinydiamond said:
Thanks for the replies. I think I'm going to stick with stock now. Have been enjoying the Motorola features like the hands-free driving thing and I wasn't seeing any advantage running CM anymore. Can I flash SUTL-49 using TWRP or do I have to hook to a PC and use ADB?
Click to expand...
Click to collapse
You can flash it with TWRP from here:
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
Thank you!
I rooted my XT1052 straight after updating to 5.1, a few years back. As a result I have never been able to install the OTA update (the one which fixed Stagefright, so far as I'm aware it's the only OTA Moto did after the 5.1 update.)
I've been unable to install a few apps recently due to SafetyCheck failing on the rooted phone, so yesterday I decided I would unroot and return to stock, which would also enable me to install the bugfix OTA. (And with Magisk, nowadays we can keep root access without a modified system partition.)
I didn't have a stock image (or I had an image of some sort on a hard drive but couldn't remember its provenance). Moto's download page has images for the XT1053 but not the XT1052… Eventually I found firmware.center, where (I thought) I found the right image.
However, when flashed it (following the step-by-step guides which are the same on various pages, including Moto's own instructions), it failed to flash the `system` image. I got messages about invalid block sizes (IIRC) and then an error saying the image was corrupt (it wasn't; I checked the MD5).
This left me unable to boot. So I downloaded LineageOS (I'd been considering switching to LineageOS anyway to get Android 6), and was able to flash it from TWRP without any issues (other than the fact that a newer version of TWRP is required than the one published on their website…)
All well and good – except that now, when I turn my phone on it goes straight into Recovery (TWRP). Initially I could only get System to boot by starting the bootloader (Pwr+VolDn) and selecting 'BP Tools', which would cause it to boot normally. (I found this by trial and error.) Now, after re-flashing the boot image, It also works if I select Standard Boot from the bootloader. But I still have to select it manually. If I just turn the phone on normally, with the power button, it always boots into Recovery. Also, all the 'reboot' options from fastboot/adb or TWRP all boot to Recovery.
Now, I think I know what I did wrong. The stock image I downloaded was 'XT1052_GHOST_RETGB_5.1_LPAS23.12-15.5-1_cid7_CFC.xml.zip', but my system version before was 5.1_LPA23.12-15.5. I just assumed that the 5.1_LPAS23.12-15.5-1 version was a minor update – likely with the Stagefright OTA installed – so I went for that. But probably I should have gone for the exact version I already had installed.
Searching these forums and the wider web, I haven't found anyone with the exact same issue. But from similar issues, I decided I needed to re-flash the partition table (gpt.bin). I took the gpt.bin image from an older 5.1 ghost ROM I had saved, but I'm not able to flash it – the bootloader shows security warnings when I try.
So I'm stuck now – I have tried pretty much everything I can think of.
If anyone has any ideas I'd be very grateful!
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Alexjrbr said:
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Click to expand...
Click to collapse
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
cmjs said:
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
Click to expand...
Click to collapse
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Alexjrbr said:
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Click to expand...
Click to collapse
Woohoo! Well done!
Look forward to seeing your solution
cmjs said:
Woohoo! Well done!
Look forward to seeing your solution
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Moto X 2014 XT1092
Alexjrbr said:
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Click to expand...
Click to collapse
Can this solution be used in my case. I have the same problem of the phone booting to recovery on start up...