[ROOT] TowelRoot - 4.3 & 4.4.2

Search This thread
By:
Advanced…
cLogic

cLogic

Senior Member
Sep 13, 2012
466
193
Montreal
the S3 was updated to kitkat 4.4.2 and then updates stopped .. altho your carrier decided to stop back at jellybean 4.3

you have to come to the dark side and flash a custom rom to go beyond 4.4.2 :cool:
 
I

icewater0

Member
May 3, 2015
6
0
How does towelroot use Internet access?

This apk will not root unless I have an Internet connection. Anyone know how towelroot uses it?

Thanks!
 
A

admiralawezome

New member
Oct 25, 2015
3
0
not working on t-mobile stock rom 4.3... it says.. This phone isnt currently supported -.- i give up on rooting my t-mobile sgs3......
 
DocHoliday77

DocHoliday77

Senior Member
May 10, 2011
9,403
6,892
HuntsVegas!!!
I believe we do need it, at least for the new firmware that was just released.
Shoot me a pm when you get it and I can add it to my collection/repo.

What build are you planning to flash?

Sent from my SGH-T999 using Tapatalk
 
S

slimcyril

Senior Member
Feb 7, 2015
541
121
I rooted my Samsung galaxy s3 Verizon i-535 running 4.4.2 with towelroot installed supersu & flashed cwm recovery from rom manager, booted recovery but got a black screen with yellow so now I don't have a recovery, please keep me advised?
 

Attachments

  • 1452299874091.jpg
    1452299874091.jpg
    49 KB · Views: 230
  • 1452299895321.jpg
    1452299895321.jpg
    50.9 KB · Views: 229
S

slimcyril

Senior Member
Feb 7, 2015
541
121
@audit13 I have a friend that has reflashed this phone twice at the Samsung store in Bestbuy & she's still willing to restore the phone back but I just wanna be able to root & use my recovery to install cool stuff

---------- Post added at 01:57 AM ---------- Previous post was at 01:52 AM ----------

