Related
Ok, i just got my samsung galaxy s5 a week ago. And yesterday i checked for an update and there was one and i downloaded it and installed it. The update said it improved software stability on the s5. I have the t-mobile version and after i intstalled the update i found out that geohot released a root for the device :| . what im afraid of is that this update fixed the exploit the root is using or, this update will detect whether i root the device or now and knox will be tripped. does anyone else know anything about this update that was sent out by t-mobile yesterday?
KERNAL version
3.4.0-1616466
Fri May 23 20:25:39 KST 2014
Build Number
KOT49H.G900TUVU1ANE6
SE for Android Status
Enforcing
SEPF_SM-G900T_4.4.2_0016
Fri May 23 20:25:18 2014
Security software version
MDF v1.0 release 3
VPN v1.4 Release 1
nightlyshade said:
Ok, i just got my samsung galaxy s5 a week ago. And yesterday i checked for an update and there was one and i downloaded it and installed it. The update said it improved software stability on the s5. I have the t-mobile version and after i intstalled the update i found out that geohot released a root for the device :| . what im afraid of is that this update fixed the exploit the root is using or, this update will detect whether i root the device or now and knox will be tripped. does anyone else know anything about this update that was sent out by t-mobile yesterday?
KERNAL version
3.4.0-1616466
Fri May 23 20:25:39 KST 2014
Build Number
KOT49H.G900TUVU1ANE6
SE for Android Status
Enforcing
SEPF_SM-G900T_4.4.2_0016
Fri May 23 20:25:18 2014
Security software version
MDF v1.0 release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Try Towelroot, it is confirmed working on the S5 and it doesn`t trip KNOX. Link http://towelroot.com/ and click the Lambda from the phones browser and follow instructions.
+1 on towelroot. Works fast and nothing negative can happen if you mess up. I'm talking about the rooting process that is. Hit one button and done. If it's not compatible it just won't root
Sent to you from my slimmed down S5
your KNOX will trigger only if you install CUSTOM RECOVERY or CUSTOM KERNEL. and the safest method that I KNOW to root without triggering KNOX is TOWEL ROOT as described by our 2 good member in your thread.
rooting makes private mode useless
Towel Root is your best bet, like Chaintanyapatel8880 said the only time Knox will trigger is flashing a custom recovery or rom. I think the only rom you can flash that won't trigger it is the alliance rom in the tmobile section since there is an option to flash it through Odin.
Sent from my SM-G900T using XDA Premium 4 mobile app
nightlyshade said:
Ok, i just got my samsung galaxy s5 a week ago. And yesterday i checked for an update and there was one and i downloaded it and installed it. The update said it improved software stability on the s5. I have the t-mobile version and after i intstalled the update i found out that geohot released a root for the device :| . what im afraid of is that this update fixed the exploit the root is using or, this update will detect whether i root the device or now and knox will be tripped. does anyone else know anything about this update that was sent out by t-mobile yesterday?
KERNAL version
3.4.0-1616466
Fri May 23 20:25:39 KST 2014
Build Number
KOT49H.G900TUVU1ANE6
SE for Android Status
Enforcing
SEPF_SM-G900T_4.4.2_0016
Fri May 23 20:25:18 2014
Security software version
MDF v1.0 release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Reiterating from my personal experience. T-Mo G900t KOT49H.G900TUVU1ANE6
I recently sent back a knox tripped back for battery issues, the battery life was horrid. Freaking Android system. (No problemas)
After trying towelroot i'm rooted with stock rom, Make sure to do these things when you do root, Disable ServiceIQ (Find in search) and start looking into making modifications via system tuner but don't do the one click partition stuff that improves stuff for you, that will earn you a factory reset and a whole lot of force closes. =)
Since i've rooted i've had no issues with installing Xposed, BusyBox and all the other goodies that rooting comes with but remember, if you do install a new rom which usually requires a new recovery you WILL trip knox :cyclops: (Correct me if i'm wrong)
I can't tell you how many times i've factory reset and rentered in my credentials but i'm loving titanium backup now.
Stay stock and modify, but don't touch bootloader or recovery
I'd love to get back to Alliance rom or Omega, but I want the radio updates until stuff is ironed out or knox is beaten. I made the mistake of rooting the first day and was stuck with the ANCH baseband and couldn't do anything about it and when you trip your knox you say byebye to radio and modem updates until the higher ups figure things out.
I'm not new to flashing ROMs, but I am new to flashing them for the S5. What is it with this KNOX thing that everyone keeps talking about? Why is it so dangerous? Is that the reason modding for the S5 seems to be at a standstill?
Luuthian said:
I'm not new to flashing ROMs, but I am new to flashing them for the S5. What is it with this KNOX thing that everyone keeps talking about? Why is it so dangerous? Is that the reason modding for the S5 seems to be at a standstill?
Click to expand...
Click to collapse
KNOX is advanced security. Before if the binary counter goes custom we can use triangle away and reset the counter which will set the phone for the warranty but in case of KNOX, there is no way we can reset once it becomes 0x1. and the warranty is gone... there is no way as of yet to reset it... it can become 0x1 if you flash custom recovery and or custom kernel but if you use TOWEL ROOT by GEOHOT, knox will not change. I have tried personally...
Ah, okay. So you can actually easily flash the S5 (well, as much as any other locked phone) but people don't want to lose their warranty...
Doesn't seem like the worst trade-off to me though. If a Google Play edition of the device hits, I would gladly flash my device to a stock Android 5.0 ROM on the S5.
Luuthian said:
Ah, okay. So you can actually easily flash the S5 (well, as much as any other locked phone) but people don't want to lose their warranty...
Doesn't seem like the worst trade-off to me though. If a Google Play edition of the device hits, I would gladly flash my device to a stock Android 5.0 ROM on the S5.
Click to expand...
Click to collapse
Actually It is a golden deal even if we loose warranty. rooting and custom recovery unlocks tons of features. It's like heaven for smartphone...
Luuthian said:
Is that the reason modding for the S5 seems to be at a standstill?
Click to expand...
Click to collapse
Urghhh if I read another statement like that I'm gonna scream! Modding is NOT at a standstill!! Why do so many people use these sweeping statements just because they can't have a fully working non Samsung based Rom. Modding is very much on the move for Samsung based roms. If you are waiting for fully working non Samsung you may as well have bought a N5 as by not using Samsung software you lose a hell of a lot of what makes an s5 and s5! Buy a nexus... Save some money and be happy
Sent from my SM-G900F using Tapatalk
towerlroot worked here without messing up knox.
this is my first smartphone I was worried too -- ecspecially because I have insurance on the phone lol
I have not put in custom rom there yet because I need to get a SD card and would rather move my apps there before doing so, but no issues and the thing could not be easier to do with his program.
That's great...
Sent from my SM-G900F using XDA Premium 4 mobile app
The question is, can a rooted (but older) firmware be as secure as a non-rooted (up-to-date) firmware?
Sure you install apps or modify certain files/settings to improve security, but what if there's a serious security flaw in the kernel?
Installing a newer kernel would render towelroot useless (the reason i don't mention CF-Auto-Root is because of KNOX, but you can't always have the best of both worlds)
Goldie said:
Urghhh if I read another statement like that I'm gonna scream! Modding is NOT at a standstill!! Why do so many people use these sweeping statements just because they can't have a fully working non Samsung based Rom. Modding is very much on the move for Samsung based roms. If you are waiting for fully working non Samsung you may as well have bought a N5 as by not using Samsung software you lose a hell of a lot of what makes an s5 and s5! Buy a nexus... Save some money and be happy
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
I didn't mean it like that. I assume people simply aren't working on it much because the bootloader hasn't been unlocked. POintless to build ROMs that can't be used yet. That's all. I'm actually quite happy with my S5, and would be even if we never saw a big ROM community for it. It's a good phone, and Touch Wiz is far less intrusive than it used to be. Even knowing an F device is in the works I'm still happy with my purchase.
Checked old threads, and even made a thread a couple months ago about this question, but it goes a bit further.
I've finally rooted using this method: http://forum.xda-developers.com/galaxy-s4-tmobile/general/root-nb4-knox-0x0-t2802185
I didn't trip knox, that's great right?! Well, I went further, installed xposed, then gravity box and started playing around with my newly rooted device.
I then installed supersu (I haven't really needed it but I wanted to test something out from another thread, here: http://forums.androidcentral.com/samsung-safe-knox/366118-solution-how-permanently-remove-knox.html)
Well I've removed Knox!
Not quite: because knox is located in the bootloader, it's a little more complicated to remove. My question (finally) is that even though I've disabled knox as a pesky security feature, if I were to finally enable a custom recovery, or flash to a different rom (I wanna go aosp, and go to lolipop) would I have issues with knox again, and trip the counter? I still want to upgrade my phone using JUMP but I don't want to have problems with T-Mobile.
Thanks guys!
devilsmarch said:
Checked old threads, and even made a thread a couple months ago about this question, but it goes a bit further.
I've finally rooted using this method: http://forum.xda-developers.com/galaxy-s4-tmobile/general/root-nb4-knox-0x0-t2802185
I didn't trip knox, that's great right?! Well, I went further, installed xposed, then gravity box and started playing around with my newly rooted device.
I then installed supersu (I haven't really needed it but I wanted to test something out from another thread, here: http://forums.androidcentral.com/samsung-safe-knox/366118-solution-how-permanently-remove-knox.html)
Well I've removed Knox!
Not quite: because knox is located in the bootloader, it's a little more complicated to remove. My question (finally) is that even though I've disabled knox as a pesky security feature, if I were to finally enable a custom recovery, or flash to a different rom (I wanna go aosp, and go to lolipop) would I have issues with knox again, and trip the counter? I still want to upgrade my phone using JUMP but I don't want to have problems with T-Mobile.
Thanks guys!
Click to expand...
Click to collapse
As soon as you flash custom recovery knox will be tripped
1eyedmonster said:
As soon as you flash custom recovery knox will be tripped
Click to expand...
Click to collapse
Kinda what I thought would happen unless you changed the bootloader.
You can't change it unless it has the same certificate from Samsung right? Even if you copied it over to a different bootloader?
devilsmarch said:
Kinda what I thought would happen unless you changed the bootloader.
You can't change it unless it has the same certificate from Samsung right? Even if you copied it over to a different bootloader?
Click to expand...
Click to collapse
I know once you have the latest bootloader you can't go back and with the forthcoming android L you will need the latest bootloader so I would just update to the latest version and root and flash away aosp or whatever I know it invalidates your warranty but for me it's worth the risk however the cm12 alpha is full of bugs so I would wait for a beta at least to avoid disappointment
So I just got a 5.0 Lollipop SM-G900A, Baseband G900AUCU4B0F3 warranty replacement for my old rooted 4.4.2 SM-G900A AT&T S5.
I want to get root back. I don't care about warranty since I'm technically out of warranty now and they replaced my phone past warranty (I was really nice to the friendly female CSR I got on the phone). I believe my options are:
Live without root
downgrade to 4.4.2 and root with towelroot without tripping knox
root 5.0 but trip knox
I'd like to do number 3, but I don't know what the best method is at this point. I haven't kept up on any developments in root area since I rooted my 4.4.2 and was supremely happy with it ever since. I know that flashing an already rooted ROM is one of the options but honestly I've gone down the custom ROMs road before on previous phones and I know if I start that again I'll be going through tons of ROMs looking for the one I like best and I've been so happy with rooted vanilla stock that I don't want to take the time to go down that path right now if I can help it. Is there a way to root 5.0 directly if you don't care about Knox/warranty?
I fully realize that I could RTFF and figure out what my answer is but I'm hoping someone who is current will take pity on me and point me in the right direction and cut my RTFF down from hours to minutes. TIA for any help.
https://twitter.com/srsroot/status/634952981960597504
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
I don't believe it's possible to root 0F3 at this time. Sorry bro...
If root is achieved once again, I would highly recommend sticking to Muniz_ri's rooted stock roms which can be found in the "General" section of each carrier-specific S5 Thread, then running his debloat script (and installing google now launcher) to have a very clean android.
Has there been any updates on this? the "SRSroot" site seems sketchy. Google is not showing me results that I want to hear.
Frankbot said:
Has there been any updates on this? the "SRSroot" site seems sketchy. Google is not showing me results that I want to hear.
Click to expand...
Click to collapse
No update, still unrootable.
Sent from my Galaxy S5 using XDA Labs
Hey there
I am basically fixing my sister's Galaxy S5 (G900H) by just completely formatting the device and installing the latest software since it has slowed down considerably. The only experience I ever had with Samsung devices was with my old Galaxy S3 so I'm kind of familiar with the whole process or at least I'll do some reading to catch up, but my question is, which ROM should I go for? What is the latest and most stable? I know this is a difficult question to answer because it is subjective and based on personal preference (I'm a HTC addict so I know all about that), however I cannot really see any of the familiar ROMs like Android Revolution HD, Venom/Viper ROM, etc. so I am having a hard time deciding. I want a ROM that is as stock as possible like Android Revolution HD on many devices.
Any help is appreciated.
Thank you guys!
EDIT: On a side note, I know the best thing to do would be to go to SamMobile and download the latest official firmware, but from my experience with many Android devices I believe that custom ROMs are the best since they are debloated and customized for optimum performance and battery life, especially since Samsung seems to enjoy bloating their devices with so many unnecessary things.
Latest stock lollipop is great IMO, no need for custom at least for mine
Custom always come with problems from experience, better speed and smaller size at the expense of stability, Id opt for stability every time
Thank you for your reply. I decided I should install the latest official ROM then root the device and debloat it myself. It'll take a bit more time but it's worth it, I suppose. Thanks again!
That's what I've done, the stock ROMs are great IMO, apart from the bloat of course
Just be advised that some people are finding it impossible (or very difficult) to root the latest Lollipop firmwares......
If you have KitKat on the device, a better option would be to root that, then retain root access through and during the upgrade process.....The way to do that (so I believe) is.....
Root KitKat. ...
Use Mobile Odin or Flashfire (both apps by Chainfire) to upgrade to Lollipop while injecting root at the time of flashing.
For info......Flashfire is the newer, more up to date of the two.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
I know this is a late reply but I recently acquired my sister's S5 after giving her my other phone, an iPhone 5S (stupid move by her, I know, but good for me), and the device is currently on Android KitKat. I already downloaded the latest Lollipop firmware from SamMobile, so from my understanding I should root KitKat using Flashfire, then upgrade and at the same time include the root file using Flashfire?
Thanks!
TarekElsakka said:
I know this is a late reply but I recently acquired my sister's S5 after giving her my other phone, an iPhone 5S (stupid move by her, I know, but good for me), and the device is currently on Android KitKat. I already downloaded the latest Lollipop firmware from SamMobile, so from my understanding I should root KitKat using Flashfire, then upgrade and at the same time include the root file using Flashfire?
Thanks!
Click to expand...
Click to collapse
No fella.....not quite.....
You can't use Flashfire unless you already have root access.....
If you are on KitKat, you have 2 options for root.......
1) Towelroot......This will give you root without tripping Knox
2) CF Root......will give you root but WILL trip Knox.
Once you have got root THEN use Flashfire to upgrade to Lollipop and retain root.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Awesome, @keithross39, thank you for the helpful information. This is a stupid question but what is Knox?
Knox is an eFuse that gets unalterably tripped if a custom software package is installed.......
It's primary use is to ensure that a device is safe for connection to enterprise (business) networks.....
But Samsung are also using it as a warranty flag.....
Once Knox is tripped, they refuse to supply any form of warranty repair......even if the software modifications had absolutely nothing to do with the fault......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Thanks again, keith, you've been a great help. The device's warranty has already ended quite some time ago because it was only for one year, but I guess it's better to be safe than sorry in case a factory problem comes up somehow. Thanks again!
No problem fella....too true...better safe than sorry..
I think I read some time back that Samsung refused to repair a knox tripped device even though the phone owner offered to pay in full for the repair.....
Shows you how serious Samsung is about Knox.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
I agree you can always run into issues with custom ROM's. Although I prefer them over stock to be honest. The inner tech nerd in me.
DigitalCorrosion said:
I agree you can always run into issues with custom ROM's. Although I prefer them over stock to be honest. The inner tech nerd in me.
Click to expand...
Click to collapse
True.....it's fair to say that we wouldn't be here if we didn't care for the benefits of custom roms.....
But for me at least, knox has (temporarily) removed that option. When my warranty has expired, I guess I'll start to experiment.....but that's not for another 15 months yet.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
I just tried rooting using TowelRoot but it kept giving me an error "this phone isn't currently supported". I went on Google and tried changing the code strings by tapping the "welcome" sign three times and changing the codes, but none of them worked. I guess my only option is to root using CF-Auto-Root, huh?
TarekElsakka said:
I just tried rooting using TowelRoot but it kept giving me an error "this phone isn't currently supported". I went on Google and tried changing the code strings by tapping the "welcome" sign three times and changing the codes, but none of them worked. I guess my only option is to root using CF-Auto-Root, huh?
Click to expand...
Click to collapse
The device probably *is* supported but the kitkat build may be too recent.....
Go to settings >> about device and check the build date.....
If it was compiled on or after July 1st 2014, then you need to download an older kernel and Odin flash it before attempting to towelroot.....
The exact steps are as follows.
1) source a copy of your current kernel and an older (device specific) Kernel.
2) odin flash the older kernel.
3) Reboot, install towelroot and run it
4) odin flash your current kernel.
5) Reboot and enjoy root access.
At stage 3, your phone will appear to be unstable, don't worry about this, it is to be expected.
For information, which build of kitkat is installed on your device as of now?
Edit.....This is the guide I followed to root....
http://forum.xda-developers.com/showthread.php?t=2843044
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Okay, let's see:
Model number: SM-G900H
Android version: 4.4.2
Kernel version: 3.10.9-2109283
[email protected] #1
Wed Jul 9 14:56:51 KST 2014
By looking at the information, I don't think I am running a recent version at all!
Ah.....900 "H"......exynos version right?
I don't have experience of that model, and I think I read that the H variant isn't compatible with Towelroot. ......
Someone correct me if I'm wrong.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
I am not sure which version it is, to be honest. I've tried Googling but I couldn't find anything related to official kernels, just custom ones. If I were to take a wild guess, I'd have to assume that I could extract the kernel from an old firmware on SamMobile? This seems to be the oldest one for my device:
2014-04-01 Egypt 4.4.2 G900HXXU1ANCI G900HOJV1ANCH
But then again is extracting the kernel from it even possible?
Just done a bit of Googling.......
http://www.droidviews.com/root-att-and-verizon-galaxy-s5-without-voiding-knox-warranty/
If you decide to try and towelroot, you are going to go down a long and unsuccessful road....
From what I've read, CF Root is the only option.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
It seems like I am going to go the custom ROM route since I will be tripping the knox system at any case. Thanks for all your help, man, I truly appreciate it.
I have been a HTC user for a long, long time now and my main recovery is TWRP, should I go for that on my S5? I only see Philz (CWM) recovery mentioned around here, though, so I'm not too sure. I'm also going for this ROM: AbhiDroid S6 port for S5[SM-G900H].
So basically I had a custom firmware on my s8 for a while and decided to go back to stock. Now I know knox is flagged, but should it really have problems with apps reporting that it's rooted?
For example, secret mode on the browser reports unavailable because it's rooted and my bank app won't let me use fingerprint login because it's apparently modified.
I used Odin to flash back to stock and used the CSC that resets the phone. Is there any other steps I missed or does knox trigger all this now?
steocullen91 said:
So basically I had a custom firmware on my s8 for a while and decided to go back to stock. Now I know knox is flagged, but should it really have problems with apps reporting that it's rooted?
For example, secret mode on the browser reports unavailable because it's rooted and my bank app won't let me use fingerprint login because it's apparently modified.
I used Odin to flash back to stock and used the CSC that resets the phone. Is there any other steps I missed or does knox trigger all this now?
Click to expand...
Click to collapse
Yes unfortunately Knox triggers a lot of stuff now, s health and all sorts won't work.
sofir786 said:
Yes unfortunately Knox triggers a lot of stuff now, s health and all sorts won't work.
Click to expand...
Click to collapse
So in that case then does it make more sense to just go back to a custom rom that fakes knox? I only went back to stock to get the firmware updates and bugfixes etc.
steocullen91 said:
So in that case then does it make more sense to just go back to a custom rom that fakes knox? I only went back to stock to get the firmware updates and bugfixes etc.
Click to expand...
Click to collapse
That's i would recommend, it's best to choose a Rom that's regularly updated,the devs will update the base of roms which will include bugfixes and security updates.
sofir786 said:
That's i would recommend, it's best to choose a Rom that's regularly updated,the devs will update the base of roms which will include bugfixes and security updates.
Click to expand...
Click to collapse
That's cool thanks. I had an old version of batman rom and when I had an s7 I used to have the superman rom. Both were Tkkg1994 and the superman rom seemed great on the s7 so I'll probably go with his latest one to try it out.