I've seen posts instructing how to root via SuperSu and Magisk; I know those methods have to be done a certain way because of the partition system. But I have not seen any posts about Kingroot. Would it work the successfully? I imagine it going like this:
1) root with Kingroot
2) boot to TWRP via ADB
3) flash TWRP
4) flash SuperSU if desired
Or
4) if desired, flash a kernel, flash Magisk, flash TWRP again
5) boot to system, uninstall Kingroot
Does that sound right? Would Kingroot even work to begin with?
GroovinChip said:
I've seen posts instructing how to root via SuperSu and Magisk; I know those methods have to be done a certain way because of the partition system. But I have not seen any posts about Kingroot. Would it work the successfully? I imagine it going like this:
1) root with Kingroot
2) boot to TWRP via ADB
3) flash TWRP
4) flash SuperSU if desired
Or
4) if desired, flash a kernel, flash Magisk, flash TWRP again
5) boot to system, uninstall Kingroot
Does that sound right? Would Kingroot even work to begin with?
Click to expand...
Click to collapse
Why use kingroot? Remove the first step and you basically have hot to flash su..
pcriz said:
Why use kingroot? Remove the first step and you basically have hot to flash su..
Click to expand...
Click to collapse
True, but if you happen to want to root while away from a computer it could be useful.
In any case, it was simply a curiosity about whether it would even work at all. I doubt I'd ever use Kingroot for my Pixel.
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
True, but if you happen to want to root while away from a computer it could be useful.
In any case, it was simply a curiosity about whether it would even work at all. I doubt I'd ever use Kingroot for my Pixel.
Click to expand...
Click to collapse
Oh okay. I was just curious. I haven't tried kingroot but since rooting requires patching the boot.img and I don't know if you can do that while booted into the OS I'd say no. I am only assuming how kingroot works but again whatever the solution it needs to be able to make changes to the boot.img without already having root privs.
The closest solution I would see is having twrp already loaded.
pcriz said:
Oh okay. I was just curious. I haven't tried kingroot but since rooting requires patching the boot.img and I don't know if you can do that while booted into the OS I'd say no. I am only assuming how kingroot works but again whatever the solution it needs to be able to make changes to the boot.img without already having root privs.
The closest solution I would see is having twrp already loaded.
Click to expand...
Click to collapse
This makes sense. Thanks
Sent from my Google Pixel XL using XDA Labs
Even if it did work it wouldn't work the way you are describing. King Root basically acts like malware and refuses to give root privileges to any app that interferes with its functioning. Adaway won't work with King Root because adware is part of the King Root program. You also wouldn't be able to install SU while King Root is on your phone. King Root will actively prevent you from installing any other root program. People used to be able to do what you describe but King Root was updated to prevent you from installing SU.
Related
is it possible to root this phone without using adb?
nighthawk626 said:
is it possible to root this phone without using adb?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=805010
You can try this, I personally did it with adb so I honestly have no idea how well it works. Hell I'm I can't even say it works for sure.
Well good luck
xaodxkevin said:
http://forum.xda-developers.com/showthread.php?t=805010
You can try this, I personally did it with adb so I honestly have no idea how well it works. Hell I'm I can't even say it works for sure.
Well good luck
Click to expand...
Click to collapse
You obviously did not read through that thread, it was shown to not work. That root method doesn't involve the flashing of the engineering bootloader, which is required to be able to flash self signed update packages in recovery, such as clockwork recovery. People ran into errors because they couldn't flash clockwork. They also couldn't flash the engineering build because they were not rooted.
So, in short, to the OP, no, you cannot root without ADB. You CAN download an app that will give you temporary root, but that will only allow you to use applications that require root, it won't allow you to actually flash a custom ROM. For that you need to follow nbetcher's root method, which is in the android dev section, it's a fairly obvious thread in capital letters near the top
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
sblantipodi said:
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
Click to expand...
Click to collapse
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
mwalt2 said:
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
Click to expand...
Click to collapse
is there a way to undo this process once done?
sblantipodi said:
is there a way to undo this process once done?
Click to expand...
Click to collapse
Naturally, backtrack your steps.
beekay201 said:
Naturally, backtrack your steps.
Click to expand...
Click to collapse
Can I safely remove all the files copied from the zip ?
sblantipodi said:
Can I safely remove all the files copied from the zip ?
Click to expand...
Click to collapse
Yes.. Restoring whatever in the process..if you modified anything that was there already.
Galaxy Nexus 4.3 NO ROOT w/ SuperSU_1.51.zip
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
innerspace said:
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
Click to expand...
Click to collapse
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
download the most current supersu.zip and flash it in recovery.
if you're using a toolkit (i bet you are) STOP IT.
Zepius said:
download the most current supersu.zip and flash it in recovery.
about 2 minutes prior to your reply, I updated the "Toolkit" along with all the other items (supersu, img, etc..)
And after that, my device is rooted again.
Although, the main reason I started all of this was to update my device's build further, but it seems the OTA update is now gone... I'll have to wait for it appear again and see how it goes...
Zepius said:
I'll keep that in mind...
if you're using a toolkit (i bet you are) STOP IT.
Click to expand...
Click to collapse
Thanks for the reply!
Much appreciated!
Click to expand...
Click to collapse
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
I did, though I'm fuzzy on how exactly, and no, no toolkits here. IIRC I ended up wiping, updating recovery, and then manually flashing, but I had to do it multiple times to get root to stick. Sorry I don't have any better info to provide, glad to hear a) I wasn't the only one who experienced this problem, and b) you got your root back.
I have searched the forums for my device, and other people's posts trying to find a way to root my device. Towelroot did not work for me. I read that i could install Philz touch recovery and root with that, but i cannot find the version of that for my phone. If somebody could point me in the direction of a method to root my phone, i would very much appreciate it
The Cheese Deity said:
I have searched the forums for my device, and other people's posts trying to find a way to root my device. Towelroot did not work for me. I read that i could install Philz touch recovery and root with that, but i cannot find the version of that for my phone. If somebody could point me in the direction of a method to root my phone, i would very much appreciate it
Click to expand...
Click to collapse
You could download GooManager (or Flashify) off the Play Store, install custom recovery (TWRP) and root. It will install the one for your phone automatically.
You need root to use GooManager.
Im curious, what happened with Towelroot? I cant see any reason it wouldnt work. Can you tell me the steps you used?
DocHoliday77 said:
You need root to use GooManager.
Im curious, what happened with Towelroot? I cant see any reason it wouldnt work. Can you tell me the steps you used?
Click to expand...
Click to collapse
I downloaded the towelroot apk, installed it and clicked "make it rain" and the app said i should have root. I downloaded root checker and it says i do not have root access.
After running Towelroot You have to install SuperSU from the Play Store, then open the app and let it update the binary and disable Knox.
If SuperSU hangs, reboot and it'll work on the second try.
DocHoliday77 said:
After running Towelroot You have to install SuperSU from the Play Store, then open the app and let it update the binary and disable Knox.
If SuperSU hangs, reboot and it'll work on the second try.
Click to expand...
Click to collapse
I had tried CF-Auto-Root before towelroot, and it seems to have either partially installed SuperSU, or SuperSU just doesn't like my phone. It shows up in my app list as "eu.chainfire.supersu.MainActi" and force closes when i try to open it. I cannot uninstall it. (i should have mentioned this in my OP maybe)
Oh ok. That makes more sense to me for why Towelroot didn't work then. Probably the easiest fix would be to reflash the firmware with Odin, then try Towelroot first. Since you dont have root now, its going to make fixing the problem any other way near impossible.......actually, now that I said that, you could flash twrp recovery, then use its file manager to manually delete any traces of the failed root.
Still, I think the firmware flash is an easier and safer option. But its up to you how you want to proceed.
DocHoliday77 said:
Oh ok. That makes more sense to me for why Towelroot didn't work then. Probably the easiest fix would be to reflash the firmware with Odin, then try Towelroot first. Since you dont have root now, its going to make fixing the problem any other way near impossible.......actually, now that I said that, you could flash twrp recovery, then use its file manager to manually delete any traces of the failed root.
Still, I think the firmware flash is an easier and safer option. But its up to you how you want to proceed.
Click to expand...
Click to collapse
I successfully flashed TWRP, exactly what files should i delete?
Check the cf autoroot thread to be sure, but probably the su binary, install-recovery.sh, daemonsu, etc.
DocHoliday77 said:
Check the cf autoroot thread to be sure, but probably the su binary, install-recovery.sh, daemonsu, etc.
Click to expand...
Click to collapse
The recovery file manager does not see a lot of the files on my phone. It does see the SuperSU folder, but even if i delete or rename it, it just fixes itself upon reboot. I'm thinking of flashing the 4.4.2 firmware through odin, is a factory reset absolutely necessary to do that?
I flashed the firmware, ran towelroot, installed SuperSU, installed the binary, disabled Knox, and i am now running a rooted device!
Thank you very much DocHoliday77 for all of your help, i greatly appreciate it.
Which firmware did you reflash? Stock 4.4.2??
I cannot find towelroot on the app store. Are there any suggestions on what to do without towelroot
What are the correct steps to get android pay working with systemless root. I flashed in the following order: Pure nexus(supports pay), banks GAPPS, unSU, Systemless 2.66. Now, I heard i need to delete /su/xbin_bind but i can't find that.
I'm using 2.61 and androidpay has always worked fine. Never deleted any files after flashing that. I'd love to hear from anyone on 2.66 to know if it's working.
Edit: upgraded to 2.66 myself and it works fine so far. Will test androidpay soon, but I can't imagine why it wouldn't work...
smac7 said:
What are the correct steps to get android pay working with systemless root. I flashed in the following order: Pure nexus(supports pay), banks GAPPS, unSU, Systemless 2.66. Now, I heard i need to delete /su/xbin_bind but i can't find that.
Click to expand...
Click to collapse
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
dmudd said:
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I looked in /system and it's not there. I did however folder called ADDON.D that has Update_SuperSU within it. If i understand correctly, this would set-off the trigger to see system as modified. Is it possible the unSU zip i used (to try to unroot pure nexus) didn't work correctly?
So, apparently i was supposed to go to terminal and enter
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Click to expand...
Click to collapse
before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
smac7 said:
So, apparently i was supposed to go to terminal and enter before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
Click to expand...
Click to collapse
If you can add a card you pass the safetynet. You should be ready to use it. Just remember if you do anything else that you can still cause your phone to fail the safetynet and prevent payment even after your cards are added.
I've posted in a Nexus 6P thread, might be helpful though, but I had to disable SuperSU (not Full unroot) in order to get AndroidPay/CapOneWallet/Safetynet to work. And that's after editing build.prop, removing /su/xbin_bind, and installing EX Kernel, using Stock 6.0.1 and SuperSU 2.66 with systemless root.
The folder is located under /su not /system
dmudd said:
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
bdivs11 said:
The folder is located under /su not /system
Click to expand...
Click to collapse
You're right. I thought it was under /system but it is under /su
Sent from my Nexus 5X using Tapatalk
smac7 said:
So, apparently i was supposed to go to terminal and enter before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
Click to expand...
Click to collapse
if you didn't perform these commands, then youll have to do full unroot and do it again putting them in BEFORE flashing 2.66
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
2x4 said:
if you didn't perform these commands, then youll have to do full unroot and do it again putting them in BEFORE flashing 2.66
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Click to expand...
Click to collapse
so I flashed 2.66 without doing these commands, thus breaking my android pay. how do i "fully unroot"? flash the un-SU.zip? I thought that was only for the system-based root methods, but perhaps I am wrong. I assume once I am unrooted I can just download any terminal emulator (do you recommend one?), enter the commands, then re-flash 2.66. Thanks for your help!
BTW I don't understand why 2.66 added these steps. 2.61 didn't require any terminal emulator commands and android pay worked fine! Perhaps the easiest solution would just be to flash 2.61 over 2.66?
Android Pay is not working on my 5x. I used the MSkip Toolkit's systemless root option, as well as used that Toolkit to unlock, de-encrypt, ect. That was done with I think a temp flash of TWRP so I keep stock recovery?
The only other thing I did to my phone was the build prop edit to enable tethering on Verizon which in the thread people said doesn't break their Android Pay.
Android Pay says cannot verify yadda yadda. I disabled SU in the app, rebooted and AP still doesn't work. Now when I try to re/enable SU fails installing/fails updating binary.
Anyone have any advice? Does some file need to be deleted or a fresh install?
greves1 said:
so I flashed 2.66 without doing these commands, thus breaking my android pay. how do i "fully unroot"? flash the un-SU.zip? I thought that was only for the system-based root methods, but perhaps I am wrong. I assume once I am unrooted I can just download any terminal emulator (do you recommend one?), enter the commands, then re-flash 2.66. Thanks for your help!
BTW I don't understand why 2.66 added these steps. 2.61 didn't require any terminal emulator commands and android pay worked fine! Perhaps the easiest solution would just be to flash 2.61 over 2.66?
Click to expand...
Click to collapse
Chainfire (SuperSU dev) is not developing systemless root to be compatible with Android Pay. That was never his aim. Anything he adds is for the purpose of not using /system for root. If you would like to read on changes to SuperSU, I suggest reading the brief changelogs or following his SuperSU beta thread to keep up to date on changes in SuperSu (systemless or otherwise).
Btw, you can flash whichever version of SuperSu you desire. If it is easier to get Android Pay working for you, cool.
I just use 2.61 and it just works with Android pay. No terminal commands or anything
stu5797 said:
I just use 2.61 and it just works with Android pay. No terminal commands or anything
Click to expand...
Click to collapse
Same here. I can't see any reason to "upgrade" since the later versions seem to require additional steps, and for the user I don't seem to get any added value from the later versions.
greves1 said:
I'm using 2.61 and androidpay has always worked fine. Never deleted any files after flashing that. I'd love to hear from anyone on 2.66 to know if it's working.
Edit: upgraded to 2.66 myself and it works fine so far. Will test androidpay soon, but I can't imagine why it wouldn't work...
Click to expand...
Click to collapse
What steps did you take in order to upgrade? Just flash the zip? Do you still need to run the terminal commands before the flash?
tallgrasshawk said:
What steps did you take in order to upgrade? Just flash the zip? Do you still need to run the terminal commands before the flash?
Click to expand...
Click to collapse
Don't do this upgrade if you want androidpay to work. I thought it was working at first, but later realized it wouldn't work at the store. You can just flash the zip to upgrade, but this seems to break the android pay. It would be interesting to try it the way you suggest, with running the terminal commands before flashing. Perhaps this would preserve androidpay! Good luck, post back if you find that works.
greves1 said:
Don't do this upgrade if you want androidpay to work. I thought it was working at first, but later realized it wouldn't work at the store. You can just flash the zip to upgrade, but this seems to break the android pay. It would be interesting to try it the way you suggest, with running the terminal commands before flashing. Perhaps this would preserve androidpay! Good luck, post back if you find that works.
Click to expand...
Click to collapse
I've done it both ways and it definitely works when you run the terminal commands prior to flashing. I did it wrong (without terminal commands) first, so i had to do "full unroot" from the app itself, then in recovery ran the terminal commands and flashed 2.66 again and now it works fine for me.
You also have to avoid modifying the /system partition after the fact otherwise that will also break android pay, even if you already have a card added.
you can check with this app if android pay will work:
https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground&hl=en
for example, the aggressive doze option on the new greenify beta will break safetynet, as will Adaway (unless you flash the systemless hosts zip first)
newb question
So... is there a pointer to how to actually issue the commands *before* you flash SuperSU and get root? I can't flash SuperSU to get root until I issue the commands but when I try the commands I get an error message that I need root rights. I'm sure I'm missing something easy. Thanks! (Also, has anyone found a sticky post about what commonly works without breaking root. Obviously anything that touches system, but tutorials on installing AdAway, Greenify, cflumen, etc., or even without breaking Pay would be huge. It just seems every other post has varying information.)
Phssthpok said:
So... is there a pointer to how to actually issue the commands *before* you flash SuperSU and get root? I can't flash SuperSU to get root until I issue the commands but when I try the commands I get an error message that I need root rights. I'm sure I'm missing something easy. Thanks! (Also, has anyone found a sticky post about what commonly works without breaking root. Obviously anything that touches system, but tutorials on installing AdAway, Greenify, cflumen, etc., or even without breaking Pay would be huge. It just seems every other post has varying information.)
Click to expand...
Click to collapse
Months later but adb/fastboot is the key to for terminal commands to your mobile. Likely you've solved by now but if not, theres an easy way to get adb going: http://www.androidbeat.com/2015/11/how-to-set-up-adb-and-fastboot-on-mac/
Dear all,
I have my Z1C on the latest FW with Dual Recovery and root (SuperSU) but locked bootloader. Now, some apps will not run when they detect root. Can I "unroot" the phone in a convenient way and "re-root" when needed? Without using King Root and while keeping all my data etc.?
Cheers,
Ben
If you are willing to use Xposed, you can use a module called "RootCloak" which is used for hidding root from such apps which don't work unless your phone is not rooted.
BagOfLemon said:
If you are willing to use Xposed, you can use a module called "RootCloak" which is used for hidding root from such apps which don't work unless your phone is not rooted.
Click to expand...
Click to collapse
Thanks. So Xposed works with Dual Recovery/locked bootloader?
I was hoping I could just uninstall SuperSU and re-flash it in TWRP to re-gain root.
nurunet said:
Thanks. So Xposed works with Dual Recovery/locked bootloader?
I was hoping I could just uninstall SuperSU and re-flash it in TWRP to re-gain root.
Click to expand...
Click to collapse
I think it works with Dual Recovery, I'm not entirely sure though, same for Lock/Unlock BL but it should not impact how it works.
Also there is an option in several app for Root to disable it (Completely but you can re-enable it very easily)
BagOfLemon said:
Also there is an option in several app for Root to disable it (Completely but you can re-enable it very easily)
Click to expand...
Click to collapse
There is in the version of SuperSU I am using, but it doesn't seem to work for the banking app I tried. Root cloak reportedly works for it, but I was unsure if Xposed would work with my config and did not want to risk a boot loop or similar.
nurunet said:
There is in the version of SuperSU I am using, but it doesn't seem to work for the banking app I tried. Root cloak reportedly works for it, but I was unsure if Xposed would work with my config and did not want to risk a boot loop or similar.
Click to expand...
Click to collapse
It should work independently of your recovery so no worries. You can still download the zip to uninstall in case of something gone wrong or do a Nandroid backup to be sure
BagOfLemon said:
It should work independently of your recovery so no worries. You can still download the zip to uninstall in case of something gone wrong or do a Nandroid backup to be sure
Click to expand...
Click to collapse
I guess I'll try this WE.
I tried it. In SuperSU settings I chose permanent unroot, rebooted, and voilà: The banking app worked. Then I flashed the latest SuperSU in TWRP, and root was back. Neat!