Develop Bugs

[Q] How to tell if ROOT was successful?

I came from the EVO where you could check to see if it said S-OFF if the root was successful.
I used ODIN to root, and it said it was a success, but nothing changed on my phone as far as i can tell. When i rebooted, there was a Yellow Triangle on the boot up, so im assuming that everything is good.
I tried searching, but no one covered this topic that i can tell. Id rather know for sure before i try anything else.

In the market download an app called "Root Checker" ... run it and it'll give you an answer

gah, cost me 99 cents ( i hate paying for ****) but it says im rooted.
Thanks boss.

All you had to do was downlaod a root app and it would check. You could have done titanium.
Sent from my SPH-D710 using xda premium

Randomsilliness said:
gah, cost me 99 cents ( i hate paying for ****) but it says im rooted.
Thanks boss.
Click to expand...
Click to collapse
come on bro if you came from the evo then its all the same really. Check for superuser and download wifi tether and check. Or just go into market type in root and see what pops up... Root checker its free...Plus S-Off was for our bootloader but apps like z4root gave you root access with out S-off. At least in older bootloaders
Edit: try this link full of root apps https://market.android.com/search?q=root&so=1&c=apps

wow of all the roundabout ways to check for root
could have just opened the superuser app that installs with every root method we have.
if it fails and shows a toast saying you don't have root guess what?
if it opens you have root

most of this thread wat is this i don't even.

There used to be a free root check app by joeykrim, I guess its pay only now. Just use any app that uses root and you will know.
Sent from my Galaxy S2

Rooted my phone but no rooted applications work

Hi folks,
I rooted my phone but no applications that require root access work.
I am currently running the 40.2 update on my verizon nexus.
I tried wifi_tether_v3_1-pre111.apk, rom tool box, root checker and root toolbox.
Rooted applications always say that my phone doesn't have root access or a kernel is missing.
When I do a fastboot oem lock, it shows that my phone is unlocked. I am quite confused as to why no programs that require root work for this phone.
Is their any programs out there that can verify that phone is rooted. Is their any technique other then what I tried that can verify it.
I am stuck and I dont know what else to do.
Is anyone else experiencing this issue? I cannot be the only one.

Simply unlocking the boot loader does not give you root. Check the stickies in the dev forum a guide
Sent from my Galaxy Nexus using Tapatalk

I have checked. If you could "simply" provide a link to even one sticky with this information other than the "obvious" answer you provided I'd be quite appreciative.
If you don't know that is fine to. Don't be the guy/gal who gives driving directions but has no idea.
Thanks!

vastcomm said:
I have checked. If you could "simply" provide a link to even one sticky with this information other than the "obvious" answer you provided I'd be quite appreciative.
If you don't know that is fine to. Don't be the guy/gal who gives driving directions but has no idea.
Thanks!
Click to expand...
Click to collapse
Check my sig
Sent from my Galaxy Nexus using Tapatalk

vastcomm said:
I have checked. If you could "simply" provide a link to even one sticky with this information other than the "obvious" answer you provided I'd be quite appreciative.
If you don't know that is fine to. Don't be the guy/gal who gives driving directions but has no idea.
Thanks!
Click to expand...
Click to collapse
I normally would of, or but I answered your question on mobile as i was leaving the house this morning
Sent from a phone that is not running ICS

You need to install the root binaries to achieve root, look in the general thread and theirs a guide to show you how to root with superboot r3. Once you run it in adb, it will install the binaries and superuser apk. Then after go to the market and search busybox, install the app and let it install the busy box file.
It is impossible that your missing a kernel if your phone can boot. The programs you installed to check "root" are not compatible with the phone. For future reference, check the stickies in the general thread.
Sent from my Galaxy Nexus using xda premium

[Q] Custom ROM with un-root ability

Hey everyone,
Just got a GN a few weeks ago, and I am dying to try a custom ROM, but I got dinged by my work with my infuse because they have a no-root policy strickly enforced when accessing our corporate email.
I was not able to use an un-root app like root keeper, apparently because the ZEUS rom I was using had an autoroot on startup.
I am hoping the nexus has better options for using the un-root app, to (temporarily) unroot my phone when accessing my mail.
I have been reading that it is better to manually root the handset, rather than use a toolkit, which I am OK with; but I really would be interested in hearing from someone that has successfully used an unroot app to remove root.
- Thanks!

