Related
I've read a few posts stating the bootloader exploit for the S4 would be relatively easy to patch by At&t and my concern is that they may do so before my upgrade on June 7. If at&t does patch it before then would it be possible to use Odin to downgrade the phone to an earlier firmware release that doesn't have the patch? If not I'll have to figure out a way to get the phone as soon as possible.
calvin35 said:
I've read a few posts stating the bootloader exploit for the S4 would be relatively easy to patch by At&t and my concern is that they may do so before my upgrade on June 7. If at&t does patch it before then would it be possible to use Odin to downgrade the phone to an earlier firmware release that doesn't have the patch? If not I'll have to figure out a way to get the phone as soon as possible.
Click to expand...
Click to collapse
I don't see how anyone could know that for sure at this point. However, if a patch is released (OTA) or if newer firmware is put on the phones that patches the vulnerability itself, then it seems realistic that ODIN probably will not be able to fix the issue. Once it is patched, you probably won't be able to go back. Of course, another exploit might be found or Adam's attempt at a more permanent bottloader unlocker might find a solution. OTA updates can be fixed by just not taking them until they are cleared as OK. Newer firmware on the phone would probably need another fix. But nobody knows how long it will be until AT&T / Samsung patches the vulnerability.
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.
.
Hello XDA community,
This is my first post on here and I hope I'm not doing something wrong in terms of protocol, but I have a rough idea on finding a root for this phone that needs support and refining from you guys, the XDA community.
My idea is this: If we can find a way to downgrade the phone software back to before the December 2016 security patch, we can run a Dirty Cow root exploit (, which is ready to go on GitHub, ) to temp root this device (or any device, in theory). Once we have temp root, we could run a program like SunShine or whatever else to turn that temp root to perm root. (SunShine currently says that, to full root this device, it needs some kind of temp root.)
Now going back to the first part about downgrading the software to before the December 2016 security update, I initially thought we could achieve this through mfastboot or RSD Lite, since they allow flashing of officially signed Motorola firmwares. However, I read that when upgrading the Moto Z, and presumably all other variants, from Android MM to Android N, the (locked) bootloader is updated, too, and will not allow downgrading, resulting in a prevalidaton error. This is where I need your help.
The question is: How can we downgrade the firmware back to MM, or some other before-December firmware, to use Dirty Cow for root. Please leave ANY suggestions in the comments.
Thank you for your time and help. I have faith that we will be able to solve this together.
I don't think you can downgrade. But i've been running this for the past 9 or so months to prevent the forced updates: https://forum.xda-developers.com/moto-z-play/themes/app-moto-z-play-apps-stop-ota-motocare-t3538812
(no idea if that would work on the z force)
Well I know there are many videos on YouTube claiming to downgrade certain Moto devices through RSD Lite or mfastboot for different budget Moto devices, but I suspect they are all fake. Nonetheless, I hope there is a legitimate way to downgrade.
I forgot to mention that if you can get a replacement Moto Z Force from Verizon, which is very easy to do in my area, they ship you a refurbished replacement, which runs marshmallow and has no updates installed, but I don't have the opportunity to get another replacement, so for anyone else, that's one way you could "downgrade" and try Dirty Cow to root the device.
I'm just going by this topic https://forum.xda-developers.com/moto-z/how-to/dont-upgrade-to-nougat-ota-t3524456
but i don't really know for sure
Wow. Now I wish I'd known about this MUCH sooner. Its too late for me. Well, in that case, try to see if you can revert back to marshmallow if you unofficially upgraded to nougat and check what month of security patches you are on. If it's before the December 2016 security patch, then you can run Dirty Cow and get temporary root. With temp root you can most likely find a way to make it permanent root.
If i install the UK fingerprint version here . Will the update still come to my phone? I see they have new updates now and oreo 8 is coming. Will i be able to install those from within the device or will i run into issues?
Also are there any issues using the UK rom over the US rom?
Also are there any better ways to enable the fingerprint sensor without install the UK version?
Does it also void warranty?
Thanks!
I'm in the US & I installed the UK ROM you link to above. It works as advertised. I wondered about receiving the update as well and read through the entire thread. It says you will be able to receive updates and you won't void your warranty since you are flashing official firmware. Of course that is just a post on an internet forum and carries no weight. Other than the warranty does it really matter? You can always update using Flashtool.
Yesterday I updated to 8.0 following this thread https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479 and now I have 8.0, my bootloader is unlocked, I have root, adaway, my phone passes safetynet, and most importantly it still works..
There are some subtle differences between N & O that have made it worthwhile. Sorry I can't be of more help, I can only share my positive experience.
rjglenn said:
I'm in the US & I installed the UK ROM you link to above. It works as advertised. I wondered about receiving the update as well and read through the entire thread. It says you will be able to receive updates and you won't void your warranty since you are flashing official firmware. Of course that is just a post on an internet forum and carries no weight. Other than the warranty does it really matter? You can always update using Flashtool.
Yesterday I updated to 8.0 following this thread https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479 and now I have 8.0, my bootloader is unlocked, I have root, adaway, my phone passes safetynet, and most importantly it still works..
There are some subtle differences between N & O that have made it worthwhile. Sorry I can't be of more help, I can only share my positive experience.
Click to expand...
Click to collapse
if you unlocked your bootloader, while you might be if there is an update, you can't just download and apply it from phone. If you're only interested in major android upgrade, this won't be a problem as at most we probably will only got one more android major version update (or none, it will be close to two years after device release).
If you are interested on monthly security update though, this could be a pain to flash manually each month
So if i just install the UK via the xperia flash tool method here (https://forum.xda-developers.com/x-compact/how-to/fingerprint-reader-version-flash-t3470154) , will i get OTA updates for security patches? Or do i have to manually do it every time?
mystycs said:
So if i just install the UK via the xperia flash tool method here (https://forum.xda-developers.com/x-compact/how-to/fingerprint-reader-version-flash-t3470154) , will i get OTA updates for security patches? Or do i have to manually do it every time?
Click to expand...
Click to collapse
Yes, you will receive updates as long as you do not tamper with the bootloader or recovery. If for some reason it doesn't work you can always use flashtool to apply an update. The convenience of the fingerprint reader working far outweighs the inconvenience of having to update a phone with a computer.
I have the ONA19TB002, and it still has old firmware, as I disabled the Wireless Update, due to reports of it installing software on its own. Malwarebytes really doesn't like that product. Is there a good way of getting updated firmware without potentially unwanted programs being installed? I see someone uploaded firmware, but not sure about trusting that either? Is there an Onn, tech support website or contact information? Thank you.
Does the lack of responses mean it's either take a chance with Wireless Update, or take a chance with uploaded firmware?
Thanks
Use the update here in the forum. I've personally used it a couple of times. It's fine.
I got an ONA19TB002 too stuck on build 20190516. Wireless update installed an update once to fix the audio jack but nothing after that. It didn't take the November OTA from the Stock Backups/Images thread and the 'July' OTA while it installed, nothing really changed as far as I can see. How does one flash the full image?
Anyway one how to update this thing?