yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini General] The Jinxer:
hmm....

Do you have knox? What I mean is has samsung updated your phone to actually use knox enforcement?

Only from the recent update to my S4 mini (GT-9190) knox was implemented. the only reason I updated was because I thought that it was 4.4. damn basterds have killed my root access in favour of some knox S**T. I went from admin to 2nd class user. Samsung should put up a changelog for the updates
[Galaxy S 4 Mini General] tinko975:
yes, i have knox and root deactivated it.
[Galaxy S 4 Mini General] The Jinxer:
thought so, that is why I cannot understand why mine does not work
[Galaxy S 4 Mini General] mironiko:
Mine still didn't work. Same problem as before. On JDQ39.

A pity...

P.S. Here's my system SS. Any ideas why it doesn't work..?

And, is there another rooting method that doesn't change Knox to 0x1..?

Thanks!
[Galaxy S 4 Mini General] mironiko:
Anybody, please..?

Thanks!

TT via S4M i9192
[Galaxy S 4 Mini General] Whosat:
No other known method if this doesn't work for you
[Galaxy S 4 Mini General] sono81:
Rooting S4 Mini Verizon

Hello all,

I just got a S4 mini from verizon. I originally had an Incredible 4g LTE. As I have been looking through the various threads I have come to realize that for this particular model of S4 mini, there is no actual root method yet is there?? Im a newbie to this particular phone so any information you can provide about rooting this phone would be much appreciated.

thanks all

Sono
[Galaxy S 4 Mini General] silentscreamz:
From what I have seen, both saferoot and kinko works but not sure about the warranty void. I know I used kinko w/o any problems till I tried to flash something then my knox went to 0x1. Hope this helps but the SCH-I435 is not getting much love.
[Galaxy S 4 Mini General] louron:
I rooted my sch-i435 using the method within this thread > http://xdaforums.com/showthread.php?t=2565758, which I believe we are on, that states "Again, using this WILL NOT set the "Knox Warranty Void" flag.".

The method also mentions explicitly:

1. You can't install custom recovery and custom ROMs on a phone with a locked bootloader. This rooting program does not unlock your bootloader and won't allow you to flash custom on a locked device. However, NOTHING allows flashing a custom recovery on a bootloader locked phone at the moment. See Safestrap for a way to install some custom ROMs.

Hope this helps.
[Galaxy S 4 Mini General] gungrave80:
Sorry, I cannot open the link you pasted. Could you please fix it?

Thank you very much.
[Galaxy S 4 Mini General] louron:
My bad...link fixed
[Galaxy S 4 Mini General] bigbry2k3:
Didn't work with any method on MK5

I have MK5 update i guess that's what it's called. But It didn't work. I get stuck on the bat file that says transfering files and just hangs there. But everything up to that point works perfectly. Just would not load files i guess. I waited 30 minutes and it still did not load files. Any other method to root?
[Galaxy S 4 Mini General] tinko975:
Kingo isnt worl if you want to install cm. I must repear root from cmw..
[Galaxy S 4 Mini General] fburgos:
working on i9192 ububmk4 firmware, first the notification for disabling knox didnt appear at all, i had the knox notification blocking supersu, but i went to setting all apps, and fc all knox apps, the open supersu it ask to update binary and block knox reboot, pickup where the script left it and seems to work fine.
[Galaxy S 4 Mini General] tammovh:
Incase its of interest to anyone, I have the GT-I9192 with I9192XXUBNB1 baseband and have rooted with Kingo as saferoot did not work.

Unfortunately Kingo

did

trigger the Knox flag. Beware...
[Galaxy S 4 Mini General] Baelphes:
I own a SCH-I435L and can tell you guys this didn't work. Kingo didn't work either, so I guess I'm out of luck for the moment. Not having root sucks :mad:
[Galaxy S 4 Mini General] micallen:
No go on SCH-L520 (4.2.2)

--- Samsung Galaxy S4 Android 4.3 Root ---

--- Based on the CVE-2013-6282 exploit by cubeundcube ---

[*] Testing adb usability

Plug in your phone and Press any key to continue . . .

[*] Waiting for your phone to appear

[*] Your phone is detected and ready for rooting.

[*] Sending files to your device...

[*] Starting rooting program.

ro.build.product=serranoltespr

ro.build.id=JDQ39

setsockopt() failed: Bad address.

this device is not supported.

kallsyms_addresses search failed.

[*] Checking if rooting succeeded

[*] Unfortunately, rooting failed. Cleaning up.

Press any key to continue . . .
[Galaxy S 4 Mini General] SHIRI:
Bloody hell, not working here:

