Database Info

[Q] How do I temporarily "unroot" device?

Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G

Questions belong in Q&A. Moved

artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
i cant c y u would have to unroot, it shouldnt matter as apps dont care if it is rooted or unrooted, correction some apps u have to b rooted to work properly.
do u actually get an error message when trying to install an app
the only way is to restore back to stock, or if u just rooted ur stock firmware, meaning u didnt flash a rom, u can try flashing the system.img file, that might work but i never heard of any1 doing that

Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.

artisticcheese said:
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
Click to expand...
Click to collapse
dont think there is a temporary unroot method, going back to stock was the true method to unrooting, which app were u trying to install.
u can trying going back to stock, installing app, let it do its thing, backup with tibu or some other backup, reroot and then restore backup of app.....maybe wont work as restoring a backup is actually reinstalling the app
edit: try this i havent so try at ur own risk http://www.thespicygadgematics.com/2012/06/how-to-easily-unroot-any-android-phone.html it seems easy enough, i didnt think it was possible but it seems to b

artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.

cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test

cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
Thanks,
How do I root back after that though?

vincom said:
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
Click to expand...
Click to collapse
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.

artisticcheese said:
Thanks,
How do I root back after that though?
Click to expand...
Click to collapse
Flash superuser zip in cwm.

cschmitt said:
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
Click to expand...
Click to collapse
kool. i learn something everyday

There is cool app in Playstore (free) which allows rooting/unrooting with no reboots and other complicated steps
FYI
https://play.google.com/store/apps/...51bGwsMSwxLDMsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0

Voodoo OTA can do a temp unroot as well. The Flixter app will not allow you to stream movis on a rooted phone. I used Voodoo to temp unroot then went back into Flixter and it started to play the movie.

I use an app called Temp root remover
It allows you to temporarly unroot and reroot in a matter of seconds

need help - how to copy TWRP nandroid backup to device?

how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.

Latest TWRP has MTP mode.

but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB

You'll need to give us more information.
Why did it fail? Why did your phone stop booting?

1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop

gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.

how can you copy using twrp while in recovery? are you able to access your PC from recovery?

gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.

ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??

Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty

No. Do a full flash of userdata.img

Please explain
What would I achieve by flashing it?

gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.

Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working

gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.

I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5

gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup

CM Titanium Backup and SuperSU - a strange journey to apocalypse?

Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?

cocororo said:
Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?
Click to expand...
Click to collapse
lmao, your title is nice!
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken. .52 is stable even though its not listed as, i have been using it for some time, and its whats needed for M. you may even find some .6 versions, dont use those, they are systemless, well you can if you want lol. i havent tried them yet, so i dont know what pitfalls may lurk.

Thank you for your help and I am happy to entertain
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
I will try to update SuperSU as soon as possible.
But sadly TWRP now freezes a few moments after I start the device in recovery mode. When the device starts normally, it freezes as well while showing the CM launcher screen. It stays animated but nothing happens. I will try to re-install TWRP via fastboot flash and then install SuperSU .52 and post my experiences here. :fingers-crossed:

Hi again bweN diorD,
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".

cocororo said:
Hi again bweN diorD,
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".
Click to expand...
Click to collapse
hmmm,
i havent used 2.52 on a cm rom, but i have used it on plenty aosp 6.0.* roms without issue.
clean things up so its booting again, then look in developer options and make sure root is turned on. i have seen a few times devs default it to off, but i have never seen a custom rom come not rooted at all.

bweN diorD said:
clean things up so its booting again, then look in developer options and make sure root is turned on.
Click to expand...
Click to collapse
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". That worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused

cocororo said:
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". turn it on apps and adb and see if that helps, thats the preferred setting anywaysThat worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. its not gone in twrp, it sees that you have root and doesnt ask. really its unadvised to use the twrp generated root anyways But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.hmm, maybe thats the problem, maybe you need to install supersu to get things working properly. its on the play store, give it a shot
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused
Click to expand...
Click to collapse
^^^^
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.

bweN diorD said:
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.
Click to expand...
Click to collapse
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?

cocororo said:
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?
Click to expand...
Click to collapse
sorry, i really dont know what happens as far as titanium when you put an app on the sd.
glad you got root working though, although i still dont understand why it wouldnt work the right way.
if you run into any more specific road blocks, ill try and help if i can, but this general problem with the data, i havent a clue the problem or solution, short of the data isnt there completely.

Hi again,
sorry for my late reply! I tried a couple of things but here's the most obvious one:
Apparently the backup files are kind of corrupt. I don't know what went wrong there but TB did not create a full backup. Indeed there is a .tar.gz file for every app but in fact none of these has more than 2 KB. So I strongly assume that this might be the mistake - which also means that all my app's data is lost.
bweN diorD said:
glad you got root working though
Click to expand...
Click to collapse
At least this is a success and I am happy to have TWRP, OpenGapps and Titanium Backup running on a fully rooted device :good:
Thank you for all your time and help! I really appreciate how supportive we "techies" are :highfive:
Have a great day and - a bit late but anyway - a happy new year!

How To Backup *Everything*

Okay, I'm not a techie and I want to know how to backup everything on my phone before I attempt to root my OnePlus One using KingRoot.
At first I naively thought that copying all files and folders from my phone to my laptop would work, but 3 things seem to suggest it's not as easy as that:
I get an error message every time I try copying the files in the ColorNote folder
I saw a mention somehwere that to backup something called EFS you need to run a special app
I'm guessing that my contacts and SMS messages will not be backed up just by copying files and folders from my phone.
So my question is how do I backup *everything* (not just those things I have specifically refered to here) just in case something goes wrong when running KingRoot?
I would prefer not to have to upload my data to the cloud to back it up if at all possible.
Thanks fine people!

