yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
they both do have the same numbers for "PDA" and "CSC" but i see different information for the following:

for the verizon version it shows:

Product code	VZW

and for the tmobile version it shows:

Product code	TMB

does this means the checksums for both the verizon and tmobile with be the same since the "Product code" is different?

also if my phone is originally from verizon and i now have a tmobile sim card with service do i need to take that out since i did download the verizon version (even though both the verizon and tmobile version have same pda and csc)?

or

do i need to take out the tmobile sim and put back in the (verizon tracfone sim) and then flash the verizon file which i did download off sammobile.

i just dont want to mess this up since it wont auto update im thinking its because it was a verizon phone with verizon firmware on the verizon network then all i did was factory reset the device with the tmobile sim card in it and then it rebooted and all the verizon software was gone and tmobile software showed up including the boot screen.

so i not sure if i need to put the old verizon sim card in first before i flash the verizon file i downloaded "G965USQU8FTJ3_G965UOYN8FTJ3_VZW.zip"

dang this is probably going to get even worse since im in ubuntu

btw i will probably flash to the U1 after i flash "G965USQU8FTJ3_G965UOYN8FTJ3_VZW.zip" as i dont want any carrier bloat but i do use this phone for the hotspot mainly as it is just a data line.

should i not do the U1 and just stick with "G965USQU8FTJ3_G965UOYN8FTJ3_VZW.zip"?
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
1. The firmware files (except USERDATA) are 100% identical

2. It's impossible for you to do anything to screw up the process

3. If you want U1 firmware in the end, then just flash that and don't even bother with U
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
Yea i think i do want the U1 firmware in the end as long as i can still tether like i am now. Tmobile dont require their apps to be installed for this?

I was also looking at the U1 firmware and im not used to their naming conventions do i just grab the most recent firmware by date?

Should i have sim card removed when flashing any firmware then insert sim after it boots up?

Thanks for ur help.
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
1. You can flash any version that's from your current bootloader level, or from a higher bootloader level

2. The SIM card has no effect whatsoever on flashing. You can do whatever you want with it during flashing
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
I noticed under the "U1" firmwares there is a firmware version for each carrier.

I just downloaded "G965U1UES8ETI1_G965U1OYM8ETI1_TMK.zip" which has the "TMK" in its name.

I watched a youtube video where a guy changed from the "U" to the "U1" but it has "USC" in its file name.

Is that for us cellular and is that the version with the least bloat?

Why is there so many versions of the n america variant for the U1 firmwares....
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
They all look identical. You can choose any one that you want
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
im running ubuntu 20.04 lts amd64 desktop and cant get heimdall to work

i built from sources like it says here

http://www.bernaerts-nicolas.fr/linux/74-ubuntu/357-ubuntu-xenial-bionic-heimdall-compile-samsung

everything built from sources fine and it even detects phone with 'sudo heimdall detect' but when i try to do 'sudo heimdall print-pit --verbose' i get:

en1gma@M4800:~$ sudo heimdall print-pit --verbose

Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

http://www.glassechidna.com.au/donate/

Initialising connection...

Detecting device...

Manufacturer: "Samsung"

Product: "SDM845"

length: 18

device class: 2

S/N: 0

VID:PID: 04E8:685D

bcdDevice: 021B

iMan:iProd:iSer: 1:2:0

nb confs: 1

interface[0].altsetting[0]: num endpoints = 1

Class.SubClass.Protocol: 02.02.01

endpoint[0].address: 82

max packet size: 0010

polling interval: 09

interface[1].altsetting[0]: num endpoints = 2

Class.SubClass.Protocol: 0A.00.00

endpoint[0].address: 01

max packet size: 0200

polling interval: 00

endpoint[1].address: 81

max packet size: 0200

polling interval: 00

Claiming interface...

Setting up interface...

Initialising protocol...

ERROR: libusb error -7 whilst sending bulk transfer. Retrying...

ERROR: libusb error -7 whilst sending bulk transfer. Retrying...

ERROR: libusb error -7 whilst sending bulk transfer. Retrying...

ERROR: libusb error -7 whilst sending bulk transfer. Retrying...

ERROR: libusb error -7 whilst sending bulk transfer. Retrying...

ERROR: libusb error -7 whilst sending bulk transfer.

ERROR: Failed to send handshake!ERROR: Failed to receive handshake response. Result: -7

