HOW TO HAVE ROOT AFTER JELLY BEAN OTA"Only for those who did OTARootKeeper process and still have no root."
For those who did OTARootKeeper process, and is not able to have root working properly.
I did all this after breaking my head for a few hours. Many are in this same situation that I was, hope i can help all.
Process:
. Once you have made the process of Backup and Temp-UnRoot in OTARootKeeper
. Once you have upgraded to the OTA Jelly Bean and restored root in OTARootKeeper
. And still having problems with root access.
. Open the PlayStore and search for SuperUser
. You will see that an update is available. Just update the SuperUser app and open it.
. On the main screen of SuperUser is showing the version of the binary that you have early installed via OTARootKeeper (ver. 3.0.3.2)
. Will be available an update of the binary (ver. 3.1.1). Just update the binary version.
. Once updated the root binaries, the root will work normally, giving permissions to all applications that you need.
OBS:
If you have problems with SuperUser, after do the process above, install the SuperSU app via PlayStore, and use it for root permissions.
I hope that I helped! If so, just thanks! :good:
This is not development selection..
Please move to general area..
Sent from my XT910 using Tapatalk 2
Please change the name of the thread (system version and leak) and move it to general section
Hit the thx button if i helped ya in anyways
That's a bit sad, but it still does not help me. I've definitely protected root with Voodoo, as it still says I have root, but when I click "temp unroot" it does nothing. Might Superuser from Koush do something wrong?
EDIT: Huh, I've found the way around. If you have backed up root with OTA Rootkeeper like me, but cannot restore it follow these steps:
1. Download Android Terminal from Play Store.
2. Open it, type in "cd /system/usr/we-want-root", confirm with Enter.
3. Type "./su-backup", confirm with Enter.
4. You should now see different prompt - ending with "#" instead of "$".
5. Type "mount -o remount,rw /system", confirm with Enter
6. Type "cp su-backup /system/xbin/su", confirm with Enter
Congratulations, you are now rooted. Beware, this method works only if you have backed up you root before OTA! If something is wrong after second step type "ls -l" and you should see "rwsr-s--- su-backup" - those "s" are is important, they mean you are able to get root access.
Related
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
smokin1337 said:
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
Click to expand...
Click to collapse
good looks bro.. worked perfect!!!!
evod3 said:
good looks bro.. worked perfect!!!!
Click to expand...
Click to collapse
Simply , you should have went to the official xda thread of super su by chain fire and should have flashed the zip. The zips removes the super user and replace it with super su
evo401 said:
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Click to expand...
Click to collapse
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Zeuszoos said:
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
Wrong! Now you cannot grant root access to any app since you don't have the binary.
If you do the 3rd step you will lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store and update the binary then remove the old superuser apk as smokin1337 said. Your steps are lengthy and will never work.
Or just flash the zip file.
Zeuszoos said:
Originally Posted by Zeuszoos
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work. Just make sure that it has Write access to the System partition. Even when in Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
mnomaanw said:
Wrong! Now you cannot grant root access
to any app since you don't have the binary. If you do the 3rd step you will
lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store
and update the binary then remove the old superuser apk as smokin1337 said.
Your steps are lengthy and will never work.
Click to expand...
Click to collapse
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Zeuszoos said:
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Click to expand...
Click to collapse
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
mnomaanw said:
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
Click to expand...
Click to collapse
No problem.
As for mounting it read/write, yes, that does need to be done. I should have included that. Thanks for noting it.
There is a utility that will mount your system partition as writable when you boot it up. It's called "mount r/w" or something like that. It's in the Google Play Market. I think it has an icon of a yellow folder with a lock, or something like that. Most people recommend against doing that and if you don't want to do it that way, as I'm sure you know, root explorer can mount it writable until you tell it not to, or reboot..
I installed the leaked ICS update, but I have apparently lost root. I tried using Voodoo, but it just says that it has been denied Superuser permissions and that there is no root backup available.
So I tried just plain rooting it using the Motofail method again, to no avail. It says that it is successful in completing the exploit.
However, no matter what app that requires root that I open, it says that the app has been denied Superuser permissions without even prompting me. Root checker says I am not rooted.
I went into the Superuser app, and I went to update the SU Binary. It says that Superuser has been granted Superuser permissions. But then it fails out at the end and says "This updater cannot update the su binary on phones that have some kind of write protection like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM manager."
I shouldn't even need to update the binary though, since it says I have the latest one installed.
What can/should I do? It's getting kind of annoying not having root on my phone.
Something along the same line happened to me too bro,I also made a thread about it but to no avail:-/ if you find something out,let me know and I'll do the same.
Sent from my DROID RAZR using xda premium
kevintstephens said:
I installed the leaked ICS update, but I have apparently lost root. I tried using Voodoo, but it just says that it has been denied Superuser permissions and that there is no root backup available.
So I tried just plain rooting it using the Motofail method again, to no avail. It says that it is successful in completing the exploit.
However, no matter what app that requires root that I open, it says that the app has been denied Superuser permissions without even prompting me. Root checker says I am not rooted.
I went into the Superuser app, and I went to update the SU Binary. It says that Superuser has been granted Superuser permissions. But then it fails out at the end and says "This updater cannot update the su binary on phones that have some kind of write protection like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM manager."
I shouldn't even need to update the binary though, since it says I have the latest one installed.
What can/should I do? It's getting kind of annoying not having root on my phone.
Click to expand...
Click to collapse
Try this on ics terminal
Code:
./system/su-backup
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
ln -s /system/su-backup /system/bin/su
Sent from my XT910 using Tapatalk 2
This also happened to me, and ive had no luck rooting either. I used the terminal trick and it says theres nothing to recover i su.
mcnabb311 said:
This also happened to me, and ive had no luck rooting either. I used the terminal trick and it says theres nothing to recover i su.
Click to expand...
Click to collapse
Of course, you need a su bkp first.
Here's mine
http://db.tt/L9TLf2xg
Cheers
Sent from my XT910 using Tapatalk 2
Thanks alot, i must try this.
---------- Post added at 07:46 PM ---------- Previous post was at 07:14 PM ----------
So if you dont have root access, will the terminal move the unzipped su file? How can you apply this to your sysytem? Voodoo doesnt give you options to search for the file either. Of course, nothing has superuser permissions without root either. I guess Im too much of a n00b.
Same here
Na dude its not noobish,im tryna figure out everything myself,I've been flashing since the hd2,so i know a couple things but this is just mind boggeling lol
I'm at a loss. I've downloaded your su-backup file, but I don't know how to move it to the /system folder, as it is write protected, and I don't have root to bypass that. And whenever I tried typing things in using the terminal, it just denied everything.
kevintstephens said:
I'm at a loss. I've downloaded your su-backup file, but I don't know how to move it to the /system folder, as it is write protected, and I don't have root to bypass that. And whenever I tried typing things in using the terminal, it just denied everything.
Click to expand...
Click to collapse
You can't move this file to system folder because you have a non-rooted device. Be patient, we are working hard on that....
My Razr Maxx installed the OTA ICS update today. There were no error messages. Everything seemed to run fine. And on top of that I thought that my root was preserved.
Well, I have an old version (3.0.3.2) of SuperUser intalled that I cannnot uninstall. I cannot mount /system/ as read-write using ADB. I can't mount /system/ as rw using Terminal Emulator on the phone. I tried the one-click script EternityProject EasyRootICS to install root and it seemed to work (no errors reported), but when I edited the batch file to get rid of all of the CLS (clear screen) commands, I was able to see that when it tried to write the new superuser app to /system/bin/ it's failing (with no error reporting).
So what do I do now?
The bottom line is that I need root, but I don't know how I can get root without getting rid of my old SuperUser installation first.
I have the exact same problem..... I can't get rid of Superuser, but I can't get access too use any root applications. SU denies all of them...
Go to this link here and where it says "Note: If you don't get root by other method root attempt with su and Superuser.apk already installed." download from that link.
http://www.mod2xtreme.com/showthread.php?13332-TOOL-ROOT-Razr-EternityProject-EasyRootICS-Win-Linux
It helped with Superuser not working properly.....
before i made the update i did a backup of the root with voodoo ota rootkeeper.
now after the update rootkeeper the box "root permission granted" is unchecked and i dont know how to change it.
i tried to delete the "su backup" but it didnt work.it is written that the su backup is deleted but when i restart the rootkeeper it is still there.
i found a thread which could help me :http://forum.xda-developers.com/showthread.php?t=1911261
(For those with 'partial' root after JB update - regain root).
with adb the command su works.
but the problem is when i start adb shell there is no device listed anymore.i still can browse through the directory of my asus prime but i cannot push files because then there is no device error.
when i quit adb and restart adb to run "adb devices" the device is listed but after i start adb shell there isnt any device listed anymore.
cheers
lumpilumpe
Don't delete the SU backup - that is all you have with root at the moment.
It isn't clear which steps you can do.
Push files to device (in any state, /data/local/tmp for example?)
SU within ADB shell?
remount /system within ADB?
Seems like you can make it, if you work out the right things to do...
thx for the fast reply. yeah su within adb.
step 1:adb shell
step 2:su
step 3: yeaaaaahh... i found my mistake!!!
thx again for your answer , i solved it now.
for everyone who has the same problem.follow the steps from these link :http://forum.xda-developers.com/showthread.php?t=1911261
i made a mistake before .
last question:what can i do next time to prepare myself a better way?
cheers
lumpilumpe
Q
UOTE=tshoulihane;34224306]Don't delete the SU backup - that is all you have with root at the moment.
It isn't clear which steps you can do.
Push files to device (in any state, /data/local/tmp for example?)
SU within ADB shell?
remount /system within ADB?
Seems like you can make it, if you work out the right things to do...[/QUOTE]
lumpilumpe said:
before i made the update i did a backup of the root with voodoo ota rootkeeper.
now after the update rootkeeper the box "root permission granted" is unchecked and i dont know how to change it.
i tried to delete the "su backup" but it didnt work.it is written that the su backup is deleted but when i restart the rootkeeper it is still there.
i found a thread which could help me :http://forum.xda-developers.com/showthread.php?t=1911261
(For those with 'partial' root after JB update - regain root).
with adb the command su works.
but the problem is when i start adb shell there is no device listed anymore.i still can browse through the directory of my asus prime but i cannot push files because then there is no device error.
when i quit adb and restart adb to run "adb devices" the device is listed but after i start adb shell there isnt any device listed anymore.
cheers
lumpilumpe
Click to expand...
Click to collapse
I like SuperSU instead of SuperUser.
Check to see if you still are rooted by installing another app that requires root. (SuperSU will do).
What I did was simply have SuperSU forget OTA Rootkeeper, then close OTA Rootkeeper completely meaning ending it completely and then opening it again and having SuperSU ask if I want to grant it SU permissions again.
I don't remember if SuperUser lets you forget an app so it asks you again or not.
I succesfully updated my Samsung Galaxy S3 from Android 4.2.2. to 4.3 after rooting my Phone.
However, SuperSU doesn't work anymore, giving the message "If you upgraded to Android 4.3 you need to manually re-root".
I cannot find an answer in the forums here on XDA developmers.
Can anyone help me?
Thanks in advance,
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Rooted 4.3 and installed SuperSU
morwit99 said:
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Click to expand...
Click to collapse
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Same problem here
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
otto68 said:
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
Click to expand...
Click to collapse
if you have supersu or super user already than just download update-supersu from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and flash it through the recovery mode( custom recovery preferred).
xprivacy / reboot to recovery
In my case I was getting false alerts as xprivacy has blocked system access. (eg was with AdAway) Cleared those apps in XPrivacy and all worked find then.
Also you can try to go into recovery and the try to reboot. You may get message to reinstate/fix SU.
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
You rock, I had re-rooted my updated Android 4.3 but my SuperSU was not usable anymore. Redownloaded it, allowed it to update SU Binary, disabling Knox, and viola! Root galore
suyash1629 said:
if you have supersu or super user already than just download update-supersu from ...LINK REDACTED.. and flash it through the recovery mode( custom recovery preferred).
Click to expand...
Click to collapse
that fixed it for me..thanks :good:
Tried all these steps on the new 4.3 MK6 ROM. Does not work for me. I cant find the Root access option itself in developer options. I already tried flashing CF-Autoroot multiple times after factory reset, using odin. I CWM still says binaries outdated and SuperSU doesn't work work even after updating from play store. Later i tried flashing supersu via the recovery mode. Still no success. Any suggestions?
Edit:
Another factory reset and flash did it. I don't know how. But it is fixed now.
By following your step, my superuser icon is gone...
Stuck in ODIN
Everytime I try to root S3 LTE via ODIN with CF auto root, it gets stuck there, need some help please, have had to use kies's recovery tool 3 times today because of that
i dont have this function
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
Hi, I dont have this function in my phone, nowhere, please help me?
fragiepacino said:
Hi, I dont have this function in my phone, nowhere, please help me?
Click to expand...
Click to collapse
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
no
tallman43 said:
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
Click to expand...
Click to collapse
the root function in the developers section, nowhere i can tick it
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Sorry I thought you wanted to know how to get into developer settings....This thread is from 2013 i don't have S3 anymore if your trying to get root to work just follow some of the other suggestions posted.:good:
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Here you don't have the "root access" setting ?
Sent from my GT-I9300 using XDA Free mobile app
s3 i9305 supersu binary problem
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
—------------------------------------------------------
I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.
Please help.
I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:
Root access not properly configured or granted.
Superuser Application Status
Installed: SuperSU by Chainfire - version 2.46
System Files Status
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User Account Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
Optional: ADB Shell User Status
Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional: System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
_----------------------
So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.
Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.
Made sure no double superuser programs running.
Got rid of Knox.
Tried to custom install Supersu update, says invalid certificate.
I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.
Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.
Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix.
PS. If this post is i wrong place please advise where itshould be.
Thanks
S :good:
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
I can't find my phone as one of the packages. I have an Alcatel phone.
root my mobile but didn't get access
rooted my phone micromax a116, all proccess done wel as shown in tutorials. But root checker says that "root access is not properly installed on this device". Please tell me what to do?