GT-I9195, android 4.2.2, version UBML4

It starts and then says the phone is not supported... here is the picture too...

Any ideas guys???
[Galaxy S 4 Mini General] tinko975:
Use another type to root. Thru cwm.
[Galaxy S 4 Mini General] E:V:A:
Probably the CVE-2013-6282 has been patched in this version. Even though Samsung is usually not that fast issuing patches, this is already an old vulnerability issued 20131025. But we also know that Samsung often take shortcuts when applying patches...

Second, if you look at the get-root sources memo.txt file you will find:

# use CVE-2013-6282 vulnerability
# kernel start address 0xc0008000
In some cases, modify KERNEL_START_ADDRESS or KERNEL_SIZE in 'getroot.c'

And in getroot.c see:

#define KERNEL_START_ADDRESS 0xc0008000
#define KERNEL_SIZE 0x2000000
#define SEARCH_START_ADDRESS 0xc0800000
#define KALLSYMS_SIZE 0x200000
...
int main(int argc, char **argv) {
char devicename[PROP_VALUE_MAX];
char buildid[PROP_VALUE_MAX];
FILE *old, *new;
int found;

__system_property_get("ro.build.product", devicename);
__system_property_get("ro.build.id", buildid);
printf("ro.build.product=%s\n", devicename);
printf("ro.build.id=%s\n", buildid);

// Check for known variants
if (!strcmp(devicename, "jfltevzw") && !strcmp(buildid, "JSS15J")) {
/* Addresses for VZW */
...
} else if (!strcmp(devicename, "jflteatt") && !strcmp(buildid, "JSS15J")) {
...
} else if (!strcmp(devicename, "[COLOR=Red][B]serranods[/B][/COLOR]") && !strcmp(buildid, "[COLOR=Red][B]JDQ39[/B][/COLOR]")) {
prepare_kernel_cred_address = 0xc009b88c;
commit_creds_address = 0xc009b378;
ptmx_fops_address = 0xc0f26a80;
ptmx_open_address = 0xc03220f0;
tty_init_dev_address = 0xc031a524;
tty_release_address = 0xc031a6a8;
tty_fasync_address = 0xc03195d4;
ptm_driver_address = 0;
} else {
if (get_addresses() != 0) {
exit(EXIT_FAILURE);
}
}

Thus for our build we need to at least change those, in case the automatic detection mechanism is broken for our builds. So unless someone can prove that this CVE has been patched, then we could try that out.
[Galaxy S 4 Mini General] k1mu:
1. The fact that the initial getsockopt() call gets "Bad Address" for the return error means that you've been patched. Further investigation of a different kernel base, etc. is only called for if you can actually do the arbitrary memory read/write that the flaw permits. In your case, it's not exploitable, so there's no point in worrying about the kernel start/size.

2. Are you using a "serranods" device with a JDQ39 build and it's running a patched kernel? That's not very nice of Samsung to do that. I can pull that autodetect out of the code (it saves a minute or two because Saferoot doesn't have to search for the kernel symbols). However, that's not going to help with getting you rooted as it's a sure bet that CVE-2013-6282 is patched.

I notice that you've got a ML4 baseband - anything after MK2 seems to have a fairly good chance of being already patched.

And anything running Kit Kat is going to be patched.

---------- Post added at 06:33 AM ---------- Previous post was at 06:28 AM ----------

FYI: I am not following this thread. If you want help, post in the original Saferoot thread.

However "This device is not supported" means just what it says. If you're fortunate to have an unlocked bootloader, use CF-Root instead, not Kingo.
[Galaxy S 4 Mini General] The Jinxer:
how do i know if my bootloader is locked? and will that method void my knox? i have a GT variant, which has hardly any locks and things that verizon or whatever others put on SCH models for instance
[Galaxy S 4 Mini General] mielletseed:
Yes, CF-autoroot will trip the knox bit.
[Galaxy S 4 Mini General] DevCake:
I understand it will trip the counter but has a custom recovery been successfully installed? I'm in a position that as long as the recovery works it is worth it.

~DC
[Galaxy S 4 Mini General] netzone:
Confirm worked on I9190 MK2 Build. Warranty Void still 0x0

Thanks.... :good:
[Galaxy S 4 Mini General] tempazz:
Not supported i9195, android 4.2.2 version UBNB3.
[Galaxy S 4 Mini General] ADR USR:
9192 MK4 rooted . knox 0x0 :good:

But when checking OTA updates = "You have changed your device ..." :bad:

How to solve?

In the saferoot.zip there unroot.bat.

works for this purpose?
[Galaxy S 4 Mini General] postal302:
If you take the update you won't be able to gain root again. Samsung has patched the exploit this root method uses.

If you want to stop the nagging update notifications go to /system/app and rename "SDM.apk" to "SDM.apk.old" and "SDM.odex" to "SDM.odex.old" then reboot.

Otherwise if you want to unroot you can use the "full unroot" option in SuperSU.
[Galaxy S 4 Mini General] ADR USR:
"full unroot" option in SuperSU fail.Does not work.

Some other method to unroot?

I did not make system modifications. I just root.

Unfortunately I can not unroot.

Edit :

now Full unroot worked.

But System status = Custom
[Galaxy S 4 Mini General] postal302:
The original thread has manual unroot instructions (look at post #2). Follow those and you should be returned to non custom status. If it doesn't work try rooting your phone again (begin fresh) and follow the unroot instructions.

Remember, if you unroot your phone and take the update you will not be able to root your phone again (at least not by this method).
[Galaxy S 4 Mini General] ADR USR:
Thank you. but Nothing worked.

luckily I managed to 1) manually delete the files in system / xbin.

2) I uninstalled Superuser.

3) Factory Reset ... and at the end: System Status = Official again.