ERROR: Protocol initialisation failed!

Releasing device interface...

can anyone help with this as i dont really want to install windows just for odin...... grrrr.
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
I'd recommend looking for a thread specifically geared towards flashing using Ubuntu
[Samsung Galaxy S9+ Guides, News, & Discussion] TheMadScientist:
Heimdall does not work with some of the US devices like s8 s9s and such. Odin is the only way
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
doing a full windows 10 install over my full ubuntu 20.04 install :( pretty sad!!!

luckily i have two laptops and still do have one full install of ubuntu 20.04 but i really liked having two laptops with ubuntu 20.04

i dont like side by side installs (dual boots) they always fighting to control the hard drive boot partition.

anyhow this is pretty sad!

ok so if i flash the latest "U1" what is the option i chose in odin to make it have no specific carrier?

just like it came from samsung unlocked from factory.

the phone is already wiped so it dont matter.

i do have tmobile service if that makes any difference.

thanks in advance
[Samsung Galaxy S9+ Guides, News, & Discussion] jcsww:
Did you have the device in download mode and was USB Debugging enabled in Developer Options?

Disable your main drive, pop in a USB Key or external drive and install Windows 10 to that. That way, you can use it when you need to without creating any issues with yourain drive.
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
yep the device was in download mode as when i did the command 'sudo heimdall detect' it did detect it.

i tried with enabling usb debug mode and then selecting always allow this device and i also tried with booting to stock recovery and wiping data and cache partitions.

i also tried the heimdall from the ubuntu repo which installs 1.42 by default and i also built it too

adb was installed from ubuntu repo.

everything looked good it just wouldnt communicate with the phone as it should of.

bummer.

anyhow i do have windows 10 installed to the installed ssd and i think everything is updated now.

i downloaded "Odin3_v3.14.1 stable" i hope this will work with the tmobile firmware U1 i downloaded.

getting ready to try on phone that has had the data and cache partitions wiped.

will see soon.

just not sure which options to check for the odin files to make this "U" phone to change into a "U1" phone just like from samsung factory unlocked.

the home and csc files i guess are troubling me.
[Samsung Galaxy S9+ Guides, News, & Discussion] jcsww:
Make sure your ODIN is the 3.13.1 either patched or modded. The U1 firmware are not branded! There is no T-Mobile U1 official firmware. The U1 XAA firmware is a non-carrier specific firmware.
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
wow!

that was a close one.

ok going back to find odin 3.13.1 patched.

thanks. sure glad i came back and checked as i was just now installing the samsung usb drivers and adb platform tools.

so it is non carrier specific until the "home-csc" is flashed?

as long as the "non-home-csc" is used it stays non carrier specific?

i extracted the zip and selected the BL, AP, CP and CSC.

i left user data empty

flashing now.

everything appears to be working correctly.

i havent signed in with my google account yet but besides that everything seams to be working good.

still has samsung bloat.

when phone boots up i just see the "Samsung" logo :)

that is good!

thanks for the help

and thanks to the people who put up these firmwares!!!
[Samsung Galaxy S9+ Guides, News, & Discussion] jcsww:
Good to hear. Some images include a User data and or CSC of the carrier specific firmware. From what you wrote though, it all sounds good. If you can take OTA's, then you are good to go.
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
Do i need the user data thing so i can take OTA's?

I was going to ask about this today so im glad you brought it up.

Do i get software / system updates from samsung or tmobile?

Do i need the user data installed to get these updates?

Thanks
[Samsung Galaxy S9+ Guides, News, & Discussion] jcsww:
Userdata isn't needed with the U1 firmware. With the U firmware variants, it contains some carrier specific settings and bloat ware. If you are going to use T-Mobile or switch carriers before you buy a new device. The U1 firmware is the best firmware in my opinion to stick with unless you want specific carrier apps that aren't available in the PlayStore.
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
Thats what i needed to know.

Thanks
[Samsung Galaxy S9+ Guides, News, & Discussion] natibongo:
Is G965U1UES8ETI1 the current OS version?
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
For U1, yes
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
do these both have the same bootloaders so you can go back and fourth flashing each firmware?

G965U1UES8ETI1_G965U1OYM8ETI1_TMK.zip

