No root access for sense lolipop - Sprint HTC One (M7)

Well i flashed some lollipop roms & i have a huge prob...I've lost root access for most apps.SuperSu app show them as greanted & actually no Su access..Any solution please..Well now im on latest official lollipop update...
also i got this " erofs (read-only file system)" when i tried to modify system file.

crazykas said:
Well i flashed some lollipop roms & i have a huge prob...I've lost root access for most apps.SuperSu app show them as greanted & actually no Su access..Any solution please..Well now im on latest official lollipop update...
also i got this " erofs (read-only file system)" when i tried to modify system file.
Click to expand...
Click to collapse
Which rom exactly? There are currently a total of 3 including the RUU. On the Superuser app check if there's a update for the binary.

luigi311 said:
Which rom exactly? There are currently a total of 3 including the RUU. On the Superuser app check if there's a update for the binary.
Click to expand...
Click to collapse
RUU in this thread http://forum.xda-developers.com/sprint-htc-one/general/sprint-htc-one-android-5-0-coming-soon-t3001541.
Thanks i'll check that out

Is there a root method for lollipop yet? S-OFF, unlocked, and TWRP installed, just waiting for a method to root and disable write protection.

Robert542 said:
Is there a root method for lollipop yet? S-OFF, unlocked, and TWRP installed, just waiting for a method to root and disable write protection.
Click to expand...
Click to collapse
Does TWRP ask you to install SuperSU when you try to exit it? I haven't tried on Lollipop yet, but I know when I've been running stock unrooted in the past, TWRP would prompt me to root when I restarted to system.

coal686 said:
Does TWRP ask you to install SuperSU when you try to exit it? I haven't tried on Lollipop yet, but I know when I've been running stock unrooted in the past, TWRP would prompt me to root when I restarted to system.
Click to expand...
Click to collapse
This method seems to work just fine for me. After installing supersu in TWRP then opened supersu selected TWRP and it downloaded the latest binaries and flashed in TWRP and worked fine after reboot.

I RUU'ed today to the newest Sprint M7 version. After downloading TWRP Manager got message that TWRP needs root permissions. Downloaded WinDroid, used it to flash TWRP. then used it to gain root access. WinDroid did not work for me on Windows 10 Tech Preview. Went to other hard drive with Win 7, and worked great. The thing I have noticed is that Root App Delete will not uninstall the Sprint bloat, or the Google crap (movies, TV, books, etc).

coal686 said:
Does TWRP ask you to install SuperSU when you try to exit it? I haven't tried on Lollipop yet, but I know when I've been running stock unrooted in the past, TWRP would prompt me to root when I restarted to system.
Click to expand...
Click to collapse
Unfortunately it does not. I even tried Philz to see if it would root and it's still a no go. Philz said I was rooted and just needed to download superuser from the play store. I downloaded super user and it says I need to root my phone.
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
retiredtrebor said:
I RUU'ed today to the newest Sprint M7 version. After downloading TWRP Manager got message that TWRP needs root permissions. Downloaded WinDroid, used it to flash TWRP. then used it to gain root access. WinDroid did not work for me on Windows 10 Tech Preview. Went to other hard drive with Win 7, and worked great. The thing I have noticed is that Root App Delete will not uninstall the Sprint bloat, or the Google crap (movies, TV, books, etc).
Click to expand...
Click to collapse
Write protection needs to be disabled.

Robert542 said:
Unfortunately it does not. I even tried Philz to see if it would root and it's still a no go. Philz said I was rooted and just needed to download superuser from the play store. I downloaded super user and it says I need to root my phone.
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
Write protection needs to be disabled.
Click to expand...
Click to collapse
And how does one go about disabling write protection?

retiredtrebor said:
And how does one go about disabling write protection?
Click to expand...
Click to collapse
From my understanding, that has to be done by a ROM and/or kernel developer.

Related

Unlock and Temper, can not root

