Database Info

[Q] Just got Shield (32GB), It has 4.4.2, says OTA "1.21" available...

Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc

I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc

Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.

And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc

the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....

Unlocked US LG V20 Updated At Long Last, What's in the OTA?

I couldn't find anything anywhere online about this OTA that I got yesterday on my US996, no record of it ever existing. So I asked LG about it and this was their response. I haven't applied the update yet, but will update this post if I notice anything other than what LG stated. I will hold off for a while on installing it so if enough people want me to capture and share the OTA then I will.
https://www.youtube.com/watch?v=KsD3pGv5cv8

From what I see all I've noticed is the Nov 6 security patch which means blueborne and krack are fixed among other exploits, ARB is still 0 so can be rolled back if wanted for some reason. Cool that it adds rcs support, not that my carrier has support anyway

was there a point for a video? simple screenshot of the conversation would have sufficed

updated, and i can't use my sim card anymore, the phone detected sim card but no signal at all, got some extra buttons in dailer.

ttnduy said:
updated, and i can't use my sim card anymore, the phone detected sim card but no signal at all, got some extra buttons in dailer.
Click to expand...
Click to collapse
As I mentioned in another thread, after I installed the update, it listed "unknown version" for baseband and wouldn't connect to Verizon for a few minutes. Then the baseband version showed correctly and it connected.
Since baseband is a wholly separate CPU and OS, it's not clear what it was updating in the background, but it fixed itself eventually.

alexandero11 said:
I couldn't find anything anywhere online about this OTA that I got yesterday on my US996, no record of it ever existing. So I asked LG about it and this was their response. I haven't applied the update yet, but will update this post if I notice anything other than what LG stated. I will hold off for a while on installing it so if enough people want me to capture and share the OTA then I will.
https://www.youtube.com/watch?v=KsD3pGv5cv8
Click to expand...
Click to collapse
Obviously LG thinks that we don't need to know the details, just that LG has improved the usability and functionality of the phone, that's all we need to know. /s
From what I can tell, it's the same build of android, NRD90M, as before the update. So probably only has google supplied security patches.
As long as LG gives us US996 Unlocked users an Oreo update early next year, I'm OK with them not doing much with the original 7.0 firmware... but definitely security updates more than once per year would have been nice.
The "slower than" or "completely missing" compared to major carriers updates up until this one, has definitely been a disappointment since the factory unlocked version of the phone should be the easiest to get updates pushed out for.

LG Q7+ Update Avaiable

So this morning I woke up to a security update message from T-Mobile. So if your interested they are rolling out a security update this morning. Now I'm actually with Metro Pcs but I recently flashed my device with the T-Mobile variant since it has less bloat ware and just ain't garbage as Metro's firmware. So being that Metro is part of the T-Mobile network I'm assuming you will be receiving it as well.
Now as for anyone ever hoping to require root you might want to block this update as I have just done. As you can see from the picture attached they are not giving you an option as in these updates make it harder and harder for someone to find an exploit or a (back door) as many say to aquire root. As as since it has been mentioned that these devices if and do receive the Android Pie 9.0 update it wouldn't be until late 2019 so til then I'm going to keep exploring and working on finding a way to root this device. For noobies, YES I ALREADY HAVE READ THE ANDROID TECH ARTICLES AND YOU TUBE VIDEOS. The switch in developer options will not unlock bootloader and LG does not have these devices on their list of phones even capable to be unlocked. So til then it's back to the grind.
~~~~FUN IS ILLEGAL

Paranoid "security" is purely meant to stifle open source community activity, nothing else (Maybe someone would need this if worked as CIA/MOSAD spy )

Hey, Funisillegal to turn off the automatic update just the toggle in developer options is enough right?

FullAccessForAll said:
Hey, Funisillegal to turn off the automatic update just the toggle in developer options is enough right?
Click to expand...
Click to collapse
No it's not brotha it will still force update just like clicking the unlock bootloader doesn't unlock bootloader

Funisillegal said:
No it's not brotha it will still force update just like clicking the unlock bootloader doesn't unlock bootloader
Click to expand...
Click to collapse
So how do you turn off automatic updates?

And isnt't enough simply to switch updates off from Android regular settings?
Settings->System->About Phone->Security updates (or somehow similar, watching just on my Polish menu)

