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/
Related
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.
Hello all,
I recently got my hands on a Note 2 running Android 4.3 on the MK6 bootloader. I have done a bit of research, but am still somewhat confused about how to root the phone. If I am correct, I just use Odin to flash this:
http://forum.xda-developers.com/showthread.php?t=2589891
Onto the phone to have root access, correct?
Next, if I want to have CWM, I flash this:
http://forum.xda-developers.com/showthread.php?t=2159652
If there are any steps I am missing, please let me know. I would like to procede with as much knowledge as possible to avoid bricking the phone. I am aware that doing this will trip the Knox e-fuse, and I am ok with that.
Thanks in advance!
Luigiman765 said:
Hello all,
I recently got my hands on a Note 2 running Android 4.3 on the MK6 bootloader. I have done a bit of research, but am still somewhat confused about how to root the phone. If I am correct, I just use Odin to flash this:
http://forum.xda-developers.com/showthread.php?t=2589891
Onto the phone to have root access, correct?
Next, if I want to have CWM, I flash this:
http://forum.xda-developers.com/showthread.php?t=2159652
If there are any steps I am missing, please let me know. I would like to procede with as much knowledge as possible to avoid bricking the phone. I am aware that doing this will trip the Knox e-fuse, and I am ok with that.
Thanks in advance!
Click to expand...
Click to collapse
#1 is a full ROM like you have but rooted.
Try this
http://download.chainfire.eu/280/CF...uto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
#2 is good. You need to do that before doing number 1.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt
philz_touch_6.15.4-t0lteatt.tar.md5
Flash via ODIN http://d-h.st/N1V
dicksteele said:
#1 is a full ROM like you have but rooted.
Try this
http://download.chainfire.eu/280/CF...uto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
#2 is good. You need to do that before doing number 1.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt
philz_touch_6.15.4-t0lteatt.tar.md5
Flash via ODIN http://d-h.st/N1V
Click to expand...
Click to collapse
Alright, thanks!
So I flash the CF Auto Root via Odin, then CWM, and then I can flash any ROM, right?
Thanks for the help
Luigiman765 said:
Alright, thanks!
So I flash the CF Auto Root via Odin, then CWM, and then I can flash any ROM, right?
Thanks for the help
Click to expand...
Click to collapse
Yes. For now stick with ROMs in here.
http://forum.xda-developers.com/galaxy-note-2-att/development
Here's a guide for TWRP recovery
http://www.addictivetips.com/android/what-is-twrp-how-to-install-use-it-on-android-devices-guide/
Download is here to flash in ODIN
http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.6.3.1-t0lteatt.img.tar
It's a little easier to use to start.
Always make backups !!!
So, today I tried to root my phone, and as soon as I was finished flashing CF Auto Root, Knox blocked the root and said that "Unauthorized access to a secured area has been blocked."
Does that mean I cannot root my phone?
Luigiman765 said:
So, today I tried to root my phone, and as soon as I was finished flashing CF Auto Root, Knox blocked the root and said that "Unauthorized access to a secured area has been blocked."
Does that mean I cannot root my phone?
Click to expand...
Click to collapse
No you're fine. Go to Google Play, Download the Update for SuperSU. Update it, it will pop up a window and ask if you want to disable Knox.
SAY YES !
dicksteele said:
No you're fine. Go to Google Play, Download the Update for SuperSU. Update it, it will pop up a window and ask if you want to disable Knox.
SAY YES !
Click to expand...
Click to collapse
Thanks for the answer, but there is no option to update SuperSU from Google Play, and I can't uninstall it either.
Is there a direct link where I can download the file to update the SuperSU to disable Knox?
Luigiman765 said:
Thanks for the answer, but there is no option to update SuperSU from Google Play, and I can't uninstall it either.
Is there a direct link where I can download the file to update the SuperSU to disable Knox?
Click to expand...
Click to collapse
Login to Google on your PC.
Try going here.
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
It should say Installed. Click the Installed button, make sure phone is listed. See if it will install from there.
dicksteele said:
Login to Google on your PC.
Try going here.
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
It should say Installed. Click the Installed button, make sure phone is listed. See if it will install from there.
Click to expand...
Click to collapse
Hmm, unfortunately it says that it is already installed on the phone I am trying to root, and I can't install it again
Luigiman765 said:
Hmm, unfortunately it says that it is already installed on the phone I am trying to root, and I can't install it again
Click to expand...
Click to collapse
It should say installed. When you click it another window pops up. It should list your phone. Just click install button.
If that does not work go to Application Manager and try and remove it.
dicksteele said:
It should say installed. When you click it another window pops up. It should list your phone. Just click install button.
If that does not work go to Application Manager and try and remove it.
Click to expand...
Click to collapse
Yeah, I clicked the "Installed," but I cannot click on the phone that I have this on, it says already installed
And I can't uninstall it from Appilcation Manager, just "Force Stop" or "Turn Off"
I am very stuck unfortunately ):
Luigiman765 said:
Yeah, I clicked the "Installed," but I cannot click on the phone that I have this on, it says already installed
And I can't uninstall it from Appilcation Manager, just "Force Stop" or "Turn Off"
I am very stuck unfortunately ):
Click to expand...
Click to collapse
Interesting. I've never seen that before. And I really just saw it because mine is doing the same thing.....
Try flashing via ODIN
http://download.chainfire.eu/280/CF...uto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
Or is that the one you did?
EDIT:
I just uninstalled my updates and flashed this. Worked for me.
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Not saying it's going to work, should really. It's the lastest.
dicksteele said:
Interesting. I've never seen that before. And I really just saw it because mine is doing the same thing.....
Try flashing via ODIN
http://download.chainfire.eu/280/CF...uto-Root-t0lteatt-t0lteatt-samsungsghi317.zip
Or is that the one you did?
EDIT:
I just uninstalled my updates and flashed this. Worked for me.
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Not saying it's going to work, should really. It's the lastest.
Click to expand...
Click to collapse
Thanks for the research, so I should try flashing that via recovery?
Yes. That's the latest version
Sent from my stuff using xda app-developers app
dicksteele said:
Yes. That's the latest version
Sent from my stuff using xda app-developers app
Click to expand...
Click to collapse
Agh, still nothing - I can't uninstall SuperSU and flashing did not help; Knox still is working.
Should I just wipe from recovery first?
Luigiman765 said:
Agh, still nothing - I can't uninstall SuperSU and flashing did not help; Knox still is working.
Should I just wipe from recovery first?
Click to expand...
Click to collapse
Whole lotta WTF. I'm now running into the same issue with the Note2_lte_e250_R7. 2 ROM I flashed.
Everything I have tried is not getting root to stick. I will kick it's a$$.
Trying a couple more things. I'll let you know when I succeed.
---------- Post added at 12:46 PM ---------- Previous post was at 12:08 PM ----------
May have found something....
Koushik Dutta
https://plus.google.com/u/0/110558071969009568835/posts/YsXBtjuD6rD
Superuser installation issues after installing over SuperSU
It seems SuperSU is writing a file that is confusing Superuser installation on stock builds. If you want to install Superuser over SuperSU, you will need to manually remove the /system/etc/.has_su_daemon file.
I have the /system/etc/.has_su_daemon file.l I'm creating a CWM zip to remove it.
Hopefully that's the solution.
dicksteele said:
Whole lotta WTF. I'm now running into the same issue with the Note2_lte_e250_R7. 2 ROM I flashed.
Everything I have tried is not getting root to stick. I will kick it's a$$.
Trying a couple more things. I'll let you know when I succeed.
---------- Post added at 12:46 PM ---------- Previous post was at 12:08 PM ----------
May have found something....
Koushik Dutta
https://plus.google.com/u/0/110558071969009568835/posts/YsXBtjuD6rD
Superuser installation issues after installing over SuperSU
It seems SuperSU is writing a file that is confusing Superuser installation on stock builds. If you want to install Superuser over SuperSU, you will need to manually remove the /system/etc/.has_su_daemon file.
I have the /system/etc/.has_su_daemon file.l I'm creating a CWM zip to remove it.
Hopefully that's the solution.
Click to expand...
Click to collapse
And it wasn't ..... I created a flashable zip that deleted them and it didn't work.
But I did kick it's a$$.
Like I said earlier I running the 【ROM】【March 01】【4.3】Note2_lte_e250_R7. 2 . It's a N7105 port for the ATT.
So I knew there was something called a Multitool in the N7105 threads from Dr Ketan.
I flashed that in TWRP, it's an aroma install type flash, so I only choose Root and install Busybox.
Like all of our other flash installs it looked like it completed successfully.
Every flash or ODIN I've done or most today, I've gotten into adb shell and did
ls -l /system/xbin/su. never saw the file.
After flashing root and busybox I finally saw
[email protected]:/ $ ls -l /system/xbin/su
-rwxr-xr-x root root 100452 2008-08-01 05:00 su
Woo Hoo !
Got into phone, ran supersu, still said no binary.
Not sure why I did this really buy I typed su while in adb shell, Supersu window popped up on my phone, I clicked accept and all root stuff is working.
I have no clue why this worked. But it did, for me anyways. Hopefully it'll work for you, Luigi.
dicksteele said:
And it wasn't ..... I created a flashable zip that deleted them and it didn't work.
But I did kick it's a$$.
Like I said earlier I running the 【ROM】【March 01】【4.3】Note2_lte_e250_R7. 2 . It's a N7105 port for the ATT.
So I knew there was something called a Multitool in the N7105 threads from Dr Ketan.
I flashed that in TWRP, it's an aroma install type flash, so I only choose Root and install Busybox.
Like all of our other flash installs it looked like it completed successfully.
Every flash or ODIN I've done or most today, I've gotten into adb shell and did
ls -l /system/xbin/su. never saw the file.
After flashing root and busybox I finally saw
[email protected]:/ $ ls -l /system/xbin/su
-rwxr-xr-x root root 100452 2008-08-01 05:00 su
Woo Hoo !
Got into phone, ran supersu, still said no binary.
Not sure why I did this really buy I typed su while in adb shell, Supersu window popped up on my phone, I clicked accept and all root stuff is working.
I have no clue why this worked. But it did, for me anyways. Hopefully it'll work for you, Luigi.
Click to expand...
Click to collapse
Thanks for all the info!
So, let me get this straight:
I don't need the ROM you're running on my phone. What I should do is find the Multitool, flash it via recovery, and root and Busybox. Then, connect my phone to my computer to run adb (which I don't really know how to do, so I'll have to look that up), type in su, and then from there everything should work as normal.
Also, an extra piece of information I forgot to mention earlier that you might find useful: SuperSU does NOT start at all; it just immediately closes when I click the icon, and then the Knox warning comes up. Did this happen for you?
Luigiman765 said:
Thanks for all the info!
So, let me get this straight:
I don't need the ROM you're running on my phone. What I should do is find the Multitool, flash it via recovery, and root and Busybox. Then, connect my phone to my computer to run adb (which I don't really know how to do, so I'll have to look that up), type in su, and then from there everything should work as normal.
Also, an extra piece of information I forgot to mention earlier that you might find useful: SuperSU does NOT start at all; it just immediately closes when I click the icon, and then the Knox warning comes up. Did this happen for you?
Click to expand...
Click to collapse
Really have no clue.All I know is it worked for me.
For me SuperSU opened all he way. It told me I didn't have the su binary, do a manually install. Everything I did, did not work until my last post. 99% sure it will work for you.
For ADB use this....
http://four-nineteen.com/veronica/XDA Developers/Nook Tablet/DRIVERs/ADB + Fastboot + Drivers.zip
Unzip and save only the files that start with ADB. Create a directory like ADB under C:\.
Copy all the ADB files to C\ADB
Go to command prompt in windows, cd to c:\adb directory (whatever you created)
Type adb devices. Make sure it has a device listed
C:\xUltimate-v2.4.2\jar>adb devices
List of devices attached
8675309JennieJennie device
If so, type adb shell
C:\xUltimate-v2.4.2\jar>adb shell
[email protected]:/ $
_______________________________________________________________________________
Just found something else that works.... I've tried it also.
Flash the AGNI kernel. (Awesome addition to a ROM)
https://app.box.com/s/9wlk6y1o50gbhmhvjp2u
Credit to @mjohnson4580 for fix.
Then flash the root update.
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
See what that does.
Here's info in the kernel
http://forum.xda-developers.com/showthread.php?t=2602053
Aweome work by psndna88
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
No, i downloaded normal su (SuperSU) and then flashed it through TWRP. I don't know which su you are using, but there are loads of us who have installed SuperSU without an issue.
nemexs said:
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
Click to expand...
Click to collapse
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
PS: regular supersu is both systemless and "normal" root it makes a decision during installation determining whether your device can support normal root and if not then it does a systemless boot.img patch.
StykerB said:
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
You beat me to pointing him to it. If I can add, there's a dedicated SuperSU thread to seek help if SuperSU causes an issue:
http://forum.xda-developers.com/showthread.php?t=1538053
Highly unlikely but just in case. If you are not sure, there are sufficient number of toolkits out there that can simplify the job for you.
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
nemexs said:
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
Click to expand...
Click to collapse
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
tropicanapure said:
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
Click to expand...
Click to collapse
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
nemexs said:
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
Click to expand...
Click to collapse
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
tropicanapure said:
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
Click to expand...
Click to collapse
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
nemexs said:
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
Click to expand...
Click to collapse
Assuming your bootloader is already unlocked beforehand, the straight answer to your question is yes, that's how most of us do it.
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
otonieru said:
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
Click to expand...
Click to collapse
doesn't work for me.
Any ideas?
I dont understand what problem pokemon go has with root.
Sent from my iPhone using Tapatalk
It will ban the users with rooted phones i had a account for my son and he can't login anymore but i don't know if is banned or is that app dose not connect to the server if the phone is rooted all he gets is Unable to connect to server.
Magisk, I runn CM 13 n only magisk do the trick.
See I tried magisk and its says it's not installed correctly
FreeTheWeb said:
It will ban the users with rooted phones i had a account for my son and he can't login anymore but i don't know if is banned or is that app dose not connect to the server if the phone is rooted all he gets is Unable to connect to server.
Click to expand...
Click to collapse
The app checks for su binaries then says your os isn't supported
Solved by changing from supersu to magisk
FreeTheWeb said:
Solved by changing from supersu to magisk
Click to expand...
Click to collapse
I thought you needed an unlocked bootloader for that to work?
lpstudio said:
I thought you needed an unlocked bootloader for that to work?
Click to expand...
Click to collapse
You can use mr.bump after flash magisk, that will do the trick. In my case magisk breaks my rom RIL but there is another option, Chainfire's suhide. You can use it with Super SU without problem and it hides root from each app individually.
lemit93 said:
You can use mr.bump after flash magisk, that will do the trick. In my case magisk breaks my rom RIL but there is another option, Chainfire's suhide. You can use it with Super SU without problem and it hides root from each app individually.
Click to expand...
Click to collapse
Nice so all I need is suhide? no magisk?
lpstudio said:
Nice so all I need is suhide? no magisk?
Click to expand...
Click to collapse
Yep.
So for me (i'm on android aosp 7.0) i dont think that mathers but...
Before you do this make sure that you have no root or xposed
The steps are the following:
1 - On twrp terminal enter these 2 comands (to ensure systemless root)
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
2- Flash the latest SuperSU v2.78 SR1 or newer
3- Flash mr.bump or cbump (to bump the kernel)
4- Reboot the phone and see if you have root
5- Use FlashFire from chainfire (because twrp doesnt work well, dont know why) to flash suhide
6- If all goes well you should have saftynet pass (pokemon and androidpay are already on blacklist)
lemit93 said:
Yep.
So for me (i'm on android aosp 7.0) i dont think that mathers but...
Before you do this make sure that you have no root or xposed
The steps are the following:
1 - On twrp terminal enter these 2 comands (to ensure systemless root)
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
2- Flash the latest SuperSU v2.78 SR1 or newer
3- Flash mr.bump or cbump (to bump the kernel)
4- Reboot the phone and see if you have root
5- Use FlashFire from chainfire (because twrp doesnt work well, dont know why) to flash suhide
6- If all goes well you should have saftynet pass (pokemon and androidpay are already on blacklist)
Click to expand...
Click to collapse
Where do I find mr.bump or cbump? I have look in all the threads regarding bump and tried google it but I can't find anything called mr.bump or cbump.
deuce237bblock said:
Where do I find mr.bump or cbump? I have look in all the threads regarding bump and tried google it but I can't find anything called mr.bump or cbump.
Click to expand...
Click to collapse
Took me a while too xD. The thread where I get it was removed.
Found it on a paranoid thread, Here you go sir: Mr.Bump - all credits to @dadi11
lemit93 said:
Took me a while too xD. The thread where I get it was removed.
Found it on a paranoid thread, Here you go sir: Mr.Bump - all credits to @dadi11
Click to expand...
Click to collapse
Thank you very much. I actually found it in the download section of this thread.
I'm using cloudyg3 2.5 rom. Any ideas if magisk will work with it?
Dunno if Magisk works anymore, there's a dedicated thread in the Magisk forum. On my S3 (which is my backup phone) I have it all installed, excluding xposed. suhide works.
http://forum.xda-developers.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722
Might reinstall the NamelessROM today to see if only systemless SuperSU and suhide are enough.
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.