Database Users

Security warning for all Note 10.1 devices

As many of you know, all devices that have a Exynos processor have a security hole, called EXYNOS EXPLOIT.
Basically, this security hole allowes apps to have complete access to everything on your device.
For more information on this security hole, click:
http://www.google.com/search?q=samsung+exynos+exploit
Samsung has released new firmware for exynos devices, these firmwares close this security hole.
For your own security, every Note 10.1 should change to the latest 2013 firmware.
2013 firmware has a code that ends with M** for example:
N8010XXUCMA5 (4.1.2)
N8000XXCMA1 (4.1.2)
N8013UEUCMA3 (4.1.2)
You can get the newest firmware on samsung-updates.com and samfirmware.com.
Firmware on these sites is official Samsung firmware from Samsung Kies.
About country versions and OTA updates:
Experience shows that the waiting time for your country firmware version or an OTA update for your country depends on the priority your country has for samsung (waiting time of 1 day, many months or possibly never get an update for your country).
Samsung firmware for the Note 10.1 includes all languages and is almost identical in all country versions (with exception of the China version).
Also the Taiwan version offers all languages at setup. You just have to select Samsung Keyboard in your language version in settings and the firmware will be like your own country version.
You should backup all your data/apps/settings with something like Titanium backup, install the new firmware and then do a factory reset.
You can also not do the factory reset, but you may have compatibility problems.
To install firmware on your Note 10.1 you need Odin.
You can download it here:
Samsung Odin3 v1.85 for Note 10.1
http://www.mediafire.com/?8qv95ije5gd2vjk
Samsung Odin3 Manual for Note 10.1
http://www.mediafire.com/view/?7ueokoji11965ao
Direct links to the firmwares:
4.1.2 Germany for GT-N8010
http://www.hotfile.com/dl/190278866/d6b1373/N8010XXUCMA5_N8010OXACMA5_DBT.zip.html
4.1.2 Germany for GT-N8000
http://hotfile.com/dl/189226269/e9c...-GT-N8000-DBT-N8000XXCMA1-1357533079.zip.html
4.1.2 USA for GT-N8013
http://hotfile.com/dl/189276711/f83...GT-N8013-XAR-N8013UEUCMA3-1357740396.zip.html

legion1911 said:
As many of you know, all devices that have a exynos processor have a serious security hole, called EXYNOS EXPLOIT. Basically, this allowes apps to have complete access to everything on your device.
Samsung has released new firmware for exynos devices, these firmwares close this serious security hole.
Every Note 10.1 should change to a firmware with code that ends with M** (that M means 2013), for example:
N8010ZSBMA1
N8000XXCMA1
N8013UEUCMA3
For GT-N8010
http://hotfile.com/dl/188458272/712...-GT-N8010-BRI-N8010ZSBMA1-1357196432.zip.html
For GT-N8000
http://hotfile.com/dl/189226269/e9c...-GT-N8000-DBT-N8000XXCMA1-1357533079.zip.html
For GT-N8013
http://hotfile.com/dl/189276711/f83...GT-N8013-XAR-N8013UEUCMA3-1357740396.zip.html
You can get the newest firmware on samsung-updates.com and samfirmware.com.
They are not mirrors, they often have one rom, that the other one does not have.
Click to expand...
Click to collapse
That's the build for 4.1.2.

Stoney60 said:
That's the build for 4.1.2.
Click to expand...
Click to collapse
Which only Germany has, as far as I know?
Officially, anyway. I'm using redemption at the mo, which I think uses the German 4.1.2... not sure though.

Stoney60 said:
That's the build for 4.1.2.
Click to expand...
Click to collapse
No. It is not related to the android version. the patch is in the boot image. Also the 4.1.1. ending with M** is fixed.

legion1911 said:
No. It is not related to the android version. the patch is in the boot image. Also the 4.1.1. ending with M** is fixed.
Click to expand...
Click to collapse
Pardon me, but:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Stoney60 said:
Pardon me, but:
View attachment 1654212
Click to expand...
Click to collapse
What you posted does not contradict me. you refered to 3 roms and say they are 4.1.2. They are not all 3 4.1.2. The fix is in the boot image, not in android. If you take your 4.1.2 and change only the boot image, you are again with security hole.

