Related
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Thank you sir!
obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6
crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.
crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.
Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.
looking around i can not find anywhere that exactly states what versions of android and on what devices towelroot supports. My question specifically being for the S5 SM-G900A att phone. I am right now on lollipop and i realise i have to downgrade, but I only want to downgrade as little as possible to get towelroot to work. (the end goal being root access of course)
On another note I have two other questions i will ask here so as to not clutter the forum.
1. is there anyway to downgrade my android version without wiping all my data?
if not, any advice on backing up all my data before it gets wiped? mainly my photos, apps, and appdata.
2. I see the only custom recovery i can use is safestrap, i have read is some places that it can not backup your user data (videos, photos, etc.) and nowhere mention it does. question being if this is true and if so how can i back up all my data? i really like the idea of just doing weekly rom backups and being able to restore all my apps and all my data with very little lost (less then a week is good enough for me).
brazblue said:
looking around i can not find anywhere that exactly states what versions of android and on what devices towelroot supports. My question specifically being for the S5 SM-G900A att phone. I am right now on lollipop and i realise i have to downgrade, but I only want to downgrade as little as possible to get towelroot to work. (the end goal being root access of course)
On another note I have two other questions i will ask here so as to not clutter the forum.
1. is there anyway to downgrade my android version without wiping all my data?
if not, any advice on backing up all my data before it gets wiped? mainly my photos, apps, and appdata.
2. I see the only custom recovery i can use is safestrap, i have read is some places that it can not backup your user data (videos, photos, etc.) and nowhere mention it does. question being if this is true and if so how can i back up all my data? i really like the idea of just doing weekly rom backups and being able to restore all my apps and all my data with very little lost (less then a week is good enough for me).
Click to expand...
Click to collapse
If you took the OTA update to 5.0 their is currently no way to safely downgrade and root.
Towel root only worked on 4.4.2 kernel.
Safestrap no longer works in 5.0 either.
Just have to hang tight till someone figures out root for stock 5.0.
Thank you for the help, i did not realize it was for 4.4.2 only. (why no list of working versions) as well you say no safe way to downgrade.....are there options or is it impossible? I just got the phone recently and I wasn't the one to update it, I got it second hand and well i can't control what has happened to it before me. sadly it was updated to 5.0
I may attempt a unsafe downgrade if possible, it really depends on what risk levels and if it's risk of doing something wrong and bricking or if there is a risk out of your hands and it may or may not work. else i will just wait and not update my phone in the time being.
nutt_case said:
If you took the OTA update to 5.0 their is currently no way to safely downgrade and root.
Towel root only worked on 4.4.2 kernel.
Safestrap no longer works in 5.0 either.
Just have to hang tight till someone figures out root for stock 5.0.
Click to expand...
Click to collapse
brazblue said:
Thank you for the help, i did not realize it was for 4.4.2 only. (why no list of working versions) as well you say no safe way to downgrade.....are there options or is it impossible? I just got the phone recently and I wasn't the one to update it, I got it second hand and well i can't control what has happened to it before me. sadly it was updated to 5.0
I may attempt a unsafe downgrade if possible, it really depends on what risk levels and if it's risk of doing something wrong and bricking or if there is a risk out of your hands and it may or may not work. else i will just wait and not update my phone in the time being.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3077652
The above post is the unbrick/downgrade thread for the g900a.
You'll notice it says not to attempt if you've taken the OC4 ota...I'd read through their first. At this point it looks pretty risky.
Good luck either way you go!
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
cwhiatt said:
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
Click to expand...
Click to collapse
Hello Hiatt,
Thanks for using XDA Assist. What specific device do you currently have? There are so many devices here and each might deal with your question differently. I moved your other thread to off topic since it was referring to iPhones, but this one seems to have a more specific device in mind.
Thanks,
coal686
I presently have a Tmobile Galaxy S6 which is rooted and running Sick as Hell (version X).
From what I have read and heard it seems as though root and encryption together don't always play well together.
Also, it was the other post of mine that mentioned iPhones (the one about factory resets and eDiscovery).
cwhiatt said:
I presently have a Tmobile Galaxy S6 which is rooted and running Sick as Hell (version X).
From what I have read and heard it seems as though root and encryption together don't always play well together.
Also, it was the other post of mine that mentioned iPhones (the one about factory resets and eDiscovery).
Click to expand...
Click to collapse
Lol, that's what I said. The other post was more about the iPhone issue so I moved it to off-topic. Since you have a Galaxy S6, I'll move this thread there so people with that device can give you a more personalized answer.
I don't think that having root is an issue with encryption. I Had my S5 encrypted only problem was a ui crash when entering the boot password. That was specific to the rom I was using and simply had to enter password 1 or 2 characters at a time between errors.
But I do think there may be a problem with custom recovery and encryption.
My S5 was verizon, thus still locked bootloader and used safestrap to get to a custom recovery which wasn't always active.
I would talk to someone with a lot more knowledge then I about this further. But pretty sure just having root is not a problem the recovery is where you can have issues
cwhiatt said:
I did a couple of searches and came up empty but I am wondering if any ROM developers are working with encryption and root?
When I had my Galaxy S5 (Tmobile) it was first encrypted. I recall then once I rooted it I was no longer able to encrypt the device. I think there may have been some workarounds but they were pretty cumbersome to say they even worked at all.
I'm wondering if any developers are working that angle and if so should my inquiry be presented to developer of said ROM?
I also realize that encrypted devices do tend to read a bit slower than those no encrypted but I think I can live with that.
Please advise.
Best,
Hiatt
Click to expand...
Click to collapse
Hi there,
Root + Encryption can work together as long as no custom recovery involved, so if you get your root by exploit instead of installing custom recovery almost 99% chance you can have your phone encrypted while preserving the root privilege.
My case explained here : http://forum.xda-developers.com/galaxy-note-3/general/success-root-encryption-t3372958
I didn't have a problem with encryption and root. The only problem that I had was that my Galaxy S6 Edge needed to be encrypted before root. I could not encrypt my phone with the "stock" rooted kernel. Once I was encrypted, I could install TWRP and root via supersu systemless root.
Once I had root, I would use flashfire to back up and install because TWRP could not read the DATA partition since it was encrypted. For some reason, it seems once the phone has been decrypted, the data partition could be backed up with flashfire, and I would be able to restore a backup as well.
This is where I ran into issues. If you are flashing a custom rom that will require you to wipe data, your device will lose encryption. Because I can be somewhat of a crack flasher at times, and that I am too lazy to deal with having to re-encrypt and reinstall all my settings, I just opted to stick with an unencrypted phone.
Hopefully at some point, TWRP will be compatible with encryption so that lives will be easy for us crack flashers..until then, I will probably stick with an unencrypted device unless I just want to stick with a stock rom, or a custom rom that I can load up and not have to wipe data every time there is an update.
Hey there!
since hours im trying to get my S7 Edge G935F unrooted after ive placed apps as system apps.
equal if i try to unroot with magisk manager options, magisk uninstaller zip in twrp while rooted with magisk or when rooted with superSU with full-unroot option im always causing a boot loop and i need to flash the rom (Android 7.0 G935FXXS2DRA9_G935FDBT1DQJ1_DBT) from new. (Ive rooted via twrp in both cases)
Now ive tried with an app from playstore called "Impactor System Unroot" to my surprise it worked! but not as good as i hoped for because now im not rooted anymore but i cant pass safety net.... im running out of ideas and i hoped someone with more knowledge and better understanding may could come up with a magic trick! i beliefe that its somehow must be possible after all.
As always thanks for your time, help and answer!
Best regards
Chris
If your device now really has all traces of root removed, it's likely that it's an unlocked bootloader that is triggering SafetyNet. You'll have to relock it, but keep in mind that this will wipe your device. And if you don't do it right you might end up with a device that can't boot at all and be quite difficult to recover...
Why though? Is it really worth the hassle?
Didgeridoohan said:
If your device now really has all traces of root removed, it's likely that it's an unlocked bootloader that is triggering SafetyNet. You'll have to relock it, but keep in mind that this will wipe your device. And if you don't do it right you might end up with a device that can't boot at all and be quite difficult to recover...
Why though? Is it really worth the hassle?
Click to expand...
Click to collapse
So in other words unrooting and keeping custom system apps is not possible right? because wipe in order to relock the BL will take the away anyway
Just because of messing around more or less haha. wanted to see if i can somehow put a gps spoofer as system app and get rid of root afterwards
cmg15326 said:
So in other words unrooting and keeping custom system apps is not possible right? because wipe in order to relock the BL will take the away anyway
Just because of messing around more or less haha. wanted to see if i can somehow put a gps spoofer as system app and get rid of root afterwards
Click to expand...
Click to collapse
Hehe, I am trying the same thing on my Huawei without success, tried the options you tried as well, hoping for some solution.
Hi all,
I'm hoping someone here can give me advice on how (or if!) I can recover from a bootloop after a failed Magisk update attempt, without losing the data on my tablet...
My Tab S8 was boot-looping constantly after I tried a Magisk update; trying the plugged-in-volume-up+volume-down trick from this thread gives me the screen with options for Continue, Device Unlock Mode, or Cancel. Before I go any further, I really want to make sure I don't do something that will accidentally wipe all my data!
I'm a long-time Android user and generally just competent enough to follow instructions (like the incredibly helpful howto guide in this forum!) and root my various phones and tablets, but tbh I don't have a full understanding of the various modes and what does / doesn't wipe the data on the device. I have a handful of documents on it that I would really like not to lose, so I don't want to screw this up by choosing options I don't fully understand... Any suggestions will be greatly appreciated!
(Or if someone with actual clue is willing to jump on a web meeting and help me recover it without losing data, I'll gladly compensate you for your time...)
Thank you in advance,
Lisa
Have you tried the Root How-To's instructions to update your firmware without wiping, only using the same version of the firmware your were on already?
Apologies if you already tried that.
Good luck!
roirraW edor ehT said:
Have you tried the Root How-To's instructions to update your firmware without wiping, only using the same version of the firmware your were on already?
Apologies if you already tried that.
Good luck!
Click to expand...
Click to collapse
Thank you! I looked at that, but haven't tried it yet - my concern is that I don't know why the Magisk update failed, so I don't know whether trying the Root How-To's update would run into the same problem. The bootloop is incredibly difficult to interrupt - I had to try the volume up + volume down multiple times before getting the timing right.
If that's the best way to proceed, though, I can certainly give it a shot!
lorenzin said:
Thank you! I looked at that, but haven't tried it yet - my concern is that I don't know why the Magisk update failed, so I don't know whether trying the Root How-To's update would run into the same problem. The bootloop is incredibly difficult to interrupt - I had to try the volume up + volume down multiple times before getting the timing right.
If that's the best way to proceed, though, I can certainly give it a shot!
Click to expand...
Click to collapse
I do believe it's the best option since Magisk needs to be updated in the AP file. You likely need to dirty flash to stock first, if possible (not rooted, without wiping), so that you can have a working system to use the Magisk app to manually patch the AP file, copy the AP file back to the computer as the instructions say, then flash again.
roirraW edor ehT said:
I do believe it's the best option since Magisk needs to be updated in the AP file. You likely need to dirty flash to stock first, if possible (not rooted, without wiping), so that you can have a working system to use the Magisk app to manually patch the AP file, copy the AP file back to the computer as the instructions say, then flash again.
Click to expand...
Click to collapse
THANK YOU for your advice here! I was just able to restore it to the original firmware simply by following the Root How-To's update-without-wiping instructions. Currently debating whether I really want to update it and risk further problems, or just stick with the working firmware... But either way, I was able to recover the documents I need and it's great to have the tablet working again. I really appreciate your help!
Be well,
Lisa
lorenzin said:
THANK YOU for your advice here! I was just able to restore it to the original firmware simply by following the Root How-To's update-without-wiping instructions. Currently debating whether I really want to update it and risk further problems, or just stick with the working firmware... But either way, I was able to recover the documents I need and it's great to have the tablet working again. I really appreciate your help!
Be well,
Lisa
Click to expand...
Click to collapse
You're welcome, glad that helped! I know I was nervous the first time I updated Magisk, but I did it at the same time I updated the firmware. That is, I would've had to update the Magisk app first, so that I could apply that updated Magisk to the new AP file.