Database Develop

[Q] (AT&T) Best path to 4.4.2 from 4.4?

My setup: 4.4 ATT Moto X, Rooted (by way of latest jcase method), Locked bootloader, and I'm pretty sure write protection is off (though I don't remember how to check)
What I am wanting to know is how would and should I be able to get to 4.4.2, and get my root back (as I'm not confident any method will be able to "keep" my root safely without screwing something else up)? What's the best way based on my setup, and what files or tools would I need(stock 4.4 or 4.4.2 ROM, a new recovery image, etc)?
Since the root method I used hijacks the recovery, I suppose I technically don't have a functional one (other than it maintaining my root). Do I even need a custom recovery? I don't ever plan to flash anything other than basic stock firmware, though I may toy around with Xposed in the future. Also as a sidenote, im currently using ART instead of Dalvik. If any method or technique might conflict with that (other than Xposed), then let me know to the best of your knowledge.

Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)

...
Sent from my XT1058 using XDA Premium 4 mobile app

kj2112 said:
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Honestly i dont even care to have an unlocked bootloader. I just realy need root after I update. Write protection, so far i think, i've only needed for AdAway to work on my phone, though Im sure I have used or applied it else on my device. And thanks for the thread, but I was already subscribed .

Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
Click to expand...
Click to collapse
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.

NameLessThugZero said:
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
Click to expand...
Click to collapse
The only ways to use 4.4.2 Rooted with Write Protection DISABLED is the Safestrap way, or to unlock your bootloader.
Since you have AT&T, Moto doesn't give out the code to unlock your bootloader (Non-Developer Edition Verizon phones are the same way.) so if you really want to unlock your bootloader, see -> http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651 I know the thread title says VERIZON but it works for ATT users too.

I see, thanks for the explanation, because I certainly wouldn't have know it was for AT&T users too! I'll check them out.
Sent from my XT1058 using XDA Premium 4 mobile app

Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)[/QUOTE
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse

NameLessThugZero said:
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
Right. You want a modified version of the OTA that does not modify your bootloader and will patch /system from 4.4 to 4.4.2. I also manually patched the kernel up to 4.4.2.
And, my experience is that you also have to downgrade to 4.2.2. I don't quite understand why, but I have never been able to upgrade to 4.4.x (neither from the 4.4 leak or the official 4.4 version) without going back to 4.2.2 first. The eclipse ROM instructions, on the other hand, suggest that a safestrap:twrp factory wipe might be enough, but I remember trying that once, and it didn't work. YMMV
I already made a zip to flash a full copy of 4.4.2 (not a patch) that I made from my system dump, but it hasn't been tested. (I'm waiting for the SBF.)

Alright. Well I guess I'll have to wait a bit for someone to come out or prove there's a safer, surer method to update. Moto always did like to make thing like this difficult, heh.
Sent from my XT1058 using XDA Premium 4 mobile app

[Q] Already rooted, what to do with Kitkat update notification?

I am already rooted with xposed installed on Verizon and got the notification for the Kitkat OTA update -- which thread do I follow to safely take the OTA KitKat update? Thanks.

libertao said:
I am already rooted with xposed installed on Verizon and got the notification for the Kitkat OTA update -- which thread do I follow to safely take the OTA KitKat update? Thanks.
Click to expand...
Click to collapse
You can just try to take it as long as you have stock recovery installed (TWRP/CWM/PhilZ will cause a soft-brick situation), but depending on what Xposed modules you use and the changes made it could likely fail.
The safest and best way would be to factory restore the firmware via this: http://forum.xda-developers.com/showthread.php?t=2448960, then take the OTA to 12B, followed by the OTA to 24A. The whole process is pretty painless, I did it going from an old CarbonROM build to the latest stock KitKat in about an hour and a half or so.

acejavelin said:
You can just try to take it as long as you have stock recovery installed (TWRP/CWM/PhilZ will cause a soft-brick situation), but depending on what Xposed modules you use and the changes made it could likely fail.
The safest and best way would be to factory restore the firmware via this: http://forum.xda-developers.com/showthread.php?t=2448960, then take the OTA to 12B, followed by the OTA to 24A. The whole process is pretty painless, I did it going from an old CarbonROM build to the latest stock KitKat in about an hour and a half or so.
Click to expand...
Click to collapse
To add, you can re-root with ioroot25 and if you need a recovery for any reason, use AutoRec to install the latest TWRP. You need to jump through a few hoops to install recovery on KK and it does them for you. If you plan on staying on the stock rom, I would leave the stock recovery.

mjones73 said:
To add, you can re-root with ioroot25 and if you need a recovery for any reason, use AutoRec to install the latest TWRP. You need to jump through a few hoops to install recovery on KK and it does them for you. If you plan on staying on the stock rom, I would leave the stock recovery.
Click to expand...
Click to collapse
In my opinion, ioroot25 only does a partial root, there is BusyBox installed with SuperSU... I would also recommend doing a manual BusyBox install (Play Store has several free installers) for a "full" root install.
Sent from my Nexus 4 using Tapatalk