G965USQU8FTJ3_G965UOYN8FTJ3_VZW.zip
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
Yep
[Samsung Galaxy S9+ Guides, News, & Discussion] jcsww:
Both of them have the same bootloader version, which is version 8. You can tell that by looking at the fifth number from the left of the end of the firmware. In those two examples: 8ETI1 and 8FTJ3.
[Samsung Galaxy S9+ Guides, News, & Discussion] en11gma:
Thanks. Just wanted to make sure. I know it says it in the 1st post but for some reason my brain just dont understand it good. I know the directions are clear but my brain...

Thanks
[Samsung Galaxy S9+ Guides, News, & Discussion] megamb11:
Just picked up a phone online. IMEI is clean, no idea if it is SIM unlocked. Digging into the history (I've been rooting for a few years now), I see that this was a VZW phone and still has a firmware from that last owner. When I started the phone up first time (before installing SIM card or connecting to Wi-Fi, I got a TMB splash screen. I am a TMB user, but how can the firmware be VZW (I checked firmwares in Sammobile) and the splash screen be TMB?

To my point... phone is still on A9 and I want to go to A10. Downloaded the correct U1 (XAA) file from Sammobile (matched BL v7) and I am getting hung up on "setup connection". From there, I intend to make the switch over the newest TMB firmware.

Here is what I tried:

1. tried Odin 3.13.1_3B and 3.14.1_3B

1. unistalled/reinstalled drivers

2. working from 3.0 USB port

4. deivce cord works (tested with ADB interface)

Any ideas?
[Samsung Galaxy S9+ Guides, News, & Discussion] jcsww:
Do you have USB Debugging enabled in the devices Developer Options?
[Samsung Galaxy S9+ Guides, News, & Discussion] megamb11:
yes, and with authorization
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
What I think he's getting at is to try using a different method for getting to DL mode. I have this exact same issue on my Win 10 laptop when I try flashing S8s, S9s, and Note 9s. Anything older or newer works fine - it's only those series that have the issues.

What works best for me is to boot the phone to DL by holding Volume Down and Bixby at the same time, while plugging it in via the cable (start with the phone powered off). If that still doesn't work, try a different cable. Even that trick only works for me with one of my cables - the other 2 will still give the Setup Connection error.

Or, if you have a Win7 machine, try using that. My Win7 laptop will always flash those models, without fail
[Samsung Galaxy S9+ Guides, News, & Discussion] jcsww:
Have you made sure the Samsung drivers are installed while the device is in Download Mode? Personally, I always favored the PatcheD 3.13.1_3B ODIN over the modded.
[Samsung Galaxy S9+ Guides, News, & Discussion] TheMadScientist:
Also usb 3.0 can cause issues. Use a2.0 usb hub. I had this issue a while back. 3.0 issues only exist in download mode and odin everything else works good
[Samsung Galaxy S9+ Guides, News, & Discussion] megamb11:
Progress so far... not much.

BTW, thank you everyone who has replied to this issue. It's communities like this that keep information flowing and people informed.

Downloaded another U1 ZIP from Updato (per comment from jcsww). Tried this morning and same "setup connection" issue. Tried 3 different USB cables. All of my ports on my PC are 3.0 or 3.1... don't think I have any 2.0 extensions lying around, but I will check later. Unfortunately, I sold the last laptop that I had with an older WIN version on it some months ago.

Run ODIN in compatibility mode or is that even possible?

Question concerning the drivers? What evidence should I see in Device Manager that my phone is connected while in DL mode? The only change I have noticed is listed under "Modem" as Samsung Modem Device #X. MTP is not listed/available and I have never been able to get ADB to work in the DL partition (or Recovery partition for that matter) on any device that I played with over the years.
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
The modem is all that loads in Device Manager, along with possibly the USB controller. ADB has never, and will never, be enabled in DL mode. ADB is enabled in Recovery, but it only works for sideloading official OTA update zip files.

You'll have to either try a USB 2.0 hub/adaptor, or a totally different computer
[Samsung Galaxy S9+ Guides, News, & Discussion] megamb11:
So here's a kicker for you... DL'd Smart Switch to see if I could work from there... here is what I get on the phone info:

Version - SJ9 (TMB)

Here's the issue... there is no SJ9 for TMB; SJ6 was the last version on A9 before going to A10. There is, however, an SJ9 version for VZW. Do I have a phone stuck in limbo with files mismatched? This would explain the TMB splash that I got BEFORE I ever loaded my SIM card in the device.

Can I downgrade within the same BL version and try to get to a common baseband version within the providers and then move to U1 and then wholly to TMB?
[Samsung Galaxy S9+ Guides, News, & Discussion] megamb11:
Got it working... phone is updating on TMB OTA now. Had my work comp with a USB 2.0 on it. But, I have to wonder if there was an issue with the FRP lock. I was not factory resetting in the system, only in the recovery partition. Would this have caused an issue with the "setup connection"?
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
Nope
[Samsung Galaxy S9+ Guides, News, & Discussion] tp2droid:
I'm running the newest version of Linux Mint myself. I use virtualbox to run my W10 vm for various purposes (like getting a old scanner to work within the vm). If you use a Windows 10 vm with Virtual box, the usb should pass through fine. Initially, I totally forgot that Odin requires you to boot into recovery mode ... Odin kept seeing com3/com4 connected properly for my Samsung device ... but it could never load the files once I clicked start.

But, once I booted into recovery mode and pressed go, Odin had no issues pushing the firmware to the phone.

With Virtualbox, all I had to do was go to devices and select the samsung to be passed through. In the W10 vm, you should see the Samsung device listed under device manager under 1 or 2 possible device types/names.

When my w10 didn't work (I figured it would because the Scanner did), I tried getting Heimdall to work before I realized I wasn't in recovery mode on the phone. Not surprising about Heimdall since it's from 2013 or 2015.
[Samsung Galaxy S9+ Guides, News, & Discussion] tp2droid:
the phone is unlocked then. i have a att phone that picked up the tmobile firmware when i insterted a ultramobile sim.
[Samsung Galaxy S9+ Guides, News, & Discussion] YooperNC:
I have a Cricket (AIO) S9, and stopped getting OTA updates after July 2020. Is there going to be another update for this phone? If not, I found AIO-G960U1UEU8FTK2-20201202145101, and I have Odin 3.13.1, 3.13.1 Patched, and 3.13.3. I understand that this will require a full reset, as I would be going from G960U to G960U1. My question is: Would this still give me WiFi calling? If not, I can't afford to flash it. Our home is a cell signal wasteland, so we depend on WiFi calling 100% of the time. Anyone know the answers to my questions? Thanks!
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
Well hopefully you mean that you have an S9, or otherwise this firmware won't get you very far lol.

Try flashing U1 but use a CSC from a U firmware package - don't use the U1 CSC. That's worked for some users in the past
[Samsung Galaxy S9+ Guides, News, & Discussion] YooperNC:
Sorry, I was standing on my head when I wrote that... (LOL)

Any U package? What has to match in order to do this? Thanks!
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
Well at minimum, the Android version and bootloader level has to match. But I always recommend getting as close as possible. If the U1 version is TJx, use the U CSC that's from a TJx build, same goes for TKx, TLx, etc
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
AT&T USERDATA for bootloader 8 has been added - build TK4.

I also added the full firmware package because, while lots of other carriers got this build, I didn't see that anyone else had uploaded it on AFH yet.

And, from now on, you can expect AT&T USERDATAs to be added right away, when new bootloaders and new Android versions are released :)
[Samsung Galaxy S9+ Guides, News, & Discussion] zzgerilla:
after alot of time unsuccessful attempt flashing and getting "threads completed. (succeed 0 / failed 1)" message from odin i finally manage to flash the firmware from G965U(T-Mobile) to G965U1 by doing this step.