Dear All,
I manage to unlock my bootloader, but enter into recovery,
I also used management to installed Super SU, on internal memory,
While doing the rooting, I using TWRP Recovery method I installed Successfully Super SU, but when I reboot my phone and check for super SU which is not visible on my home screen, and using root cheker when I check with application its showing no root access.
Please help
Thanks
Vivek
vievk said:
Dear All,
I manage to unlock my bootloader, but enter into recovery,
I also used management to installed Super SU, on internal memory,
While doing the rooting, I using TWRP Recovery method I installed Successfully Super SU, but when I reboot my phone and check for super SU which is not visible on my home screen, and using root cheker when I check with application its showing no root access.
Please help
Thanks
Vivek
Click to expand...
Click to collapse
I have the exact same problem. I hope some people here can help.
Aaberg said:
I have the exact same problem. I hope some people here can help.
Click to expand...
Click to collapse
you need an unsecured kernel. if you're still on stock ROM, that kernel has write protection enabled, and system changes won't survive a reboot.
nkk71 said:
you need an unsecured kernel. if you're still on stock ROM, that kernel has write protection enabled, and system changes won't survive a reboot.
Click to expand...
Click to collapse
I'm completely stock besides the unlocked bootloader and recovery. Do you have a kernel that you can recommend?
nkk71 said:
you need an unsecured kernel. if you're still on stock ROM, that kernel has write protection enabled, and system changes won't survive a reboot.
Click to expand...
Click to collapse
Hey Nkk71
That's strange, my device rooted with superSU completely stock and survives a reboot. Titanium backup and other still obtain root and root checker shows rooted.
Just curious
mb_guy said:
Hey Nkk71
That's strange, my device rooted with superSU completely stock and survives a reboot. Titanium backup and other still obtain root and root checker shows rooted.
Just curious
Click to expand...
Click to collapse
I used the method shown in the video. I'm on an unlocked European HTC One, if that helps.
mb_guy said:
Hey Nkk71
That's strange, my device rooted with superSU completely stock and survives a reboot. Titanium backup and other still obtain root and root checker shows rooted.
Just curious
Click to expand...
Click to collapse
I stand corrected then
Can you just explain to the OP how you installed it... I'm on custom ROM so dont have these issues and i'm using superuser not superSU.
and where is the superuser.apk? i'm assuming in your case it would be under /data/app as opposed to /system/app, is that correct?
---------- Post added at 11:41 AM ---------- Previous post was at 11:38 AM ----------
Aaberg said:
I used the method shown in the video. I'm on an unlocked European HTC One, if that helps.
Click to expand...
Click to collapse
Don't know what video you're referring to, but try flashing the zip from this thread: http://forum.xda-developers.com/showthread.php?t=1538053
This flashable zip: http://download.chainfire.eu/supersu in custom recovery.
nkk71 said:
I stand corrected then
Can you just explain to the OP how you installed it... I'm on custom ROM so dont have these issues and i'm using superuser not superSU.
and where is the superuser.apk? i'm assuming in your case it would be under /data/app as opposed to /system/app, is that correct?
---------- Post added at 11:41 AM ---------- Previous post was at 11:38 AM ----------
Don't know what video you're referring to, but try flashing the zip from this thread: http://forum.xda-developers.com/showthread.php?t=1538053
This flashable zip: http://download.chainfire.eu/supersu in custom recovery.
Click to expand...
Click to collapse
I don't now what video either. You are right I flashed 1.93 from TWRP, didn't move the app to system. Perhaps that's why it survives.

[SOLVED] Safe to continue?? or start again? please help