Like this
Sent from my SPH-D710 using xda app-developers app

legion1911 said:
No. It is not related to the android version. the patch is in the boot image. Also the 4.1.1. ending with M** is fixed.
Click to expand...
Click to collapse
I'm saying, I've been to both Samsung-update.com and Samfirmware.com, neither of which have the updates you have posted in the op. The hotfile links you posted take you to a d/l site that has the N8013EUCMA3 firmware that is the same as the 4.1.2 build number you can see in my screenshot.
---------- Post added at 08:54 PM ---------- Previous post was at 08:50 PM ----------
gronimo21 said:
Like this
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yup, just like my screenprint

will there be an official update?

Legion, can you update the first post with some more specific advice. Is this THE ota exynos update? Are Sammy going to release this OTA or is this it? Is this image for ALL devices irrespective of country. How it affects region specific devices. Also, flashing details etc.
I was under the impression that Bri was for Taiwan specific devices only! But I read somewhere that this update can be flashed regardless of region.
I think a little more advice on the first post would help users here.
I'm downloading now and will update as soon as, but a lot of users won't download based on the first post being unclear.
Riki

As per I know all patches will be release via OTA, the US 4.1.2 rom is already patch the German 4.1.2 rom has received the patch via OTA. Others I am not aware of but yes it will come out in form of an OTA. The OTA should be around 10 - 20 MB

So this download is NOT needed then? Is there any point downloading the ROM Legion has linked to?

The roms he has linked are stock firmwares for regions like Germany, US which have already received the patch. If you are on stock rom for your country then wait you will receive the OTA soon, if you are on a stock rom from another region then you will not so it makes sense to flash the German rom.
Also a question to all those how many device have been harmed because of exploit till date I have not seen even a single member posting about it so I do not think it is as serious as we make out to be

Well, downloaded and installed on ma tab UK 8010. Been messing around with it for the last half hour, checking everything works as it should.
Device OFFICIAL status.
Allshare Cast works fine.
No issues with language.
Seems slightly smoother and faster.
All tested apps work as they did prior.
Still 4.1.1 as expected. Exynos exploit fixed.
So, I would say given my previous thread, IF you have issues with Kies or OTA I would download and install.
Riki

samir_a said:
The roms he has linked are stock firmwares for regions like Germany, US which have already received the patch. If you are on stock rom for your country then wait you will receive the OTA soon, if you are on a stock rom from another region then you will not so it makes sense to flash the German rom.
Also a question to all those how many device have been harmed because of exploit till date I have not seen even a single member posting about it so I do not think it is as serious as we make out to be
Click to expand...
Click to collapse
Absolutely agree with Samir. Why would you downgrade to 4.1.1 just to fix a feature which seems never to have caused a problem!
Other than allowing the Note10.1 to be much easier to root for the hundreds (probably thousands) of users who have used the simple rooting method using the Exynos Exploit?
No issues with language.
Seems slightly smoother and faster.
All tested apps work as they did prior.
Click to expand...
Click to collapse
Compared to what - original 4.1.2?

I think I would rather wait for the "official" OTA update than download from a unknown source, thanks all the same.

Dont worry his source are geniune as they are the samfirmware stock rom links so do not worry about the source

pwatkins said:
Absolutely agree with Samir. Why would you downgrade to 4.1.1 just to fix a feature which seems never to have caused a problem!
Other than allowing the Note10.1 to be much easier to root for the hundreds (probably thousands) of users who have used the simple rooting method using the Exynos Exploit?
Compared to what - original 4.1.2?
Click to expand...
Click to collapse
I agree, but I was on 4.1.1 anyway. So closing a potential issue is a no brainer for me. It may well be the best/easiest way to root the tab but having such a potentially dangerous exploit there is not worth the risk.
Just because no one has been affected (or reported having been affected, or even knows they are affected) doesn't justify keeping it open. Especially IF you use the tab for banking, or other financial or work purposes!
My thoughts anyway.

Well its not that someone can use the exploit by magic they need a disguise to do that in form of an app or something else so if you are using it for banking then you would anyways be extra sure of the source of apps you install or website you browse.
Also once you patch it does not mean that your device cannot be hacked there are many other ways to it may be the above one was the easiest.
Again I am in no advocating not to patch the exploit but just putting some facts. Infact there was an article which said there were may fishing apps on google play itself

