Didn't want to hijack that other thread, so I thought a more explicity thread might help others.
So I followed http://www.youtube.com/watch?feature=player_embedded&v=iMYMR3_Vk8I and got my phone unlocked. I'm unsure what to do next to get a "stock" phone rooted. All I want is to have my phone rooted so I can run SU apps. There are a couple options from the tool, of which I'm not sure what is what:
1. Flash a Recovery (TWRP 2.1) - Not sure what this is for, should I flash it? What does it do?
2. Kernels - Do I download a kernel like: http://forum.xda-developers.com/showthread.php?t=1762537 and Flash Kernel?
3. Perm Root - From the name this sounds like what I want... but can I run it on my freshly restored/unlocked phone? Do I need to run this after one of the above (or both) steps?
1. Yes. A recovery is, put simply, a tool that can be used to flash things to your phone (e.g. custom ROMs and mods). You will need a recovery in order to achieve permanent root, so flashing the recovery is definitely a good idea.
2. The thread that you linked to does not contain a kernel, it contains a custom ROM. Since we do not have any customized kernels for this phone yet, skip the flash kernel step entirely. You may want to go back and use it if a kernel is developed that you prefer, but for now, there are no kernels to flash.
3. Perm root is the step that you want, but you need to flash the recovery first. The perm root script will run and then eventually boot you into the recovery, which you must use to flash SuperSU.zip which is the package that gives you root on your current ROM.
polarimetric said:
1. Yes. A recovery is, put simply, a tool that can be used to flash things to your phone (e.g. custom ROMs and mods). You will need a recovery in order to achieve permanent root, so flashing the recovery is definitely a good idea.
2. The thread that you linked to does not contain a kernel, it contains a custom ROM. Since we do not have any customized kernels for this phone yet, skip the flash kernel step entirely. You may want to go back and use it if a kernel is developed that you prefer, but for now, there are no kernels to flash.
3. Perm root is the step that you want, but you need to flash the recovery first. The perm root script will run and then eventually boot you into the recovery, which you must use to flash SuperSU.zip which is the package that gives you root on your current ROM.
Click to expand...
Click to collapse
Thanks polarimetric for explaining! Hopefully your explanations and my slight quirks below can help some others.
The TWRP reflash worked fine. I had an issue with the Perm Root though... for some reason the SuperSU.zip wasn't actually getting copied over to the phone before it was rebooted into recovery. I ended up mounting the sdcard and manually copying over SU/SuperSU.zip to my sdcard. At that point I ran Perm Root again (which in my case just reboots into recovery). From there I clicked "Install" and selected the /sdcard/SuperSU.zip file. It installed and rebooted.
Successfully rooted!
More advice pleae.
polarimetric said:
3. Perm root is the step that you want, but you need to flash the recovery first. The perm root script will run and then eventually boot you into the recovery, which you must use to flash SuperSU.zip which is the package that gives you root on your current ROM.
Click to expand...
Click to collapse
I flashed a recovery yesterday since I needed to recover. After that my endlessly booting appliance booted successfully.
Now I want to Root. I tried this using the Hasoon2000 thing yet and got a "Simply Brilliant" screen when I rebooted into recovery but then got could not connect message when I tried to permanently root.
Do I need to flash a different recovery?
Wow, this thread got my hopes up til I saw it was bumped.
As of several months ago, we lost the ability to root:
http://forum.xda-developers.com/showthread.php?t=1792514
So, until an exploit is found or verizon says we can do it, we can't root.
Hesacon said:
Wow, this thread got my hopes up til I saw it was bumped.
Click to expand...
Click to collapse
Yeah, the same thing happened to me. I tried HTCDev unlock last night and it didn't work, so I was very surprised to see that as the most recent post. Now I'm extremely disappointed.
i hope i am not getting anyone elses hopes up either.... but man i am disappointed
This phone isn't even relevant anymore... I don't know why Verizon gives a **** about locking us out.
Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
Do I have root?
First you install the unlock APK, unlock it...Install goo beta, Install Open-Script Recovery, reboot and ill have TRWP? and be able to install custom roms?
IM READY TO JUMP SHIP!
You have your recovery to install everything.....
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
It has its own recovery? or do i need to install one...
David522d said:
It has its own recovery? or do i need to install one...
Click to expand...
Click to collapse
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
also a video showing you how to flash a custom rom, with TWRP and goo manager, is there also
demandarin said:
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
Click to expand...
Click to collapse
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Anyone ?
I don't know about goo manager but I flashed cwm touch with fastboot (normal cwm didn't work and twrp wasn't out)
Sent from my sgs2 running cm9
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Yeah steps sound good. you could always flash a ROM that has root. I dont think you need root to install twrp. Double check though. post in twrp thread to make sure.
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
David522d said:
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
Click to expand...
Click to collapse
There is nothing that will work 100%, but its pretty close, maybe 98%? Anytime someone does anything with the bootloader, recovery rom, or OS rom, there is a chance for bricking: interuption in the write process, loss of power, corrupted dl (crc check should catch most of those). If your worried about bricking it, leave your TFP stock and await the OTA's - that way if it gets bricked by Asus then they are responsible and you havent nullified your warranty.
Unlocking the bootloader allows the use of non stock bootloaders/recoveries to be installed and used. From the new bootloader/recovery, you can install a rom that either has root, or not. You don't even have to change roms after unlocking. The 2 are independent.
Right -
Unlocking with the APK does not root or in any other way modify or prep the prime for what you're about to do. Depending on your stock ROM revision this is either very easy or a complete pain in the ass, I'll provide both versions:
For Stock ROM ending .15 or earlier -
* DO NOT RUN THE GOO IM.MANAGER FIRST. Follow these steps below.
* Download Sparky's APK to root - it's in the development forum for the TF Prime. Run it. This will get you root access on the system. It's automated and practically idiot proof, just follow the on screen instructions.
* If you're going the Team Win route, once rooted, load up the Goo.im manager, then follow the instructions as per a rooted installation for getting TW Recovery into place. This is pretty painless really and works automatically, approve the Superuser permissions as required. Once the recovery is in, you can reboot into it and then get with the flashy.
-----
If you're on the Stock ROM ending .21, you're going to have to do what I did. As you're already unlocked using the BLOB files to downgrade -will- result in a hard brick. SO!
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
Hope this helps.
This whole blob thing is new for me since i have always insta-rooted, and CWM'ed any android device i get; but from what I've gathered, it is used by ASUS to lowlevel write the os on locked systems, similar to the way nvflash dumps img's directly to the memory. Once your unlocked with the CWM or twrp, then you can no longer use blobs, just the rom zips. The recovery rom handles the unpacking and dumping of the kernel and OS into the appropriate partitions. Some roms are zipped with install scripts that wipe your cache, user space and dalvik - but its always a safe bet to do that anyways.
Nice writeup Hobbesian
Well, some blobs are fine, but generally they're strictly either Team Win Recovery or Clockwork mod recovery suites, and they need to be slipped in using fastboot (I believe ROM manager and GOO managers use their own scripts to handle installation) as a rough rule. The "big" BLOB files which Asus puts out are a guarantee to hardbrick an unlocked device (some days I wonder if it would kill Asus to offer a route to re-lock and re-stock a device on the proviso that if you brick it doing so you're still out of warranty).
That said - Virtuous Prime is definitely an excellent first step into Custom ROM tinkering, it gives you root and all the associated useful features, as well as the ability to start experimenting with more feature heavy ROM builds such as Cyanogen and AOKP Cornerstone. They're even nice enough to include a partially tweaked build.prop which saves you a lot of the work in modifying that.
I should point out my guide is relevant only if you already applied the unlock APK to your system, if you haven't done so, there's alternative routes including the downgrade blob option to get root without unlocking your device.
paddycr said:
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
Click to expand...
Click to collapse
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
David522d said:
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
Click to expand...
Click to collapse
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
EDIT: if you're in fastboot and you cannot get adb to recognize your prime you need to install the correct drivers for your pc/mac. Hobbesian describes how to do this a few posts above this. In his nice write up he also describes how to flash TWRP directly from fastboot. If you want TWRP, follow his instructions since you'll have less messing around to do.
paddycr said:
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
Click to expand...
Click to collapse
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
David522d said:
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
Click to expand...
Click to collapse
Yes, all of the roms will have root. Hit my thanks button if it works for you
paddycr said:
Yes, all of the roms will have root. Hit my thanks button if it works for you
Click to expand...
Click to collapse
Would it be easier to install CWM, then install TWR
David522d said:
Would it be easier to install CWM, then install TWR
Click to expand...
Click to collapse
I think both ways are the same. There's no correct answer to that. It depends on whether you would prefer to use CWM or TWRP.
I followed a tutorial to successfully root my phone in the past, but I need to do it again and want to understand it a bit better this time. (I'm doing it using command-line heimdall from Ubuntu.) Doing "sudo heimdall flash --recovery recovery.img --no-reboot", the tutorial provided a recovery.img which went on to install CWM. Then from within the rooted phone I installed another custom recovery. But do I need to do this as a 2-step process like this, or can I simply for the first time on an UNrooted phone do "sudo heimdall flash --recovery SOME-OTHER-RECOVERY.img --no-reboot"?
The tutorial also provided a CWM-SuperSU-v0.87.zip. What's actually the purpose of this, and do I even need it?
It also came with an s3pit.pit, but I didn't actually do anything with this. Did the 'heimdall' command that I ran do something with this, or is it safe to do the rooting process without it?
I'm asking because I'd like to root my phone not blindly following one tutorial which provided its own files (http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-linuxubuntu/). Surprisingly there are no other decent tutorials out there on rooting this phone from Ubuntu, any ideas?
You can flash any compatible recovery in step 1. I see no reason to flash something you don't need. I recommend philz recovery (link in signature) but twrp is good. I would stay away from cwm as its not great if you want to go to 4.2 android roms
Having a recovery is one thing but actually you're still not rooted. You need recovery to flash a zip which will give you root. Unless you just want to flash a custom rom, in which case you only need the recovery and can skip flashing root stuff
Sent from my GT-I9300 using Tapatalk 2
I wasn't aware of these distinctions, thanks. What alternative zips that give me root could you recommend? I would rather use one that is on xda-developers rather than on a blog post on some random website. Does it need to be compatible with the recovery, or would any 'root zip' meant for the i9300 work?
So is it possible to root the stock default ROM by just flashing a root zip using the stock recovery? Or is a custom recovery needed for this?
Roots are in Development section as said CWM is rather out of date now .
Both TWRP and Philz work well .
jje
I think I have misunderstood. In the first response it said "You need recovery to flash a zip which will give you root", which I assumed was the "CWM-SuperSU-v0.87.zip" I mentioned in the original post. I'm wondering about alternatives for this zip, not for the recovery (for the recovery I'll use Philz or TWRP as has been suggested).
iamthemandroid said:
I think I have misunderstood. In the first response it said "You need recovery to flash a zip which will give you root", which I assumed was the "CWM-SuperSU-v0.87.zip" I mentioned in the original post. I'm wondering about alternatives for this zip, not for the recovery (for the recovery I'll use Philz or TWRP as has been suggested).
Click to expand...
Click to collapse
You don't need an alternative. It contains 2 things. The su binary (what gives you root) and the super user app (a graphical "gatekeeper" to root). If you're applying root to a handset, you'll be using these things
Sent from my GT-I9300 using Tapatalk 2
Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
I was just been going through different forum threads and found that most people find it difficult to root there device,
So I decided to write a easy tutorial to do that(not ment for Android 5.0 Lolipop, yet)
things you should know before following this:
a. it MIGHT(not necessarily)trigger KNOX(on samsung some devices)
b. you need unlocked bootloader in case you have a sony device.
Click to expand...
Click to collapse
these are the steps you need to follow to root your device, it is a general method and SHOULD work on almost all devices(might not work for few):
1. First of all you are supposed to know what device you are using, and if you know what device you are using, you are ready to proceed
2. Next thing you would need to find is the process needed to flash image/md5 to the device you want to root(might trigger KNOX)(unlocked bootloader needed)
3. So if you don't know how to flash image/md5 to your device, just search here, on XDA for how to install cwm recovery(for example) on *your device*(might trigger KNOX, google it to know if your device have it or not, will void your warranty)(unlocked bootloader needed)
4. Cwm recovery is a custom recovery(few more are there too) for almost every device (you can make one if its not available yet, just search XDA)(if not, this is probably not a process you can follow, find some other)
5. When you have successfully installed the cwm recovery to your device, then you would need to know how to enter recovery mode on your device, generally, holding power+volume up keys for few seconds when the device is off will get you to recovery mode, and on Samsung devices, it's power+home+volume up keys that are supposed to be kept pressed to get to recovery mode, and if any of these don't works, just google "how to enter recovery mode on *your device*"
6. Now you need to download a supersu update zip from: HERE.
7. Place it anywhere on your phone and now turn off your device and boot to recovery mode (by process explained above)
8(a). When you enter recovery (any custom recovery you can find), there's an option to install zip from SD card (external or internal)
8(b). Select it and find out the supersu zip you downloaded above and then select it and confirm to install it
When it's done(installing that zip), you are done, you had rooted your device successfully and now you can enjoy the root access!
Just reboot your device normally and you can find SuperSU icon in the app drawer(if you don't, just install it from play store), open it and it will simply open with an option to follow them
If for some reason, supersu says super user binary is not installed and supersu can't install it, then it's not rooted, and you can retry the process of installing supersu update zip by booting to recovery and installing it from there (explained above)
It is not supposed to happen (the problem stated above) as you are not doing any wrong thing during the process (if you followed my steps)
So, that's it if you have any problem during doing this, just reply and I will try to solve it for you
tell me if it didnt worked for you, i will make a list of devices that are not able to be rooted by this( i guess there wont be any.)
Hit thanks of I helped you
Sent from my SM-T211 using XDA Free mobile app
Ok I did this and it triggered KNOX... I let SU try and Disable it, but it's been trying for over 30min.
Edit: Re-booted and let SU try again. It disabled KNOX it said.
Many devices are not able to root via this method, especially those with locked bootloaders. There is no generic root all method as there are too many variations on software, hardware, and everything in between.
run2jeepn said:
Ok I did this and it triggered KNOX... I let SU try and Disable it, but it's been trying for over 30min.
Edit: Re-booted and let SU try again. It disabled KNOX it said.
Click to expand...
Click to collapse
well, you should know that flashing anything will trigger knox, its not stated in this post because when i created it, i didnt knew about KNOX, i will add it now.
es0tericcha0s said:
Many devices are not able to root via this method, especially those with locked bootloaders. There is no generic root all method as there are too many variations on software, hardware, and everything in between.
Click to expand...
Click to collapse
ok thanks
i changed the post and stated that this process need unlocked bootloader thanks again