Patched Odin 3.13.1

[termn8er]

Ok thanks. TMO doesn't have a U1 version yet. So now that I am on UI 5, I'll wait for them to create a U1 variant then use that one. Thanks for the information!

 

[valeck69]

Greetings! Can someone help with Odin? When flashing, the program hangs on the Setup Connection.
Do not offer options with a cable, crooked hands, correct firmware and the like)))
In the subject for a long time, I can flash. On this computer with the same cable, I flashed note 10 without problems.
The drivers are all installed (note 10 was flashed), the phone is detected correctly through the ADB terminal. The firmware is 5-file, and it was downloaded both through Frija and from the SamFw site. Downloaded both native SM-N986U and general SM-N986U1. I tried to flash both 12 and 13 android. And there is always one problem: it checks the firmware files and hangs on the Setup Connection
Version Odin3_v3.14.1, Note 20 Ultra 5G phone SM-N986U
By the way. There is no item "Unlock OEM" in the developer section.

 

[rafal.polska.b]

There is a button "Reboot download if possible"
Just an idea for new Odin version: would it be possible to add second button: "Reboot to recovery" ?

 

[alb.boy]

Thank You! I was getting with official ODIN the error: FAIL! SHA256 is invalid but with your patched version didnt have any issue. Flashed android 13 on SM-G991U1 with ATT Carrier like a champ!

 

[iBowToAndroid]

Ok thanks. TMO doesn't have a U1 version yet. So now that I am on UI 5, I'll wait for them to create a U1 variant then use that one. Thanks for the information!

They absolutely do. U1 firmware has CSCs for every carrier, just like U firmware does. So yes, F936U1 TMB has existed ever since the phone was released, just like all of the other CSCs. Not that it matters anyways because you can flash any U or U1 firmware anytime you want, regardless of carrier/CSC

Greetings! Can someone help with Odin? When flashing, the program hangs on the Setup Connection.
Do not offer options with a cable, crooked hands, correct firmware and the like)))
In the subject for a long time, I can flash. On this computer with the same cable, I flashed note 10 without problems.
The drivers are all installed (note 10 was flashed), the phone is detected correctly through the ADB terminal. The firmware is 5-file, and it was downloaded both through Frija and from the SamFw site. Downloaded both native SM-N986U and general SM-N986U1. I tried to flash both 12 and 13 android. And there is always one problem: it checks the firmware files and hangs on the Setup Connection
Version Odin3_v3.14.1, Note 20 Ultra 5G phone SM-N986U
By the way. There is no item "Unlock OEM" in the developer section.

Hanging on SetupConnection is a USB issue. Need to change cables, ports, PCs until something works.

From what I've seen, A-to-C cables tend to work better than C-to-C. And USB 2.0 tends to work better than 3.0

If it's a desktop, make sure it's plugged into a rear port, not front.

Make sure your drivers are correct.

 

[burc ugur]

When is will add Odin v3.14.4 ?

 

[alecxs]

When is will read OP?

 

[mohitgalaxy3]

Hi @realbbb

Did you figure out why cross flashing works on U and U1 models and didn't on N and B model.
Is there anything we can do at firmware side with shell exploit that will help in doing cross flashing b/w B and N.

 

[iBowToAndroid]

Hi @realbbb

Did you figure out why cross flashing works on U and U1 models and didn't on N and B model.
Is there anything we can do at firmware side with shell exploit that will help in doing cross flashing b/w B and N.

1. It doesn't work because Samsung doesn't allow it, period

2. No, shell exploit will not allow for cross flashing. Even a device that's bootloader unlocked can't be cross-flashed

 

[mohitgalaxy3]

1. It doesn't work because Samsung doesn't allow it, period

2. No, shell exploit will not allow for cross flashing. Even a device that's bootloader unlocked can't be cross-flashed

So only option is to root and replace the csc folder manually. Is it ?

 

[iBowToAndroid]

So only option is to root and replace the csc folder manually. Is it ?

U and U1 models can't be rooted

 

[mohitgalaxy3]

U and U1 models can't be rooted

You didn't even read my post...forget it.

 

[iBowToAndroid]

You didn't even read my post...forget it.

No, rooting a B or N model and replacing the CSC folder manually will not allow you to change firmware

 

[HTCCM11/2]

Hello,
it concerns the USB driver for SM-N975F and the update made by Odin at the end of the operation displayed the USB Fail error, however, the update was completed after that restart and the operation itself without problems.
Where did this error come from - what is the cause and how to remove it.