Way I see it is simple. The tab has a major exploit, the option to fix that exploit is now available. Folks can argue semantics/doomsday scenarios all day long, but it don't change the facts!
Peace

How to change baseband version in Galaxy S4(i9500)?

I bought Samsung Galaxy S4 in 2013 back when it was a flagship device, it came installed with Android Jellybean, almost 4 years have passed and it is still stuck at Jellybean. Since then, it didn't got a single update.
I'm not sure what is the latest update for S4 because the updates pushed by Samsung never reach my phone and that is because of baseband version. Other S4's have got quite a few updates till now. In fact, I updated my friend's S4 to Lollipop and my own S4 is stuck at Jellybean.
I visited Samsung website and found that they release updates only for some baseband versions of S4 and that list didn't contain the baseband version of my S4 so it is forever stuck at 4.2.2. Samsung Customer Care says go to service center, they will update your phone manually. I said why should I when I got a flagship phone, it should get updates OTA.
Because my S4 didn't get any update, the same thing must have happened with many other ones and will probably happen with S8 due to launch in 2017. Many of those S8s will never receive any single update.
So is it possible that baseband version can be changed and I switch to the one that gets update? There is always an option to flash a custom ROM but if I get an official update to Lollipop, I will be happy.

Before the Samsung update reaches your phone it has to pass through the carrier's hands first, where they add their crappy bloat.
In other words, if there's no update, then it's probably your carrier's fault.
You could update manually with Odin.

Pwnycorn said:
Before the Samsung update reaches your phone it has to pass through the carrier's hands first, where they add their crappy bloat.
In other words, if there's no update, then it's probably your carrier's fault.
You could update manually with Odin.
Click to expand...
Click to collapse
I am from India so no system of carrier here.

Umm, you guys in India have cellular networks. Those are the aforementioned carriers. They may not add any bloat, but they do have to test the updates first before releasing them to the devices. This is to ensure the update doesn't cause unwanted problems on the network. However, we're heading into 2017, and after all this time you should have received an update to Android 5.0.1. So let's verify that you have a model intended for India. Please enter download mode and read off the model number at the top left corner of the screen.

Changing the baseband will not automatically get you a ROM update. If you want an updated ROM for your phone, I suggest updating to the latest bootloader and modem, flash TWRP, and then flash a custom ROM.

Strephon Alkhalikoi said:
Umm, you guys in India have cellular networks. Those are the aforementioned carriers. They may not add any bloat, but they do have to test the updates first before releasing them to the devices. This is to ensure the update doesn't cause unwanted problems on the network. However, we're heading into 2017, and after all this time you should have received an update to Android 5.0.1. So let's verify that you have a model intended for India. Please enter download mode and read off the model number at the top left corner of the screen.
Click to expand...
Click to collapse
Here is the correct firmware version of my device: sammobile.com/firmwares/download/14242/I9500XXUAMDK_I9500ODDAMDK_INU
Sam Mobile is not displaying Android version, if you look at sammobile.com/firmwares/database/GT-I9500/INU, my device PDA and CSC versions are second from last. But if you look at other S4s in the same list, most of them got Android 5.0.1 so can't I just download any one of them and flash it using Odin?

You're looking on the wrong page. Individual ROM pages do not display the Android version, but the full list does, where that information is applicable. In your case, the ROM you linked to doesn't have a version number, but also happens to be the ROM originally on the device, based upon the PDA and CSC. Check here. Not only does it tell you the version, but tells you the date it was posted. The one you want will be at the top of the list, as it's the latest available for your device.

Strephon Alkhalikoi said:
You're looking on the wrong page. Individual ROM pages do not display the Android version, but the full list does. Check here. Not only does it tell you the version, but tells you the date it was posted. The one you want will be at the top of the list, as it's the latest available for your device.
Click to expand...
Click to collapse
I also posted the same link as yours, just scroll to the very bottom, there are 2 entries that doesn't display the Android version and one of them is mine - second from last. The PDA and CSC matches my device.
PDA - I9500XXUAMDK
CSC - I9500ODDAMDK

