Hi,
I own a Moto X DE for few days. It runs Kit Kat, and is unlocked and rooted with TWRP. Today, I've got a notification about an OS update. But when I try to update my system, the phone reboots on the TWRP menu, and no way to update.
Any idea about this?
Thanks.
I have a the T Mobile (Same as Dev). Had it rooted and bootloader unlocked. I didn't really care for saving data tbh. So what I did was return to stock.
Already had the 4.4 in my fastboot folder. So I booted into recovery and wiped everything.
Then went back to download mode and fastbooted the T-Mobile 4.4 version. Ran phone setup, check for update and installed. Took about 10 minutes max.
Though of course this is one way out of a few. The stickies in this section have the various ways. Find one which better suits you.
Do note you should not take OTA with root and a custom recovery
Sent from my XT1053 using Tapatalk
Thanks, should have read a bit before asking. Sorry, and thanks again for the help.
Related
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.
I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
You're not alone. Several threads on this in general forum and Q&A. Consensus so far is hang tight and the update should resurface.
Sent from my Nexus 6 using XDA Free mobile app
Factory image is still on Google website. Grab it there.
bluh5d said:
I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
Click to expand...
Click to collapse
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
If I manually flash the image will it change where my future otas come from ? Like doesnt a motorola nexus 6 updates come from a different server than a google play nexus 6 ?
Same thing for me, except I was waiting to be able to charge up my phone before installing. By the time I got to a charger it was gone. I'll probably just wait for it to resurface.
Same same here. Fully stock. Is the common theme for people experiencing this that they are on VZW? I am. Tmo bought phone with VZW sim.
Fyi, rebooting and charging havent helped.
I know i can manually update, but I'm hoping to confirm that the OTA process still works correctly with my stock phone running on VZW.
Its not only VZW.. I'm T-Mobile and the same happened
SirRastusBear said:
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
Click to expand...
Click to collapse
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
mlevin said:
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
Click to expand...
Click to collapse
Flashed each separately.
Flash bootloader image
Reboot bootloader (important)
Flash radio image
Flash recovery image
Flash boot image
Flash system image (takes a while)
Flash userdata image ONLY if you want to wipe your own data
Reboot when done
Flash custom recovery
Install SuperSU from custom recovery
Reboot
Profit
Cheers
Those like me who don't want to manually flash.. I just got off the phone with Google, and apparently within 24-48 hours the update will be available again for those devices affected by this hiccup. I'll wait.
I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?
Asisentr said:
I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?
Click to expand...
Click to collapse
I'm in the same boat (although mine is not dev edition, I have unlocked the bootloader & rooted running xposed) and would love an answer!
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
You can't update if you've modified the system partition, ex. being rooted, having xposed etc.To update you need to be completely stock.
I received the same notification on my XT1060DEV. I chose to ignore it.
Anyone know what the update is for? Someone posted in the general section to "never update a rooted unlocked XT1060 ever" because it bricked it or something. My guess is they didn't know what they were doing. I've been having issues lately with my XT1060 not wanting to connect to 2.4GHz wireless networks, only 5GHz. I've tried removing apps one-at-a-time but no luck. Maybe a reset back to square one and the update is due.
Not sure what the update is for though.
So I'm unlocked and rooted on 5.1 with TWRP... but I don't have stock recovery. XT1060 verizon dev edition doesn't have a stock recovery for anything but 4.4.4. So how do I flash recovery to take the update? I'm assuming that flashing recovery from 4.4.4 is a bad idea? If so, what's the solution?
i have 2 1060s one is retail 16 gb (one daughter) the oher is 32 gig dev tooted twrp expoesd. dev daugher tried to do the update it failed and hten she rebooted. it kept tying to apply booting to recovery after 3 minutes and and failing until I removed the update form cache.
I shoul have captured it so I could examine and fix the script.
retail 16 gb updated just fine.
anybody know what this is?
if it not an image maybe we can apply the frixes directly
Mike7143 said:
Anyone know what the update is for?.......
Not sure what the update is for though.
Click to expand...
Click to collapse
Its the security update patch upto 1st April, 2016.
https://motorola-global-portal.cust...detail/a_id/110538/p/30,6720,8696/reg/1417809
I'm on completely stock 5.1 ROM but I have TWRP 2.8.7.0, Xposed installed. So in order for OTA to succeed I'll have to undo all the modifications including the removal of Xposed? The other changes I've made to the system are the removal of some of the Motorola bloatware.
The trick is now to get the right SBF from Motorola.
Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!
Mike7143 said:
Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!
Click to expand...
Click to collapse
Marshmallow?!
So far it's not to bad.
What do you mean by Marshmallow update!? This is just a security update so it should still be Lollipop.
Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
If you are boot-looping after trying the update with TWRP, you will have to delete the update file using TWRP.
From the TWRP main menu, Choose Advanced, then File Manager.
Go into /cache, and delete the Blur_Versionxxxxblahblahblah.zip file.
That'll stop your boot loop.
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
entermetallica said:
I just got a n6 today, and its running on 5.1.1. The marshmallow update came a long time ago so i thought it would update, but it showed that phone is up to date. Why is this so and how do i update?
Click to expand...
Click to collapse
First of all congrats on the new phone. I'm on AT&T and updates came too slow for me. I chose to flash a system image to get upgraded to marshmallow and now we can download ota's directly from Google to keep up to date. Cutting out the need to wait for our updates to be made available from the carriers. Edit: to be clear you have to flash the ota's as well.
I believe others have removed sim card to try to get ota via wifi. I think. Anyway good luck.
Sent from my SM-T700 using Tapatalk
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Dopamin3 said:
If you just got it today, good! Don't waste your time setting it up. Remove your SIM card and download the newest factory image "MOB30I" from here for the Nexus 6 (Shamu)
Just follow the instructions and you will be on the latest software. Then you should get OTA's normally from here on out. If you do it the Google recommended way it will wipe the phone so that's why I said don't set it up. If you already set it up it's going to be harder but you can manually flash the radio, bootloader, boot (kernel), and system with retaining your data but it's more hassle than it's worth.
Click to expand...
Click to collapse
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
entermetallica said:
Thank you for your help, Im trying to flash it as it says on the website, but my device is not recognized after I type adb reboot bootloader. The phone shows up in adb devices but not in fastboot.
Click to expand...
Click to collapse
Assuming you're using Windows, if you look in device manager do you see anything either with a red x or yellow exclamation mark? If so you are missing the driver. This thread has the driver zip and briefly explains how to install it via device manager. Once you get the driver installed it should work fine.
And I can't remember if you need to or not to flash the stock images, but you might need to unlock your bootloader. Tap the build number a bunch of times and you will have access to developer options, and there you might need to check "Allow OEM unlocking" or something like that. Again I'm not 100% sure if that's necessary or not. I've ran my bootloader unlocked since day 1 and haven't looked back.
The bootloader does need to be unlocked to flash anything at all, except for a Google-signed OTA image.
Thanks for the help, ive done it. I had to boot into fastboot, and then install drivers from device manager
Sent from my Nexus 6 using XDA-Developers mobile app
I recently pulled my old Note 3 out of the drawer to do some misc tweaks, and think i screwed it all up...LMFAO!!!
Quick specs of phone...
Samsung Galaxy Note III (AT&T SM-N900A) 64gb (yes, i said 64gb and not 32gb)...but NOT why I am posting, so please don't even comment about it.
Steps that led to where I am...
First off I will say the device was originally rooted 4.3 back in 2013, and never updated since. Today I decided I wanted to update the phone to the last OS that worked perfect for a root, no i didn't just update it. I followed SuperSU's & TWRP instructions on first bringing the phone back to stock, didn't work and left me in recovery mode. Again, doubtful but may have been caused by me. So I was left with a wipe/restore because every time I attempted recovery via OneClickBin it would fail. After wipe/restore I was able to reinstall SuperSU and device was still rooted, obviously. So I attempted to completely remove root through SuperSU and it just kept getting stuck on spinning wheel. So then I attempted to reinstall TWRP and now I am stuck at the screen shown below in screen shots. Thanks in advance for any and all assistance, regarding this matter.
-Semper Fi
Oh yeah...and I'm a total and permanent disabled Veteran who doesn't have the ability to "go to AT&T store". So lets please try to fix this without going anywhere. Thanks again in advance.
Wrong forum you want the. A&TT note 3 forum .
Sent from my SM-N930F using XDA-Developers Legacy app
If the phone doesn't have a locked bootloader, you can try flashing back to stock with Odin and then run ota updates until the phone is running the latest stock ROM.
AT&T variant have a locked bootloader. You can't use TWRP or any other custom recovery.
Please follow this guide to fix your softbrick, root and update.
zlazaar said:
AT&T variant have a locked bootloader. You can't use TWRP or any other custom recovery.
Please follow this guide to fix your softbrick, root and update.
Click to expand...
Click to collapse
This was EXACTLY what I needed and worked flawless!! And I am so sorry for not responding sooner, as I have been in the hospital again.
DONE!! Thank You to those that helped!!