Related
Just now installed stock Takju 4.3 image. Unfortunately, root is not working. I flashed SuperSU.zip, also did the update of the app via play store, but when I open the app I get the message:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Any solution?
[Solved]
Chainfire's SU zip for GS4 4.3 works fine for Nexus also. Check his G+ post here:
https://plus.google.com/+Chainfire/posts/9rcWNJbVZkL
Sounava said:
Just now installed stock Takju 4.3 image. Unfortunately, root is not working. I flashed SuperSU.zip, also did the update of the app via play store, but when I open the app I get the message:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Any solution?
Click to expand...
Click to collapse
same thing happened to me with yakju clean install, maybe it has something to do with this? http://www.xda-developers.com/android/android-4-3-rooted-courtesy-of-chainfire/
1) You must flash the Android 4.3 modified SuperSU file: http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip
2) If you're flashing via CWM Recovery, you must hit NO when it asks you to disable the recovery restore. If you hit yes, SuperSU will NOT work.
GldRush98 said:
1) You must flash the Android 4.3 modified SuperSU file: http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip
2) If you're flashing via CWM Recovery, you must hit NO when it asks you to disable the recovery restore. If you hit yes, SuperSU will NOT work.
Click to expand...
Click to collapse
Thanks it worked!
I also found that chainfire has made a post regarding this also
https://plus.google.com/+Chainfire/posts/9rcWNJbVZkL
|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here.
If you have not updated to 4.4, go here.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Edit:
Here is some potentially useful info for root method #1 from ansonantonym.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery then flash SuperSu and the Knox Remover
4) Reboot
5) Download SuperSu from the Play Store
6) Open SuperSu and update the binary when prompted
7) Reboot
8) Enjoy rooted 4.3/4/4
Downloads:
Odin
TWRP (Odin flashable tar)
SuperSu (v1.65)
SuperSu (v2.01)
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
Please be sure to thank Chainfire, Dees_Troy, and Kaito95.
*****
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jeremyds45 said:
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
upndwn4par said:
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
Click to expand...
Click to collapse
Ah it is so nice to have root again... Thank you so much for putting up with a noob.
Crazy events of a noob that lead me to root
Installed ota 4.3
Tried to root and install superuser by odin and then custom recovery to flash
Root didn't happen because of knox
Could only get to CWM custom recovery if it was right after odin and battery pull?...
Flashed the script to remove knox, which did remove knox
Tried the same root method as above and no root access
Tried supersu and then updating in play with no success
Changed security update settings etc nothing
Reset delvik, cache, permissions, etc nothing
Different root method and files for odin, and custom recovery stuck
Used files from this thread, went into custom recovery and flashed supersu
Installed supersu from play store...
Updated the binary using custom recovery
Rebooted...
ROOT access, all root applications work fine and root sticks even after reboots
I never messed with cf auto root method
THANK you guys for your time effort and sharing, helps noobs out like me a lot!
Sweet! I've missed root since I upgraded using the OTA file you provided. Looking forward to much other great things coming from you
Thank You
upndwn4par said:
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here. Make sure you understand the risks and uncertainties described in the OP.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery and flash SuperSu.
4) Flash the Knox Remover
5) Reboot
6) Download SuperSu from the Play Store
7) Update the binary when prompted
8) Reboot
8) Enjoy 4.3
Downloads:
Odin
TWRP (Odin flashable tar)
UpdateSuperSu
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
*****
Click to expand...
Click to collapse
Method two absolutely worked. Thank you so much. I was scared to flash TWRP but knowing you did it gave me the courage. Have full root and happy
questions about this root
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
THANKS!!!! your a lifesaver didn't know how much longer i could take without root
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
bkong said:
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
Click to expand...
Click to collapse
use the TWRP method worked perfected for me
Thanks
PimpMyPC said:
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
Click to expand...
Click to collapse
The second method worked great. I believe (and the way that worked for me) that you use your custom recovery to flash the knox script, not using Odin and pda. I don't think it removed anything other than knox, there is a different script for removing knox and att bloatware. Should still be able to factory reset... But can't guarantee that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Root & Knox
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
tailgunner9 said:
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
Click to expand...
Click to collapse
Those settings are just for granting device administrator privileges. If unchecked, Knox is still doing it's thing, just not at an administrative level.
Yes, it is safe to try and root.
I have Android Device Manager as admin. That way if I ever lose my device I can just log in to the Play Store and locate and / or wipe the device.
To do this just flash the recovery.img file using odin and clicking the pda button correct?
Is there a way to freeze Knox instead of deleting it in the event I would want to go back to full stock?
After you are rooted, use an app like Titanium Backup(pro) or My Backup pro. Both will freeze it.
Root
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
tailgunner9 said:
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
Click to expand...
Click to collapse
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
indymx said:
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
Click to expand...
Click to collapse
Thanks indymx, may get the nerve up to try it on my AT&T S3. Let me know if you run into any problems. Guess Rom Manager and other programs that require Root are working Ok and you have rebooted few times to be sure it keeps Root?? Have Happy Thanksgiving.
I have a T-Mobile Galaxy S4 and I tried rooting it using the CF-Auto-Root, but when I open SuperSU, it says "there is SU binary installed, and SuperSU cannot install it." I decided I want to root it all the way but I can't figure this out. How do I root this phone?? Do I have to use the CyanogenMod?? Please help!!
chosenginger said:
I have a T-Mobile Galaxy S4 and I tried rooting it using the CF-Auto-Root, but when I open SuperSU, it says "there is SU binary installed, and SuperSU cannot install it." I decided I want to root it all the way but I can't figure this out. How do I root this phone?? Do I have to use the CyanogenMod?? Please help!!
Click to expand...
Click to collapse
Ok, So my question would be did you use Odin to install CF-Auto-Root? Most I've seen use it and have no problem. Odin installs it then the phone reboots and that's when a special recovery is installed and then loaded and the root process is done. After that stock recovery is again installed. Not positive but I heard there may be other methods named similiar to this that will root phones that have 4.3 and lower.
Make sure you have the version mentioned here http://forum.xda-developers.com/showthread.php?t=2294005
Also. if you think for some reason that your phone maybe rooted but SuperSU isn't working right you could always go to the Play store and download Chainfire's SuperSU and then install it. If your phone was truly rooted this should fix SuperSU
Corwinder said:
Ok, So my question would be did you use Odin to install CF-Auto-Root? Most I've seen use it and have no problem. Odin installs it then the phone reboots and that's when a special recovery is installed and then loaded and the root process is done. After that stock recovery is again installed. Not positive but I heard there may be other methods named similiar to this that will root phones that have 4.3 and lower.
Make sure you have the version mentioned here http://forum.xda-developers.com/showthread.php?t=2294005
Also. if you think for some reason that your phone maybe rooted but SuperSU isn't working right you could always go to the Play store and download Chainfire's SuperSU and then install it. If your phone was truly rooted this should fix SuperSU
Click to expand...
Click to collapse
I have the SGH-M919 model and yes I used ODIN, but whenever I open SuperSU, it comes up that it has no binary. I already checked and I have the chainfire version.
Sent from my SGH-M919 using xda app-developers app
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Alte.78 said:
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
If you want you can PM me or join Freenode IRC and PM droidlambda. I've already started making CyanogenMod for the device, although I haven't come that far yet (even though the TWRP recovery you installed was ported by me). I could give you some advice (of my experiences with this phone and porting) and my basic config (which builds recovery successfully) if you want.
Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?
Alte.78 said:
Getting Root
For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu.
Click to expand...
Click to collapse
If we install TWRP, can't we just flash SuperSU zip from recovery to avoid the KingRoot removal hassle?
Alte.78 said:
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable.
Click to expand...
Click to collapse
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?
Thanks.
Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Great!
nick_white said:
Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?
Click to expand...
Click to collapse
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.
Karboush said:
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Click to expand...
Click to collapse
Thats absolutely cool! I want to have custom recovery anyway, but your discovery will surely help a lot of people. :good:
nick_white said:
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?.
Click to expand...
Click to collapse
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Could you point me as to where did you find the firmware for the phone. I'm tempted to try rooting it. Is xposed necessary for the root to take full effect or no ? Cause it sounds a bit tricky and risky.
CostasV23 said:
Could you point me as to where did you find the firmware for the phone.
Click to expand...
Click to collapse
Try this link: http://www.sammobile.com/firmwares/database/GT-I9195I/
soo
Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Click to expand...
Click to collapse
So my phone has the AOD1 firmware can i root it like AOD2? Im in greece
Alte.78 said:
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?
Click to expand...
Click to collapse
Can you tell me if these will work for sure I have the aob1 firmware
Ok, so I have mine updated to I9195IXXU1AOG1. How do I get SuperSU on it without changing Knox to 0x1?
Which version of Xposed is everyone using? On the S4 Mini Plus?
xposed?
Is xposed necessary for the rooting process? or can i just skip it to avoid all the fuzz?
Alte.78 said:
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.
Click to expand...
Click to collapse
I upgraded my firmware to:
PDA: I9195IXXU1APA1
CSC: I9195IPHN1APA1
which is also (one of) the latest version, and has the Stagefright vulnerabilities fixed.
Then rooted with latest KingRoot (4.80) + Super Sume Pro.
Then installed Xposed 2.6.1 (stable) and installed "classical" (write to /system). It worked, no bootloops. Maybe you tried a different Xposed version?
Hi! anyone have a baseband I9195LUBUCNJ2?
Synomenon said:
Which version of Xposed is everyone using? On the S4 Mini Plus?
Click to expand...
Click to collapse
Im using the app_process 58 and
xposedBridge.jar 54 which i think is the latest stable edition as of 13/07/2016
Xposed installer version 2.61 with auto flash in recovery method no problems 5 months that i have it
Full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i)
For more than a year, after I upgraded my firmware to:
PDA: I9195IXXU1APF1
CSC: I9195IYUX1APG1
which was the latest version from https://www.sammobile.com/firmwares/database/GT-I9195I/
I am using a debloat version of Galaxy S4 mini Plus (serranoveltexx). Inspired by @btnetro I made a script and tested a full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i). All this time my device has worked very well and even now I am very pleased with him. For those who want to keep stock OS like me, I decided to share with you this flashable zip.
First flash via Odin, a custom recovery on your device( installation instructions here: https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207 ), restart your device and copy attached files in the root of your ext. SD card. Reboot your device in recovery mode and flash “Full_debloat_i9195i.zip”. For those who want to keep weather widget flash this file “weather2014_A3.zip” too (first debloat). Wipe /cache and reboot your device.
OK, i've a weird issue.
I tried all the available recoveries (Philz touch 6.59.0, twrp 2.8.4.0 & 2.8.7.1 etc, and all flashed with odin method) but none of them recognize my external SD.
I tried other sd cards as well, known to be good as they're used in other phones, but end up with th same.
Funny part is that inside os (stock KK 4.4.4) i can see all the files in SD card...
Any suggestion?
I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks
There is no update. 5.0.2 is the latest.
ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?
MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:
If you want to go back to stock just flash the latest firmware with odin.