I had my phone rooted on stock OS and Superuser worked fine. But when I installed the Sprint Jelly Bean ROM, Superuser stopped giving my apps permissions. Am I supposed to re-root after installing ROMs?
SeparateElite said:
I had my phone rooted on stock OS and Superuser worked fine. But when I installed the Sprint Jelly Bean ROM, Superuser stopped giving my apps permissions. Am I supposed to re-root after installing ROMs?
Click to expand...
Click to collapse
Have you tried opening SU and enabling permissions??
mine did this, then su updated, all is good now
message brought to u by my JellyBombed GalaxyS3
Related
Hi guys, I have a bit of a problem with 4.1.2 Jelly Bean and Superuser 3.1.3. After OTA update to 4.1.2 and flashing back latest touch CWM recovery, I flashed latest SuperUser 3.1.3 (i guess). In recovery everything works fine, it writes that everthing was istalled successfully, but when I try tu run SuperUser app or any app that requires root, message pops out that SuperUser has crashed and I have option to send log to google which i don't want to...can you please help me and tell me where is the catch? Thanks a lot in advance
I have Galaxy Nexus Maguro, JZO54K, Official 4.1.2 JB, Unlock, CWM touch
Use SuperSU instead...it's pretty much replaced the old SU app
http://forum.xda-developers.com/showthread.php?t=1538053
Thanks, it works Yipee
Hello,
So I recently had my SGS3 rooted until I stupidly installed the OTA update that Att released. Everything was good, but now my phone was unrooted and I was unable to reroot using conventional rooting methods. Now, I figured that it would be good to install a custom ROM in order to re root my phone and put jelly bean on it. However, when I went into the Clockwork mod recovery, it gave me a status 7 error while trying to install the latest nightly build of CyanogenMod 10. I also cleared out all the caches and did a factory reset. Does anyone know what I might be doing wrong?
Thank you very much for your help!
wickbok said:
Hello,
So I recently had my SGS3 rooted until I stupidly installed the OTA update that Att released. Everything was good, but now my phone was unrooted and I was unable to reroot using conventional rooting methods. Now, I figured that it would be good to install a custom ROM in order to re root my phone and put jelly bean on it. However, when I went into the Clockwork mod recovery, it gave me a status 7 error while trying to install the latest nightly build of CyanogenMod 10. I also cleared out all the caches and did a factory reset. Does anyone know what I might be doing wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
Download the file below file to your S3 and install it via Mobile Odin to get CWM back.
Well, from what I read, you aren't rooted anymore.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
wickbok said:
Hello,
So I recently had my SGS3 rooted until I stupidly installed the OTA update that Att released. Everything was good, but now my phone was unrooted and I was unable to reroot using conventional rooting methods. Now, I figured that it would be good to install a custom ROM in order to re root my phone and put jelly bean on it. However, when I went into the Clockwork mod recovery, it gave me a status 7 error while trying to install the latest nightly build of CyanogenMod 10. I also cleared out all the caches and did a factory reset. Does anyone know what I might be doing wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
If I recall correctly, Status 7 means you have an older/not-supported version of CWM installed. Your best bet is going to be to download the Samsung Galaxy S3 QCom ToolKit, and use that to install the proper CWM version. Then you will be able to wipe/install a custom ROM.
AS the title explains, I was running rooted ICS and did the update to JB over Kies. The root broke, I am trying to figure out the steps I need to take to put the phone back into rooted JB. SuperSU and Titanium backup are both dead - uninstalled SuperSU and went to reinstall it but it says I cant.
SRT_Outlaw said:
AS the title explains, I was running rooted ICS and did the update to JB over Kies. The root broke, I am trying to figure out the steps I need to take to put the phone back into rooted JB. SuperSU and Titanium backup are both dead - uninstalled SuperSU and went to reinstall it but it says I cant.
Click to expand...
Click to collapse
Just root the phone again the same way you did it for ICS.
SRT_Outlaw said:
AS the title explains, I was running rooted ICS and did the update to JB over Kies. The root broke, I am trying to figure out the steps I need to take to put the phone back into rooted JB. SuperSU and Titanium backup are both dead - uninstalled SuperSU and went to reinstall it but it says I cant.
Click to expand...
Click to collapse
Use the instructions on this thread to root again.
Hey guys, sorry my first post is a question but I really can't seem to find the answer on the interwebz.
I originally rooted via galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-easiest-method<- this guide and it worked flawlessly.
Then, I tried to update OTA to 4.1.2 but couldn't due to my root... so I used Supersu to "full unroot."
Afterwards, I wiped my cache to download the update OTA and installed. I then tried to re root my phone but no luck.
I also tried Chainfire's auto root but it also didn't work. I did try downloading the superuser app on Google Play but it didn't work either.
Anyway, I am stuck. I hope you guys can help!
Thanks
F4injected said:
Hey guys, sorry my first post is a question but I really can't seem to find the answer on the interwebz.
I originally rooted via galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-easiest-method<- this guide and it worked flawlessly.
Then, I tried to update OTA to 4.1.2 but couldn't due to my root... so I used Supersu to "full unroot."
Afterwards, I wiped my cache to download the update OTA and installed. I then tried to re root my phone but no luck.
I also tried Chainfire's auto root but it also didn't work. I did try downloading the superuser app on Google Play but it didn't work either.
Anyway, I am stuck. I hope you guys can help!
Thanks
Click to expand...
Click to collapse
Are you on 4.1.2 now? the AT&T OTA update?
I tried so many times just to update to 4.1.2 and kept it stock but it just wouldnt update. AT&T customer service couldnt help with anything. I read there was a lot of people having this problem.
My solution was I rooted, installed twrp and just found a TW based ROM and installed that. I recommened cleanrom, skynote and the jedi. Those were the only ones I tried and used.
chousayz said:
Are you on 4.1.2 now? the AT&T OTA update?
I tried so many times just to update to 4.1.2 and kept it stock but it just wouldnt update. AT&T customer service couldnt help with anything. I read there was a lot of people having this problem.
My solution was I rooted, installed twrp and just found a TW based ROM and installed that. I recommened cleanrom, skynote and the jedi. Those were the only ones I tried and used.
Click to expand...
Click to collapse
Yes, I guess I am one of the lucky ones that was able to get the update OTA from AT&T.
I couldn't originally because I thought it was my root. The update kept saying memory full. So I unrooted and it actually still wouldn't work. I then restarted into recovery and cleared my cache. Then I tried it and it worked, so I'm not too sure.
I ran the chainfire root what I thought was successfuly, it said rooting rebooting and all but I still have no superuser. Im running 4.1.2 someone help me
dub913 said:
I ran the chainfire root what I thought was successfuly, it said rooting rebooting and all but I still have no superuser. Im running 4.1.2 someone help me
Click to expand...
Click to collapse
If you can still get into your custom recovery, try flashing [ROM][ZIP]Stock Rooted Deodexed/Odexed MD4 with SuperSU/Busybox 1.20.2
dub913 said:
I ran the chainfire root what I thought was successfuly, it said rooting rebooting and all but I still have no superuser. Im running 4.1.2 someone help me
Click to expand...
Click to collapse
Most likely the SuperSU app is installed but being blocked by Knox. Go to the app store and search SuperSU. Update it. Then it should appear on the phone. Run it. It will ask if you would like to disable Knox. Answer yes. After that you should have root.
I can't get into recovery mode. When I try it runs chainfire again and nothing happens