G965U and G965U1 Firmware Links Here

Search This thread

jcsww

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

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.
 

en11gma

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

megamb11

Senior Member
Oct 11, 2017
62
5
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?
 

jcsww

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

Do you have USB Debugging enabled in the devices Developer Options?
 

iBowToAndroid

Senior Member
Nov 9, 2010
5,446
1
1,721
Twin Cities MN
Do you have USB Debugging enabled in the devices Developer Options?
yes, and with authorization
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
 
  • Like
Reactions: TheMadScientist

jcsww

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

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.
 

TheMadScientist

Recognized Contributor
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?
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
 

megamb11

Senior Member
Oct 11, 2017
62
5
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.
 

iBowToAndroid

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

megamb11

Senior Member
Oct 11, 2017
62
5
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?
 

megamb11

Senior Member
Oct 11, 2017
62
5
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"?
 

tp2droid

Member
Aug 22, 2011
12
2
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.

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.
 

tp2droid

Member
Aug 22, 2011
12
2
the phone is unlocked then. i have a att phone that picked up the tmobile firmware when i insterted a ultramobile sim.

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?
 

YooperNC

Member
Apr 30, 2015
32
7
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!
 
Last edited:

iBowToAndroid

Senior Member
Nov 9, 2010
5,446
1
1,721
Twin Cities MN
I have a Cricket (AIO) S6, 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!
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
 
  • Like
Reactions: YooperNC

YooperNC

Member
Apr 30, 2015
32
7
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
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!
 

iBowToAndroid

Senior Member
Nov 9, 2010
5,446
1
1,721
Twin Cities MN
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!
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
 
  • Like
Reactions: YooperNC

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