[Q] What it takes to unroot? - Nexus 5 Q&A, Help & Troubleshooting

Hey guys,
Last time, I asked you about some technical details of rooting.
Now, I have some little questions about unrooting
Lets say I have rooted my device with CF-Auto-Root (which is great by the way...)
so now I have SuperSu and the su binary in /system/xbin, stock ROM and recovery, and unlocked bootloader.
Now I wish to unroot without loosing any data.
1. If I manually delete su, does it enough to say I have unrooted my phone? Or any other actions are required?
2. What does the unroot option in SuperSu actually do?
3. If I flash stock recovery (even though I already have it), will it unroot my device?
4. How does the survival mode of SuperSu keep me rooted in case of OTA update?
Thanks,
Casteel.

There are existing threads that can help you.
Please read:
Q&A - all you need to know about android
General - how to flash factory images
General - ota help-desk
Sent from my Nexus 5 using Tapatalk

Casteel said:
Hey guys,
Last time, I asked you about some technical details of rooting.
Now, I have some little questions about unrooting
Lets say I have rooted my device with CF-Auto-Root (which is great by the way...)
so now I have SuperSu and the su binary in /system/xbin, stock ROM and recovery, and unlocked bootloader.
Now I wish to unroot without loosing any data.
1. If I manually delete su, does it enough to say I have unrooted my phone? Or any other actions are required?
2. What does the unroot option in SuperSu actually do?
3. If I flash stock recovery (even though I already have it), will it unroot my device?
4. How does the survival mode of SuperSu keep me rooted in case of OTA update?
Thanks,
Casteel.
Click to expand...
Click to collapse
1. If you remove the binary, you are essentially unrooted.
2. The unroot option does the same thing as above.
3. Flashing stock recovery alone, will not remove root permissions.
4. I'm not certain on the technical aspects of Survival mode, but I believe, it runs a script after the OTA to retain root.

El Daddy said:
1. If you remove the binary, you are essentially unrooted.
2. The unroot option does the same thing as above.
3. Flashing stock recovery alone, will not remove root permissions.
4. I'm not certain on the technical aspects of Survival mode, but I believe, it runs a script after the OTA to retain root.
Click to expand...
Click to collapse
Cool. Thanks.
Why flashing stock recovery won't remove root, but OTA update will?
What's the difference between these processes?

Casteel said:
Cool. Thanks.
Why flashing stock recovery won't remove root, but OTA update will?
What's the difference between these processes?
Click to expand...
Click to collapse
The reason why is because recovery is on a separate partition. It does not effect anything on /system/ where the su binary lies.
OTA's patch and update files on /system/ causing SU to be removed in most cases. In some cases having root may cause the OTA to fail, requiring removal of the binary before continuing with the OTA.
Click the link in my signature for the Nexus 5 OTA Help-Desk for more info on OTA's

El Daddy said:
The reason why is because recovery is on a separate partition. It does not effect anything on /system/ where the su binary lies.
OTA's patch and update files on /system/ causing SU to be removed in most cases. In some cases having root may cause the OTA to fail, requiring removal of the binary before continuing with the OTA.
Click the link in my signature for the Nexus 5 OTA Help-Desk for more info on OTA's
Click to expand...
Click to collapse
Great, thank you very much :good:
And thanks for referring to the links, looks useful indeed.

Deleting SuperSU or unrooting will prevent apps from gaining root access, but it won't return your phone to stock. The only way to return to stock is to reflash the factory image.

Related

Still get OTAs while having ROOT?

If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
Yes!
SWTR said:
Yes!
Click to expand...
Click to collapse
Indeed.
KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
The OTA will download but not install. You need stock recovery AND any system file that is updated by the OTA needs to be stock as well otherwise OTA install will fail.
Plenty of threads on XDA speak of this.
If you look at the OTA updater file you will see if uses MD5 (or similar) to check each system file it updates to make sure its as it was originally.
When you root it alters some system files.
Best thing is to install custom recovery and take a backup before rooted. Then root. When you get an OTA just restore backup and flash stock recovery. Then OTA will re-download. Let it install, then flash custom recovery and re-root.
Thanks, well I'll just stay unrooted and make the best out of it, the Moto G is just as amazing as Motorola developed it to be.
No stock recovery it's no need. I updated last ota with Philz recovery without problems.
denzel09 said:
No stock recovery it's no need. I updated last ota with Philz recovery without problems.
Click to expand...
Click to collapse
Do you mean you downloaded OTA and flashed manually via recovery. You can do that I agree, but what you can't do is let OTA install naturally the way Motorola intended.
No. I had Philz recovery. System stock partition. Downloaded ota normally, reboot like ota update ask, phone reboots in philz recovery and this last flash ota automatically without any problem. There is not need to reflash stock recovery or flash ota update manually with custom rec, only need a non root stock system partition. I dont know if stock cwm or other rec like twrp work in same way but i doubt, always used only philz recovery.
You do not need stock recovery, I don't know who made this stupid rumour up. I use twrp and it flashes fine.
Sent from my Google Nexus G -

OTA zip pack? Keep root?

