HI folks,
does flashing slimkat latest build, unroot the phone?
i recently migrated from Resurrection Remix ROM 4.4 to SlimKat 4.4
How ever when i tried to restore my apps using Titanium Backup, it shows me an error saying that the phone is not rooted. When i boot into recovery, i already have a TWRP recovery. Now i am not sure whether my phone is rooted or not? I even tried to install SuperSU by chainfire, but it says i need to install it's binary from recovery, i am not sure how do i do that.
Kindly guide me to solve this problem.
Do i need to root my phone again? If Yes, which rooting method to use? If No, then what am i missing?
Thanks
grishm said:
HI folks,
does flashing slimkat latest build, unroot the phone?
i recently migrated from Resurrection Remix ROM 4.4 to SlimKat 4.4
How ever when i tried to restore my apps using Titanium Backup, it shows me an error saying that the phone is not rooted. When i boot into recovery, i already have a TWRP recovery. Now i am not sure whether my phone is rooted or not? I even tried to install SuperSU by chainfire, but it says i need to install it's binary from recovery, i am not sure how do i do that.
Kindly guide me to solve this problem.
Do i need to root my phone again? If Yes, which rooting method to use? If No, then what am i missing?
Thanks
Click to expand...
Click to collapse
the other day i installed one of the roms based on slimkat and my es file explorer wouldn't give me root access to /system nor mount the system to R/W rebooted the phone few times and still no luck so went back to the other 4.4.2 version that was working for me,i am not sure what goes wrong when we flash slimkat roms
It's already rooted. Go to developer options and set root access to apps.
You get developers options in main settings after you click build name in about multiple times.
Sent from my GT-N7100 using Tapatalk
Related
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 have an i747M, from Fido (rogers) running the stock 4.3 firmware. yesterday i tried to root it using odin to install CWM, and then CWM to install supersu.
after successfully installing supersu, i restarted the phone, and got knox blocking the app. i updated it from Play, but then i couldn't open it, and it said it can't install the binary. when my phone asked to update the security certificates, i (stupidly) agreed.
i downloaded the .zip for supersu 1.89, and tried installing that, with the same result, but this time i also can't uninstall supersu.
i've bumped my binary counter, but i'm back to basically stock now.
my goal is to install aokp. is there a way to do it without gaining root first?
if i install CWM through odin, can i flash the aokp rom from CWM?
will the phone reset the recovery?
is this risky?
You could try installing a pre-rooted Rogers rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
I was not able to find a pre-rooted 4.3 for Fido and, since you intend to install a custom rom and recovery, the pre-rooted Rogers ROM might be a good place to start.
It's there a reason to install a rooted rom before aokp? As far as I can tell, I can install aokp without rooting at all.
or am I missing something?
Sent from my SGH-I747M using xda app-developers app
Yes, you can just install a custom ROM without rooting first.
I mentioned the prerooted ROM because you post said you wanted to install su.
Ok, please confirm i have this procedure correct:
1. i use Odin to install CWM
2. boot straight into CWM
3. from inside CWM, i flash the AOKP zip file, and then the gapps zip file
my understanding is that this will keep cwm as my recovery and install aokp with gapps.
am i missing anything?
audit13 said:
Yes, you can just install a custom ROM without rooting first.
I mentioned the prerooted ROM because you post said you wanted to install su.
Click to expand...
Click to collapse
Milothicus said:
Ok, please confirm i have this procedure correct:
1. i use Odin to install CWM
2. boot straight into CWM
3. from inside CWM, i flash the AOKP zip file, and then the gapps zip file
my understanding is that this will keep cwm as my recovery and install aokp with gapps.
am i missing anything?
Click to expand...
Click to collapse
Just make sure you flash a tar version of CWM that is meant for your phone.
I can't really speak about 4.3 because I'm on 4.1.2 but the method you described is the same method I used.
Milothicus said:
I have an i747M, from Fido (rogers) running the stock 4.3 firmware. yesterday i tried to root it using odin to install CWM, and then CWM to install supersu.
after successfully installing supersu, i restarted the phone, and got knox blocking the app. i updated it from Play, but then i couldn't open it, and it said it can't install the binary. when my phone asked to update the security certificates, i (stupidly) agreed.
Click to expand...
Click to collapse
If you want to kill Konx to enable root you can flash this knox removal script: http://forum.xda-developers.com/showthread.php?t=2507931
If you are just going to flash AOKP via CWM, this may not be necessary, but this is the answer to your Knox problem.
So I updated to stock 4.3(I747M) via Odin, then flashed TWRP with Odin, then Flashed a 4.4 ROM with TWRP.
The Super SU app is failing to update the binary. And it's not giving root access to apps. Does this have anything to do with the MK5 bootloader?
I can't seem to find a fix? If someone could point me in the right direction, that'd be great.
Thanks!
Try flashing a another ROM such a Validus or CM11 as ROMs are pre-rooted.
Also, I prefer Philz Touch over TWRP. Maybe the recovery program makes a difference?
solaris11 said:
So I updated to stock 4.3(I747M) via Odin, then flashed TWRP with Odin, then Flashed a 4.4 ROM with TWRP.
The Super SU app is failing to update the binary. And it's not giving root access to apps. Does this have anything to do with the MK5 bootloader?
I can't seem to find a fix? If someone could point me in the right direction, that'd be great.
Thanks!
Click to expand...
Click to collapse
I did this procedure with the same bootloader on a Koodo phone, no problem. I I rooted and installed TWRP 2.6.3.1 and then I flashed Quantum ROM. Which ROM did you flash? (Oh, I see now you tried OmniRom.) Only difference with how I did it is I had already taken the stock OTA from Koodo.
jmppe3 said:
I did this procedure with the same bootloader on a Koodo phone, no problem. I I rooted and installed TWRP 2.6.3.1 and then I flashed Quantum ROM. Which ROM did you flash? (Oh, I see now you tried OmniRom.) Only difference with how I did it is I had already taken the stock OTA from Koodo.
Click to expand...
Click to collapse
Yeah I bricked my phone messing with bootloaders...used an SD boot image to get to download mode and odined stock 4.3. Odined twrp. Twrp flashed omni's latest build. Does omni not come prerooted? That doesn't make much sense. I'll try another ROM.
It should also be noted I tried rooting stock 4.3 but it really didn't like that at all.
Sent from my SGH-I747 using xda app-developers app
audit13 said:
Try flashing a another ROM such a Validus or CM11 as ROMs are pre-rooted.
Also, I prefer Philz Touch over TWRP. Maybe the recovery program makes a difference?
Click to expand...
Click to collapse
On validus now...same thing
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Weird that you don't have root. I have Validus and apps like root explorer ask for root access which I can grant.
Maybe the 4.3 bootloader is causing a problem?
audit13 said:
Weird that you don't have root. I have Validus and apps like root explorer ask for root access which I can grant.
Maybe the 4.3 bootloader is causing a problem?
Click to expand...
Click to collapse
Yeah, this whole thing is weird. I had the 4.3 bootloader (rooted at end of Dec 2013) and didn't have an issue. I went to Quantum ROM FWIW. Have you tried a full wipe (system, cache, dalvik, data) with a clean flash of the ROM?
I am having some rooti issues with my i747, and I already have a custom rom installed. After installing SlimKat 4.4.4 today, (previously running Liquidsmooth v2.1 4.2.2), I go to check my root privileges using RootChecker, and it tells me that I do not have proper root access. Given that this device has been rooted prior to my installation of SlimKat, and the fact that Superuser has been working fine for me in the past, I try to re-root using ODIN, and that wouldn't work either. Also, updating Superuser is not an option, due to my root access being lost. Is there a way to root my device without having to go back to the stock ATT rom, or is that my only option?
~ZenithV99
Try flashing this in recovery.
https://www.dropbox.com/s/h6mifyhsp6z9d04/UPDATE-SuperSU-v2.01.zip
I am currently running the Hyperdrive Rom. It has been a while since i flashed it. I seem to remember that I did not root my phone because the rom had root priv. I only installed the custom recovery. I would like to switch over the AOKP rom but I am not sure if I need to root first or if the rom has root. and also, if I do root will I then have to install a recovery again after. would also appreciate any advise on which root method is best. thanks for any help.
Check the change log for the rom and compatibility with your current Android firmware version. Most of the time after you root you'll be asked if you want custom recovery.
Sent from my SM-N900T