Develop Bugs

S4 Mini -Root Issue

Hi Guys ,
When I connect my phone just vibrate so my last solution is to root it .so below my issues :
-Using Odin3 v1.85 ,I got that :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-clockwork-6.0.5.1-serranoltexx.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Using other Odin versions ,I got :
Stuck on initialization .
Also be informed I tried with different usb port ,different cables.

Odin 1.85 sounds old, I user Odin 3,09 that I downloaded from xda (see link below) to install custom recovery (TWRP) now but I have run clockwork earlier on my s4 mini (GT-i9195) and it works fine.
Odin 3.09 - http://forum.xda-developers.com/showthread.php?t=2353876

linol said:
Odin 1.85 sounds old, I user Odin 3,09 that I downloaded from xda (see link below) to install custom recovery (TWRP) now but I have run clockwork earlier on my s4 mini (GT-i9195) and it works fine.
Odin 3.09 - http://forum.xda-developers.com/showthread.php?t=2353876
Click to expand...
Click to collapse
When I plug my phone just vibrate and nothing happen after. when I want to power it also vibrate and nothing on screen .but I can enter on odin mode >
What's could be ? I need your support .
Thanks in advance

How about you plug your USB cable directly at the backside of CPU incase of desktop pc. and also Turn off AntiVirus and kill kies in task manager if its running.
But before doing any of that try connecting your phone to kies. and check if it can be connected. if not install the drivers.

thanks for your but didn't help ,below what I got :
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..

You can try flash emergency firmware from Samsung kies. Never tested but maybe can bring back to life your phone.

kies can't detect my mobile

Have you installed the Samsung drivers?

Yes,installed

bingozingo said:
Yes,installed
Click to expand...
Click to collapse
Looks like your eMMC is dead.

How can I confirm that ?

bingozingo said:
How can I confirm that ?
Click to expand...
Click to collapse
IMO, the only way is to look for a full restore image of your device.
Keywords to use in your search are: i9195xxucnh5, rev01, low_user_ship, tar.md5
The full restore image is the one used by Kies to initialise the devise to its factory state. It can be a single file or, in most cases, 4 files (BOOTLOADER, AP, CP and CSC).
It contain the PIT file, necessary to re-partition the entire eMMc, and every image for each new created partition.
If you find that image, or a member can provide it, there are good chances that your phone come back to life.
If Odin fails to flash the image and says "can't re-repartition", then your are good to look for another chipset.
Sorry, i can't help you with links.

pls ,have you the steps to do that ?,also did you have the full name of the all files that can help for search .

pls help
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
I wanna be crazy .

Can you note exactly what is written on the Download Mode screen ?

Downloading
Do not turn off target!!

bingozingo said:
Downloading
Do not turn off target!!
Click to expand...
Click to collapse
No, i mean what is written in the upper left corner.

Odin Mode
product name : GT-I9195
Current Binary : samsung official
system status : official
Knox kernel lock : 0x0
knox warranty void : 0x0
csb-config-lsb : 0x30
bootloader ap swrev : 2
write protection : enable

bingozingo said:
Odin Mode
product name : GT-I9195
Current Binary : samsung official
system status : official
Knox kernel lock : 0x0
knox warranty void : 0x0
csb-config-lsb : 0x30
bootloader ap swrev : 2
write protection : enable
Click to expand...
Click to collapse
Nothing strange here...
Your bootloader can see the content of system partition.
Can you access stock recovery (Power Button+Volume Up) ?
If you can, do a factory reset then reboot.

When I want to enter on recovery mode( power+volume up ) ,it's just vibrate .nothing on screen

Samsung Galaxy Note 2 N7100

Hello,
First, my note 2 stuck at boot logo.
When i try to enter recovery stuck about 15 seconds on logo after that says with red failed to mount /efs (no such file or directory) ; failed to mount /system (no such file or directory); failed to mount /cache (no such file or directory) ; failed to mount /cacahe/recovery/last_recovery (no such file or directory) ; failed to mount /data (no such file or directory).
I read that it would be something about a "rescue fireware" was a topic on the XDA forum but no link was not working.
Please help me fast!
Thx!

alex2003881 said:
Hello,
First, my note 2 stuck at boot logo.
When i try to enter recovery stuck about 15 seconds on logo after that says with red failed to mount /efs (no such file or directory) ; failed to mount /system (no such file or directory); failed to mount /cache (no such file or directory) ; failed to mount /cacahe/recovery/last_recovery (no such file or directory) ; failed to mount /data (no such file or directory).
I read that it would be something about a "rescue fireware" was a topic on the XDA forum but no link was not working.
Please help me fast!
Thx!
Click to expand...
Click to collapse
Same happened to my phone too and no luck. still stuck! Someone help please!

