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.
Related
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.
(I cant post to the original thread, but im hoping someone here can help me please?)
Ive rooted 6 or so different android phones mainly using cf-autoroot, including an i9300, and never had any issues. But I have had a few issues rooting my 9503 using the cf-autoroot method (method #1 in this post). It aooeared to work, but SuperSU subsequently fell over, and Knox complained but after reading other posts I rectified that, but obviously not quite correctly:
After using cf-autoroot, SuperSU DID NOT appear in the apps list, but Google Play said it was installed but only presented the option to open it (not update or remove).
So I then tried flashing twrp (as per method #2 in this post) which all appeared to go successfully according to Odin. I was expecting to install superSU updater, as per step 3, but recovery mode appeared unchanged/stock so of course I couldnt flash anything as there was no option to do so. Yet there were no errors reported by Odin?
So I then got hold of the app file for SuperSU 1.93 and installed it (via Airdroid). It ran. It found knox. It removed it, and root was installed successfully (as verified by root checkers, titanium backup, droid wall and the like). So I concluded I had successfully rooted my 9305.
But when I reboot SuperSU falls over again on boot up, and the version I added via Airdroid has disappeared, and of course there is no root mode.
But I can then restore root access after a reboot simply by following the same process, namley installing the supersu apk via Airdroid.
Can anyone suggest what is the easiest way to get round this, or even why it's happening? And why is the later version of SuperSU disappearing on reboot?
non persistent SU after rooting Android 4.3 - solved
OK, so Im still unsure how I ended up successfully rooted ,but then reverting back to a non-working or incompatible SU version on reboot (presumably the version installed via cf-root?). It's news to me that an app installed via standard means can be overridden for any reason on reboot. One day someone might explain that or tell me the appropriate phrase to use for my friend google so he can explain it to me.
So what I was then trying to do was install a custom recovery so I could flash the latest SU, as per OP. Try as I might I cant. Even removing the battery once TWRP has been transferred using Odin the standard recovery still prevails. So that one is still unresolved.
But in the meantime, as with most well written apps, the answer is within SU itself. Going into Options in the Su installed via the standard app installer, I selected the option to install that SU as a binary. And it worked, so now SU persists across reboots.
Just in case someone else has the same issue, although judging by all the replies I suspect not (or maybe everyone else is able to post to the original thread, although I dont see this exact problem or solutio there).
If it didnt help anyone, sorry for wasting your time!
Hi,
I have the same problem : my root is lost after each reboot.
I must uninstall SuperSU, then update SuperSU end reboot to have the root again.
Could you give me your solution with simple words because I don't understand what you posted befort. Sorry for my bad english ...
Thanks.
Before I begin, I would like to make it very clear that this is all very new to me. I have been researching this for quite a bit and read/followed quite a few guides. Most seem to not fit the OH7 version though.
The phone;
Model: SCH-I545PP
Version: 5.0.1
Build: LRX22C.I545PPVRUAOH7
Rooted with kingroot 4.5.0 and cleaned with Super SuMe Pro.
I have had to root this phone 7 times after 6 soft bricks, been at this for days. So I have rooted for the 7th time and stopped to hopefully acquire some help here. I know this phone has a locked bootloader so I have tried to work around that by deodexing to acquire Xposed. After pulling the system with the app, priv-app and framework folders, I used Lordroid's deodexer tool. Followed his guide as well as I can and received no errors in the process.
After putting the flashable zip onto my phone, I attempted to flash using flashfire from the app store. I can link the guides I used if needed. But all attempts landed me at the verizon splash screen. Waited 30 minutes on one attempt then just shut it down and went back to stock. So that is as far as I have gotten.
At this point, I am unsure if there is something I am missing or is this just a lost cause? I am thankful for any help there is to offer.
Okay so I have not seen anything new in regards to us unfortunate enough to have the Cricket variant of the grand prime, so I decided to put together a little step by step to get xposed installed and running on this device, I think it may work on others as well, but since I have not attempted it then do not just assume it will. This guide is as stated in the sub line of the post for the SM-G530AZ running 5.1.1 Lollipop. I am not responsible if you brick or bootloop etc etc your device. So long as you can follow directions you should be fine.
1. First of all you must already have root access on your device, mine is using SUPERSU to handle root requests. If you do not have root yet then check forums for way to do so it is there already, however you must root with kingroot or manually with the same exploit that kingroot is leveraging in order to obtain it before attempting the install of xposed, otherwise it will fail.
2. You need to download the zip file attached to this post to your desktop or device and unzip it into your device sdcard.
3. Once you have extracted the apk and zip files into the sdcard you need to install the xposed installer apk so make sure you have enabled Unknown Sources from your settings/Security menu and you may get a warning from the device as well that is okay just tap okay and finish the install.
4. Now you need to download flashfire from the play store and install it as well. Open flashfire and flash the xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip that you will have extracted Choose flash zip in flashfire and make sure you leave automount unchecked. You can open the xposed installer app to make sure it recognized it, which it should if you flashed it properly.
5. Now you can enjoy the Xposed Framework on your device.
I am currently attempting to learn as much as I can about the trust zone and smc as I can tell you that is the only way we are going to get custom recovery and roms on this thing sadly. I am also following someone who claims to be able to rollback android from 5.0+ to 4.0-4.4.4 via jtag which is something I too have pondered on if it was possible and honestly I think it would be, I would like to explore the possibility that their may have been more vulnerabilities within the device prior to the 5.1.1 update I currently have 5.1.1 installed which is what the device had at time of purchase for me, however some may still be running 4.4.4 if you happen to be using 4.4.4 still then I cannot say whether this guide will work or not for you I think it would but you would probably need to use a little older version of the xposed installer but I am not certain, I would probably just update to lollipop if you really want to be safe about it and the firmware has been posted on these forums as well. Please hit the thanks if this helped you out at all, and if you are confused or have an issue you can pm me and I will try my best to get back to you whenever possible. But this is how I got xposed working on my device by simply rooting with kingroot, then using the mrw script to remove kingroot and replace with supersu and enabling unknown sources. The root guide that exists for this device however stated to flash some other boot.img and I actually had issues when I did that step, so after i went back to stock again I did the root guide with kingroot and did not ever flash that other boot image and all worked fine for me.
Awesome thanks. I assume install King root then flashfire then SuperSU binary then uninstall king root. For SuperSU?
Sent from my DROID Turbo using XDA-Developers mobile app
THANK YOU THANK YOU THANK YOU! Thank you so much!!!!!! I have been trying to do this for 3 days now!!! I have soft bricked my device, restored it, got it going again, soft bricked again. Over and over. Until finally, today on my first day off all week I took the time to read your posts over again. I found this one and it finally got me there! I have the same exact phone, Cricket Samsung Galaxy Grand Prime Model SM-G530AZ. I have been struggling to find a TWRP or CWP recovery and I am pretty sure there isn't one available currently. So then I found this method and FINALLY SUCCESS!!!!! Anywhere I can donate to you?
I'm new to the forum. I've been lurking here for the past couple of weeks trying to piece together a way to root my SCH i545 running 5.0.1 with the pl1 update so that I might get to the point of running a custom nougat rom. Yesterday I started trying to figure out how to get a custom rom loaded on it, but got nowhere. I've never done anything like this before.
So, today I came across this thread. https://forum.xda-developers.com/galaxy-s4-verizon/general/update-1545vrsgpl1-t3537781 which linked me to the stang5litre rom. I thought I'd see if I could get that running. I downloaded kingoroot and got it rooted, confirmed by root checker. Then I downloaded SuperSU and tried to load it. I used Titanium Backup to remove the superuser, but when I tried to install the SuperSU it said that KNOX was interfering with the install. After some reading, uninstalled the KNOX using Titanium Backup and tried installing the SuperSU again. This time I got an error that said I needed to reboot. On rebooting, the phone makes it as far as the red Verizon screen and sticks.
It will still boot into the Recovery and Download modes. Can someone please tell me how to proceed from here?
Your best option is to start over by re-flashing it with stock PL1.
Then be careful during the superuser replacement process, that's when things went wrong basically breaking the system bootup.
Try using something like Super SUme to replace King with SSU.