Database Develop

[Q] Bootloader unlocked, SuperSU installed, can't write to system?

Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?

neil.io said:
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
Click to expand...
Click to collapse
You flashed the latest version of TWRP custom recovery?

samwathegreat said:
You flashed the latest version of TWRP custom recovery?
Click to expand...
Click to collapse
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img

neil.io said:
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
Click to expand...
Click to collapse
That might be the issue. It might not be compatible with 4.4.3
Try this one: http://techerrata.com/browse/twrp2/ghost
Also, which version of SuperSU are you using? There was a new one released recently. Find it here: http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip (Flash it from within TWRP - install ZIP)
Please update, and then advise whether or not your issue is resolved.
EDIT: Also, make sure you are using the "stericson" busybox variant. Others have been reported to cause issues.

Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!

neil.io said:
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
Click to expand...
Click to collapse
Open SuperSU, and check to see if busybox is listed under apps. There should be a green "#" symbol next to it. It SHOULD have prompted you to grant access to it, so perhaps at some point you either denied the su request, or didn't see it. If you see a RED "#" symbol, tap it, and change to "Grant".
Please advise...

It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.

neil.io said:
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
Click to expand...
Click to collapse
I would suggest a full return to stock (follow the return to stock thread in the general sub-forum). This is not normal....
You appear to be using the XT1053, correct? Take caution to NOT downgrade or you could end up with a brick.
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.

samwathegreat said:
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
Click to expand...
Click to collapse
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.

neil.io said:
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
Click to expand...
Click to collapse
How did you SBF to stock? Did you use RSD Lite? Did you retain userdata, or wipe everything (suggested)?
The stericson variant installs fine for me...granted I'm on 4.4.2 (the latest for my variant).
I did NOT use smart install...just used regular install to /system/xbin (You might consider trying smart install if you haven't yet...)
Honestly, I'm out of ideas. Although the "stericson" variant is recommended, perhaps you should try another version from the market if you need busybox.
I've done extensive searches and haven't found anyone else having a similar issue - even with Moto X on 4.4.3

I gave up and used the recovery method. Really odd - it does seem like the other installer apps couldn't mount /system as writeable, but it's weird that other apps that installed to that area worked.
Anyway, thanks again!

[update] New wroking xposed for zenfone series

Hello guys,
In recent days, I had seen that some members have issue regarding working xposed that was released previous.
Today, I got a new version of working xposed which is patched by @shakalaca
all credit goes to original developer, I am just posting it here.
I tested it on ze550kl.
it also works on most zenfone series.
prerequisite are same as it was before.
phone must rooted
busy box must installed
root permission must provided to adb shell when asked
just extract archive & first run remov exposed freamework, if there is any non working xposed framework is installed & uninstall xposed apk if installed.
after that reboot system.
not to install frame work first click install xposxed frame work, let process complete & reboot system.
after that click install xposed installer.
now you have working xposed for sdk21 v78 arm64.

Xposed
Work perfect! Thanks!!!

Perfect work. Thanks

rajlko said:
Hello guys,
In recent days, I had seen that some members have issue regarding working xposed that was released previous.
Today, I got a new version of working xposed which is patched by @shakalaca
all credit goes to original developer, I am just posting it here.
I tested it on ze550kl.
it also works on ZenFone 2 2.20.40.13x and ZenFone Selfie 1.13. 40.661
prerequisite are same as it was before.
phone must rooted
busy box must installed
root permission must provided to adb shell when asked
just extract archive & first run remov exposed freamework, if there is any non working xposed framework is installed & uninstall xposed apk if installed.
after that reboot system.
not to install frame work first click install xposxed frame work, let process complete & reboot system.
after that click install xposed installer.
now you have working xposed for sdk21 v76 arm64.
Click to expand...
Click to collapse
It should be pointed out that on my phone query window pops root rights, only after you enter in supersu (my system cant anwer permission adb shell, while manually entered into the application SuperSU)

post updated.

Works great !
edit1
Snapprefs works now

roman.kaskad said:
It should be pointed out that on my phone query window pops root rights, only after you enter in supersu (my system cant anwer permission adb shell, while manually entered into the application SuperSU)
Click to expand...
Click to collapse
sometime pop up for root rights delay due to some mismatch, like you are using patched firmware or boot image of any other system.
Pop window for root right will works well if you have original kernel installed in your phone.
e.g. if you have ze551kl & you are using boot image of ze550kl for root your phone, then you will have this issue.
In patched firmware you may face this issue due to same issue.

Now all the ZE551KL users have to use the ze550kl root method to gain root.
Does that mean all ze551kl users will face the root rights issue?
Sent from my ASUS_Z00TD using Tapatalk

yvg107x said:
Now all the ZE551KL users have to use the ze550kl root method to gain root.
Does that mean all ze551kl users will face the root rights issue?
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
Not at all,
it happens some time.
sometime you need to open super user & after that window popup for root right, it happens due to su also.

dose it working with new version .763

BTiwari said:
dose it working with new version .763
Click to expand...
Click to collapse
Yes

roman.kaskad said:
It should be pointed out that on my phone query window pops root rights, only after you enter in supersu (my system cant anwer permission adb shell, while manually entered into the application SuperSU)
Click to expand...
Click to collapse
I had the same issue.. But i fixed it by going to auto start manager... in pre-loaded apps... And switching 'Super Su'option to 'on'...
I think as the app didnt had the the permission to auto start... Prompt only comes only when we go tp app manually.... Anywayzz it worked for me...

BTiwari said:
dose it working with new version .763
Click to expand...
Click to collapse
yes.

flash official xposed-v79-sdk21-arm64.zip normally work fine for me. not patched version.
my decive: ze551kl

not working?
I have the .763 stock firmware on the ZE551KL and rooted with instructions from this thread. It seems to install and "Android is upgrading" pops up, but then there is no Xposed app to install modules from and I've tried installing Xprivacy and BootManager and both say Xposed is not installed. So I guess it didn't work

thefallenghost said:
I have the .763 stock firmware on the ZE551KL and rooted with instructions from this thread. It seems to install and "Android is upgrading" pops up, but then there is no Xposed app to install modules from and I've tried installing Xprivacy and BootManager and both say Xposed is not installed. So I guess it didn't work
Click to expand...
Click to collapse
when you unzip file,there will be three bat files, installxposedframvwork, Installxposedinstaller & removexposedframework.
If you have rooted & install custom recovery, then you may flash zip file from recovery.
if you have not install custom recovery, then unzip file, first run installxposedframework, let process complete, provide root access from you phone when asked, let phone reboot.
after that run installxposedinstaller, let process complete, now you have xposed apk in you phone.
you may also download it from google play store or official thread from developer.

---------------------------------------
rajlko said:
when you unzip file,there will be three bat files, installxposedframvwork, Installxposedinstaller & removexposedframework.
If you have rooted & install custom recovery, then you may flash zip file from recovery.
if you have not install custom recovery, then unzip file, first run installxposedframework, let process complete, provide root access from you phone when asked, let phone reboot.
after that run installxposedinstaller, let process complete, now you have xposed apk in you phone.
you may also download it from google play store or official thread from developer.
Click to expand...
Click to collapse
Ok. When you say I have the apk in my phone, where exactly is it?! I cannot find it... Edit: Nevermind, I had forgotten to run the installer (faceapalm). Sorry...

hi
I can't reboot from Xposed Installer
When I try and reboot through the Xposed Framework I get the following error message everytime:
tmp-mksh: <stdin>[5]: /data/data/de.robv.android.xposed.installer/cache/busybox-xposed: not found
Reboot failed. Please use the device's normal reboot function.
I had busybox installer.
Not sure what else I'm doing wrong?

pedrazadixon said:
flash official xposed-v79-sdk21-arm64.zip normally work fine for me. not patched version.
my decive: ze551kl
Click to expand...
Click to collapse
Thanks for that.
installed and working on Ze551kl with stock rooted rom.
I am now have Adblock installed. woohoo!

ericpeacock79 said:
Thanks for that.
installed and working on Ze551kl with stock rooted rom.
I am now have Adblock installed. woohoo!
Click to expand...
Click to collapse
Last version v85. Work fine.
Only flash the lasted zip.

N910T acting crazy after root

So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.

I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...

Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk

Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.

noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?

I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip

https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it

Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk

Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?

Did you flash over 2.71. And do you have a su app icon on your scrren.

noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.

Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot

MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!

Welcome bud.

Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother

Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk

Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha

My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk

I think it's normal...maybe...ha Im pretty sure it's the warranty bit

are there root for N910A 5.1.1

[Guide] Pass Safetynet on a rooted 7.0 AOSP based ROM - Updated 11-01-2016

Update (11/09) - This method no longer works with the november security updates from Google as it causes suhide to break.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
2) Let the system reboot normally.
3) Reboot to recovery
4) If you have Magisk installed, flash the Magisk uninstaller Link
5) If you have suhide installed, flash rm-suhide 0.51 Link
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install suhide 0.55 Link
Reboot into system. Verify that you have root. I'm not 100% sure this is necessary, but I like to do it before proceeding.
Reboot back into recovery.
Flash xsetpropSu.zip (attached to this post) Link
Reboot the system
Install RootSwitch 1.3.3.2 Link
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Optional
Using tasker to automatically disable root when certain applications are run. @NYZack made a little writeup here
Credits:
@NYZack - Helping me figure out how to put all of this together
@Captain_Throwback - For help with xsetprop
@Chainfire - SuperSU + SuHide
@topjohnwu - Magisk

work around found

no longer relevant post..

I don't know if the kernel can be modified to pull that trick. Even if someone does though, it's not going to last long. Every bypass you can find, Google can find. Then they know what to fix. The only way to win, is not to play.
And no, you can't lock the bootloader without wiping data.

Well I got it to work...I will turn this thread into a Guide. Who knows how long it will last, but...at least it's working for now.

Thread updated with instructions. I hope this can help someone!

So there's no way to do this without rooting and magisk?

3dawg said:
So there's no way to do this without rooting and magisk?
Click to expand...
Click to collapse
I want root, so I did not try to do that. If your bootloader is unlocked, I do not think there's a way to do it.

Thanks
skaforey said:
Thread updated with instructions. I hope this can help someone!
Click to expand...
Click to collapse
Yes I just followed these instructions and I am green panel. I have to check at a terminal to pay with phone but it probably will work. One note that was kinda unclear in case others do same....It should read :
Turn the Root switch ON....not OFF....when wanting to use AP. You can turn it back on when you want to do other things that require root permissions. I believe this is dynamic and working with the magisk mount point in addition to tricking the boot process into thinking the bootloader is locked.
Thanks so much for this. I was so angry with Google. And I was just going to say FK it and not use AP.
WORKS! Do all the steps in the order he says above and you can turn root off and on at will and have Android Pay work just fine! YAY!

skaforey said:
This thread started as a plea for help, but thanks to @NYZack I have gotten it to work.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) If you have suhide installed, download rm-suhide 0.51 Link
2) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
3) Let the system reboot normally.
4) Reboot to recovery
5) Flash rm-suhide 0.51
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install Magisk v8.zip Link
Install suhide 0.55 Link
Reboot into system
Install Magisk Manger 2.1 (apk) Link
Open up Magisk Manager app and go to modules. Click on the + button. Add the following zip for xsetprop Link
Install RootSwitch 1.3.1.2 Link
Reboot system
Using Root Explorer (or some other file manager capable of root access), browse to /magisk/xsetprop and modify post-fs-data.sh . Add the following line to the end of the file, save and exit
Code:
xsetprop ro.boot.flash.locked 1
Reboot system
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Click to expand...
Click to collapse
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.

Captain_Throwback said:
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.
Click to expand...
Click to collapse
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.

No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!

Pkt_Lnt said:
http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
Click to expand...
Click to collapse
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can't get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??

jcrompton said:
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??
Click to expand...
Click to collapse
Yea I know I think it's something to do with either the kernel I've selected or perhaps suhide no longer works...I'm not sure what the deal is. I'm running Franco #55 and even without root, I get failure but inside the testing app ...see attached

Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.