Funisillegal said:
So this morning I woke up to a security update message from T-Mobile. So if your interested they are rolling out a security update this morning. Now I'm actually with Metro Pcs but I recently flashed my device with the T-Mobile variant since it has less bloat ware and just ain't garbage as Metro's firmware. So being that Metro is part of the T-Mobile network I'm assuming you will be receiving it as well.
Now as for anyone ever hoping to require root you might want to block this update as I have just done. As you can see from the picture attached they are not giving you an option as in these updates make it harder and harder for someone to find an exploit or a (back door) as many say to aquire root. As as since it has been mentioned that these devices if and do receive the Android Pie 9.0 update it wouldn't be until late 2019 so til then I'm going to keep exploring and working on finding a way to root this device. For noobies, YES I ALREADY HAVE READ THE ANDROID TECH ARTICLES AND YOU TUBE VIDEOS. The switch in developer options will not unlock bootloader and LG does not have these devices on their list of phones even capable to be unlocked. So til then it's back to the grind.
~~~~FUN IS ILLEGAL
Click to expand...
Click to collapse
Is anyone even working on a root for this device? Doesn't seem like it, I have one of these phones sealed in box never opened for the off chance someone picks up the charge and needs a stock firmware to toy around with given the phone was BOGO when I picked it up for my DIGITS line.

So far relying on ISLAND and IceBox, and it yields nice results.
Lg has equiped system with many quite useful and convenient features.
Not needed applications are just frozen.
However waiting for brealing from such utilities as KingoRoot.
So far disabled automatic updates hopefully making would-be exploits available for future versions of KingoRoot.View attachment 4747486

Question Still on November Security patch

I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?

T-Mobile I'd imagine. Just use Pixel Flasher or https://flash.android.com

I joined the beta program

BladeRunner said:
I joined the beta program
Click to expand...
Click to collapse
How is it? Stable enough to daily drive? I was stuck on the Nov. 22 patch as well until I sideloaded via ADB last night.

Nov 1 is the latest Play System Update afaik, at least thats what the QPR shows....

Google is having problems

This is one of those moments where it's not you it's them is actually true and not gaslighting . Play Updates are not rolling out properly

BladeRunner said:
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
Click to expand...
Click to collapse
Seems you are not alone.
T-Mobile is running way behind on Google Pixel security updates
Timely updates are supposed to be a prime Pixel perk
www.androidpolice.com

Yeah I am on December update very annoyed with Google nothing has changed

Deleted

That sucks and should not be the Pixel experience. I would call T-Mobile and ask them why you are on an old update?
I have had decent updates so far but would be rather upset if I had a security update that was older than other OEM as that is part of the reason for getting a Pixel.

Sign up for Beta and you'll get QPR2 Beta 2. In my experience, it is much more fluid and responsive than previous builds. It fixes the scrolling issues and seems to have improved battery compared to the December update.

My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.

Colchiro said:
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Click to expand...
Click to collapse
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.

EtherealRemnant said:
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
Click to expand...
Click to collapse
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.

Colchiro said:
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Click to expand...
Click to collapse
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.