Well, you might want to reread my post, as I edited it while you were typing.
Anyway, in post 6, this is the link you provided: sammobile.com/firmwares/download/14242/I9500XXUAMDK_I9500ODDAMDK_INU
This is mine: sammobile.com/firmwares/database/GT-I9500/INU/
Big difference.
The link you provided takes you directly to that particular ROM. The link I provided takes you to every ROM available for that device using the CSC of INU. Based upon your opening post, you're looking to update to the latest ROM. However, you are getting hung up because the ROM you currently have on your device doesn't have a date. It doesn't matter how old your ROM is! The latest version for your device will always be at the top of the database page, i.e. the link I provided in post 7. Thus, as of this moment, the ROM you want is here. Download it, flash it via Odin, and you're done.

Strephon Alkhalikoi said:
Well, you might want to reread my post, as I edited it while you were typing.
Anyway, in post 6, this is the link you provided: sammobile.com/firmwares/download/14242/I9500XXUAMDK_I9500ODDAMDK_INU
This is mine: sammobile.com/firmwares/database/GT-I9500/INU/
Big difference.
The link you provided takes you directly to that particular ROM. The link I provided takes you to every ROM available for that device using the CSC of INU. Based upon your opening post, you're looking to update to the latest ROM. However, you are getting hung up because the ROM you currently have on your device doesn't have a date. It doesn't matter how old your ROM is! The latest version for your device will always be at the top of the page. Thus, as of this moment, the ROM you want is here. Download it, flash it via Odin, and you're done.
Click to expand...
Click to collapse
Thanks! By the way, I did post 2 links, it's just that because I don't have a total of 10 posts, I can't post link so the second link(in plain text) isn't easily spotable but it is there and it is same as yours. Check after "Sam Mobile is not displaying Android version"

Obvious link was not obvious. You're right.

Strephon Alkhalikoi said:
Obvious link was not obvious. You're right.
Click to expand...
Click to collapse
I've downloaded firmware from the link you provided, flashed it via ODIN and now my S4 is successfully running 5.0.1, thanks a lot! Need one more help from you - I didn't perform factory reset, I directly flashed the firmware and now only 2 things have changed on my phone - root status and android version. Root is now gone and that's what I wanted, Android version has also changed but all my files, data and apps are same; no single app got deleted, all are exactly same as before so do I need to perform a factory reset and wipe cache?

If you haven't encountered any bugs or app crashes, I don't think a factory reset is needed.

SM-G950U1 on AT&T, still on Aug 1 security patch, no OTAs, what to flash?

Bought an unlocked S8 from Samsung I use AT&T for service. I wouldn't be opposed to flashing/odin'ing AT&T firmware. Currently on build NRD90M.G950U1UEU1AQH3 and the August 1st security patch. I'm unsure of the best path to get to an AT&T firmware.

Go to the att section. Find the qf7 firmware and flash it with Odin.
Go to the adb update from server thread. Download all the firmwares (starting with qf7 to whatever it is) and put them on your external storage. While on qf7 reboot into recovery and select install update from storage. Flash each one, after the last one wipe data/factory reset and reboot.

So to be clear, flash AQF7 in Odin. This will get me onto an AT&T specific SM-G950U (<-- Not U1) ROM that I can then sideload the updates onto? Is sideloading the ADB updates just to speed things up vs waiting for OTAs once I'm on the correct ROM?

I flashed my at&t version to AHQ3 thinking I would be getting faster support. I am also surprised that the Unlocked AHQ3 is still on the August security patch. I really expected this version to get patched much faster or am I missing something?

msk said:
I flashed my at&t version to AHQ3 thinking I would be getting faster support. I am also surprised that the Unlocked AHQ3 is still on the August security patch. I really expected this version to get patched much faster or am I missing something?
Click to expand...
Click to collapse
The US unlocked version is the red headed stepchild of the S8 world, it really is slower for updates.

I am running AQK3 on an ATT version, think I got it from sammobile, just got one I think it was the VZW version but don't remember, didn't change the AT&T bloatware... since I did not pawn/root it in my current setup. Patch level is oct not nov...

You should have received the November security patch update last night or should be getting it sooner than later. If anything try running the manual software update on WiFi when you get a chance.

How do I go from 7.0 with "U" software to 8.0?

