Hey guys, got my Nexus 5X with Android 6.0.0 build number MDB08L. I rooted it with the Nexus Root Toolkit v2.1.0 successfully, tested with Root Checker.
Problem is after my root process, NRT asks me to install BusyBox 1.24.1
I've granted BusyBox root access and tried installing to /system/xbin and /system/bin but installation to both directories are not successful. I'm not sure why this is the case.
Would greatly appreciate any help I can get. Happy to supply any other info. Thank you!
I think NRT may cause the problem, try rooting with new systemless supersu
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
cavalloz said:
I think NRT may cause the problem, try rooting with new systemless supersu
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
Thanks. Is there another workaround? I prefer not to try an experimental way..
I'm on 6.0.1 with latest systemless and everything is good (apps, busybox, xposed, gravitybox,..).
btw you can try rooting the old way (supersu 2.52) but don't use NRT
cavalloz said:
I'm on 6.0.1 with latest systemless and everything is good (apps, busybox, xposed, gravitybox,..).
btw you can try rooting the old way (supersu 2.52) but don't use NRT
Click to expand...
Click to collapse
Oh okay, will try it out soon. Thank you
Sent from my Nexus 5X using Tapatalk
Related
Is it safe to install Safestrap v4.0.1 on Fire v4.6.4? Or should I first downgrade to 4.6.1 (update-fire-phone-33.4.6.1_user_461013320.bin OR ...461013820.bin)?
DePingus said:
Is it safe to install Safestrap v4.0.1 on Fire v4.6.4? Or should I first downgrade to 4.6.1 (update-fire-phone-33.4.6.1_user_461013320.bin OR ...461013820.bin)?
Click to expand...
Click to collapse
Yes it is safe, I've tried it and had no problems using Safestrap v4.0.1 on Fire v4.6.4.
jack9955 said:
Yes it is safe, I've tried it and had no problems using Safestrap v4.0.1 on Fire v4.6.4.
Click to expand...
Click to collapse
Great news! Much obliged.
DePingus said:
Great news! Much obliged.
Click to expand...
Click to collapse
Thank you for this information. I wasnt able to find a safe root method for OS4.6.4 can you post me in the right direction? Does Towel root work?
webbie2 said:
I wasnt able to find a safe root method for OS4.6.4 can you post me in the right direction? Does Towel root work?
Click to expand...
Click to collapse
Towelroot, Framaroot, etc. don't work. Only Kingroot works at the moment and I know that this specific app doesn't meet the criterion "safe".
Oh and there's one from Wondershare, but this one is even more work, needs install. to PC, etc. and it's not much cleaner than Kingroot.
Most people used this method for stock OS root:
• Use Kingroot, disable auto updates in Kinguser right after root succeeded
• Remove Kingroot with SuperSume Pro (free version no longer available, only paid version)
Although, if you keep Safestrap installed, try flashing the SuperSu ZIP from Chainfire, someone mentioned it but I'd need to search for it...
i getting this on Supersu
there is no SU binary installed and Supersu cannot install it. this is a problem!
if you just upgraded to android 5.0 you need to manually re root consult the relevant forum for your device!
eternity4ever said:
i getting this on Supersu
there is no SU binary installed and Supersu cannot install it. this is a problem!
if you just upgraded to android 5.0 you need to manually re root consult the relevant forum for your device!
Click to expand...
Click to collapse
I had absolutely no problems with root and ARHD 50.2. Flash it again, and DON'T flash SuperSU when twrp ask for it.
If it's still give problems, just flash latest SuperSU for MM and it should work without problems.
Running N910PVPU4DPC1 [http://forum.xda-developers.com/note-4-sprint/development/rom-t3352832]
It's been running fine for the past month or so, then yesterday, I went to run Titanium Backup, and it said my phone no longer had root access.
---------------------------------------------
SuperSU
There is no SU binary installed, and SuperSU cannot install it. There is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!
---------------------------------------------
I've tried to re-root via CF-Auto-Root, it'll complete without error, but still no root access.
Anyway I can get root back without blowing out and starting from scratch?
If you have recovery just flash SuperSU itself.
SaintZ93 said:
If you have recovery just flash SuperSU itself.
Click to expand...
Click to collapse
Thanks for your reply SaintZ93.
Just tried that via https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Uninstalled my previous version of SuperSU, booted to TWRP 3.0.2-0, no errors on install, fire up SuperSU, I get the same error message as before.
I was really hoping to get SU back with out having to go and reinstall everything. Doesn't look like it's going to work out that way.
Actually I just noticed the same thing, its quite weird, I lost root also. I had root working fine with PD1 now its gone.
I believe a security update was pushed, well at I know one was on my Sprint Note 4, and I think it auto installed that's what made me lost root.
I simply flashed supersu from TWRP and I had root again.
Don't know if this would help, but I turned off firmware updates on my phone and haven't had an issue for the last 3 days.
I think the update was pushed out on Tuesday or Wednesday because I noticed I didn't have root on Thursday.
krakerx said:
Running N910PVPU4DPC1 [http://forum.xda-developers.com/note-4-sprint/development/rom-t3352832]
It's been running fine for the past month or so, then yesterday, I went to run Titanium Backup, and it said my phone no longer had root access.
---------------------------------------------
SuperSU
There is no SU binary installed, and SuperSU cannot install it. There is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!
---------------------------------------------
I've tried to re-root via CF-Auto-Root, it'll complete without error, but still no root access.
Anyway I can get root back without blowing out and starting from scratch?
Click to expand...
Click to collapse
I believe that the SuperSu that comes with that ROM is systemless, which you would need to flash SuperSu 2.68
I am in the same boat.
ianmb said:
I believe that the SuperSu that comes with that ROM is systemless, which you would need to flash SuperSu 2.68
Click to expand...
Click to collapse
That worked like a f'n charm!
I uninstalled SuperSU, downloaded SuperSU 2.68 [https://download.chainfire.eu/924/SuperSU], installed via TWRP, and verified!
Thanks for all the help!
krakerx said:
That worked like a f'n charm!
I uninstalled SuperSU, downloaded SuperSU 2.68 [https://download.chainfire.eu/924/SuperSU], installed via TWRP, and verified!
Thanks for all the help!
Click to expand...
Click to collapse
Glad it worked for you
can I stall SUPERSU 2.68 with stock recovery? how?
I extracted the 2.68 zip but can I install without a custom recovery?
krakerx said:
That worked like a f'n charm!
I uninstalled SuperSU, downloaded SuperSU 2.68 [https://download.chainfire.eu/924/SuperSU], installed via TWRP, and verified!
Thanks for all the help!
Click to expand...
Click to collapse
Same issue of lost root. Worked great so far. Thanks for the info.
Sent from my SM-N910P using Tapatalk
Hello everyone
Recently due to Niantic's decision to prohibit root users of playing Pokémon Go I decided to give a try to Magisk. I followed every step and even flashed my ROM again.
But when trying phh's root it wont work. Rootchecker says root was not correctly installed and trying to use any root app won't make Superuser show any prompt for root permissions.
Thank you so much for the help guys.
more info
renezada88 said:
Hello everyone
Recently due to Niantic's decision to prohibit root users of playing Pokémon Go I decided to give a try to Magisk. I followed every step and even flashed my ROM again.
But when trying phh's root it wont work. Rootchecker says root was not correctly installed and trying to use any root app won't make Superuser show any prompt for root permissions.
Thank you so much for the help guys.
Click to expand...
Click to collapse
What is your ROOT Method, That makes a difference since there might be a conflict in ROM (Preinstalled mods or apps), also, What ROM is it?
CKWTHN said:
What is your ROOT Method, That makes a difference since there might be a conflict in ROM (Preinstalled mods or apps), also, What ROM is it?
Click to expand...
Click to collapse
I flash Magisk v6 and phh's on TWRP. On the other hand I use the stock ROM MM 6.0.1 build 32.2.A.0.253
Apparently Magisk doesn't work properly on Sony devices. See topjohnwu's OP in the Magisk thread.
It partially works for me with some apps like Adaway and TiBU requesting for permissions and working properly but with most other apps not requesting root.
benengyj said:
Apparently Magisk doesn't work properly on Sony devices. See topjohnwu's OP in the Magisk thread.
It partially works for me with some apps like Adaway and TiBU requesting for permissions and working properly but with most other apps not requesting root.
Click to expand...
Click to collapse
I don't know how I could have missed that... Thanks a lot for that. I hope it gets a fix soon enough tho.
Rooted (super su) and ElementalX kernel, nougat 7.1.2. I want to use viper4android and having problems (driver installs but it doesn't work). I read that installing magisk su might work better but I get an error every time I try. Super su is systemless and guides are saying it should work just to flash the zip of magisk but it isn't working. Is there anything I need to do? I also have poweramp installed which may be messing with viper4android but I'm a bit lost. Any help would be great.
Are you trying to install Magisk on top of SuperSu or in place of it? Also, you are using the version of Magisk that was modified for the Pixel, not the official version, correct?
jhs39 said:
Are you trying to install Magisk on top of SuperSu or in place of it? Also, you are using the version of Magisk that was modified for the Pixel, not the official version, correct?
Click to expand...
Click to collapse
I'm going in place of SuperSU, I think you've nailed my issue though....I didn't know there was a modified version
Kevinj17 said:
I'm going in place of SuperSU, I think you've nailed my issue though....I didn't know there was a modified version
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B1xZ4VKT4JKZUFhVUlk0enhBVFk/view