Related
Hi,
Ok guys so a friend of mine wanted root on his S4 Gt-i9500, which I got for him using towelroot, no problems there and for a while he was happy with the root access and getting his phone debloated and a few other bits and bobs. However now he wants to try a couple of AOSP roms, and has asked me to help, which Im happy to do.
If it was my phone I'd take my chances and see what happens but with someone elses device I feel like I should be a bit more responsible, although I have made the dangers clear.
So what I want to do Is add a custom recovery, I've done a bit of googling and I can find out how to do it easy enough when rooted the traditional way, but my concern would be will I run into any problems with the Bootloader still being locked if I just flash a twrp .img with Flashify?
Maybe I should do a full unroot, and root via CF-Root Method and then find a TWRP .tar and flash with Odin.
Not used to having the Bootloader Locked issues as I use a HTC so is an easy unlock.
Any advice people can give would be helpful, hopefully I can just use Flashify and keep it as simple as possible
Ok, just to make things crystal clear, there is a big difference between a locked (i.e. encrypted) bootloader as found on AT&T and Verizon phones, and a SEAndroid Enforcing (aka Knox) bootloader. With the former you cannot customize the firmware that came with the phone, but developers have found workarounds. With Knox, you're still able to root and install custom ROMs if desired. You simply lose the ability to use Knox, which most of the userbase doesn't care about. In HTC speak, all Galaxy S4 bootloaders except the AT&T and Verizon models are equivalent to S-Off.
For installing TWRP, downloading an image and installing through Odin will work. TWRP Manager from the Play Store can also do the job, and do it without you being connected to the PC. Once you have TWRP installed, installing a custom ROM is quick, easy, and painless. Custom ROMs are usually pre-rooted, i.e. including SuperSU or Clockworkmod Superuser. This means you won't have to root again.
Samsung I9505 Galaxy S4 - OS v4.4.2 | Downgrading & SD-Card Restrictions & 4.4 vs 4.3
Hey guys,
Just got this phone in immaculate condition from a friend. As it has been updated from OS 4.2 to 4.4, I now have restricted SD-Card access.
Before I start using the device, is there:
- Any way to overcome the SD-Card restrictions?
- Any way to down-grade (reliably) to 4.3.x?
I will root the device once everything is up and running (or before, should you recommend it).
Thank you very much guys!
Flip.
Root the device, download SD Card Fix from the Play Store, then run it. The app will modify platform.xml and enable full access.
Thanks mate. Appreciate the response.
I'll use KingoRoot again to root it. Then install SuperSU and BusyBox.
So is downgrading not an option? or just too risky?
OS 5 doesn't have full App support yet, so that's not really an option... I'll wait for OS 5.1
You don't even need Kingroot. Just flash CF-Autoroot through Odin to root and install SuperSU.
Downgrading may be possible. However, it's more likely the radios (cellular and WiFi) will not work. If you want Android 5.x you probably should look into the custom ROMs in I9505 Original Android Development rather than staying on Touchwiz.
Samsung Knox + SuperUser on SGS4 i9505 OS v4.4.2 Root
Samsung KNOX is preventing SuperSU and KingoUser (either) from installing. Neither of them appear to be "sticking".
When I open Knox, it says it is initialising, then closes. I cannot access any of the settings to disable and remove (and backup settings) Knox and its components.???
I've googled and there are just topics of people with the same problem and no answers to the problems!
The only answers say to perform actions that require root \ elevated actions (when you cannot elevate access without a SuperUser app installed!!!)...
Here are some screen shots. I appreciate any suggestions from you guys!
Thank you.
p.s. Hmm some Root functions are working. i.e. those that don't require SU!
Screen Shots: http://imgur.com/a/Qbxeb
Flash SuperSU through recovery. The first time you run SuperSU after flashing, you should get the option to disable Knox. Let SuperSU disable Knox, then reboot. On my device, trying to disable Knox the first time caused SuperSU to hang, so I hard rebooted the device and went back into SuperSU. I got the prompt a second time and this time I successfully disabled Knox.
When I hold down Vol Down I get this info and no options:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATE: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
Click to expand...
Click to collapse
Message: Downloading..... Do not turn off target !!
Wtf? That doesn't even make sense!! Target? lol
This is word for word, character for character, and exact case.
So how do I get in to the good ol' menu with half a dozen options as my two HTC's and Samsung have??
Thank you!
Since I haven't followed this thread for a little while, let's make sure we're on the same page.
1. You flashed CF-Autoroot using Odin to root the S4.
2. SuperSU successfully removed Knox from the equation.
2. You then installed a custom recovery (TWRP recommended) using Odin.
3. You now want to flash a custom ROM through the recovery?
If the answer to 3 is "yes", hold down power for about ten seconds to get out of download mode. Then press volume up, home, and power to boot into the recovery. If the answer is anything else, then start over with the first item and go down from there. Some confusion may be generated thanks to my previous post, where it mentions installing SuperSU through recovery. Installing SuperSU through recovery is only possible if a custom recovery has been installed previously. For that, I apologize.
Is there a root procedure for the galaxy s4 that's on the newest lollipop update ? I was able to root with kingroot but read its not safe to use kingroot and try install a custom rom ?
dpmeeks said:
Is there a root procedure for the galaxy s4 that's on the newest lollipop update ? I was able to root with kingroot but read its not safe to use kingroot and try install a custom rom ?
Click to expand...
Click to collapse
CF-autoroot or flash TWRP then in TWRP flash SuperSU
Kingroot and SuperSU_me method works also... Watch the entire process in 2 parts... https://www.youtube.com/watch?v=IWnYFDQ1Vio
K94U said:
Kingroot and SuperSU_me method works also... Watch the entire process in 2 parts... https://www.youtube.com/watch?v=IWnYFDQ1Vio
Click to expand...
Click to collapse
Have you lost root since? I've read a lot about people loosing root after a few hours to a couple of days. Any other issues, like random crashes / freezes / reboots?
Ezintn said:
Have you lost root since? I've read a lot about people loosing root after a few hours to a couple of days. Any other issues, like random crashes / freezes / reboots?
Click to expand...
Click to collapse
That's why flashing TWRP and SuperSU is the safest/easiest way to root, it's about as straightforward as it gets
mattzeller said:
That's why flashing TWRP and SuperSU is the safest/easiest way to root, it's about as straightforward as it gets
Click to expand...
Click to collapse
Wasn't aware I could flash a custom recovery on a stock unrooted phone. I don't use the s4, that's why both of the ones I own aren't rooted already, my personal phones are often rooted before I even get home from the store! I need root and su without tripping knox or making any significant changes to the current set-up on either phone. I would prefer the recovery was stock on at least one of 'em. So how should I go about this? One is a tri band and the other isn't. The dual band one needs to be as stealth as possible. Losing root really won't matter as long as the system permissions remain as is prior to losing root.
Ezintn said:
Wasn't aware I could flash a custom recovery on a stock unrooted phone. I don't use the s4, that's why both of the ones I own aren't rooted already, my personal phones are often rooted before I even get home from the store! I need root and su without tripping knox or making any significant changes to the current set-up on either phone. I would prefer the recovery was stock on at least one of 'em. So how should I go about this? One is a tri band and the other isn't. The dual band one needs to be as stealth as possible. Losing root really won't matter as long as the system permissions remain as is prior to losing root.
Click to expand...
Click to collapse
Flashing a custom recovery is going to trip knox. Why do you care about knox? Triband or not flashing TWRP and SuperSU is the same. If you lose root and have things that require root to operate, you will lose the function of those things, unless it's a one off type of thing
mattzeller said:
Flashing a custom recovery is going to trip knox. Why do you care about knox? Triband or not flashing TWRP and SuperSU is the same. If you lose root and have things that require root to operate, you will lose the function of those things, unless it's a one off type of thing[/QU
It's imperative that root is stealth. Just need to give one app already running su permissions. On one device knox is monitored, that's why I care. I wouldn't care on my s5, but I never tripped it anyway - rooted with modified stock recovery, flashed MOAR, flashed TWRP. Been using MAOR and TWRP since each was first released. Been rooted on my personal devices since 3 days after the Hero was released. I've just never rooted the s4 or "stealth rooted" any device. That's why Kingroot / SSM looks promising. Any help would be appreciated.
Click to expand...
Click to collapse
I want to root my phone, and I haven't been doing that kind of stuff since S3 so I'm a bit lost.
I've read the thread about root by Chainfire. From what I understand, this can be used for a phone with Android 6.01, right? On the other hand, I've read about a systemless root. Can this be done with my phone model and this Android version?
My main concern is the warranty. I know the first solution will trip the knox. What about the latter? Would this be better in my situation?
(And a minor question: my phone has found a software update. Should I do it before or after rooting my phone, or does it matter at all?)
for me and it can be different for other users, i have a preference for system root.
if you just want a stable root on your phone, and don't care about passing google security checks (safetynet) you should choose chainfires supersu. just download the latest zip (assuming you already have a custom recovery) and flash it. supersu will "decide" which rooting method (system/systemless) fits to your phone.
The more advanced method is magisk-root which gives you no option for system-root. the whole magisk concept is based on systemless changes to the system partition. it gives you the opportunity to pass safetynet and to add systemless modules. the downside is, that the usability (due to it's complexity) can sometimes be a bit tricky (trial and error )
hope this helped for your decision..
BTW: afaik is knox triggered with both methods
drei.liter.milch said:
if you just want a stable root on your phone, and don't care about passing google security checks (safetynet) you should choose chainfires supersu. just download the latest zip (assuming you already have a custom recovery) and flash it. supersu will "decide" which rooting method (system/systemless) fits to your phone.
The more advanced method is magisk-root which gives you no option for system-root. the whole magisk concept is based on systemless changes to the system partition. it gives you the opportunity to pass safetynet and to add systemless modules. the downside is, that the usability (due to it's complexity) can sometimes be a bit tricky (trial and error )
hope this helped for your decision..
BTW: afaik is knox triggered with both methods
Click to expand...
Click to collapse
To add something: if supersu installs in systemless mode you can bypass it.
Flash the supersu zip
Reboot
Go to supersu and select full root wipe
Click no when asked to restore boot image
Your phone will automatically reboot don't let it go to system, go to recovery
With twrp go to terminal and enter this command without quotes "echo SYSTEMLESS=false>>/data/.supersu
Reinstall supersu zip
Reboot
You yave system root :good:
Sent from my Samsung Galaxy S5 Neo using XDA Labs
Thanks for your replies! I do not care about safetynet. I do care about warranty but from what I see, there is no way around this.
Would you update phone's software first?
Joanka said:
Thanks for your replies! I do not care about safetynet. I do care about warranty but from what I see, there is no way around this.
Would you update phone's software first?
Click to expand...
Click to collapse
Yeah update your system first and if you need warranty just full wipe root and select yes for biit image restore from supersu let us know if it works for you and don't hesitate to ask if you need anything
Sent from my Samsung Galaxy S5 Neo using XDA Labs
Thanks for your help! I'm updating the sofware right now and I will proceed with the root.
"just full wipe root and select yes for biit image restore from supersu" -I think I'm not sure what it means. Would you explain it a little bit more?
Joanka said:
Thanks for your help! I'm updating the sofware right now and I will proceed with the root.
"just full wipe root and select yes for biit image restore from supersu" -I think I'm not sure what it means. Would you explain it a little bit more?
Click to expand...
Click to collapse
Yes, click full unroot and click yes for boot image restore but no for recovery restore
Sent from my Samsung Galaxy S5 Neo using XDA Labs
I have mine (S5 Neo G903W) rooted and as far as I can tell if you want your warranty you can unroot it anytime
The phone provider however doesn't state anything about rooting or whatnot and I am not a type of person who does stupid stuff that needs a warranty anyway lol
For warranty they can check knox status, if is tripped usually is void
Hi guys,
S7E Exynos International 935F here.
Is it possible to temp flash TWRP just to install Magisk?
Is it possible to flash anything useful using stock recovery? (Which seems to happen after booting with vol up+ home + power and waiting for abit)
Will the modded/patched boot image trip knox?
Main objective is to do a titanium backup, wipe the phone, reinstall minimum stuff + app data for that minimum stuff.
Will a ROM like Black Diamond be considered custom and thus trip knox?
Thanks!
TWRP = trip knox.
ivoryroot ( Xperia) for Samsung?
I think not, knox is not drm keys
Airbag888 said:
Hi guys,
S7E Exynos International 935F here.
Is it possible to temp flash TWRP just to install Magisk?
Is it possible to flash anything useful using stock recovery? (Which seems to happen after booting with vol up+ home + power and waiting for abit)
Will the modded/patched boot image trip knox?
Main objective is to do a titanium backup, wipe the phone, reinstall minimum stuff + app data for that minimum stuff.
Will a ROM like Black Diamond be considered custom and thus trip knox?
Thanks!
Click to expand...
Click to collapse
Any custom binary (whether twrp or samsung based custom roms or aosp based custom roms) will trigger knowx bit..
And no you can't install anything useful in stock recovery. Twrp isn't that heavy lol. You can keep it because it is 1000% more useful then stock recovery : )
And no, you cannot even flash magisk without twrp ; )
Want twrp-less root ? And a systemless too like magisk ? Try cf auto root- create your own root file (you can choose system less option there! ) and flash it using odin, other options like magisk or super su require twrp..
Sent from my S7 Edge using XDA Labs
shah22 said:
Any custom binary (whether twrp or samsung based custom roms or aosp based custom roms) will trigger knowx bit..
And no you can't install anything useful in stock recovery. Twrp isn't that heavy lol. You can keep it because it is 1000% more useful then stock recovery : )
And no, you cannot even flash magisk without twrp ; )
Want twrp-less root ? And a systemless too like magisk ? Try cf auto root- create your own root file (you can choose system less option there! ) and flash it using odin, other options like magisk or super su require twrp..
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
@shah22 Thanks!
Sorry if I'm being thick.
You mentioned custom binary - do you mean firmware or does that include recovery?
I was under the impression that installing systemless root like magisk (or as you mention cf auto root) would not trigger knox and also be hidden from detection from google and/or banking type apps
My main reason for root (temp twrp) would be to either be able to do a nandroid of my system or titanium before having to wipe everything. From what you're telling me that's not going to happen.
I went through a bunch of root-less apps like smart switch for example that never saved application data, only the apk
Would you say there's a custom ROM that offers several features similar to stock but performs better with better battery life and is mature enough to be a daily driver? I saw Black Diamond but I'm cautious and I realise knox will blow but right now outside of s-health I don't think I have any 'knox' data
Anyway thanks for your time
Airbag888 said:
@shah22 Thanks!
Sorry if I'm being thick.
You mentioned custom binary - do you mean firmware or does that include recovery?
I was under the impression that installing systemless root like magisk (or as you mention cf auto root) would not trigger knox and also be hidden from detection from google and/or banking type apps
My main reason for root (temp twrp) would be to either be able to do a nandroid of my system or titanium before having to wipe everything. From what you're telling me that's not going to happen.
I went through a bunch of root-less apps like smart switch for example that never saved application data, only the apk
Would you say there's a custom ROM that offers several features similar to stock but performs better with better battery life and is mature enough to be a daily driver? I saw Black Diamond but I'm cautious and I realise knox will blow but right now outside of s-health I don't think I have any 'knox' data
Anyway thanks for your time
Click to expand...
Click to collapse
Flashing any firmware or recovery NOT signed by samsung triggers knox bit irreversibly, so flashing anything other then samsung stock WILL result in knox being triggered.. so now you know bruh xD
Any root systemless or not, any rom which is modified will trigger knox. Till now there is NO root method which doesn't triggers knox..
If you want fast stable rom, you can try black diamond rom yeah.. but i will recommend flashing latest stock oreo rom for your region and then flashing twrp+magisk plus debloat it and add any other mods you want. This way it may get less bugs then custom rom, and maybe more stable and faster, upto your preference..
And yeah, triggering knox causes samsung pay, secure folder / encryption to not work properly.. some other samsung related services and some banking apps too..
Sent from my S7 Edge using XDA Labs
shah22 said:
Flashing any firmware or recovery NOT signed by samsung triggers knox bit irreversibly, so flashing anything other then samsung stock WILL result in knox being triggered.. so now you know bruh xD
Any root systemless or not, any rom which is modified will trigger knox. Till now there is NO root method which doesn't triggers knox..
If you want fast stable rom, you can try black diamond rom yeah.. but i will recommend flashing latest stock oreo rom for your region and then flashing twrp+magisk plus debloat it and add any other mods you want. This way it may get less bugs then custom rom, and maybe more stable and faster, upto your preference..
And yeah, triggering knox causes samsung pay, secure folder / encryption to not work properly.. some other samsung related services and some banking apps too..
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Haha that does clear things up thanks!
I used to try/flash custom ROMs back in the day (think nexus 1, S2, S3) then got too busy (2 kids popped up plus more work responsibilities) to delve into the community to keep up on what can and cannot be done.
My biggest gripe right now is there's no 'stock' method to nandroid where you actually save application data =\
Anyway I also naively thought you could push a custom recovery not to be flashed but just to run in fastboot so you could perform the nandroid / other stuff.. guess not
I do appreciate your advice on the way forward. I wonder if I can easily copy my s-health data to g-fit for example and be done with it :shrug: