TOWELROOT

Search This thread

androhun

Member
Sep 15, 2014
5
0
Knox status

"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. "

So you moved/deleted few files from the /system folder and your phone's knox status is still intent, right?
 
Last edited:

paroariax

Senior Member
Feb 25, 2010
55
7
It's worth noting on the first post that once you install SuperSU, Knox Security will detect and try to disable it (asking you to reboot). DON'T REBOOT, but instead run SuperSU and allow it to update the su binary and disable Knox Security. This is normal, and won't trip the warranty void flag.
 

MFaust

Senior Member
May 9, 2008
161
39
Oradea (Blaj)
www.neobux.com
Some help please

Hi, i just bought a S4 mini duos and i have android 4.2.2 the firmware is i9192XXUBNC1.

my question is... can i root it without trigger knox?

and... if it is possible i want to stay for a whille on 4.2.2 for some testing and after to update to 4.4.2

btw i tryed to update via OTA and it sayd that no update is available.

thanks!
 

andu86

Senior Member
Jan 3, 2012
306
127
Bucharest
OnePlus 7
Samsung Galaxy S22
Hi, i just bought a S4 mini duos and i have android 4.2.2 the firmware is i9192XXUBNC1.

my question is... can i root it without trigger knox?

and... if it is possible i want to stay for a whille on 4.2.2 for some testing and after to update to 4.4.2

btw i tryed to update via OTA and it sayd that no update is available.

thanks!

if you have 4.2.2 you can't root it with towelroot, only 4.4.2 works and i dont know if it works on the duos model, some users reported that it didn't work.

you can always choose when to update to a newer firmware if its available for your phone
 

MFaust

Senior Member
May 9, 2008
161
39
Oradea (Blaj)
www.neobux.com
Hi, i just bought a S4 mini duos and i have android 4.2.2 the firmware is i9192XXUBNC1.

my question is... can i root it without trigger knox?

and... if it is possible i want to stay for a whille on 4.2.2 for some testing and after to update to 4.4.2

btw i tryed to update via OTA and it sayd that no update is available.

thanks!

i managet to root my S4 mini (android 4.2.2) without triggering Knox, this were the steps:

1 download and flash I9192XXUBMK4 (android 4.2.2) via ODIN
2 used Saferoot.zip (you can find it here on xda, dont remember the page right now)
3 because i got some force closed problems like weather and G search app i entered recovery wipe data and catche
4 reconfigurate device, open SuperSU and disable KNOX

Hope this helps someone!

(Dont forget to click thanks!:p)

P.S. System Status changed to CUSTOM!
 
Rooted I9195XXUCNK1

