G965U and G965U1 Firmware Links Here

Search This thread

iBowToAndroid

Senior Member
Nov 9, 2010
5,446
1
1,721
Twin Cities MN
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"?
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
 

en11gma

Senior Member
Jan 18, 2013
1,029
89
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

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.
 

iBowToAndroid

Senior Member
Nov 9, 2010
5,446
1
1,721
Twin Cities MN
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.
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
 

en11gma

Senior Member
Jan 18, 2013
1,029
89
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

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....
 

iBowToAndroid

Senior Member
Nov 9, 2010
5,446
1
1,721
Twin Cities MN
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....
They all look identical. You can choose any one that you want
 

en11gma

Senior Member
Jan 18, 2013
1,029
89
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:
[email protected]:~$ 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.
 

TheMadScientist

Recognized Contributor
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:
[email protected]:~$ 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.
Heimdall does not work with some of the US devices like s8 s9s and such. Odin is the only way
 

en11gma

Senior Member
Jan 18, 2013
1,029
89
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
 
Last edited:

jcsww

Senior Member
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!

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.
 

en11gma

Senior Member
Jan 18, 2013
1,029
89
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.

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.
 

jcsww

Senior Member
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.

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.
 

en11gma

Senior Member
Jan 18, 2013
1,029
89
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.

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!!!
 
Last edited:

jcsww

Senior Member
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!!!

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.
 

en11gma

Senior Member
Jan 18, 2013
1,029
89
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.

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
 

jcsww

Senior Member
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

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.
 

en11gma

Senior Member
Jan 18, 2013
1,029
89
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.

Thats what i needed to know.
Thanks
 

en11gma

Senior Member
Jan 18, 2013
1,029
89
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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 26
    For those who aren't already aware, G965U is the model number of all of the US carrier versions of the S9+. The G965U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.

    Manual Odin flashing is designed for those who:

    - want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
    - want to flash U1 firmware to their U device
    - want to convert from U1 firmware to carrier U firmware
    - want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)

    For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model - so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit SamFirm/Frija.

    This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.

    Odin 3.13.1 3B Patched is required for flashing these.

    Happy flashing!

    U firmware: https://www.androidfilehost.com/?w=files&flid=257072
    U1 firmware: https://www.androidfilehost.com/?w=files&flid=257075

    Notes:

    - DON'T QUOTE THE OP WHEN YOU REPLY, kthx

    - I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading to an S9+, welcome back :)

    - My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc

    - My naming method for folders on AFH is: build - bootloader - Android version
    So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.

    - HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.

    - Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T. I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.

    - For identifying USERDATAS, and to know what region/CSC to use in SamFirm/Frija:

    ATT = AT&T (not available via SamFirm/Frija)
    BST = Boost Mobile
    CCT = Xfinity Mobile (Comcast)
    CHA = Spectrum Mobile (Charter)
    SPR = Sprint
    TMB = T-Mobile
    TMK = Metro PCS
    USC = US Cellular
    VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
    XAA = U1 firmware

    - the correct procedure for switching from one carrier's firmware to another is:
    1. Flash full U1 firmware package including non HOME CSC
    2. Upon boot, insert a SIM of the carrier whose firmware you want
    3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
    4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want
    12
    Oh nice! So the next Ota would always be the unlocked firmware? Is there a thread for detailed instructions? Like I meantioned, my last Samsung was an S4.....

    ---------- Post added at 07:11 AM ---------- Previous post was at 07:00 AM ----------



    Is there a detailed writeup on how to do this? Last Samsung device was an S4.

    Here is a quick guide

    Proceed with Caution. This is a firmware flash using Odin and will not trip KNOX.

    * Download Mobile Driver for Samsung phones and install it

    * Download G965 U1(Unlocked Model files) from here

    * Extract using 7-Zip(WinRar will error out)

    * Download the PatcheD Odin from here

    * Factory Reset the phone and remove your Google Account if you have already set the phone up.

    * Assemble all required files on Odin

    * Put the phone into Download mode by holding down the Bixby Button, then the Volume Down button and then the Power Button. Hold all 3 buttons down till a warning page appears, proceed by pressing the Volume up button

    * Connect the Phone to your PC using the factory cable

    * Press Start on Odin

    * The whole process should take about 5 minutes to finish.

    * The phone will restart twice and voila you will have an unlocked S9+ with no carrier boot logo or bloat.



    Phonlab's Video guide for S8+ still works for the S9
    6
    I will stop posting any leaks for Pie, that way i don't get accused for it for the S9 or S9 Plus, this is something that's always been warned on people to install on there own RISK, and not me being responsible for there actions if something goes wrong with there phones.

    This is a huge shame. Not that I'm interested in the Pie builds right now since they are so buggy, but the fact that you even have to not post because people are complaining of their phones not working is just a shame. For me, Xda is a place for getting leaks, custom roms, and apps that are outside the box to the point where they sometimes can't be on the play store. While most things on Xda are tested before being posted, it's always been a bleeding edge, use at your own risk type of site.

    I've been coming here for years to extend the life of phones, rooting, and running custom roms. This kind of nonsense (people complaining about a clearly marked unstable alpha not working right) reminds me of the whole issue in society today. People just don't want to take responsibility for anything. The entire reason I haven't tried the Pie builds is because it's buggy. That's why it's an alpha. I can't afford to be without my phone, so I stay put on Oreo.

    Anyways, I'll stop my rant. Glad to have you here and appreciate the leaks and all you bring to us. You've been awesome throughout the years (my Evo3d rocked your rom the whole time I had it), and if you haven't heard it from anyone recently, I totally appreciate your work!
    5
    Odin files G965USQU3ARG7
    https://www.androidfilehost.com/?fid=3700668719832236886

    Running On My Galaxy S9+ SM-G965U Wicked Venom

    ---------- Post added at 10:27 ---------- Previous post was at 10:25 ----------

    Odin files G965USQU3ARG7
    https://www.androidfilehost.com/?fid=3700668719832236886

    Running On My Galaxy S9+ SM-G965U Wicked Venom
    Link: G965USQU3ARG7-to-U3ARH1 https://www.androidfilehost.com/?fid=3700668719832237024

    Running On My Galaxy S9+ SM-G965U Wicked Venom

    ---------- Post added at 10:42 ---------- Previous post was at 10:27 ----------

    Odin files G965USQU3ARG7
    https://www.androidfilehost.com/?fid=3700668719832236886

    Running On My Galaxy S9+ SM-G965U Wicked Venom

    ---------- Post added at 10:27 ---------- Previous post was at 10:25 ----------

    Link: G965USQU3ARG7-to-U3ARH1 https://www.androidfilehost.com/?fid=3700668719832237024

    Running On My Galaxy S9+ SM-G965U Wicked Venom

    Links are up.
    4
    G965USQU3ARG2-to-U3ARG5-UP Link https://www.androidfilehost.com/?fid=5862345805528056747

    Sent from my Samsung Galaxy Note 8 using XDA Labs