Database Users

[Q] Some Questions About Software Update

Hey everyone,
Just wanted to ask a quick question regarding the firmware
I got my UK unlocked S5 last week and as soon as I set it up, an update came through, which is 100mb, the note regarding say "Improved performance", the update download, but I haven't installed it yet. Mainly because of a bad experience I had after updating my S3. I haven't come across any bugs since I've been using it, and I'm concerned that if I update, the battery will drain quicker, or perhaps cause an error in the recovery mode(these things happened to my S3 after updating to 4.3). So 2 main questions.
1. Has anyone here downloaded this 100mb software update their S5? If so, what differences did you notice?
2. Suppose I updated and wasn't happy with the new changes? Would it be possible to go back to the original firmware version that my phone came with when I took it out of the box, *without rooting my S5?
Hope some people on here can shed some light on these questions.
Thank you in advance*

1. It's just a system update. The phone is new there are bound to be updates as issues are ironed out
2. You can odin any firmware whenever you want
Sent from my SM-G900F using Tapatalk

MasterfulNinja said:
Has anyone here downloaded this 100mb software update their S5? If so, what differences did you notice?
Click to expand...
Click to collapse
Your instincts are dead on. Updates may fix bugs or add a desireable feature. But just as often they introduce new bugs, break root or disable root exploits, break a few apps and add noxious DRM frameworks like the Knox qfuse warranty bit. They can seriously mess up a custom ROM and may depreciate features like MSC or car dock that may be important to you personally.
Updates cannot always be reverted. Try downgrading your Kitkat baseband to Jellybean and see what happens. Or try removing the Knox security bit after you take the update that introduced it. I disable automatic updates and wait to hear what early adopters find before upgrading.
Unfortunately you didn't tell us the all important version of your update. Or even tell us what your current firmware version and carrier are. Your update might be similar to the recent ATT /Verizon OTA adding the mixed blessing of reactivation lock. That is causing bootloops for some people with custom kermels. 4.4.3 is mostly bug fixes, with a few UI tweaks. And I believe 4.4.4 took aim at closing yet another open-SSL exploit and reverting some of the new 4.4.3 bugs.
No matter what an update intends to do, a few new bugs and unexpected conflicts usually turn up. A quick Google finds reports like this:
International Business Times said:
Issues Spotted for the Android 4.4.3 Kitkat
The Android 4.4.3 Kitkat system update is pretty much all about improving performances, strengthening stability and fixing a couple of bugs. However, it reels in a couple of issues experienced by users of Nexus devices that have already been upgraded to the latest update.
According to IT Pro, some of these issues include wi-fi problems, crashes and reboots and bugs found in apps. Google has not yet given any statement about how to deal with these issues nor has there been any word if these issues are only experienced by a handful.
Click to expand...
Click to collapse
.
.