KevinAlbrecht said:
Hey everyone,
Just got a GN a few weeks ago, and I am dying to try a custom ROM, but I got dinged by my work with my infuse because they have a no-root policy strickly enforced when accessing our corporate email.
I was not able to use an un-root app like root keeper, apparently because the ZEUS rom I was using had an autoroot on startup.
I am hoping the nexus has better options for using the un-root app, to (temporarily) unroot my phone when accessing my mail.
I have been reading that it is better to manually root the handset, rather than use a toolkit, which I am OK with; but I really would be interested in hearing from someone that has successfully used an unroot app to remove root.
- Thanks!
Click to expand...
Click to collapse
C m9 has this option I believe
Sent from my Galaxy Nexus

How can they tell if you are rooted just through email use?

CM9 lets you restrict root access to ADB only. Might want to check that out

imnuts said:
How can they tell if you are rooted just through email use?
Click to expand...
Click to collapse
We access our corporate mail through the GOOD for enterprise application, and and that scans for root on load.
Sent from my Galaxy Nexus using xda premium

If the app scans for just the root binary or Superuser app, then I don't see a way to prevent it from detecting root without actually being unrooted. It likely looks in all $PATH dirs for su, and then in /system/app or /data/app for the application to grant permissions. Any ROM can be unrooted, just remove the su binary (and any symlinks) and the Superuser app before flashing.

Damn, they take the fun out of the whole Nexus experience.
Sent from my Galaxy Nexus using Tapatalk 2

imnuts said:
If the app scans for just the root binary or Superuser app, then I don't see a way to prevent it from detecting root without actually being unrooted. It likely looks in all $PATH dirs for su, and then in /system/app or /data/app for the application to grant permissions. Any ROM can be unrooted, just remove the su binary (and any symlinks) and the Superuser app before flashing.
Click to expand...
Click to collapse
Yeah, thanks. I guess what I am asking is if any of the unroot apps work with the custom ROMs the Nexus has. The ZEUS rom I was using with the infuse had something related to voodoo that kept ROOT, and the unroot apps did not have an affect.
I have only flashed two android ROMs with my infuse, but am an application developer by trade, so I am not skeered by the command prompt. I know there are a few CM9 based ROMs out there. I was looking at the PARANOID rom just cause that seemed interesting with the tablet hybrid. I just would like to know before I go through the whole flashing proc. that I can unroot before I connect to my work email (about once a week).
- Thanks for the replys so far. - Kevin

Just wondering...what is so dangerous about having root when accessing email?

fredryk said:
Just wondering...what is so dangerous about having root when accessing email?
Click to expand...
Click to collapse
Depending on the apps, root permission allows an app to gain full control of your device, so if one is not careful, he may let a rouge app into the phone. From a security standpoint, the rouge app may steal data from the email, which no company wants.
Think root as your computer's "Run as Administrator", same reason companies/schools limit user permission using User Policy(or whatever it's called)

Could just make a script to delete su and superuser and busybox, and make a flashable zip to put them back again.
Would require a couple of reboots every time but would still be quick to do once you had the zips set up
Sent from my Cyanogenmodded GNex

dr.m0x said:
Could just make a script to delete su and superuser and busybox, and make a flashable zip to put them back again.
Would require a couple of reboots every time but would still be quick to do once you had the zips set up
Sent from my Cyanogenmodded GNex
Click to expand...
Click to collapse
That's why I asked if anyone had success with the RootKeeper app. Although I would be interested in building an android script, my experience is soley with vb/C# web & desktop applications.
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en

Use SuperSU. What I did was temporarily block root, installed whatever MDM app was needed, set up the stock Exchange information, and allowed root again.
Let me know if this works for you.
Sent from my Galaxy Nexus using Tapatalk 2

Thanks shanky,
I will look into super su. The GOOD application checks on every launch, and so I will need to run it whenever I need to check work email, and but that is only once or twice a week from my phone.
Sent from my Galaxy Nexus using xda premium

KevinAlbrecht said:
Thanks shanky,
I will look into super su. The GOOD application checks on every launch, and so I will need to run it whenever I need to check work email, and but that is only once or twice a week from my phone.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hi Kevin,
did you have success with that? Or any other suggestion?
I have the same problem, my IT wants to wipe GFE container if my device keeps rooted.
Thanks..

