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
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.
I recently flashed the official 4.3 update that came out a few days ago. I have clockwork mod recovery and I flashed the supersu zip, which failed to work. I then flashed cf auto root via odin and now it says super su has stopped working when I try to gain root access. I really need root access because I back up my app data via helium backup (GREAT app btw). Please help! Thanks :crying:
hey guys. lurker turned new poster here at XDA. a friend of mine turned me on to this a while back when he introduced me to the world of rooting. I've recently bought a Galaxy S III (SGH-i747), and I've been trying to root it using mskip's unified toolkit (http://forum.xda-developers.com/showthread.php?t=1979290). I got it rooted once, but eventually bricked it when trying to get 4.4 on it, and had to reinstall the stock 4.1.1 rom on it and lost the root in the process.
I'm completely new to all this, and I'm still trying to figure it out. I've been searching as much as I can and reading a lot, but I'm not sure if there's something I'm missing here. when I try to root it lately using the toolkit, it gets stuck in the process after I exit Odin, and will never progress.
before when the root was actually in place, I tried to install a custom OS after doing a full wipe of the system, and it never would install. I tried it with TWRP and CWM, and there was no success with either of them. the one peculiar thing, however, is that I could never get it to install with the "ALLINONE" option. when I got it to work that once, I had to install it each individually.
is there some sort of guide out there that would make this easier for me to get 4.4 on the phone? or will someone be able to help me through the process?
thank you for your time!
I just rebooted my comp, reinstalled the drivers for the phone through the toolkit, and gave it one more shot at rooting it (option 1 in the program), and this is what the process looked like.
*see attached image*
I *always* get stuck at the "pushing superuser.apk and su binary.." part.
any thoughts?
hachikid said:
I just rebooted my comp, reinstalled the drivers for the phone through the toolkit, and gave it one more shot at rooting it (option 1 in the program), and this is what the process looked like.
*see attached image*
I *always* get stuck at the "pushing superuser.apk and su binary.." part.
any thoughts?
Click to expand...
Click to collapse
I used this when I first rooted my I747. http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
My Bell s3 was on 4.1.2. I rooted by installing a rooted rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
Do not flash a 4.1.1 or 4.1.2 rom if you have a bootloader from 4.3.
when I got the phone, it had 4.1.2 on it. when I bricked it, I flashed a stock 4.1.1 ROM on it, and that's what I've been using as my base ROM.
Boomer1605: I'll try that when I get home.
anyone else know what is up with the place I get stuck at during the toolkit way?
My Bell s3 was on 4.1.2 when I got it. SInce I needed to unlock it and didn't want to pay, I installed the stock Bell 4.1.1 firmware from here: http://www.sammobile.com/.
After using the menu option to unlock the phone and confirm that it was unlocked, I flashed the pre-rooted Bell s3 4.1.2 rom.
Everything worked perfectly, no errors or issues at all.
Cool! Can I find a pre-rooted 4.1.1 AT&T rom on that site? I can't really look at that link cause I'm currently at work.
Pre-rooted roms are here: http://forum.xda-developers.com/showthread.php?t=1739426
I was able to install Root Explorer on my pre-rooted ROM and delete a tonne of Samsung apps.
I was able to install a pre-rooted version of 4.1.1, and I did a system/data/cache/dalvik wipe from the TWRP screen, but when I tried to install both Liquid Smooth and Omni Rom, it failed. I even restarted and didn't wipe, and it still failed. not sure where to go from here... :/
tativle coast
totally got it to work! I skipped using the toolkit to install TWRP, and used GooManager to use the latest TWRP. worked like a charm! currently running on Liquid Smooth 4.4.2!
thanks for the rooted copy of 4.1.1!
hachikid said:
totally got it to work! I skipped using the toolkit to install TWRP, and used GooManager to use the latest TWRP. worked like a charm! currently running on Liquid Smooth 4.4.2!
thanks for the rooted copy of 4.1.1!
Click to expand...
Click to collapse
Awesome! Congratulations. For future reference, TWRP also had tar images for use with Odin.
I am S-OFF and using latest version of Android Revolution HD (22.2) after having issues with trying to get lollipop, I revert back to Kit Kat. Everything is working fine, except when I'm trying to use SuperSu or Xmodule, I get an error stating 'there is no SU binary installed...' or that my phone is not rooted (it is). Anyone know why I would get this error?
bloodclaw said:
I am S-OFF and using latest version of Android Revolution HD (22.2) after having issues with trying to get lollipop, I revert back to Kit Kat. Everything is working fine, except when I'm trying to use SuperSu or Xmodule, I get an error stating 'there is no SU binary installed...' or that my phone is not rooted (it is). Anyone know why I would get this error?
Click to expand...
Click to collapse
You could try updating SuperSU by flashing the newest release. I have this problem on some ROMs when the recovery I'm using isn't compatible, I much prefer TWRP but some ROMs flash better with PhilZ.....So you might make sure you're on the latest version of TWRP or the compatible version of PhilZ.
If all else fails, try re-flashing your ROM or a different one and coming back to ARH if you prefer that one.