acejavelin said:
In my opinion, ioroot25 only does a partial root, there is BusyBox installed with SuperSU... I would also recommend doing a manual BusyBox install (Play Store has several free installers) for a "full" root install.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I forgot about that, I just used the app store BusyBox installer and it worked great.

[Q] VZW 4.4.4 Unlocked: Root and Tether enabled?

Before I update my DevEd to 4.4.4, I want to ensure that I will still be able to root (use recovery tool or something else?) and that there is some way to use tether.
On 4.4.3, I've been happy using WiFi Tether for Root users - would be nice if this continued to work, but am okay using a different method if need be.
Can someone confirm that both root & tether are functional, and if so, what method(s) are working?

With an Unlocked Bootloader, Yes, you can root by flashing TWRP and SuperSU, the same process. Just make sure you have the latest TWRP and SuperSU from their source web sites. That will be true for ALL updates so long as you have an unlocked bootloader. And it can be dev edition or carrier edition, as long as the bootloader is unlocked.
Wifi tether for root still works on my VZW Dev X with 4.4.4 update.

Mercutio5 said:
Before I update my DevEd to 4.4.4, I want to ensure that I will still be able to root (use recovery tool or something else?) and that there is some way to use tether.
On 4.4.3, I've been happy using WiFi Tether for Root users - would be nice if this continued to work, but am okay using a different method if need be.
Can someone confirm that both root & tether are functional, and if so, what method(s) are working?
Click to expand...
Click to collapse
Of course...you're unlocked. Same method - flash TWRP and it will root for you. Since you don't seem to be aware -- you can NOT update unless you flash back stock recovery and un-do any changes you made to /system including installing Xposed (if you did). If all you are using root for is WiFi Tether, nothing to worry about as you probably haven't modified /system. You WILL have to flash back the stock recovery.img before you can accept any OTA. Its always been like this.
WiFi tether should work on 4.4.4, as should the entitlement 'hack'. (I believe both have been confirmed, but check the entitlement hack threads to be sure about it)
And finally......since you mention being on 4.4.3 now, I'm assuming you are using the XT1053 GSM Dev edition (since 4.4.3 was never released for VZW). If so...you do realize that 4.4.4 isn't out yet for the XT1053, right?
It's only out for the VZW XT1060 and soak-tests are just now happening for the AT&T XT1058.

samwathegreat said:
Of course...you're unlocked. Same method - flash TWRP and it will root for you. Since you don't seem to be aware -- you can NOT update unless you flash back stock recovery and un-do any changes you made to /system including installing Xposed (if you did). If all you are using root for is WiFi Tether, nothing to worry about as you probably haven't modified /system. You WILL have to flash back the stock recovery.img before you can accept any OTA. Its always been like this.
WiFi tether should work on 4.4.4, as should the entitlement 'hack'. (I believe both have been confirmed, but check the entitlement hack threads to be sure about it)
And finally......since you mention being on 4.4.3 now, I'm assuming you are using the XT1053 GSM Dev edition (since 4.4.3 was never released for VZW). If so...you do realize that 4.4.4 isn't out yet for the XT1053, right?
It's only out for the VZW XT1060 and soak-tests are just now happening for the AT&T XT1058.
Click to expand...
Click to collapse
I'd just assumed to be on 4.4.3 since it's previous to 4.4.4 - but you're correct, I'm on 4.4.2 VZW. After reading through some update methods discussed on XDA, it seems that using RSDLite w/FXZ is the easiest - no need to undo any changes made to /system (I'm sure I've made some, but have no idea what they might have been) and no need to remove TWRP. Plus it supposedly preserves all the data.
And thank you for assuaging my concerns re: root & tether

Mercutio5 said:
I'd just assumed to be on 4.4.3 since it's previous to 4.4.4 - but you're correct, I'm on 4.4.2 VZW. After reading through some update methods discussed on XDA, it seems that using RSDLite w/FXZ is the easiest - no need to undo any changes made to /system (I'm sure I've made some, but have no idea what they might have been) and no need to remove TWRP. Plus it supposedly preserves all the data.
And thank you for assuaging my concerns re: root & tether
Click to expand...
Click to collapse
Take caution!! The original leaked fxz was indeed a keep data fxz. It's now gone. The new official leaked fxz is NOT a keep data fxz.
All you have to do is edit the XML file and remove the line containing 'erase userdata' and it will preserve your data.
If you don't do this all your data WILL be erased.
Keep that in mind...
Good luck

samwathegreat said:
Take caution!! The original leaked fxz was indeed a keep data fxz. It's now gone. The new official leaked fxz is NOT a keep data fxz.
All you have to do is edit the XML file and remove the line containing 'erase userdata' and it will preserve your data.
If you don't do this all your data WILL be erased.
Keep that in mind...
Good luck
Click to expand...
Click to collapse
Yikes!! Thank you for the heads up.
How did the leaked FXZ disappear? Surely someone's still got it somewhere?