I'm trying to wrap my head around all this, but my head is spinning. In December I was looking to get my S7 flat to 7.0 rooted. I discovered that root can only be achieved with eng kernel and that has its drawbacks. I decided I don't need/want root at that cost of stability, performance and battery life. Somehow I settled on installing a "U" variant that seemed to work well with less Verizon bloat. I couldn't get the S Health app and monitors on the back of the phone working, but I figured I could live with that. Recently I tried casting my phone to a Amazon Fire Stick and discovered the "Smart View" button is missing and I couldn't figure out how to get it back, so I might've lost that too. I also discovered in the past nine months Oreo is out with additional features and I figure if I'm going to go through the hassle of reinstalling, I might as well upgrade.
So, I hear root with Oreo is better than it's been, but not perfect, so I'l like to upgrade to unrooted oreo, either stock or debloated (if such a version exists without tradeoffs). Is there a certain version I'm supposed to go to so there's some flexibility in reinstalling the OS? Like I know sometimes versions of software are released that upgrade little, but patch exploits.
Also, if I do get whatever version of Oreo installed, do I then ignore OTA updates going forward? Is there any advantage to that?
And I can use the mobile hotspot feature. I don't think I have any special plan to accommodate that, nor do I have an unlimited plan (with Verizon). Is that intended, or is that from the "U" variant. Would I lose that?
My phone's info is below, if anyone can decipher what I did:
Model #: SM-G930U
Android Version: 7.0
Baseband Version: G930UUEU4BQE2
Kernel Version: 3.18.31
Build #: NRD90M.G930UUEU4BQE2
I apologize, I know my nomenclature isn't up to snuff. I realize that this stuff isn't for the casual user, at least on this phone. It's very hard to figure out what's current if you're not in the loop.
Thank you for any help you can offer.

If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment

djh816 said:
If possible, I'd try just doing an Odin of the full Verzion equivalent to what you are on. That has the best chance of being compatible with the bootloader you are on. If not, you may have to downgrade to earlier U variant and then switch to equiv V variant. If I recall correctly the *BRA1 firmware intersected on all carrier releases. In my case in the past, I was on too new of an AT&T variant and it wouldn't let me switch because the model didn't match. I had to switch to the generic U variant and then go to Verizon variant after.
In your case I'd try either of these in full Odin form (and may need princecomsy Odin or other that will force it):
G930VVRS4BQC9 - Closest Verizon V variant firmware that is released same month as your current version (a couple weeks later)
G930VVRU4CRE5 - June 5th 2018 Verizon V variant firmware based on 8.0
Edit:
Alternatively I think you should be able to go to the latest U generic variant 8.0 firmware, whatever that would be. I think that's G930UUEU4CRG2 at the moment
Click to expand...
Click to collapse
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/

Umbra. said:
Thank you for the reply! I really wasn't expecting any replies, there's just too much going on in my post.
I backed up everything tonight so when I flash it I can wipe everything and do it right. This sammobile site lists all the firmware updates and that helped somewhat demystify things. Is it true that the fifth digit from the right of build is the bootloader? If that's the case, does that mean I can install any version from the last MM update through the september oreo update and upgrade and downgrade between them without issue since they all have a "4" for that digit? Is the bootloader the thing that sometimes gets updated, preventing downgrades or is the baseband and modem also something that I need to consider. If I just install the latest verizon oreo update, am I limited in downgrading?
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/
Click to expand...
Click to collapse
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date

djh816 said:
Purely anecdotal but in my case I think the newer version I had was the issue. I don't believe you are limited in downgrading if you have a full signed odin of your current model variant that you can downgrade too. I think the main issues come in when you are going from a different model and a newer/older firmware. If you are staying on latest G930V Verizon firmware for example, I believe you could downgrade as far back as needed with full Odin. Just not necessarily U variant firmware without finding the crossover point with that firmware (like AT&T and Verizon variants both on BRA1 firmware). I could be mistaken on the requirements but messing around with flashing an older rom with same 930 variant, then switching to a new variant from that may work. In my case I had to downgrade to BRA1 AT&T, then switch to BRA1 generic 930U, then switch to Verizon BRA1 930V. Also the stock version of Odin didn't like me switching variants but princecomsy version worked (not sure if that works well with new firmwares though). As you say though, there may be some limits in downgrading depending on what bootloader you are on. I don't think I've personally had a situation where I couldn't but with all those efuses out there who knows..But even then you should be able to pivot to another variant of similar release date
Click to expand...
Click to collapse
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction

