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

lollipop vs kitkat

am really tired,when i updated to lollipop program take alot of ram space and make some app to re open it again when i returned to it,not save it,so i returned to kitkat but the battery drain fast about 1% every minute.
that crazy so what to do? am not expected that from note 4.
advice plz with abuild version or area which work good,no matter kitkat ot lollipop.
thanks

I also returned back to Kitkat & after returning I reset my Note 4 (factory reset) , and every thing working fine
Lollipop is full with bugs so maybe my next update will be Android M when it will come, I believe Lollipop is a no go with a lot of bugs and issues even the coming 5.1.1

one-option said:
I also returned back to Kitkat & after returning I reset my Note 4 (factory reset) , and every thing working fine
Lollipop is full with bugs so maybe my next update will be Android M when it will come, I believe Lollipop is a no go with a lot of bugs and issues even the coming 5.1.1
Click to expand...
Click to collapse
what is your product name and which baseband version u on ?
IR work with u?
my phone is N910H

My Note 4 n-910G is working good on lollipop. I'm on stock non-rooted 5.0.1 and i cant wait to get 5.1.1 (M would be heaven but i'm not holding my breath for it). Lollipop for me is quite fast and just tiny annoying bugs, nothing major. Kitkat 4.4.4 was blazing fast for me before. It's suffered a little after i flashed L but i wont go back now. I'm lucky i haven't got the battery issues i keep hearing about, or those lags/bugs. That would make me throw the phone across the room.
Here's to Samsung to give it's best flagship of late 2014, early 2015 Android M

LightspeeDLee said:
My Note 4 n-910G is working good on lollipop. I'm on stock non-rooted 5.0.1 and i cant wait to get 5.1.1 (M would be heaven but i'm not holding my breath for it). Lollipop for me is quite fast and just tiny annoying bugs, nothing major. Kitkat 4.4.4 was blazing fast for me before. It's suffered a little after i flashed L but i wont go back now. I'm lucky i haven't got the battery issues i keep hearing about, or those lags/bugs. That would make me throw the phone across the room.
Here's to Samsung to give it's best flagship of late 2014, early 2015 Android M
Click to expand...
Click to collapse
Have you checked your camera pictures ???
Observe the viewfinder, the way everything looks, it will all show like some paint effect compared to the pictures that came sharp while on kitkat.
Please do compare pictures when on kitkat and after lollipop update.
I have created a new thread on it. Many have not observed their camera picture quality post update.

ok... now i'mma worried. will try it

bigheart90 said:
am really tired,when i updated to lollipop program take alot of ram space and make some app to re open it again when i returned to it,not save it,so i returned to kitkat but the battery drain fast about 1% every minute.
that crazy so what to do? am not expected that from note 4.
advice plz with abuild version or area which work good,no matter kitkat ot lollipop.
thanks
Click to expand...
Click to collapse
Ok go back to lollipop and flash the 5.1.1 kuybi rom. It's fast and smooth. It's been debloated and is very good on battery life. It's much better then any of the other lollipop and kitkat. In fact I would go as far to say it's the best lollipop build here on xda for now.

Clarification for XT1644(US, Verizon) and Nougat

I have read so many threads about Nougat that I have gotten myself a bit confused, I think.
I am running an XT1644 in the US on the Verizon network. My device has an unlocked bootlader and is running stock software, albeit rooted (i like adaway), build number MNPJ24.139-48.
I am quite interested in trying out some of the Nougat-based ROMS, and each of them suggest flashing the soak test first. As I read the threads for the soak test, they seem to suggest that they are all for India or variants other than mine.
At the risk of making myself out to be an idiot, I'd like some clarification/confirmation as to how I can get the correct soak test for my variant. I have no issue with following directions, however, the sheer amount of directions and variations for this model just make me want to be extra cautious before flashing.
Thanks

Don't do it. The soak test was not for our models and it can have issues like missing IEMI or WiFi. Verizon being CDMA as opposed to GSM, you can get in even worse problems.
Ah, and once you flash the N bootloader, you can't go back to the MM one. Reverting to MM will be incomplete and with possible issues. Some people report success, some lost their radio.
You have the stock firmware, there are also available .49 and .64 versions. I have rooted too my G4 Plus and didn't receive the OTA updates anymore.