fffft said:
Your instincts are dead on. Updates may fix bugs or add a desireable feature. But just as often they introduce new bugs, break root or disable root exploits, break a few apps and add noxious DRM frameworks like the Knox qfuse warranty bit. They can seriously mess up a custom ROM and may depreciate features like MSC or car dock that may be important to you personally.
Updates cannot always be reverted. Try downgrading your Kitkat baseband to Jellybean and see what happens. Or try removing the Knox security bit after you take the update that introduced it. I disable automatic updates and wait to hear what early adopters find before upgrading.
Unfortunately you didn't tell us the all important version of your update. Or even tell us what your current firmware version and carrier are. Your update might be similar to the recent ATT /Verizon OTA adding the mixed blessing of reactivation lock. That is causing bootloops for some people with custom kermels. 4.4.3 is mostly bug fixes, with a few UI tweaks. And I believe 4.4.4 took aim at closing yet another open-SSL exploit and reverting some of the new 4.4.3 bugs.
No matter what an update intends to do, a few new bugs and unexpected conflicts usually turn up. A quick Google finds reports like this:
.
.
Click to expand...
Click to collapse
Thank you very much for your detailed answers! That's exactly it! And I know from experience that updating firmware can cause a negative affect to the phone's performance. My iPhone 4S is still on iOS 5.1 but runs perfectly, while friends who updated their 4S to 7.1 experience freezes and heavy lag. Maybe companies do this deliberately, so people get frustrated and end up having to get the latest, more powerful model so the OS to run smoothly?
I do exactly the same, I always wait to see what people about an update before updating. The only difficulty with Android updates is that there seem to be so many different versions of updates. For example, when I researched the 100mb one for the S5,* various sites mentioned it, but others say the size of the update was 30mb, which were called "improved performance" I also heard about updates not always being able to be reverted to the previous version,* and also about Knox. So, you can see why I'm hesitant to update.
I know quite a bit about using Android, but have very limited knowledge regarding rooting and custom roms and so on. Also, after reading that rooting a phone incorrectly can turn it into a brick, I'm happy to just leave it as it is. I've attached a photo which shows my current firmware version, as well as other information. Also, as my S5 is unlocked, the only updates I'll receive will be from Samsung. I asked my carrier (T-Mobile UK) and that's what they told me. Only phones from bought from them include added apps that they put on, and I think they may also be able to tweak the updates received, by adding their own features.
Some more questions for you;
1. Do you recommend a factory reset after each software update?(I had to factory reset my S3 to stop the battery draining issue that 4.3 caused. But was wondering if it's best to factory reset after each and every update on Android devices)
2. I know you said that sometimes reverting back to a previous firmware isn't always possible, but can't using Odin with the correct firmware version work? Like Goldie mentioned in the above reply. And does changing the firmware via Odin require rooting the phone?

MasterfulNinja said:
Thank you very much for your detailed answers! That's exactly it! And I know from experience that updating firmware can cause a negative affect to the phone's performance. My iPhone 4S is still on iOS 5.1 but runs perfectly, while friends who updated their 4S to 7.1 experience freezes and heavy lag. Maybe companies do this deliberately, so people get frustrated and end up having to get the latest, more powerful model so the OS to run smoothly?
I do exactly the same, I always wait to see what people about an update before updating. The only difficulty with Android updates is that there seem to be so many different versions of updates. For example, when I researched the 100mb one for the S5,* various sites mentioned it, but others say the size of the update was 30mb, which were called "improved performance" I also heard about updates not always being able to be reverted to the previous version,* and also about Knox. So, you can see why I'm hesitant to update.
I know quite a bit about using Android, but have very limited knowledge regarding rooting and custom roms and so on. Also, after reading that rooting a phone incorrectly can turn it into a brick, I'm happy to just leave it as it is. I've attached a photo which shows my current firmware version, as well as other information. Also, as my S5 is unlocked, the only updates I'll receive will be from Samsung. I asked my carrier (T-Mobile UK) and that's what they told me. Only phones from bought from them include added apps that they put on, and I think they may also be able to tweak the updates received, by adding their own features.
Some more questions for you;
1. Do you recommend a factory reset after each software update?(I had to factory reset my S3 to stop the battery draining issue that 4.3 caused. But was wondering if it's best to factory reset after each and every update on Android devices)
2. I know you said that sometimes reverting back to a previous firmware isn't always possible, but can't using Odin with the correct firmware version work? Like Goldie mentioned in the above reply. And does changing the firmware via Odin require rooting the phone?
Click to expand...
Click to collapse
1. Yes, a data factory reset after a update/flash a rom is remmended and gives best performance and stability;
2. I haven`t tried flashing a older rom itself but it should be possible i guess as this is not dowgrading like from 4.4.2 to 4.3. You could try it and if it fails there`s no harm done as you can flash your current rom back.
3. Installing a update or flash a rom usualy will kill root, though superSU Pro offers a survival mode to keep root after a update. You can also flash a rom with Mobile Odin Pro and enable everroot and the 2 other options so you will not loose root.

@MasterfulNinja
I don't automatically accept updates. Someone more impulsive, or indifferent can be the guinea pig. That approach is effective in avoiding some unpleasant firmware surprises. Often an older firmware version runs smoother and is more stable as in your IOS 5 vs 7 example. Running an older firmware means that you may have unpatched security vulnerabilities but in practice this usually isn't a great or unmanageable problem. It is a point to keep in mind though.
Rooting isn't nearly as dangerous as many people think it is. Someone who can follow directions and avoid flashing firmware from a completely different device will rarely brick a phone. And even if you did, you can usually recover from the mishap. I mention this because one of the best ways to maintain a stable phone OS is to install a decent custom ROM (which typically requires root). And then most of the heavy lifting is done by the developer who has already removed bloat, restrictions and other objectionable pieces. And monitors and releases tailored and usually stable updates for those using his ROM.
Android updates vary in size because they are screened by carriers, each deciding what update components and /or custom bits goes into their version of the update. More restrictive Apple manages all IOS updates centrally from their California servers i.e. they don't relinquish direct control to carriers. Still it isn't hard to find articles giving a good summary of what issues android firmware updates are addressing.
Some people believe that you should accept every update and as soon as it becomes available. I don't see a compelling need to update unless you are trying to resolve a current bug or are enticed by a specific new feature. I don't recommend a factory reset after each update. I do recommend that you clear the system cache from recovery mode though. A factory reset usually won't benefit you but it is time consuming to reinstall and reconfigure your phone.
Having said that, if you have a specific issue, such as the 4.3 battery drain then you have a rationale for doing so. But I have to say that I experienced the same S3 issue and clearing the cache was sufficient to stabilize the phone for me. Some phones will develop corruption or configuration conflicts over time, especially if you install a lot of apps. Or if you have a specific app that makes a mess of your file system. With that in mind, I do do a factory reset about once a year to clean up the phone, the same as I would do for a laptop OS. But I don't see a reason to do it after every update.
Odin is a Samsung product, complete with DRM. So no, you cannot flash anything with Odin. You can flash most stock firmware and in particular Odin will look for OEM signatures if you try to change the bootloader or modem. In the case of downgrading, it is the Knox qfuse on your phone that will cause the Odin flash to fail. If you try to downgrade you end up with a partial flash which can soft brick your phone and trip the Knox flag.
.

New to Flashing, Want to install Eclipse [Note 3]

Hello everyone.
Is there a one true guide to installing a ROM on my Note 3? I'm running a T-Mobile N-900T. It seems that after browsing the web, I've seen so many different ways to install a ROM that I'm extremely hesitant to try one on the off-chance that it is no longer supported and may brick my device. This is a non-warrantied phone (bought it on Swappa) so I only get once chance if I end up Hard Bricking it, so my fear level is at the absolute highest.
I wanted to run Eclipse Note 3 TW Rom (found here: http://forum.xda-developers.com/showthread.php?t=2620723) because it's a nice simple ROM that retains S-Pen function and removes all the bloat and stuff. However, I noticed that it says "This is based off of 4.4.2 NC2 for Verizon Wireless." Does this mean it won't work with a T-Mobile Note 3?
This is as far as I got in towards the process before I stopped due to something unexpected:
1) TowelRoot. Rooted it and confirmed with the Root app that it was indeed rooted.
2) Downloaded SuperSU. I installed the binary using the Normal mode since I didn't have CWM or TWRM at the time. It asked me to disable KNOX and it looks like it was fine. I restarted it.
This is where I stopped. After I installed it, it asked me to confirm if I want to confirm allowing Freedom and SetCPU. I did and it continuously started spamming the notification that it was allowed for 20 minutes.
I went into the SuperSU program to see what's wrong and it then told me that the Binary could NOT be found and that I may have to flash my rom back to get it back to normal. It then gave me the error that something was wrong on my phone and that I might have to install something called Samsung Kies to make it better.
I pretty much freaked out at this point and de-installed SuperSU out of fear that I might screw up my phone. Now I'm extremely fearful to do anything without seeing some sort of de facto guide on what to do next.
If it helps, here's the phone information I have. I know that different ROM flashing methods are used for various kernels.
Model: SM-N900T
Android Version: 4.4.2
Baseband: N900TUVUCNB4
Kernel: 3.4.0-660648 | [email protected] #1 | Wed Feb 12 21:31:27 KST 2014
Build Number: KOT49H.N900TUVUCNB4
SE for Android Status: Enforcing | SEPF_SM-900T_4.4.2_0005 | WED FEB 12 21:31:01 2014
Security Software Version: MDF v1.0 Release 2
I have a 128GB Samsung SDXS MicroSD. The phone recognizes 119 GB of it which I know is normal.
Any help or direction would be most appreciated. The world of Flashing has so many roads that my head is spinning and my fear is that I will turn this phone into a $500 brick because I followed the wrong guide.
Thank you.

Best way of flashing a new rom is using "Odin".

dodoqq said:
Best way of flashing a new rom is using "Odin".
Click to expand...
Click to collapse
Thanks.
I do understand that and I have the program, but I can't find any SOLID documentation. I see all these different guides out there and I'm scared that I'm going to pick the wrong one. The ages vary as well, so I don't know if they are still relevant or not.
Not only that, I don't believe that just Odin is enough. There are also prerequisites that are required before I can just up and use Odin. That'st he part that I would hope a decent guide out there would provide me.

A bit early by a few minutes but, Bump for help.
Any information or leads would be terrific.
Thank you.

Nanaya Shiki said:
A bit early by a few minutes but, Bump for help.
Any information or leads would be terrific.
Thank you.
Click to expand...
Click to collapse
Contact me on Google+, I can help you with this and calm you down about it.
It's +NicholasPhilipChum

[Q] I've become an Idiot. (For Sprint)

Alrighty then, I've been gone a good while, and now no longer know what I'm doing, which I know is dangerous.
I'd picked up an S4 for myself and my mother last Black Friday, and that same night, rooted both our phones. I also know that within a good week, an OTA update had been put out, but I'd blown it off, as I couldn't get it going and finishing up my bach and getting into grad school took over my life. That said, I recently got my father's line upgraded to an S4 (it was a dollar and he wanted it, so eh). It forced me to remember my own phone and it's horribly outdated self, and so I have returned.
As it stands now, I do not know what or how to go about getting this puppy up to speed, or even how to really explain where I'm at software wise, so I took a couple snapshots of the phone info, hoping I could get a hand with it.
Any help you guys could give would be appreciated.
Also, not sure if this means anything, but the System update it says I have downloaded will not install.

You have android 4.3 and the latest version is 4.4.2.
Upgrade to 4.4.2 for your phone and then you can flash the latest custom roms for android version 4.4.2 if you are out of warranty and do not wish to use knox.
Youre not outdated. Just a version behind. There are not many changes in 4.4.2 stock rom.
Thank me if I helped
Sent from my Samsung Galaxy S4 via XDA app.

[Q] Towelroot no longer works... ideas?

I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.

CKR83 said:
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
Click to expand...
Click to collapse
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky

Rooting Help?
fgth90 said:
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Click to expand...
Click to collapse
I see that there are tutes here, and am wading through the 50+ pages of forum posts to find what I need. However, my worry is that none of this stuff will work because of the new firmware. Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Thanks all the pertinent info, I think.
Because the update was so new, I don't think there's a way to root this anymore. People keep telling me to use ODIN and to download an earlier ROM (and I now have ODIN and an earlier ROM -- hopefully from a good source, but I have no idea if it is), but my impression is that this latest AT&T "security" update keeps you from reflashing the ROM because of the bootloader lockout.
Any further help would be appreciated.
Thanks

CKR83 said:
...
Any further help would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
As I told you, the only method working for me (because of towelroot non working) is cf auto root.
Check periodicaly here http://autoroot.chainfire.eu/ to see if your model is listed.
I had just a look and it's not listed yet.
If it is, flash by odin and look if root works.
If not, you've got to flash by odin the same rom again (keep your original file on pc), you'll loose nothing, and report this fails on chainfire to test other solution.
Good luck
Franky

CKR83 said:
Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Not only build number and kernel version, you need to check your Bootloader version with Phone INFO ★Samsung★ app (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.

vndnguyen said:
Not only build number and kernel version, you need to check your Bootloader version with (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
Click to expand...
Click to collapse
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Does that help any? People keep telling me I need to use ODIN and flash this, that or the other thing. Those comments would probably be more helpful if I knew more about this stuff, but my reading has lead me to believe that ODIN won't work with certain version of the bootloader. Or is that wrong?

CKR83 said:
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Did you every get your post July 2014 AT&T GS5 rooted?
If so, please drop me an email.
Thanks
TPG
Click to expand...
Click to collapse

No unfortunately not....
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

[Q] trying to update

hey everyone im very new and i would really appreciate if you could help me with this little problem. I got a old s5 from my sister and i noticed it hadn't been updated since she got it. Now, here is where the problem starts, she was using Verizon and i have T-mobile the phone is unlocked but it wont update the os normally... I have no idea how this all works but i think its not updating because its trying to update through Verizon....
so is there a way i can change this phone to t mobile or do i need to self install the os updates myself?
if so then i know that i need to towel root it and i have the program downloaded and installed my device info is blow if you need other information please let me know and i will provide it asap ....plz and thank you
MODEL NUMBER: SM-G900V
ANDROID VERSION: 4.4.2
BASE BAND VERSION: G900VVRU1ANG
KERNEL VERSION:3.4.0

Blaze-209 said:
hey everyone im very new and i would really appreciate if you could help me with this little problem. I got a old s5 from my sister and i noticed it hadn't been updated since she got it. Now, here is where the problem starts, she was using Verizon and i have T-mobile the phone is unlocked but it wont update the os normally... I have no idea how this all works but i think its not updating because its trying to update through Verizon....
so is there a way i can change this phone to t mobile or do i need to self install the os updates myself?
if so then i know that i need to
Are root it and i have the program downloaded and installed my device info is blow if you need other information please let me know and i will provide it asap ....plz and thank you
MODEL NUMBER: SM-G900V
ANDROID VERSION: 4.4.2
BASE BAND VERSION: G900VVRU1ANG
KERNEL VERSION:3.4.0
Click to expand...
Click to collapse
Are you wanting to root it or just upgrade the firmware? Have you ever used Odin?
Try connecting to kies if you just want to upgrade firmware.

Tulsadiver said:
Are you wanting to root it or just upgrade the firmware? Have you ever used Odin?
Try connecting to kies if you just want to upgrade firmware.
Click to expand...
Click to collapse
I:silly:'ve only done that stuff on my old iPhone, but when i switched to android it was like coming from north korea to china. Its just so much freedom I've never experienced before and i'm super happy i'm here( china i guess) but i couldn't imagine what america freedom feels like...and i'm guessing having it rooted and flashing custom Kernel would be like coming to america. I doubt ill ever get around to using those things to there full potential, so i guess ill just upgrade the firmware... unless you have movies or stories of the freedom im missing i doubt ill venture out to go find it. thank you for your info and looking forward to your reply

Blaze-209 said:
I:silly:'ve only done that stuff on my old iPhone, but when i switched to android it was like coming from north korea to china. Its just so much freedom I've never experienced before and i'm super happy i'm here( china i guess) but i couldn't imagine what america freedom feels like...and i'm guessing having it rooted and flashing custom Kernel would be like coming to america. I doubt ill ever get around to using those things to there full potential, so i guess ill just upgrade the firmware... unless you have movies or stories of the freedom im missing i doubt ill venture out to go find it. thank you for your info and looking forward to your reply
Click to expand...
Click to collapse
No custom kernel for us. We have a locked bootloader. We do have custom Roms. I would root but that is just me. I dislike all the bloatware if nothing else. You don't have to use your phone any differently but you never know when you will come across a great app or something and it requires root.
You are on the right firmware for root. Install towelroot, make it rain, download SuperSU from the playstore, install and update the binaries (it will ask you to) choose the normal method. Reboot your phone and you are rooted. I would go a step further and download busybox from the play store, install the app then install busybox, then install safestrap which is our custom recovery.
You can still just run a stock ROM if you wish but you now have the ability to change your phone to a certain degree. At least get rid of some bloatware. Otherwise, I'd try kies first and see if it will update your phone.
http://www.samsung.com/us/kies/