Related
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
So I've recently unlocked the bootloader thanks to SunShine. I previously froze the Moto updater app in Titanium so as not to continually receive prompts to upgrade. Since I'm not unlocked, rooted and have TWRP running.. Would it be worth my time to upgrade to 4.4.4?
1. What are the benefits or drawbacks of upgrading or is it so minor I'm barely going to notice a difference?
2. I don't want to screw anything up. I want my Xposed apps and everything I have now running great.
3. If I do upgrade is it difficult to re-root (assuming I will indeed lose root) or is it as simple as reinstalling SuperSU?
4. Is "okay Google Now" any faster? I'd use it more if it wasn't so incredibly slow.
5. I assume there will be no data wipe if I upgrade, correct?
6. Is it even worth it to upgrade? Better cell service? Faster or slower os?
Side Question: Can anybody recommend good WiFi Hotspot app now that I'm unlocked and rooted?
Sent from my Moto X
You can upgrade and flash custom recovery and root on any Android version now.
Will 4.4.4 change much? No. But there's no reason not to. You may need it for future X feature updates perhaps. Not sure.
Supposedly 4.4.4 lowered Android O/S battery usage, though my wifes 4.4.2 is fine... So again, up to you.
I don't see how updating will hurt anyway. But... Once you do, there's no going back.
Also on 4.4.2 AT&T unlocked through Chinese, have been planning to update to 4.4.4 now that it's rolled out to AT&T, mostly to see if the supposed camera improvements are better, and though I don't use the video recorder, I like that they added the pause (I was surprised when I couldn't find it)
I believe I just need to uninstall xposed, unfreeze any system apps, flash stock recovery, take the update, and reinstall TWRP
In the past yearly updates to my iPhone decreased performance and slowed things down. After awhile I got tired of the decreased performance on hardware that used to run find and said "Screw It!" so I will keep it on iOS 7 forever and no update anymore.
Should I root to keep my 2013 Moto X on 4.4.3 and speedy as the day I bought it?
Or
Should I update to 4.4.4 knowing in advance I'll be forced to update to 5.0 down the line?
I don't flash or use root much at all, would just use it to simply prevent OTA automatic download.
Thank you for you thoughts
As far as I know, you don't prevent the download after root. In fact not even the installation unless you change files in the system partition.
So, you don't want to update your Android phone because you had bad experiences with your iPhone in the past with updates? That seems like great logic. I've never had any issues with updates causing the phone to run slower or worse, unless there was an inherent bug with the update, which happens occasionally, but only once or twice in the 5+ years I've had Android phones, over a wide array of devices. Based on reviews, there may be some small issues with 5.0 currently, but overall the OS should be faster than KitKat due to ART.
ap3604 said:
Should I root to keep my 2013 Moto X on 4.4.3 and speedy as the day I bought it?
Or
Should I update to 4.4.4 knowing in advance I'll be forced to update to 5.0 down the line?
Click to expand...
Click to collapse
It really depends on your device, but you certainly can't base the X updates on how it went with other phones.
You have 4.4.3 on there? Who is your carrier, or what model X is it? Have you unlocked the bootloader?
My advice, if you can unlock the bootloader, do so now. Root the phone, rename the 3C_OTA.APK and 3C_OTA.ODEX which reside in /system/priv-app. That will prevent any OTA from downloading and prompting you to install.
Then sit tight, wait for Lollipop to start being pushed, and the inevitable feed back that will come as people rush to install it.
Based on that feed back, you can stay where you are, or rename 3C_OTA.APK and 3C_OTA.ODEX back to their original names, and take the update.
KidJoe said:
It really depends on your device, but you certainly can't base the X updates on how it went with other phones.
You have 4.4.3 on there? Who is your carrier, or what model X is it? Have you unlocked the bootloader?
My advice, if you can unlock the bootloader, do so now. Root the phone, rename the 3C_OTA.APK and 3C_OTA.ODEX which reside in /system/priv-app. That will prevent any OTA from downloading and prompting you to install.
Then sit tight, wait for Lollipop to start being pushed, and the inevitable feed back that will come as people rush to install it.
Based on that feed back, you can stay where you are, or rename 3C_OTA.APK and 3C_OTA.ODEX back to their original names, and take the update.
Click to expand...
Click to collapse
KidJoe,
Since I am running stock 4.4.4, rooted, running TWRP 2.7.1.1 and using the XPosed X Tether module. Going with the current understanding that TWRP is not compatible (as of yet anyway) with 5.0 Lollipop, and to preclude from taking the 5.0 OTA, I went ahead and using root explorer, renamed the above two files in your post above by adding .bak to file extension. I also went into to etc/security and renamed the file otacerts.zip to otacerts.zip.bak. I'm thinking I should be good and that renaming these 3 files will not have any unintended consequences on the Moto X XT1060 and keep the phone from taking the OTA at this point in time. Thanks!
doiy, kid joe got you sorted, i missed that. sweet.. I did the same thing and renamed that file, I don't plan on upgrading to 5.0 OTA until after reviews etc come in for that OTA for moto x 2013.. or unless 5.0 gets xposed or something like it from chainfire
rob6909 said:
KidJoe,
Since I am running stock 4.4.4, rooted, running TWRP 2.7.1.1 and using the XPosed X Tether module. Going with the current understanding that TWRP is not compatible (as of yet anyway) with 5.0 Lollipop, and to preclude from taking the 5.0 OTA, I went ahead and using root explorer, renamed the above two files in your post above by adding .bak to file extension. I also went into to etc/security and renamed the file otacerts.zip to otacerts.zip.bak. I'm thinking I should be good and that renaming these 3 files will not have any unintended consequences on the Moto X XT1060 and keep the phone from taking the OTA at this point in time. Thanks!
Click to expand...
Click to collapse
I never touched the OTACERTS.ZIP, but you should be good to NOT get the Lollipop update until you rename those back
I recently upgraded my phone to an AT&T S5 (I decided I didn't like the S6 specs). Currently, the phone is 100% stock, unrooted. I know that previous Samsung phones had problems with OTA updates when they were rooted. Now, with the possibility that the Lollipop OTA is coming soon, I'm hesitant to root until the OTA comes out. Here are my questions:
1. Should I wait to root until after the OTA hits the streets, or is there a strategy to root and still safely apply the OTA?
2. I don't want to be one of the first to get the OTA since it may be buggy. Is there a way to delay the OTA if I'm not rooted?
So, nobody has any thoughts about this?
I can't tell you what you should do but I can tell you what I would do. I would root now, load Titanium backup, and wait for 5.0 to come out. With TBU I freeze the OTA so it's not pushed without my permission. Additionally TBU will backup everything going forward so I can easily move up and restore my apps.
I believe the current process to root will work so be patient.
woody1 said:
So, nobody has any thoughts about this?
Click to expand...
Click to collapse
I wouldn't even take the OTA. Lots of issues with it. I am pretty sure LP will be the same.
I rooted mine, installed SafeStrap, and installed the XDK ROM, which eliminates all updates. My phone works great, does everything I want it to. Don't need problematic upgrades to downgrade my system.
cmerlyn said:
I wouldn't even take the OTA. Lots of issues with it. I am pretty sure LP will be the same.
I rooted mine, installed SafeStrap, and installed the XDK ROM, which eliminates all updates. My phone works great, does everything I want it to. Don't need problematic upgrades to downgrade my system.
Click to expand...
Click to collapse
Thanks to both of you for your suggestions. I think I'm going to go ahead and root and stay on the stock rom for a while. If the OTA shows up soon and looks worthwhile, I'll give it a try. Otherwise, I'll install SafeStrap and try a custom ROM.
Sure. Here's an easy answer: if you search for S5 AT&T and lolipop, you'll find lots of things that will say that AT&T will be taking its SWEET time putting an ota upgrade for lolipop out.
It is available from Samsung thru Kies, and I think I am personally going to take a new rom, and try and upgrade and unlock this piece of junque (and I upgraded from a Galaxy SII! )
Sigh
Been on lollipop for a bit now and I'm just not digging it. I don't like the double slide-down on the status bar, don't like that gravitybox doesn't seem to work well, I keep getting random reboots, and as far as I can tell, removable media doesn't seem to be working.
I've got a Verizon XT1060 developer edition and I'm unlocked. Upgraded from kitkat via OTA updates but did a factory reset of everything first, took the few small OTAs, then to lollipop.
I've been reading around about downgrading but it seems the majority of the posts with the danger danger notes are either for people who've been flashing stuff that wasn't officially for their phone, don't have developer edition devices, have root but don't want to lose it, etc.
What's the skinny on going back to the latest official kitkat version with a fully unlocked, XT1060? Can I just go grab the 4.4.4 image files from Motorola and flash ALL of them? Or do I need to skip flashing a couple files in there?
Kinda pissed that this update isn't going well. I suppose there's a chance I need to flash the stock files once Motorola posts them that'd help but that'll be a while and it's not going to change gravitybox support and the features I'm not digging.
Mike