Log odin
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/003> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:1/003> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:1/003> File analysis..
<ID:1/003> skip file list for home binary
<ID:0/004> skip file list for home binary
<ID:1/003> param.bin
<ID:0/004> param.bin
<ID:1/003> userdata.img
<ID:0/004> userdata.img
<ID:1/003> dqmdbg.img
<ID:0/004> dqmdbg.img
<ID:1/003> omr.img
<ID:0/004> omr.img
<ID:1/003> Home Binary Download
<ID:0/004> Home Binary Download
<ID:1/003> Total Binary size: 8797 M
<ID:0/004> Total Binary size: 8797 M
<ID:1/003> SetupConnection..
<ID:0/004> SetupConnection..
<ID:1/003> Initialzation..
<ID:1/003> Set PIT file..
<ID:1/003> DO NOT TURN OFF TARGET!!
<ID:1/003> Get PIT for mapping..
<ID:1/003> Firmware update start..
<ID:1/003> NAND Write Start!!
<ID:1/003> SingleDownload.
<ID:1/003> sboot.bin
<ID:1/003> up_param.bin
<ID:1/003> cm.bin
<ID:1/003> keystorage.bin
<ID:1/003> uh.bin
<ID:1/003> vbmeta.img
<ID:1/003> boot.img
<ID:1/003> recovery.img
<ID:1/003> dt.img
<ID:1/003> dtbo.img
<ID:1/003> system.img
<ID:0/004> Can't open the serial(COM) port.
<ID:1/003> vendor.img
<ID:1/003> vbmeta.img
<ID:1/003> modem.bin
<ID:1/003> modem_debug.bin
<ID:1/003> cache.img
<ID:1/003> product.img
<ID:1/003> cache.img
<ID:1/003> product.img
<ID:1/003> RQT_CLOSE !!
<ID:1/003> RES OK !!
<ID:1/003> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)
<ID:1/003> Removed!!

Samfw.com_SM-N975F_AUT_N975FXXS8HWA1_fac
SAMSUNG_USB_Driver_for_Mobile_Phones. 1.7.59.0

 

[realbbb]

Hello,
it concerns the USB driver for SM-N975F and the update made by Odin at the end of the operation displayed the USB Fail error, however, the update was completed after that restart and the operation itself without problems.
Where did this error come from - what is the cause and how to remove it.

Log odin
<ID:0/004> Added!!
<ID:1/003> Added!!
<ID:1/003> SetupConnection..
<ID:0/004> SetupConnection..

<ID:1/003> Initialzation..
<ID:1/003> Set PIT file..
<ID:1/003> DO NOT TURN OFF TARGET!!

<ID:0/004> Can't open the serial(COM) port.

<OSM> All threads completed. (succeed 1 / failed 1)
<ID:1/003> Removed!!

Looks like you connected two devices, attempted to flash both of them, successfully flashed one of them.. The other failed.


RealBBB
Other Rules

 

[HTCCM11/2]

What... how I connected 2 devices i don't have other. In odin is only one phone connected to the computer is visible.

Maybe there is a second device in the history of the program? Is it possible that someone connected to this process (as a second device). What can I do about it and how to clear the access of each device.

Yes, the update process ended positively, the device is working properly.

How about Samsung Drive drivers, were they reinstalled before the update operation?.

 

[realbbb]

What... how I connected 2 devices i don't have other. In odin is only one phone connected to the computer is visible.

Maybe there is a second device in the history of the program? Is it possible that someone connected to this process (as a second device). What can I do about it and how to clear the access of each device.

Yes, the update process ended positively, the device is working properly.

How about Samsung Drive drivers, were they reinstalled before the update operation?.

Likely an error in the program/windows. It thought there was two devices. Close app, disconnect device, re-start app, reconnect device, configure files and flash away.


realBBB
Lilly Day

 

[cyanogenmodricky]

thank you, it worked on my j6+, i cannot get flash combination firmware, but now its installed thanks to you

 

[Exe1111]

Where can I download?

 

[AnonVendetta]

This patched Odin let me cross flash SM-T976B firmware on my SM-T976N (Tab S7 Plus, Korean variant). I honestly didnt think it would work, every time I had tried this Odin in the past with other devices, it always failed. It booted fine too, it seems like everything is working so far.

I'm going to try on my Note 20 Ultra 5G soon, which is the Korean SM-N986N variant. I want to see if it will accept American U/U1 firmware, since I live in the US.

@Exe1111: 1st post of this thread.