Hi RTHppc,
Sorry for the very late reply. I can confirm this does work with GFE. The unroot effectively does not cause a compliance violation.
Overall it was a hassle to verify, even though our infrastructure team was completely on board. GOOD was balking when I attempted to register a second device (even temporarily) with the same sim card. It would only throw an ambiguous error 'unknown error'.
I could go on, but that is the subject for a rant thread.
Sent from my SGH-I997 using xda app-developers app

[Q] How to root my Galaxy Nexus but still get OTA updates from Google?

Excuse my complete noobishness, but can someone help me root my Galaxy Nexus but still get OTA updates from Google? I found multiple sources from here and a video from QBKing77 but nothing answer my question completely. I would be really grateful if someone with experience could help me by give me step by step instructions.
Thank you.

Rooting your phone does not disable OTA updates.

Why would you want ota if you rooted? Just flash a rooted version of the updated rom when it's released.
Sent from my Galaxy Nexus using Tapatalk 2

eqjunkie829 said:
Why would you want ota if you rooted? Just flash a rooted version of the updated rom when it's released.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I want to root just for two or three apps that require root access and still get updates from Google. I want the process: root -> get OTA update -> root again etc...

ZlateWay said:
I want to root just for two or three apps that require root access and still get updates from Google. I want the process: root -> get OTA update -> root again etc...
Click to expand...
Click to collapse
That's what I do. I don't flash ROMS, just use a few apps that require root. Install OTA Root Keeper from the play store to retain root. Run the app before installing any updates to preserve root. Then when you receive an OTA, install the update then run OTA Root keeper again to get your root back. Worked for me on Verizon Galaxy Nexus coming from 4.0.4 to 4.1.1.
Sent from my Galaxy Nexus using Tapatalk 2

The_other_ray said:
That's what I do. I don't flash ROMS, just use a few apps that require root. Install OTA Root Keeper from the play store to retain root. Run the app before installing any updates to preserve root. Then when you receive an OTA, install the update then run OTA Root keeper again to get your root back. Worked for me on Verizon Galaxy Nexus coming from 4.0.4 to 4.1.1.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That is what I'm looking for! Can you explain to me step by step how did you did that? It would be great if you help me.

Use the guide in my sig or stickied at the top of this forum.
Only change would be fastboot boot recovery cwm.img rather than flash.

Just root the phone, and don't flash any custom recovery, then download supercurio's OTA root keeper app from the playstore, to backup your root then enable root with the same app after you receive OTA
Sent from my Galaxy Nexus using Tapatalk 2

suprakarma said:
Just root the phone, and don't flash any custom recovery, then download supercurio's OTA root keeper app from the playstore, to backup your root then enable root with the same app after you receive OTA
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks

ZlateWay said:
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
Click to expand...
Click to collapse
Don't use the toolkit?
Sent from my Galaxy Nexus

Why not?
The toolkit is SUPER easy.
Open the tool kit and the DOS window guides you through what to do, by typing numbers or letters to get the desired option. I can post the guide on when to boot in recovery mode and what the phone will do but as for the Toolkit, it's self helping. Just install it, run it and follow the on-screen instructions.
I do exactly the same as what you want successfully; I have a completely stock Nexus, but it's rooted for the use of some apps. The OTA update tells me when there is an update, I install then simply root again. I'd rather not have an app to keep root as that will be yet another app to clog up my phone's app drawer.
A lot of the custom roms aren't to my taste so I am happy to keep the stock experience
Will post again the steps when I am on my home PC.

anotherxdauser said:
Why not?
The toolkit is SUPER easy.
Open the tool kit and the DOS window guides you through what to do, by typing numbers or letters to get the desired option. I can post the guide on when to boot in recovery mode and what the phone will do but as for the Toolkit, it's self helping. Just install it, run it and follow the on-screen instructions.
I do exactly the same as what you want successfully; I have a completely stock Nexus, but it's rooted for the use of some apps. The OTA update tells me when there is an update, I install then simply root again. I'd rather not have an app to keep root as that will be yet another app to clog up my phone's app drawer.
A lot of the custom roms aren't to my taste so I am happy to keep the stock experience
Will post again the steps when I am on my home PC.
Click to expand...
Click to collapse
simply because the toolkit is an excuse not to learn the FUNDAMENTALS of owning a nexus device.
what happens when something goes wrong? do you know what the toolkit is doing behind the scenes? most of the toolkit users DONT. there are more than enough 'HALP!1!1 I BriKt mah PhoneZ!1!!oneone' to prove this is the case....
if you understand what its actually doing, you understand how useless it truly is...