4) Flashed I9192SERCNG2_SER over mk4

System : Official

Knox : 0 x 0
[Galaxy S 4 Mini General] XThe_GManX:
Hey, does anyone know if a safe root for the BML4 version will be available in the future? I just bought this phone a month ago and found out it came with Knox, the phone is good but Knox is probably the worse idea Samsung could have to make their phones more safe, I've come across a bunch of apps that needed root to function and now I'll have to wait for my warranty to past (two years) till I can finally enjoy my phone's true potential.

Thanks in advance.
[Galaxy S 4 Mini General] geri.st:
U could Google for towelroot.

This could do it without tripping knox

;)
[Galaxy S 4 Mini General] XThe_GManX:
I've tried towelroot, but it doesn't work with the BML4 version of the 9195 =/

Though I've read a post here on XDA that in the European Union, the Knox Flag being 1 doesn't matter as far as your warranty goes, they say that devices purchased in the EU have are required to have 2 years warranty and that flashing the device is not reason enough to void it =P
[Galaxy S 4 Mini General] geri.st:
Weird it worked for me with bml4! Already twice ;) sure u did it right?

Well, that's what EU says, but Samsung says different things...

U could show some screen shots, what your phone says, when using towelroot!
[Galaxy S 4 Mini General] XThe_GManX:
You did? That's weird because the latest towelroot does not support my phone, I've attached a screenshot of my baseband, is it similar to yours?

(had to write ontop of the picture because my phone isn't in English)
[Galaxy S 4 Mini General] mojtaba7b7:
root s4 mini 19190 kitket without computer

Hi .towel root and frama root dont woek who can help me to i root my phone? Russia rom
[Galaxy S 4 Mini General] geri.st:
Which Firmware Version are you running

Does it matter if Knox will be tripped?

---------- Post added at 03:07 PM ---------- Previous post was at 02:59 PM ----------

Now it is the phone of my gf, but AFAIK yes. I asked her to send me a screen shot ;)

So let's try together.

Install towelroot again

Let it ra1n

And then tell me what the apk says ;)
[Galaxy S 4 Mini General] XThe_GManX:
It says "This phone isn't currently supported".

My phone is currently running android 4.2.2, maybe it's because of that but Samsung Kies doesn't report any newer version.
[Galaxy S 4 Mini General] geri.st:
Just found out I am already on cne6

Where do you live?

Check out sammobile.com

Maybe there you can find an new version for your phone... As long as you accept using Odin (if you install non rooted fw later than yours eg cne6 Knox won't complain!) Then you can update and root your device!

sent dem from my bacon
[Galaxy S 4 Mini General] XThe_GManX:
No new firmware for my phone, I'll contact Samsung to know if they recognize the EU law. But otherwise I'll just have to wait for an update to my phone or another method to root the BML4 version under Jelly Bean.

Thanks for all the help!
[Galaxy S 4 Mini General] geri.st:
You can install cne6 with no problem, you can keep the modem of your country. No problem with any law ;)

sent dem from my bacon
[Galaxy S 4 Mini General] XThe_GManX:
I don't understand what you mean with cne6, is it a ROM?
[Galaxy S 4 Mini General] geri.st:
Yes. Like bml4

For Germany it's

http://www.sammobile.com/firmwares/3/?download=31540

In which country do you live, maybe there is a ROM, but not for your carrier.

sent dem from my bacon
[Galaxy S 4 Mini General] XThe_GManX:
There is CNE6 for a different carrier from Portugal. I guess I could install that one, root it and go back to mine. But I'll contact Samsung before and post the results here ;)
[Galaxy S 4 Mini General] geri.st:
No, then you have to stick to that firmware...