This is driving me nuts... I was on 5.1.1 and I am trying to get it rooted.
I'm following a guide which goes like this..
1. downgrade to kitkat 4.4 using flashtool
2. root 4.4
3. Install custom recovery
4. Flash 5.1.1 pre-rooted zip
I have had problem after problem and I think something may have screwed up along the way.
I finally managed to get kitkat installed using flashtool and a generic C6903 .108 ftf.
Problem 1... I used 'Easy Root tool' from xda to root kitkat... but it seemed to hang at the cleaning up' stage - is this a problem?
Problem 2... every time I restart my phone - kitkat asks what language etc. Whats that all about?
PROBLEM 3. The guide Im following says to install busybox after rooting kitkat.
I've tried 2 different busybox installers and both of them fail when trying to install bb.
QUESTION: Are these 3 problems linked and will it prevent me from continuing with the guide I am trying to follow??? i.e. do I need busybox to install XZ Dual Recovery and therefore a pre-rooted zip?
Root Checker basic says kitkat is rooted, as does the first busybox installer.
I'm taking a short break from this nightmare, so in the meentime if any of you chaps could advise me on whether or not its ok to continue or if I have fecked up the whole process, that would be great.
Thanks in advance
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Gamer4Life said:
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
Click to expand...
Click to collapse
Problem1... thank you, I'll try again
Problem2... Thanks. I thought It could be the lack of a SIM card and then I thought no! that can't be it lol... as usual - I was wrong ha
others... yeah mate, tried 2 different installers from play store - no joy with either.
Thanks for your help
xasbo said:
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Click to expand...
Click to collapse
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
thesweeney80 said:
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
Click to expand...
Click to collapse
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Gamer4Life said:
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
Click to expand...
Click to collapse
thanks for the tip mate but no joy see my reply to xasbo, cheers
xasbo said:
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Click to expand...
Click to collapse
Thanks mate. I was hoping Gamer4life might be right as there was no Supersu installed.
I installed supersu from play store no problem... but when I try to update binaries it says' update failed. Please reboot and try again.'. tried reboot but same story.
I guess I'll try 'easy root tool' again and then will give kingroot a bash if needbe.
One last pre-emptive question...
If I root kitkat using kingroot... should I replace kinguser with supersu before proceeding with XZDR and a pre-rooted zip or will kinguser be sufficient to continue.
Many thanks to you and everyone else who has tried to help me with this clusterf*ck,.. I appreciate it
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Gamer4Life said:
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
must have been a glitch in the matrix mate becuase its now working (Possibly thanks to your suggestion of installing Supersu?).
I reconnected to PC in order to give 'easy root tool' another crack at it.
As soon as I start install.bat It says checking if device is rooted AND I get a superuser request on my phone for adb.shell - Happy days!
I granted root access to adb shell and the root tool says Job Done. Root success etc.
So I disconnect and try to update su binaries and it worked first go!!!
*Touch wood* I think I'm now past the tricky part and it should be plain sailing from here on in. lol
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Gamer4Life said:
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
Correct, TowelRoot doesn't work for this version.
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
thesweeney80 said:
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Click to expand...
Click to collapse
:good: godspeed
@thesweeney80 you are welcome have fun
xasbo said:
:good: godspeed
Click to expand...
Click to collapse
Gamer4Life said:
@thesweeney80 you are welcome have fun
Click to expand...
Click to collapse
you fellas are the muts nuts.
All done, everything went smoothly once I got kitkat rooted properly.
MANY thanks for all your help.
Honestly I wouldnt even bother owning a smartphone if it wasnt for the peeps on XDA... F*cking awesome. THANKS :good: :highfive:
:good: awesome! don't forget to pay it forward sometime.

Need immediate help on king root problem,to all devs please take a look