Well, for starters the "fundamentals of owning a nexus device" don't include rooting at all. I know many people who use Nexus devices un-rooted and are fine.
Plus, I'm more than happy not learning too much about it as I'd rather spend my time eating cake.
Remember, not everyone here is in to tweaking settings, trying different radios, resetting their phone every 5 mins to test yet another ROM.
Some people are more than happy with the stock experience but just want root. The toolkit makes that simple.
Secondly, if the toolkit was doing things behind the scenes, I'm sure someone would have found that out and reported by now.
Thirdly, how do you know custom ROMs aren't doing the same thing? They are far more likely to be able to phone home without the owner knowing.
Fourthly, I personally tried rooting the manual way but the one line help of "just type this" I got never really worked with my phone.
Fifth, I've used the toolkit on my own phone and my partners many times, I've seen nothing bad, no bricking.
Don't see why you're so against something which makes life a lot easier for people who aren't too sure how to root the manual way?

anotherxdauser said:
Well, for starters the "fundamentals of owning a nexus device" don't include rooting at all. I know many people who use Nexus devices un-rooted and are fine.
Plus, I'm more than happy not learning too much about it as I'd rather spend my time eating cake.
Remember, not everyone here is in to tweaking settings, trying different radios, resetting their phone every 5 mins to test yet another ROM.
Some people are more than happy with the stock experience but just want root. The toolkit makes that simple.
Secondly, if the toolkit was doing things behind the scenes, I'm sure someone would have found that out and reported by now.
Thirdly, how do you know custom ROMs aren't doing the same thing? They are far more likely to be able to phone home without the owner knowing.
Fourthly, I personally tried rooting the manual way but the one line help of "just type this" I got never really worked with my phone.
Fifth, I've used the toolkit on my own phone and my partners many times, I've seen nothing bad, no bricking.
Don't see why you're so against something which makes life a lot easier for people who aren't too sure how to root the manual way?
Click to expand...
Click to collapse
And yet another person who fails at grasping why XDA exists....
Sent from my Galaxy Nexus

Actually, I do. I understand why XDA exists but I also understand the multi-uses it really has.
Not everyone who comes here has a desire to mess with their phones all the time...
If you're not a fan of the toolkit, why not flame the developer?
Here's a short guide on what the OP wanted to do.
1) Make sure phone is up to date. Make a note of your software version - probably 4.1.2 or 4.2 and build number (mine is JZO54K)
2) Turn on USB Debugging (Settings > Developer Options > USB Debugging)
3) Shut down the phone
4) Start in Bootloader (power button + vol up + vol down)
5) Run the Galaxy Nexus toolkit
This is where we use the toolkit. Read the info and select your build number. The windows will guide you through what options you have. If you want to root only, choose that option. Go through the menus and type YES to begin.
6) Phone will restart
7) After ~160 seconds, ToolKit will restart to Bootloader
8) Phone will restart
9) Toolkit will finish rooting by pushing the files to the phone.
10) Phone will restart back to Bootloader
11) Finish - Confirm in ToolKit
See pictures for further info.

Pirateghost said:
And yet another person who fails at grasping why XDA exists....
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
the toolkit also exists on xda..

k786 said:
the toolkit also exists on xda..
Click to expand...
Click to collapse
So does the person that thought I was saying the toolkit did something malicious... I never said any such thing.
Toolkits are pointless. It takes longer to learn the toolkit than it does the three commands needed to unlock and root a nexus. That's my ****ing point, yet this guy is going on about how easy the toolkit is to use. If it's so ****ing easy, why did you have to provide screenshots and instructions?
XDA-spoonfeeders.com
I miss XDA
Sent from my Galaxy Nexus
**edit**
i cannot believe that someone would actually think its NOT beneficial to understand the process, and rely solely on a toolkit...its amazing to think that there are people so wrapped up in their own little minds, that they refuse to take the time to learn to do things the right way and understand what they are doing to their device.
what happens when joe user, who only knows the toolkit, flashes a mod on his phone that was NOT intended for his phone/build/rom version, and he bootloops? he jumps on xda and posts a thread. HALP I JACKED MAH PHONE!!! how do i fix it with the toolkit?
please, for the love of tech, LEARN what it is you are doing. do us all a favor and help spread the KNOWLEDGE and stop with the damn toolkit. this website is designed for you to learn, not follow a damn prompt/menu to get instant gratification.

