SuperSU Root & TWRP Recovery (XT1096) - X 2014 Q&A, Help & Troubleshooting

Thanks in advance for any information/guidance provided! Please bear w/ me, I am pretty new to all of this. I apologize for any incorrectly used terminology.
I have a Verizon Moto X 2014 (XT1096) that I have recently unlocked the bootloader and rooted via SuperSU and TWRP Recovery. When I opened SuperSU, I got an error message stating that I needed to update the binary, but it was unable to be done OTA. I used TWRP to sideload the binary zip file onto the phone's internal storage, which seemed to work fine.
Using the same method, I moved CM13 (01/14/16 nightly build) to the internal storage and followed the remaining steps in the process.
Jump ahead a few days (phone seems to be working great & am running on T-Mobile LTE perfectly) and now I have a few questions:
1. Is my phone for all intents and purposes, considered Pure Edition since I have unlocked BL and rooted the phone?
2. I can download nightly updates, but when I try to install them, the phone reboots/does not install the build.. How can I download and install the updates OTA?
3. Is it necessary for me to keep the TWRP recovery/backup zip file on my phone's internal storage? (wondering b/c phone is ony 16 gb and the backup used a large amount of available storage)
4. Is there any way for me to have stock Marshmallow on this phone instead of CM?
Thanks again and sorry for the likely horrible explanation.
Daniel

dwilso621 said:
Thanks in advance for any information/guidance provided! Please bear w/ me, I am pretty new to all of this. I apologize for any incorrectly used terminology.
I have a Verizon Moto X 2014 (XT1096) that I have recently unlocked the bootloader and rooted via SuperSU and TWRP Recovery. When I opened SuperSU, I got an error message stating that I needed to update the binary, but it was unable to be done OTA. I used TWRP to sideload the binary zip file onto the phone's internal storage, which seemed to work fine.
Using the same method, I moved CM13 (01/14/16 nightly build) to the internal storage and followed the remaining steps in the process.
Jump ahead a few days (phone seems to be working great & am running on T-Mobile LTE perfectly) and now I have a few questions:
1. Is my phone for all intents and purposes, considered Pure Edition since I have unlocked BL and rooted the phone?
2. I can download nightly updates, but when I try to install them, the phone reboots/does not install the build.. How can I download and install the updates OTA?
3. Is it necessary for me to keep the TWRP recovery/backup zip file on my phone's internal storage? (wondering b/c phone is ony 16 gb and the backup used a large amount of available storage)
4. Is there any way for me to have stock Marshmallow on this phone instead of CM?
Thanks again and sorry for the likely horrible explanation.
Daniel
Click to expand...
Click to collapse
1) No, you don't have a pure edition. The xt1095 is the pure edition. Nothing to do with the bootloader being unlocked or rooted. The xt1095 is called the pure edition because it is the only model that does NOT lose warranty after you unlock the bootloader. You have the xt1096, so when you unlocked it you voided the warranty.
2) The CM updates should work fine. Does it give an error?
3) What zip file are you talking about? Do you mean a backup of your system?
4) If you use verizon's service, no. If you use any other service such as tmobile or any other gsm company yes. If you don't use verizon service, you can flash the xt1095 marshmallow firmware. It will work 99%, the only thing that won't work is verizon service because verizon is CDMA.
Sent from my XT1095 using Tapatalk

2) No, it doesn't give an error. It shows a pop up message saying the phone will reboot into recovery mode to install the update. Note: this feature requires a compatible Recovery or the updates will need to be installed manually.
3) Where would I download the img apk for Android 6.0?
Thanks again!

AGISCI said:
1) No, you don't have a pure edition. The xt1095 is the pure edition. Nothing to do with the bootloader being unlocked or rooted. The xt1095 is called the pure edition because it is the only model that does NOT lose warranty after you unlock the bootloader. You have the xt1096, so when you unlocked it you voided the warranty.
2) The CM updates should work fine. Does it give an error?
3) What zip file are you talking about? Do you mean a backup of your system?
4) If you use verizon's service, no. If you use any other service such as tmobile or any other gsm company yes. If you don't use verizon service, you can flash the xt1095 marshmallow firmware. It will work 99%, the only thing that won't work is verizon service because verizon is CDMA.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
2) No, it doesn't give an error. It shows a pop up message saying the phone will reboot into recovery mode to install the update. Note: this feature requires a compatible Recovery or the updates will need to be installed manually.
3) Yes, I was referring to the system backup zip file
4) Where would I download the img file for stock Android 6.0? I'm using it on T-Mobile, not Verizon.
Thanks again!

