Which ROM should I opt for? - Galaxy S 5 Q&A, Help & Troubleshooting

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].

Related

Want to root but scared

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.

[Q] Updating a rooted S5 keeping root and knox 0x0

I have had an S5 since around this time last year. I rooted with towelroot so that I could stop the annoying camera shutter sounds. Recently I keep hitting a bug on Android with cq-camera-daemon process draining the battery. I keep getting OTA notifications weekly telling me that a new update is available.
Basically, I would like to update to the latest stable to get rid of that bug, but I would also like to keep root so I don't lose functionality / access. Also would like to keep knox 0x0. What is the best way to do this today? I've not visited this site since I used towelroot and it was such a long time ago I can't remember much.
thanks
Hi All,
Just signed up - you have a great community here!
I'd like to +1 this question as well.
Thanks. My problem is that I don't really know what to search for or what is new or outdated info.
I did keep searching and I've may be found the following:
- using towelroot disabled knox. Since it is disabled, the features gained with knox can no longer be used anymore anyway.
So I guess that there would be no harm now in tripping knox as the phone is out of warranty anyway? If this is the case, then I'll just follow the documented procedures to do a full flash of any stable custom ROM.
First of all, the warranty on Samsung's phones in the UK is 2 years.......
I *think* I've read that an app being developed by Chainfire (called Flashfire) will allow updating to Lollipop without tripping Knox......although I don't mind being corrected on that if I'm wrong......
Here's the thread link......
http://forum.xda-developers.com/showthread.php?t=3075433
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Thanks for your reply mate!
How did you manage to root and still keep kn0x0?
When I got my phone, it was running KitKat......I DIDN'T let it upgrade to Lollipop.........then I followed this guide...
http://forum.xda-developers.com/showthread.php?t=2843044
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Thanks, I might give this a go today.
My Samsung is an Australian variant. I think we only have 12 month warranty here. I've not seen anything to suggest otherwise.

will upgrading to Lollipop delete installed mod on KitKat?