ZlateWay said:
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
Click to expand...
Click to collapse
Don't use a toolkit. Learn commands yourself and you won't have to worry about what a toolkit is or isn't installing.
Sent from my Galaxy Nexus using xda premium

root toolkits are fine, if you already know what you are doing. the problem with root toolkits arises when a person that has no idea what they are doing uses them and messes something up, which happens often, just read all the threads that users start asking for help, that include the words "i used a root toolkit". you dont see any these thread with the words i used fastboot or adb. usually what happens is something simple gets messed up, then the situation becomes worse because the user didnt know/learn the basics, and messed something up after. this is the problem with root toolkits, they go around you having to learn the basics. then we get all these threads about "help, i bricked my device". just taking the little time needed to learn the basics prevent this from happening.
this is a nexus device, its meant to be able to root the device easily. this is the basic procedure.. fastboot oem unlock, fastboot flash a custom recovery, flash the su binaries or custom rom in your custom recovery, reboot. that is it. it takes me 3 minutes to do this. add on a little reading beforehand, and maybe itll take you 30 minutes. much better than getting lost after using the root toolkit, or even messing up your device messing with stuff that you shouldnt. and, occasionally, the root toolkit itself can mess things up.
btw, op, you can always install an official "ota" manually, without receiving it ota, and without having root too. also, if you flash a rooted stock rom(unmodified, only root), youll still receive otas

You can unlock and root without install a custom recovery. IF you don't install any custom recovery and leave the stock one you'll continue to receive the ota updates.
Bye
Sent from my Galaxy Nexus using xda app-developers app

[Q] Lost Root Access after Upgrading to Cm 10.1.3.1

Hey can anybody help me with an answer to this question
I lose root Access to my phone after Upgrading to Cm 10.1.3.1 From 10.1.3 I'm Running Droid 4.2.2 But when I Re install 10.1.3 from backup root is back and have ALL ROOT Permisions

Viper1979X said:
Hey can anybody help me with an answer to this question
I lose root Access to my phone after Upgrading to Cm 10.1.3.1 From 10.1.3 I'm Running Droid 4.2.2 But when I Re install 10.1.3 from backup root is back and have ALL ROOT Permisions
Click to expand...
Click to collapse
Can you give us more information on what model of s3 and any other weird things that have been happening to your phone?
Sent from my SGH-I747 using XDA Premium 4 mobile app

lost root after upgrading
Bruce Lee said:
Can you give us more information on what model of s3 and any other weird things that have been happening to your phone?
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Samsung Galaxy S3 At&t 1747 16gb 1747UCDLK3 Qualcom
1.5GHz Dual Core Processor NFC Enabled 4g LTE Capable
Garnet Red Origanly Jb 4.1.2.
Hope thats enough info dont really know wht else is needed.

Viper1979X said:
Samsung Galaxy S3 At&t 1747 16gb 1747UCDLK3 Qualcom
1.5GHz Dual Core Processor NFC Enabled 4g LTE Capable
Garnet Red Origanly Jb 4.1.2.
Hope thats enough info dont really know wht else is needed.
Click to expand...
Click to collapse
Thanks thats good. But my question now is..... I didn't see the ROM said you tried to flash in the ATT Dev section? Can you post a link or describe the ROM better. No ROMS should make you lose root access.
Sent from my SGH-I747 using XDA Premium 4 mobile app

Bruce Lee said:
Thanks thats good. But my question now is..... I didn't see the ROM said you tried to flash in the ATT Dev section? Can you post a link or describe the ROM better. No ROMS should make you lose root access.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cyanogen Mod 10.1.3.1 thats because I used ROM Mgr for all my roms like most of us do I believe, and use Xda for all of my stock Jb ROM downloads along with oden. I flashed through Clockwork Recovery and this is the first time I flashed a ROM and lost root after aperantly other people are having some of the same probs.

I would recommend you don't use that ROM especially if other people are having issues. I would recommend the cyanogenmod ROMS and the hyperdrive Touchwiz ROMS.
Sent from my SGH-I747 using XDA Premium 4 mobile app

