Problems Rooting the S4 Mini - Galaxy S 4 Mini Q&A, Help & Troubleshooting

I rooted my S4 Mini a while back using Odin and it worked fine. I recently updated my phone to the latest firmware which I think is 4.4.2 and it removed my root access. I tried rooting using Odin but it would not work. My phone model number is SGH-I257M. I looked up how to root for that model and during the Odin phase, it would be stuck on RESET and it wouldn't say PASS hence when I verified for root it failed.
I was also told that rooting using the method for the I9195 would also work. For this one, Odin does say PASS but when the phone reboots, the phone did not install the S4Mini_kit which consisted the SuperU and the BusyBox hence when I verified for root it failed again. I feel as if I tried everything to my knowledge. It would be great if someone could shed some light in what I may be doing wrong.
Thank you

Related

[Q] Root for sm-t217s running the new 4.4.2 kitkat update?

Hello my names Aaron, I rooted my galaxy tab 3 (sm-t217s) a little bit ago then unrooted just because my wifi wasnt turning on.. I had to do a stock restore through odin to get it all working again. When I did that I got the new kitkat update and gladly updated it. Now again though I want to root it so I can again do all the great things you can do with rooting!
So my questions are:
Can I root it running 4.4.2 the same way I did when I was running 4.2.2? Will it brick it if I just put on a custom recovery the same way as before and let that install superSU?
I would just like to know and if not then is there another way currently to root it?
I couldnt find anything about it that is why I am posting about it.. must not be a very common tablet?
Anyways thanks for your time and help!
WhiteRage said:
Hello my names Aaron, I rooted my galaxy tab 3 (sm-t217s) a little bit ago then unrooted just because my wifi wasnt turning on.. I had to do a stock restore through odin to get it all working again. When I did that I got the new kitkat update and gladly updated it. Now again though I want to root it so I can again do all the great things you can do with rooting!
So my questions are:
Can I root it running 4.4.2 the same way I did when I was running 4.2.2? Will it brick it if I just put on a custom recovery the same way as before and let that install superSU?
I would just like to know and if not then is there another way currently to root it?
I couldnt find anything about it that is why I am posting about it.. must not be a very common tablet?
Anyways thanks for your time and help!
Click to expand...
Click to collapse
Either use towelroot to root from within android or you can still flash twrp from Odin and root that way. Twrp may set warranty bit, mine was was already tripped so I can't say dor sure if it does.
Sent from my SCH-I535 using XDA Free mobile app
I used towel root on4.4.2 update worked great, and yes twrp does set set warrenty bit
Sent from my SM-T217S using Tapatalk
I used towelroot on my tablet, it does what it has to do. Does not reboot, but when I use Root Checker it says that I do not have root.....any suggestions?
I was rooted with towel root fine under the June 2014 update to 4.4.2, but I mistakenly took the update to NH4 while rooted. My device seems to be fine, but I lost root and Towel root will not seem to root me again, no way, no how. My warranty bit is clean, and I don't want to trip it, but I'd love to have root back. Is there anyything I can do on NH4 from within Android to get root back? TIA
How did you do an unroot through Odin and which version of Towelroot did you use to root it again? I have the same tablet.
I have SM-T217S running Kitkay 4.4.2. I've tried almost every root app there is (Kingo, Towel, ect.). They all say my device isn't compatible. And when I go to update under settings, it says that my device is running unauthorized software and that I need to use Samsung kies to flash. But it has no root & no custom software, everything is normal. I have tried using computer to root but still nothing. What could I do to fix it?

Samsung Galaxy S4 Mini ATT Unrootable 4.4.2

I have tried many methods which do not flash your device ( towelroot, poot,etc ), and I have tried some of the others: Kingo and Odin.
None of these methods work with the Samsung Galaxy S4 Mini ATT running 4.4.2. All of the .apk attempts result in saying " Your device is not currently supported " or just not working. I have made many attempts with Odin, with many different types of files, all of which have ended in saying " Failure ". I really want to root my phone so I can remove all of my bloatware and really use my device. Any help will be appreciated.
May have your service provider, AT&T, prevented the phone from being rooted?
RoyaLKurTx3 said:
May have your service provider, AT&T, prevented the phone from being rooted?
Click to expand...
Click to collapse
I can provide any information to see if my provider has done something to my phone to prevent it from being rooted.
Rooted with king root
I was able to root my at&t s4 mini using king root. I had to do a factory reset so my phone was stock with no software updates.

[Q] TowelRoot on 4.4.2 not working 2015

So i recently been wanting to root my T-Mobile Galaxy Note 3 again, the first time i did it in TowelRoot and it worked just fine, but i had to turn it in for warranty, i got a new one and I'm wanting to root it, i open TowelRoot and it says "This phone isn't currently supported". What? that doesn't make sense because i did the same process before with the exact same model phone and it worked just fine ( I run 4.4.2 ) as i looked into the problem i found that if you tap the "welcome to the towelroot v3" 3 times, it gives you a code that you can change, i changed it to all the available codes to try and fix it, got nothing. i have no idea why its deciding to not root this phone but it worked just fine with my first Note 3. Please someone help, any help is fine.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Towelroot won't work on kitkat, you need chainfire's autoroot, look in original development.
Pp.
If you flash the NE6 kernel using Odin you can then use Towelroot to root your phone. Then you can flash the NK3 kernel back If you want

[Q] Rooting SCH-R890/US Cellular Galaxy S4 Mini

Hi! I've got a Galaxy S4 Mini from US Cellular. The model number is SCH-R890. I had rooted my phone, but my phone had accumulated junk over the year or so I had it, so I booted into (stock) recovery and restored the firmware.
I now have the official/stock firmware on my phone, but I'm unable to root it.
I tried towelroot (kernel version is 3.4 from May 20, 2014,) which is what I originally used to root my phone, but after I installed SuperSU from the Play store, it says it can't find the su binary.
I tried Framaroot, and both exploits failed.
I tried CF Auto Root, and I followed the instructions, but my phone got stuck in a bootloop. I ended up having to boot in to recovery, clearing the cache partition, and rebooting. This got me out of the boot loop, but as a result, I also do not have root.
I think I've provided all relevant information except for the build number, which is KOT49H.R890TYUBNE4. There are no available OTA updates. If there's any other information needed, feel free to ask, and I'll try to provide it.
As I had root on my phone before restoring it, it would be nice to get it back, but if I can't, I guess that's okay too. Any ideas?
I apologize in advance for any engrish/grammatical issues I may have made in this post, I'm a bit tired.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers. Register an account on XDA for full access.
Stand by
Good luck

Samsung galaxy s9 root problems

I'm new to rooting and i rooted my phone today. But, when trying to confirm root for an app that needed it to be root it immediatly restarted and gave the security error saying the phone has been flashed with unauthorized software & is locked and i had to flash stock firmware to get out the error. During the time rooting phone nothing went wrong for me. So i'm curious. Is there something i forgot to do that made my phone do that
i have same problem. I´ll tried wit a new rmm by pass

Categories

Resources