Hello everyone
I just bought a new Samsung Galaxy S5 international (SM-G900F) and I am about to root it in order to be able to install a sound mod which boosts the sound. I was considering using the one from this thread: http://forum.xda-developers.com/showthread.php?t=2729652
Basically, it will modify the sound setting values found in mixer_path.xml file in /system/etc
How it is going to be done: (Help needed here)
Plan A- I am planning to downgrade to KitKat in order to root without triggering the Knox counter, then install the mod, then upgrade to LolliPop again.
Plan B- Alternatively, I can downgrade to KitKat and root, then install a prerooted lollipop rom (not sure if it will trigger the Knox counter), then install the sound mod.
Plan C- Maybe there is a method you can tell me about to access the system files of the phone from ADB on my pc without rooting and just modify the values found in mixer_path.xml file in /system/etc
Plan D- A less probable way would be to download an original Lollipop Rom, modify the mixer_path.xml file in /system/etc, save it and then flash it to the phone as an official Rom using Kies 3. I don't even know if this is possible.
Whichever method I choose to go with, I intend to unroot once the Mod is installed in order to get OTA updates. (Not sure how to do this)
My questions:
If I upgrade from KitKat to LolliPop, will it write a new mixer_path.xml file with the default values? Or will it keep the modified version of the file?
If I install the Mod on Lollipop, will an update (OTA) write a new mixer_path.xml file with the default values? Or will it keep the modified one?
Also, once my phone is rooted, I believe OTA updates will not work, so how do I manage to get back the OTA updates from Samsung without losing the modified version of mixer_path.xml file in /system/etc? I don't mind losing root access once I have my sound mod installed.
Thank you very much for your answers, and feel free to tell me what is the best plan or point me toward a better method to achieve this, or anything else that I might not know regarding rooting the S5 without triggering the Knox counter.
Have a great day
ofcourse your mods will reset to default values after update....
and if you want ota updates then you need to flash official stock rom via odin
shazore said:
ofcourse your mods will reset to default values after update....
and if you want ota updates then you need to flash official stock rom via odin
Click to expand...
Click to collapse
Thank you Shazore, I guess I will have to root after each update to reapply the mods, it's just that it might take weeks or months to find a vulnerability that allows to root a new build after an update. But I guess the S5 will not receive any further official updates after 5.1.1 which is a piece of cake to root, unlike marshmallow which imho will possibly take a while to get rooted.
Thank you again for the reply and have a great weekend
If you are worried about tripping knox, lollipop is NOT a piece of cake to root......
The only method of rooting LP (that I've read about) is CF Root which WILL trip knox......
If you want to keep knox at 0x0 and be running LP, then you need to 'towelroot' while on KK and use an app like Flashfire to inject root into a LP firmware as it's flashing it......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
If you are worried about tripping knox, lollipop is NOT a piece of cake to root......
The only method of rooting LP (that I've read about) is CF Root which WILL trip knox......
If you want to keep knox at 0x0 and be running LP, then you need to 'towelroot' while on KK and use an app like Flashfire to inject root into a LP firmware as it's flashing it......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
In all honesty, around June I spent like a week of googling and reading on how I can get root on lollipop without triggering knox but all I could find was unclear and incomplete tutorials which involved going back to Kitkat and root with towel root and update to lollipop using a modified lollipop rom from Alexander or something like that. I finally gave up because the method was not properly explained which made it too risky to trigger knox.
From your message it sounds like they came up with a new method (chainfire) which I would be happy to try if I have a clear tutorial to follow Would it be possible to point me to the tutorial you followed to root your S5 while keeping knox0?
Thank you in advance for your help
I used the first part of this tutorial to root while still on KitKat........
http://forum.xda-developers.com/showthread.php?t=2699648
then I froze the system apps that controlled firmware updating......
And here is the thread for Flashfire.....
http://forum.xda-developers.com/showthread.php?t=3075433
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I used the first part of this tutorial to root while still on KitKat........
http://forum.xda-developers.com/showthread.php?t=2699648
then I froze the system apps that controlled firmware updating......
And here is the thread for Flashfire.....
http://forum.xda-developers.com/showthread.php?t=3075433
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Thank you for providing the tutorials to follow, it's sad that a full tutorial still doesn't exist, but hopefully people can find your post and get access to both tutorials
I am very excited to get started and about all the cool stuff I wanted to install once rooted.
I will see if I have time next week to backup everything that's on my S5 and get started with downgrading to KK and rooting, what scares me most is this Flashfire process as I have never tried it. I guess if it worked for you it should work for me too
If I encounter any problem I will post it here or/and in the relevant thread.
Thank you again and have a great weekend
Hey....no problem fella......
Just one thing though.......at no time have I ever used Flashfire.......My phone came with KitKat and remains to this day with KitKat......The only reason I even know about Flashfire is that I saw people mentioning it on the Mobile Odin thread (which I have purchased and used on my S2)
I have absolutely no intention of upgrading to lollipop until (if) xposed becomes compatible.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
Hey....no problem fella......
Just one thing though.......at no time have I ever used Flashfire.......My phone came with KitKat and remains to this day with KitKat......The only reason I even know about Flashfire is that I saw people mentioning it on the Mobile Odin thread (which I have purchased and used on my S2)
I have absolutely no intention of upgrading to lollipop until (if) xposed becomes compatible.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Thank you for the additional input, xposed is not something I use that often, I just have it on my Galaxy Tab 4 7" to customise the look and add some functionalities to the stock debloated rom.
One of the only reason I need root on my S5 is to have access to the sound settings XML file and boost the headphones amplifier, I don't like using apps that pretend to boost your volume when in fact all they do is to boost your gain which distorts the sound and make it sound louder at the price of poor sound quality. That's why I want to access the sound mixer and increase the output power of the sound card without altering the input gain.
Once someone figures out how to safely bypass the knox security to allow flashing everything out there, I will be more than happy to get a taste of Marshmallow on my S5 Till then, I guess I will have to try it out on my moto g 1st generation, it's amazing what Motorola did with that phone: Water resistant, updates almost as fast as a nexus, descent specs, good screen and long battery life. When I compare it to my S5 it feels like the moto g is a bargain comparing to my powerful but overpriced S5.
I shifted off topic, lol. I will try to find time next week to get root on my S5, thank you again for all the support
Yeah....It looks like Knox is here to stay, and it would seem that most devs have given up on trying to crack it.......
The main reason I use xposed is for Rootcloak......I use some apps that look for root access and refuse to open if they detect it.......
I need these apps, but at the same time, having an unrooted device is really not an option for me.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
Yeah....It looks like Knox is here to stay, and it would seem that most devs have given up on trying to crack it.......
The main reason I use xposed is for Rootcloak......I use some apps that look for root access and refuse to open if they detect it.......
I need these apps, but at the same time, having an unrooted device is really not an option for me.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
I didn't know knox cracking was being abandoned by the devs here. That's sad because all current and future Samsung devices will have the knox protection, which means one has to choose between keeping warranty on a bloated slow phone or customising their phone at the expense of losing the warranty. The loss is always on the consumer side and Samsung has everything to win: they win by pushing people to use their useless apps which generates more income for the company (through advertising or data collection), and if you don't want to use these apps and get a clean or custom rom, then you have to root and lose your warranty which gives Samsung a good way to escape their responsibilities whenever a device is faulty because of a bad manufacturing process, therefore they win by not having to fix or replace these faulty devices using the excuse that rooting could have been the cause of the damage.
I live in Germany and from what I have read on many threads here I will not be losing my warranty if I root because the European laws protect the consumer. I still wouldn't want to try my luck and would rather wait that my warranty is almost finished before carelessly rooting and trigger knox, my S5 is covered until December 2016.
Your needs for xposed are justified, there is always a choice to make but Kitkat is not a bad one, it's still a great version of Android and shouldn't cause you any troubles with apps built with lollipop in mind. The only negative thing about Kitkat comparing to lollipop would be the dalvik cache which doesn't give you the same fast launch speed for apps as you would experience under lollipop. But hey, what's 3 seconds longer to launch maps or chrome? It's not like there is fire in the house and you need to find an exit during these 3 seconds relying on Google maps, lol.
Since this thread seems active, I take the chance to ask a question:
I am setting up a phone to give to my mother which lives in another country and I am visiting her soon, I customised the original but rooted rom with the apps I judge useful for her and removed all the crapware.
The problem is: she might encounter a problem at some point (supposed in 6 months) and someone might reset the phone for her, she will be lost once the phone gets back to factory settings and no one around her will have the knowledge to set it the way I did.
So how can I implement the changes and integrate them into the factory image on the device? I don't want to do it through a NANDROID backup because she wouldn't know how to access the recovery and the process will be too complicated compared to just going to the settings and click on factory reset.
Anyone with a good idea or a useful link to another thread explaining g how to do this?
This app.......
https://play.google.com/store/apps/details?id=de.j4velin.systemappmover
will apparently convert 'user' apps into system apps. I guess it does so by moving them to the system app partition. If I understand this correctly, doing this will protect them from erasure even if a factory reset is done.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
This app.......
https://play.google.com/store/apps/details?id=de.j4velin.systemappmover
will apparently convert 'user' apps into system apps. I guess it does so by moving them to the system app partition. If I understand this correctly, doing this will protect them from erasure even if a factory reset is done.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
I checked this app on the store and I am going to give it a try, I will copy the apps I need after the reset to the system partition on my moto g and make a factory reset, I will report if it works
Just to make sure I don't get stuck on a bootloop, could you give me your opinion on what folder I need to copy the apps to? And should I copy the installed apps or should I copy the apk version of them? Thank you for your input
Right now the wife is giving me a headache because I spend more time on xda than with her, hahaha, I hope to get the chance to experiment with this app sometimes today.
I wish this app worked on my wife's brain, I need to debloated her and disable the app that makes her so annoying, hahaha
I will be reporting if the app works for creating a custom image for the reset as soon as it's done
Thank you once again.
Lol about the wife.....been there, done that, still wearing the teeshirt.......
About moving the apps.....I don't think you have to do any moving yourself.....
You just install the apps as normal then get the linked app to do the rest.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
Lol about the wife.....been there, done that, still wearing the teeshirt.......
About moving the apps.....I don't think you have to do any moving yourself.....
You just install the apps as normal then get the linked app to do the rest.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
I am finally back after spending yesterday and today testing various things I wanted to experiment I used the app you linked to transfer some apps to the system partition, it worked perfectly and the apps I added were still there after resetting my phone Thank you for that one, this will be very useful in the future
Unfortunately the app you linked couldn't do the opposite operation, it couldn't remove the default apps that I didn't need or that were bloatware because this option is not supported in lollipop, so I uninstalled them using titanium backup but I ended up getting error messages and had to restart to twrp recovery where I cleared the cache and the dalvik, unfortunately it didn't help and the phone didn't want to complete the boot, I then had to flash the rom again through adb, then the phone booted fine.
I repeated the operation of removing the unwanted apps using es file explorer and accessing the system folder to delete the apk of the unwatchable apps, this also generated errors and I ended up having the same story as the previous situation where I was unable to boot, my last resort was to flash the rom again.
I concluded that some apps I removed had some sort of link to other apps relying on them, either relying on the manufacturer's framework or it is a security bug I generated where an app is looking for one of the apps I removed to launch. At the end I gave up on seeking a clean rom and this time I will just remove the most annoying apps that are not related to the manufacturer.
As for the wife thing, I might be joining your club of single men, lol, a divorce seems inevitable, but that's definitely not the right place to discuss that
Once again thank you very much, your support was great and I shall pm you to join my future thread(s) the next time I have a query I have clicked the thank you button in every reply you posted, that's to show my gratitude
No problem fella.....i'm not an expert at *all* things Android, but if a question is asked, and I know the answer, I'll do what I can to help/advise.....
I'm still married myself (20+ years).....
All I'll say on that is.....I would have had a shorter prison sentence if I'd committed murder.....and best to leave it at that....lol
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
No problem fella.....i'm not an expert at *all* things Android, but if a question is asked, and I know the answer, I'll do what I can to help/advise.....
I'm still married myself (20+ years).....
All I'll say on that is.....I would have had a shorter prison sentence if I'd committed murder.....and best to leave it at that....lol
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Hahaha, I am not willing to serve a 20 years sentence and murdering is for the moment not one of my plans, I say for the moment, lol.
I decided to give to the xda community some of my knowledge as a way to pay back all the help I got in the forums, you can have a look at this link if you ever want to boost your sound
http://forum.xda-developers.com/general/general/guide-technical-explanation-boost-t3202087
Feel free to drop me a reply there if you think something needs to be improved or changed
I am still hoping to get a day away from my wife hopefully this week or the next one, so that I can root my S5 under Kitkat and upgrade to lollipop following the tutorials you shared on a previous post. I will report if it works or I will write here if I have some kind of problem (hopefully not, lol).
Till then I wish you a great day and thank you again for everything

Guidance on restoring S5 to "clean" for returning to VZW

I rooted my S5 last Spring. I forget the name of the root. It was where you downgraded to KK NK2, did the root and then loaded a Lollipop (OA8 I think). I believe this left Knox intact. Which is good because I have a Verizon Edge plan and I'm about to dump this POS for a Note 5.
Can anyone give me guidance on how to restore this phone to a state that VZW would accept? I assume they wouldn't like it the way it is if they looked. I've got the unlocked padlock at boot. Will a factory reset do it for me? Or do I need to find a clean RIM like NK2 or OA8 and reflash it? I currently have OC4 loaded. I have a pending OTA upgrade but my phone refuses to take it for some reason. Perhaps it's the root?
Thanks
Mac
Towelroot. That's what it was called.
macdaddy69 said:
Towelroot. That's what it was called.
Click to expand...
Click to collapse
Bump. My Note 5 has shipped...
If you towelrooted, then knox *should* be intact......It just depends on how you kept root on upgrade to Lollipop........
Provided knox *is* at 0x0 (can be checked by booting into download mode and reading what the counter says) simply odin flashing a stock firmware will be enough to return the device to an *acceptable* standard.......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
The last time I checked is was 0x0 still. The download mode screen no longer reports anything about Knox on my phone though. Seems like there was an app that would report it but I can't recall what it was called. It was a basic Towelroot root, then pushed the pre-rooted ROM of 0A8 I think. It was the popular method last Spring. I can't recall much more than that.
I'll see if I can locate a clean ROM. I'll factory reset it and then push that ROM. My new phone is shipping much faster than expected. It should be here tomorrow or Tuesday. It's not due for a whole week oddly enough. And no mention was made of returning the S5. I wonder if it's slipping through the cracks of VZW's Edge plan...
This *might* be the app you were thinking of.....
https://play.google.com/store/apps/details?id=com.bryancandi.knoxcheck
The chances are that the pre rooted os you pushed had the knox c**p disabled....
That being the case, you should be ok....
Don't get too sure that VZW has forgotten about your S5, they're probably waiting til you've signed for your new device before chasing you for the S5.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

Just got an AT&T Android 5.0 warranty replacement for my rooted 4.4.2; options?

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

Categories

Resources