I just had a carrier update(Telus canada) pushed to my phone and i'd like to update however I do not want to loose root/etc.
Does anyone know of a patched version of this OTA zip or how to patch it?
Or where can i find the OTA in my phnoe to try and use flashfire?
Version : G930W8VLU2API1
PDA : G930W8OYA2API1
CSC : G930W8VLU2API1
Phone : G930W8VLU2API1
Size : 178.69MB
kylecore said:
Or where can i find the OTA in my phnoe to try and use flashfire?
Click to expand...
Click to collapse
Should be in /cache or any other cache dir, you can reroot anyway with cfroot.
Never found a way to flash the OTA zip neither in Flashfire nor in TWRP. The only way to update a rooted phone is either to download the whole thing with Samfirm or just unroot and then flash the update as usual. Maybe someday I will know better
Wasn't the vision of Systemless root that you would be able to apply OTA updates despite having root as it didn't modify the system partition? I'm not sure though if either of the root methods for the S7 are systemless roots.
I can't find the ota in cache or really anywhere I look with flashfire even though I've downloaded it. And the ota won't flash regardless because of two. I just want the notification to go away lol
Sea-Wolf said:
Wasn't the vision of Systemless root that you would be able to apply OTA updates despite having root as it didn't modify the system partition? I'm not sure though if either of the root methods for the S7 are systemless roots.
Click to expand...
Click to collapse
Yeah, you can receive OTA with systemless root as long as you didn't debloat your phone, but then there is no reason for me to root. Or did I mistake anything? Would be awesome if you could use systemless root and systemless xposed with a debloated device and still receive OTA via Flashfire or even the stock updater.
Is there any link to an OTA .zip ?

Get OTA with root and xposed?

Hi guys,
It it possible to get OTA with root and xposed? Should i uninstall xposed and unroot device?(how to unroot? uncheck Enable superuser?)
Nope
Flash stock
farid993 said:
Hi guys,
It it possible to get OTA with root and xposed? Should i uninstall xposed and unroot device?(how to unroot? uncheck Enable superuser?)
Click to expand...
Click to collapse
Hi
As long as you have the latest Systemless root and SU by Chainfire (being around for months) you did not modified the system files of your phone and unroot (from SuperSU) yes is possible
Some people said is possible also no unroot necessary if you just fake system status
MAX 404 said:
Hi
As long as you have the latest Systemless root and SU by Chainfire (being around for months) you did not modified the system files of your phone and unroot (from SuperSU) yes is possible
Some people said is possible also no unroot necessary if you just fake system status
Click to expand...
Click to collapse
Thank you. So just uninstall xposed and unroot(or not) and i`m good.
How about TWRP recovery? To install Xposed i should use TWRP to flash it(or could i use FlashFire only?)
Also should i defrost all system apps that i froze them?
farid993 said:
Thank you. So just uninstall xposed and unroot(or not) and i`m good.
How about TWRP recovery? To install Xposed i should use TWRP to flash it(or could i use FlashFire only?)
Also should i defrost all system apps that i froze them?
Click to expand...
Click to collapse
Hi
Option 1 Systemless root and systemless SuperSu ( Chainfire) no xposed (rovo89) , no system modification, no R/W systems, no TWRP , unroot from SuperSu , OTA possible
Option 1.1 use Flashfire guide here
Option 2 ( have not tested it) fake system status
In my experience trying to return Custom status to Official after rooting, even after removing root, is near impossible
That said, with this new systemless root, I haven't tried, but if you have altered any system files, which is generally what people use root for (Adblocking = Hosts file mod etc) then it won't return to Official unless you flash stock over the top again
Not seen this new status spoofer until now, be interested to see if that works
Thanks guys
So i guess with xposed it is impossible to get OTA, because to fake system status we need xposed but to get OTA we need to uninstall xposed.
Also *Detection* is right. We root our device to alter system.
So at the end we need download whole ~2gb firmware(flash, root, xposed, all other changing system thing again) for 20-30mb monthly security patch
farid993 said:
Thanks guys
So i guess with xposed it is impossible to get OTA, because to fake system status we need xposed but to get OTA we need to uninstall xposed.
Also *Detection* is right. We root our device to alter system.
So at the end we need download whole ~2gb firmware(flash, root, xposed, all other changing system thing again) for 20-30mb monthly security patch
Click to expand...
Click to collapse
Basically yep, unless you're not bothered about the security update and just wait for feature/performance updates
With my S5 I used to update every update, download the new ROM, flash with ODIN, TWRP > Root > Mod
Doesn't take too long tbh
*Detection* said:
In my experience trying to return Custom status to Official after rooting, even after removing root, is near impossible
That said, with this new systemless root, I haven't tried, but if you have altered any system files, which is generally what people use root for (Adblocking = Hosts file mod etc) then it won't return to Official unless you flash stock over the top again
Not seen this new status spoofer until now, be interested to see if that works
Click to expand...
Click to collapse
farid993 said:
Thanks guys
So i guess with xposed it is impossible to get OTA, because to fake system status we need xposed but to get OTA we need to uninstall xposed.
Also *Detection* is right. We root our device to alter system.
So at the end we need download whole ~2gb firmware(flash, root, xposed, all other changing system thing again) for 20-30mb monthly security patch
Click to expand...
Click to collapse
*Detection* said:
Basically yep, unless you're not bothered about the security update and just wait for feature/performance updates
With my S5 I used to update every update, download the new ROM, flash with ODIN, TWRP > Root > Mod
Doesn't take too long tbh
Click to expand...
Click to collapse
+ 1 guys
After rooting is very hard to keep system "clean" enough ....if you meet the conditions is possible.....but to my by far *Detection* suggestion is easier...
status spoofer i have not tried ( I have a custom rom) ......

On H83010i, bootloader unlocked not rooted. Want H83020f rooted

I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root
Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.

Samsung Galaxy S8 unroot

Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?
minalm said:
Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?
Click to expand...
Click to collapse
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
you have given a very detailed explanation and i fell like a simple thank you would be enough. you helped me out now and i feel somewhat obliged to thank you this way.
cheers
Is the things still the same... namely unrooting will not return KNOX and can not use Samsung warranty?
hi
i have a rotted phone s8..i flashed a stock rom, but phone is still rooted. Some apps like us google pay,mcdonalds tell me that phone is rooted..What i can do?

Categories

Resources