G965U and G965U1 Firmware Links Here

[iBowToAndroid]

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

Yep

 

[jcsww]

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]

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]

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]

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?

 

[megamb11]

yes, and with authorization

 

[iBowToAndroid]

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

 

[jcsww]

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]

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]

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]

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]

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]

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"?

 

[iBowToAndroid]

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"?

Nope

 

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

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
VIDID: 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]

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]

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!

 

[iBowToAndroid]

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

 

[YooperNC]

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]

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