follow the steps from the first page
Hi to all ! :)
- So, I would like to explain what happened in my case when I tried to root S4 mini International i9195 with towelroot.
- I was on original XXUCNK1 kernel from 3. november 2014. with KNOX on and I have downloaded this I9195XXUCNK1.zip kernel from this thread: http://xdaforums.com/galaxy-s4-mini/general/index-official-stock-kernel-collection-t2947372 and also I have downloaded old voulnerable kernel KERNEL_I9195XXUCNF7.zip and Odin 3.09 also but from an other thread here on the XDA.
- I have extracted ALL packages and I went in "Download mode" on the phone. (Swich off the phone and then keep holding all three buttons (1-Home button, 2-Volume Down and 3-Power button) on the phone until "Download mode" appeared on the screen and then pushed volume button UP (only once) to start download.
- Connected the phone with PC via USB cable and then I started Odin 3.09 by clicking right mouse button and "Run as Administrator".
- First I have choosen extracted old voulnerable kernel XXUCNF7.tar.md5 under AP in Odin and I didn't change anything under "Options" in the Odin (Auto Reboot and F. Reset Time was already checked) and I started the flashing. It took few seconds and I got green massage "PASS" on the Odin what means that it's done and it's O.K. Phone rebooted and started normaly but when I went to "Options" and "About the phone" to see changes in the kenel I have surprise to see that even everything in "Odin" was good during the flashing without any error I still had the same text and kernel which I had before the flashing. :confused:
- I thought, O.K. I have to change something in "Odin" and first I have uncheked in "Options" - "Auto reboot" and I have started the flashing process again.
Now it took much longer to flash (about one minute) and when i got green "PASS" message I took battery out and restarted the phone.
But after the phone was rebooted there was no changes in the options "About the phone". The kernel stated still XXUCKN1 and not XXUCNF7. :rolleyes:
- Then I have uncheked and "F. Reset the time and Auto Reboot" in the "Odin" options and I started flashing again. It took some time and I got again green "PASS" in Odin.
- Again, I restarted the phone and it boot normaly and I wanted to see if now is something changed in "Options" and "About the phone".
But it was still unchanged with XXUCNK1 kernel. :mad:
- Fortunately :fingers-crossed: I was not lazy to try to instal and run "Towelroot" again to see if it will maybe work because before I started all this flashing procedure I have already dowloaded and installed "Towelroot" but I got message that the phone is not supported.
And... When I clicked on "Make it rain" I got immediately message that my phone should have now have the root acces. :victory:
- I have rebooted the phone and installed "SuperSu_2.49" and updated SU binary via "Normal" way and disabled KNOX.
After that I flashed back (the new kernel with "Odin" and not checked any options in it) the new XXUCKN1 (when it is unpacked it has the name "boot.tar.md5") kernel even it already stated that it is on this kernel already, but anyway...
After that I have instaled BusyBox 28 Pro in the System and also Titanium Backup 7.1.2 and I checked if I got Samsung status: "Custom" but it was still "Original".
So ... I rebooted the phone thinking maybe after the reboot I will get the "Custom" status because of writing to the "System" but it was still "Original". :D
- Thus, everything worked good even it looks on the first hand that it will not work at all.
So, I hope that someone will have any benefits on this little help. :highfive:

Cheers !!! :cool:
 
Last edited:

SilviuMik

Senior Member
Nov 17, 2011
1,495
1,512

Just a small correction . U can`t see what kernel version u have . U see only 3.4.0 and some numbers and build date . NOTHING more related to what u flash that name XXUCNF7 or XXUCKN1
That is why u did not see different names there
In about phone there are 2 places which show XXUCKN1 for example : Baseband which is Modem and Build number which is system version ( build.prop file is responsible for that )
Cheers.
 
  • Like
Reactions: RuffBuster

RuffBuster

Senior Member
Feb 3, 2012
1,321
359
So, I hope that someone will have any benefits on this little help. :highfive:

Cheers !!! :cool:

I always like to hear success stories. Thanks for reporting back. I'm about to take these same steps myself and root my new phone. I'm running the newer stock from March this year but I've got a good feeling things should proceed like yours.

Can you confirm that your system status is STILL showing "original" and is your knox still untripped?

Many thanks.

EDIT:

Worked a treat! No knox trip and fully rooted!

Now I just need to find and download my relevant stock firmware in case I need to flash for warranty purposes to remove root. But all good here very happy!

Also used Wanam to change device status to official I know it's only cosmetic but hey.
 
Last edited:
  • Like
Reactions: Boombastical
Hi RuffBuster,

Actually, I didn't check in „Download mode“ if the status is still „Official“, but in the options and „About the phone“ under „Secure boot status“ and there is still „Samsung“ so...
At the moment I don't have access to the phone but on the next monday I will check it.
I did check Knox immediatly after the root in „Download mode“ and it was 0x0. After that I have installed SuperSu, Busybox, Lucky patcher, Link2Sd, Xposed, Greenify... etc

Greetz !
 
Last edited:
  • Like
Reactions: RuffBuster

liobeir

Senior Member
May 11, 2011
425
25
waasmunster
question

What do you mean by "After all the above steps are done, flash the kernel from your firmware the same way as you did it the first time."?

Do i flash the same kernel i flashed before towelroot or?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Hi all,

    there is a new app for rooting phones, the name is Towelroot and it was made especially for Verizon Glaxaxy s5 but the dev says that every phone with kernel build date < 3 June can be rooted.

    With this app you can root Galaxy S4 Mini with kitkat firmware without tripping knox counter. It will stay 0x0 and you will have root access.

    First of all you must put a vulnerable kernel with build date <3 june

    you can grab one from [INDEX] Official Stock KERNEL collection for Galaxy S4 Mini (Kernel for I9195XXUCNF7 is the one you have to grab to work with towelroot, offcourse if you own an i9195 )

    Flash it via odin. Leave everything intact and load the kernel to AP.



    After the phone boots, install towelroot, press makeitra1n and you are rooted.

    Next step is to install SupserSU from google play.

    After all the above steps are done, flash the kernel from your firmware the same way as you did it the first time.

    There you go, knox 0x0 and root access.

    http://xdaforums.com/showthread.php?t=2783157
    3
    Me too, and flashed the newer kernel as well, but it is not what I am asking.

    Will flashing a stock rom trigger the knox? Logic says no, but can someone who has done it verify it?
    (I am just a reply away from a cool present :fingers-crossed: )
    No worries, a stock Rom via odin will not trigger knox! Done it many times!
    2
    Towelroot tripped Knox on Australian I9195T

    Hi,
    After doing lots of research on Samsung Galaxy S4 Mini sold in Australia as I9195T version. Awhile ago I updated the firmware via OTA. Telstra only released this 4.4.2 version in the middle of 2015 some 6 months later than other carriers or Countries. To Find out I lost Write Access to SDCard. this model having only 8MB of internal memory means you are always running out of space. Could not even do the OTA update from 4.2.2 to 4.4.2 Ran out of memory half way through.
    So I moved lots of apps and freed up as much as I could. Finally got 4.4.2 installed and then No Write Access, found some apps allow Write Access. Anyway This perfectly good working turns to **** and no mention of this prior to update Typical of Samsung and Android lack of info. We the users have to do the research then decide to up date or not.
    After the update the phone never really worked properly anyway. After more research most suggestions fixes or comments required a Master RESET of Factory reset. ie save all your data and apps. Remove SD Card so it can not be corrupted etc. Used ADB full update after finally getting drivers to work. But my S4 mini had not been fully operational since the firmware patch. So ADB Full Backup would not work. Used Helium Backup worked but does not fully backup everything. same as Kies only partial backup.

    Anyway after all that I finally did a factory reset that was supposed to backup then reset. Found out that only backup some apps and settings. Then spent many hours over the next few days to restore everything back to normal. Still not sure every app is configured as it was prior to reset. Then finally I could do an ADB Full Backup of the internal Memory ONLY without 64GB SD Card which is half full. File size was about 3GB. Just to be sure prior to Rooting the device. I tried plenty of different types of One Click Rooting Apps, so I would not trip Knox, reading plenty of comments about many procedures to Root will trip KNOX. Found your method using Towelroot. Then found that the latest firmware passed July 2014 had been patched.
    My firmware is I9195TDVUACOE3-I9195TTELCOE3 released on 03-07-2015 v4.4.2 with prior firmware being I9195TDVUABNB1-I9195TTELBNB1 v4.2.2 released on 02-09-13. There has been only one update from this model's release mid 2013 in Australia for 3 carriers Telstra, Vodaphone and different Model i9195 for Optus.
    So I tried Towelroot using the 4.4.2 Boot file extracted from Firmware download from SAMMOBILE and used script as suggested to make root.tar.md5 file for ODIN. Downloaded it and tried Towelroot, to find it would not Root the phone. Phone locked up and would not boot. So I had to use method of remove battery and restart into Download Mode to again restore phone back to normal using root.tar.md5 file extracted from OC3 Latest version firmware.

    I was glad I achieved a working phone again with KNOX still 0x0. Then more research realising that I must use same version boot file from 4.4.2, but a release prior to June 3 2014. But Did not have any options of early releases in this region. Seams to be many releases around Europe.
    Found a software site that lists all Samsung's Firmware for I9195 models. I could have downloaded many 2-3GB files from several countries, but assumed wrongly that the boot files would be same for each release and only the carrier's or Country files differ in each Rom.

    My only choice was to select from I9195XXUCNF7 series released on 13/6/14 or I9195XXUCNEA released on 27/5/14. So decided to try your boot file already indicated that would work with Towelroot.. I could have pick any Complete firmware from the 20+ Listed from any as listed. But what would I gain as suggested earlier.
    But maybe I was wrong and you have to match firmware components and not use a different Boot file from another release. ie must be from XXUCNF7 and use earlier release being same as latest already updated. Must be XXUNCNF7 older and XXUNCOC3 Latest. So KNOX will not be tripped.
    Anyway I went for XXUNCNF7 Boot so I could be rooted by Towelroot On my I9195TDVUCOE3 firmware. That worked OK. So Achieved that part, Then I reinstalled my latest boot TDVUCOE3, phone rebooted OK.

    But on startup, I had a message in Yellow on top of the screen indicating Set Warranty bit : Kernel before booting with Samsung Symbol on Screen followed by Home screen with Icons. After bootup was completed I used SuperSU app to complete the root process. Did not disable KNOX and then used Root Checker to find Root was successful.
    Next I installed SD Fix App to get write access back again.
    Using Xplore to read Root directories found the permission.xls file modified as to allow Write access to Ext SD Card, taken away by Android update in 4.4.2. Suddenly I got my access back to the SD card and it allowed about 2GB of files to be transferred from Internal Memory to EXT SD Memory. I have now got 2.5GB Free instead of 500MB free of Internal Memory. Phone is now useable. ONLY ISSUE is NOW KNOX is 0x1 (Tripped).

    Conclusion I think you cannot mix Firmware version or I9195T sold in Australia is different to I9195 European or International model or I9195L Latin American Model. But I have limited choices. I used factory STOCK Firmwares. I could have used Software extracted from I9195T Recovery process using ODIN or used PC Based TWRP or CWM, PC Kingroot , Framaroot. that would have tripped KNOX.
    Pingpongroot, Kingroot, and OneClickRoot apps did not work on my latest version firmware. So now have a rooted phone working properly, KNOX Tripped. Does not really matter as phone is 2 years old and out of Warranty anyway.
    I just wanted to experiment to get my phone working how it was when I purchased it.

    The moral of the story DONT UPDATE FIRMWARE without RESEARCH. DONT USE OTA updates pushed on users by manufacturer's WHIMS. and BULL**** about safety, security etc. An update that reduces the functionality, is a breach of Consumer Law. " Item is NOT FIT For PURPOSE" breaches the code.
    Samsung and Googles Android should be made to fix the problem of reduced access to SD Cards, especially models with only 8MB of internal memory. But they obviously don't care to fix it, by releasing a patch or new versions of 5.0 Lollipop for I9195 models.
    So we have to root the phone and lose Warranty to fix it as users.

    Anyway that's it folks
    2
    Ok, maybe I will give it a go this weekend. Just need to understand how the option to get root rights remain if you don't install SU? I mean is not the basic thing to get root the SU binary itself? Or is it that towelroot already installs an SU-binary which later is updated with installing the SuperSU application, which then asks to "update" - not install - the SU binary?

    On the process of getting back the vulnerable kernel to start the whole thing: which winrar can extract the official update packages from Samsung? I thought these packages are encrypted and so I had no success in getting the full content that time when it appeared on my device.

    You can install supersu while you are on the vulnerable kernel, there is no problem with that, disable knox when supersu asks you and it wont trigger knox, it will stay 0x0. I did it every time i installed a new firmware..

    Afterwards you can put back the kernel that your firmware had.

    There is a topic created by me with kernels for i9195 and i9192, you can grab from there an old kernel with vulnerabilities and a new kernel.

    you can find the topic here [INDEX] Official Stock KERNEL collection for Galaxy S4 Mini
    2
    Here are some screenshots for those who don't believe KNOX is not triggered:

    evysybe6.jpg
    4e2ahupa.jpg
    9ypy6ete.jpg
    vuda5ugu.jpg