Reece Pondwell said:
Okay, I'm not a techie and I want to know how to backup everything on my phone before I attempt to root my OnePlus One using KingRoot.
At first I naively thought that copying all files and folders from my phone to my laptop would work, but 3 things seem to suggest it's not as easy as that:
I get an error message every time I try copying the files in the ColorNote folder
I saw a mention somehwere that to backup something called EFS you need to run a special app
I'm guessing that my contacts and SMS messages will not be backed up just by copying files and folders from my phone.
So my question is how do I backup *everything* (not just those things I have specifically refered to here) just in case something goes wrong when running KingRoot?
I would prefer not to have to upload my data to the cloud to back it up if at all possible.
Thanks fine people!
Click to expand...
Click to collapse
Do you plan to unlock bootloader and flash custom recovery? If not and you just want root,you can safely skip all of this backup part as kingroot/kingoroot won't do any harm to your device.
Also if you don't like kinguser as default granting roots app,you can change it into SuperSu too.
Here's a great guide by @Nishidh
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965

Mr.Ak said:
Do you plan to unlock bootloader and flash custom recovery? If not and you just want root,you can safely skip all of this backup part as kingroot/kingoroot won't do any harm to your device.
Also if you don't like kinguser as default granting roots app,you can change it into SuperSu too.
Here's a great guide by @Nishidh
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
Click to expand...
Click to collapse
Hi and thanks for your reply.
I don't plan to unlock the bootloader. I also wasn't planning on flashing a custom recovery (tbh I don't even know what "flashing" means), however I was thinking of using the KingRoot desktop version and their website states that "the desktop KingRoot version can only be flashed using recovery custom tools". I'm guessing that means that when I run KingRoot it will automatically flash a custom recovery.
BUT if doing that means that my data is wiped then I will stick to the android version even though at the moment I am trying to write an absolute minimum of data to my phone. (My reason for wanting to root is to have one last attempt to recover a load of data that I lost off my phone using a file recovery program that requires root access).
I know that if I run KingRoot just to root it is not supposed to delete any data, but I thought that it was generally thought to be good practice to backup your data before the process anyway just in case something untoward happens (in fact I *think* I read a reccommendation to do that on the official KingRoot website).
Thanks for the video link & tip and, of course, your advice!

Reece Pondwell said:
Hi and thanks for your reply.
I don't plan to unlock the bootloader. I also wasn't planning on flashing a custom recovery (tbh I don't even know what "flashing" means), however I was thinking of using the KingRoot desktop version and their website states that "the desktop KingRoot version can only be flashed using recovery custom tools". I'm guessing that means that when I run KingRoot it will automatically flash a custom recovery.
BUT if doing that means that my data is wiped then I will stick to the android version even though at the moment I am trying to write an absolute minimum of data to my phone. (My reason for wanting to root is to have one last attempt to recover a load of data that I lost off my phone using a file recovery program that requires root access).
I know that if I run KingRoot just to root it is not supposed to delete any data, but I thought that it was generally thought to be good practice to backup your data before the process anyway just in case something untoward happens (in fact I *think* I read a reccommendation to do that on the official KingRoot website).
Thanks for the video link & tip and, of course, your advice!
Click to expand...
Click to collapse
No don't use the desktop version.Use the mobile version and make sure you've fast net connection.Kingroot doesn't install recovery.It just roots,though,ofc not as good as rooting from recovery but still enough for daily tasks.

Mr.Ak said:
No don't use the desktop version.Use the mobile version and make sure you've fast net connection.Kingroot doesn't install recovery.It just roots,though,ofc not as good as rooting from recovery but still enough for daily tasks.
Click to expand...
Click to collapse
Thanks for that. I've tried running KingRoot app, but having some problems as reported here: https://forum.xda-developers.com/oneplus-one/help/kingroot-app-t3573101

Reece Pondwell said:
Thanks for that. I've tried running KingRoot app, but having some problems as reported here: https://forum.xda-developers.com/oneplus-one/help/kingroot-app-t3573101
Click to expand...
Click to collapse
Yes,its totally safe to quit the app.
You can try Kingoroot too.

Mr.Ak said:
Yes,its totally safe to quit the app.
You can try Kingoroot too.
Click to expand...
Click to collapse
Thanks Mr Ak!

Having Trouble Rooting Phone

I have tried rooting using both Magisk and Supersu. I've not had luck passing safety net checks. I've uninstalled Magisk. The specific problem I'm having is that I'm trying to remove all the supersu files. When I get into recover mode using twrp, I can see a /supersu folder. I delete it, or at least it acts like it deletes it but when I reboot into recovery, it's still there. When I use a root explorer app, the folder is nowhere to be found.

rwmappraisal said:
I have tried rooting using both Magisk and Supersu. I've not had luck passing safety net checks. I've uninstalled Magisk. The specific problem I'm having is that I'm trying to remove all the supersu files. When I get into recover mode using twrp, I can see a /supersu folder. I delete it, or at least it acts like it deletes it but when I reboot into recovery, it's still there. When I use a root explorer app, the folder is nowhere to be found.
Click to expand...
Click to collapse
Have you wiped cache after removing the supersu files? Any time you remove apps/files from /system, you have to wipe cache and/or Dalvik/ART cache or it thinks it's still there when it isn't.
Why didn't you just use SuperSU's app settings to unroot and uninstall SuperSU then use Magisk?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

use the unsu script and flash a unrooted boot.img from your rom

Try kingroot
Sent from my SHV-E210S using Tapatalk