Is metro/T-Mobile variant getting one UI 2? (A102U) - Samsung Galaxy A10 Questions & Answers

Heya. I read and seen on several sites that the A10e was going to get the One UI 2 update in May of 2020. It's June and I still haven't even gotten the security patch due for May, let alone a Android 10 update. This is on the Metro by T-Mobile variant SM-A102U
Update: I found that the A102USQU6BTE4 baseband of the A102U has gotten the android 10 update, but the ATE5 versions got a security patch instead. Will the ATE5 versions get the update eventually, or can I take the BTE4 version and flash it to the phone through Odin? (I'm assuming that'd obviously be a know). Hopefully I'm posting this in the right place.

Related

January Security Update?

Some reviewers had posted that the January security update was pushed prior to release, but I've had my 5X running since Tuesday and its still on the December patch.
I made sure to manually check for updates just in case and the phone didn't see anything. I'm connected to both data and wi-fi so I'm not sure what is up.
Has anyone received it other than pre-release folks?
fluked said:
Some reviewers had posted that the January security update was pushed prior to release, but I've had my 5X running since Tuesday and its still on the December patch.
I made sure to manually check for updates just in case and the phone didn't see anything. I'm connected to both data and wi-fi so I'm not sure what is up.
Has anyone received it other than pre-release folks?
Click to expand...
Click to collapse
Honor has a BetaClub program that lets users test a new software build before it gets released to everyone. The update with the January Android security patches should be out soon.
honordevice said:
Honor has a BetaClub program that lets users test a new software build before it gets released to everyone. The update with the January Android security patches should be out soon.
Click to expand...
Click to collapse
How can we join this betaclub? Google doesn't return any luck
fluked said:
Some reviewers had posted that the January security update was pushed prior to release, but I've had my 5X running since Tuesday and its still on the December patch.
I made sure to manually check for updates just in case and the phone didn't see anything. I'm connected to both data and wi-fi so I'm not sure what is up.
Has anyone received it other than pre-release folks?
Click to expand...
Click to collapse
I received my phone on Wed. (Feb. 17) from Amazon. It's still on the Dec. 1 Android security patch with no update available.
austenfan said:
I received my phone on Wed. (Feb. 17) from Amazon. It's still on the Dec. 1 Android security patch with no update available.
Click to expand...
Click to collapse
See my thread here >> http://forum.xda-developers.com/honor-5x/how-to/guide-kiw-l24-to-stock-t3318268
Bit of a newbie here, came across this forum when looking at new phones and was quite excited by the idea of being able to play with all that was available in the phone.
So I went and bought a 5x have got my unlock code but have not unlocked it just yet, I am UK based and so have the L21 and just wanted to check that the general consensus is to leave the thing untouched (except for a new launcher and a few apps installed) until I have received or somehow updated to the B140 update.
I couldn't work out in the other thread about returning to stock if the B140 for the Kiwi 21 had actually been released yet, couldn't find any downloads on the Huawei site for the UK.
SaulBee said:
Bit of a newbie here, came across this forum when looking at new phones and was quite excited by the idea of being able to play with all that was available in the phone.
So I went and bought a 5x have got my unlock code but have not unlocked it just yet, I am UK based and so have the L21 and just wanted to check that the general consensus is to leave the thing untouched (except for a new launcher and a few apps installed) until I have received or somehow updated to the B140 update.
I couldn't work out in the other thread about returning to stock if the B140 for the Kiwi 21 had actually been released yet, couldn't find any downloads on the Huawei site for the UK.
Click to expand...
Click to collapse
I'm not sure how I could be more clear that the B140 update is for the L24 only
I just uploaded the latest OTA B140 for the KIW-L24 here >> https://www.androidfilehost.com/?fid=24421527759882720
KIW-L21 Users See post 8 for the files you need (But note the OTA is only for the L24)
Click to expand...
Click to collapse
That's what I thought thanks for confirming. I will wait till my phone updates before I try debloating scripts etc...
Sent from my KIW-L21 using Tapatalk

updating, appears another security update