SoNic67 said:
Don't do it. The soak test was not for our models and it can have issues like missing IEMI or WiFi. Verizon being CDMA as opposed to GSM, you can get in even worse problems.
Ah, and once you flash the N bootloader, you can't go back to the MM one. Reverting to MM will be incomplete and with possible issues. Some people report success, some lost their radio.
You have the stock firmware, there are also available .49 and .64 versions. I have rooted too my G4 Plus and didn't receive the OTA updates anymore.
Click to expand...
Click to collapse
Thank you. This is what I was thinking, but the "tinkering" side of me was itching and I needed the voice of reason to help solidify the decision to wait

The .64 update for the MM works fine on my phone, but I am on ATT network (GSM) so... Idk for Verizon.

myk.robinson said:
Thank you. This is what I was thinking, but the "tinkering" side of me was itching and I needed the voice of reason to help solidify the decision to wait
Click to expand...
Click to collapse
I have the XT1644 on T-Mobile and I'm using a 7.1 ROM. But I never updated my bootloader from MM I just flashed CM 14 and everything still works. The only minor issue I've come across is that it will only allow me to set 1 fingerprint. However, it says every fingerprint fails but I'm still able to use them to unlock the device. So it's apparently just a weird bug. My advice, make a good backup and try either beanstalk 7.1, Xperience 7.1 {my current ROM} Or really any of the others. I've flashed all of them and haven't had any issues. And now there's dual boot so you can always keep one MM ROM and one N ROM on your phone.
---------- Post added at 02:32 AM ---------- Previous post was at 02:30 AM ----------
I have the XT1644 on T-Mobile and I'm using a 7.1 ROM. But I never updated my bootloader from MM I just flashed CM 14 and everything still works. The only minor issue I've come across is that it will only allow me to set 1 fingerprint. However, it says every fingerprint fails but I'm still able to use them to unlock the device. So it's apparently just a weird bug. My advice, make a good backup and try either beanstalk 7.1, Xperience 7.1 {my current ROM} Or really any of the others. I've flashed all of them and haven't had any issues. And now there's dual boot so you can always keep one MM ROM and one N ROM on your phone.

New firmware 4.4.2 03/2017 BTU (UK) Woot Woot!

Yep, today XAR firmware update for kitkat us been released. It has updates and patches to fix known bugs and issues as of 02/17.
It is the most stable and secure kitkat available for our wifi note 8.0.
I am downloading now, but will be waiting for the BTU UK variant to be released, as it may have even later updates, and already set fir 13 channel wifi. Yep I be a lazy base - tard.
Its here! Galaxy Note 8.0 (WIFI) GT-N5110 BTU N5110XXSDQD1 Android 4.4.2 03.04.2017 1321607
http://samsung-updates.com/device/?id=GT-N5110

gooberdude said:
Yep, today XAR firmware update for kitkat us been released. It has updates and patches to fix known bugs and issues as of 02/17.
It is the most stable and secure kitkat available for our wifi note 8.0.
I am downloading now, but will be waiting for the BTU UK variant to be released, as it may have even later updates, and already set fir 13 channel wifi. Yep I be a lazy base - tard.
http://samsung-updates.com/device/?id=GT-N5110
Click to expand...
Click to collapse
FYI - I am based in the UK and my Note 8.0 has very surprisingly updated to 4.4.2 - first update in ages and very odd that it should be Kitkat and not something more up to date.

IMO, i am happy with each update of kitkat. Since the end of jelly bean, google has bollocks upped with each version.
Finally after a few years trying to get kitkat just right, I am able to. Now with the latest update, I am sure the few issues I still deal with will be corrected and finally have a smooth kitkat.
Can't say that for LP, MM, and New-guts. New is not better IMO if it is wonky and filled with security flaws. Plus I don't see any improvement across the board over kitkat. Kinda like do peeps like dealing with cheeky google? I just don't understand them, as much as they don't understand me. HA!

I didn't think about how long these file hosts take... so I recommend to use SamFirm to download your firmware. It is fairly new, and I suggest searching online for sites to assist with setup and function before finding a download. That is why i do not have a link or have posted a download attachment.

Small list of still active vulnerabilites after being fully tested.
Media server, Serialization, and stock browser.
I assume we may see another release of updated kitkat firmware late next year.
It does not bother me, having only two issues active. As for stock browser, who uses it anyway? I don't!

