Randomly Lost Root in CleanROM 1.4 - HTC Rezound

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

Related

Root permission problems

I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
I finally got root to work, but now some apps when requesting root re-boots my phone.
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
In regard to all fo the problems below:
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
wowens0822 said:
I finally got root to work, but now some apps when requesting root re-boots my phone.
Click to expand...
Click to collapse
theguitarhero94 said:
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
Click to expand...
Click to collapse
BigRed35m said:
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
Click to expand...
Click to collapse
eddiecanuck said:
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
Click to expand...
Click to collapse
Listen up guys I'm assuming most of you are bone stock and freshly unlocked the problem is the SuperSU APP it is stated in the OP for the unlock method and most of the root threads around here that currently the binaries we have for supersu that is flashed in recovery during the root process are not compatible with the SuperSU APP from the market. Downloading "superuser" from the market will fix all of your problems.
download this > https://play.google.com/store/apps/details?id=com.noshufou.android.su&feature=nav_result#?t=W10.
Until further notice this will be necessary. There are some people that have hacked in different binaries for their updates/roms just make sure you read OP's first before tryingto switch back to the SuperSU app.
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
eddiecanuck said:
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
Click to expand...
Click to collapse
Did you make a NAND b4 supersu app installed? Revert if so if not i recommend UKB in the development sections its a solid rom right now with lots of options. I'd say fix it now so it doesnt bite you later. Also you could try freezing in tibu then using tibu to uninstall SuperSU that is.
I did an uninstall updates for SuperSU to get it back to what was flashed, and I can uninstall Superuser. Haven't done a NAND yet but will. Looking at UKB, was going to stay stock for a while but after looking at that I probably won't.
Most likely flash it tonight, has some nice features. Thanks again for the input.

Can we install 4.5.145 OTA

https://doc-0k-1o-docs.googleuserco...009/*/0BzrP5DWIlpplYjFOY1MwOXFNLWc?e=download
here is the ota zip
if we flash this can we flash 4.5.141 with rsd?
any answers?
I wouldn't count on it. The ZIP seems to contain what looks like the bootloader, or at least a piece of it (ap20bl.img). Who knows what might happen after that. Motorola said a downgrade is not possible.
I would just wait for the .145 fruitcake. Then switching back and forth should be safe and painless.
ok thanks for answer
Installed 4.5.145 for fun
blttalas said:
ok thanks for answer
Click to expand...
Click to collapse
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
sn0wba11 said:
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
Click to expand...
Click to collapse
Did you do this via the standard update or by flashing that zip yourself?
vikingarcher said:
Did you do this via the standard update or by flashing that zip yourself?
Click to expand...
Click to collapse
Standard
Su ota survival
Has anyone tried to install the update after activating the superuser ota survival option
Root after sys 4.5.145 update?
fdaconta said:
The traditional preinstall method should still work. No wiping happens with that. I used it back when I first rooted my phone, everything stayed exactly as it was (all stock) except I had root too.
Click to expand...
Click to collapse
This response is from the developer thread. I would respond there but the policy for members with less than 10 posts is silly.
None of the existing preinstall methods (e.g. atrix-4g-moto-fastboot or superoneclick 2.3.3) work with 4.5.145.
sn0wba11 said:
Standard
Click to expand...
Click to collapse
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
vikingarcher said:
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
Click to expand...
Click to collapse
Came across a link at Android Central that used Voodoo OTA RootKeeper to restore --> Forgot I installed this awhile back; reinstalling app restored my superuser access
Re-rooted 4.5.145 after OTA
I successfully re-rooted mine last night using the pre-install method.
Read my topic here:
http://forum.xda-developers.com/showthread.php?t=2153422
From 141, to 145, back to 141.... and finally ended up with a working (and rooted) 145.

[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] Failed Root?