file size is around 250mgb
build number MRA58K
Android 6.0
2017-03-01 Android security patch level
VS99027A
rsswga said:
file size is around 250mgb
build number MRA58K
Android 6.0
2017-03-01 Android security patch level
VS99027A
Click to expand...
Click to collapse
I received this as well. I went ahead and accepted it. I know they are working on root, but I am probably going to replace the V10 with something else soon anyway. Update went smooth and no issues after. as rsswga stated it looks like it is just a security patch.
whatsinaname said:
I received this as well. I went ahead and accepted it. I know they are working on root, but I am probably going to replace the V10 with something else soon anyway. Update went smooth and no issues after. as rsswga stated it looks like it is just a security patch.
Click to expand...
Click to collapse
I went ahead and updated as well to the new software. Two updates in two months. At least they're paying attention to this phone. For the most part.
I am from India and has LG V10 H961N dual sim verizon model. I don't get any OTA and I used kdz file from link below to update to recent patch.
I flashed using uppercut and it works fine. the build number MRA58K is same for me.
https://lg-firmwares.com/lg-h961n-firmwares/
So:
Given that the likelihood of root not being achieved, I'm wondering the following:
If this update is more specifically related to security, is it conceivable that it could be taken on my rooted phone, or is it tied to a specific version of Verizon/Android OS?

Current T-mobile firmware?

What version firmware are you all running on the S9+ T-Mobile version? I'm still on the Feb security patch and phone shows no updates available. Just making sure I'm not missing anything here.
ARC6 is the latest
hi
cledee said:
ARC6 is the latest
Click to expand...
Click to collapse
Yep,
ARC6 with the March 1 security patch
Wonder If I disabled something via BK Disabler that's not allowing me to dowoad the updates....
Sent from my SM-G965U using Tapatalk
quailallstar said:
Wonder If I disabled something via BK Disabler that's not allowing me to dowoad the updates....
Click to expand...
Click to collapse
No it's not updating my phone either, it just shows no update for me too. And I haven't disabled anything. So I don't know what's up with that
Same here
Wondering if they pulled the update
Running the same ARBG build here, too.
noxarcana said:
Running the same ARBG build here, too.
Click to expand...
Click to collapse
Same here. New s9 plus just bought yesterday. I just checked no updates available. Wonder if they pulled it.
Hopefully the removal of the update has something to do with the v2 bootloader. When you update to ARC6, you can't go backwards from that point, or at least currently. The v1 bootloader in ARBG is a lot more flashing friendly.
jcsww said:
Hopefully the removal of the update has something to do with the v2 bootloader. When you update to ARC6, you can't go backwards from that point, or at least currently. The v1 bootloader in ARBG is a lot more flashing friendly.
Click to expand...
Click to collapse
Unfortunately, this doesn't matter in my case as I have the Snapdragon variant. Jailbreaking Apple devices is easier than dealing with Samsung's BS these days; however, I couldn't give up the ability to expand storage with an SD card.
I've been hearing a lot of people complaining about dropped calls on the ARC6 update. I never experienced it myself while on ARC6 but I'm on ARDA now.
noxarcana said:
Unfortunately, this doesn't matter in my case as I have the Snapdragon variant. Jailbreaking Apple devices is easier than dealing with Samsung's BS these days; however, I couldn't give up the ability to expand storage with an SD card.
Click to expand...
Click to collapse
Mine is a SnapDragon model also. Although based on older information and models. I am hoping we get a V3 bootloader for those who are stuck on v3 that can be upgrade and then downgraded. The Note 8 bootloader is possible to flash backwards for some reason. Because we are on the 845 though, it will probably take a little time for someone to figure out who to get it to successfully flash backward. The call dropping issue on some firmware versions also is a problem that doesn't exist on other firmware variants. I had the call dropping on 1ARC6 but not on 1ARBG. That might have slipped into the firmware with the v2 bootloader. Whatever the reason, the Samsung community has a lot of development and cross-flashing activity that will hopefully get this figured out soon.
I came from a V30, which is much more of a mess to even attempt to flash anything other than what the current firmware is could potentially leave you hard bricked. Outside of Nexus and Pixel devices, I find Samsung in its current state more cross-flashing and mod friendly than some other manufactures. I have never used an Apple device to know how easy or difficult they are to jailbreak or what that means in comparison to what we do with modded, bootloader unlocked, and cross-flashing devices on the Android side. The locked down Apple ecosystem will always keep me away from their platform.
quailallstar said:
What version firmware are you all running on the S9+ T-Mobile version? I'm still on the Feb security patch and phone shows no updates available. Just making sure I'm not missing anything here.
Click to expand...
Click to collapse
Same
March here on mine.
Sent from my SM-G965U using Tapatalk
Received a notification yesterday about a new update version available for download.
Updated and now running the following:
SM-G965U
T-Mobile USE
Baseband version: G965USQS2ARF4
Build number: R16NW.G965USQS2ARF4
Kernel version: 4.9.65-13087505
Service provider SW version: SAOMC_SM-G965U_OYN_TMO_OO_0079
Carrier configuration version: 2.400001
Android security patch level: June 1, 2018
Got my update yesterday as well. Matches what quailallstar shows.

Need Help in Samsung S9+ security Patch Update

