Unlock and Temper, can not root - One (M7) Q&A, Help & Troubleshooting

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.

Related

SuperSU

Hi
I have installed SuperSU to my phone
Will this stop me getting any updates OTA
Thanks
Lee
No,
But you may lose root after ota.
Sent from my GT-N7000 using xda premium
Well, I installed SuperSU by flashing CWM-SuperSU-v.0.87.zip in CWM (which was first temporarily flashed using CWM.zip as an upgrade in the stock recovery)...
Here is the link for both zip files that I used to root:
http://downloadandroidrom.com/file/GalaxyNote/rooting/ICS
That rooted the phone fine while keeping everything stock and everything appears to work great, but now the OTA is failing...
So I'm running, thus rooted, stock 4.0.3 ICS and tried updating to 4.0.4 via OTA. Any ideas how to fix the failing OTA update without flashing a clean stock ROM via ODIN?
voxano said:
Well, I installed SuperSU by flashing CWM-SuperSU-v.0.87.zip in CWM (which was first temporarily flashed using CWM.zip as an upgrade in the stock recovery)...
That rooted the phone fine while keeping everything stock and everything appears to work great, but now the OTA is failing...
So I'm running, thus rooted, stock 4.0.3 ICS and tried updating to 4.0.4 via OTA. Any ideas how to fix the failing OTA update without flashing a clean stock ROM via ODIN?
Click to expand...
Click to collapse
Unroot your phone using Busybox Uninstaller (If you have installed busybox from Dr.Ketan thread only) from Dr.Ketan Thread. And Try Again.
Thanks for the suggestion, but the rooting zip that I mentioned didn't come from the Dr's thread, so his unrooting zip won't help here...
I updated my post above with the link to the zip file that I used for the rooting.
Looks like installing SuperSU this way did something to the /system that causes the OTA to fail... Any ideas on how to work around this?
open super SU - setting - Full unroot
Thanks, but I already tried that: SuperSU uninstalls, but OTA still fails at apparently the same place. I installed it back from the market and tried the full unroot again, with the same result... Any other ideas?
Before rooting, all the previous OTA updates worked flawlessly.
Did you flash a custom kernel, e.g. franco (as also in the webpage)? It may be the issue.
I also tried to unroot using the Voodoo OTA RootKeeper, but that didn't help me either.
If you can download 550MB data, then just flash using PC odin.
kopitalk said:
Did you flash a custom kernel, e.g. franco (as also in the webpage)? It may be the issue.
Click to expand...
Click to collapse
No. Only stock kernels, regularly updated OTA
dr.ketan said:
If you can download 550MB data, then just flash using PC odin.
Click to expand...
Click to collapse
Yeah, looks like I will have to...
I just thought that installing only the SuperSU was such a minimalistic way to root and would be easy to unroot since the app itself provides that feature.
The only other thing that was done to this phone was to make Titanium backups of several apps, but I don't see how that could affect anything either.
Anybody else ran into this exact problem?
Easy Unrooting?
dr.ketan, is there a "SUPERSU-Busybox-UNinstaller.zip" corresponding to the SUPERSU-Busybox-Installer.zip from your original thread:
http://forum.xda-developers.com/showthread.php?t=1424997
?
I see a set of attached files at the bottom of this post:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
, but the insides of the SU-Busybox-Installer.zip are not the same as SUPERSU-Busybox-Installer.zip,
so I assume the SU-Uninstaller-signed.zip will not work. Or will it?
Thanks.
You can try the uninstaller. If you look at the script basically it will remove superuser.apk and su binary. Since superuser (by chainsDD) and superSU are using the same apk name (superuser.apk), the effect will be the same. However I'm not sure how to remove busybox other than by flashing stock kernel.
voxano said:
dr.ketan, is there a "SUPERSU-Busybox-UNinstaller.zip" corresponding to the SUPERSU-Busybox-Installer.zip from your original thread:
http://forum.xda-developers.com/showthread.php?t=1424997
?
I see a set of attached files at the bottom of this post:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
, but the insides of the SU-Busybox-Installer.zip are not the same as SUPERSU-Busybox-Installer.zip,
so I assume the SU-Uninstaller-signed.zip will not work. Or will it?
Thanks.
Click to expand...
Click to collapse
This is for SU Busybox installer, not for SuperSU busybox installer.
If you have rooted with same file, you can see attached with that uninstaller, then only it works
May it be work, but chances of leftover there.
Not so easy UNrooting...
kopitalk said:
You can try the uninstaller. If you look at the script basically it will remove superuser.apk and su binary. Since superuser (by chainsDD) and superSU are using the same apk name (superuser.apk), the effect will be the same. However I'm not sure how to remove busybox other than by flashing stock kernel.
Click to expand...
Click to collapse
Thanks for the input, kopitalk. Sounds like flashing stock kernel would be the only certain way to unroot in this case...
---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------
dr.ketan said:
This is for SU Busybox installer, not for SuperSU busybox installer.
If you have rooted with same file, you can see attached with that uninstaller, then only it works
May it be work, but chances of leftover there.
Click to expand...
Click to collapse
So there is NO "SUPERSU-Busybox-UNinstaller.zip" corresponding to the SUPERSU-Busybox-Installer.zip from your original thread, right?
Moot
http://forum.xda-developers.com/showthread.php?t=1810954
http://forum.xda-developers.com/showthread.php?t=1329360

