Hello all
Have searched this forum, but im not really sure what to do.
I've used titanium backup to perm remove a few stock apps, the exchange stock app and amazon app
Now i can't recive any updates OTA, and i get this message..:
assert failed: apply_patch_check("/system/app/Stock.apk"....
E:Error in /sdcard/download/OTA_Ace_HTC_WWE_172_405_3_r2_1_32_405_6_release_1632939lowfu0y78jktpp2.zip
(status 7)
using 2.2 android version number 1.32.405.6
please help
//Cham
You can't accept OTA updates when you are rooted.
I see, but only used temp root with visionary
is that going to affect something?
Or what are my options to get a hold of updates in the future, a costum rom instead? I do kinda like the stock rom, just without stock apps
anyone?
Once again, if you are rooted, it doesnt matter how, you CANNOT accept ota update.
If you deleted something you shouldnt have, then restore the backup to that, or do a factory reset and re-root.
Ok i just figures since it was TEMProot that it didn't matter. Tnx for the reply, tried the factory default option (no luck), is there any place where I can get the Stock firmware to re-flash the phone?
Or would anyone in here recommend another rom ? Tons of custom roms, as I can tell.
Thread moved in Desire HD General.
go here and youll find your rom that you need,
you need the ones that are "RUU_Ace_HTC_WWE" in the file name, as these are what we call World Wide Editions
Thank you very much.
Just to make sure I do not **** something up, what are the steps i should follow, to install the rom?
This is what I did: http://forum.xda-developers.com/showthread.php?t=888109
Got the same problem -- some time ago I removed some "useless" apps from my /system/app folder, and when 1.72 update was released I wasn't able to install it in any way (I was trying to follow this guide). I restored the missing apps, and then everything went fine using the guide mentioned above!
Hope this helps.
sitlet said:
You can't accept OTA updates when you are rooted.
Click to expand...
Click to collapse
Sorry but that ain't correct... You *can* update your phone if you're rooted, the main problem is that root will be gone after update. The best solution is to *always* reject OTA updates provided by HTC and wait until devs here have found a safe way to update your device without losing root privileges.
Thank you
Thank you all, it gave perfectly sense since I'm quite happy with the stock firmware, i'll stick with this. The root is not so necessary for me at least for now
I'm glad it was corrected that visionary did not remove the ability for OTA, that was also what I've read before used it.
I hope I dont ask something that has been asked a milion times, but I didnt find very clear answers to this...
I got my A500 a few weeks ago, updated right out of the box to 3.2 and am happy so far BUT would now, after some use like to root it.
I see that its possible by downgrading, also read somewhere about an modified official updater that would work - what I want to know, how can I root that thing without any data loss?
Is the downgrading variant completely safe for that? Or, in any case, is there anything that can make a full backup without root?
Oh, and when finished - is there a ROM that basically just gives me root and throws out all of the crap ACER installed on the system?
Thanks ^^
Pray to the Acer Gods usually helps.
But really, if you synch your contacts to Google, then you have little to worry about. If.... you trust the cloud.
Paid apps, are always able to be re-installed through the Market.
If you have a recent version of the market, then you should be able to restore most of the free apps.
But hey, they were free, so who really cares....
SD card (photos and such) are not effected.
I've been researching this as well, but have yet to find a solution. It appears that there is no way to make a backup of your stock ROM before flashing a custom ROM, since you have to downgrade in order to root.
Since there are stock 3.2 rooted ROMs in the dev section, I'm tempted to just make that my initial flash after downgrading/rooting, set it up, then do a backup.
And fyi, astro file manager can backup your apps similar to titanium backup. I plan on doing that to restore the apps I've already installed.
Hope that helps a little. I mostly commented in case someone provides you with a solution...then I'll see it.
Chemo84 said:
I hope I dont ask something that has been asked a milion times, but I didnt find very clear answers to this...
I got my A500 a few weeks ago, updated right out of the box to 3.2 and am happy so far BUT would now, after some use like to root it.
I see that its possible by downgrading, also read somewhere about an modified official updater that would work - what I want to know, how can I root that thing without any data loss?
Is the downgrading variant completely safe for that? Or, in any case, is there anything that can make a full backup without root?
Oh, and when finished - is there a ROM that basically just gives me root and throws out all of the crap ACER installed on the system?
Thanks ^^
Click to expand...
Click to collapse
I must have been lucky. I followed the easiest path to downgrade on the tutorial from this forum. After I applied root and used acer recovery installer to install taboonay 2.2. I didn't clear cache or do a factory reset, and everything worked. Only lost the acer apps, which I was able to get back painlessly from either tabootools or gameloft. I am sure that people would not recommend going my route though.
Taboonay 2.2 is a pretty clean rom, and I feel it's nice with Richardtrip's 3.4 kernel.
just revert to 3.0.1 with the 2nd method of this thread http://forum.xda-developers.com/showthread.php?t=1276227 and you won't lose anything.
superfrancy97 said:
just revert to 3.0.1 with the 2nd method of this thread http://forum.xda-developers.com/showthread.php?t=1276227 and you won't lose anything.
Click to expand...
Click to collapse
Also works with 3.2.1 Australian default rom. Only problem is I lost default rom as I jumped into custom stuff at 3.2.1 and could not find info on how to back up the operating system without root.
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.
Hello everyone,
My Moto X Pure edition is on the way on the mail. I'm already excited to root it and get twrp on it. However, I believe the phone will come with android lollipop installed, and I should get an option for an OTA update for android 6.0.
My question is: Should I root my phone and install twrp BEFORE receiving the update, or after? I plan to use WinDroid Toolkit to root my phone and install twrp (seems to be the easiest way) so have any of you done it while having 6.0 already installed?
Your phone will most likely arrive with 6.0 pre-installed on it. You can't take an OTA with TWRP installed. I can't answer the WinDroid question.
Edit: It will most likely come with 6.0 already assuming you purchased it from Motorola.
quakeaz said:
Your phone will most likely arrive with 6.0 pre-installed on it. You can't take an OTA with TWRP installed. I can't answer the WinDroid question.
Edit: It will most likely come with 6.0 already assuming you purchased it from Motorola.
Click to expand...
Click to collapse
Thanks a lot for your help! It's good that the phone will most likely come with MM. Does Motorola also offer an OTA update to 6.0.1?
I wanted to flash a pre-rooted stock-based ROM because I thought it would be easier to get root. Although, my preference really would be to get the stock update, then just root that. The only reason I wanted to flash an already rooted ROM was because it seems kind of tricky to root it haha. Is the systemless root by ivcarlos the easiest way to root MM? Or have you perhaps found another way to root it on MM?
Additionally, just to make sure before I go on with anything: I should first let the clean phone upgrade to android 6.0.1, AFTER that I should unlock the bootloader, followed by installing TWRP and root, correct? @vertigo_2_20
Thank you for any help you can give me!
Henryy97 said:
Thanks a lot for your help! It's good that the phone will most likely come with MM. Does Motorola also offer an OTA update to 6.0.1?
I wanted to flash a pre-rooted stock-based ROM because I thought it would be easier to get root. Although, my preference really would be to get the stock update, then just root that. The only reason I wanted to flash an already rooted ROM was because it seems kind of tricky to root it haha. Is the systemless root by ivcarlos the easiest way to root MM? Or have you perhaps found another way to root it on MM?
Additionally, just to make sure before I go on with anything: I should first let the clean phone upgrade to android 6.0.1, AFTER that I should unlock the bootloader, followed by installing TWRP and root, correct? @vertigo_2_20
Thank you for any help you can give me!
Click to expand...
Click to collapse
IIRC, that's how I did it (OTA 6.0.1 > unlock bootloader > flash TWRP > root), though I did miss some things along the way that I only found out about after the fact, so I've included warnings about those thing here. Before I rooted, I read the following (and a LOT more, but these are the primary ones I based how I did it on):
ivcarlos' method, which you mentioned
And this, which is what I followed for rooting, though I don't remember why. I also had to use 2.62-3 as mentioned in the instructions vs 2.65 which is mentioned at the end as verified working, since it didn't work for me.
I ran across this as well, probably when 2.65 didn't work, and there's some good tidbits in there, worth reading through.
I also found this, but only after I finished rooting with the other method, and I didn't have the time to mess with it. I don't know enough to say whether it's really a better method or not, but something worth checking out if you have the time.
Just make sure you backup anything you want to keep (phone log, texts, pictures, etc) before unlocking the bootloader. I recommend SMS Backup & Restore with Titanium Backup as a secondary backup. Then, use fastboot to back up your recovery before flashing TWRP (I didn't know to do this until too late). Also, make sure you back up your /system and /boot partitions (don't need /data, since you're dealing with a freshly wiped phone from unlocking the bootloader, so nothing there to back up) with TWRP (and store the backups on the external SD card and/or your computer) as soon as you get TWRP flashed, before you do anything else.
Remember, anything you do that modifies /system can potentially break the "systemless" aspect of this root, thereby breaking Android Pay as well as the ability to receive OTA updates. Examples of things that might do this are AdAway (there's apparently a systemless file that needs to be flashed before installing it, which I didn't realize until too late, so mine may be broken already) and battery apps like GSam and BetterBatteryStats. I've yet to get an answer on if these really do break it, though. One that definitely will is Xposed, but I just found there's a systemless version, so when I get time I plan on trying that out. I think even if you do break it you can just a) reflash your backup (/recovery, /boot, & /system) then take an OTA and reflash TWRP and re-root, or b) flash the updated partitions from the OTA then reflash recovery and re-root. Of course, any of those things that changed /system (AdAway, Xposed, battery apps, etc), will probably be broken by this, and I believe they're supposed to be uninstalled first and reinstalled after.
I wouldn't doubt if I've screwed something up, so hopefully somebody can correct me on anything I did, as well as provide more information regarding the breaking of systemless.
vertigo_2_20 said:
IIRC, that's how I did it (OTA 6.0.1 > unlock bootloader > flash TWRP > root), though I did miss some things along the way that I only found out about after the fact, so I've included warnings about those thing here. Before I rooted, I read the following (and a LOT more, but these are the primary ones I based how I did it on):
ivcarlos' method, which you mentioned
And this, which is what I followed for rooting, though I don't remember why. I also had to use 2.62-3 as mentioned in the instructions vs 2.65 which is mentioned at the end as verified working, since it didn't work for me.
I ran across this as well, probably when 2.65 didn't work, and there's some good tidbits in there, worth reading through.
I also found this, but only after I finished rooting with the other method, and I didn't have the time to mess with it. I don't know enough to say whether it's really a better method or not, but something worth checking out if you have the time.
Just make sure you backup anything you want to keep (phone log, texts, pictures, etc) before unlocking the bootloader. I recommend SMS Backup & Restore with Titanium Backup as a secondary backup. Then, use fastboot to back up your recovery before flashing TWRP (I didn't know to do this until too late). Also, make sure you back up your /system and /boot partitions (don't need /data, since you're dealing with a freshly wiped phone from unlocking the bootloader, so nothing there to back up) with TWRP (and store the backups on the external SD card and/or your computer) as soon as you get TWRP flashed, before you do anything else.
Remember, anything you do that modifies /system can potentially break the "systemless" aspect of this root, thereby breaking Android Pay as well as the ability to receive OTA updates. Examples of things that might do this are AdAway (there's apparently a systemless file that needs to be flashed before installing it, which I didn't realize until too late, so mine may be broken already) and battery apps like GSam and BetterBatteryStats. I've yet to get an answer on if these really do break it, though. One that definitely will is Xposed, but I just found there's a systemless version, so when I get time I plan on trying that out. I think even if you do break it you can just a) reflash your backup (/recovery, /boot, & /system) then take an OTA and reflash TWRP and re-root, or b) flash the updated partitions from the OTA then reflash recovery and re-root. Of course, any of those things that changed /system (AdAway, Xposed, battery apps, etc), will probably be broken by this, and I believe they're supposed to be uninstalled first and reinstalled after.
I wouldn't doubt if I've screwed something up, so hopefully somebody can correct me on anything I did, as well as provide more information regarding the breaking of systemless.
Click to expand...
Click to collapse
Thank you for your reply! I'll read the links you sent me, although from what I can see the "root done right" is for the nexus 6, and if it works for the moto x pure it doesn't seem to be overall that much beneficial over the systemless root.
What exactly is the effect of breaking the "systemless" aspect of the root? For example, if I install AdAway, what will happen? I didn't really get that from your post.
Perhaps after all this process, I'll write a how-to guide, heh
So according to your experience, SUPERSU 2.62-3 is the adequate version to use for android 6.0.1?
Thanks again!
Henryy97 said:
Thank you for your reply! I'll read the links you sent me, although from what I can see the "root done right" is for the nexus 6, and if it works for the moto x pure it doesn't seem to be overall that much beneficial over the systemless root.
What exactly is the effect of breaking the "systemless" aspect of the root? For example, if I install AdAway, what will happen? I didn't really get that from your post.
Perhaps after all this process, I'll write a how-to guide, heh
So according to your experience, SUPERSU 2.62-3 is the adequate version to use for android 6.0.1?
Thanks again!
Click to expand...
Click to collapse
My understanding is that breaking it will render Android Pay inoperable and will make it so you can't take an OTA, though as I mentioned, it seems you still can by reverting back, it's just a LOT more work. But again, as I said, I'm not completely sure and I haven't been able to get an answer.
As for the supersu version, it doesn't really matter, because you'll just update it once you're rooted and booted into the OS. I just found that, despite what that post said, 2.65 did not work for me, so I had to flash 2.62-3 which did. Not a big deal, was just a little frustrating and scary when 2.65 didn't work because I was worried that I broke something and that the method wasn't going to work.
Edit: Good catch BTW on the link having to do with the Nexus. I didn't even look at what sub-forum it was in. At least it's one less thing to worry about for now, though I do hope it spreads to more devices, because we could always use more, not to mention better (assuming it is) ways of doing things.
vertigo_2_20 said:
My understanding is that breaking it will render Android Pay inoperable and will make it so you can't take an OTA, though as I mentioned, it seems you still can by reverting back, it's just a LOT more work. But again, as I said, I'm not completely sure and I haven't been able to get an answer.
As for the supersu version, it doesn't really matter, because you'll just update it once you're rooted and booted into the OS. I just found that, despite what that post said, 2.65 did not work for me, so I had to flash 2.62-3 which did. Not a big deal, was just a little frustrating and scary when 2.65 didn't work because I was worried that I broke something and that the method wasn't going to work.
Edit: Good catch BTW on the link having to do with the Nexus. I didn't even look at what sub-forum it was in. At least it's one less thing to worry about for now, though I do hope it spreads to more devices, because we could always use more, not to mention better (assuming it is) ways of doing things.
Click to expand...
Click to collapse
Thanks. I am aware that you can revert back to lollipop, and do the update from there whenever you want to update to a newer OTA MM update. However, my real question is, what does it mean to break the systemless aspect? I know that it will prevent further OTA updates, but will xposed work as it should, etc? If I am rooting my device, it's really to get xposed. So, if it means that I must revert to an unrooted stock rom everytime I wanna update, then so be it. I just want to make sure that breaking the systemless root aspect will not make the ROM unstable. Will it?
Henryy97 said:
Thanks. I am aware that you can revert back to lollipop, and do the update from there whenever you want to update to a newer OTA MM update. However, my real question is, what does it mean to break the systemless aspect? I know that it will prevent further OTA updates, but will xposed work as it should, etc? If I am rooting my device, it's really to get xposed. So, if it means that I must revert to an unrooted stock rom everytime I wanna update, then so be it. I just want to make sure that breaking the systemless root aspect will not make the ROM unstable. Will it?
Click to expand...
Click to collapse
I think you'll find all the info you're looking for and more in those links. But in summary, as I said, AFAIK the only consequence is breaking OTAs. It does not prevent you from using xposed, rather xposed is one of the things that breaks it. Systemless is so called because it roots without affecting the /system partition, therefore preventing the breaking of Android Pay and allowing OTAs. Once /system is modified (unclear if at all or just beyond a point), these two will no longer function. So if you "break" the systemless root by doing stuff that modifies /system (i.e. xposed, etc), you basically now have a standard (non-systemless) root, which simply negates the benefits it provides. But as far as I could tell, systemless is the only option anyway, so you just do it since it works and it's easy, then you either are careful not to break it if Pay/OTAs are important to you, or if you don't care about those then you just do whatever you want just as if you were rooted in the traditional way. But as I said, once I get the time, I plan to try out the systemless xposed, though it may not matter since I might have already broken it, but may as well, and maybe it'll mean not having to uninstall it when it comes time to take an OTA. If you play with it and figure it out, let me know.
vertigo_2_20 said:
I think you'll find all the info you're looking for and more in those links. But in summary, as I said, AFAIK the only consequence is breaking OTAs. It does not prevent you from using xposed, rather xposed is one of the things that breaks it. Systemless is so called because it roots without affecting the /system partition, therefore preventing the breaking of Android Pay and allowing OTAs. Once /system is modified (unclear if at all or just beyond a point), these two will no longer function. So if you "break" the systemless root by doing stuff that modifies /system (i.e. xposed, etc), you basically now have a standard (non-systemless) root, which simply negates the benefits it provides. But as far as I could tell, systemless is the only option anyway, so you just do it since it works and it's easy, then you either are careful not to break it if Pay/OTAs are important to you, or if you don't care about those then you just do whatever you want just as if you were rooted in the traditional way. But as I said, once I get the time, I plan to try out the systemless xposed, though it may not matter since I might have already broken it, but may as well, and maybe it'll mean not having to uninstall it when it comes time to take an OTA. If you play with it and figure it out, let me know.
Click to expand...
Click to collapse
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Henryy97 said:
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Click to expand...
Click to collapse
I bought my phone ~5-6 months ago. When I got it, the MM update was waiting (released late last year). Probably ~2 months later, another update came through. Since then, nothing. So it looks like probably 3 maybe 4 a year. I'd rather be rooted with all the benefits than get a small update, though I'd really rather have both.
6.0.1 is not out yet although there is a reteu version posted which works great. Rooting is as simple flashing su 2.62-3 with twrp.
lafester said:
6.0.1 is not out yet although there is a reteu version posted which works great. Rooting is as simple flashing su 2.62-3 with twrp.
Click to expand...
Click to collapse
I'll check it out. Do you mind sharing the link to that version just in case? I am very confused now though, because @vertigo_2_20 says he has 6.0.1, and you say you didn't get it. Perhaps location matters? Can you elaborate a little bit more?
And actually, I've just realized: I think I was looking at too many outdated posts perhaps with all the complicated root procedures such as the one by ivcarlos. The guide that amit.lohar made is very simple which is the one vertigo kindly shared in this OP. One final question @vertigo_2_20 (sorry for so many questions). Does the method by amit.lohar work for 6.0 anddd 6.0.1? I would assume so since they're pretty much very similar. What is your take on this?
I assumed I was on 6.0.1 because I received a system update after being on MM, so I don't know what else it could be. Though it does just say 6.0 in settings. Regardless, I only did it a few weeks ago, so if you're fully updated, you'll be the same as what I was. Even if not, I would think it wouldn't matter. As long as you do a back up before messing with things, worse case scenario is you screw something up and restore the backup.
Henryy97 said:
I'll check it out. Do you mind sharing the link to that version just in case? I am very confused now though, because @vertigo_2_20 says he has 6.0.1, and you say you didn't get it. Perhaps location matters? Can you elaborate a little bit more?
And actually, I've just realized: I think I was looking at too many outdated posts perhaps with all the complicated root procedures such as the one by ivcarlos. The guide that amit.lohar made is very simple which is the one vertigo kindly shared in this OP. One final question @vertigo_2_20 (sorry for so many questions). Does the method by amit.lohar work for 6.0 anddd 6.0.1? I would assume so since they're pretty much very similar. What is your take on this?
Click to expand...
Click to collapse
No I don't get links for people... this forum is small and easy to read. Dev section has one pre loaded with franken and there are two threads in general.
Henryy97 said:
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Click to expand...
Click to collapse
If receiving the OTA updates is something you really want, systemless root will allow you to get them with a lot less effort. The trick is knowing which of the apps that require root privileges will end up modifying your system. Avoid the ones that will and you can enjoy root with less work to get updates. If the only root required apps you are interested in modifies the system, then it will be a matter of what you value more.
Sent from my awesome phone!
That reminds me of another thing I haven't yet figured out. If /system is modified, I'm assuming the OTA will still show up and just won't install, but I wonder if it won't even show up anymore. Anyone know?
aybarrap1 said:
If receiving the OTA updates is something you really want, systemless root will allow you to get them with a lot less effort. The trick is knowing which of the apps that require root privileges will end up modifying your system. Avoid the ones that will and you can enjoy root with less work to get updates. If the only root required apps you are interested in modifies the system, then it will be a matter of what you value more.
Sent from my awesome phone!
Click to expand...
Click to collapse
Ahhh! I guess I'll just flash ROMS to update my phone then because I need my xposed Besides, after 6.0, if we want root, we can only get the systemless one anyway, right?
Also, I did not quite understand something about systemless root. If the root is 'systemless', then how can apps still edit the system? I've read up that after a memory wipe, the root will actually go away but what happens if I have apps that already modified the system? I just don't quite get how the apps can get into the system and modify it, if the root itself cannot do that because it is systemless. Am I getting the wrong idea here? I've read, and read, and read. I can't find an answer to that :/ According to what you have said though, if I were to get an app that modifies the system, then it would essentially *break* the systemless aspect of it, right? Therefore, it just becomes a normal root?
I feel like I'm going in circles now so I hope someone will be able to explain this for me or just point me in the right direction!
Systemless root does not mean root doesn't have access to /system, it simply means a way of gaining root access without modifying the /system partition, because if you gain root with the old methods, which DO modify /system, it breaks Android Pay and OTAs. Root still has access to modify system, hence why you have to be careful in installing apps, xposed, etc, because if they have root access, they can modify it, and if they do, your systemless root just became useless. The whole point is to NOT modify it so as to keep those certain functions intact, but it doesn't prevent you from doing so after gaining root.
vertigo_2_20 said:
Systemless root does not mean root doesn't have access to /system, it simply means a way of gaining root access without modifying the /system partition, because if you gain root with the old methods, which DO modify /system, it breaks Android Pay and OTAs. Root still has access to modify system, hence why you have to be careful in installing apps, xposed, etc, because if they have root access, they can modify it, and if they do, your systemless root just became useless. The whole point is to NOT modify it so as to keep those certain functions intact, but it doesn't prevent you from doing so after gaining root.
Click to expand...
Click to collapse
My experience was rooting 5.1.1 on the new phone. I backed up at every stage. I tried a few roms, no big deal. I liked 5.1.1 better due to micro sd card usage. I stupidly allowed the OTA to attempt to install. I knew it would fail but hoped it would stop nagging. The result I did not expect was phone continually rebooting on its own, trying to complete the update. After it completed the reboot it would start to shut down and begin the reboot process again. I restored a backup and froze the Motorola Update app with Titanium Backup. Problem solved. Don't do what I did!
Why would you want to stay on L? M is so much better. Between Doze and permission control, you'll have better battery life and more privacy and security. Not to mention the increased security from having more up-to-date software. I'd recommend just taking the update.