Hello I have Samsung S9+ SM-G965F Android 9.0 One UI
Serial No. RF8K20VD8WR
Baseband version: G965FXXU2CRLF
Last Security Patch Level show December 1, 2018.
Is it normal? Upon checking updates it shows device upto date.
Once I had changed the firmware may be last year to get One UI after that I am not able to receive any security update. How I can get the update of One UI 2.0?
Many thanks in advance.
bukhtawar said:
Hello I have Samsung S9+ SM-G965F Android 9.0 One UI
Serial No. RF8K20VD8WR
Baseband version: G965FXXU2CRLF
Last Security Patch Level show December 1, 2018.
Is it normal? Upon checking updates it shows device upto date.
Once I had changed the firmware may be last year to get One UI after that I am not able to receive any security update. How I can get the update of One UI 2.0?
Many thanks in advance.
Click to expand...
Click to collapse
One UI 2.0 isn't OTA yet, see separate thread for trying the beta (although my personal advice is wait a month for the finished version)
On release you'll need to probably download it and install manually, making sure the version you install matches your phones original CSC to re-enable OTA updates.
pinsb said:
One UI 2.0 isn't OTA yet, see separate thread for trying the beta (although my personal advice is wait a month for the finished version)
On release you'll need to probably download it and install manually, making sure the version you install matches your phones original CSC to re-enable OTA updates.
Click to expand...
Click to collapse
agreed with the waiting part. also might want to take the serial out of both of your posts

Refurbished and guess what, messed up firmware

Hello,
I recently acquired a refurbished S9+ and as many other people, I realise now that someone must have been messing around with the internal software. This is my secondary phone so it's no big deal but I would like to understand what was done on it nevertheless, and maybe turning it back to a cleaner state, if possible, and if it has not too many drawbacks.
-apparently, Samsung Pay is not working. It hangs indefinitely on the screen where you must choose the type of security.
-when looking into the Play Store settings, the device is not certified
-WiFi calls apparently are unavailable
-OTA update is not working (nothing happens when I try to check for an update manually. What's more, no information about the last update is available. By the way, the phone software is outdated. (last Android security fix is dated from Feb 2019)
From what I read, it looks like the CSC was modified, right ? Would it be a good idea to change it back to original ? (I may need some guidance about that but we are not there yet) Would such a procedure restore, for instance, the OTA update feature ?
(see pictures attached - there is what is written on the phone's back cover too, if it can help)
Thank you very much in advance. Please tell me if you need some other specific screenshots.
PS : I also bought a Note 10+ from the same refurbisher and it ended up being a Korean model. But the firmware seems clean. I know Samsung Pay won't work in France, WiFi calls either, and I will be stuck in "LTE" 4G instead of 4G+ but at least OTA updating is functionnal (I got an update a few days ago) and honestly ? That's fine with me for the price.
Anyone ?
From what I've read researching on similar issues, the previous owner who messed around with the internal software must've flashed custom firmware on your S9+, and probably tripped Knox (and is why your Samsung Pay app won't work). According to some developers on here, you're able to hide the fact that you've rooted the phone, but I don't think you can un-trip Knox once it's been done.
Prior to your post, I didn't know a single thing about CSC and I'm not sure how it's really relevant when flashing a mobile device (unless it's carrier-related), but I think all that's required when flashing a device is the model number. Luckily, I stumbled upon a thread that is actually your exact, same model! Do what you please with it, and I hope I helped — I'm not a professional, nor am I really knowledgeable about all of this stuff, but I'm trying.
This is the thread I was talking about:
Official Stock Firmware Thread (11 August 2022) - Galaxy S9+ (SM-G965F)
UPDATE (7 APRIL 2022): Samsung has officially declared the Galaxy S9 and S9+ EOL. They will no longer be supported, and FVB4 will most probably be the final build for this device. Latest stable firmware: G965FXXUHFVG4 / G965FOXMHFVB4 /...
forum.xda-developers.com
Oh thank you for the finding, I'll have a look !
Kera Fardd said:
Oh thank you for the finding, I'll have a look !
Click to expand...
Click to collapse
You're welcome! Was it what you were searching for?
Not sure, but I hope it will help me understand the firmware/CSC stuff better
Alright so apparently this phone actually is a SM-965N, judging by what is displayed when booting into download mode.
Unfortunately I only saw this after starting a flashing attempt with Odin and now it's stuck at "system.img" so... I'm gonna let it run a few more hours but...
It's most likely bricked at this point, isn't it ? (edit : interestingly, after I forced-closed Odin and reboot the phone, it was not)
If you ask me I find this kind of "refurbishing" a little bit sketchy to say the least.

Categories

Resources