[Q] Did Perm Root - Only got Temp Root? - AT&T HTC One (M8)

Hey guys.
Used the HTC All in one toolkit and rooted, installed TWRP, and a new rom on my device. I want to S-off but since my phone is brand new it doesnt seem to work. (This will never work on your phone stop trying - error with firewater) I used the Perm Root method on the All-in-one toolkit but everytime i reboot my device i lose root and need to wait for it to come back up (2-3 Min after bootup). This means its not permanent correct? Maybe this is why firewater is not working?
Another really weird thing, when i reboot with adb reboot, the phone takes literally like 10-15 minutes to power on. What is that about?
TWRP seems as it is permanent, and on the bootloader it says tampered and unlocked with s-on.
Im kinda confused here, I came from a nexus 4 so im not used to things not working.
SOOOOOOO..
(Q) Can someone give me an overview of what is going on so i can go in the right direction? should i unroot to stock and try again? Why would it give me a TEMP root if i used the permanent root method of flashing SuperSU in recovery? If i switch roms, is the perm root method removed?
Thanks in advance guys!

If you flashed a custom ROM, they are already rooted. So if you also flashed SuperSU in addition, you might have some conflict, such as a built-in SU conflicting with the SuperSU you flashed.
I would re-flash the ROM (you can probably "dirty" flash and keep user data, just wipe cache and Dalvik), don't flash any separate SuperSU or SU, and see if the problem persists.
The long boot problem is a known issue if you flashed a 2.xx based ROM (Android 4.4.3) but your phone is still on older firmware (hboot, radio, etc.). You might also experience some other significant bugs like broken WiFi or Bluetooth.
Firewater s-off has been patched for some time now, but Sunshine S-off should work (but costs $25).
You will need s-off to manually update firmware. But the alternative is to return to stock ROM and recovery, accept your latest OTA, which will install the new firmware.

redpoint73 said:
If you flashed a custom ROM, they are already rooted. So if you also flashed SuperSU in addition, you might have some conflict, such as a built-in SU conflicting with the SuperSU you flashed.
I would re-flash the ROM (you can probably "dirty" flash and keep user data, just wipe cache and Dalvik), don't flash any separate SuperSU or SU, and see if the problem persists.
The long boot problem is a known issue if you flashed a 2.xx based ROM (Android 4.4.3) but your phone is still on older firmware (hboot, radio, etc.). You might also experience some other significant bugs like broken WiFi or Bluetooth.
Firewater s-off has been patched for some time now, but Sunshine S-off should work (but costs $25).
You will need s-off to manually update firmware. But the alternative is to return to stock ROM and recovery, accept your latest OTA, which will install the new firmware.
Click to expand...
Click to collapse
Thanks for the speedy response.
I flashed the insertcoin rom. It was supposed to root with that (Chose SuperSU on aroma install) but no SuperSU was installed. It seemed like insert coin was a little buggy. So i installed the SuperSU with perm root option on all-in-one toolkit. And SuperSU was giving me errors of not being supported and need to update through recovery, it wasnt updating. Wiped, Reflashed insertcoin, this time SuperSU installed on the device, tried s-off with firewater and didnt work. Then i did a full wipe again.
This time I flashed M8Rx.v2 and seems like a solid running rom - Minus the fact that Wifi is broken. (It said use a specific kernel if on 1.58 firmware, but my phone came with 2.xx, maybe it went down to 1.58 with insertcoin) Came with SuperSU however now it doesn't have permanent root (I have not done perm root on all-in-one after wiping and flashing M8Rx.v2).
I have read that perm root may not work unless s-off. Is this true?
Also - Worth noting that when i was stock, there was no OTA available. i was on build 2.xx and now with M8rx.v2 im on build 1.58.502.1.

H0rn3t920 said:
I have read that perm root may not work unless s-off. Is this true?
Click to expand...
Click to collapse
No, that is completely false.
How are you determining root or no root?
For Insertcoin, you won't see SuperSU or SU in the app drawer. Its in the Settings>InsertCoin. If not having SuperSU in the app drawer is solely what led you to believe you weren't rooted, I think you may have just been confused about it and were rooted all along.
I don't know about M8Rx, as I've never used it.