No root access for sense lolipop

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.

Looking for root for tab s2

Wondering when xda will have section for s2???? Also hoping a dev can come up with a root method. I can test as I have a sm-t810.
suzook said:
Wondering when xda will have section for s2???? Also hoping a dev can come up with a root method. I can test as I have a sm-t810.
Click to expand...
Click to collapse
Get in line behind the tab a.
OK have you tried the kingroot exploit in this section first?
http://forum.xda-developers.com/showthread.php?t=3158198
ashyx said:
Get in line behind the tab a.
OK have you tried the kingroot exploit in this section first?
http://forum.xda-developers.com/showthread.php?t=3158198
Click to expand...
Click to collapse
King root does not work. Thanks
suzook said:
King root does not work. Thanks
Click to expand...
Click to collapse
Usually takes a few goes, have you tried previous versions?
ashyx said:
Usually takes a few goes, have you tried previous versions?
Click to expand...
Click to collapse
Tried about 50 times, different versions..? No go....I don't care about knox. Was hoping for a cfroot method.
suzook said:
Tried about 50 times, different versions..? No go....I don't care about knox. Was hoping for a cfroot method.
Click to expand...
Click to collapse
Watch this space
ashyx said:
Watch this space
Click to expand...
Click to collapse
I'm watching!
suzook said:
I'm watching!
Click to expand...
Click to collapse
Test 1.
please be as specific as possible if it fails, screenshots or vids are best.
smt810_cf-autoroot_v1
sm-t810_stock_recovery
ashyx said:
Test 1.
please be as specific as possible if it fails, screenshots or vids are best.
smt810_cf-autoroot_v1
sm-t810_stock_recovery
Click to expand...
Click to collapse
I flashed 1st file, all went well, but when i install supersu app, it says it needs to update binaries, but it fails
suzook said:
I flashed 1st file, all went well, but when i install supersu app, it says it needs to update binaries, but it fails
Click to expand...
Click to collapse
looks like the superuser app in system app doesnt have correc permisions???
suzook said:
looks like the superuser app in system app doesnt have correc permisions???
Click to expand...
Click to collapse
Shouldn't need to install the superuser app. It should already be installed.
Root again and watch the process. Particularly watch to see if the system and cache partition successfully mount or fail.
This is why I need screen shots and vids.
ashyx said:
Shouldn't need to install the superuser app. It should already be installed.
Root again and watch the process. Particularly watch to see if the system and cache partition successfully mount or fail.
This is why I need screen shots and vids.
Click to expand...
Click to collapse
OK, i will try again with pics.....they do mount, but the superuser app in /sytem/app doesnt have proper permisions...that make sense?
Here it is
suzook said:
OK, i will try again with pics.....they do mount, but the superuser app in /sytem/app doesnt have proper permisions...that make sense?
Click to expand...
Click to collapse
Can you post a screen shot of root validator so I can see what got installed.
If the partitions mount as you say then there may be a problem with the supersu script.
You should not have to install any superuser app or update the binary as the exploit uses the latest binaries.
I will be turning in for tonight so if you can get the screen shots of the process where it mounts the partitions and where it installs the supersu files and a screen shot from root validator that will give me something to look at tomorrow.
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
suzook said:
Here it is
Click to expand...
Click to collapse
Ok the supersu script didn't run. I will fix that tomorrow.
Good night.
ashyx said:
Can you post a screen shot of root validator so I can see what got installed.
If the partitions mount as you say then there may be a problem with the supersu script.
You should not have to install any superuser app or update the binary as the exploit uses the latest binaries.
I will be turning in for tonight so if you can get the screen shots of the process where it mounts the partitions and where it installs the supersu files and a screen shot from root validator that will give me something to look at tomorrow.
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
Ok the supersu script didn't run. I will fix that tomorrow.
Good night.
Click to expand...
Click to collapse
Great, thanks. Have a great night.
Hi. Any autoroot for SM-T715Y? Thank you.
looking Root for SM-T710 8"
ashyx said:
Watch this space
Click to expand...
Click to collapse
Hello Ashyx,
I am looking for auto Root for SM-T710 as well....
i am checking XDA almost everyday to see if they opened section for Tab S2...
Maybe you are the 1st hero that can make the S2 rooted....
thanks
If and when I get root working for the sm-t810 I will look at root for you guys.
suzook said:
Great, thanks. Have a great night.
Click to expand...
Click to collapse
Test 2.
Watch for the supersu script running in the process. You should see the supersu installer script run after the partitions get mounted.
smt810_cf-autoroot_v2
Check with root validator for root.
ashyx said:
Test 2.
Watch for the supersu script running in the process. You should see the supersu installer script run after the partitions get mounted.
smt810_cf-autoroot_v2
Check with root validator for root.
Click to expand...
Click to collapse
nope, same as build 1. no superuser app, script does not run. Will be away from a computer in a half hour till later on today, won't be able to test for about 11 hrs from now. Thanks, I'm sure we(you) will get it.

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.

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