And don't use Vodafone etc.. They have bloatware and are mostly locked for sim arts cards for their carrier!

Use eg dbt, for Germany, that is not simlocked. If you then flash your actual modem, then nothing goes wrong!

Anywhere in that forum you can read a mail from Samsung, AFAIK they say the warranty is gone, when Knox is tripped ;)

sent dem from my bacon
[Galaxy S 4 Mini General] mojtaba7b7:
frimware vsrson
[Galaxy S 4 Mini General] JolkyB:
Custom rom?

Okay, maybe someone can help me here. I am totally new to this phone and the only custom rom I have installed is cyanogenmod on my s3. I have the sch-i435, and I don't care at all about my warantee. How can I get a custom recovery and cyanogen or something similar, if at all? I can't seem to find any documentation anywhere.
[Galaxy S 4 Mini General] postal302:
Unfortunately with Knox the boot loader is locked down and trying to install a custom recovery will hard brick the phone.

You'll want to research safestrap to see if you can use that. I'm not familiar with it at all so I can't offer any advice on it but that would allow you to load custom roms. Otherwise if you just want root look into towelroot over in the S5 forums, that should work for all Verizon Samsung phones.
[Galaxy S 4 Mini General] mielletseed:
Are you sure? As far as I know the KNOX boot loader will detect custom kernels or recoveries and trip the knox flag but not prevent you of installing any custom software ...
[Galaxy S 4 Mini General] osvanberg:
Correct!
[Galaxy S 4 Mini General] postal302:
If I understand right (and correct me if I'm wrong) safestrap operates like an app in Android instead of overwriting your existing operating system. At a certain point in boot up the safestrap "app" takes over then creates a complete operating environment inside of the safestrap program. At that point you "boot" into a safestrap compatable recovery which then loads a safestrap compatable ROM. This essentially hijacks the android boot up, runs a complete (safestrap compatable) recovery and ROM and never finishes loading your stock software. All your existing stock bootloader, recovery and ROM are left untouched and existing on your phone.
[Galaxy S 4 Mini General] postal302:
Sorry, I just reread your question and realized I answered the wrong question. From what I understood, if the bootloader is locked a phone will get bricked by attempting to install a custom recovery. As far as I knew, phones loaded with Knox have a locked bootloader.

The i435 I have access to its my wife's so I don't get to play with it enough to know what works best.
[Galaxy S 4 Mini General] mielletseed:
If the bl was locked you would not need knox flag...

You can install any ROM or recovery but this will be detected and your phone gets marked "for ever"
[Galaxy S 4 Mini General] tempazz:
I have i9195 with firmware i9195XXUBNB3. I had trouble with root. Saferoot said that that my device is not supported.

After some reading.

1. I flashed kernel from I9195XXUBMJ7 with ODIN.

2. Rooted with safe root.

3. Updated SuperSu.

4. Disabled KNOX with SuperSu.

5. Restored kernel from i9195XXUBNB3 with ODIN.

And now I have rooted UBNB3 firmware and knox still 0x0.

I guess that this method must work also with I9195XXUBML4 firmware. But in step 5 you need to flash kernel from I9195XXUBML4.
[Galaxy S 4 Mini General] real_mister:
Thanks for the tip! Worked as expected.
[Galaxy S 4 Mini General] Projost:
inebdu continued

I have exactly the same problem. I would like to root my phone using saferoot or towelroot.

1. is it possible to flash the kernel only? if so where did you find the stock kernel files?

2. I have downloaded the I9195XXUBMJ7 and i9195XXUBNB3 firmware for my country from sammobile. Can i flash just the kernel from this? and how?
[Galaxy S 4 Mini General] TRB01:
Hello, I've googled a bit and I'm finding nothing on how to flash the KOT49H S4 mini from verizon. I tried the root method listed in the first post but it said my kernel was patched. Is this the end of the line for me or is there an alternative that works? I saw another method that required firmware images but it looked like that was for a different version of the S4 mini and not the i435 from Verizon.
[Galaxy S 4 Mini General] devinpatterson:
I was (and currently am) on KOT49H, for my i435. I used towelroot, and it was painless.
[Galaxy S 4 Mini General] AbanadonedFace:
Is there presently a way to re-root or keep root after updating to the newly-available 5.0 or 5.0.1 update OTA or through Kies?
[Galaxy S 4 Mini General] override1984:
I'm looking at my TowelRooted VZW SCH-I435 (4.4.2) (kernal version 3.4.0 dpi@SWDD3013 #1 Fri May 23 23:07:04 KST 2014) (build number KOT49H.I435VRUBNE1) with NOX still intact as it constantly spams you have updates available over and over refusing to let me do much of anything but update ... but I don't wish to lose my root... I'd rather it be outdated and rooted then lose all my functionality .... what should I do? fight past all the popups? .. or just give in? Has someone figured something out?

Will TowelRoot still work after the update? Can it be reapplied after update and still succeed?

I just got this phone not too long ago .. it replaced my Galaxy S 1 (fascinate) that i kept rooted and rom'd for years ( Thank you XDA Community! )
[Galaxy S 4 Mini General] AbanadonedFace:
What I did for the moment is used a free app called App Quarantine to freeze the "SDM" process. I had to go to the menu and check an option allowing system processes to be shown in the list. No more update notifications.

God damn do I hate VZW and Samsung after trying to do stuff with this phone. Everything is closed off. Can't even use the device as mass storage. None of the ROMs are ever available for the SCH-i435, it's always the other carriers' models of the phone. Will not ever be renewing a Verizon Wireless contract as long as I live.
[Galaxy S 4 Mini General] override1984:
Awesome thanks for the tip at least I can use my phone in peace! :victory:
[Galaxy S 4 Mini General] j3grizz:
Recovery? ?

Is there a recovery for this phone yet? Sorry ahead of time if this doesn't belong here! I can't seem to find anything!
[Galaxy S 4 Mini General] gtaber:
The app you mentioned says it's for rooted phones only......which is what I can't get on this P.O.S. , ROOT.
[Galaxy S 4 Mini General] dantoys:
No Worky for my Phoney...Dang Verizon...

Verizon Wireless Samsung Galaxy S4 mini SCH-I435 Android 4.4.2 Hardware I435.05

config vers..B13.SAM.SCHI435.0

I need this phone Rooted, Can Anyone Please Help.. I have tried every method I have found on XDA Site...

(Except Removing Stock Rom and Applying Custom Rom)

Please Help, Thanks in Advanced..

fyi..Towel Root Failed, Saferoot Failed, i tried many others from google..(Most are phishing sites..)
[Android General] dj.houba:
Hi everyone,

I need to restart custom ROM counter, I tried Triangle Away, but when I click "Reset flash counter" and "Continue", nothing happen. No reboot, nothing.

On my SGS III (I9300) I tried it on custom firmware, on stock firmware (Android 4.2.1, I9300XXEMG4, France version) and on older version 4.0.4. Rooted, permission granted, package for GT-I9300 by "Triangle Away" downloaded. I bought last version of Triangle Away from market v3.25.

Please help, how to boot to Triangle Away recovery? :eek:
[Android General] dj.houba:
Solved

Funny, 1hour after I add this post, developer of Triangle app released new version that fix this bug.

Now it's working well :)

Maybe admin can delete this topic.
[G Pad 8.3 Themes and Apps] woody1:
I just installed Nova Launcher on my stock G Pad and imported all of the apps from the stock launcher. The stock weather widget doesn't seem to work with Nova. Does anybody know a workaround to get it to work?
[G Pad 8.3 Themes and Apps] haasgo:
Afaik not possible. Like on samsung roms, only for stock launcher. Stock calender widget should also crash on nova launcher.
[G Pad 8.3 Themes and Apps] CuraeL:
You are correct, Sir. Stock widgets, HTC, LG and Samsung will only work in their respective UI Launchers.
[G Pad 8.3 Themes and Apps] woody1:
OK, thanks for the heads up on that. There are plenty of other weather widgets, I just like the look of the LG stock one.
[Xperia Z General] rebelos:
Necessary Files for Xperia Z :

Tip :For Building any Rom for Xperia Z u need these specific device files

1 . first is "sony.xml"

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<project path="device/sony/fusion3-common" name="CyanogenMod/android_device_sony_fusion3-common" remote="github" revision="cm-11.0" />
<project path="device/sony/qcom-common" name="CyanogenMod/android_device_sony_qcom-common" remote="github" revision="cm-11.0" />
<project path="device/sony/yuga" name="CyanogenMod/android_device_sony_yuga" remote="github" revision="cm-11.0" />
<project path="vendor/sony" name="CyanogenMod/proprietary_vendor_sony" remote="github" revision="cm-11.0" />
<project path="kernel/sony/apq8064" name="CyanogenMod/android_kernel_sony_apq8064" remote="github" revision="cm-11.0" />
<project path="hardware/sony/DASH" name="CyanogenMod/android_hardware_sony_DASH" remote="github" revision="cm-11.0" />

</manifest>