The other thread was just too messy with too much cross information.
So, here's the quick and dirty. If you're on 4.4. and rooted you can upgrade to 4.4.2 after disabling Gravity Box and ANY mods (wifi tether, etc) and you will keep root but you will lose the ability to write to the system. This effectively makes root useless.
It's unlikely 4.4.2 will ever be rooted, but there is some sliver of hope that a solution will be found (likely involving SBF) that allows you to retain root and /system RW but it can't be taken for granted.
There's lots of other info, but this thread is just designed to separate out the discussions.
Just to add..
Inside the OTA is a manifest file which which contains check sums for files which need to exist on your phone. If the expected files are not on your phone, or the checksums of the files don't match the manifest, the OTA will fail. Hence why you need to undo some of the "hacks" and "mods"
Addtioinally to install the OTA, you need to have stock recovery on your phone. If its not on there, the OTA will either fail, or worse, put you in a boot loop! (erasing your phone's cache can help you out of the loop... mfastboot erase cache )
Once you are on 4.4.2, you can not downgrade your rom to 4.4 or older!! Trying to downgrade can/will result in bricking your device.
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
When MotoWPNoMo came its disabling write protection was "permanent" (it survived flashing between the roms which were out at that time) however it does NOT survive the 4.4.2 OTA.
The statement in the initial post... "keep root but you will lose the ability to write to the system. This effectively makes root useless. " is 100% accurate for those with locked bootloaders.
I got the notification this morning when I woke up that the OTA was downloaded and ready to install. It was a persistent notification, and I didn't want it there. I long pressed on it and went to app info, which was MotoOTA. I force stopped it, which did remove the notification, but it came back immediately.
I then unchecked the "show notifications" box and it was gone. I'm not really a fan of freezing apps with TiBu or anything like that, so this worked for me. I don't really care to update unless I can keep root and have write protection off.
I didn't see anything in the changelog that really implied that I'm missing much by not upgrading, for now at least. I decided to get the Moto Maker edition because I valued the customization more than then unlocked bootloader. The phone works great and does everything I need it to right now, so I have no desire to upgrade and lose root yet.
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
fury683 said:
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
You don't have to boot into recovery each time. You do need to soft reboot each time after a hard reboot though for it to stick
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
fury683 said:
...One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
The early root processes (RockMyMoto and SlapMyMoto) replaced stock recovery with a trick that booted the phone with write protect disabled. To take the OTA, you need to put stock recovery back, thus removing this trick.
Later, MotoWPNoMo replaced the trick of booting to a tricked recovery, and allowed Write Protection to be disabled for normal boot too, and allowed stock recovery to be put back on, but this doesn't survive the OTA.
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
evandena said:
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
Click to expand...
Click to collapse
No. Put your phone in bootloader mode... then...
mfastboot erase cache
KidJoe said:
No. Put your phone in bootloader mode... then...
mfastboot erase cache
Click to expand...
Click to collapse
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
evandena said:
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
Click to expand...
Click to collapse
Have to enter that command from the PC
Wifi Tether require Write Protection?
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You'll probably have to keep the file on your phone to replace each time you do a hard reboot. Without R/W, your changes won't stick after a boot. Otherwise, I think you can still use the entitlement trick without an issue other than it not sticking.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
I'd like to know this too. At this point the only thing I really use root for is Greenify, which no longer requires root, tethering with my unlimited data (VZ), and bypassing the exchange pin requirement.
KidJoe said:
Have to enter that command from the PC
Click to expand...
Click to collapse
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
CartlandSmith said:
you select recovery by hitting vol up button.
Click to expand...
Click to collapse
Yep, was. It was booting to safe mode when Recovery was selected.
I should clarify, I don't use the entitlement hack I just use the Wifi Tether apk. Just wondering if it requires write protection to be disabled or not. Thanks.
If I take the OTA and have root but no system RW, is it still possible to install Xposed, soft reboot, and it works normally until a hard reboot happens? Or is Xposed completely broken?
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You're talking "wifi tether for root" like this -> https://code.google.com/p/android-wifi-tether/
I don't think it will work due to the changes it makes when you start and stop tethering. (It appears to update files in the normally write protected area). Then again, if temp changes can be made after 4.4.2 is installed, it might work.
I think you and I are the only ones who use that app.. most everyone else is using Xposed or the hacked entitlement apk.
evandena said:
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
Click to expand...
Click to collapse
If it's booting normally when you select recovery, it's because your recovery is missing - probably because you used SlapMyMoto.
You need to restore your recovery... you can boot into fastboot, then write the correct recovery to your phone with fastboot flash recovery recovery.img, where recovery.img is a file pulled out of the SBF package for whatever version you're running.
You guys really should just wait! Even if a new root method isn't discovered, you will be able to flash a stock 4.4.2 ROM or Eclipse's stock-based ROM via Safestrap soon enough. Certainly not worth risking losing root! Patience!
Sent from my Moto X
Related
Hey guys, will the android update 4.2.2 erase everything on my nexus?I am rooted and unlocked, so if the main update thing does erase all of my data is there another way to update without loosing any of my data? I used the nexus toolkit to root, and I know there was an option to reinstall android without erasing data, but is that possible with a newer version of android..
Thanks
Micro
No it will not erase everything.
Because you are rooted, there is a chance that the OTA will not succeed, depending on how close to stock you are. (Some root apps appear to diddle a variety of things in /system, and if any of these things are targets of the OTA patching process, the OTA will fail). Also if you have a custom kernel, this particular OTA will not succeed.
If the OTA fails, no worries - it always fails during initial verification steps when it is checking to make sure that the checksums of targeted files exactly matches what it expects, before anything on your tab has been altered. So, if it fails don't freak out - everything on your tablet is the same as before the OTA started.
If it succeeds, you will loose root as a result of the setuid/setgid permissions of the "su" binary getting reset by the OTA installer script. You can either manually fix that with a "chmod" command (via adb with the custom recovery running and /system mounted) or you can simply re-flash the same SuperSU (or Superuser) root installer kit that you used when you originally rooted. The OTA also flashes a new stock recovery in place, so you will need to re-flash your custom recovery back into place after it has finished. That should be no problem so long as you know how to do so, using either fastboot directly or a toolkit.
I'm not sure you needed to start a new thread on this - scroll through a few pages here and see just how many "4.2.2. update question" threads there have been recently.
good luck.
PS If your OTA fails and you want to try patching things by hand, read through all the trouble threads in here before posting. Each time it runs, it will report the source of the error in /cache/recovery/recovery.log. As always, make a Nandroid backup before you begin.
Sorry what exactly does ota mean? And so your saying there's no way to update without loosing my data? If that's the case I'm not updating because I'm filled to the max with data
Thanks
Micro
microzee said:
Sorry what exactly does ota mean? And so your saying there's no way to update without loosing my data? If that's the case I'm not updating because I'm filled to the max with data
Thanks
Micro
Click to expand...
Click to collapse
Which part of this:
bftb0 said:
No it will not erase everything.
Click to expand...
Click to collapse
did you find confusing?
I said that it will either succeed or fail, and if it fails it will do so in a way where nothing changes. If it succeeds, it will change some things, but not the things you are referring to as "my data".
OTA = Over The Air (update)
I used rootkeeper, temp unroot then installed ota update by toching on it. But after successfully updating my tablet is still on 4.2.1. Pls help. Even after updateing application msg on boot ithas not updated.
Sent from my Nexus 7 using xda app-developers app
sukhjit_bhullar said:
I used rootkeeper, temp unroot then installed ota update by toching on it. But after successfully updating my tablet is still on 4.2.1. Pls help. Even after updateing application msg on boot ithas not updated.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I was wondering if RootKeeper would work or not.
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
Wait....I just tried usig RootKeeper to temporarily un-Root the device then upgrade to 4.2.2 and it seems to have worked without an issue. I let it run through the entire upgrade, it rebooted, I looked to see what version I was on, it shows as 4.2.2, I then used RootKeep to restore Root, it worked like it was supposed to and it looks like it kept 4.2.2 as well.
I've tested a few apps that need Root and they worked just fine.
Hi all,
I've the same Problem here. the OTA-Update fails on my Nexus 7 (rooted). The message is only the green Robot with "Error". After restarting I can see that the version is still 4.2.1 :crying:
This is not the mainpoint (I've read up to now some threads which describing this issue). My point is: I can not restart the OTA-Update. There is no message whicht tolds me, that there is an update avalible... neither in the statusbar nor in the Settings.
Additionaly I can not find the log-file, which was some times described, where the error will be explained (I think it was deleted after the second restart).
Can someone explain me, how I can restart the OTA? Is it possible with the Framework-data deletion-trick? If I use this trick, what will be deleted in the Framework? Is there a place where the file /cache/recovery/recovery.log will be backuped?
If here is the wrong place for my questions, I'll make a new thread, but I think the thread which I've chosed fits it more or less
BR
SolarPlexus said:
Can someone explain me, how I can restart the OTA? Is it possible with the Framework-data deletion-trick? If I use this trick, what will be deleted in the Framework?
Click to expand...
Click to collapse
it's the framework data deletion trick*, yes. If you find solution to the update error problem, please keep us posted, cause i have the same issue...
*settings->apps->all->google service framework->force close->clear data. After that you go to the update menu (settings->about tablet->system updates) and tap on check now.
Ok guys it looks like Jcase did it again he created an exploit that gets write protecton off for good or until an OTA. He states this will survive even an FXZ or factory data reset.
Here is what I did took about 15 min. go here ---->http://forum.xda-developers.com/showthread.php?t=2551113 down load the exploit follow the instructions it's very easy the exploit does it all. I am not sure if I needed to do this or not but I did to be safe I used fastboot and put stock recovery back. Just take the recovery.img from the FXZ and open a command prompt type in this command------> fastboot flash recovery recovery.img
You must be in fastboot obviously it will flash recovery back and you lose WP off. You then run MotoWpNoMo and it bypasses WP protection for ever or until OTA from what I have read. Open a command prompt and type in this command------> adb shell getprop ro.boot.write_protect to check if write protection is disabled it will return a value of "0". No more having to boot into recovery to make system changes that require writer protection off this is true root. Great job Jcase!!!!!!!!!!!!!!!!!!!!
Oh and we have stock recovery back and I beleive that voodoo ota root keeper works on 4.2.2 so I think we will have a very easy time upgrading to 4.4 and not have to re-root this is just a theory at this point.
I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit.
Why couldn't this come at the beginning of a weekend, instead of a week? Aaaarrrrrggghhhh!
fat-fingered and Maxx-ed out.
Einsteindks said:
Why couldn't this come at the beginning of a weekend, instead of a week? Aaaarrrrrggghhhh!
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
It actually did but I worked all weekend and was not able to try it until today but it is SUPER EASY TO DO.
The other plus to this is voodoo still protects root on 4.2.2 so since we have stock recovery back we SHOULD not guaranteed but should be able to download the update to our sdcard an install 4.4 through stock recovery and keep root. The only question is if we would need to run the exploit again to get write protection off. I don't know if it would survive the OTA but I am leaning on it not surviving. Not that it matters this works on 4,4 anyway.
Another quick way to see if WP is off is to uninstall then re-install SS recovery we could not do that before unless we booted in to recovery with WP off. I just tried it and it works great.
Worked perfect on my Mini. Just be patient and keep an eye on it for granting superuser permission and unlocks after reboots.
should i just wait for kitkat to come out? because i dont feel like refreshing everything and starting over lol.. since i went back to stock and not able to save data XD
bigv5150 said:
Ok guys it looks like Jcase did it again he created an exploit that gets write protecton off for good or until an OTA. He states this will survive even an FXZ or factory data reset.
Here is what I did took about 15 min. go here ---->http://forum.xda-developers.com/showthread.php?t=2551113 down load the exploit follow the instructions it's very easy the exploit does it all. I am not sure if I needed to do this or not but I did to be safe I used fastboot and put stock recovery back. Just take the recovery.img from the FXZ and open a command prompt type in this command------> fastboot flash recovery recovery.img
You must be in fastboot obviously it will flash recovery back and you lose WP off. You then run MotoWpNoMo and it bypasses WP protection for ever or until OTA from what I have read. Open a command prompt and type in this command------> adb shell getprop ro.boot.write_protect to check if write protection is disabled it will return a value of "0". No more having to boot into recovery to make system changes that require writer protection off this is true root. Great job Jcase!!!!!!!!!!!!!!!!!!!!
Oh and we have stock recovery back and I beleive that voodoo ota root keeper works on 4.2.2 so I think we will have a very easy time upgrading to 4.4 and not have to re-root this is just a theory at this point.
I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit.
Click to expand...
Click to collapse
you mean i can keep the root by flash back the stock recovery.img ? so i can still receive the ota , and have the root after update ?
I doubt that you can keep your root and take the OTA. It caused a whoping lot of problems last time around, and I don't see it being any different when we take KitKat either. Best to flash a stock version of the ROM, then take the update. You may still keep write protection off.
fat-fingered and Maxx-ed out.
Einsteindks said:
I doubt that you can keep your root and take the OTA. It caused a whoping lot of problems last time around, and I don't see it being any different when we take KitKat either. Best to flash a stock version of the ROM, then take the update. You may still keep write protection off.
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
That is not necessarily true. The issue with the last update was taking the ota with root still installed. Voodoo still works on 4.2.2 so if you protect root and then unroot with voodoo you should be able to take the update and then restore root after the update. I used voodoo on the last update and kept root what screwed me was I lost write protection off. When I tried to run pwnmymoto it saw I was already rooted and wouldn't run the exploit so I was stuck till I could fxz and run pwnmymoto again. That won't happen here since we have write protection off script now. So you use voodoo then restore root then run motowpnomo and you will have root and write off protection.
bigv5150 said:
That is not necessarily true. The issue with the last update was taking the ota with root still installed. Voodoo still works on 4.2.2 so if you protect root and then unroot with voodoo you should be able to take the update and then restore root after the update. I used voodoo on the last update and kept root what screwed me was I lost write protection off. When I tried to run pwnmymoto it saw I was already rooted and wouldn't run the exploit so I was stuck till I could fxz and run pwnmymoto again. That won't happen here since we have write protection off script now. So you use voodoo then restore root then run motowpnomo and you will have root and write off protection.
Click to expand...
Click to collapse
root vs running your phone without a recovery. 2 different things , wouldn't you say? root was maintained through the OTA without any steps to hide it. rooting your phone doesn't mess up system updates. running without a recovery does.
Ok, so I am right in that when root is in place, it causes problems during updates (due to recovery used for WP off mode. Prob'ly the reason for most noob problems.). I wasn't aware that voodoo still worked. I certainly would've used it last time! I'll try it next time. So, theoreticaly, having a clean root, run the WP script, flash the OE recovery back on, and, using voodoo, KK should take, as long as the factory ROM isn't altered? Ideally then, we should be able to restore root, and still have a WP off after KK? I'm guessing, to be on the safe side, safestrap should temporarily be uninstalled. Probably not necessary, but it couldn't hurt.
Edit: looks like voodoo wont work into 4.4, due to KK.
fat-fingered and Maxx-ed out.
mistermojorizin said:
root vs running your phone without a recovery. 2 different things , wouldn't you say? root was maintained through the OTA without any steps to hide it. rooting your phone doesn't mess up system updates. running without a recovery does.
Click to expand...
Click to collapse
I don't understand what you are trying to say we have full root now and stock recovery like any other android device. Taking an OTA root wont survive the reason why people boot looped had nothing to do with root as much as not having recovery. Once the OTA tried to install itself there was no recovery to install it hence the bootloop.
Einsteindks said:
Ok, so I am right in that when root is in place, it causes problems during updates (due to recovery used for WP off mode. Prob'ly the reason for most noob problems.). I wasn't aware that voodoo still worked. I certainly would've used it last time! I'll try it next time. So, theoreticaly, having a clean root, run the WP script, flash the OE recovery back on, and, using voodoo, KK should take, as long as the factory ROM isn't altered? Ideally then, we should be able to restore root, and still have a WP off after KK? I'm guessing, to be on the safe side, safestrap should temporarily be uninstalled. Probably not necessary, but it couldn't hurt.
Edit: looks like voodoo wont work into 4.4, due to KK.
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
Correct but most of us have probably altered the system in one way or another and will have to fxz for a clean system to take update.
Voodoo wont work on 4.4 it works for 4.2.2 but I see what you are saying it may not restore root once on 4.4. That I am unsure of since I don't believe any one has tried it. Worst case scenario it doesn't restore root and you have to re-root then install stock recovery then run motowpnomo. I can't see the harm in trying.
this is not a root tool correct just RW tool?
StankFiss said:
this is not a root tool correct just RW tool?
Click to expand...
Click to collapse
Yep
fat-fingered and Maxx-ed out.
bigv5150 said:
Ok guys it looks like Jcase did it again he created an exploit that gets write protecton off for good or until an OTA. He states this will survive even an FXZ or factory data reset.
Here is what I did took about 15 min. go here ---->http://forum.xda-developers.com/showthread.php?t=2551113 down load the exploit follow the instructions it's very easy the exploit does it all. I am not sure if I needed to do this or not but I did to be safe I used fastboot and put stock recovery back. Just take the recovery.img from the FXZ and open a command prompt type in this command------> fastboot flash recovery recovery.img
You must be in fastboot obviously it will flash recovery back and you lose WP off. You then run MotoWpNoMo and it bypasses WP protection for ever or until OTA from what I have read. Open a command prompt and type in this command------> adb shell getprop ro.boot.write_protect to check if write protection is disabled it will return a value of "0". No more having to boot into recovery to make system changes that require writer protection off this is true root. Great job Jcase!!!!!!!!!!!!!!!!!!!!
Oh and we have stock recovery back and I beleive that voodoo ota root keeper works on 4.2.2 so I think we will have a very easy time upgrading to 4.4 and not have to re-root this is just a theory at this point.
I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit.
Click to expand...
Click to collapse
Am I the only one who noticed that this is totally missed credited? Jcase had nothing to do with this exploit. He is thanked for his contribution of root access that allows for it but that is all.
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Am I the only one who noticed that this is totally missed credited? Jcase had nothing to do with this exploit. He is thanked for his contribution of root access that allows for it but that is all.
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I guess so because everyone else knows how to read maybe you should read the WHOLE POST!!!!! is says at the end that "I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit". I mean it's actually in your post where you quoted me "reading comprehension it's a wonderful thing".
Crud. Just tried this, and it says driver errors and some junk. I KNOW everything IS installed, I put stock recovery back first. Security things/firewall off, to. Any ideas?
Edit: scratch request...was starting in fastboot mode...oops.
fat-fingered and Maxx-ed out.
Einsteindks said:
Crud. Just tried this, and it says driver errors and some junk. I KNOW everything IS installed, I put stock recovery back first. Security things/firewall off, to. Any ideas?
Edit: scratch request...was starting in fastboot mode...oops.
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
Lol can't tell you how many times I have made that mistake. Also using the wrong USB port for rsd and it doesn't see my phone.
I'm getting confused reading all of the posts that seem to be more about upgrading and rooting than this actual exploit. But my question is this.... I am rooted through jcase's exploit ("pwnmymoto" i think it's called) and still on the original firmware (pre camera update) with no recovery. Can i run this permanent WP killer from where my phone is now? Or do i have to flash the stock recovery back first? Also, will this wipe data?
To be honest, it's been a while since i flashed anything and i'm not real comfortable with the FXZ process just yet. All of my other phones have been highly supported by the devs and i have always had a utility to do all of the work for me. I'm hoping this will be pretty easy. I just want to know what i'm getting into before i soft brick my phone and have to wait days to figure out how to fix it.
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
No nothing roots 4.4 at this point.
vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.
akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.
mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Claghorn said:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Click to expand...
Click to collapse
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
madbat99 said:
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
Click to expand...
Click to collapse
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Claghorn said:
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Click to expand...
Click to collapse
Since lollipop it is very sensitive to anything different or missing in system. Just flash the 5.1 factory image with the ~w removed from the flash-all.bat file so it doesn't wipe data. Or use wugs to flash stock 5.1 image with "no wipe" enabled. Or like I said in previous you can always flash a clean system image of 5.0.2 then take ota. Either way will update you without wiping data.
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
neo5468 said:
... I don't get it why people bother with OTA all the time ...
Click to expand...
Click to collapse
I'm not really bothering with it - it just showed up and started bothering me .
1.Backup everything.
2.Flash 5.1 with nexus root toolkit.
3.Restore all the data.
4.Change your build in NRT to android 5.1
5.Root it and flash TWRP/CWM if you want.
6.?????
7.Profit! duh
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root.
Click to expand...
Click to collapse
... or wait for a week until someone will release a rooted 5.1 update
sensboston said:
... or wait for a week until someone will release a rooted 5.1 update
Click to expand...
Click to collapse
Why would you wait a week, we already waited too long for offical 5.1 to come out for our tablet. It is 5minutes of work, works 100% and also fasboot is the safest way to flash. Also you download the image straight from developers.google.com so there is no bs. I much rather flash that. But to each his own.
There is already a recovery flashable "stock rooted 5.1" thanks to scrosler (cleanrom Dev).
5.1 rooted ROM
neo5468 said:
Why would you wait a week
Click to expand...
Click to collapse
Agree, week is too long. A few days - better words And "one click" solution is much better in case of possible mistakes during flashing separate partitions, rooting etc...
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
Click to expand...
Click to collapse
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
beall49 said:
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
Click to expand...
Click to collapse
Custom recovery is fine. There is also a new boot loader to flash as well I think. You can also run the flash all batch file in the factory image and just remove the -w from it so it doesn't wipe data. But what you posted is also correct, but flash the boot loader too. If your rusty at it just use wugs toolkit, it will run the commands for you.
Solid, removing the -w was what I was forgetting. I knew there was something else.
Thanks!
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
nlinecomputers said:
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
Click to expand...
Click to collapse
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
madbat99 said:
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
Click to expand...
Click to collapse
No big deal really. I don't keep important data on it. It's mostly used for Kindle and games. Easy to fix.
Ok guys, bear with me.
I haven't done much "developing" or anything but I was able to get Xposed to install and now have Gravity Box running on my stock and locked Maxx. I used the KingRoot described and provided in the thread http://forum.xda-developers.com/droid-ultra/general/root-kingroot-4-4-4-su-6-7-t3117552 by @aviwdoowks. I had installed SuperSU Pro, KingRoot from the aforementioned thread, and the Xposed framework. After getting root with KingRoot, I went into SuperSU and checked survival mode (don't know if this does anything or not). Then, I went into Xposed and had it set to classical installation.
Now, this is where some persistence and effort went into effect. Through multiple attempts, of rebooting , KingRoot rooting, and trying to install Xposed, it finally took. Where aviwdooks, says to wait after booting to run KingRoot, I ran it immediately. As soon as root was obtained I would go into Xposed and run the Classical install. When it finally took, and asks to reboot, HIT CANCEL. Then from the Xposed menu, hit soft-reboot. So far I have survived multiple soft-reboots with Xposed running.
hope this helps someone.
@teerout
Kudos
Does it all go to data? Or rather once installed is system not utilized?
Btw the synchronization to gdrive is all sorted out now. My entire sd excluding 0/TiBU AND including legacy/TiBU!! Using Drive AutoSync.
Ti does tower above He in both convenience and allowing all user apps. I thought I would say it here as my thread is rather a mess
Avi,
I don't know how to answer that about data or system being utilized. Good work with getting the backups to work. I should do something similar.
teerout said:
Avi,
I don't know how to answer that about data or system being utilized. Good work with getting the backups to work. I should do something similar.
Click to expand...
Click to collapse
Still working?
How long now?
yes, still working. I had it running the other day, but wanted to make sure I could recreate it before posting on here. So from installing it this morning around 830, its past noon now, still working and surviving the soft-reboots. it looses functionality on a hard reboot, but can always be re-activated. hope to hear others can get it too.
@teerout
Hi,
You on su6-7.2?
We are all waiting to hear from you at 9:41am sharp.
Yes this is a known effect of a soft boot. You can change anything you want in /system (with root) as long as you only do soft boot. Only the user apps get initialized from terminating zygote.
You are better flashing in root per CrashXXL's thread. It would be nice to bake xposed in so it survives a KK OTA like root does but I suspect the only way is to image and flash the entire 6-72 /system partition.
aviwdoowks said:
@teerout
Hi,
You on su6-7.2?
We are all waiting to hear from you at 9:41am sharp.
Click to expand...
Click to collapse
No, SU6-7.
Yea, Ive been debating if I want to take the steps to work through the method crash put together. Got essentially the same results. Im tempted to try the "crash" method with an older fxz from Moto, but don't want to destroy my device.
teerout said:
No, SU6-7.
Yea, Ive been debating if I want to take the steps to work through the method crash put together. Got essentially the same results. Im tempted to try the "crash" method with an older fxz from Moto, but don't want to destroy my device.
Click to expand...
Click to collapse
Have many bricked that way? I just thought it was damn arduous.
Soooo how long?
aviwdoowks said:
Have many bricked that way? I just thought it was damn arduous.
Soooo how long?
Click to expand...
Click to collapse
don't think anyone has reported they bricked, im just hesitant to force my phone to brick through the process. im also trying to determine from this other thread by littletoslo in the QA section, if they used an older fxz file and got it to work.
xposed is still running with the gravity box mods, no hiccups.
On 6-7, the crashxxl method survives a hard reboot for both su and xposed. Using an older or newer fxz with the crash method will brick your device. Furthermore, just flashing an older version may result in serious gpt version issues.
Sent from my XT1080 using XDA Free mobile app
larsdennert said:
On 6-7, the crashxxl method survives a hard reboot for both su and xposed. Using an older or newer fxz with the crash method will brick your device. Furthermore, just flashing an older version may result in serious gpt version issues.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
To verify: I took the OTA this morning after a quick skim of xda, much to my chagrin, as I learned xposed didn't survive. To fix this, I can just reflash the 6-7 back using rsdlite and I'm back in business? Is anyone working on a fix for surviving hard reboot with baked in xposed on the 6-7.2? Thanks!
Yes the keys didn't update. You can do a full rsd flash of 6-7 and go back through the root/xposed process. If I find some time I will tackle making a system image of 6-7.2 with root and xposed. It may come down to root on the G4 though. If it doesn't have a R/O system image, I'm jumping ship from many years of Motorola.
larsdennert said:
Yes the keys didn't update. You can do a full rsd flash of 6-7 and go back through the root/xposed process. If I find some time I will tackle making a system image of 6-7.2 with root and xposed. It may come down to root on the G4 though. If it doesn't have a R/O system image, I'm jumping ship from many years of Motorola.
Click to expand...
Click to collapse
How this pertains to the op?
aviwdoowks said:
How this pertains to the op?
Click to expand...
Click to collapse
Basically just reaffirming that you can temp install xposed if you have some sort of root as long as you only soft reboot. Problem is you can only soft reboot so many times before it locks up and then you have to cold boot (Vol up + Vol Dn + Power). A better way is to bake it in to the r/o system image like CrashXXL and the Moto X. An even better way is to be done with Motorola LOL.
larsdennert said:
Basically just reaffirming that you can temp install xposed if you have some sort of root as long as you only soft reboot. Problem is you can only soft reboot so many times before it locks up and then you have to cold boot (Vol up + Vol Dn + Power). A better way is to bake it in to the r/o system image like CrashXXL and the Moto X. An even better way is to be done with Motorola LOL.
Click to expand...
Click to collapse
.... Reboot is hold power on X, Ultra & newer
Ok. :good:
I think I've just successfully extracted a modified 6-7.2 system image for flashing back. This should be interesting.
larsdennert said:
I think I've just successfully extracted a modified 6-7.2 system image for flashing back. This should be interesting.
Click to expand...
Click to collapse
you had my curiosity, now you have my attention.
See next post
Save for pics
used here