1 -remove the sim card from the phone.

2 -Hard reset the phone.

3 -let the phone boot up to first intro and power it down and go to the download mode.

4 -flash the G965u1 (SM-G965U1_XAA_G965U1UEU7ETH2) firmware using modded odin

if that failed, format and install fresh windows on your pc and install all the required drivers and software for flashing the phone and try the step above again.

Good luck.
[Samsung Galaxy S9+ Guides, News, & Discussion] doubledragon5:
I have T-Mobile. What is the purpose and gains of flashing the G965U1
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
No carrier bloatware
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
Bootloader 9 files have (finally) been added for AT&T - both USERDATA and (because I think every other carrier got v9 back in January, so no one else will get this same build) the rest of the full firmware files
[Samsung Galaxy S9+ Guides, News, & Discussion] echoheart152:
thanks for all the good info, just flashed my g965u sprint phone with g965u1 bootloader 9 and I finally have working mms and access to lte network to make calls with a straight talk sim.
[Samsung Galaxy S9+ Guides, News, & Discussion] sunshinethief:
hi all, thx to everyone who has contributed to this lexicon of firmwares and knowledge... but...

...just to ensure im not off the mark here, i have a S9+ that i bought for my nepbuild hew locally (in the USA) that was advertised as "Unlocked"... I gave it to my nephew who put his Cricket SIM into it and all works EXCEPT for calls, they fail immediately, but SMS/MMS/data all work... the phone is indeed SIM unlocked, but in the software section it shows "service provider sw ver. = TMB/XAA/VZW", the phone displays a Tmobile boot screen (with insanely irritating chime!) at every boot and has Tmobile bloat included... from what i gather this started out as a Verizon-branded phone, was unlocked, then flashed with a Tmobile firmware version (build number QP1A.190711.020.G965USQS9FUA2)... my nephew being a Cricket user Im assuming flashing this phone to the ATT carrier version should allow his SIM to work for calls, is this correct?