If you can boot into Odin mode, flash a stock rom from sammobile.com.

audit13 said:
If you can boot into Odin mode, flash a stock rom from sammobile.com.
Click to expand...
Click to collapse
I tryed this no result

What happened when you used Odin? Post the Odin log?

audit13 said:
What happened when you used Odin? Post the Odin log?
Click to expand...
Click to collapse
Nand write fail. Or Sometimes, complete write operation failed!

audit13 said:
What happened when you used Odin? Post the Odin log?
Click to expand...
Click to collapse
When i try to put rescue firware with odin says setup connection after that fail.
Tomorrow i'm going to samsung official service.
I'll comeback with edit!

karanvirkohli said:
Nand write fail. Or Sometimes, complete write operation failed!
Click to expand...
Click to collapse
What does the log actually say? It probably failed when trying to flash a certain file.
Did you try different USB cables and USB ports?

Flash repair firmware
4 file
Sent from my GT-N7100 using Tapatalk

Hey, sorry for hijacking your thread.
I have the same problem. I tried many different scenarios and I couldn't fix it. I gave up and went to Samsung and after 48hs I called finding out that they refused to fix it. Talked to the IT guy and he said he has no idea how to fix it and told me the only fix is to change the whole motherboard and he said its not suggested to do so as its expensive. I have no idea what I should do. I flashed custom recovery, stock recovery. Tried to separate the whole firmware and flash it piece by piece using the skipsoft tool. I tried flashing PIT files with custom recovery, stock recovery, stock rom I have tried multiple PIT files from multiple websites.
This happens when I try flashing stock rom downloaded by samfirm or sammobile.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100OJVFOD1_N7100XXUFOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
If I to flash a PIT file using any of the scenarios mentioned above I get this ( the 4 files repair rom in this example )
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<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> CODE_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<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> MODEM_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<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> CSC_XEF_N7100OXADLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
It will keep doing this forever until I unplug the cable. I'm running stock Kitkat 4.4.2 but all methods I find are for older versions with different bootloaders yet I still tried them as there are no recent fix from what I can find.

In the first situation, the sboot.bin causes an error because the bootloader in the ROM is older than the phone's current bootloader.
Did you try flashing the latest stock ROM from sammobile.com using Odin 3.07 in the PDA slot? Sammobile.com ROMs should only be unzipped once to yield a tar.md5 file and flashed in the PDA slot.
Tried different USB cables and USB ports?

audit13 said:
In the first situation, the sboot.bin causes an error because the bootloader in the ROM is older than the phone's current bootloader.
Did you try flashing the latest stock ROM from sammobile.com using Odin 3.07 in the PDA slot? Sammobile.com ROMs should only be unzipped once to yield a tar.md5 file and flashed in the PDA slot.
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yes I did all that. Same error. If I extract the tar file and do another odin flashable tar using skipsoft tool it doesnt work, removing one file at a time didnt work either. I tried the latest on sammobile, the latest on sammobile for my country, and the latest from Samfirm for my country. I also tried using SmartSwitch and Kies recovery using the serial number and model number and they don't recognise the phone during downloading like about 60% of downloading it will show an error that it doesnt recognise it.

When flashing the sammobile.com tar.md5 file in Odin's PDA/AP slot, do you receive an error message? If yes, what is the error?

audit13 said:
When flashing the sammobile.com tar.md5 file in Odin's PDA/AP slot, do you receive an error message? If yes, what is the error?
Click to expand...
Click to collapse
Same exact error of post #10
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100OJVFOD1_N7100XXUFOA1_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

The ROM being flashed has a bootloader that is too old or the ROM is not meant for the phone.
The model # for the phone has been confirmed as being a gt-n7100 on the Odin screen?

audit13 said:
The ROM being flashed has a bootloader that is too old or the ROM is not meant for the phone.
The model # for the phone has been confirmed as being a gt-n7100 on the Odin screen?
Click to expand...
Click to collapse
Odin screen that is in download mode ? Yes it says GT-N7100.

You're using the latest ROM for the phone? Which country?

audit13 said:
You're using the latest ROM for the phone? Which country?
Click to expand...
Click to collapse
Yes. Egypt. I have used both latest on sammobile and download by using samfirm. I have tried both of them. I have tried indian and few other countries all lead to the same error.

Are you using the original Samsung cable?