I'm usually good at searching for answers for my problems, but I couldn't find the answer to my problems. I'll be as specific and detailed as I can.
I got my HTC Rezound and was running Android 4.0.3 out of the box. Then I decided to root my phone mainly to try to remove HTC sense and bloatware.
*First time at rooting*
From my understanding, I first had to unlock the bootloader, install a custom recovery, then install a custom rom (if I choose to, which I wanted to do).
So I successfully unlocked the bootloader through the HTCdev website. (I'll admit I was having trouble initially on my Windows 8.1 desktop, but I switched to my Windows 7 laptop and it worked perfectly)
Then I went on ahead to flash a custom recovery (Amon Ra Recovery).
After that, I managed to go into Recovery from the Bootloader to install Superuser. Then I updated it to the latest version via Google Play.
So far, I was having little to no issues up to this point.
But here's where I start getting into trouble...
Before I install a custom rom I wanted to test out the phone with it's new unlocked features. So I decided to download Titanium Backup (which downloaded and installed successfully) and it failed to find root access. So I decided to do some research and found out that rebooting it a few time helped some people out. Not for me.... Hard rebooted as well, but no dice. Looking at my Superuser (v 3.1.3), I noticed that the binaries were out of date (v3.0.3, and the latest is 3.1.1)
Thinking that this was the issue I tried to update it.
This is what the Binary Updater read:
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.1.1
Checking installed version = 3.0.3
Unpacking sutools... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Gaining root access... fail!
Then I decided to continue reboot 3-5 times, still nothing changes.
I downloaded a root checker app, which also told me that my phone is not rooted. I've also tried to reset my phone to factory settings through Recovery, but nothing changed.
I'm not sure if it's the Amon Ra Recovery or what. All I know is that my phone is telling me that it's not rooted, when I successfully did all the steps to do it. If there is another thread that I may have missed that solves this issue, please help me out.
I'm pretty sure I may just need to update the binary files on Superuser, but I can't do that through the Binary updater on my phone due to it's failing to gain root access. I just can't find the proper Binary files online. I'm also not too sure on how to update the binary files either.
Help?
:angel::crying:
androooleee said:
I'm usually good at searching for answers for my problems, but I couldn't find the answer to my problems. I'll be as specific and detailed as I can.
I got my HTC Rezound and was running Android 4.0.3 out of the box. Then I decided to root my phone mainly to try to remove HTC sense and bloatware.
*First time at rooting*
From my understanding, I first had to unlock the bootloader, install a custom recovery, then install a custom rom (if I choose to, which I wanted to do).
So I successfully unlocked the bootloader through the HTCdev website. (I'll admit I was having trouble initially on my Windows 8.1 desktop, but I switched to my Windows 7 laptop and it worked perfectly)
Then I went on ahead to flash a custom recovery (Amon Ra Recovery).
After that, I managed to go into Recovery from the Bootloader to install Superuser. Then I updated it to the latest version via Google Play.
So far, I was having little to no issues up to this point.
But here's where I start getting into trouble...
Before I install a custom rom I wanted to test out the phone with it's new unlocked features. So I decided to download Titanium Backup (which downloaded and installed successfully) and it failed to find root access. So I decided to do some research and found out that rebooting it a few time helped some people out. Not for me.... Hard rebooted as well, but no dice. Looking at my Superuser (v 3.1.3), I noticed that the binaries were out of date (v3.0.3, and the latest is 3.1.1)
Thinking that this was the issue I tried to update it.
This is what the Binary Updater read:
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.1.1
Checking installed version = 3.0.3
Unpacking sutools... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Gaining root access... fail!
Then I decided to continue reboot 3-5 times, still nothing changes.
I downloaded a root checker app, which also told me that my phone is not rooted. I've also tried to reset my phone to factory settings through Recovery, but nothing changed.
I'm not sure if it's the Amon Ra Recovery or what. All I know is that my phone is telling me that it's not rooted, when I successfully did all the steps to do it. If there is another thread that I may have missed that solves this issue, please help me out.
I'm pretty sure I may just need to update the binary files on Superuser, but I can't do that through the Binary updater on my phone due to it's failing to gain root access. I just can't find the proper Binary files online. I'm also not too sure on how to update the binary files either.
Help?
:angel::crying:
Click to expand...
Click to collapse
1) I'd recommend TWRP or CWM for your recovery, both can be found in the Original Development section.
2) Try flashing this via recovery for root on an ICS rom - http://forum.xda-developers.com/showpost.php?p=23897942&postcount=371
i think rooting method u use is not working.
have u try another rooting method?
like z4root or superOneClick shortfuse?

[Q] Did Perm Root - Only got Temp Root?

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!

Categories

Resources