Mercutio5 said:
Yikes!! Thank you for the heads up.
How did the leaked FXZ disappear? Surely someone's still got it somewhere?
Click to expand...
Click to collapse
Its all the same "inside" except the included XML file now contains the "Erase USERDATA" statement. Just remove that line from the XML before flashing with RSDLite and you're good.
No reason for the original leak to stick around.

[Q] Best practice for updating VZW unlocked bootloader rooted 4.4.2 Stock ROM

I am on Verizon 4.4.2, bootloader unlocked, rooted, with TWRP. Obviously, OTA won't work, but what is the best way for me to update to 4.4.4 stock ROM w/o wiping my user data?

If the Moto X is anything like the Nexus 5, there may be an OTA update.zip that is lurking around and you can just flash that and then reflash root to update you to the latest software version. Or you could download and flash the SYSTEM.IMG and BOOT.IMG from the 4.4.4 Verizon ROM. I'd recommend the first one and make sure that someone else can safely say that the second method would even work!

Toys Samurai said:
I am on Verizon 4.4.2, bootloader unlocked, rooted, with TWRP. Obviously, OTA won't work, but what is the best way for me to update to 4.4.4 stock ROM w/o wiping my user data?
Click to expand...
Click to collapse
The proper way to update is to use the 4.4.4 FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In order to retain your data and apps, you need to use the tools provided by @SamuriHL and use the "keep data" option.
Everything you need is listed in the first post, including links and instructions for the tools to use. All of your apps and settings will be intact --AS LONG as you use the tools provided in the OP. If you fail to do this, you WILL lose your data. Afterwards, you can flash TWRP again (from here: http://techerrata.com/browse/twrp2/ghost ) using fastboot, and re-root your device.
Next time, please remember to post your questions in Q&A, not general.
Good Luck :good:
P.S. I also want to add that using the FXZ is superior to taking the OTA for several reasons, many that I don't care to list. First and foremost, you don't need to worry about flashing stock recovery back (required to take an OTA), and you don't need to worry about any changes you may have made to /system. Follow the simple instructions, and it is done.
You will find numerous instances of people who have struggled to take the OTA, or who have spent enormous amounts of time trying only to have the OTA fail to install. I doubt you'll find ONE person who has struggled with the FXZ. It is so much simpler that I don't understand why anyone recommends using the OTA unless you are completely stock and unrooted. IMO, that is the only time you should use the OTA when an FXZ is available.

samwathegreat said:
The proper way to update is to use the 4.4.4 FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In order to retain your data and apps, you need to use the tools provided by @SamuriHL and use the "keep data" option.
Everything you need is listed in the first post, including links and instructions for the tools to use. All of your apps and settings will be intact --AS LONG as you use the tools provided in the OP. If you fail to do this, you WILL lose your data. Afterwards, you can flash TWRP again (from here: http://techerrata.com/browse/twrp2/ghost ) using fastboot, and re-root your device.
Next time, please remember to post your questions in Q&A, not general.
Good Luck :good:
P.S. I also want to add that using the FXZ is superior to taking the OTA for several reasons, many that I don't care to list. First and foremost, you don't need to worry about flashing stock recovery back (required to take an OTA), and you don't need to worry about any changes you may have made to /system. Follow the simple instructions, and it is done.
You will find numerous instances of people who have struggled to take the OTA, or who have spent enormous amounts of time trying only to have the OTA fail to install. I doubt you'll find ONE person who has struggled with the FXZ. It is so much simpler that I don't understand why anyone recommends using the OTA unless you are completely stock and unrooted. IMO, that is the only time you should use the OTA when an FXZ is available.
Click to expand...
Click to collapse
Curious,
What would the difference be in using FXZ vs flashing a 4.4.4 ROM such as krypton? Is it because the FXZ will update boot loader?

SR3TLAW said:
Curious,
What would the difference be in using FXZ vs flashing a 4.4.4 ROM such as krypton? Is it because the FXZ will update boot loader?
Click to expand...
Click to collapse
Flashing Krypton is possible from Custom recovery, unlike an OTA / FXZ. In addition, I believe that Krypton only includes the /system and /boot partitions. This is why he states that you need to be on 4.4.2+ first.
The FXZ overwrites all relevant partitions with new data.

Vekhez said:
If the Moto X is anything like the Nexus 5, there may be an OTA update.zip that is lurking around and you can just flash that and then reflash root to update you to the latest software version. Or you could download and flash the SYSTEM.IMG and BOOT.IMG from the 4.4.4 Verizon ROM. I'd recommend the first one and make sure that someone else can safely say that the second method would even work!
Click to expand...
Click to collapse
Unfortunately the X is nothing like the N5.

KJ said:
Unfortunately the X is nothing like the N5.
Click to expand...
Click to collapse
Yeah, I've found that out as of recently, they are very different devices, very very different indeed

Update Questions

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.