audit13 said:
Are you using the original Samsung cable?
Click to expand...
Click to collapse
It is not the one that came with the phone but it is one that I bought from Samsung. I also tried few other cables that came with LG and Asus phones.

Need help to unbrick Samsung SM-A505F

Hello,
A friend of mine tried to root his phone(SM-A505F) using Odin3 and TWRP i really don't know what he did but he says that he unzip the .tar file for TWRP and tried to flash each .img file that was converted to .tar.md5 into AP. So what happens next is he accidentally flash something in BL. Now the phone is stuck on a loop and can only go to download mode. Now i'm trying to help him unbrick it by just flashing a stock which I found here: https://forum.xda-developers.com/galaxy-a50/how-to/stock-rom-samsung-galaxy-a50-sm-a5005f-t3926746
But the phone is SM-A505F and we're from Philippines and it was bought locally so region wise there is no stock rom for SM-A505F so i tried to use SM-A505GN.
Unfortunately it's not working. Odin3 always get's stuck on here:
<ID:0/005> 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..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 6025 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> up_param.bin
<ID:0/005> cm.bin
<ID:0/005> keystorage.bin
<ID:0/005> uh.bin
<ID:0/005> vbmeta.img
<ID:0/005> boot.img[/SIZE]
And on the phone it shows: "SW REV. CHECK FAIL(BOOTLOADER) DEVICEL: 3, BINARY: 1"
I would really appriciate any help here as my friend is crying over it, as it is a just bought phone
Thanks in advance
PS. Also tried the SM-A505F stock rom and it has the same result