redpoint73 said:
No, that is completely false.
How are you determining root or no root?
For Insertcoin, you won't see SuperSU or SU in the app drawer. Its in the Settings>InsertCoin. If not having SuperSU in the app drawer is solely what led you to believe you weren't rooted, I think you may have just been confused about it and were rooted all along.
I don't know about M8Rx, as I've never used it.
Click to expand...
Click to collapse
That was part of it, the other part was when using firewater, i would get no superuser prompts. That is a good piece of info though, thanks!
So how would i go about doing a permanent root and s-off? should i go back to stock and use the 25$ method or should i keep my rom and custom recovery and then do it? Mainly im curious about the permanent root as i have done what i should have for a permanent root and its not permanent. So I dont really understand what to do here.

H0rn3t920 said:
That was part of it, the other part was when using firewater, i would get no superuser prompts. That is a good piece of info though, thanks!
So how would i go about doing a permanent root and s-off? should i go back to stock and use the 25$ method or should i keep my rom and custom recovery and then do it?
Click to expand...
Click to collapse
I think you are perm rooted already. Not getting SU prompt in firewater is likely a different issue.
Make sure debugging is activated. Also, firewater doesn't work with some custom ROMs, not sure about InsertCoin. But you might try a different ROM.
Firewater was patched some time ago, and doesn't work for most M8's at this point. As your device was updated to the 2.xx software, firewater likely won't work. But you should at least get to the "whelp" error message from firewater before concluding that it won't work on your device.

redpoint73 said:
I think you are perm rooted already. Not getting SU prompt in firewater is likely a different issue.
Make sure debugging is activated. Also, firewater doesn't work with some custom ROMs, not sure about InsertCoin. But you might try a different ROM.
Firewater was patched some time ago, and doesn't work for most M8's at this point. As your device was updated to the 2.xx software, firewater likely won't work. But you should at least get to the "whelp" error message from firewater before concluding that it won't work on your device.
Click to expand...
Click to collapse
I did get the whelp message...
My confusion here is if i am perm rooted, why do i lose root on a reboot? All my xposed modules stop working, says version 58 has been installed but only found version 47. I hit install/update, superuser permissions granted and it immedietely says version 58 is found. I need to then soft reboot in order for all modules to activate.
Now its saying SuperSU is having issues updating the binaries. I flash the binaries in TWRP and then after the phone boots, it says the same thing again, to update binaries. I want to get into SuperSU to unroot and then flash SuperSU again in TWRP to see if that works, but i can not get around the update binaries screen. If i hit cancel, app closes.
EDIT: So i updated binaries, and i didnt get the update notification anymore. Got into the app, unrooted, then reinstalled supersu from TWRP, and then installed SuperSU from app store. Asked to update binaries, did it. Enabled SU at boot in SuperSU Settings. Still exactly the same. Even though xposed is granted superuser permissions, i need to go into the app and tinker with it before its auto granted and version 58 of xposed is seen.
I also tried in SuperSU Settings to write to system but it doesnt seem to work.
What am i missing here!?

Did you try to flash the ROM again, and this time not do anything additional to root (aside from the AROMA selection of SU/SuperSU), like I suggested back in Post #2?
I think something with the toolkit or flashing SU otherwise is messing with the built-in root.
I'm on InsertCoin, and have never had any issues with root.

redpoint73 said:
Did you try to flash the ROM again, and this time not do anything additional to root (aside from the AROMA selection of SU/SuperSU), like I suggested back in Post #2?
I think something with the toolkit or flashing SU otherwise is messing with the built-in root.
I'm on InsertCoin, and have never had any issues with root.
Click to expand...
Click to collapse
Thats how i did it to begin with on all my roms that i flashed. Only went and flashed the SuperSU after I realized that the rom itself didnt give a permanent root.

So I wiped the phone fully like 4-5 times before flashing M8Rx.v2 and everything is working super smooth and beautiful now. Thank you to redpoint73 and his help!

H0rn3t920 said:
Thats how i did it to begin with on all my roms that i flashed. Only went and flashed the SuperSU after I realized that the rom itself didnt give a permanent root.
Click to expand...
Click to collapse
Odd, all I can think is that the AROMA option to select SU/SuperSU is a little buggy.
Looks like persistence (or at least vigorous wiping) was the key!