i have downloaded the ATT_Userdata file in the first post of this thread, along with the 3GB G965U_UB5_9.zip that was in the same folder, do i also still need a G965U1 firmware package to flash before i use the ATT files, to remove the Tmo bloat? should this work to get his phone working for calls? i have downloaded and installed the patched Odin build along with the Samsung USB drivers already.

thanks in advance for any clarification, really hesitant to proceed without some confirmation.
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
You may be able to force the bloatware to switch just by inserting an AT&T SIM. Try that, before messing around with firmware
[Samsung Galaxy S9+ Guides, News, & Discussion] LatencyXXX:
Does anybody have an unlocked BL that is for the G965U1UES9FVD1? I have spent days trying to unlock the OEM enable option.. but it is hidden and unable to flash TWRP or anything.

The latest IMG that i was able to find off other ROMs that were unlocked is for v7. Unable to flash v9 w/ ODIN.

Anybody know what else I can try at this time? I have ran out of options.
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
BL unlocking doesn't work that way. It's not done with firmware files.

It can be done on your model, but requires a paid service
[Samsung Galaxy S9+ Guides, News, & Discussion] adventurousMan:
Is anyone here? I am trying to flash SM-G965U1 stock firmware in SM-G965U, using patched odin but unsuccessful. I used patched odin old ones and latest one also. But after setup connection it showed 0 success 1 failed operation. I removed FRP, Hard reseted the device. I installed latest samsung usb drivers. Used Heimdall but still no success.
[Samsung Galaxy S9+ Guides, News, & Discussion] iBowToAndroid:
You need to state the exact error that you get in Odin, and also any error that may appear on the phone screen
[Mi 3 Android Development] Dr. Ramm:
TeamHorizon's XenonHD rom builds for Full Device Name (cancro)

http://www.xenonhd.com/

XenonHD is a custom firmware aka ROM for various Android devices. It is based on LineageOS 15.1 with additional features, performance and battery life improvements.

The idea behind XenonHD is to give users a ROM that is "blazing fast, rock stable and buttery smooth".

Device Source:

android_device_cancro

android_kernel_cancro

Download Links:

Recovery: TWRP

ROM: Experimental

Gapps: opengapps.org

Changelog: Experimental​

Flashing Instructions:

To install this ROM you will need to have a latest custom Recovery such as TWRP installed.

Copy the downloaded ROM to your phone.

Boot into your recovery

Back up your ROM

Make a full wipe (system, data, cache, dalvik)

Install the ROM

Install GAPPS package

Reboot - the first boot can take up to 5 minutes

Installing updates:

Copy the downloaded update to your phone.

Boot into your recovery

Back up your ROM

Install the update

Optionally wipe caches

Reboot

​

Other Links:

Github

Google+

Telegram

XDA:DevDB Information

Official XenonHD 8.1 ROM by TeamHorizon, ROM for the Xiaomi Mi 3

Contributors

Dr. Ramm, dadi11, Shivam Kumar Jha , GuaiYiHU, linuxxx

Source Code: https://github.com/TeamHorizon

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.4.x

Based On: LineageOS

Version Information

Status: Beta

Created 2018-03-15

Last Updated 2018-03-15
[Mi 3 Android Development] sinz0000:
Good to see you back with this ROM. :D