My goal is to COMPLETELY get rid of any root files / SuperSu files that are located on my device without having to reformat. Couple months ago i managed to install SuperSu and gained root and I did my own cleanup of bloatware apps and whatnot. Since then I have deleted SuperSu by going into the settings of SuperSu and clicking on the "Clean Root" option but without doing the original boot files option. Doing so, the phone reboots, cleans up , deletes SuperSU and i no longer have root. This is great and all but just one problem reminds.....
I can no longer play Pokemon GO because of the newest update that came out yesterday since it checks for rooted devices. Is there a way to completely remove all the files that are associated with the root process / SuperSU so that I can play this game. I have tried to use the app "SafetyNet Helper" to check for Google's SafetyNet CTS tests and it fails after i tried uninstalling SuperSU. I have heard of the Magisk app but it looks like you need a unlocked bootloader to install it.
Is there a way to get my phone back to the original state without reformatting my phone through Odin. At the end of the day, yes, i would rather have a rooted device than to play Pokemon GO but say what you will but this game has gotten me out, walking around my town, being social and actually making friendships.
Thanks for any help in advance,
Just go here. http://forum.xda-developers.com/tmo...ow-to-unroot-to-stock-o-loosing-data-t3445573
Related
After finally getting my HTC Status (ChaCha), rooted (the first phone I got rooted) with XTC Clip (this is a device to unlock the bootloader and carrier lock on HTC phones), ClockworkMod, and SuperUser. After updating it that night, the apps I had granted root permissions stopped being able to use root functions (like ES Explorer's root read/write function) or not all, except for AdFree, which continued to keep most ads at bay. Now SuperUser no longer shows any apps listed, and attempts to update the binaries but gets stuck at "Gaining root access" and crashes eventually. The Update Fixer program gets stuck at 'Waiting for root access', not unlike Titanium Backup Pro, which is stuck at 'awaiting root access'. I also tried Super Super User as well, and it was stuck on "The SU binary needs to be updated. Continue? Installing, please wait ..." After more than an hour of waiting, I quit. Same for SuperUser Update Fixer. I also uninstalled the SuperUser update and found that didn't fix anything. I reinstalled Titanium Backup Pro too, same results. I have read that some folks have had success installing Busybox (separate from Tiny Busybox that is part of SuperUser), but I don't see how I would install it if I can't get root permissions! After reading the comments posted on Google Play about SuperUser following the update, I can see plenty of people have had various sorts of problems with SuperUser now. Any thoughts on how to remedy this, besides badgering the author of the software? (I did post feedback to Google Play, nothing hostile or anything, trying to be as precise as possible.)
Hello, i have a gt-n8010 tablet and just updated it to 4.4.2, from 4.1.2 i had root, worked any method cwm or autoroot, but in this version cant make root work well, i use SuperSU as root app, i do this: (debugging is on)
1 install SuperSU through autoroot (using odin) it installs and everthing goes well, reboots and it says something about disabling knox i just hit yes
2 install pro and configure the SuperSU app,*
but at some point after using the app (granting root access), when i access the SuperSU interface it tells me that SuperSU has to update the "su" binary it asks me "normal" or "CWM", i hit normal as always because i didnt install CWM recovery, but this time fails installation and closes the app unlike version 4.1.2 wich didnt have any problem, and doesnt let me to access the app interface because it keeps telling me about updating binary, but when an app asks for root access it still asks me to grant it, and any app previously root granted stays granted.
the apps i use with root are: root explorer, root uninstaller, game killer, triangle away
wich seems strange is that root explorer, root uninstaller and triangle away once i grant root access they work fine, i can access root folders and modify them, uninstall system apps and even reset flash count, but game guardian, game killer and gamecih dont work as they should, they open well but cant use them to read memory and change any ingame value.
gamecih just never shows that has root access even if i granted it and doesnt respond to hotkey
game guardian opens and appears to work but when searching for a value shows 0 results everytime, every game
and game killer opens, but the message saying "Rooted" never shows and after like 20 seconds it closes and opens again in an infinite loop without letting me use it, it also doesnt respond to hotkey.
i have also tried the CWM recovery method and install SuperSU through recovery, it install without problem and just as previous method after some time of use it tells me that SuperSU has to update binary and fails installation and still cant use apps like game killer, i go back to CWM recovery and reinstall it, it reinstalls but this second time, it tells me something about disable recovery flash i just hit yes and after that it warns me about root access loss and ask me to fix it, wich i say yes, then i hit reboot now and everything goes well, but same problem, updating binary problem and no game killer type apps.
i have tried uninstalling every knox app, but still the same. i like to hack games rooting for anything else doesnt matter, any idea what can be causing this? and how to solve it?
voltrex32 said:
Hello, i have a gt-n8010 tablet and just updated it to 4.4.2, from 4.1.2 i had root, worked any method cwm or autoroot, but in this version cant make root work well, i use SuperSU as root app, i do this: (debugging is on)
1 install SuperSU through autoroot (using odin) it installs and everthing goes well, reboots and it says something about disabling knox i just hit yes
2 install pro and configure the SuperSU app,*
but at some point after using the app (granting root access), when i access the SuperSU interface it tells me that SuperSU has to update the "su" binary it asks me "normal" or "CWM", i hit normal as always because i didnt install CWM recovery, but this time fails installation and closes the app unlike version 4.1.2 wich didnt have any problem, and doesnt let me to access the app interface because it keeps telling me about updating binary, but when an app asks for root access it still asks me to grant it, and any app previously root granted stays granted.
the apps i use with root are: root explorer, root uninstaller, game killer, triangle away
wich seems strange is that root explorer, root uninstaller and triangle away once i grant root access they work fine, i can access root folders and modify them, uninstall system apps and even reset flash count, but game guardian, game killer and gamecih dont work as they should, they open well but cant use them to read memory and change any ingame value.
gamecih just never shows that has root access even if i granted it and doesnt respond to hotkey
game guardian opens and appears to work but when searching for a value shows 0 results everytime, every game
and game killer opens, but the message saying "Rooted" never shows and after like 20 seconds it closes and opens again in an infinite loop without letting me use it, it also doesnt respond to hotkey.
i have also tried the CWM recovery method and install SuperSU through recovery, it install without problem and just as previous method after some time of use it tells me that SuperSU has to update binary and fails installation and still cant use apps like game killer, i go back to CWM recovery and reinstall it, it reinstalls but this second time, it tells me something about disable recovery flash i just hit yes and after that it warns me about root access loss and ask me to fix it, wich i say yes, then i hit reboot now and everything goes well, but same problem, updating binary problem and no game killer type apps.
i have tried uninstalling every knox app, but still the same. i like to hack games rooting for anything else doesnt matter, any idea what can be causing this? and how to solve it?
Click to expand...
Click to collapse
Try to download/update via the Google play store, it might do the trick.
Lange-199 said:
Try to download/update via the Google play store, it might do the trick.
Click to expand...
Click to collapse
I already have, and didnt work
voltrex32 said:
I already have, and didnt work
Click to expand...
Click to collapse
Try to uninstall supersu (root uninstaller) and install via Google play, the same su update question will then be asked and click on normal just like you did before. The problem might be due to a old version of supersu from the flash.
Lange-199 said:
Try to uninstall supersu (root uninstaller) and install via Google play, the same su update question will then be asked and click on normal just like you did before. The problem might be due to a old version of supersu from the flash.
Click to expand...
Click to collapse
I have already tried reinstall, first shows to work fine, when message that su binary has to update comes out and it installs correctlly, it just needs sometime after or a reboot for the app to ask me again about su binary update and fail installation, during the time it "installed correctlly" i still have the same problem losing root access with gamekiller type apps.
i have also tried full unroot from inside the app, then reflash SuperSU, and still have the problem even that is 2.02 version.
But have to say that i have root access already, i tried another su app, i installed CWM recovery then installed rom manager from Google play, then inside rom manager downloaded and installed Superuser and it worked and still does, all my apps that need root access work, dont know how or why, but they work. For obvious reasons i had to install SuperSU first then grant root access to rom manager then install the other su app and bingo!!, but for reasons i dont know, the SuperSU app was no where to be found, like if it was uninstalled, but thanks anyway
It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.
Newest update has blocked access to rooted phones. Even after hiding/ removing root access privileges (I've tried both hiding and un-rooting) I cannot log in, so I'm left only to assume that the version of the OS itself is blocked.
Simple question: Does anyone know of a way around this? I see hundreds of posts about magisk, but I cannot do that while using slimkat ( magisk requires android 5.0+)
I've really gotten into this game over the last coiuple months, but I refuse to revert to some vanilla stock version of android to play. If anyone could provide any info I'd greatly appreciate it.
I'd do what I always do when I need/want to run something of that nature: I install a "sacrificial ROM" alongside my Slim using MultiRom and boot into it when needed.
So...an app demands a non-rooted ROM? No problem: Here's a plain vanilla AOS sandbox for you to play in.
I'm playing to PoGo with any issues with SlimRom 6, I just deleted a file called su.bin from /system/bin and /system/xbin.
This erases root of the rom, and make it playable. Use SafetyNetHelper on Google Play Store to check if you pass the test (PoGo uses this test).
You can delete them (you have to delete both) on the file manager of TWRP.
The way i got mine to work(i can also use the Fake GPS hack with my POgo as well! ) is 1st i downloaded an already rooted(with SuperSU) rom for my phone off of xda and i installed the fake gps app through ucky patcher to make it a system app. i then downloaded a stock rom for my phone from here at xda, and i flashed it using Odin, this replaced everything to make it stock again but kept my system files(the fake gps app) so then all i had to do was redownload PoGo and login as normal and voila! their security check diverted and still able to fake gps it lol
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
bitblocksplicer said:
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
Click to expand...
Click to collapse
Which ROM are you actually running?