MrBrady said:
Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.
Click to expand...
Click to collapse
I'm using stock Rom and only custom kernel so this should work on Nbd90z....I'd think. Last test was dreaded message but I'm trying to add few things to suhide blacklist. We shall see

I get the green screen. But then when I tap at store nfc terminal...it claims error....I'm going to try hiding nfc service, and what I think is play services based on uid chainfire explained. I'll try a small purchase and remember to screen capture the error if occurs

skaforey said:
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.
Click to expand...
Click to collapse
I built the mod for people that were already using Magisk. If you're not using Magisk, then of course you can try just putting the binary in /su/xbin and put the post-fs-data.sh in /su/su.d and see if that works for setting the props at boot time.
I don't use Xposed, so using Magisk + phh's Superuser was my target for the module. I also did try the su.d method with SuperSU, but it wasn't working on my device. I also didn't want to have to use RootSwitch. But feel free to unpack the zip and try whatever combinations you want.

photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command

skaforey said:
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command
Click to expand...
Click to collapse
I'm using it for android pay not pogo. And I did. I'm sure the prop is right or wouldn't get green go. It's an error from AP saying something about unable to verify and might be rooted....or words to that effect

How do I replace KingRoot with SuperSU?

Hello, just got the tablet and I'm rooted and everything thanks to root junky and this community!
The only issue I have on 5.3.1 is that I try and replace ringroot with SuperSU but it won't update the binary. Can anyone lend me a hand to tell me what I am doing wrong?
Thanks!

stu5797 said:
Hello, just got the tablet and I'm rooted and everything thanks to root junky and this community!
The only issue I have on 5.3.1 is that I try and replace ringroot with SuperSU but it won't update the binary. Can anyone lend me a hand to tell me what I am doing wrong?
Thanks!
Click to expand...
Click to collapse
I noticed this on my fire 5.1.3. When I saw that message on CMD window, I just dragged supersu from supertool folder over CMD and it replaced kingroot automatically. Hope that helps.

anmsr said:
I noticed this on my fire 5.1.3. When I saw that message on CMD window, I just dragged supersu from supertool folder over CMD and it replaced kingroot automatically. Hope that helps.
Click to expand...
Click to collapse
Err...no, that won't work. Use the conversion function built into the 5th gen SuperTool. Select the option to root then skip over the KingRoot section as device is already rooted. SuperTool will the proceed with removing KingUser and installing SuperSU.

Davey126 said:
Err...no, that won't work. Use the conversion function built into the 5th gen SuperTool. Select the option to root then skip over the KingRoot section as device is already rooted. SuperTool will the proceed with removing KingUser and installing SuperSU.
Click to expand...
Click to collapse
how to do that, I have seen option 6, which is combination of installing kingroot, get root access and then replace it SuperSu. In my experience, I noticed it does not do anything after I get root access on fire tablet. But when I drag and drop it works. I am not expert but open to your suggestion.

Thanks for your help! Davey can you please elaborate on conversion function? Not really sure what to do?

Davey126 said:
...use the conversion function built into the 5th gen SuperTool. Select the option to root then skip over the KingRoot section as device is already rooted. SuperTool will the proceed with removing KingUser and installing SuperSU.
Click to expand...
Click to collapse
anmsr said:
how to do that, I have seen option 6, which is combination of installing kingroot, get root access and then replace it SuperSu. In my experience, I noticed it does not do anything after I get root access on fire tablet. But when I drag and drop it works. I am not expert but open to your suggestion.
Click to expand...
Click to collapse
stu5797 said:
Thanks for your help! Davey can you please elaborate on conversion function? Not really sure what to do?
Click to expand...
Click to collapse
Not sure where the confusion lies. When option #7 is selected in the lastest SuperTool build two things happen:
- attempt to root using KingRoot
- once rooted SuperTool will then attempt to replace KingUser with SuperSU
Note: an active adb (tethered) connection to the device must exist for the conversion process to work. Also make sure you have the Oct 2016 build of the SuperTool.