Kingroot worked ,it rooted my Xperia ZR ,but the problem occurred when i tried to unroot my phone with the app ,it showed that it was unrooting ,old version so circle was spinning then it automatically closed the app ,but didnt uninstalled itself ,since i had read to reboot after unrooting i tried , but the app was there and suddenly after opening the app it was showing me my phone is rooted ,i tried several times to unroot but of no use but after checking wid root checker it showed my phone is not rooted but now that i want to root i have no option app shows rooted but not working its of latest version. Please i would praise each of u to find me a safe solution to root my phone again pleae guys im in middle of nowhere please .It can also b with the help of PC . Please
Try replacing Kingroot with SuperSU first with this method http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/
Then unroot using SuperSU.
It might work. I have done the first part but not the second.
Ugh.. King root sucks.. Horrible app and don't give full root..
Sent from my Xperia ZR using Tapatalk
hagar006 said:
Ugh.. King root sucks.. Horrible app and don't give full root..
Sent from my Xperia ZR using Tapatalk
Click to expand...
Click to collapse
Could you explain further please, particularly the 'don't give full root' part? I have used it and then immediately switched to SuperSU as explained in the link posted above by me but I have not yet come across any shortcomings.
So what's your problem now?
Sent from my Xperia ZR using Tapatalk
---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------
sling-shot said:
Could you explain further please, particularly the 'don't give full root' part? I have used it and then immediately switched to SuperSU as explained in the link posted above by me but I have not yet come across any shortcomings.
Click to expand...
Click to collapse
I'm so sorry..Hehe the post was meant for the author of this thread.. My sincere apologies..
Sent from my Xperia ZR using Tapatalk
---------- Post added at 02:04 PM ---------- Previous post was at 02:00 PM ----------
King root by itself is Crap.. Lucky someone made an app to make king root work..
Sent from my Xperia ZR using Tapatalk
sling-shot said:
Could you explain further please, particularly the 'don't give full root' part? I have used it and then immediately switched to SuperSU as explained in the link posted above by me but I have not yet come across any shortcomings.
Click to expand...
Click to collapse
After rooting with king root, if you reboot, then the root is gone. By normal methods, this should not happen, thats why the its often not encouraged.
ariftwister said:
After rooting with king root, if you reboot, then the root is gone. By normal methods, this should not happen, thats why the its often not encouraged.
Click to expand...
Click to collapse
OK. That might have been true. But I did not wait to find out.
Off topic :
Now however I have a problem. Even with the XZDualRecovery installed I am not getting full read write access to system partition. Any ideas? I am on stock ROM.
I will post this in the Ask Anything thread.
sling-shot said:
OK. That might have been true. But I did not wait to find out.
Off topic :
Now however I have a problem. Even with the XZDualRecovery installed I am not getting full read write access to system partition. Any ideas? I am on stock ROM.
I will post this in the Ask Anything thread.
Click to expand...
Click to collapse
So you did it by king root right? I think it may not have given you full root.
ariftwister said:
So you did it by king root right? I think it may not have given you full root.
Click to expand...
Click to collapse
I had created pre-rooted FTF strictly according to the instructions given. But that did not give me root. Why? Was the use of Philz Touch to flash the probable reason?
I am dreading going through the whole process again!
Is there a way to see if I have full root or not? Because Root Checker says I have root. Other super user activities run properly. Link2SD is able to integrate updates of system apps to /system successfully. If there is no read/write access to /system, then how is Link2SD able to do that?
Only in a file manager I am not able to modify /system files.
And funny thing is sometime back, I did have ability to modify /system. Don't know how I got it, don't know how I lost it.
sling-shot said:
I had created pre-rooted FTF strictly according to the instructions given. But that did not give me root. Why? Was the use of Philz Touch to flash the probable reason?
I am dreading going through the whole process again!
Is there a way to see if I have full root or not? Because Root Checker says I have root. Other super user activities run properly. Link2SD is able to integrate updates of system apps to /system successfully. If there is no read/write access to /system, then how is Link2SD able to do that?
Only in a file manager I am not able to modify /system files.
And funny thing is sometime back, I did have ability to modify /system. Don't know how I got it, don't know how I lost it.
Click to expand...
Click to collapse
I'm not king root user, but generally your file manager needs you to grant it root access
btw, just use supersu
cipetonk said:
I'm not king root user, but generally your file manager needs you to grant it root access
btw, just use supersu
Click to expand...
Click to collapse
At present I am using SuperSU. My file manager has super user permission.
sling-shot said:
I had created pre-rooted FTF strictly according to the instructions given. But that did not give me root. Why? Was the use of Philz Touch to flash the probable reason?
I am dreading going through the whole process again!
Is there a way to see if I have full root or not? Because Root Checker says I have root. Other super user activities run properly. Link2SD is able to integrate updates of system apps to /system successfully. If there is no read/write access to /system, then how is Link2SD able to do that?
Only in a file manager I am not able to modify /system files.
And funny thing is sometime back, I did have ability to modify /system. Don't know how I got it, don't know how I lost it.
Click to expand...
Click to collapse
You see KingRoot is the culprit here, I have gone through some threads, which also confirms that king root turns your system, write protected. Also not all apps need write access to system thats why other root apps works properly for you. Regarding Link2SD, they make symlinks to /system so not exactly writing to system.
I suggest you do a clean root by flashing by the correct method.
ariftwister said:
You see KingRoot is the culprit here, I have gone through some threads, which also confirms that king root turns your system, write protected. Also not all apps need write access to system thats why other root apps works properly for you. Regarding Link2SD, they make symlinks to /system so not exactly writing to system.
I suggest you do a clean root by flashing by the correct method.
Click to expand...
Click to collapse
I will try that again. Thanks.
sling-shot said:
I will try that again. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Official Thread of KingRoot. It also has links on how to successfully migrate to SuperSU. Hope It helps.
ariftwister said:
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Official Thread of KingRoot. It also has links on how to successfully migrate to SuperSU. Hope It helps.
Click to expand...
Click to collapse
I will go through it. May be the method I followed to get SuperSU was wrong.
ariftwister said:
You see KingRoot is the culprit here, I have gone through some threads, which also confirms that king root turns your system, write protected. Also not all apps need write access to system thats why other root apps works properly for you. Regarding Link2SD, they make symlinks to /system so not exactly writing to system.
I suggest you do a clean root by flashing by the correct method.
Click to expand...
Click to collapse
I do not understand what is going on here. I have flashed and lost root now.
In the previous version of Pre-Rooted Zip (which I had used) I had also included RICDefeat.zip. As all documents suggest that with XZDualRecovery it is not needed, this time I recreated a Pre-Rooted Zip from scratch using PRFCreator v1.1 (the latest available) with only the original FTF created using Flashtool, SuperSU 2.46.zip and XZDualRecovery 2.8.21.zip. PRFCreator worked seemingly without error and I got a nice final ZIP.
Then I booted into TWRP, flashed this ZIP. Everything seemed to go fine except I had an error at the end which said "unable to mount /system" (this was after SuperSU and XZDualRecovery were successfully flashed.)
On rebooting I find that I no longer have root. Does this mean that I cannot flash the firmware again?
.
sling-shot said:
I do not understand what is going on here. I have flashed and lost root now.
In the previous version of Pre-Rooted Zip (which I had used) I had also included RICDefeat.zip. As all documents suggest that with XZDualRecovery it is not needed, this time I recreated a Pre-Rooted Zip from scratch using PRFCreator v1.1 (the latest available) with only the original FTF created using Flashtool, SuperSU 2.46.zip and XZDualRecovery 2.8.21.zip. PRFCreator worked seemingly without error and I got a nice final ZIP.
Then I booted into TWRP, flashed this ZIP. Everything seemed to go fine except I had an error at the end which said "unable to mount /system" (this was after SuperSU and XZDualRecovery were successfully flashed.)
On rebooting I find that I no longer have root. Does this mean that I cannot flash the firmware again?
.
Click to expand...
Click to collapse
I'm sorry, but what are you trying to achieve here? I don't get it.
ariftwister said:
I'm sorry, but what are you trying to achieve here? I don't get it.
Click to expand...
Click to collapse
Full root with read write access to /system in stock firmware.
Flash Stock FTF thru Flashtool, Flash any custom kernel with recovery, flash SuperSu Zip via that recovery, now flash stock kernel then reboot. Done.
ariftwister said:
Flash Stock FTF thru Flashtool, Flash any custom kernel with recovery, flash SuperSu Zip via that recovery, now flash stock kernel then reboot. Done.
Click to expand...
Click to collapse
Apologies if I am testing your patience. Please tell me if so.
How about flashing an older kernel, rooting it using Towelroot, install recovery, flash SuperSU, flash current kernel?
I have not unlocked bootloader yet.