Related

Randomly Lost Root in CleanROM 1.4

Ok I'm currently running CleanROM DE 1.4 with Gingerbread firmware.
I was enjoying root priviledges for a while but then Superuser started acting up.
Apps that I had previously granted root access still worked with root priviledges, but I couldn't grant root access to new apps.
In addition, the "app has been granted root access" popup no longer showed up for the apps that already had superuser, and the allow/deny dialog no longer shows up for new apps.
Looking at the log in Superuser, it seems that no apps have been granted root access for about 2 weeks, even though apps I already granted Superuser still worked.
I then went to recovery and reinstalled the su files, but that just removed Superuser so now I don't have root at all.
Is there anyway to fix this without reinstalling the ROM? I'd rather not do that unless I have to.
Thanks
Edit: I have one hypothesis for why this happened, and a possible fix.
A while ago, I flashed SlimROM but a lot of things weren't working.
I tried flashing the ROM and Kernel multiple times, but it still had problems.
I didn't flash the Old Firmware Patch, so now I think that was the problem.
Then I nandroid restored back to CleanROM (also flashed boot.img because I'm S-ON), but I didn't flash the Old Firmware Patch again.
So could not flashing the Old Firmware Patch be the cause of the problem?
Flash the old firmware patch. Then flash super user & su in Amon Ra developer options (or advanced options I can't remember which it's called)
AshtonTS said:
Flash the old firmware patch. Then flash super user & su in Amon Ra developer options (or advanced options I can't remember which it's called)
Click to expand...
Click to collapse
I tried that, but it didn't fix anything.
I ended up just installing SlimROM.
(Need to change my sig now)
wlmeng11 said:
I tried that, but it didn't fix anything.
I ended up just installing SlimROM.
(Need to change my sig now)
Click to expand...
Click to collapse
Edit: SlimROM was too slim.
Sent from my viperRez

[Q] Unrooting issues? (screw up while previous unrooting?)

Greetings,
I know the easy answer to this is going to be to flash a new rom, but if I wanted to do that I would have already. I'd rather find and repair the source of the issue and learn from it.
That being said, shortly after getting my tbolt (when they were first released) I used the revolutionary root and added in VPN software for work. Being unaware that OTA updates hadn't been blocked during the rooting, the phone took an update and went into a death-boot-loop. I found a clean updated OTA rom, flashed and unrooted the phone as the VPN software didn't work well for what I intended anyway.
Great, now the phone is all back to stock (or so I thought).. After a while, another OTA update came down, it asked to update, I allowed, and it said update failed.. Repeat ad nauseum for the next several weeks. Since I was happy with the way the phone was operating, I didn't care if it got the updates or not.
So last week, I decided that since the phone is out of warranty anyway, I might as well root and get rid of some of the bloat, and while I'm at it, get rid of the damn nag screen every tine I hook it to a computer. Searched around, found thunderbolt tool 1.0.1, downed it and tried it out, and it proceeded to say unable to lock my phone.
After a little screwing around, the "update status" on the phone itself reports ROM Version: 2.11.605.9, while the tool was getting a response of 2.11.605.5, so it was using the wrong method to get into the phone. So I edited the batch file to use the .9 method no matter what it reported back, and it proceeded to root, add the recovery, and superuser.
Ahhh, life is good, the phone is rooted again, time to start doing my own customization.
Except that after a couple reboots, everything loses the root rights.
Running titanium backup says "asking for root rights" and then "titanium has been granted superuser permissions" but it just hangs there at the "asking for root rights" screen.
Wireless tether similar story... Start the app and it says "press to start tethering" and touching the screen gets "wireless tethering has been granted superuser permissions", then hangs at "please wait while starting".
Won't do anything that requires root, unless I run the tool again and select "S-off but no root", and it will go through a procedure and root will work again for a while.
Also, as I'm typing this, I discovered that it doesn't necessarily require rebooting to lose root. I had root working last night, but when I picked up the phone to get the proper messages to type, it is not showing root again, and it hasn't been rebooted since root was working.
Thoughts on how to repair this without flashing a rom?
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like OTA RootKeeper to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Milimbar said:
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like -edit- to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
Click to expand...
Click to collapse
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
I'll check out the rootkeeper.
disconnecktie said:
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Never took the .19 update, and both the tool and phone report as .05 now. (if I remember correctly the .09 reverts back to .05 to get in)
damm315er said:
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
Click to expand...
Click to collapse
What recovery are you using?
I only use 4ext and would recommend that.
The fix permissions will take up to 5 min and may not help your particular issue, but shouldn't hurt to try.
If 4ext - Boot into recovery, select tools then select fix permissions.
If CWM I think its in the advanced menu.
and If TWRP I think it is in the advanced menu again.
Good luck and listen to the others here, they go out of their way to help people a lot
Ok earlier I misread your post. I thought it said 605.19. Still though something you're doing is causing you to only get temp root. Reread the op of the allinone tool and make sure you meet the requirements before you start it. That away when you run it this time you are in the best possible situation for it to work. Trter is very helpful and if you post your issue in his thread he will probably assist you with anything you need.
Sent from my ADR6400L using Tapatalk 2
I remember having a similar problem about 6-7 months ago.
I would randomly loose root, though not as often as he is describing.
In my case it was a combination of an outdated root method and a flawed ROM.
If everything he is using is current, including the ROM, he shouldn't have an issue.
If it were me I would flash Santod's stock deodexed ROM and be done with it.
It is the stock ROM with nothing changed except it is prerooted.
I understand that you would like to "fix" this issue without flashing a ROM, however the ROM itself could be the problem. this solution is the simplest I can think of.
Using everything from the thunderbolt toolkit, so yes, 4ext.
Found and ran the fix permissions, ran for 15 minutes before it finished so we'll see how it goes.
I get what you're saying about the rom being screwed up, and am starting to think my only choice is to reflash it, so I'll start looking into a new rom.. That being said I'm still pursuing fixing this until I find a rom that serves my purpose.
Is there a good stable ICS for thunderbolt, pre-loaded with root and good battery life?
Yea the one in the post above yours. If you want something a that is faster and has better battery than it then head over to infectedrom.com and check out all the different options santod has made.
Sent from my ADR6400L using Tapatalk 2

[Q] Randomly lost root access

I recently got s-off, updated from 1.15 to 2.06, installed abp and also flashed a no ads zip file for good measure because some ads would still get through. Everything was going great until the phone randomly froze. I held down the power button and rebooted into recovery and cleared my cache and dalvik cache, thinking that may have been the problem. Upon rebooting after that, I come to find out I've lost my root access. This is so weird. I am still s-off and have the 2222222 confirmation shown when I am in the bootloader, I still have super user installed, but when I run an app that needs root, such as adaway, it says I don't have root. I downloaded root checker and it confirmed that I didn't have root. I don't understand how this could have happened. Is there anyway to regain root? I have been having the worst luck with this phone :\
terrorist96 said:
I recently got s-off, updated from 1.15 to 2.06, installed abp and also flashed a no ads zip file for good measure because some ads would still get through. Everything was going great until the phone randomly froze. I held down the power button and rebooted into recovery and cleared my cache and dalvik cache, thinking that may have been the problem. Upon rebooting after that, I come to find out I've lost my root access. This is so weird. I am still s-off and have the 2222222 confirmation shown when I am in the bootloader, I still have super user installed, but when I run an app that needs root, such as adaway, it says I don't have root. I downloaded root checker and it confirmed that I didn't have root. I don't understand how this could have happened. Is there anyway to regain root? I have been having the worst luck with this phone :\
Click to expand...
Click to collapse
Send me a PM if you want me to help you out. You need to install a custom recovery and use that to install a rooted rom and kernel. It can be a stock rooted rom. Or mostly stock however you want to do it, I'll help you set it up and teach you some things along the way.
I can teach you all kinds of things via team viewer, it wont take long and it's a necessity for having a rooted phone in my opinion. I know it can be frustrating and over whelming but it will get better I promise.
Oh and also you don't need to worry about losing s off. It's at a much lower level than anything you've mentioned touching. So it will always be there regardless because you definitely don't want to be messing with hboots or s off type stuff.
Hey, I PMed you.
Try uninstalling superuser and installing either supersu or the other superuser.
Sent from my HTC6435LVW using xda app-developers app
I can't uninstall my Superuser unless I use Titanium Backup. I tried installing SuperSU (while still having my original Superuser installed) and the SuperSU said that "There is no SU binary installed"
terrorist96 said:
I can't uninstall my Superuser unless I use Titanium Backup. I tried installing SuperSU (while still having my original Superuser installed) and the SuperSU said that "There is no SU binary installed"
Click to expand...
Click to collapse
I got your PM. I'll pick your brain about the ideal setup for your needs and how you use the DNA via gtalk. Then we'll make a plan of attack and you can update the thread with your solutions opinions etc.
As long as your opinion of me is good. Otherwise, it's prohibited. I have a green title and seniority rules
HTC EVO CyanogenMod Cant use BEATS AUDIO
CharliesTheMan said:
Send me a PM if you want me to help you out. You need to install a custom recovery and use that to install a rooted rom and kernel. It can be a stock rooted rom. Or mostly stock however you want to do it, I'll help you set it up and teach you some things along the way.
I can teach you all kinds of things via team viewer, it wont take long and it's a necessity for having a rooted phone in my opinion. I know it can be frustrating and over whelming but it will get better I promise.
Oh and also you don't need to worry about losing s off. It's at a much lower level than anything you've mentioned touching. So it will always be there regardless because you definitely don't want to be messing with hboots or s off type stuff.
Click to expand...
Click to collapse
I need help with rooting my HTC EVO to stock or CyanogenMod. With CyanogenMod my phone will not play audio/BEATS or will not open
PLAYSTORE.
How to get root back after subsequent apps are denied root?
Over the last year, this has happened several times while having different custom roms installed. It happened several times with my Galaxy S4 and S5, and recently with my Galaxy Tab S 10.5. I have not lost root on my Nexus 7 (2013). The common denominator appears to be the Samsung devices.
Through SuperSu, I have removed root, rebooted, and installed root again with CF-Root which has not given me root access.
The only way I have been able to recover to date is to do a factory rest. It is interesting to note that I would have thought that the factory rest would take me back to the Samsung rom but in the last two time that I did this on either device, I ended up with the custom rom that I just had but without root or custom recovery.
To go back to a Samsung rom, I would think that if I started the device in download mode and did a flash with odin.
But rather than go through this, is there a reason why this happens and/or is there a way to avoid it?
Lastly, is there a true way of getting root back once it stops granting root?
cyaclone said:
How to get root back after subsequent apps are denied root?
Over the last year, this has happened several times while having different custom roms installed. It happened several times with my Galaxy S4 and S5, and recently with my Galaxy Tab S 10.5. I have not lost root on my Nexus 7 (2013). The common denominator appears to be the Samsung devices.
Through SuperSu, I have removed root, rebooted, and installed root again with CF-Root which has not given me root access.
The only way I have been able to recover to date is to do a factory rest. It is interesting to note that I would have thought that the factory rest would take me back to the Samsung rom but in the last two time that I did this on either device, I ended up with the custom rom that I just had but without root or custom recovery.
To go back to a Samsung rom, I would think that if I started the device in download mode and did a flash with odin.
But rather than go through this, is there a reason why this happens and/or is there a way to avoid it?
Lastly, is there a true way of getting root back once it stops granting root?
Click to expand...
Click to collapse
Best to post such things in your device specific forum.
This forum is for the Droid DNA.
However, gaining root is as simple as downloading the latest SuperSu zip and flashing it in recovery.
Very simple to do on any rom.

[Q] Can't Root My EVO 4G LTE No Matter What I Do

I have been trying to root my HTC EVO 4G LTE for days now without any luck. I have an unlocked bootloader. That was pretty easy. I originally tried the "Kingo Android Root" which unlocked the bootloader and claimed that it had rooted my phone. However, I did not have superuser privileges. I re-ran the "Kingo Anroid Root" several times. Each time it said I was rooted, yet every time I checked I was not. So, I came to the conclusion that the EVO 4G LTE was incompatible with the "Kingo" method.
So, I moved on to methods more specific to the EVO 4G LTE. I tried WinDroid, which flashed TWRP recovery and I then booted to that. However, when I installed superuser.zip, it said successful even though rebooting my phone once again left me without superuser privileges. I retried flashing superuser.zip multiple times, yet each time it failed to give me superuser access. It was around this time I noticed that while my bootloader reads "Tampered" and "Unlocked", I still have S-ON rather than S-OFF. Could this be preventing superuser.zip from giving me superuser access? I tried rumrunner to get S-OFF but that failed halfway through. Yes, I have installed both HTC and ADB drivers.
Honestly, this has just been a nightmare. I thought it would be a simple and relatively painless process, but it has become a multiple day affair that is consuming way too much of my time. I am about to either just pay someone to do this for me or give up entirely. So, any help is appreciated. Thanks in advance.
Hit up the link below and download the latest version of SuperSU, then flash in recovery. As far as the tampered warning in the bootloader, that's normal when you've unlocked the bootloader. As far as S-off goes, post your Hboot and radio (firmware) version, as that will determine which method you need to use to gain S-off.
http://forum.xda-developers.com/showthread.php?t=1538053
Also make sure that you have your superuser rights set to "ask" in the SuperSU app.
Well, I downloaded the new SuperSU.zip you posted and I rebooted to recovery. I installed it and TWRP said the install was successful. I then chose to reboot system. By the way, I don't think I mentioned this in my OP, but after the "Success Screen" and choosing to reboot I am prompted with a screen that says "No OS installed! Are you sure you want to reboot?" to which I say yes and then continue to another screen that asks if I want to "Install SuperSU. This will root your device." I swipe yes to tell it to install SuperSU even though I just installed it. Then, it kind of just sits there until rebooting normally. Just letting you know in case this changes anything. Should I try it again and choose to not install the second SuperSU? Could it be overwriting the updated one I flashed a few seconds prior?
Anyways, as you can probably guess by the nature of my disorganized post's first paragraph, the updated SuperSU did not root the phone as there is still no sign of the SuperSU app, nor any indication that I am rooted such as being able to delete the annoying bloatware installed. Any other suggestions?
Oh, and for the information you need for the S-ON problem:
HBOOT-2.09.0000
RADIO-1.13.11.0830
Magnum_Enforcer said:
Also make sure that you have your superuser rights set to "ask" in the SuperSU app.
Click to expand...
Click to collapse
Okay, but I don't currently see the SuperSU app. Isn't that supposed to come from the root or do you have to download that off the play store? I assume this post was for if updated SuperSU zip file worked.
Install the SuperSU app from the Play store, then check the permissions I previously mentioned. Also, the Rumrunner method should work fine but you can also try the Firewater method. Try Rumrunner a few times first, though.
Installing the SuperSU app off the play store and then running it only gives me a prompt that says, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Any ideas on how to fix this?
Install the SuperSU zip in recovery again. Then reboot.
Magnum_Enforcer said:
Install the SuperSU zip in recovery again. Then reboot.
Click to expand...
Click to collapse
Okay, I tried it again, but it isn't installing. I flash the UPDATE-SuperSU-2.02.zip file and then reboot. Then I go to the SuperSU app that I got off the Play store and it still brings up the same prompt followed by the app closing. Any ideas why the SuperSU.zip won't flash in TWRP?
M3TLGMR said:
Okay, I tried it again, but it isn't installing. I flash the UPDATE-SuperSU-2.02.zip file and then reboot. Then I go to the SuperSU app that I got off the Play store and it still brings up the same prompt followed by the app closing. Any ideas why the SuperSU.zip won't flash in TWRP?
Click to expand...
Click to collapse
Try an older version like 1.94.
Okay, I tried the 1.94 version. Same result as all the other versions of SuperSU I have tried.
I did notice something odd that somehow slipped past me. I copied the zip file to my root directory on my PC, yet when I launch into TWRP I find the file in the "/data" directory. Could this be the problem? That the zip files aren't in the root when in TWRP? Anyway, can I move the files up a level while in recovery? Because the files are in the root directory of my phone when I copy them on my PC. They aren't in the "data" folder...
Not sure what to tell you at this point. The location of the zip file shouldn't matter, though. Putting it on the root of your internal or external storage makes it easier to flash when it comes time to install, but it can be flashed even if it's in a folder somewhere. I'd suggest making sure that you have the latest version of TWRP on your phone (2.7.1.0) and starting over with a clean install of a rooted ROM, like MeanBean, since it is fairly easy to install while still being S-on. Link can be found below:
http://forum.xda-developers.com/showthread.php?t=2048229
I was having a similar issue to this a week ago. What is TWRP showing when you flash the file?

[Q] Dev Edition 5.0.1 Want Root Only, No Recovery

I have converted my AT&T M8 to stock Dev Edition following this thread. Worked a treat.
http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
I'm going on a vacation and want to use my phone as a transfer spot for photos taken with a DSLR. To do that, I will need to be able to copy/move files from the camera's SD card onto my phone's SD using USB OTG.
I understand that if I keep the stock recovery, loader, etc and only achieve root, then I will be able to get any OTA that becomes available. I will also be able to use one of the methods to enable writing to the SD of the phone.
So, the question is, how to get root without changing anything that will impact the OTA ability?
Hope I was clear in what I have and what I'm looking for.
No Direction?
Nobody?
GHammer said:
Nobody?
Click to expand...
Click to collapse
I've never heard of anyone wanting just root, so I'm not sure. But if your bootloader is unlocked you can try TowelRoot and see if that works and just install SuperSu through the playstore.
Unique
Ha! I'm unique.
Actually, I like Sense, and Lollipop is fine. I just didn't loike all the crap AT&T forced onto the phone and Uber was the last straw.
So, I want to keep the phone 'stock' except for accessing the extrenal SD.
I'll give Towelroot a shot and see how it goes.
GHammer said:
Ha! I'm unique.
Actually, I like Sense, and Lollipop is fine. I just didn't loike all the crap AT&T forced onto the phone and Uber was the last straw.
So, I want to keep the phone 'stock' except for accessing the extrenal SD.
I'll give Towelroot a shot and see how it goes.
Click to expand...
Click to collapse
Maybe I'm just off base here, but once the bootloader is unlocked, can't you just fastboot TWRP recovery, install SU (zip) file via recovery, then fastboot stock recovery and end up with a stock rooted device? Or does Lollipop not allow this?
DanGeorges said:
Maybe I'm just off base here, but once the bootloader is unlocked, can't you just fastboot TWRP recovery, install SU (zip) file via recovery, then fastboot stock recovery and end up with a stock rooted device? Or does Lollipop not allow this?
Click to expand...
Click to collapse
Hmmmm, perhaps just booting a recovery and installing SU would work.
See why I asked?
Guess this will wait for the weekend now. Restoring a phone takes more time than I have and it looks like I'm in uncharted territory.
Again, my objective is to have an OTA acceptable system with root.
Thanks for the two ideas, and of course, I'm open to others.
GHammer said:
Hmmmm, perhaps just booting a recovery and installing SU would work.
See why I asked?
Guess this will wait for the weekend now. Restoring a phone takes more time than I have and it looks like I'm in uncharted territory.
Again, my objective is to have an OTA acceptable system with root.
Thanks for the two ideas, and of course, I'm open to others.
Click to expand...
Click to collapse
I had a rooted device (4.4.2) and when I wanted the OTA to 4.4.4, I kept the root, but re-fastbooted the stock recovery so that the OTA would work. It kept my root (I think), and then I just re-installed TWRP so that I could still do backups..
I hope that someone with more knowledge than I will chime in if I'm wrong (or right).
DanGeorges said:
I kept the root, but re-fastbooted the stock recovery so that the OTA would work.
Click to expand...
Click to collapse
This is what I would suggest. There may be other ways (root without custom recovery). But I know for certain that the following will work: flash TWRP, flash SU or SuperSU to root. Than flash back to stock recovery.
You will be on stock recovery, have root, and should not impact OTA (provided all system files are also stock and not altered by root).
You can also try to fastboot boot TWRP (and then flash SU/SuperSU) without actually flashing TWRP. I'm not certain this will work, but I think it does under LP. I think something on 4.4.4 broke this ability, but then it came back.
Weekend Project
I will try the boot TWRP method first, and if that fails, I'll flash TWRP, get root, then go back to stock recovery.
This is now just an exercise to see which method works as the stock File Manager reads the USB and can copy files to the SD. I had not tried since 4.4.4. but did yesterday and it works for any kind of file.

Categories

Resources