TOWELROOT

[nunein]

That is no surprise: Towelroot IS working with 4.4.2 (and not with JB)

Sent from my black pearl using Tapatalk

 

[geri.st]

Worked great! German dbt 4.4.2

 

[Neffy27]

What about Verizon S4 mini, anyone can confirm it.

Does not on AT&T Samsung Galaxy S4 Mini.

 

[tobbbie]

Here are some screenshots for those who don't believe KNOX is not triggered:

..

..

I can confirm that towelroot works after I have officially updated from 4.2.2 to 4.4.2 in Germany.

Knox is not triggered (see the origional screenshot from Bullet92) - but strangly I see the System Status of the device to be "Custom" and not "Official" despite I have not done any changes to the system yet (except putting SU there).

Also it seems to be difficult to write to the /system - is there any special trick for the S4 mini?

 

[kev23m]

strangly I see the System Status of the device to be "Custom" and not "Official" despite I have not done any changes to the system yet (except putting SU there).

Also it seems to be difficult to write to the /system - is there any special trick for the S4 mini?

As long as knox is not triggered it is good. You can always flash stock with knox and go back to original. I did that with mine and have given it to samsung to check for hardware defects.

 

[TheAndroidDude]

Rooted GT-I9195 W/TW

When I rooted my S4 Mini (LTE) on 4.4.2 (kitkat) Knox flag was tripped. So I continued to install custom recoveries etc. Still on stock ROM however I took the liberty to uninstall all Knox related files from my device. So far nothing has gone wrong... Flag is still at 0x1... If you care about your warranty, don't root using towelroot it might trip the flag

 

[tobbbie]

When I rooted my S4 Mini (LTE) on 4.4.2 (kitkat) Knox flag was tripped. So I continued to install custom recoveries etc. Still on stock ROM however I took the liberty to uninstall all Knox related files from my device. So far nothing has gone wrong... Flag is still at 0x1... If you care about your warranty, don't root using towelroot it might trip the flag

Are you sure what you did in which sequence - and especially did you check if KNOX was tripped directly BEFORE you applied the towelroot process? Mind that towelroot gets you root access by an exploit in the existing (!) kernel and so the partition for the kernel is NOT touched. Same goes for the recovery partition - it is also NOT touched. There is no identified reason as to why towelroot should break the KNOX.

Other methods of rooting the device are going the way to install an alternate recovery FIRST (and this breaks the KNOX) and THEN get you root on the regular system. Even if you keep the original kernel, the alternate recovery has broken KNOX this way.

So as your device is now - with another recovery - it is obvious that KNOX must be tripped.

---------- Post added at 09:43 PM ---------- Previous post was at 09:25 PM ----------

...just to continue here what I have originally suspected and done in the meantime:

Towelroot does NOT make the reboot in case of successful root. It gets you root in the same session immediately after you click "make it ra1n". So there is no reason why/how KNOX could be tripped. I did root my device with this method and still have KNOX intact (I just checked again to be sure). I have in the meantime made some changes to the /system folder, e.g. removed the photo-click sound, freed some space by removing the japanese language files for text-to-speech (gives you 25MB) and inserted all the updated system apps back to the system (did not ODEX them and removed classes.dex from the .apk - so they are all larger than the ODEXed originals). Also I moved out Google+ from System to be regular app.

---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------

I can confirm that towelroot works after I have officially updated from 4.2.2 to 4.4.2 in Germany.

Knox is not triggered (see the origional screenshot from Bullet92) - but strangly I see the System Status of the device to be "Custom" and not "Official" despite I have not done any changes to the system yet (except putting SU there).

Also it seems to be difficult to write to the /system - is there any special trick for the S4 mini?

Installing Busybox has made the remount command possible which I guess is needed for writing to /system. Still I have no clue about the "Custom" system status - does anyone else also see this after towelroot?

 

[TheAndroidDude]

Are you sure what you did in which sequence - and especially did you check if KNOX was tripped directly BEFORE you applied the towelroot process? Mind that towelroot gets you root access by an exploit in the existing (!) kernel and so the partition for the kernel is NOT touched. Same goes for the recovery partition - it is also NOT touched. There is no identified reason as to why towelroot should break the KNOX.

Other methods of rooting the device are going the way to install an alternate recovery FIRST (and this breaks the KNOX) and THEN get you root on the regular system. Even if you keep the original kernel, the alternate recovery has broken KNOX this way.

So as your device is now - with another recovery - it is obvious that KNOX must be tripped.

---------- Post added at 09:43 PM ---------- Previous post was at 09:25 PM ----------

...just to continue here what I have originally suspected and done in the meantime:

Towelroot does NOT make the reboot in case of successful root. It gets you root in the same session immediately after you click "make it ra1n". So there is no reason why/how KNOX could be tripped. I did root my device with this method and still have KNOX intact (I just checked again to be sure). I have in the meantime made some changes to the /system folder, e.g. removed the photo-click sound, freed some space by removing the japanese language files for text-to-speech (gives you 25MB) and inserted all the updated system apps back to the system (did not ODEX them and removed classes.dex from the .apk - so they are all larger than the ODEXed originals). Also I moved out Google+ from System to be regular app.