Difficulty Rooting Newest RUU

Hello everyone,
I'm having an issue - I wasn't able to flash the newest extracted firmware in the development section so I went ahead and just ran the full RUU. I've been running custom roms for years and I decided that maybe I just wanted to run stock rooted for a while so I unlocked my bootloader again, flashed the most recent TWRP and installed the most recent SuperSU zip.
Unfortunately it does not seem to have rooted my phone. SuperSU is indeed installed in the system folder and it prompts for root permission when I use root apps, but even when I grant permission the apps cannot obtain root access. What happens is it looks like they are going to get root access, the phone slows down a bit for a second, and then I get an error message from the app in question saying that either my phone isn't rooted or that root permission has been denied. If I open SuperSU, it lists all of my root apps with the green hashtag indicating that permission is granted.
Am I correct in assuming that installing SuperSU did not root my phone? If so, is there a way to root without installing a custom rom?
For clarification, this is all on the most recent RUU, software version 6.23.651..10, Lollipop 5.0.2
Thanks in advance.
Which version of SuperSU are you flashing?
Sloth said:
Which version of SuperSU are you flashing?
Click to expand...
Click to collapse
Well I'm a dolt, I was using v1.69 but now I see that is a very old version. Going to try 2.46 right now, thanks.
Edit: Same issue on 2.46 :/
For anyone still looking at this thread, I was able to achieve root by flashing the newest SuperSU, version 2.52 which is actually still in beta and therefore not offered if you go to the main portion of the SuperSU website.
SuperSU v2.65 is the current stable offering