Why are you so happy with a 4.4.2 release of kit kat? Our Note 8.0's could easily handle Nougat...Right? So... help me understand, Why I with an ATT sgh-i467 should be content with my update, but not upgrade to something more.

rmkblades said:
Why are you so happy with a 4.4.2 release of kit kat? Our Note 8.0's could easily handle Nougat...Right? So... help me understand, Why I with an ATT sgh-i467 should be content with my update, but not upgrade to something more.
Click to expand...
Click to collapse
If you're really dependant on your Note 8, you could upgrade to a Tab A with S Pen. These are currently running 6.0.1. I doubt it'll get Nougat, but maybe Samsung will release the S3 in a 8" form factor...

rmkblades said:
Why are you so happy with a 4.4.2 release of kit kat? Our Note 8.0's could easily handle Nougat...Right? So... help me understand, Why I with an ATT sgh-i467 should be content with my update, but not upgrade to something more.
Click to expand...
Click to collapse
Because It works, no issues, and not effected by security issues since LP.
Also I have customised my 4.4.2 to be more robust like a tab 4, without relying on a customized build with issues.
So far I am the only one with a truly functional customised firmware that I am happy with.

gooberdude said:
Because It works, no issues, and not effected by security issues since LP.
Also I have customised my 4.4.2 to be more robust like a tab 4, without relying on a customized build with issues.
So far I am the only one with a truly functional customised firmware that I am happy with.
Click to expand...
Click to collapse
Any chance you would be willing to share the firmware?
?

rmkblades said:
Why are you so happy with a 4.4.2 release of kit kat? Our Note 8.0's could easily handle Nougat...Right? So... help me understand, Why I with an ATT sgh-i467 should be content with my update, but not upgrade to something more.
Click to expand...
Click to collapse
rmkblades said:
Any chance you would be willing to share the firmware?
Click to expand...
Click to collapse
I can't due to limits placed by ROM developers. As i had to mix 5 different ROMs to obtain what I have.
You can get a nice look by using the system ui. Though to get chrome to close when its tab closes, stock S5 libs have chrome customisations lib and some chrome cast drivers.
Plus some system apps to make gallery more robust.
I gave up on spen menu, as it did not bring much versatility since I removed stock browser because of it being unsecured with malicious scripts, and scrap book with smart clip just eat too much resources for what they are.
Can't remember which ROM I grabbed a cool one off flashbarservice app. The drawer is like the jelly bean version with a pull out tab and single row. Plus the short cuts are mini.
Using the tab 4 touchwiz and keyboard (that has left and right cursor control), though you loose automatic handwriting mode when spen is detached. It now becomes manually switched with the settings key.
I swapped out a secsettings app to allow access to default applications, as Samsung killed it in 4.4.2 for Note 8.0.
I enabled color blind, interaction control, grey scale, and accessibility shortcut menu. Though I can't have the shortcut menu activate or deactivate without a reboot.
Though the i467 has the features in the stock ROM, so obtaining the latest AT&T ROM, you can copy the system apps to allow some cool accessibility features developers over looked.
If I had permissions to allow copying and distributing custom apps and a few custom libs, i would as a complete ROM. But that is only half of it. I am not an android developer, and have no tools to properly create a flashable ROM to distribute.

Moto G5 Plus Software Update

My Moto G5 Plus is telling me that my software is up to date, yet it's still running Android 7.0, but more importantly the security patch level is 1/1/17. I don't know about major OS updates, but there MUST be at least some updates out there that I'm not getting. Can someone link me to somewhere where I can find a .zip files for all OTA updates, so I can just flash the update and then flash Magisk again to retain root? Thanks!

You are probably not receiving OTA updates since you've rooted your phone, right? There was no major updates but there was few security patches this year. Which model exactly you have? That's gonna help in providing you correct links...

I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?

nlinecomputers said:
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
Click to expand...
Click to collapse
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.

acejavelin said:
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
Click to expand...
Click to collapse
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.

nlinecomputers said:
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
Click to expand...
Click to collapse
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.

acejavelin said:
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
Click to expand...
Click to collapse
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?

I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?