Also mine show November as last play service update (I'm on the beta). Italian unlocked phone

Nov is the latest still for play system. There wasn't a Dec and Jan hasn't rolled out yet

EtherealRemnant said:
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Click to expand...
Click to collapse
There's also the indeterminate minutes, if/when something goes sideways...
This is being delayed for un-branded devices as well, such as mine purchased G-Store direct, based on some sort of carrier-block. I'm tempted to go dig through some dev-docs, to see if I can find this (could be an section not published for most, I suppose), but I figure to what end, mostly.
As you mention, easy side-load, but without knowing why this is being blocked for non-TMo (branded, so not gated by their release of their OTA) devices, it's a gamble of sorts...

I just posted in another thread that I think this is an odd situation. I use an MVNO Boost Mobile that uses T-Mobile and I got the update on the 5th. Maybe I got it before they pulled it? Why would they hold the update back to T-Mobile customers but not the MVNO?

Question Has anyone with an unlocked A53 5G (in the US) received the Android 13 update?

Just as the subject mentions. Curious if it's just me?

Nada. No update. And when I mentioned this on their forum, they deleted the post.
I even tried the thing where you remove the SIM and search for updates then. Didn't make any difference.

Searching with Sammoblie and Frija, only the carrier version(A536U) from Xfinity/Comcast has gotten it in the US.

I don't have it either, what bothers me most is that 13 was released for older A phones including lower priced models already. Is it possible that because this is an enterprise phone (at least in the USA) it requires more time for testing?

pj1980 said:
I don't have it either, what bothers me most is that 13 was released for older A phones including lower priced models already. Is it possible that because this is an enterprise phone (at least in the USA) it requires more time for testing?
Click to expand...
Click to collapse
What bothers me was how quickly Samsung deleted my post on their forum after I asked about this.
It's been like 6 weeks since the same phone in other countries was given this. It's quite annoying.

snark.shark said:
What bothers me was how quickly Samsung deleted my post on their forum after I asked about this.
It's been like 6 weeks since the same phone in other countries was given this. It's quite annoying.
Click to expand...
Click to collapse
Samsung's discussions has a sticky at the top that updates happen whenever (edit: or at least it did before). And that's definitely how it goes for all their devices.
Even Samsung flagships go through silly stuff for updates and Android versions so its not A53 only.
The A53 unlocked has carrier apps on it so its tied to the carrier testing. Why will US carriers release Android 13 for older devices before newer? No idea but that's how their testing is going. They have some reason.
Really, you will get it when you get it. If you just think it won't show up until the year 2721 then it should be easier for you lol.
Its frustrating I know for unlocked to be dependent on carriers. But, waiting, it will at least probably have less bugs so that's fine enough. A buggy device isn't fun at all.
edit: Also A52 appear to be doing better than the A53 in getting Android 13 and listed as Enterprise. So, I don't think Enterprise has anything to do with it.
edit: The end result appears to be what Samsung's sticky said which is updates happen when they happen.

Samsung promised 4 years of updates for this phone so they have about 3 more years to give us android 13.

tmeader said:
Just as the subject mentions. Curious if it's just me?
Click to expand...
Click to collapse
3 Days ago, my phone suddenly shut itself off, and then stuck itself in a bootloop and would not boot again. It's a Samsung A53 5G (ATT&T) running android 12 one UI version 4.1 at the time. After booting into safe mode and wiping application config data, it still would not come out of safe mode until I factory reset it and connected it to a wifi network.
Finally after all of this BS, I got it to boot normally, but then, as if by magic, my phone was running Android 13 UI Version 5.0!
WTF!?
So I spent an entire day recovering my bank accounts, cashapp, applications, and various accounts, and chalked this pain in the ass up to the game...
And then this morning, it ****in' happened again.
I'm done with Samsung. This phone has been a $500 piece of **** since day 1. It's not even 3 months old yet. Samsung has gone from the most badass manufacturer of android devices, straight to the bottom of the abyss in terms of quality.
The Bloatware they send with these devices now should be unlawful. The amount of YOUR resources they use to track every single thing you do, every place you go, every dollar you spend is unfathomably creepy and discomforting.
Do yourself a favor and get comfortable with 12. because 13 is an even bigger piece of ****, and in my case, it has totally wrecked my phone twice in 3 days now.
Do yourself an even bigger favor, and throw your samsung into the bottom of the ocean and go buy yourself an IPhone. I'm really sad about the way Samsung has turned out. I'm even more sad about the way Android has gone down the drain. And Google has turned into the world's most powerful creepy stalker with Facebook a close 2nd.
I think if people actually new just how intrusive these tech companies have become, they'd stop using them altogether. There needs to be new and better privacy regulations and trackers and spywares and metadata miners and these 'ad targeting' programs and applications should be illegal.

ImMrMyagiLafAtMe said:
3 Days ago, my phone suddenly shut itself off, and then stuck itself in a bootloop and would not boot again. It's a Samsung A53 5G (ATT&T) running android 12 one UI version 4.1 at the time. After booting into safe mode and wiping application config data, it still would not come out of safe mode until I factory reset it and connected it to a wifi network.
Finally after all of this BS, I got it to boot normally, but then, as if by magic, my phone was running Android 13 UI Version 5.0!
WTF!?
So I spent an entire day recovering my bank accounts, cashapp, applications, and various accounts, and chalked this pain in the ass up to the game...
And then this morning, it ****in' happened again.
I'm done with Samsung. This phone has been a $500 piece of **** since day 1. It's not even 3 months old yet. Samsung has gone from the most badass manufacturer of android devices, straight to the bottom of the abyss in terms of quality.
The Bloatware they send with these devices now should be unlawful. The amount of YOUR resources they use to track every single thing you do, every place you go, every dollar you spend is unfathomably creepy and discomforting.
Do yourself a favor and get comfortable with 12. because 13 is an even bigger piece of ****, and in my case, it has totally wrecked my phone twice in 3 days now.
Do yourself an even bigger favor, and throw your samsung into the bottom of the ocean and go buy yourself an IPhone. I'm really sad about the way Samsung has turned out. I'm even more sad about the way Android has gone down the drain. And Google has turned into the world's most powerful creepy stalker with Facebook a close 2nd.
I think if people actually new just how intrusive these tech companies have become, they'd stop using them altogether. There needs to be new and better privacy regulations and trackers and spywares and metadata miners and these 'ad targeting' programs and applications should be illegal.
Click to expand...
Click to collapse
That's not the experience of most people. Since you bring up Apple as if that will help you avoid this when it can happen there too: https://myphotoyear.com/ios-16-update-goes-wrong/
Its just a fact of life.
More or less it could be improved or solved by multi-OS versions at the same time (such as dual boot on a computer), slower major OS versions, etc. This is not how Google or Apple thinks though.
To add, you can of course improve loss of data by using system backup and also backing up your stuff separately. Though Android still isn't perfect there.
Of course, if you see an update, avoiding updating for some months might also help though not ideal.
edit: For instance you could have used the Samsung restore which may be presented on first use setup or even manually done in Settings > Accounts and Backups > Restore which will restore much if you used the online backup or backup to sd card. Some apps and data will be missing if apps don't support it, etc. Unfortunately, it seems to only offer one backup at least online so any backup on the account since might have destroyed it.
edit: using that and backing up to sd card includes 10GB of stuff on my phone whereas the online is suggested as 2GB (it backs up files and also eg debug built from source apps). So, if you want the best, it may be what you should do from now on. Then restore it if need be. Still, up to apps to support backup individually. Make sure to run it weekly or something.
Also, I know you're pissed about that. Try not to be pissed with me lol. Thanks.

I'm thinking we're in for weeks, or months, more wait. We haven't even gotten a January Security Update.

Just received the Android 13 (One UI 5.0) update last night on my unlocked phone. Also includes the Jan 2023 security update. Looks like they just made the January cutoff

Hmm I have unlocked a53 on t mobile, I checked for updates today and it said there were none.

I received the update today for Android 13 including dual sim support.

I been checking my A53 unlocked running on Visible every week since Christmas for an update. Today it found the Android 13 UI 5.0 update. downloading it now.
How is the new version? any bugs found?

ok, once my phone updated and rebooted now I am no longer connecting to 5G. I've rebooted a few times and nothing has changed. I'm stuck back on 4G.

tmeader said:
Just received the Android 13 (One UI 5.0) update last night on my unlocked phone. Also includes the Jan 2023 security update. Looks like they just made the January cutoff
Click to expand...
Click to collapse
5 days after your post (6 since you got the update), with daily checking, and it's still a No for me.

My A53 arrived this morning and upon turning it on, my device had a lot of firmware updates waiting for me. I just updated to Android 13 not too ago along with January's Security patch.
I happen to live in the US, use T-Mobile, and I'm using the international version with dual SIM support.

snark.shark said:
5 days after your post (6 since you got the update), with daily checking, and it's still a No for me.
Click to expand...
Click to collapse
Another 3 days...
Still no Android 13 update.
I may wind up going to the Samsung service location in my area. This is ridiculous.

snark.shark said:
Another 3 days...
Still no Android 13 update.
I may wind up going to the Samsung service location in my area. This is ridiculous.
Click to expand...
Click to collapse
They do rollouts on top of things.
You could of course use a sim from a different carrier that has the upgrade available and do it that way. Might just get it immediately or still not. Then switch back. That is a possible workaround.
Of course, if you see a signed image for download for Android 13 for your carrier. That might work too even though it still is a wait for it to show up that way.
I don't know if there's any other way here because of the CSC. It would be interesting to know if a Samsung service shop would do it for you. I can't imagine they would.

Received the update today. Seems to run faster.