[ROOT] TowelRoot - 4.3 & 4.4.2

Search This thread

DocHoliday77

Senior Member
May 10, 2011
9,403
6,892
HuntsVegas!!!
Odin doesn't wipe data, so your apps and all are preserved. At some point you updated SuperSU causing it to be installed on the user data partition, which is why its still there after the flash. If you factory reset it should fix everything to be as you want. This will wipe internal sdcard though, so backup!
 
  • Like
Reactions: Shack70

Shack70

Senior Member
Jan 20, 2014
150
24
York
Amazon Fire HD 8 and HD 10
Odin doesn't wipe data, so your apps and all are preserved. At some point you updated SuperSU causing it to be installed on the user data partition, which is why its still there after the flash. If you factory reset it should fix everything to be as you want. This will wipe internal sdcard though, so backup!

That worked! So now my next question would be if I wanted to root again what is the better way? Flash to route66 or towel?


Sent from my SGH-T999L using XDA Premium 4 mobile app
 

DocHoliday77

Senior Member
May 10, 2011
9,403
6,892
HuntsVegas!!!
Towelroot is the safer and easier way. Anytime you flash anything, there is some risk involved. With Towelroot, you're not doing any extra flashing so risk is reduced.
I still recommend and use root66, but only in certain situations now. Though it does have some risk involved because your flashing your device, its still pretty minimal.
 

chuangk

Member
Jul 11, 2014
6
0
Ok, for wifi, try this...

Open your dialer and enter *#0011#
This should open service mode.

Next press menu and select WiFi.
Press the button to turn wifi power saving mode off. (This has to be redone if you reboot)

Hopefully that'll help a little.

Thank you Doc for the advises and the easiest way to root the phone:good::good:. I did try to turn WIFI power saving mode off but without any noticeable improvement. I also factory-reset twice but the battery still drained a lot faster. One thing caught my attention immediately after the upgrade was that the battery charges faster but also drains faster. Not sure why this happened. Anyway, hope there will be a way to downgrade back to stock 4.3 soon.
 

Rareutu

Senior Member
Oct 21, 2010
161
36
Chicago
thank you for this method, unfortunately i only found out about this now and rooted with cf-auto-root last night. Are there are advantages using towelroot instead of cf-auto-root besides that you dont need odin?

Out of curiousity, did your cf-auto-root method stick around longer than 48 hours? I'm on my third try and the root keeps disappearing. I'll flash back to stock 4.3 (NC2) when i get a chance and try towelroot, but there's no documentation on my issue online (to the best of my searches), and all the KNOX 'fixes' didn't work for me and it's all just incredibly maddening!
 

chuangk

Member
Jul 11, 2014
6
0
You can flash an older stock 4.3 rom, just not the full firmware. Maybe that'll help battery and wifi?

Hmmm, this is getting to an advance level to me. I downloaded the stock Wind mobile 4.3 rom from Sammobile but I think this rom is the full firmware. Do I just flash this rom using ODIN and then I am back to stock 4.3 or are there special steps to follow so the full firmware is not flashed? Sorry that I am not an expert on this.:p
 

yeeahnick

Senior Member
Aug 3, 2011
958
262
Out of curiousity, did your cf-auto-root method stick around longer than 48 hours? I'm on my third try and the root keeps disappearing. I'll flash back to stock 4.3 (NC2) when i get a chance and try towelroot, but there's no documentation on my issue online (to the best of my searches), and all the KNOX 'fixes' didn't work for me and it's all just incredibly maddening!

Yes i am still rooted as of today with cf-root. I did remove all the knox stuff manually with TB. Ive tried towelroot before and its really really easy and simple to use. Good luck
 

DocHoliday77

Senior Member
May 10, 2011
9,403
6,892
HuntsVegas!!!
Out of curiousity, did your cf-auto-root method stick around longer than 48 hours? I'm on my third try and the root keeps disappearing. I'll flash back to stock 4.3 (NC2) when i get a chance and try towelroot, but there's no documentation on my issue online (to the best of my searches), and all the KNOX 'fixes' didn't work for me and it's all just incredibly maddening!

What are you running now? Im assuming you're on 4.1.2, but you said you'd flash back to 4.3. Thats the latest available, so im kinda confused as to what you're flashing back from. If its a rom, you should already be rooted.

If you are on 4.1.2, I dont know if Towelroot will work. But if not just flash the root66 NC2 firmware.