This might help but I'm not so sure but this might help: Go to Settings>Developer Options and Above the sub-menu "Debugging" there's Root Access, by default it should be Apps Only but hopefully this could help a little...

Answer To Yas Problems
Viper1979X said:
Hey can anybody help me with an answer to this question
I lose root Access to my phone after Upgrading to Cm 10.1.3.1 From 10.1.3 I'm Running Droid 4.2.2 But when I Re install 10.1.3 from backup root is back and have ALL ROOT Permisions
Click to expand...
Click to collapse
Hey!!!, So I had the same problem; I've searched and searched for almost 2 months for an answer... and nothing. To be honest I was actually just going to give up and accept CM10.1.3.1 as my phone's tomb. Although, I finally fixed it in the oddest way—essentially fiddling around with the phone before bed.... serious ciber-ich—So forget anything anyone has even talked about, up to this point, because it isn't a problem with your phone; in fact you are still rooted, you've just lost access to your root due to a root-permission war between your phone and superuser/supersu (what eva).
So if anyone is interested in fixing this, here, this is what I did to fix it.
This was my first failed attempt
1) Reinstall Root (Fail!!!!)
2) Use new super User (Fail!!!!!!)
3) Reinstall CM (Fail!!!!!!!!)
4) Wait for an answer on google (fail!!)
5) Wait for an answer on here ( double fail!!!!)
Here's the Fix
1) Reinstall Root with SuperSU ( Probably didn't need to do this; however, due to all the superuser-instalation-overkill, it's probably best.)
2) Uninstall all other superuser apps you may have on your phone—also do not use CWM Superuser (It doesn't have what it takes)
3) Go to App Management, uninstall SuperSU's last update
4) Clear SuperSU's catch (self explanatory)
5) Go into AppDrawer, Open SuperSU app and make sure
- Enabled -- Yes
- Survival mode -- No
- Logging -- Access only
- Trust System User -- Yes
- *************** Respect CM root settings********** no!!!!!!!!!!!! Do not respect that ****!!!!!!!!
6) Enjoy your root access again :victory:
If anyone has any questions, just message me. I hope this was of help to anyone going through the same pain I had gone through.
For some more info on my phone.
- I'm running a I747m GSIII CM10.1.3.1d2att
- as for the root... well I can't give the link because i'm new to this site...
John Stuart

JohnStuart said:
Hey!!!, So I had the same problem; I've searched and searched for almost 2 months for an answer... and nothing. To be honest I was actually just going to give up and accept CM10.1.3.1 as my phone's tomb. Although, I finally fixed it in the oddest way—essentially fiddling around with the phone before bed.... serious ciber-ich—So forget anything anyone has even talked about, up to this point, because it isn't a problem with your phone; in fact you are still rooted, you've just lost access to your root due to a root-permission war between your phone and superuser/supersu (what eva).
So if anyone is interested in fixing this, here, this is what I did to fix it.
This was my first failed attempt
1) Reinstall Root (Fail!!!!)
2) Use new super User (Fail!!!!!!)
3) Reinstall CM (Fail!!!!!!!!)
4) Wait for an answer on google (fail!!)
5) Wait for an answer on here ( double fail!!!!)
Here's the Fix
1) Reinstall Root with SuperSU ( Probably didn't need to do this; however, due to all the superuser-instalation-overkill, it's probably best.)
2) Uninstall all other superuser apps you may have on your phone—also do not use CWM Superuser (It doesn't have what it takes)
3) Go to App Management, uninstall SuperSU's last update
4) Clear SuperSU's catch (self explanatory)
5) Go into AppDrawer, Open SuperSU app and make sure
- Enabled -- Yes
- Survival mode -- No
- Logging -- Access only
- Trust System User -- Yes
- *************** Respect CM root settings********** no!!!!!!!!!!!! Do not respect that ****!!!!!!!!
6) Enjoy your root access again :victory:
If anyone has any questions, just message me. I hope this was of help to anyone going through the same pain I had gone through.
For some more info on my phone.
- I'm running a I747m GSIII CM10.1.3.1d2att
- as for the root... well I can't give the link because i'm new to this site...
John Stuart
Click to expand...
Click to collapse
So you also deteled superuser from system/xbin/su..?