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.
Team,
I used the Galaxy Toolkit to successfully root my S3. However, I soon realized that the rooted S3 would not allow Sky Go to work so I went through the process of un-rooting. This has also been partially successful as a re-un-root says I’m already un-rooted and apps that need rooting won’t run (Hope you followed that!). I have performed countless re-starts and have ensured that all app requiring rooting have been removed (including Superuser). I have uninstalled Sky Go and re-installed a number of times but to no avail. Sky Go continues to say it won’t work because the S3 is rooted.
Do you have any idea where some remnants of un-rooting may be lurking?
Thanks
pdes said:
Team,
I used the Galaxy Toolkit to successfully root my S3. However, I soon realized that the rooted S3 would not allow Sky Go to work so I went through the process of un-rooting. This has also been partially successful as a re-un-root says I’m already un-rooted and apps that need rooting won’t run (Hope you followed that!). I have performed countless re-starts and have ensured that all app requiring rooting have been removed (including Superuser). I have uninstalled Sky Go and re-installed a number of times but to no avail. Sky Go continues to say it won’t work because the S3 is rooted.
Do you have any idea where some remnants of un-rooting may be lurking?
Thanks
Click to expand...
Click to collapse
Best thing to do to get rid of all root binaries is the back up you data (contacts, messaging and apps). Download a firmware that is for Odin. Flash that Odin Software with FS reset and the phone will be stock
I recently rooted my phone using method 3 (root from stock recovery) from:
http://forum.xda-developers.com/showthread.php?t=2217840
It kind of worked and i was able to run the root applications.
But then i decided to unroot and did so from superSU's unroot option.
It worked and i dont see rooted anywhere (no triangle or flash counter)
except when i try to update. It says "your device has been modified. Software upgrades are unavailable"
Now im facing battery problems with my phone and want to go for replacement since its under warrenty. So my questions is would they be able to find out i rooted it and deny me replacement ?
Rooting doesn't shows any special effects to your phone but its required for some apps. And about battery problems, try to check new battery from the market
HIT THANKS WHENEVER POSSIBLE OR IF I HELPED YOU...
Check in your device specific forum.
Chainfire's app Triangle Away could restore your system status to official (but requires root). And make sure its compatible with your device.
[Q] Looking to flash my phone back to stock, but my current root is "broken"
Hi all,
So I'm interested in getting my rooted phone back to the latest stock firmware. I realize this question has been asked before (I have searched and found some earlier posts), but I was hoping to get some tailored clarification for my situation before I tried to follow a specific guide. My issue is that I had rooted my phone a long while back, and unfortunately did not stay on top of re-rooting during OTA Verizon updates. Because of this, my root is no longer properly configured. In addition, it's been so long that I don't even really remember how I rooted it in the first place. (I know, I suck.)
This is the status of where I am now:
- The phone is the Verizon Galaxy S4 (SCH-1545)
- I'm currently at Android 4.4.2 and Build I545VRUFNK1
- SuperSU no longer opens (it tells me it is missing the binary and cannot install it, and that I have to manually re-root)
- Root checker pro says that root access is not properly configured
Where I'm looking to get:
- I'd like to get my firmware back to the latest stock settings for this phone.
- I'd like to do this in a way that reverses any indication that my phone has been ever rooted (resetting the flash counter, undoing "warranty void" triggers, etc).
- For now, I don't yet want to wipe my phone back to factory. I'd like to first get my firmware back to stock (with all my current data still intact), and then I'll deal with a full factory reset at a later time.
- As an aside, if anyone has a "best practice" guide for backing up data before attempting my flash back to stock, I'd love to see something. I have Titanium backup, but it's currently unusable with my root state being broken.
Would anyone be able to point me to the proper guide (the more noob-friendly, the better) to reach my goal of getting back to stock? So far, I have found the following:
http(colon)//www(dot)sammobile(dot)com/firmwares/download/39628/I545VRUFNK1_I545VZWFNK1_VZW/
But I wanted to double check that I was following the proper steps for my situation before attempting anything.
Any help is appreciated!
Hello,
I have browsed XDA for some time now(S4 launch), but this is the first time I have not been able to get my problem solved without posting directly.
As such, I'm not quite sure if this is the correct place to post this and I sincerely apologize if I am in the wrong here.
Specs:
Android Version 5.0.2.
Baseband Version G925VVRU1AOE2
Kernal Version 3.10.61 Dated May 12, 2015
Hardware G925V.04
KNOX 2.4
The biggest issue is ping pong root not working for my device. I think if I can get this to work, my issues would be solved.
-Yes, it is in the supported devices section
-- I have searched [ROOT] PingPongRoot ***S6 & S6 Edge Root Tool*** Android 5.0.2 OC3/OE2 Only!!! extensively for this specific issue to no avail
--- I follow all steps and still get "device not supported, stay tuned"
---- using the search function within the thread, I looked for anything relating to G925VVRU1AOE2 and also tried a number of tricks that weren't build specific.
----- I have flashed G925VVZW1AOC3 and rooted with ping pong root with no issues. Flashing AOE2 back on gives the same error I had before.
------ Once upon a time I rooted with ping pong root on AOE2... This was shortly after it was supported.
My ultimate goal is to install a custom ROM. I was thinking Extreme Syndicate V8
For this, I need to be rooted on AOE2 via ping pong root.. Like I mentioned before, AOC3 root works fine and I have no issues with using that, except I need AOE2 + flashfire for this ROM.
I have never installed a custom ROM before, but I would like to start. If this ROM is a bad choice, I am open to suggestions. The extreme debloat is what drew me here.
All that said and done, I'll provide a little more in depth history.
I mentioned I originally rooted AOE2 with ping pong root in the past.
Shortly after that I was using XMODGAMES and somehow ended up downloading KINGROOT. Not sure what it did to my device but I could never uninstall kingroot completely. It would reinstall on reboot even after uninstalling with kingroot.
Eventually I came across SuperSUme and used that to successfully remove kingroot and switch over to SuperSU.
All was well and good (on my Stock AOE2 ROM)
About 2 days ago my google services framework crashed. I was able to identify Google+ not syncing properly as the cause... However I could not locate a fix. Through my tinkering I lost the google play store. So I decided to just do a full factory reset, hoping it would be simpler than trying to fix the issues I was having.
That brings us to today. I have so far flashed AOE2 - > AOC3 -> AOE2, with around 5 hard resets in between.
I figured I could just use kingroot to get rooted, then SuperSUme to get back to SuperSU and that should allow me to use flashfire.
WRONG. SuperSUme never asks for root permission(or kingroot automatically blocks it idk). So SuperSUme doesn't work. I tried this with kingroot 4.9, then 4.1 and I think 4.5 (not exactly sure what the last one was)
I looked for a more complex rooting method since it appears the one touch ones weren't going to get the job done, but couldn't find anything.
If anybody could point me in the right direction to getting rooted with SuperSU, it would be greatly appreciated.
Thank you for your time.