---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------



Installing Busybox has made the remount command possible which I guess is needed for writing to /system. Still I have no clue about the "Custom" system status - does anyone else also see this after towelroot?

I confirmed that before hand Knox was not tripped. I'm looking further into it but so far Knox hasent proven to be difficult.


Sent from my GT-I9195 using Tapatalk

 

[tadhara]

SuperSU

Hi there!
I'm new to this device, as I got it 4 days ago. I updated with Odin to 4.4.2. I used Towelroot, worked like a charm, phone is rooted, KNOX isnt tampered.
I installed SuperSU from Google Play and it sais "Samsung KNOX detected. This can reduce the chances of rooting and can cause annoying pop-up messages. Should we try to block it?" What am I supposed to do here? I don't want to break KNOX so a little help would be much appreciated.
Thank you

 

[tobbbie]

Hi there!
I'm new to this device, as I got it 4 days ago. I updated with Odin to 4.4.2. I used Towelroot, worked like a charm, phone is rooted, KNOX isnt tampered.
I installed SuperSU from Google Play and it sais "Samsung KNOX detected. This can reduce the chances of rooting and can cause annoying pop-up messages. Should we try to block it?" What am I supposed to do here? I don't want to break KNOX so a little help would be much appreciated.
Thank you

You can block it from within SuperSU or disable (freeze) the relevant applications yourself. It is safe to have them disabled from SuperSU. It does not trip the KNOX flag which serves another purpose (i.e. to prevent custom kernel or custom recovery loaded). The KNOX processes in RAM are there to prevent real time access of apps to what Samsung considers potentially dangerous areas of your device.

 

[wiisixtyfour]

I just wanted to confirm that towelroot works on my Verizon S4 mini SCH-I435 on 4.4.2 (KOT49H.I435VRUBNE1). I had root before on 4.2.2 and then updated with Kies, and used towelroot right away. Just had to use the modstrings.
In towelroot click "welcome to towelroot v3" 3 times and enter "1337 0 1 7380 4 0" in the text box then click the "make it ra1n" button.

 

[tobbbie]

I just wanted to confirm that towelroot works on my Verizon S4 mini SCH-I435 on 4.4.2 (KOT49H.I435VRUBNE1). I had root before on 4.2.2 and then updated with Kies, and used towelroot right away. Just had to use the modstrings.
In towelroot click "welcome to towelroot v3" 3 times and enter "1337 0 1 7380 4 0" in the text box then click the "make it ra1n" button.

This is the string for "new Samsung" and for me towelroot has picked that one automatically on 4.4.2.

 

[ondoy1943]

GT-I9192 with 4.4.2 KK Build xxxNG2

no joy.. device not supported according to towelroot. bad rap...

 

[bfc_xxx]

Any way to make toweroot work on i9192 with 4.4.2?

 

[nunein]

Have you tried it? IMHO it should work with stock 4.4.2

Sent from my black pearl using Tapatalk

 

[SilviuMik]

Have you tried it? IMHO it should work with stock 4.4.2

Sent from my black pearl using Tapatalk

It does not work. GT-I9192`s kernel was compiled in 8 July.
TowelRoot works with kernels made before 4 July

 

[nunein]

So it already came with the patched kernel. Bad luck for 9192 users.

Sent from my black pearl using Tapatalk

 

[ADR USR]

So it already came with the patched kernel. Bad luck for 9192 users.

Sent from my black pearl using Tapatalk

Yes, especially considering that Google decided to force only stock app for everything.
Really do not understand what Google wants.
An invitation to experience other OSs. Google seems to want to look more and more with them.
Those advantages to using Android are getting in the past.

 

[tobbbie]

It does not work. GT-I9192`s kernel was compiled in 8 July.
TowelRoot works with kernels made before 4 July

That's just 4 days - I wonder how close the Samsung kernel aligns with Linux commit sources. Anyway, the tr.apk you get now at towelroot.com is again a different size (larger - now 113099 bytes) - so it has grown again. Did you try that one?

 

[ADR USR]

That's just 4 days - I wonder how close the Samsung kernel aligns with Linux commit sources. Anyway, the tr.apk you get now at towelroot.com is again a different size (larger - now 113099 bytes) - so it has grown again. Did you try that one?

I've tried. Does not work,

no root is a very bad experience in kk,
In JB. could live without, but KK is bad.

Sdcard limitation.
Text Reflow nonexistent. http://www.androidpolice.com/2014/0...-webviews-in-kitkat-probably-not-coming-back/

Without text reflow, several websites are impossible to navigate comfortably. XDA for example. Practically limits the user to only use a Browser: Opera.

Google, google ..