Related
I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?
DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats
WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..
HELP!!! i posted earlier about my rooting problem, still same thing.. when root is accessed it say you have been granted superuser permission for an interactive shell but that process doesnt work.. in my PA the superuser section it doesnt have the superus on it, it says currently no superuser app policies.. me and my friend virtually have the same software on our nexus 4, except only difference is that in his SU on PA has one policy and thats allowing the SU app to work or idk but ill show you the difference.. im thinking i might have to reflash my rom ?
PA already has SuperUser by Koush so I would recommend uninstalling SuperSU or you are going to have root issues.
What is meant by SuperUser app policies is root applications so it is saying that there is no root applications which has requested yet so there is nothing wrong with root.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
PA already has SuperUser by Koush so I would recommend uninstalling SuperSU or you are going to have root issues.
What is meant by SuperUser app policies is root applications so it is saying that there is no root applications which has requested yet so there is nothing wrong with root.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Okk well i went through the SU app to completely unistall the root but then i had no root.. and the PA root wasnt popping up, so i reflashed the one i had previous, do you think ill have to reflash PA if i uninstall again and still doesnt work? and before i reboot my phone i got to recovery and as i reboot it prompts to intsall root before i reboot so i did it and there was an error when i rebooted
Yep just reflash. Turn off phone, go into the boot loader and go to recovery through there.
Sent from my Nexus 4 using xda app-developers app
buu1152 said:
Okk well i went through the SU app to completely unistall the root but then i had no root.. and the PA root wasnt popping up, so i reflashed the one i had previous, do you think ill have to reflash PA if i uninstall again and still doesnt work? and before i reboot my phone i got to recovery and as i reboot it prompts to intsall root before i reboot so i did it and there was an error when i rebooted
Click to expand...
Click to collapse
Yeah just reflash, some people have issues with root.
Sent from my Nexus 4 using xda app-developers app
yea i did and it works fine now thanks
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
BallaratBloke81 said:
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
Click to expand...
Click to collapse
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
thahim said:
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
Click to expand...
Click to collapse
I have given it privileges. But when I open supersu says there is something wrong with su binary.
BallaratBloke81 said:
I have given it privileges. But when I open supersu says there is something wrong with su binary.
Click to expand...
Click to collapse
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
ultramag69 said:
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
Click to expand...
Click to collapse
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
BallaratBloke81 said:
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
Click to expand...
Click to collapse
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
Yes hello, can someone please upload the note 3 4.3 touchwiz apk, i accidentally deleted mine, so please.
ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
I have already reflashed stock back to my phone, re rooted and the problem still exsists
Currently I'm on stock again (downloaded from sammobile)
Every time I open superSU, it tells me there is a problem with the SU BINARY (when I was rooted. I'm not trying to use super SU unrooted lol)
Just rooted again and its still the same...
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
antique_sonic said:
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
Click to expand...
Click to collapse
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
BallaratBloke81 said:
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
Click to expand...
Click to collapse
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Rosli59564 said:
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Click to expand...
Click to collapse
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
gee2012 said:
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
Click to expand...
Click to collapse
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
BallaratBloke81 said:
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
Click to expand...
Click to collapse
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
I can't even get into the app to unroot
BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
ES explorer can't get root access either.
Should I flash superSU.zip straight over the top using recovery? Or is that not a good idea?
Rosli59564 said:
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
Click to expand...
Click to collapse
I have unrooted (flashing stock rom using recovery) and rerooted (using CF auto root... Or whatever it's called) many times.
Hello ^^
I am hoping that some of you guys can help me out of a little issue that i am having, i will try and explain what has happened up until now as best i can:
As many people know, the latest update to Pokemon GO, knocks out rooted users. I did not know this and updated last night, however, dispite running a custom ROM (PureNexus) and being rooted, my game loaded up like normal and let me play. It wasn't until i checked that my SuperSU that i found that root wasn't actually working at that time, so i re-flashed the latest Super SU and all was good, but, obviously, this knocked out Pokemon GO.
I read up on the trick of using Magisk to be able to turn off root and when was needed as to get the game to work, so i went about trying to get it working. I unrooted via Super SU and then rebooted and flashed the Magisk installer and PHH Superuser (as i heard this was best for compatability). After the phone rebooted i, installed the Magisk launcher and the PHH SU program from the Play Store, but when i opened any app that reuqited root, it was still telling me i wasn't rooted anymore, and thus, when i opened PGO, it worked.
I am kinda lost from here, i want to get my phone rooted again, and i want to get Magisk working so i can still enjoy PGO and some of my occasionally used apps that require root, so my questions are as follows:
1. Can you re-flash an SU over an old one to get root back, or do i need to fully un-root and root again?
2. If i was to re-flash SuperSU (with Magisk support), would this get me rooted again and allow me to flash Magisk as normal?
I am a little lost here, any and all help would be appreciated.
Thanks to all in advance.
Have you tried Root Cloak xposed module?
Sent from my Nexus 6P using Tapatalk
jxcorex28 said:
Have you tried Root Cloak xposed module?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
i have, it doesnt work as PGO uses safetynet, like Andriod Pay
Ohh snap, well that's all I had...I don't play PoGo
Sent from my Nexus 6P using Tapatalk
For magisk to work, you have to use it to root and unroot. From what I understand, it temporarily removes root system wide when you do this. Basically it's a more convenient way to root and unroot.
Android Police has an article on it right now. The instructions for installation and usage are correct.
The problem is probably related to a failure to make sure all traces of previous SuperSU installations are gone.
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk
For magisk to work it's best to fully unroot, maybe try unsu.zip,
Then have a 100% stock system and boot (kernel)
And before flashing magisk and phh, try the SafetyNet checker app in the playstore. (PoGO uses SafetyNet to check for root, same as Android Pay)
If you pass then go ahead and flash magisk, phh, and then phh app followed by magisk manager
In the magisk thread are all the instructions to follow
Sent from my Nexus 6P
I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Pics or it didn't happen
And last, but certainly not least...
So I can root without unlocking the bootloader using sunshine?
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^
Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.
Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?