I just got this phone, however I realized it was running on Android 11, not there recent Android 12 that came out. I checked and it's still saying it's updated but it isn't. The CSC code is TMK/TMK/VZW. The base version is G975USQU5GUCH, which is a Verizon/Comcast update. What should I do? The phone boots up with the Metro By T-Mobile logo, which is right but it doesn't receive updates.
Updates are patches for already installed Android, in your case Android 11. Updates get rolled out by OEM if they deem it necessary.
I have a small idea on what might be happening
The phone was using a software the carrier never used so when it became from what it was to TMK, they can't find updates to configure it. Is it possible to flash the next update with the correct CSC and it will configure it right?
Also the update screen is different
Related
Hello there.
I purchased my G4 in June or so of last year, and can't seem to get it to work with OTA updates. Phone is currently on 5.1, Kernal 3.19.49, Build LMY47D, Software version H81010e, Security software version MDF v1.1 Release 4. I have never attempted to flash or modify the phone, so it's been bone stock since the day I bought it.
I was out of the country and away from OTA updates from October 2015-March 2016, and since returning I havn't been able to get OTA to register an update is available using either the "Check for Updates" in Android, or LG Bridge on Windows. I didn't really put too much thought into it because of all the issues MM has/had, but now that Wi-Fi calling is available I'd really like to be able to update.
What would my best options be for getting the phone current and up to date with AT&T? I'd really like to avoid dealing with their repair services unless there is a good reason to go that route.
Thanks!
Update
Just in case someone finds this down the road with a similar problem, here's what I did.
http://forum.xda-developers.com/att-g4/general/att-h810-to-stock-guide-tot-method-t3248532
I followed that guide and manually updated from software version H81010e to software version H81010o. As soon as the software was updated, I checked for updates in settings as per usual and it immediately recognized and downloaded the OTA update from AT&T. Seems getting behind on software updates while out of country was preventing me from downloading new versions of Android.
Hey
My phone showed a software update available this morning, but I checked Samsung's website and it doesn't list a change log entry for it:
My S8+ is currently an unlocked G955U1 at version CRB9. Does this new update bring anything useful or is it just Samsung releasing a quick "update" to block a discovered bootloader exploit?
April Security Update
Aganar said:
My phone showed a software update available this morning, but I checked Samsung's website and it doesn't list a change log entry for it:
My S8+ is currently an unlocked G955U1 at version CRB9. Does this new update bring anything useful or is it just Samsung releasing a quick "update" to block a discovered bootloader exploit?
Click to expand...
Click to collapse
I'm sure there's more under the hood changes and things that apply to other carriers but here's Verizon's changelog for the update:
Software Version: R16NW.G955USQU3CRD4
Android® Security Patch Level: 2018-04-01
This software update brings the latest Android security updates and provides bug fixes on your Galaxy S8+.
Fixes an issue that caused the Samsung keyboard to crash or disappear after updating to Android Oreo.
Prevents the device from continuously restarting after updating to Android Oreo.
Fixes an issue where Windows 10 computers crashed when tethered to a S8+.
Repaired an issue that prevented video calls from being put on hold when connected to the Verizon Wireless and AT&T networks.
Click to expand...
Click to collapse
Aganar said:
My phone showed a software update available this morning, but I checked Samsung's website and it doesn't list a change log entry for it:
My S8+ is currently an unlocked G955U1 at version CRB9. Does this new update bring anything useful or is it just Samsung releasing a quick "update" to block a discovered bootloader exploit?
Click to expand...
Click to collapse
LUCKY YOU, note 8 must be a relic, yet to get Aprils update.
I have been working on my mom's Galaxy S8+ trying to fix this issue and can't for the life of me get anywhere. She purchased a new Galaxy S8+ from Swappa and after a month or so have it, started having issues with software updates. She worked with AT&T and Samsung and since the phone was still under warranty, they swapped it out for a new one from Samsung. Well, the new phone is doing the same exact thing so at this point we know it isn't a device specific issue.
Here's what happens:
1. Start up phone and wait about 5 minutes
2. Alert comes in that a software update is available
3. Tape Update now
4. Phone reboots and installs updates - states that update was installed successfully.
5. Wait 5-10 more minutes and get another alert that a software update is available.
6. Repeat 2-5 until you drive yourself insane.
At this point I have tried wiping the cache, installing the update and shutting the phone off and again, wiping the cache, turning off OTA updates. Nothing seems to work. At this point I am tempted to download Android 9.0 and do a manual install using Odin. Is that not recommended?
Currently the phone is running the following:
Samsung G955U
Android Version: 8.0.0
Samsung Experience: 9.0
Kernel: 4.4.78
Build: R16NW
Android Security Patch level: August 1, 2018
EDIT: It looks like this may be normal, actually. After checking versions again after yet another update I noticed that the security version went to October 1, 2018. After that it updated again and then went to November 1, 2018. It looks like I just need to keep doing this until it gets through them all.
Got this phone on eBay a few weeks ago. I love it but when I set it up, it thinks it has the latest updates.
Click "Check for Updates"
"Your system is up to date"
Android version 9, Security patch level December 1, 2018
Software version is Q910UM25a
Using a Koodo sim. Tried a Fido one too. Same thing.
Tried the LG Mobile Support tool, get a message saying "Your device has the latest software available from the LG Mobile Support Tool.
Anyone have any ideas? Thanks!
Normal versions are Q910UM20x not 25. Usually LG name 25,29,28 beta firmwares. You need flash 20 full(full OTA) firmware. But where find fullflash i dont know.
I seem to be in the same boat. Picked up two of these previous display model devices.
One is running Q910UM11c (Android 8.1.0, September 2018 patch level) and prompting for an update to 25a, the other is already running 25a.
I'll attempt to capture the OTA on the one still running 11c. I doubt it will help, but it can't hurt.
EDIT: I'll include the build build numbers here just in case they're useful for anything.
Q910UM11c, build OPM1.171019.026
Q910UM25a, build PKQ1.180904.001
skyblaster said:
I seem to be in the same boat. Picked up two of these previous display model devices.
One is running Q910UM11c (Android 8.1.0, September 2018 patch level) and prompting for an update to 25a, the other is already running 25a.
I'll attempt to capture the OTA on the one still running 11c. I doubt it will help, but it can't hurt.
EDIT: I'll include the build build numbers here just in case they're useful for anything.
Q910UM11c, build OPM1.171019.026
Q910UM25a, build PKQ1.180904.001
Click to expand...
Click to collapse
Same boat, mate! I on Q910UM25a, build PKQ1.180904.001 with Dec 2018 security patch. Wish I could find a way to move to regular build. But information is almost non-existent on this device.
So I downloaded the latest firmware image (WW-31.0810.1226.154-1.1.213-2303) and copied it to the root of the phone and rebooted, but instead of detecting the update file as usual and prompting to update, nothing happened. Phone currently has the last month's update to Android 13 (WW-33.0210.0210.200) and is rooted/bootloader unlocked.
Is the current month update meant for Android 12 only? Now I notice the version number is less than the one I have, and the changelog just says it has the Google security patch for May.