Thunderbolt: after rooting, I can run root manager, flash thunderbolt cwm, boot into cwm and backup/etc. However, when I try to run TiBackup or Screen Resolution, or even terminal/su - access denied, device not rooted.
Anyone else experiencing this?
EDIT: read in another thread (search was not working when I posted this originally) to go to problems in TiBackup, then update busybox...
Go into rom manager. Download SU and flash it in clockwork. Should fix ya.
Sent from my ADR6400L using XDA Premium App
ethanwinkley said:
Thunderbolt: after rooting, I can run root manager, flash thunderbolt cwm, boot into cwm and backup/etc. However, when I try to run TiBackup or Screen Resolution, or even terminal/su - access denied, device not rooted.
Anyone else experiencing this?
EDIT: read in another thread (search was not working when I posted this originally) to go to problems in TiBackup, then update busybox...
Click to expand...
Click to collapse
You could search market for busybox and install busybox and install busybox 1.18.3 then try
Just click Problems? in the bottom right of Titanium and let it install busybox for you. I was able to do that and restore all my apps.
Seems like you solved it for you, but for future reference for others, if you're having issues with Titanium only, it could be a the busybox problem, but if other root apps give issues (like Root Explorer can't mount /system as r/w), then the issue is with su or SuperUser not being installed properly.
I had to reboot twice after rooting before SuperUser apk got the notification requests to allow Titanium and RE to get su rights. After that, no problems.
In a nutshell, if you're not getting the SuperUser pop-up request on apps the first time you run them, your su isn't working right yet.
Delete please.
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Thats OK said:
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
Click to expand...
Click to collapse
I finally managed to get back to ICS, then ran the rooting procedure. However, it always failed when it came to testing Superuser. Tried it four or five times. Then I tried installing the other Superuser apks. Every last one of them said the su binary needed to be updated, but every one of them failed to do so.
That's where I am right now. Unrooted ICS.
buhohitr said:
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Click to expand...
Click to collapse
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
Is there a previous version of SU installed or leftover?
See if it's still in running apps under settings.
If you're on ICS I'd try a factory reset and go from there.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
buhohitr said:
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
Click to expand...
Click to collapse
I did launch the app and it did tell me the su binary needed to be updated. So I told it to go ahead with a normal install. Installation failed. Also tried the SU update fixer from the play store, and that failed as well.
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Lim Wee Huat said:
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Click to expand...
Click to collapse
Yes, I would agree, this is the only way left for what to do next!
buhohitr said:
Yes, I would agree, this is the only way left for what to do next!
Click to expand...
Click to collapse
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
iCurmudgeon said:
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
Click to expand...
Click to collapse
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
buhohitr said:
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
Click to expand...
Click to collapse
Well, I tried, but when I rebooted with the power and vol-down buttons, I only got an "Android" icon and something else to its left, no RCK at all. The pad rebooted eventually and I was stunned when Superuser started working! I immediately ran Voodoo OTA Rootkeeper, then let the tablet update to 4.1.1. I then ran SuperSU and it said the su binary needed to be updated. I told it to do a normal install. "Installation failed." Said bad words in several languages and tried again. Update of SU binary succeeded.
Restored root. Success. Now restoring last Titanium backup backup.
I'm still worried, though. The symptoms would seem to point to flaky or at least unstable flash memory. What do you think?
I gotta decide whether to get a Samsung Galaxy Note tablet (7-inch) or the updated Nexus 7 tablet when they come out. I don't trust this TF700 anymore..
mudge
I have the same problem, but didn't downgrade!
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
IT Wannabe said:
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
Click to expand...
Click to collapse
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
buhohitr said:
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
Click to expand...
Click to collapse
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
IT Wannabe said:
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
Click to expand...
Click to collapse
Since motochopper has the ablility to root JB, you should remove superuser root (open supersuser and select remove root then reboot), then re root using motochopper if needed.
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
IT Wannabe said:
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
Click to expand...
Click to collapse
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
sgtrwe said:
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
Click to expand...
Click to collapse
Oh, sure!
After a search through my PATH, I've found that 'su' no longer lives in /system/bin, but in /system/xbin, with busybox and dexdump and every POSIX command you can think of symlinked to busybox. It is owned by root:root.
I guess that's just the way the JB root method does it...
i just rooted my phone using motochopper. and am trying to use ltm launcher. every time i open it, it says root context not able to get permission.
and then when i go to the superuser, it says the superuser binary (su) must be updated. and it ask if i want to recovery install or just install, but none of it works. i even downloaded supersu from chainfire and it says there is no su binary installed. so i need help getting root permission to apps so i can get lmt launcher to work.
i read an old post with they guy with the same problem and u told him to flash it with something but i am not really sure how to do that. so if u can kind of explain how to do that.
thanks
wrestling103 said:
i just rooted my phone using motochopper. and am trying to use ltm launcher. every time i open it, it says root context not able to get permission.
and then when i go to the superuser, it says the superuser binary (su) must be updated. and it ask if i want to recovery install or just install, but none of it works. i even downloaded supersu from chainfire and it says there is no su binary installed. so i need help getting root permission to apps so i can get lmt launcher to work.
i read an old post with they guy with the same problem and u told him to flash it with something but i am not really sure how to do that. so if u can kind of explain how to do that.
thanks
Click to expand...
Click to collapse
Just installing the super user app from play store doesn't root your phone.
SuperUser app only manages root permissions. It itself does not root the phone. Head over to your xda section and read there how to root your phone .
omerjerk said:
Just installing the super user app from play store doesn't root your phone.
SuperUser app only manages root permissions. It itself does not root the phone. Head over to your xda section and read there how to root your phone .
Click to expand...
Click to collapse
Like I've said I have already rooted my phone using motochopper. That's not the problem. The problem is not getting super user updated
wrestling103 said:
Like I've said I have already rooted my phone using motochopper. That's not the problem. The problem is not getting super user updated
Click to expand...
Click to collapse
Did you follow the official rooting procedure as given in your xda forum? Because if your phone is rooted then you won't face any problem related to SuperUser app and updating binary and all these stuffs.
I've had the same problem as listed above.
Hello I have an unusual problem. I am modifying the ROM for my Rockchip device (rk3066). I want the firmware image to flash already rooted. I have installed busy box, su binary, and Superuser.apk. When I flash the ROM then use Rootchecker, it says I have root access. However, when I use an app that requires root it cannot gain root access. Can anyone explain to me what is going wrong?
Please be very basic in any explanation as I am a super noob trying to learn.
Thanks in advance for any help given. It will be very appreciated.
Melikey said:
Hello I have an unusual problem. I am modifying the ROM for my Rockchip device (rk3066). I want the firmware image to flash already rooted. I have installed busy box, su binary, and Superuser.apk. When I flash the ROM then use Rootchecker, it says I have root access. However, when I use an app that requires root it cannot gain root access. Can anyone explain to me what is going wrong?
Please be very basic in any explanation as I am a super noob trying to learn.
Thanks in advance for any help given. It will be very appreciated.
Click to expand...
Click to collapse
There might be something wrong with the superuser app itself. Try using SuperSU.
http://forum.xda-developers.com/showthread.php?t=1538053
Does it work?
Basically you need to tick "prompt", if you had ticked "deny for all" , superuser will not prompt you for answer when an app needs root, so have it on "prompt" in super user settings, If superuser or SU icon is in apps drawer , open it and check its settings menu.
How to get Root Access?
a) Update SU Binaries, reboot
b) Check Development Option for Root Access settings or Performance settings for Superuser Settings
c) Flash Super Su Zip in Recovery
Problems that may arise in the future : Read How To SU
Check this out! Links to useful Guides and " Banned " Documentaries
install supersu
So I tried updating the su binary from the superuser app. It says it installed OK but then says it can't gain root access.
I also tried using Supersu app. It says that there is no su binary installed. But, it definitely is there.
I also tried simple root checker. It verified that busy box is installed.
If you have a recovery installed unroot and reflash the binary n app
Sent from my WT19i using xda app-developers app
I appreciate all the input, but I think this is going off point. I have no trouble routing my tablet with the told that are out there. I can't build it into a complete ROM. I am trying to build a custom ROM
with the root built in.
Sent from my XT912 using Tapatalk
Root not routing / tools not told
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
TraderJack said:
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
Click to expand...
Click to collapse
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
S1L3nTShaDoWz said:
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
Click to expand...
Click to collapse
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
TraderJack said:
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
Click to expand...
Click to collapse
Yeah on the kernel my bad, didn't see it had a normal one for non 2.23 firmware users lol, if you don't wanna use that kernel you can always use one of the other ones, maybe Faux's or Evolutionmods kernel. I actually currently use Evolutions kernel and it's quite nice. Also that ROM will work fine I believe, quite sure 1.55 is the latest OTA and if not it doesn't really matter. All though as some people have stated on your previous thread (i think?) you might as well use an optimized stock ROM such as CleanROM or ARHD (Android Revolution HD 8.1), all it is is a stock ROM thats been optimized for better performance and maybe has some tweaks to make it better. To be clear on the ARHD ROM, I stated the version because any higher version than that is for 4.4.3 which we currently don't have the firmware for.
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Glad you got your issue solved!
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
TraderJack said:
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
Click to expand...
Click to collapse
Can't say I ever used that option, it probably just didn't flash it correctly. You may want to post the problem in the recovery thread so they know about it.
In theory it should've worked the same way as flashing the zip. The only thing I could think of is how old the binary was or the location of the flash was incorrect.
Sent from my HTC6525LVW using Tapatalk