Related

[Q] Flashing KitKat on a Moto X with 139.12.35.ghost_row.AmericaMovil.en.PR

Hello!
I'm currently stationed in Singapore and bought a Moto X about a month or so ago from eBay. While I am anxiously waiting for my Moto X to receive the 4.4 update, I realised that the system version (after the previous camera update) is 139.12.35.ghost_row.AmericaMovil.en.PR, which I found to be a Latin America version after some searching on the forums and Googling here and there.
I also found this thread, where OP said that they can be flashed over to either the T-Mobile version. Does this continue to work for the 4.4 updates by T-Mobile or AT&T, and would there be anything else required for flashing? (I saw something about flashing new radios and all, but was quite confused by contradicting explanations and suggestions :/)
Thanks in advance!
// EDIT:
To add on after a bit of searching, I realised that I am allowed to unlock my bootloader, despite claims from the original retailer on eBay that the phone came from AT&T (which is notorious, even here, for their stance on bootloader unlocking). What gives?
I got the same Moto X from a buddy yesterday. I did a lot of searching and also discovered the thread about the phone being flashed to t- mobile.
I fooled the steps on another thread titled " Return to stock 100%" out something like that...
I downloaded the correct Att firmware and with the use of RSDLite, I successfully flashed my Moto X to ATT.... it took less than 10 minutes. And as soon as it booted up, I got hit with the "update available" message ( kit Kat)
Sent from my XT1058 using Tapatalk
Thanks for the information!
I've successfully upgraded my phone to the Verizon version (minus all the bloatware that I hastily blasted off), with root and TWRP. So this is what I did, for future reference:
It seems that AmericaMovil versions are not bound by the AT&T's locked bootloader policies, and other Latin America versions are probably free from the restriction too. So I managed to get my hands on the Motorola Fastboot and unlocked my bootloader. TWRP was installed (remember to use 2.6.3.1 and above for 4.4 support), and then flashed the Verizon system dump available here. Root was installed by TWRP.
After getting on the device and setting things up, I rebooted to recovery to remove lots of bloatware (available in /system/app and /system/priv-app). Had to remove some of them through Titanium Backup as the file names were not always indicative that it came from Verizon. I made the extra step of killing the god-awful boot animation that they had by replacing it with this.
And... that concludes my experience with this, I suppose.
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
I believe the bootloader does have to be unlocked in order to flash a different firmware.
Sent from my XT1058 using Tapatalk
RagnaParadise said:
I'm not too sure whether flashing via TWRP/CMW will allow you to get OTA, unfortunately. Which is why I went straight for the Verizon system dump. But yes, you can change firmware without ever having to root the phone. Heck, I think there's a guide on restoring mentioned by @plmiller0905 below that will allow you to do it without unlocking the bootloader, even.
Click to expand...
Click to collapse
Yeah after doing so more reading.. (at least the way I'm willing to do it) is to just unlock my bootloader and then using RSD Lite (Which i still have no idea what that is / where it is) flash an SBF found here (http://sbf.droid-developers.org/ghost_rcica/list.php)
I guess following this video somewhat http://www.youtube.com/watch?v=Fr0JHSAXJDI#t=15
Does that sound right?
Should I flash the TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_CFC.xml.zip
Or just jump straight to the 4.4 version TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip
??
As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?
RagnaParadise said:
As far as I know, the use of RSD Lite doesn't require an unlocked bootloader (at least, that's what it shows in the video you showed me anyway), especially since these are images supposedly signed by Motorola themselves. Let me know if you've found something else?
As for your question on which to flash... I'm not sure, but you'd skip a lot of the hassle if you could flash 4.4 straight, so how about trying that?
Click to expand...
Click to collapse
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure
sleepyguy007 said:
Rsdlite is a shell for a flash boot flash supposedly with an XML doing all the steps together. Just makes it easier.
You need unlocked boot loader only to flash an image that doesn't match your current boot loader. So if you have a. At&t phone you can only flash at&t images by rsdlite. But if you unlock your amerimovil phone you can flash any xt1058 image I think. So amerimovil could take say a rogers or at&t or telcel image. Not sure if T-Mobile image will work on a full rsdlite flash as it is an xt1053 image. I think you can flash most of a T-Mobile image by twrp but not by rsdlite not sure
Click to expand...
Click to collapse
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?
alternetconcept said:
So if I flash the at&t image found here (http://sbf.droid-developers.org/ghost_rcica/list.php), would it come pre-loaded with all the bloatware AT&T has even though I'm not using AT&T network?
Click to expand...
Click to collapse
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)
sleepyguy007 said:
yes of course. think about it like if you took a dell windows 7 install CD , and put it on an HP. all the dell customizations would still be there.
obviously since you have unlocked bootloader, once you do the RSDlite you can always flash twrp, and superuser, and delete all that stuff. but then you wouldn't get updates again. i dont think the at&t image is really THAT bad. though i've heard the rogers one is better (though maybe not 4.4 yet)
Click to expand...
Click to collapse
Yeah unfortunately that's what I thought. Hence why I would of liked to flash the t-mobile image but I'm going to hold off until someone that is a bit more adb savvy then myself tries it out. I wouldn't know what to do if I ended up soft bricking my phone
Well it didn't take long to try it out myself...
It worked out!
I used this thread here http://forum.xda-developers.com/showthread.php?t=2446515
I downloaded the Tmobile 4.4 Image and used RSD.
All you have to do is unlock your BL. (Note: I was completely bone stock with NO root and NO special recovery like CMW or TWRP)
Have all the proper drivers installed, enable USB debugging in developer settings on the phone
Go into Fastboot on the phone
Plug in the phone and just follow the video
I do not take any responsibitliy if you brick your phone. It is fairly easy process and took only a few mins.
Hope this helps!
- deleted because I was sleepy enough not to notice that replies were done on the next page -_- -
alternetconcept said:
I've been looking through a few threads and I am not comfortable enough to flash the T-Mobile rom over my AmericanMovil one yet.
I can't seem to find step by step instructions on how to do this.. Would anyone like to explain it from the ground up?
My understanding
1) unlock bootloader
2) flash a recovery like twrp or cmw
3) flash the rom that is given in the OG post here http://forum.xda-developers.com/showthread.php?t=2477180
4) this should now give us the t-mobile version of things and we should be able to do the standard OTA from there?
[Q] So can this all be done without ever having to root the phone?
Click to expand...
Click to collapse
I've been doing some research on this since yesterday and I've been hesitant on doing it. I saw in your last post that you successfully flashed the TMO 4.4 ROM on your AmericaMovil phone, so I have a few questions for you before I go ahead and do the same:
1. Can you please confirm that your model is XT1058 and not XT1053?
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
3. Does the TMO ROM have the Tethering & portable hotspot option under Settings > More?
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
5. Have you been having any radio problems since you flashed the TMO ROM?
I wonder if I install the ROM in here http://forum.xda-developers.com/showthread.php?t=2477180 using RSDLite, would I get the OTA update to 4.4? The reason I want to install this ROM is because it only flashes system and boot.img without flashing bootloader, modem, logo etc... and I know the XT1058 radio is different from the XT1053 radio, so I've been reluctant to flash a full XT1053 ROM on my XT1058 phone.
But what I also would like to know is if an OTA update would flash a full ROM or not. In other words, if I flash the ROM above and then OTA update to 4.4 and the OTA update flashes the full ROM including the radio, I might as well flash the full 4.4 immediately.
What do you or anyone else think?
I'll answer to the best of my ability. heh
mschumacher69 said:
1. Can you please confirm that your model is XT1058 and not XT1053?
Click to expand...
Click to collapse
Mine was an XT1058, and has been flashed to XT1060. (I didn't notice that T-Mo had a 4.4 ROM on the list, so I went straight for the flashable ZIP for Verizon instead. silly me.)
mschumacher69 said:
2. Does the TMO ROM have the TMO boot logo and any TMO bloatware?
Click to expand...
Click to collapse
At least according to this article, the TMO version shouldn't have any bloatware.
mschumacher69 said:
4. Does the TMO ROM have the Mass Storage option under Settings > Storage > | > USB computer connection?
Click to expand...
Click to collapse
There's no reason why there shouldn't be; I'm seeing it on my Verizon version.
mschumacher69 said:
5. Have you been having any radio problems since you flashed the TMO ROM?
Click to expand...
Click to collapse
I can't say for sure if you'll face any problems, but I flashed the T-Mo radio provided here with my Verizon ROM, and I had no problems connecting to my network in Singapore.
--
I can't answer the rest unfortunately. Sorry. Hope I've helped.
RagnaParadise said:
I can't answer the rest unfortunately. Sorry. Hope I've helped.
Click to expand...
Click to collapse
Thank you for your answers!
Regarding Mass Storage, the reason I'm asking is because I don't have it on my AmericaMovil ROM.
The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.
alternetconcept said:
The ROM is basically exactly what you get when you buy the T-Mobile version.
I figured the radios are nearly identical from the AT&T version and the T-Mobile version so my XT1058 is running on the XT1053 radios. There is no bloatware. tethering is there but I'm not sure if t-mobile will allow it. There is NO tmobile logo that comes up on boot. USB connect to computer is there.
As for the radio section again.. I was getting only EDGE in my house before I switched to this ROM (Meaning when I was on the ORIGINAL XT1058 image) and I am still getting only EDGE in my house.. Unfortunately I haven't left my house since yesterday flashing the image but when I'll be back at work in NYC and should see '4G/LTE' over there.
We'll see.
Click to expand...
Click to collapse
Thanks for ur reply! Which network are you on right now?
mschumacher69 said:
Thanks for ur reply! Which network are you on right now?
Click to expand...
Click to collapse
I've always been on T-mobile network. Both when i was on original XT1058 AmericanMovil system version and still on T-mobile when I switched the image to XT1053.
Back on my Nexus 4 though.. I would have HSPA+ in my house.. So I thought it was a bit odd that as soon as I received this phone that I wasn't getting anything other than EDGE..

Confused by BL Unlock and Root/Unroot on DE vs MM versions

I'm a VZW Galaxy Nexus user who took advantage of the Black Friday sale on the Moto X Developer Edition (for Verizon). I guess I've been spoiled by how easy it was to unlock, root, take OTA updates on my Galaxy Nexus and both the 2012 and 2013 Nexus 7 tablets. I've been researching the Moto X methods while I wait for the phones to arrive, and I'd like to see if my understanding is correct.
1. Because I'll have a DE (Developer Edition) version, rather than a MM (MotoMaker) version, bootloader unlocking should be easy. I get the code from Motorola and follow the instructions on the Motorola website. Right?
2. For the same reason as above, rooting should be as easy as flashing custom recovery (Hashcode's TWRP 2.6.3.1 I think it is as I type this), then booting into that custom recovery and flashing the latest SuperSU. Right?
If yes to both above, then this is just as easy as it was on my Nexus devices.
What about taking OTA updates? On my Nexus phones and tablets, even with custom recovery and root I was able to take OTA updates (everything was basically stock). If I lost root (like I did when I updated to 4.4), I simply flashed SuperSU again from TWRP or CWM. Would this be any different on the moto x? I've seen posts where people with rooted moto x got stuck in boot loops after accepting the 4.4 update. Was that because they had a MM version and had to use PwnMyMoto or RockMyMoto or some similar exploit-method of gaining root? If I have the DE version, should I first flash stock recovery and unroot? Flashing stock recovery is simple, but how would I unroot the moto x if I had rooted it just by flashing SuperSU from TWRP?
Thanks in advance for the help.
GrillMouster said:
I'm a VZW Galaxy Nexus user who took advantage of the Black Friday sale on the Moto X Developer Edition (for Verizon). I guess I've been spoiled by how easy it was to unlock, root, take OTA updates on my Galaxy Nexus and both the 2012 and 2013 Nexus 7 tablets. I've been researching the Moto X methods while I wait for the phones to arrive, and I'd like to see if my understanding is correct.
1. Because I'll have a DE (Developer Edition) version, rather than a MM (MotoMaker) version, bootloader unlocking should be easy. I get the code from Motorola and follow the instructions on the Motorola website. Right?
2. For the same reason as above, rooting should be as easy as flashing custom recovery (Hashcode's TWRP 2.6.3.1 I think it is as I type this), then booting into that custom recovery and flashing the latest SuperSU. Right?
If yes to both above, then this is just as easy as it was on my Nexus devices.
What about taking OTA updates? On my Nexus phones and tablets, even with custom recovery and root I was able to take OTA updates (everything was basically stock). If I lost root (like I did when I updated to 4.4), I simply flashed SuperSU again from TWRP or CWM. Would this be any different on the moto x? I've seen posts where people with rooted moto x got stuck in boot loops after accepting the 4.4 update. Was that because they had a MM version and had to use PwnMyMoto or RockMyMoto or some similar exploit-method of gaining root? If I have the DE version, should I first flash stock recovery and unroot? Flashing stock recovery is simple, but how would I unroot the moto x if I had rooted it just by flashing SuperSU from TWRP?
Thanks in advance for the help.
Click to expand...
Click to collapse
Yes to both questions. But no, you cant take OTAs with a custom recovery.
The problems only happened when people tried to root devices that didn't have an unlockable bootloader (ATT, Verizon). Other models are fine.
You need to have the stock recovery, and all stock files. The 4.4 OTA kills root anyway. So you just have to flash TWRP again afterwards and root with SSU.
GoClifGo05 said:
That's not true. I have VZW developer edition, unlocked the booloader the day I got and I received the Camera OTA and 4.4 OTA with no issues.
You need to have the stock recovery, and all stock files. The 4.4 OTA kills root anyway. So you just have to flash TWRP again afterwards and root with SSU.
Click to expand...
Click to collapse
With TWRP? That's new. I know it works on stock recovery, but he asked about a custom one. I'll edit my post though...i can see how it sounds wrong.
No not with TWRP sorry.... It seemed as if you meant unlocking the bl blocked the ota alone. My bad.
Sent from my Moto X DE
GoClifGo05 said:
No not with TWRP sorry.... It seemed as if you meant unlocking the bl blocked the ota alone. My bad.
Sent from my Moto X DE
Click to expand...
Click to collapse
Yeah that's why I edited the post. I worded it wrong.
GoClifGo05 said:
You need to have the stock recovery, and all stock files.....
Click to expand...
Click to collapse
No problem. By "all stock files", I assume that I won't have a problem, since I haven't in the past. I haven't removed any stock apps, just disabled them (even VZW bloatware). I use stock ROM and just want root for Titanium Backup, Quickboot, tethering, maybe Greenify (but I don't think I'll use that on the moto x). Actually, I'm not sure about tethering, since the method I've seen for native tethering on the moto x involves replacing "VzwEntitlementService.apk" from the "/system/priv-app/" directory with a modified one. Would that cause an OTA to fail (assuming I had stock recovery)?
Yea just meant apps. If you can disable them from within settings then you're fine. If you modify anything in system or delete system apps via TiBu then the Ota will fail.
Sent from my Moto X DE

[Q] Stock, flashable update? (VZW Dev edition TWRP)

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

Moto x dev edt. Root/OTA root question.

Hey guys. At what point do you lose the ability to OTA update? Is it when you unlock your bootloader or when you install custom recovery and SuperSU?
yankeesfan714 said:
Hey guys. At what point do you lose the ability to OTA update? Is it when you unlock your bootloader or when you install custom recovery and SuperSU?
Click to expand...
Click to collapse
I've had no issues updating OTA while rooted and unlocked. It only becomes an issue if you modify the system. You will also not be able to update OTA if you have a custom recovery installed. However, to play it completely safe it is always best to go back to stock if you are doing an OTA.
Installing a custom recovery and messing with system apps will cause an ota to fail. Unlocking and SU alone won't make it fail
Leave system apps alone and flash back to the stock recovery prior to accepting the ota.
yankeesfan714 said:
Hey guys. At what point do you lose the ability to OTA update? Is it when you unlock your bootloader or when you install custom recovery and SuperSU?
Click to expand...
Click to collapse
Since the OTA can only install via stock recovery, installing a custom recovery is technically the point at which you lose the ability to do an OTA update.
to quote SOME of what I put here -> http://mark.cdmaforums.com/MotoX-OTA.html
For the Motorola X, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
Inside the OTA is a manifest file. It contains a list of files and their check sums it expects to be on your phone. If the files are missing, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall.
Because of #2, you must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, may need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.
Click to expand...
Click to collapse
So any any point you deviate from stock too much, an OTA will fail to install.
(there is more info at that link)
If all you have done is unlocked the bootloader, flashed custom recovery, and installed SuperSU to root... then installed root capable apps like Adfree, Wifi Tether for root, Greenify, or others that don't mess with system files and the like, you can just flash stock recovery back on to take an OTA.
If you unlock the bootloader, flash custom recovery, and install SuperSU to root... then alter the build.prop, remove or rename the BLOAT APK's from your phone, install Xposed, etc. You'll have some work to do getting back to "stock" to take the OTA.
KidJoe said:
Since the OTA can only install via stock recovery, installing a custom recovery is technically the point at which you lose the ability to do an OTA update.
to quote SOME of what I put here -> http://mark.cdmaforums.com/MotoX-OTA.html
So any any point you deviate from stock too much, an OTA will fail to install.
(there is more info at that link)
If all you have done is unlocked the bootloader, flashed custom recovery, and installed SuperSU to root... then installed root capable apps like Adfree, Wifi Tether for root, Greenify, or others that don't mess with system files and the like, you can just flash stock recovery back on to take an OTA.
If you unlock the bootloader, flash custom recovery, and install SuperSU to root... then alter the build.prop, remove or rename the BLOAT APK's from your phone, install Xposed, etc. You'll have some work to do getting back to "stock" to take the OTA.
Click to expand...
Click to collapse
Does this also apply to moto x non-dev devices?
dmonleo said:
Does this also apply to moto x non-dev devices?
Click to expand...
Click to collapse
Yes. Every device with an unlocked bootloader is essentially a 'non official' Dev edition (although unlike the Dev edition, your warranty is void).
We always got "swappa"!
dmonleo said:
Does this also apply to moto x non-dev devices?
Click to expand...
Click to collapse
While Not Explicitly stated on -> http://mark.cdmaforums.com/MotoX-OTA.html yes, that info about the conditions for taking an OTA applies to ALL Moto X's... Dev Edition, Non-Dev Edition, Moto Maker, Retail, etc. With locked bootloader and with Unlocked Bootloader.
What @samwathegreat replied to you is very accurate. From a functional stand point, once you unlock the bootloader on a Non-Dev Edition... your phone acts as if you have a Dev Edition.. (Except your warranty is void). And it doesn't matter if you have a Rogers Wireless, Sprint, GSM Unlocked, etc... and got your code from Moto, or you had a Verizon Non-Dev or ATT or Republic wireless and got the code from the Chinese website or middleman.

moto x 1st gen 4.2.2 Upgrade to 5.1

Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
bushako said:
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
Click to expand...
Click to collapse
I don't want to go back to complete stock, I want to keep bootloader unlocked and root. Is there a stock rooted rom out there I can flash w/ TWRP without having to do OTA or flashing the recovery back to stock?
Yes there is its in the development section. You'll read the thread something like xt1053 stock flash-able. It contains only the kernel and system files so you should be good.
Here http://forum.xda-developers.com/showthread.php?t=3155843
Sent from my Moto X
-RanZ- said:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
Click to expand...
Click to collapse
First off, there is no Verizon 5.1 yet. So any 5.1 you try will be for a different model, and if you flash a full rom, it will have different radios (which don't work for CDMA that Verizon still uses for voice/3g data. If you keep your stock VZW radio files, keep in mind they will be on a different version than the rest of the rom which could cause some inconsistencies and issues. IF you do flash a FULL SBF, you will be stuck with no SAFE way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature), and you'll have to wait for the Verizon 5.1 SBF to get back to Verizon's rom.
Next, to install an OTA update, when it becomes available, you need STOCK RECOVERY on your phone. The OTA also does a pre-flash check/validation of your phone before it flashes, so if anything it looks for is not what it expects, the OTA will fail. Because of that you need to be 100% stock, or very near to it.
Finally, NO, an OTA will not relock your bootloader, nor will flashing an SBF.
For more on taking an OTA, see the link in my signature on OTA Updates..
That being said, if you TRY a 5.1 rom that is out there for another model you best bet is to find one that is a TWRP back up of 5.1 installed on someone's phone, since it only updates system.img and boot.img. It may not work 100% (because part of your phone will still have the 4.4.4 files), but it will give you a taste and you could later revert back to the stock 4.4.4 which you currently have on your phone. IF you flash a FULL SBF, you might be stuck with no way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature)
Hi Bushako, I've Moto X Verizon XT1060 and it's struck in 4.2.2 android. When I try to update using setting, about phone and system update it show there is no update available but the android version on it is 4.2.2
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
-RanZ- said:
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Click to expand...
Click to collapse
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
KidJoe said:
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
Click to expand...
Click to collapse
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
-RanZ- said:
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
Click to expand...
Click to collapse
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
KidJoe said:
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
Click to expand...
Click to collapse
I will give this a try if I can locate the correct SBF files, your information has helped greatly, Thanks!
nevermind, google fixed me.

Categories

Resources