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
Related
Hello people,
I am a newbie here, and I would like to root my Sony xperia T build 9.1.A,1,140
I have tried bin4try rooting system and it all went through fine, but after starting the phone I downloaded rooting checker and it said that my device was not rooted. This was also confirmed when trying to use lucky patcher. I did have however the SuperSU app installed.
Then I withrew that root just in case from the removal option, and tried to do it through the DoomLord method. Whilst installing it said that my device was not supported. Since then I have been reading and trying to figure out how to upgrade my build version to 141 in order to root it through DoomLord method, and I have the boot.img from the stock .141 kernel. I am just a bit confused and don't know how to play it safer.
Also, I have tried installing the CWM but since I don't have a rooted phone it didnt let me install. I now have a stock Xperia T with android JB 4.1.2 build 9.1.A.1.140 and would really like your help to see what I can do.
I will now head to bed, as my brain hurts from so much information, I hope to get this sorted soon.
Thanks a lot to you all for your time and effort!
Sincerely,
Jose
UPDATE
I forgot to mention that I tried to install CWM but it didn't let me because the phone was not rooted. Also there is apparently no way to unlock my bootloader.
This morning I donwloaded the 141 tft file, a polish version, and decided to flash it into my phone. After flashing and starting the phone, the sony wave colour thing did several loops for about a minute or two. The the phone started as usual and everything works fine except for internet data.
AT THIS POINT
I do not know where to proceed, I go in mind to now try rooting my phone through Doom's method but I am afraid that maybe I can screw it up more or root it but still have no mobile data which would be almost useless to me.
Please I would really appreciate the help of anyone.
THANKS!
barceloneru said:
Hello people,
I am a newbie here, and I would like to root my Sony xperia T build 9.1.A,1,140
I have tried bin4try rooting system and it all went through fine, but after starting the phone I downloaded rooting checker and it said that my device was not rooted. This was also confirmed when trying to use lucky patcher. I did have however the SuperSU app installed.
Then I withrew that root just in case from the removal option, and tried to do it through the DoomLord method. Whilst installing it said that my device was not supported. Since then I have been reading and trying to figure out how to upgrade my build version to 141 in order to root it through DoomLord method, and I have the boot.img from the stock .141 kernel. I am just a bit confused and don't know how to play it safer.
Also, I have tried installing the CWM but since I don't have a rooted phone it didnt let me install. I now have a stock Xperia T with android JB 4.1.2 build 9.1.A.1.140 and would really like your help to see what I can do.
I will now head to bed, as my brain hurts from so much information, I hope to get this sorted soon.
Thanks a lot to you all for your time and effort!
Sincerely,
Jose
UPDATE
I forgot to mention that I tried to install CWM but it didn't let me because the phone was not rooted. Also there is apparently no way to unlock my bootloader.
This morning I donwloaded the 141 tft file, a polish version, and decided to flash it into my phone. After flashing and starting the phone, the sony wave colour thing did several loops for about a minute or two. The the phone started as usual and everything works fine except for internet data.
AT THIS POINT
I do not know where to proceed, I go in mind to now try rooting my phone through Doom's method but I am afraid that maybe I can screw it up more or root it but still have no mobile data which would be almost useless to me.
Please I would really appreciate the help of anyone.
THANKS!
Click to expand...
Click to collapse
from what i understand you can't flash a custom kernel unless ur bootloader is unlocked!! You may have to flash an appropriate firmware with flashtool that is rootable and then try to protect root and then try a fota but don't use seus or pc companion!! Someone correct me if i'm wrong!!
I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
devildogwillbur said:
I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
Click to expand...
Click to collapse
WARNING!! If you process that downgrade, you will trip KNOX security, then your phone will be bricked. Also, ESN cloning is illegal to talk about on XDA.
sent from my GS3
I will trip knox security? What exactly does Knox do, and what do you mean by that? I though Knox just makes it read 0x1 on the odin screen if you flash now? If thats what you mean, I already did that by flashing cf-auto-root. Its my understanding that the boot loader is the issue when downgrading. but on this site, they say that only at&t users should not try it, and technically this is a sprint phone I believe. Just with added software.
If I am wrong please let me know.
Also, I think you mean that it is not acceptable, not illegal. Illegal would imply I could get arrested for commenting about phone cloning on this site. And although cloning your personal phone for your own uses is not illegal, I will not mention it again on these forums. Thanks for the warnings.
sent from my GS3
Also, I guess I am not necessarily trying to downgrade, just trying to find out what needs to be done so that I can flash or ANYTHING to get away for 4.3 issues. Since the upgrade, my fiance sent me an mms and it has popped up in my messages 5 times, so it looks like she keeps sending it, but I am unable to open it because it wont download.
The more important issue is root. I want to be able to use my root apps to backup, re install my old backups from my last s3, and attempt to get my msl to try and fix the mms issue.
sent from my GS3
Today has been a productive day so far... using Skunk Ape1's root method "[Tutorial] Rooting the Sprint GalaxyS3 the Easy Way" I was able to get twrp recovery installed. (I wasn't able to do this before because prior the only method i knew was to go to goo.manager and that didn't recognize my device) SO, with twrp installed, i flashed the zip file from Skunk Ape1's root method. Following the instructions to the T everything seemed to work fine. After reboot, I had a knox message popped up, saying "SECURITY NOTICE: Unauthorized access to a secured area has..." I relive that root has been installed but knox is keeping locked up still. I am going to look for this mysterious "Knox remover script" that you will see in the first post on that page, then I will attempt root again.
I have officially given up on root currently. I have tried every root method I can find, my flash counter is somewhere around 13. I was able to use the knox removal script from here If anyone has suggestions for root, I am open to ideas. Thanks.
Finally did it
So, today i was just realizing the lack of space i had on my phone from downloading stuff and photos so i wanted to clean it up. I moved all the important stuff off, and though it would be a good time to factory reset and just have a clean new phone to start over again. ( I missed flashing and this was the closest thing I had) So, during the process of factory resting i wanted to clean everything so i click data, cach, internal external.. system.. yeah well bad idea. my phone rebooted and go stuck on the boot. So i restarted in recovery and reset again and this time is warned me that there was no OS installed... F*ck... Zact customer service wont give me the "custom software" that they installed so im screwed.
After hours of thinking and trying to do stupid odd ball things that i knew wouldnt work. I downloaded a sprint stock 4.3 tar file and odined to my phone. started up fine. works great. so... what zact said about flashing roms bricking this phone was BS.. the only custom thing i have seen was in the zact mobile app that came installed had some extra features used to send usage info and reboot stuff for zact troubleshooting. so with stock sprint rom, and zact mobile app im back to my phone working. AND with that, im going to move on to the rooting, and flashing of this piece of crap. Ill be back with more details later.
I have installed CyanogenMod with full root!!!
well first off, i had the CMinstaller set up but it did not recognize my device so after a while i decided to attempt to cf_auto_root, which seemed to work but failed root checker. I wanted to try another method. I had CMinstaller still up* I was attempting THIS method to root. I was using philz_touch_6.15.4-d2spr.tar.md5 that I flashed using Odin 3.07 (that I have had for a long time on my pc. so google that one)https://www.google.com/search?q=odin+3.07&oq=odin+3.07&aqs=chrome..69i57.3464j0j1&sourceid=chrome&ie=UTF-8 After i installed Philz touch, i noticed CMinstaller noticed my phone and started downloading system files. I continued what i was doing with the root method and installed DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0 and UPDATE-SuperSU-v1.93 just as CMinstaller finished its download, so i said what the hey, and clicked install. next thing i knew i was running cyanogenmod with full root!!! please someone else verify this and let me know if you get it going too.
Deleted
Stock 4.3 with root
so yeah, just for to check i flashed back to stock 4.3 (not sure who uploaded it but it works) It does have knox so be warned. I then followed the root method in my previous post and it worked fine. i have stock with root. If someone can try it without using that tar file, let me know. Cant really go back once you do it so i cant try the root method with the zact "custom software" myself. Let me know what you find out. Hope this helps someone.
Thanks
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Zact to Ting
Barnsie said:
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Click to expand...
Click to collapse
What I would do and have done for my fiance and myself, get on Zact.com live chat ask them to Deactivate your phones. and give them the DEC on the back of the phones. It takes about one min for it to complete per phone. Then go on over to Ting.com and start up a new account with them using your old zact phone. Ting also lists the MSL that i struggled so much trying to get. I would recommend flashing a stock rooted rom debloated, to get all that ZACT crap off your phones. and start out fresh.
Hi,
This is a great site.
I am doing this cause I deleted some photos by accident and want to use one single program that needs the phone to be rooted. Because there is no mass storage connectivity you know how it goes.
I used Odin3 to install "CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5" to my Samsung Galaxy Note 2 with Android 4.3.
Odin says "PASS!". When I try to start the SuperSU (version 2.01, was installed by Odin and CANT BE UPDATED in the play store, not even removed only opened form play store. This was the most common fix that people are giving to this situation, but it does not work for me because there is no update possibility) Because KNOX says unauthorized attempt to access not accessible areas. SuperSU does not prompt the possibility to terminate KNOX like some people are advising to do, even tough the 2.01 version of SuperSU should be able to do this. Even the RootChecker says that my phone is not rooted.
So my assumption is that the Root has not worked on my phone even tough Odin says so. So I want to try some other approach to root this phone. I just would like to know should I do some check for what Odin HAS changed in my phone and to try to change them back so I can for example try Kingos root safely.
So the questions are:
Does some one have a possible fix to my problem without me having to re root?
How can and what should I check before trying another root?
If I have to go back with stuff that Odin did, without it doing the root properly how can I do that?
And one a bit different question:
If I factory reset my phone it will install the 4.1 I thin on it, has no KNOX, will it write that on the part that is empty and might include that data of my deleted pictures or does it write it on the area that has the previous data of the Android system?
Thanks for advance if there is any advises.
Partial answer:
I followed basicly this instruction,
http://forum.xda-developers.com/showthread.php?t=2538991
just needed to find the correct TWRP for my phone and used the older 1.65 SuperSU, there is something wrong with the 2.01 and it compatibility with my phone.
This video also helped cause the information was similar to the one in the link.
https://www.youtube.com/watch?v=ZQAkLgXjnCo
Installed the DiskDigger and got most of the photos, so now I need to find out how to convert it from root version to version so I can upgrade my phone.
Everything is really easy with Odin. If the packet that I installed with it first that does't istall the custom recovery system would have had some other KNOX combatible version of SuperSU I think it would have worked. No I just needed to use the KNOX remover to remove it from my phone.
Thanks for the form all the answers where her and it just took me some time.
This is a method to obtain working root & Super Su by chainfire with up-to-date binaries for the
AT&T Variant of the Samsung Galaxy Tab 3 7.0 (SM-T217A) on 4.4.2
Let me make very clear, I did not develop these apps!
This is just a method I found after searching & some trial and error.
I thought it may be helpful if it were available here on the forums.
I spent too long looking for a method that still worked on an OTA up-to-date device etc.
Nobody bothers for an old device with a locked bootloader. :crying:
I'm sure everyone that has had or currently has this model knows that Kingo Root works (at least for partial root), and a big thanks to them for their effort & hard work.
But if you're like me, you want the freedom to use Super Su or any of the other available options out there for managing permissions.
Either way, thanks to Kingo for a temporary solution.
And thanks to gatesjunior you can have your freedom of choice back.
(Although I highly recommend that you use the version found at the bottom of the post, because the newer version I tried stalled at the 1st stage.)
If this method ends up working for you I think it would be worth the $3.99 to support the developer by purchasing his app!
(If you feel adventurous you can attempt using the google play store release, but I had no such luck.)
I had originally tried to use Super Sume version 6.5 with Kingo Root but, it just ended up losing my root access and I had to re-root my device.
Yesterday I attempted to run Super Sume v. 9.2.6 I believe, but for some reason it didn't recognize it Kingo, or Kingroot as being installed on my device.
So I ended up uninstalling it and trying an older version I had read worked, and it succeeded!
Instructions for obtaining Root & Migrating over to Super Su are as follows.
If you are currently rooted using Kingo Root, un-root from within the Kingo app 'Superuser' and proceed to uninstall the rest of their apps..
Install & run Kingroot 4.5; When this is finished, restart your phone and run an app to verify you have root. (I use the free version of Root Checker.)
This may not be necessary but at this point I re-installed Busybox.
Install & run Super Sume v6.7
Restart & Verify Root!
:fingers-crossed: Success! :highfive:
If for some reason your device failed to achieve root using Kingroot after removal of Kingoroot; you may have better luck leaving your device rooted with all the Kingo Root apps installed until after you install Kingroot.
(Although I'm sure most people would advise against it, I actually skipped the un-root/un-installation procedure until after I had installed Kingroot 4.5 because I my battery was at 9%)
Honestly it shouldn't really matter though Super Sume is supposed to remove everything like that anyways
Required APK's can be found below.
4/12/23-Edit: Replaced broken links with working ones from my google drive.
Kingroot 4.5.apk
Super Sume 6.7.apk
7z archive incase drive has false-positives: here password: xda
Thanks for your efforts!!
Hi, I would really like to appreciate your efforts for this but the links you gave at the end are not working so I am unable to even try your given method.
Thank You!!
Fixed Broken Links
SteeleRocky said:
Hi, I would really like to appreciate your efforts for this but the links you gave at the end are not working so I am unable to even try your given method.
Thank You!!
Click to expand...
Click to collapse
Sorry about that, I went ahead and put them on my google drive. Let me know if it works out for you.
Fyi, this method worked for me on a sprint sm-t217s galaxy tab 3 7.0 running kitkat 4.4.2 baseband OH1..
The:Dude said:
Fyi, this method worked for me on a sprint sm-t217s galaxy tab 3 7.0 running kitkat 4.4.2 baseband OH1..
Click to expand...
Click to collapse
Glad to hear it!
I figured it would probably work on all the Samsung Galaxy Tab 3 7.0 variants but I only have the AT&T model.
If you don't want to flash your system(or can't in my case) this is probably the next best thing.
Worked for me on my AT&T SM-T217A on 4.4.2 T217AUCUCNI1 & T217AUCUCNI2
Thank you!
sixn3is7 said:
Worked for me on my AT&T SM-T217A. Thank you.
Click to expand...
Click to collapse
You are most welcome. :victory:
Enjoy!
Got hit with a infected file warning.
Try this archive instead, password is xda.
https://drive.google.com/file/d/0ByBY1FxjHZd2WnlHMEVVTzB1VXc/view?usp=drivesdk
Let me know if updated link works, otherwise... I will update OP when I get home.
I know this thread is quite old but it helped me get back on track thanks to r4e_hafintosh and his great instructions. I am working with a Galaxy 3 7.0 SM-T217A (AT&T) version. Wasn't working right so I did a full reset. Tried to get TWRP installed and things went to hell quickly. Biggest problem then was finding a stock 4.2.2 and/or 4.4.2. I finally located both here: https://androidfilehost.com/?w=search&s=T217A so I was able to use the repair files and get back to stock 4.4.2. Then I followed instructions from r4e_hafintosh to get KingRoot installed along with BusyBox. I'm currently waiting for SuperSUMe to install and it appears I'm back on track. Thanks to r4e_hafintosh, the unknown person who posted the repair files and everyone who has posted at XDA and other Android sites that allowed me to finally hunt down what I needed. Probably a small victory for those much more well versed in customizing ROMs but I big win for me. Hopefully the next person trying to find stock files for the AT&T SM-T217A will find this post as well. Thanks all!
How can we unlock bootloader for it
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