[/COLOR @audit13 reflashing the Rom isn't a problem, I just wanna be able to use root & recovery cuz without it root is no fun, please keep me advised?
 
S

slimcyril

Senior Member
Feb 7, 2015
541
121
@audit13 I think the bootloader is locked cuz my friend at Samsung store in bestbuy reflashed the phone this morning, is there any other way to install or flash zips without a custom recovery?
 
V

Voraxi

Member
Mar 6, 2014
6
1
Confirmed to work with MetroPCS SCH-R530-M

Now to see if I can't find a stock ROM with all the bloatware removed. Anyone have any suggestions?
 
You must log in or register to reply here.

Similar threads

cyanogen
[ROM][OFFICIAL] CyanogenMod 10 Nightly Builds for SGH-T999
Replies
14K
Views
2M
V
vanclaver
zedomax
[Root] How to Root T-Mobile Galaxy S3 SGH-T999!
Replies
218
Views
307K
J
jerryspring
mskip
[SAMSUNG GALAXY S3 UNIFIED TOOLKIT V9] Drivers, Backup, Root, Recovery + MORE [TMO]
Replies
583
Views
420K
lakamel
lakamel
Jamison904
  • Locked
[ROM][KERNEL][4.3] INFAMOUS S3™ | Version 6.0 | Dec 8, 2013
Replies
5K
Views
485K
Naddict
Naddict
ayysir
  • Locked
[ROM][5/23/14][4.4.2] AOSPA 4.3 Beta 6
Replies
4K
Views
541K
ayysir
ayysir

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 38
    DocHoliday77
    DocHoliday77
    Hey everyone! Most of you have probably already heard about this, but for those who have not, I thought I would post up the information.

    XDA Recognized Developer @geohot has developed a new root method that so far is working for many, many devices....Including ours!!! And believe me, it just does not get any easier than this!

    Check out geohot's original thread here on XDA: I'm throwing a party and you should come **GS5 ROOT THREAD**

    Don't forget to at least click his Thanks button, and consider donating to him if you can. There was a bounty started for rooting the Verizon and AT&T S5's, and they finally got their wish! And geohot gets to claim a nearly $19,000 bounty!!! Amazing stuff! For those who may not be familiar with his previous work, he was the first to jailbreak the iPhone/iPod, and if I am not mistaken he did the same with the PS3!


    So anyway, you are here to root your device, no? I guess we should get on with it then!

    This is confirmed to work on 4.3, NC2 firmware for the T999, as well as 4.3 and 4.4.2 KK firmware for the I747! It should work for the T999V firmware released this morning, and for the upcoming KK updates to the T999/T999L/T999N!



    HOW TO ROOT WITH TOWELROOT
    Developed By: geohot


    Go to http://towelroot.com
    Click on the red Lambda symbol to download the towelroot.apk
    Install towelroot.apk on your device
    Open the app
    "make it ra1n"

    You are now rooted! But need to follow a couple more steps.
    Install Chainfire's SuperSU from the Play Store
    Open SuperSu and let it update the su binary
    When it asks if you would like to disable Knox, SAY YES!    ​



    Note: I tested this on stock unrooted 4.3 firmware. Build NC2. When I told SuperSu to disable Knox it just hung with the spinner going. I just had to close SuperSu, reopen and when prompted again, said yes and it worked just fine.

    There you have it! The easiest root method we have ever had for our S3's! Enjoy! :cowboy:
    View
    3
    DocHoliday77
    DocHoliday77
    Recently many have reported problems with root after installing SuperSU. Mostly they are issues with updating the binary breaking root. Chainfire knows about this and is working on it, but until he fixes it do not install via the Play Store.

    Instead, download and install (as a normal app) SuperSU 2.00 from here.
    https://www.androidfilehost.com/?fid=23622183712471997

    This should get you guys by until he finds a fix. Sorry for the trouble some of you have had.
    View
    3
    cLogic
    cLogic
    CONFIRMED .. this worked on My Videotron SGH-T999V with latest stock 4.4.2 firmware (NF1) ... altho with the following notes ...

    at first I tried to use the same procedure I used to root 4.3 (twrp 2.7.1.0 recovery, de-knox script, and superSu 1.65) ... but su binary would either fail to update or not survive boot

    used latest towel root apk (version 2), but su binary failed to update until after a reboot

    now I'm in the process of using root and Titanium to debloat KitKat .. thanks samsung, lol

    so far, I don't really notice much difference between kitkat and 4.3 which is kinda odd for a "major" release .. it's actually a letdown

    mucho thanks for bringing this to our forum, Doc ... merci bien :)
    View
    2
    DocHoliday77
    DocHoliday77
    In the end, root is root. So no real advantages once you've already done so. This just makes the process extra quick and super easy!
    I consider it to be the safest method at this point as well. If for no other reason than it limits the potential for human errors. But it also requires no flashing, which which always carries some risk of its own.


    If anyone who has never tripped the warranty bit tries this method, please confirm it does not trip it.
    Its been reported not to already on other devices, and I see no reason it would, but its better to have confirmation on each device nonetheless.

    And fyi, after flashing stock then running Towelroot, the device status remained "Official" and I could still check for updates until I rebooted. After rebooting it re-runs its check and sets the status to "Custom".
    View
    2
    serio22
    serio22
    Rareutu said:
    It's the strangest thing y'all. My root will come and go in seems like an arbitrary manner. The only reason i noticed is because my quickboot reboot widget would make the screen go blank (hang) from which i could hit the 'return' hardware key to go back to homescreen. I would then confirm by opening any root-needed app (triangle/TB, etc) and get the 'root needed for functionality' message.

    In any case - to elaborate on the root coming and going phenomenon.

    I came from stock T999 (non LTE) and believe i had an OTA or two under my belt but was running 4.0.1 or 4.1.1 latest! I can be lazy about these things and was happy about my original root method (though i can't remember which method that was) but recently tried to see if OTA method worked when i saw that Tmo was on to my root (settings/about/phone/software update produced message. Turns out the flash counter is responcible for that, as confirmed after Triangle usage).

    Then i flashed latest NC2 update - found through samfirmware via ODIN, and after i couldn't find a relatively 'safe' method to root (based on online documentation, reading up on KNOX, my own comfort levels, etc), stumbled on the cf-auto-root and flashed that. So far so good for a couple of days.

    Then, after a couple of days, the root was gone as described above. Reflashed auto root, integrated SuperSU into system and ran Aroma Installer full de-bloat. I couldn't find the recommended knox system entries to delete via TB, and assumed they were never included in the auto-root image. But i did download KNOX Disabler just in case. Never used it.

    Then my root was gone again after a couple of days and thinking i had nothing to lose i tried to run KNOX Disabler. The app didn't seem to work and looked like it was hanging, but after a reboot the root has returned.

    So now the situation is that (and this is mostly trial and error), the root will disappear after some time (i'm paranoically checking it twice a day now, and might establish duration or reboot patterns at some point), at which point i'll go through the knox disabler/hang/reboot/root returned loop.

    My situation seems unique as far as wide google and xda search results - and it seems manageable (if annoying) for the moment, but it would be great to understand and resolve the bloody strangeness.

    Thanks for listening and any contributions on the matter!
    Click to expand...
    Click to collapse
    Did you ever open SuperSU and disable Knox from there? Knox may be conflicting with root access

    ---------- Post added at 12:17 PM ---------- Previous post was at 12:02 PM ----------
    dmgriz said:
    I didn't look much further than this post but it states that for CM you need to start from ICS. Is there another thread I should check out?
    Click to expand...
    Click to collapse
    It was probably an old post.. I'm sure it will work, but since it is an old cm build you may need to edit the assert lines to match your bootloader.. I wouldn't go back to cm10 though since we have cm11
    View

New posts