Develop Bugs

[Q] Current rooting method JB

Hello,
I'm new to Android and rooting and I've decided to root my Galaxy S3. However, I'd like to know what is the most current and safest way to root the phone. I've tried downloading the app by following the video in the Generals section but the apps seems to support only 4.0.4 and I'm @ 4.1 and a Google search seems to turn up some methods that are a couple of months back. Any help is much appreciated.

Jelly Bean does not require anything special to root. The method is the same as with ICS.
I used the Team Epic Root method.

Thanks for the quick reply, but do you happen to know if this is the safest method?

I used the same method to root while I was on ICS and had no problems. Just make sure you don't reboot the phone after you Odin the recovery to it. Set Odin to not reset device and then manually boot into recovery and flash the team epic root from recovery file. If you reboot your phone after you flash the custom recovery in Odin and don't immediately manually boot into recovery and flash the team epic file afterward, your phone will overwrite the custom recovery you just flashed and put stock recovery back on your device.
Sent from my SPH-L710 using Tapatalk 2

vpy said:
Thanks for the quick reply, but do you happen to know if this is the safest method?
Click to expand...
Click to collapse
It is as safe as it gets. Rooting on the GS3 is very easy and safe (especially compared to how the HTC Evo process was). You do not have to deal with exploits in a locked bootloader, etc. You simply flash a custom recovery with Odin, and the flash a file that roots the phone with that recovery. The only gotcha (and it is not much of one) was added with LG8 which requires you to boot into recovery before booting the system ROM, so that you can root and disable the code that restores the stock recovery. That is included in the Team Epic Root for Recovery file.

thanks i'll try it and hopefully won't mess up too bad

[Q] Flashed Stock 4.4.2. How to Root?

Hello All,
I recently flashed KitKat 4.4.2 successfully but now I need to re-root. I see dodgy posts about rooting certain ways. Can someone please point me to the right direction in the easiest and safest way to root on KitKat? Thanks!

Suicide_Evo said:
Hello All,
I recently flashed KitKat 4.4.2 successfully but now I need to re-root. I see dodgy posts about rooting certain ways. Can someone please point me to the right direction in the easiest and safest way to root on KitKat? Thanks!
Click to expand...
Click to collapse
You can use CF Auto Root to re-root the phone. The only problem is this method will trip the Knox warranty void counter which can't be reset at this time. You flash it through odin and after it roots, you need to disable Knox. To do that, download (or update) SuperSU and when you run it for the first time, it will give you an option to disable Knox for the root to fully work. Finally, you can install the custom recovery. While this is optional, this is strongly recommended. You can use CWM or TWRP by downloading from either ROM Manager or Goo Manager depending on what recovery you want. After doing that, you should have a fully working root
Download CF Auto Root: http://download.chainfire.eu/233/CF-Root/CF-Auto-Root/CF-Auto-Root-d2spr-d2spr-sphl710.zip

You can also flash the SuperSU zip after using Odin to flash a custom recovery (I recommend philz)
Sent from my Sprint Galaxy S3 rocking Bilgerryans Wicked X ROM with the fluidity script, Tweaked out with a bunch of xposed modules, powered by Ktoonsez KT747 Kernel!!

[Q] Install TWRP without root using ODIN?

Hello,
I have read somewhere that is possible to install TWRP without the need to have root access before installing TWRP. Just a simple flash with ODIN should do the trick. Has anyone tried this on the note 2014?
Regards,
Trzema

of course you can do that.
TWRP is used to manage ROMs and BACKUPs, it had no effect to your installed rom.
but it will trip your knox flag like rooting does.
you can also root without installing TWRP.

[Q] How to root

Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?

itsfredo said:
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
Click to expand...
Click to collapse
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.

The Sickness said:
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
Click to expand...
Click to collapse
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.

itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
I don't know if towelroot will root 4.2.2, but it doesn't install a recovery.
Rob

itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.

lordcheeto03 said:
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
This.
You really don't need CF Auto Root at all until all you want to do is root the stock rom.
If you want to install a customer rom, use Odin to install a custom recovery and flash whatever you want from there.

lordcheeto03 said:
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?

Use cf autoroot and flash clockworkmod through Odin. Download rommanager. Download a rom. Hit install rom from SD card. Pick your ROM from downloads.

itsfredo said:
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Click to expand...
Click to collapse
I understand your apprehension, i really do. What I've said to do has worked for me when i got the phone over a year ago, and has worked here recently when i did it again. I'm trying to tell you there is no need for an updated way of doing what you want. If you want root, use CFauto root. Like i said, that method was done specifically for MDB and MDL firmwares, there is no better choice. Newer yeah, but better? Not a chance. Your firmware is equally outdated and it's worked for millions of users without fail.
As far as a custom ROM goes, find one you want to use, put it on your SD card, pick a recovery (CWM, Philz, or TWRP), flash that in Odin, boot to recovery (power+volume up) , do a full wipe (system, data, and cache) select the ROM, and flash. No need to root at all if you want to go straight to a custom ROM.
EDIT: Obviously, you might want to perform a nandroid backup once you flash your recovery... but that's really optional as long as you have the stock Odin-flashable firmware. Totally up to you.
Sent from my SGH-M919 using XDA Premium 4 mobile app

how to get root on sgh-i747m 4.4.2

hi;
I have a roger GS3(SGH-I747M) and recently I have updated to stock 4.4.2; then I flash cf-root throuth odin; trying to get root access; however, after I boot into the phone, I always gets a force close message on the phone and cannot get root access. Does anybody know what I can do to get root access on stock 4.4.2.
Please help!!!

Watch this: https://www.youtube.com/watch?v=AZgEVM2hSnI or search for towelroot.

TWRP or CWM?
audit13 said:
Watch this: https://www.youtube.com/watch?v=AZgEVM2hSnI or search for towelroot.
Click to expand...
Click to collapse
Towelroot seems quite easy. Once I do that, what's the best way to install latest TWRP or CWM on rooted 4.4.2? I had always heard GooManager, but now it's showing as not supported and unavailable.

No need to root. Just load a custom recovery and flash a custom ROM.

Flash recovery with odin.

pokerplayer999 said:
hi;
I have a roger GS3(SGH-I747M) and recently I have updated to stock 4.4.2; then I flash cf-root throuth odin; trying to get root access; however, after I boot into the phone, I always gets a force close message on the phone and cannot get root access. Does anybody know what I can do to get root access on stock 4.4.2.
Please help!!!
Click to expand...
Click to collapse
Like someone mentioned earlier, try flashing a custom recovery (I like philz touch myself) via odin. Once you access Recovery, if your phone isn't rooted upon trying to reboot you'll see a message that says "root priviliges may be lost, root (or something like it) binary su). Choose yes and your phone will be rooted once it boots. Install SuperSU (or kush's Superuser if you'd like) and then you'll see your phone is rooted.

I used TowelRoot and had absolutely no problems whatsoever. However, 4.4.2 seems to run extremely slow on the I747 so you might consider a custom ROM. That is the route I am looking into.