Hello,
I've just rooted my S4 Mini following the instructions here: http://forum.xda-developers.com/showthread.php?t=2364980 (I didn't add the optional step of flashing the custom kernel because, in all honesty, I've no idea what it means).
Root Checker tells me that the root was successful. However, I'm still unable to remove the annoying apps that came preinstalled on my phone - which is the reason I wanted to root in the first place! I go to Apps - Uninstall but the only ones I have the option to remove are the ones I've installed myself.
Is there something I need to do that I'm missing or has something gone wrong?
Thanks in advance. Apologies if I've missed something obvious!
.A. said:
Hello,
I've just rooted my S4 Mini following the instructions here: http://forum.xda-developers.com/showthread.php?t=2364980 (I didn't add the optional step of flashing the custom kernel because, in all honesty, I've no idea what it means).
Root Checker tells me that the root was successful. However, I'm still unable to remove the annoying apps that came preinstalled on my phone - which is the reason I wanted to root in the first place! I go to Apps - Uninstall but the only ones I have the option to remove are the ones I've installed myself.
Is there something I need to do that I'm missing or has something gone wrong?
Thanks in advance. Apologies if I've missed something obvious!
Click to expand...
Click to collapse
Just install titanium backup and uninstall them from there!
Sent from my GT-I9195 using Tapatalk
Ah, as simple as that. I'd thought you might be able to do it the same way as with other apps.
Thanks for your assistance!
okay so I followed this link true-android.blogspot. com/2014/03/root-t999uvuenc2-t-mobile-galaxy-s3. html to root my s3. I did not get the yellow bar that I was supposed to but I decided to follow through anyway. At the end of it I received the PASS message. I had superuser installed. The problem is that it seems like knox is keeping superuser from granting anything root privileges. Every time I launch superSU, it leaves me with a message of "unfortunately SuperU has stopped. On my notification bar it shows security information and the message "an application attempted to acces system on your device without authorization. This attempt has been blocked...." i also can't seem to log into it to uninstall it because it gives me an error. root checker tells me I don't have proper root access but I am assuming it's because superuser is being blocked. I am unable to uninstall superuser and my flash counter went up to one so I am "assuming" that I am rooted. Does anyone know how to disable knox? or if it is not knox and it turns out that my device is not really rooted, do you guys know how I can root it? this is all really confusing. Any help would be greatly appreciated.
Thanks in advance.
First thing, you will have much better luck just sticking to the forums here. Not many are willing to assist with other sites posted processes because for the most part, everything you could possibly need is right here.
Before you do much else, look over the sticky threads in each of our sections. You will find lots of very important info and ill bet a better way to accomplish what you want to do.
Check my firmware thread for root66 firmware. Flash it and your rooted and knox free. Click on the root66 heading to go to the thread.
By reading the sticky threads you will also find alternative methods. The only one I warn against is something called the toolkit.
If you have specific questions about anything feel free to ask.
Sent from my SGH-T999 using Tapatalk
Moved to Q&A.
What I did to root my s3 was I used odin. Put http://forum.xda-developers.com/showthread.php?t=2370981device on download mode. Download a recovery tar click on pda and flash it. After device reboot put su zip on sd card and flash on recovery and you will be rooted. You can you root explorer apk to delete knox from /system/app.
I'll post the files you need.
You can find everything on that website if different s3
Where it says xdadevelopers recognized contributor: click to show content...you will find all recoveries, odin, drivers, su
MODERATOR EDIT - Attachment Removed
Thread cleaned
I upgraded to 4.4.2 on my TMobile Galaxy S4. I did this Via KIES. Afterwards, I tried to root - and this is where things seemed to go wrong.
I used ODIN 3.185, and used T-Mobile_OUDHS-Recovery-jfltetmo and then installed ROOT_M919UVUAMDL.
Since then, I have the
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Message at boot, and the Samsung Galaxy S4 logo.
I tried to use Odin to put over the top CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar
I tried also to use the SD card to update again to what I think is the stock firmware from here: http://forum.xda-developers.com/showpost.php?p=50977575&postcount=49&nocache=1&z=9496224221703208
When doing an update, there were a couple of errors - but it went through. However, on reboot the same error.
Any help would be extremely appreciated.
My next try is to do the unroot steps from this post: http://forum.xda-developers.com/showthread.php?t=2335109
But hopefully someone can give some more advice before I wipe the whole thing.
Since it's a work in progress, I figure I will post as I go along.
I downloaded the 1.5gb TMB-M919UVUFNB4-20140314115123 file from the unroot link above. I then used Odin to install it... and was able to stop at step 9 - before doing the data wipe/factory restore. I can now get my phone to boot.
I am feeling so good - that I'll try to root again.
Rooted, and SuperSU instaled - all is well to this point...
Since I was fairly freaked out, hopefully this helps someone down the line (or me - since I'm fast to forget).
You tripped the Knox flag. That's all that happened. It won't affect your ability to use the phone. You didn't do anything wrong. it's normal when you root a Knox protected device.
I ran into the same issue as you on my TMobile Samsung Galaxy S4 and I wanted to say thanks for this post! It helped me get my phone restored back to the way it was and thankfully I didn't lose anything! Thanks so much!
Was wondering however.....how did you get it to root successfully after this?
I used this guide to try to root my phone
http://www.androidrootz.com/2013/05/how-root-cwm-recovery-on-galaxy-s4-gt.html
Did you use another set of steps?
Thanks in advance!
0verfiend said:
Since it's a work in progress, I figure I will post as I go along.
I downloaded the 1.5gb TMB-M919UVUFNB4-20140314115123 file from the unroot link above. I then used Odin to install it... and was able to stop at step 9 - before doing the data wipe/factory restore. I can now get my phone to boot.
I am feeling so good - that I'll try to root again.
Click to expand...
Click to collapse
anoshwadia said:
I ran into the same issue as you on my TMobile Samsung Galaxy S4 and I wanted to say thanks for this post! It helped me get my phone restored back to the way it was and thankfully I didn't lose anything! Thanks so much!
Was wondering however.....how did you get it to root successfully after this?
I used this guide to try to root my phone
http://www.androidrootz.com/2013/05/how-root-cwm-recovery-on-galaxy-s4-gt.html
Did you use another set of steps?
Thanks in advance!
Click to expand...
Click to collapse
That procedure is so old and outdated, you should really pay attention to what you read and the sites you visit.. Everything you need is here on XDA.. Use cf-auto root to root the phone, do whatever you want afterwards..
Sent from my SGH-M919 using Tapatalk
Appreciate the response. I should have mentioned that I did start off at XDA. I used this thread
http://forum.xda-developers.com/showthread.php?t=2335109
....and it led me to use that link in my previous post. I figured since it was under the forums for my device and had been stickied, it would work fine. I didn't see anyone else on that thread report the issue I ran into, possibly because it worked prior to an update I had from Tmobile.
I will try your suggestions with cf-auto root. Thanks again for the help!
serio22 said:
That procedure is so old and outdated, you should really pay attention to what you read and the sites you visit.. Everything you need is here on XDA.. Use cf-auto root to root the phone, do whatever you want afterwards..
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Skipjacks said:
You tripped the Knox flag. That's all that happened. It won't affect your ability to use the phone. You didn't do anything wrong. it's normal when you root a Knox protected device.
Click to expand...
Click to collapse
Hi, is there a way to get rid of it?
I'm rooted and have TWRP 2.8 no problems, also I'm on Insanity V11 ROM, but those lines are too ugly :crying::crying::crying:
Railius said:
Hi, is there a way to get rid of it?
I'm rooted and have TWRP 2.8 no problems, also I'm on Insanity V11 ROM, but those lines are too ugly :crying::crying::crying:
Click to expand...
Click to collapse
Flash unmodified stock kernel
[Q&A] [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.
Q&A for [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.5/8.4 ]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.5/8.4 ]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can this method be used Straight out of the box?
Hey guys, just wanna make sure that this method can be used straight out of the box? only ever rooted LGs so just want to check that I'm doing the right thing here?
Thanks
As long as you have the Samsung usb drivers installed on your pc you're good.
ashyx said:
As long as you have the Samsung usb drivers installed on your pc you're good.
Click to expand...
Click to collapse
Great stuff Thanks, got a bit confused with the CFAutoRoot page saying I needed to unlock the bootloader first, then I stumbled on your Method.
Thanks
AgentCP said:
Great stuff Thanks, got a bit confused with the CFAutoRoot page saying I needed to unlock the bootloader first, then I stumbled on your Method.
Thanks
Click to expand...
Click to collapse
Only Verizon and AT&T models have locked bootloaders. If you don't have one of these you should be fine.
Why root wifi only device?
I have rooted a couple of devices. I get it's purpose of unlocking hotspot, modifying cpu clock, adblocking, etc. I have the Tab S 10.5 and I am trying to find the benefit to rooting this device. Looks simple enough. But What will I gain? I think I have already answered my question though, maybe. I am rooting my note 3 so I can use that for a hotspot for this. But it seems the only real benefit is adblocking? Am I missing something. It has been a while since I have done this so maybe I have...
Anyways, thanks for the input.
Bdozier said:
I have rooted a couple of devices. I get it's purpose of unlocking hotspot, modifying cpu clock, adblocking, etc. I have the Tab S 10.5 and I am trying to find the benefit to rooting this device. Looks simple enough. But What will I gain? I think I have already answered my question though, maybe. I am rooting my note 3 so I can use that for a hotspot for this. But it seems the only real benefit is adblocking? Am manufacturers I missing something. It has been a while since I have done this so maybe I have...
Anyways, thanks for the input.
Click to expand...
Click to collapse
The way to look at is that rooting gives YOU control over your device not the manufacturer. Think of it as like administration rights on a PC.
Would you like it if pc manufacturers told you what you could and couldn't install on your pc?
Rooting allows you to install custom recoveries so you can back up your device, fix problems, try new custom or stock software, install root only apps such as titanium backup. You can modify system files and add back functionality that the manufacturer has decided to remove or disable. Add new functionality, maybe something that is found on another device. Speed up your device by overclocking to make it run smoother.
Change how things look and install apps such as xposed which reveals a ton of hidden features allowing you to customize your device to your liking.
Once you realise what root can do you'll never want a another device that isn't.
Confused
Hi, I have downloaded the file for the T800. However, when I unzip it there are only two files :cache.img & recovery.img. Am I missing something? Please excuse my ignorance, newbie!!
Blythlad said:
Hi, I have downloaded the file for the T800. However, when I unzip it there are only two files :cache.img & recovery.img. Am I missing something? Please excuse my ignorance, newbie!!
Click to expand...
Click to collapse
Yep you certainly are a nooby as you made the rookie mistake of not actually reading the first post.
Go back to the original thread and read the bit under the smiley face.
ashyx said:
Yep you certainly are a nooby as you made the rookie mistake of not actually reading the first post.
Go back to the original thread and read the bit under the smiley face.
Click to expand...
Click to collapse
Sorry, I read that bit,downloaded odin as well, however, I recall reading something somewhere about needing a .tar file? Maybe some full instructions would be nice for us new to rooting a device. Thanks for the reply
Blythlad said:
Sorry, I read that bit,downloaded odin as well, however, I recall reading something somewhere about needing a .tar file? Maybe some full instructions would be nice for us new to rooting a device. Thanks for the reply
Click to expand...
Click to collapse
The tar file is the file you have downloaded.
Just leave it as it is and flash with Odin.
I shouldn't have to provide step by step instructions, this is what XDA search and Google is for. This info is everywhere.
Basically:
Install Samsung usb drivers.
Disable Samsung kies if installed.
Boot your device into download mode - Hold POWER + VOL DOWN + HOME.
Run ODIN , connect USB cable, look for 'added' message.
Load the tar file into the AP slot, click START.
Wait for flash to complete, device will reboot and root.
Enjoy your rooted device with custom recovery.
New build posted: http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
I tried on my t800 running latest BRI firmware and worked fine. Thanks a lot.
Cannot complete root on T-800 (Lollipop 5.0.2)
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
chanukya said:
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
Click to expand...
Click to collapse
Have you actually read the original thread? The answer is in that thread.
http://forum.xda-developers.com/showpost.php?p=60324046&postcount=33
Works now!
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
chanukya said:
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
Click to expand...
Click to collapse
That did it! Thanks bro, made my night!
Sent from my Galaxy S5
chanukya said:
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
Click to expand...
Click to collapse
Did you see the red android after rebooting?
Supersu should have already been installed before booting into twrp.
chanukya said:
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
Click to expand...
Click to collapse
I have an apology to make. Your troubles seemed to have been due to the SuperSu script not running because it had become corrupt. I realised something was wrong when you said you had to install SuperSu with TWRP.
All fixed now.
Sent from my SM-T805 using XDA Free mobile app
No clue... any help?
Sorry for the questions....
I have SM-T805 with 4.4.2 and build KOT49H.T805XXU1ANH1...
1 - Can i root without tripping knox? (i've done it on GS3 and GS4, no issues on knox, counter remains 0x0);
2 - The cf.auto root files are locked at specific builds? Or can i use the sm-t805 on chainfire page?;
3 - Can i update to lollipop or any other official firmware? And without tripping knox?
Thanks, in advance.
---------- Post added at 08:23 PM ---------- Previous post was at 08:18 PM ----------
Sorry for the questions....
I have SM-T805 with 4.4.2 and build KOT49H.T805XXU1ANH1...
1 - Can i root without tripping knox? (i've done it on GS3 and GS4, no issues on knox, counter remains 0x0);
2 - The cf.auto root files are locked at specific builds? Or can i use the sm-t805 on chainfire page?;
3 - Can i update to lollipop or any other official firmware? And without tripping knox?
Thanks, in advance.
I'm setting up a SPH-D710 for someone else and started looking around for information to root & install a custom recovery for this phone. On this phone I have the latest kies update for Android 4.1.2, OI23. I don't see any reference to this latest OI23 anywhere and I want to know the best method for rooting this device based on the current baseband version OI23. I would like to use TRWP as the custom recovery, but I'm not certain this is the best choice for this phone.
1. What is the best rooting method for the SPH-D710 4.1.2 OI23?
2. What is the best choice for the custom recovery for this device and Android version (4.1.2 OI23)?
I rooted just fine with Cydia Impactor... As far as the custom recovery.... I'm on stock and haven't tried any others with OI23 yet...
Any clue how to get rid of the SuperSU "su binary needs to be updated" notification after rooting OI23 with Cydia Impactor?
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
Try this.
paulshriner said:
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
Try this.
Click to expand...
Click to collapse
Had to use the "Full unroot - Cleanup for permanent unroot" option from the SuperSU left behind by Cydia first to remove the "bad" su binary, then the "Aragorn" option in Framaroot 1.9.3 did the job! I now appear to have a rooted OI23 without a weird warning message!
Thank you!
Kate6 said:
Had to use the "Full unroot - Cleanup for permanent unroot" option from the SuperSU left behind by Cydia first to remove the "bad" su binary, then the "Aragorn" option in Framaroot 1.9.3 did the job! I now appear to have a rooted OI23 without a weird warning message!
Thank you!
Click to expand...
Click to collapse
Where did you get the Framaroot file? I followed the thread and downloaded the file which turns out to be nothing but a 0 mb file. I've tried a google search and found fake sites that just lead me to advertising sites.
riffraff75 said:
Where did you get the Framaroot file? I followed the thread and downloaded the file which turns out to be nothing but a 0 mb file. I've tried a google search and found fake sites that just lead me to advertising sites.
Click to expand...
Click to collapse
Google is your friend.
Kate6, You must not have completely read my post. I did use google and have been to that site also any many others that came up. Don't believe the first thing you find. Google may be your friend but what you may find there may not be. In today's internet you have to be careful. That is a site that has you complete advertising offers that never let you download or ask for lots of personal info you should never give out. I know this is an old thread and have moved on and found other ways around this problem. Thanks anyways.
Terribly sorry. My Epic 4G Touch has actually recently finally died... Won't power up at all anymore. So at this point I'm at a bit of a disadvantage to be helpful here. Best of luck though!