nlinecomputers said:
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
Click to expand...
Click to collapse
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
FamilyGuy0395 said:
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
Click to expand...
Click to collapse
Sort of... OTA files can only be flashed on a pure stock system, no root, no TWRP, no Xposed, nothing changed in system, no removed packages, etc. If the OTA script even detects that /system was ever mounted R/W it can fail (I don't know if Moto goes that far).
To flash an OTA you must restore your stock ROM completely (/system, /boot, and any other system level partitions), and restore stock recovery, and all versions must match or the OTA script will crap out with an error.
The OTA files are out there, on this forum in various threads... you can find them along with instructions on how to apply them to rooted and stock systems.

acejavelin said:
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
Click to expand...
Click to collapse
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?

nlinecomputers said:
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
Click to expand...
Click to collapse
Oh yeah... Moto's level of doing what the carriers "recommend" or whatever you want to call it, is ridiculous lately.
Good example is Nougat for the Moto X Pure Edition, if you are on Sprint or US Cellular you got it 2 months ago, but Verizon, AT&T, and T-Mobile users still haven't seen it. Except many users have figured it out, pop in a Boost Mobile SIM (not even activated) and it will grab the update almost immediately, let it apply, then swap your original SIM back in and enjoy some Nougat goodness. However that device never had a specific version for a certain carrier. Still today probably 80% of users of that FLAGSHIP device still haven't gotten an update that we know was completed in June/July, due to "partner approvals" or some such BS.
All these updates still come directly from Moto and their servers, but they are doing what the carriers tell them and only allowing it to certain devices... This has vaguely been admitted to by the mods on the official Lenovo support forums.
Honestly, many smaller brands with a history of poor update frequency get better update support than Moto's these days... My son's Axon 7 Mini already has 7.1.1 with the September update for BlueBourne, he got it the third week of September, and gets on every 3 months like clockwork. My faith in Moto is diminishing quickly, I gave them the benefit of the doubt on my last two (Moto X Pure Edition and Moto G 2015) because they were kind of transitional device during the Google-Lenovo switch over, and although my Moto G5 Plus is supported a little better I believe it is just because it is newer and not because Moto got better.
Chances this will be last Moto device? Let's just say this could be my last Moto device, and I have been a big Motorola fan for many years.

@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.

Can anyone link me where to find OTA updates for Moto G5 Plus and, if necessary, instructions? I don't see why the instructions would be any different from the OnePlus 5, other than Motorola making it harder on purpose.

FamilyGuy0395 said:
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Click to expand...
Click to collapse
Never said it was true for every phone or manufacturer, but that is the way it is with Moto devices... You cannot flash an OTA with TWRP, the script checks (among other things) the recovery and will fail if it doesn't have the correct signature, same with the modems, bootloader, partition table, and things in /system. Moto OTA updates are VERY picky and will fail at the drop of a hat on a device that is not purely stock.
The only work around, that works in SOME cases with Moto devices, is using FlashFire by Chainfire, but that is hit and miss, depends on what is updated.

There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...

Karlinski said:
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Click to expand...
Click to collapse
Do you have a link to this thread? I am curious how the modems, partition table, and bootloader updates are handled since TWRP doesn't have the correct signature to write to these partitions. I can see where it could maybe update the boot and system partitions if they were extracted from the ROM, even if they are differential deltas, but my guess is that a "TWRP flashable" OTA is mearly an extract of a blank device's boot and system partition or just he changes, and packed into an OpenRecovery script, and not the "real" OTA file.

https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616

Karlinski said:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Q9Nap said:
Do NOT attempt to apply standard OTAs over these builds; they will fail.
Click to expand...
Click to collapse
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.

acejavelin said:
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
Click to expand...
Click to collapse
The TWRP flashable stock builds DO upgrade the modem.
As stated in the OP, the only partitions NOT upgraded are gpt and bootloader.
I didn't omit these partitions because they can't be written; I omitted them to prevent potential issues for people who really don't know what they're doing.
Disabling dm-verity is required due to some partitions unavoidably losing their oem signatures during the conversion process.
Disabling force encryption is practically required, as TWRP seems buggy with it enabled.
The intended purpose of these builds is to provide a dead simple (and safe) way for users to return to stock.
I have linked useful tools at the bottom of the OP for those interested in making their own modifications to these stock builds.
Hope this helps :good:

Q9Nap said:
Hope this helps :good:
Click to expand...
Click to collapse
It does actually, thank you... Obviously I have a lot to learn about the differences between current devices and older Moto devices I am used to working.