Hmmm, this is getting to an advance level to me. I downloaded the stock Wind mobile 4.3 rom from Sammobile but I think this rom is the full firmware. Do I just flash this rom using ODIN and then I am back to stock 4.3 or are there special steps to follow so the full firmware is not flashed? Sorry that I am not an expert on this.:p

It is the full firmware. And yes, flash using Odin. If you dont want the full firmware flashed you can use Mobile Odin but you have to already be rooted. Otherwise flash a rom in recovery n
 

chuangk

Member
Jul 11, 2014
6
0
What are you running now? Im assuming you're on 4.1.2, but you said you'd flash back to 4.3. Thats the latest available, so im kinda confused as to what you're flashing back from. If its a rom, you should already be rooted.

If you are on 4.1.2, I dont know if Towelroot will work. But if not just flash the root66 NC2 firmware.






It is the full firmware. And yes, flash using Odin. If you dont want the full firmware flashed you can use Mobile Odin but you have to already be rooted. Otherwise flash a rom in recovery n

Sorry Doc. My T999V is running on stock Wind Mobile 4.4.2 rooted with Towelroot. If I simply flash the stock Wind mobile 4.3 firmware using Odin, will my phone be back to 4.3 without problem? I have read some posts saying that this can't be done because of bootloader issue. Thanks.
 

dmgriz

Member
Jun 30, 2013
5
0
Halifax, NS
Success with Eastlink T999V 4.4.2

CONFIRMED - Success rooting my Eastlink T999V (4.4.2) with towelroot. Same as @northghost, SuperSU hung up disabling KNOX but after a reset and opening SuperSU again, it worked like a charm. Thanks @geohot, Easy like Sunday morning...

Just curious anyone else have an Eastlink T999V?
 

DocHoliday77

Senior Member
May 10, 2011
9,403
6,892
HuntsVegas!!!
Sorry Doc. My T999V is running on stock Wind Mobile 4.4.2 rooted with Towelroot. If I simply flash the stock Wind mobile 4.3 firmware using Odin, will my phone be back to 4.3 without problem? I have read some posts saying that this can't be done because of bootloader issue. Thanks.

Ok, you cannot flash the older firmware. Odin won't let you and if you try ither methods it'll brick. You can flash the older roms though. Or as I mentioned, you can flash the firmware via mobile odin. It doesn't flash the full firmware, only select parts of it. If you do try this, make sure you deselect the modem before flashing.
If you're not familiar with mobile odin, search xda for its thread for more info. If you have any other questions about it, or flashing the older roms from recovery, let me know.
 
  • Like
Reactions: dmgriz

dmgriz

Member
Jun 30, 2013
5
0
Halifax, NS
Ok, you cannot flash the older firmware. Odin won't let you and if you try ither methods it'll brick. You can flash the older roms though. Or as I mentioned, you can flash the firmware via mobile odin. It doesn't flash the full firmware, only select parts of it. If you do try this, make sure you deselect the modem before flashing.
If you're not familiar with mobile odin, search xda for its thread for more info. If you have any other questions about it, or flashing the older roms from recovery, let me know.

I can confirm this (just the Odin part, not the mobileOdin part!) :p After the 4.4.2 update my alarm stopped working and ES File Manager was behaving strangely so I attempted to flash stock 4.3 with Odin. Got an error on my download screen that said something like "BOOTLOADER SW RV 2". I then tried to go back to stock 4.1.2, same error. Not knowing what else to do, I flashed the 4.2.2 update again and did a factory reset and Voila! Alarm works, ES works, rooted with Towelroot and everything appears to be fine. I would like to be able to get back to 4.1.2 someday so that I could give CM10 or some other ROM a try but for now it's all good.
 

Rareutu

Senior Member
Oct 21, 2010
161
36
Chicago
What are you running now? Im assuming you're on 4.1.2, but you said you'd flash back to 4.3. Thats the latest available, so im kinda confused as to what you're flashing back from. If its a rom, you should already be rooted.

If you are on 4.1.2, I dont know if Towelroot will work. But if not just flash the root66 NC2 firmware. n


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!
 

serio22

Senior Member
Jul 1, 2012
3,215
1,134
Houston
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!
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 ----------

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?
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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 38
    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:
    3
    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.
    3
    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 :)
    2
    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".
    2
    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!
    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 ----------

    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?
    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