This has been briefly touched on in the root threads, but I still can't seem to find a definitive answer. And it could be that there's not an answer... yet. I'm just curious about how the software being listed "modified" will affect things like OTAs and interactions with Moto. There was some talk of software being listed as 0/0, 0/1, or 1/1. As in unlocked and/or rooted. Does anybody know what we will be listed as with Mofo root? Or is this uncharted territory and we will just have to wait and see what happens when the Lollipop OTA drops?
+1 good questions I have the same ones
We don't really know yet. However, likely:
1. Modified; OTA will not install and will spit out an error.
2. Unmodified but q/e 0/1: will likely install. This means you would have rooted in the past, but flashed a fully stock Motorola image to get back to 'Unmodified',' and so it should install.
Related
Man after a fun 2 hours getting my phone back to stock, now I'm wondering, does the 1.29.xxx update even apply to my particular device? Mine is an AT&T, with version 1.26.502.12. It was until i used the RUU to regain stock and lose root. But everything i've scoured mentioned updates to 1.29.401 and an update to the Dev version. My version isn't even listed of the RU variants list
http://xda4.androidrevolution.nl/db_mirror/ROMs/RUU_Variants.txt
So, would anyone explain to me, WTF? Is the 1.29 update not meant for my phone? I've run the device updater several times and it says my phone is up to date. I guess I'm asking primarily because I read that this update helps fix some issues like the responsiveness of the back button.
You have to wait till att approves the update, some carriers can be very slow with approving updates. You cannot install updates which are not meant for your carrier, but since you are already unlocked you can just install a custom rom and enjoy the updates all the same.
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
use fastboot to flash stock recovery on your phone, undo the tethering hack, and take the OTA.
Since you have a Dev Edition with unlocked bootloader, Root and Write Protection Disable survive. You can leave stock recovery on there, unless you really need the features of TWRP like backup, etc. Then you just have to do any NEW hacks for tethering (for 4.4.2 its different than 4.4). Or you can use wifi tether for root app instead of hacks.
There was talk about repackaging the OTA to be installed via TWRP or CWM, but I don't recall the thread containing an actual zip, and think they were mostly talking about what needs to be done. Since its easy enough with the Dev Edition to update, its likely not worth the work repacking it, since it wont work for those with LOCKED bootloaders.
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
I pretty much did what was described below and maintained TWRP and root. Note: you must enter TWRP and exit after the update to reinstall SU.
http://forum.xda-developers.com/showpost.php?p=50639372&postcount=25
except I chose not to flash the following...
fastboot flash logo logo.bin
fastboot erase customize
fastboot erase clogo
Whether it makes sense or not my goal is to not "upgrade" my bootloader or GPT until absolutely necessary as they can't be downgraded. The risks associated with doing this are hotly debated so understand what you are getting into if you choose to do this to your phone.
Reverted thether hack.
Recovery tool worked for me on moto x dev. flashed stock recovery. Took ota 442. Flashed twrp. kept root and stuff. no need for a computer.
http://forum.xda-developers.com/showthread.php?t=2334554
Okay, I have to ask. Has anyone successfully downgraded a 4.4.4 KitKat Moto X (2013) to a previous firmware version?
I have the XT1058 "ghost" if that matters.
Seriously? This has only been covered nearly everyday since 4.4.2 became available. In other words, the answers are out there if you simply open your eyes or search.
No not possible to downgrade from 4.4.4
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Darth said:
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Click to expand...
Click to collapse
This is the info I wanted. Thanks.
Hi, my phone is xt1056, BL unlocked, I was fully flashed (enabled all the options in the xml file) the ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4 once.
Then I fully flashed my xt1056 with the xt1060 rom (VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml) in rsd. Now the phone is 4.4.2 and no signal, but it is 4.4.2, I can get my SPC with the app SPCUtility.apk.
After get my SPC, I was fully flashed the xt1056 (ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4) again and works well (need to unlock the network again).
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Downgrading with an unlocked bootloader is no different than locked... Extremely dangerous.
And the poster above who downgraded, then upgraded again... I would not take any OTA's going forward. Or you might get an unfortunate surprise.
DarkWolffe said:
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Click to expand...
Click to collapse
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
KidJoe said:
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
Click to expand...
Click to collapse
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
KidJoe said:
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
Click to expand...
Click to collapse
Perfect answer. Thank you for the clarity.
I've searched and found variations on these questions in other posts, but I didn't come across any pertaining quite to my situation, so I wanted advice before I do something wrong and brick my phone.
I have a Sprint Moto X, unlocked & rooted, running 4.2.2 (I think pre-camera update). I'd like to upgrade to stock Sprint Lollipop (when it comes out) & stay unlocked & rooted.
My understanding of the steps that need to be taken:
1. Unroot my device
2. Re-lock my device
3. Flash TWRP and boot to recovery
4. Flash stock Sprint Lollipop
5. Unlock, then re-root device
Is any of this extraneous, or am I leaving anything out? Do I need to upgrade to KitKat before going to Lollipop?
I also have Xposed installed and I have tweaked the PRL on my device ... this shouldn't complicate the upgrade, right?
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
imnuts said:
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
Click to expand...
Click to collapse
i have a sprint X and if i am going to update this is how i have allways done it with no issues at all.
you can leave your bootloader unlocked that is no a issue. but i always take OTA's and you cant take a OTA with a modded system. so i allways just flash my stock firmware package. that way it removes my custom recovery. Root, and all Xposed changes. Then i take the OTA and just reinstall TWRP, then SuperSU then what ever else you want.
this is the safest way i have found to update, the nice thing about Unlocked Sprint phones is we can easily Root are phones via TWRP and SuperSu.
just my .02 you can do it how ever you like but this is how i am going to do it when the OTA finally comes out if it ever does.
Recently purchased an AT&T XT1097. It was on Android 4.4.4 which I temp rooted with Kingroot and then bootloader unlocked using Sunshine. I'd like to upgrade to 5.1 so I haven't bothered yet with rooting or installing a recovery. Frankly, I'm a wee bit confused by the information I've found in numerous threads on this and other sites simply because it seems the AT&T and Verizon versions of the Moto X 2014 are problematic to work with.
Does having my bootloader unlocked at this point mean that any root method will work on the device? I believe flashing should be a non issue at this point (because the bootloader is unlocked) but will it also allow me to downgrade to 4.4.4 or 5.0.2 if I am not pleased with 5.1? Is using TWRP a good idea or would it be best to manually flash images thru fastboot (which I couldn't do without clear instructions)?
On a related note my device initially reported an available OTA system update but since unlocking via Sunshine I haven't had the notification return. MDM also doesn't see an available update. Is this due to Sunshine or left over vestiges of Kingroot despite having done a FDR?
Further update...
With no replies to my questions I've taken it upon myself to try a few things. Figured out that MDM will not see an available update unless the device can connect with AT&T via wifi at which point it tells me that an update is already in progress because the OTA is downloading to the device. I would prefer to download and flash the full image via MDM but it is refusing to do so. I'm assuming that this may be because the update the phone wants to install is now considered an interim update (5.0.2) and the full image has been pulled from Motorola's or AT&T's servers.
I have been able to successfully root 4.4.4 but have since removed it in the expectation of updating the device shortly. I have also been able to boot a TWRP image in the hopes of doing a backup before making any significant changes but the device becomes unresponsive to touch commands at the write protect warning screen. Any ideas???