Rooted, but no rooted apps work

Hello,
I recently used the toolkit to unlock and root my Sprint N6. Super user was installed and works. I installed Rootcheck after everything was complete and it verifies that the phone is rooted. I have installed Nexus 6 double tap to wake and LED control and both state that the phone is not rooted. Super user shows both those apps have super user access.
What am I missing? Thank you!!
itlbok333 said:
Hello,
I recently used the toolkit to unlock and root my Sprint N6. Super user was installed and works. I installed Rootcheck after everything was complete and it verifies that the phone is rooted. I have installed Nexus 6 double tap to wake and LED control and both state that the phone is not rooted. Super user shows both those apps have super user access.
What am I missing? Thank you!!
Click to expand...
Click to collapse
use the latest SuperSU
I am on version 2.65 and from what I can tell, that is the latest.
itlbok333 said:
I am on version 2.65 and from what I can tell, that is the latest.
Click to expand...
Click to collapse
you will also need to install busybox as well, as many root apps need it. install from the play store, then install from the app. search busybox in the play store, then choose stericsons version.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
and supersu 2.71 http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Thank you for the reply, Sorry I failed to mention I do have the move listed busy box installed as well. I have clicked on install from within the app as well. Still none of the mentioned root apps work, all say phone appears to not be rooted...
itlbok333 said:
Thank you for the reply, Sorry I failed to mention I do have the move listed busy box installed as well. I have clicked on install from within the app as well. Still none of the mentioned root apps work, all say phone appears to not be rooted...
Click to expand...
Click to collapse
try flashing the supersu 2.71 with twrp recovery, you should have root when you boot up. dont use the toolkit.
simms22,
I flashed version 2.71 through recovery, after reboot it was installed. Same "phone does not appear to be rooted" when trying to use the root apps... Root check still says phone is rooted. This is puzzling!
itlbok333 said:
simms22,
I flashed version 2.71 through recovery, after reboot it was installed. Same "phone does not appear to be rooted" when trying to use the root apps... Root check still says phone is rooted. This is puzzling!
Click to expand...
Click to collapse
very odd! tell me, which rom are you using? and did you wipe your data before rooting? if not, you might have to wipe your data then reflash your rom/gapps, and supersu.
I am stock rooted. Yes I wiped data and started from scratch after unlock and root.
itlbok333 said:
I am stock rooted. Yes I wiped data and started from scratch after unlock and root.
Click to expand...
Click to collapse
when you try to use a root app, so you get a little popup that asks you to give the app root? do yoh have the supersu app installed as well?
Yes SuperSU 2.71 flashed, the popup comes up and I grant access. Then each app says not rooted. Makes zero sense... The apps even show up in SuperSU app.
Yes, there is a popup and I have granted SU access to the above root apps, still no joy. I have SuperSU 2.71 flashed and installed, Root check verifies root.
I had this. The fix is to uninstall Busybox and reinstall into an alternative directory where it can be found. Mine appears to work fine in /su/bin, but if that doesn't work for you try the others (/system/xbin, /system/bin etc.)
It may not even need to be uninstalled - you could just try installing into the different directories until you find the one that the root apps are checking for root, though I'm not sure whether that would clutter your device with redundant binaries. I'm sure someone will be able to advise on that.

Categories

Resources