Hi, hoping I can help a bit. Had a similar issue with my A50 after flashing TWRP, so I'm hoping I can help. Im from from the Netherlands and using the FN variant, but this should apply to any variant.
You can download the F firmware from here; its quite fast (a lot better than dealing with sammobile's website).
imei.info/download-firmware/samsung/samsung-galaxy-a50/SM-A505F/
After unpacking the zip, you have to put every .tar.md5 file into the right directory in Odin.
Put phone into download mode (hold volume buttons while putting in usb c cable connected to laptop)
make sure you lock the bootloader first. (by long pressing up if i remember correctly)
I suggest using the latest ODIN for this. Can you keep me posted if this works?
---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------
Agil1ty said:
Hi, hoping I can help a bit. Had a similar issue with my A50 after flashing TWRP, so I'm hoping I can help. Im from from the Netherlands and using the FN variant, but this should apply to any variant.
You can download the F firmware from here; its quite fast (a lot better than dealing with sammobile's website).
imei.info/download-firmware/samsung/samsung-galaxy-a50/SM-A505F/
After unpacking the zip, you have to put every .tar.md5 file into the right directory in Odin.
Put phone into download mode (hold volume buttons while putting in usb c cable connected to laptop)
make sure you lock the bootloader first. (by long pressing up if i remember correctly)
I suggest using the latest ODIN for this. Can you keep me posted if this works?
Click to expand...
Click to collapse
Btw did you remove any google account before trying to flash TWRP? If not, try to get into recovery after flashing with ODIN and do a factory reset. You will have to put in the same google account after rebooting in android.

Fail (Auth) error when flashing firmware.

I wanted to install the latest unlocked firmware (SAMSUNG GALAXY NOTE 10+ SM-N975U USC USA N975USQS3BTB3) to my Note 10+, because I am on Sprint and want to have a stock ROM without all of the Sprint stuff. I was able to to this on my S10 and Odin before with no issues, but Odin says this:
<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:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> quest.fv
<ID:0/004> persist.img.ext4
<ID:0/004> carrier.img.ext4
<ID:0/004> dqmdbg.img.ext4
<ID:0/004> userdata.img
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 7987 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> abl.elf
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
The download mode screen also gives an error that says: MDM mode can't download (xbl)
Does anybody know what is going on? I have no idea why it is doing this as it has worked fine every other time with my S10.

Try enabling usb debugging in developer options?

Ge0Spartan said:
I wanted to install the latest unlocked firmware (SAMSUNG GALAXY NOTE 10+ SM-N975U USC USA N975USQS3BTB3) to my Note 10+, because I am on Sprint and want to have a stock ROM without all of the Sprint stuff. I was able to to this on my S10 and Odin before with no issues, but Odin says this:
<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:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> quest.fv
<ID:0/004> persist.img.ext4
<ID:0/004> carrier.img.ext4
<ID:0/004> dqmdbg.img.ext4
<ID:0/004> userdata.img
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 7987 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> abl.elf
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
The download mode screen also gives an error that says: MDM mode can't download (xbl)
Does anybody know what is going on? I have no idea why it is doing this as it has worked fine every other time with my S10.
Click to expand...
Click to collapse
Is it SIM unlocked? Are you using the non home CSC or home CSC?

I think there is a new Odin. Try Odin 3.14.4
Sent from my SM-N960U using Tapatalk

scottusa2008 said:
Try enabling usb debugging in developer options?
Click to expand...
Click to collapse
Yes, it is enabled

You have to get the most up to date firmware... Idk why it does that but if the firmware you trying to install is older it will not let it install. The U1 should be on c9 now I think
Sent from my SM-N970F using Tapatalk

GDHAMTON7 said:
You have to get the most up to date firmware... Idk why it does that but if the firmware you trying to install is older it will not let it install. The U1 should be on c9 now I think
Sent from my SM-N970F using Tapatalk
Click to expand...
Click to collapse
Not true. You can go to older firmware as long as it's the same bootloader version. The reason his isn't working it because he is trying to install U1 firmware on a U (carrier) device. That can only be done with the patched odin. I have gone from C9 back to BTB3 twice with no issue.

I always had to do a factory wipe when going between U1 and U. To me a clean install is better anyway.
Sent from my SM-N975U using Tapatalk

TechOut said:
Not true. You can go to older firmware as long as it's the same bootloader version. The reason his isn't working it because he is trying to install U1 firmware on a U (carrier) device. That can only be done with the patched odin. I have gone from C9 back to BTB3 twice with no issue.
Click to expand...
Click to collapse
Would you happen to have the patched Odin version I would need to use?

Ge0Spartan said:
Would you happen to have the patched Odin version I would need to use?
Click to expand...
Click to collapse
I used the 3.14.4b patched one from here https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572/amp/

Hello, not to hijack this thread, but I have a similar issue. I'm trying to flash the Galaxy Note 10+ SM-N975W firmware on the N975U1 note 10+ and am getting a failure.
<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:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1401)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 8548 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> abl.elf
<ID:0/010> xbl.elf
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
<ID:0/010> Added!!

crushdancexz said:
Hello, not to hijack this thread, but I have a similar issue. I'm trying to flash the Galaxy Note 10+ SM-N975W firmware on the N975U1 note 10+ and am getting a failure.
Click to expand...
Click to collapse
I replied to your other thread about Samsung Pay as well, but I'll link it here too.
When flashing from one variant to another (SM-N975U1 to SM-N975W), normally Odin will fail and abort the flash since there is a model number mismatch.
You need the patched version of Odin which allows this model number switch and will allow you to convert your device to the Canadian variant.
Patched Odin can be found here --> Link

MeltdownSpectre said:
I replied to your other thread about Samsung Pay as well, but I'll link it here too.
When flashing from one variant to another (SM-N975U1 to SM-N975W), normally Odin will fail and abort the flash since there is a model number mismatch.
You need the patched version of Odin which allows this model number switch and will allow you to convert your device to the Canadian variant.
Patched Odin can be found here --> Link
Click to expand...
Click to collapse
will this work if i updated to android 10? because it says build/binary invalid

crushdancexz said:
will this work if i updated to android 10? because it says build/binary invalid
Click to expand...
Click to collapse
What build are you on right now and which one are you trying to flash?

MeltdownSpectre said:
What build are you on right now and which one are you trying to flash?
Click to expand...
Click to collapse
I'm currently on this:
//oNE ui VERSION 2.1
aNDROID vERSION 10
QP1A.190711.020.N975U1UES4CTF2
KERNERL VERSION 4.14.117-18725784
#2 mON jUN 22 14:54:58 kst 2020
XAA/XAA/XAA
//
and trying to flash this: https://www.sammobile.com/samsung/g...e/SM-N975W/XAC/download/N975WVLU3CTE7/348383/
I have the same error

crushdancexz said:
I'm currently on this:
//oNE ui VERSION 2.1
aNDROID vERSION 10
QP1A.190711.020.N975U1UES4CTF2
KERNERL VERSION 4.14.117-18725784
#2 mON jUN 22 14:54:58 kst 2020
XAA/XAA/XAA
//
and trying to flash this: https://www.sammobile.com/samsung/g...e/SM-N975W/XAC/download/N975WVLU3CTE7/348383/
I have everything setup and ready to go, but I just want to double check before starting because I ended up in a bootloop last night and don't want to brick my phone. (Although I was using older firmware last night).
Click to expand...
Click to collapse
Ah, quite a simple problem. Your phone is currently on bootloader revision 4, because the XAA firmware is newer than the Canadian XAC firmware.
The Canadian firmware is based on bootloader revision 3.
Samsung doesn't allow bootloader downgrading, so you'll have to wait for XAC to release a v4 firmware and then you'll be able to make the switch.
I guess just stay on the N975U1 firmware and wait it out till XAC catches up.

MeltdownSpectre said:
Ah, quite a simple problem. Your phone is currently on bootloader revision 4, because the XAA firmware is newer than the Canadian XAC firmware.
The Canadian firmware is based on bootloader revision 3.
Samsung doesn't allow bootloader downgrading, so you'll have to wait for XAC to release a v4 firmware and then you'll be able to make the switch.
I guess just stay on the N975U1 firmware and wait it out till XAC catches up.
Click to expand...
Click to collapse
How can you tell that it's based on bootloader revision 3 on the sammobile website? Also, I managed to get out of the download screen somehow last night and back into my phone, but I can't get out now...

crushdancexz said:
How can you tell that it's based on bootloader revision 3 on the sammobile website? Also, I managed to get out of the download screen somehow last night and back into my phone, but I can't get out now...
Click to expand...
Click to collapse
Look at the numbers in bold text.
XAA: N975U1UES 4 CTF2
XAC: N975WVLU 3 CTE7
The build number itself is CTxx, and the number before that is the revision. On XAA it's 4, on XAC it's 3. Samsung has very strict downgrade protection so there's no way to get around it.
Once XAC also hits 4 (or higher), you'll be able to flash the Canadian firmware on your phone.
To get out of download mode, if nothing else works, hold ALL buttons for at least 30-40 seconds until the device forces a reboot.

MeltdownSpectre said:
Look at the numbers in bold text.
XAA: N975U1UES 4 CTF2
XAC: N975WVLU 3 CTE7
The build number itself is CTxx, and the number before that is the revision. On XAA it's 4, on XAC it's 3. Samsung has very strict downgrade protection so there's no way to get around it.
Once XAC also hits 4 (or higher), you'll be able to flash the Canadian firmware on your phone.
To get out of download mode, if nothing else works, hold ALL buttons for at least 30-40 seconds until the device forces a reboot.
Click to expand...
Click to collapse
Thank You very much MeltdownSpectre, you've been very helpful in clearing things up for me. I'm not having any luck exiting download mode though, it resets right back into the blue screen.

crushdancexz said:
Thank You very much MeltdownSpectre, you've been very helpful in clearing things up for me. I'm not having any luck exiting download mode though, it resets right back into the blue screen.
Click to expand...
Click to collapse
If you're stuck in download, flash the latest N975U1 firmware again just to reboot and get out of it.
Always good to have the stock firmware handy in case anything goes wrong and you need to re-flash.

pls help, is my s9 only soft bricked or unsolvable

i got twrp on there and magisk but couldnt log in to my samsung and google accounts, an i read startin odin i had to log out first from them, which i did so i thought i might have missed something so i did it all over and now its bricked.
it started out with getting black screen with a tiny red text that i needed official rom or something like that. and it got that if i tried booting regularly or even trying to boot twrp.
so i currently can only get into download mode and it wont let me flash new twrp or official firmware. i tried flashing recovery, bootloader and other things separate and the all fail so i'm able to enter download mode but cant do anything with odin.
this is my latest odin log, it just stops and i get the error on my phone in red text looking pretty much the same, only thing that seem to change is if it says bootloader or system etc.. the odin log saying it failed doesnt show up until i unplug or exit, and i waited a few hours the first time so i knew it was a done deal before aborting it
i'll add picture of how my download mode looked as it fails and another how it looks if i try starting the phone in any other way, it tells me to use emergency recovery in smart switch for pc but when doing that my phone isnt showing up so i can't do that neither. and that screen only showed up after i tried flashing the new firmware.
Code:
<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..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 6557 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> up_param.bin
<ID:0/004> cm.bin
<ID:0/004> keystorage.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
i got a G960F/DS and restoring it in the beginning i always had an old 2018-2019 security patch running android 9, not sure exact which firmware but the fw zip i tried flashing was called G960FXXU2CRLI_G960FOXM2CRLI_DBT
if that makes any difference. i tried finding something something in a similar time frame as my original one which is why i chose that one.
so please help me solve this

Fixed by @hainguyenthao
Thank you so much

Same issue on my side
JimZiii said:
Fixed by @hainguyenthao
Thank you so much
Click to expand...
Click to collapse
Can you tell me how you have fixed that issue?
Rgds
Bob