Umbra. said:
I don't still know about downgrading and switching, but I can live with that. I took the plunge and opted to install the latest Verizon firmware last night. Surprisingly I was able to just install it over the U firmware with basic Odin. I Then went into recovery and did a factory reset. It's gonna take awhile to set everything up how I like, but S Health works, I've got the Smart view toggle (didn't get to test it yet), mobile hotspot works, but I get some cool new features to explore (I especially like being to able to have more control over what notifications show for each app, instead of a blanket on/off). Not crazy about the new AOD font, but I'll get used to it. Thanks for nudging me in the right direction
Click to expand...
Click to collapse
Woo, welcome back to the walled garden lol.. BTW I found in the themes/lockscreen app (can't recall where) they had the old lockscreen font I preferred as a clock option

T387AAUCS3CUD1 Firmware for SM-T387AA (Samsung Galaxy Tab A)

Hi!
Does anyone know where I can find the T387AAUCS3CUD1 stock ROM? I'm trying to fix a unit that I may have messed up by tinkering with custom ROMs.

Anyone?

Still nothing?

Hi also searching high and low for T387AAUCS3CUD1.
Any success finding it?
Samsung Galaxy Tab A (T387AA) - Software Update for the Samsung Galaxy Tab A (T387AA) - AT&T
Get Samsung Galaxy Tab A (T387AA) support for the topic: Software Update for the Samsung Galaxy Tab A (T387AA). Find more step-by-step device tutorials on att.com.
www.att.com
ATT is worthless - no support. OTA Android 8 won't update to Android 10. Says already current.

No luck yet :-(

Still no luck.

Someone recently gave me a SM-T387AA, came across this thread while looking for the latest firmware for the device. It does appear that T387AAUCS3CUD1 is the latest for the AA version, which I also was unable to locate. (probably because ATT uses their own servers for firmware instead of samsung) However, while searching, I also came across a newer version of firmware for SM-T387W.
Specifically:
AP VERSION T387WVLS3CVK2
CSC VERSION T387WOYV3CVK2
CSC VTR (Canada)
ANDROID VERSION Q(Android 10)
SIZE 2.62 GB Full Files
MD5 d3b07faf990e6b33b55f5f39839799e4
BUILD DATE 20221114152111
SECURITY PATCH LEVEL 2022-06-01
To my surprise, I flashed the 387W firmware on my 387AA with ODIN and everything seems to be working just fine. Still can't unlock my bootloader though. I see there's also a 387R4 variant. I might try that next, and will report back if I do.

Would this not though prevent a user from being able to use it on AT&T?

scythe000 said:
Would this not though prevent a user from being able to use it on AT&T?
Click to expand...
Click to collapse
I popped in an ATT sim and calls/txt appear to be working.

Oh interesting, I wonder what the difference between the two firmware versions are then?

javadahut said:
Someone recently gave me a SM-T387AA, came across this thread while looking for the latest firmware for the device. It does appear that T387AAUCS3CUD1 is the latest for the AA version, which I also was unable to locate. (probably because ATT uses their own servers for firmware instead of samsung) However, while searching, I also came across a newer version of firmware for SM-T387W.
Specifically:
AP VERSION T387WVLS3CVK2
CSC VERSION T387WOYV3CVK2
CSC VTR (Canada)
ANDROID VERSION Q(Android 10)
SIZE 2.62 GB Full Files
MD5 d3b07faf990e6b33b55f5f39839799e4
BUILD DATE 20221114152111
SECURITY PATCH LEVEL 2022-06-01
To my surprise, I flashed the 387W firmware on my 387AA with ODIN and everything seems to be working just fine. Still can't unlock my bootloader though. I see there's also a 387R4 variant. I might try that next, and will report back if I do.
Click to expand...
Click to collapse
Got a link to where we can download it?

scythe000 said:
Got a link to where we can download it?
Click to expand...
Click to collapse
I used Bifrost. It can pull the latest firmware for most samsung devices that are hosted on samsung servers. Type in the model, "SM-T387W" and the CSC, "VTR", check for update and then download.
Bifrost link: https://github.com/zacharee/SamloaderKotlin