Hello Folks,
I need to know a few things about root, can someone explain me what's the difference between normal root and "systemless" root ?
And how do I know what kind of root I am using ?
I'm running SlimX, 5.11 with Xperia XZ SystemUI
I am root but I don't know wich one
Baradoura said:
Hello Folks,
I need to know a few things about root, can someone explain me what's the difference between normal root and "systemless" root ?
And how do I know what kind of root I am using ?
I'm running SlimX, 5.11 with Xperia XZ SystemUI
I am root but I don't know wich one
Click to expand...
Click to collapse
Normal root modifies files on your system partition so that you can have root access. On stock firmware, this breaks dm-verity and causes you to fail SafetyNet checks making AndroidPay and some other apps no longer work. It also prevents you from taking OTA updates because it is no longer recognized as stock firmware. Even if you fully unroot, you will still not be able to take OTA updates because the phone "remembers" that you modified system files and fails dm-verity. The only way to get back to original firmware and take OTA updates is to reflash your entire firmware, wiping all user data in the process.
Systemless root works by intercepting files at the kernel level before the phone fully boots and replaces system files. Once the helper apps are installed you can pass the SafetyNet checks, but you will still not be able to receive OTA updates. The major benefit to systemless root is that you can reflash your stock boot.img (kernel) and your phone will be back to stock firmware, you will bass dm-verity and SafetyNet checks, and you can take OTA updates all without losing any user data. It is very easy to switch between systemless root and stock unrooted by simply flashing the necessary boot.img.
My guess is that since you're on a custom ROM you have normal root. To learn more about systemless root, take a look at Magisk.
Thanks very much bro, yeah I guess I'm on normal root since I can't use android pay and can't download some apps protected by safetynet.
Either way next time I root my phone I'll try systemless method
Baradoura said:
Thanks very much bro, yeah I guess I'm on normal root since I can't use android pay and can't download some apps protected by safetynet.
Either way next time I root my phone I'll try systemless method
Click to expand...
Click to collapse
No, you are on systemless if you use slimx.
Are you sure ? I don't want to try some risky method to know
Baradoura said:
Are you sure ? I don't want to try some risky method to know
Click to expand...
Click to collapse
You can't have custom kernel and use android pay, just forget about it.
Related
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.
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 ?
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) ......
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?
Hey everyone,
I have a Nexus 5 that I haven't updated in a long time that I'd like to get the latest possible OS for. The only modifications I've made which I think might be important are:
Unlocked bootloader
Rooted using SuperSU (v2.8.2 currently)
Installed XPosed (installer v2.6.1, not sure what version of the framework but it should be the latest supported by 4.4.4) with a few modules
Installed App Ops and removed permissions from some apps
Installed StickMount
I don't believe I have any custom recovery installed (I'd used a script to root and install XPosed originally and I don't know if it made any other changes). I'm comfortable using adb if needed but I'm cool with tools like FlashFire too.
My end goal is to have an updated OS with root and XPosed. I assume I'll need Magisk for XPosed, but not sure about root.
How should I go about doing this? I'm cool with losing all of my data (I'll be making backups with Titanium Backup) though knowing ahead of time if that'll be the case would be nice. If it's possible to update without losing data and without affecting anything that'd be nice, but maybe a clean start would be good? The OTA guide on this forum is only for 5, not 6, and most online guides start with 5. I don't want to mess up obviously. xD
Any advice/steps would be appreciated! Thanks!
Aecyl said:
Hey everyone,
Click to expand...
Click to collapse
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
pavik62 said:
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
Click to expand...
Click to collapse
The link you gave doesn't have the latest 6.0.1 build and it also says that it requires a minimum bootloader (HHZ12h) that I don't have (I have HHZ11k). Would it be possible to use the latest build from Google? What do I do about the bootloader? And would using TWRP as the recovery prevent me from passing SafetyNet?
Thanks for replying!
Could I follow this guide with the latest factory image and then install Magisk, root, and XPosed? https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Roxasmaker said:
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Click to expand...
Click to collapse
Would I have to do anything to XPosed or supersu first? I'd like to update to 6.0.1, too. I've seen online that there are OTA updates for it too.
Nope. But you may have to reinstall root, which is very easy once you're updated. Just let the updates do their thing, and you'll be on your merry way! Hope I helped
I think what I'll do is flash stock 4.4.4 keeping user data and then use the OTAs to update to 6. That way I have a clean system install to use Magisk with without losing any user data. (If that doesn't work I'll just flash 6.0.1 for a clean install.)