Develop Bugs

Hopefully NOT Bricked but Unsure of What to Do

Ok, I got a new Note II the other day with 4.3 already installed via Kies or OTA. I attempted to push, via ODIN, "CF-Auto-Root-d2tmo-d2tmo-sght999.tar". I REALIZE THIS IS THE ROOT FOR S3; I KNOW I FLASHED THE WRONG FILE. PLEASE DO NOT POST SAYING I FLASHED THE WRONG FILE. I KNOW I SCREWED UP BIG TIME, AND I'M HOPING SOMEONE IS NICE ENOUGH TO TRY AND HELP ME THROUGH THIS. My laptop sat there for the better part of 2 hours acting like ODIN was cranking along but the bar never moved. After 2 hours, I had to pull the cord from the phone (stupid move, I know!), and this is, of course, where the problem began.
Now, I get the coveted "Firmware Upgrade encountered an issue. Please select recovery mode in Kies & try again." screen. The phone will, obviously, go no further than this in booting up. I am able to get to download mode.
I attempted to install JellyBean Release 4.3 (December 2013) from this thread to alleviate the issue. Here's the ODIN result:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T889UVUCMK7_2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Now, as I sit here and write this, I think installing a stock firmware like this one might not work at all. I need to install a recovery (stock or otherwise) to make this problem disappear. I tried to reinstall the CF-Auto-Root file and got this result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2tmo-d2tmo-sght999.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2tmo-d2tmo-sght999.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Again, it didn't do anything for hours. I pulled the cord again since it didn't look like it was actually writing anything to my phone.
I don't think I can use KIES as a last resort since I never backed up the phone through KIES before. I am out of ideas, and I would really like to get this phone operational again. Also, the serial number has been removed from the device (Igot the phone from Ebay), so I don't think I could use this route either.
Any and all help would be greatly appreciated.
Thanks in advance!

Download and flash CF auto-root for sgh-t889(link below)it includes recovery, then perform factory reset by rebooting in to recovery.
http://download.chainfire.eu/266/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.zip
Sent from my SGH-T889 using xda app-developers app

Help: Reverting the SM-N930A Battery Update

Alright so I'm trying to figure out what I'm doing wrong. I downloaded a copy of the pre-borked Note 7 firmware and I'm trying to flash it through ODIN. Every time I try, I get errors on both the phone and on the software.
I've been Googling all day and I can't find an explanation or a workaround. Can the experts here help with this?
ODIN log:
<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/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Note 7 display:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N930A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
OID:
WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: B2 (1,1,1,1,1) K2 S2
SECURE DOWNLOAD: ENABLE
CCIC:S2MM005 HW:3 Boot: 5 Main:ab
Then the actual error:
SW REV CHECK FAIL : [about]Fused 2 > Binary 1
[1]eMMC wrie fail: aboot

where did you find the firmware from ?

Having same issue
<ID:0/006> 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..
<ID:0/006> Odin engine v(ID:3.1205)..
<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..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I got the file from: https://www.androidfilehost.com/?fid=24651430732236681
ALL_SPT_N930PVPU1APH3_N930PSPT1APH3_CL8706608_QB10617237_REV00_userdebug_low_noship_MULTI_CERT.tar.md5
for the Samsung Galaxy Note 7(SM-N930T), by freeza

Good thing it failed, thats for T-Mobile, if it completed it would have bricked your phone. I am searching also for the AT&T version

I believe that the SM-N930P version is for Sprint. My carrier is Sprint

From my understanding, the firmware available online, which ends in PH1 has the old bootloader. Once the battery warning update hit (Green Battery Icon for those who have the replacement model) the firmware came with a new bootloader and firmware version ending in PHE.
Because of this, we cannot flash PH1 due to the bootloader change.
The 60% battery update (PK1), I BELIEVE, still uses the same bootloader as PHE.
The only solution I think would be as follows:
1) Immediately disable any future software updates. (We dont want another bootloader change)
2) Someone needs to find and or upload the PHE version firmware (which lets you charge 100%, and only has the annoying original message sometimes)
3) Backup everything.
4) Using the methods described in other places, flash the PHE version, charge to 100% and deal with only a few warning mesages. (Phone startup and Attach to charger)
4) Immediately disable any future software updates by following the instructions for Package Disabler PRO or EZ Disabler. (Making sure you're on airplane mode, SIM card out, and wifi is turned off)
These are my thoughts. I cant seem to find PHE firmware anywhere. One place has it supposedly, it seems shady cause the download link goes to an arabic website and the forums require you to pay for each download. (hmmmm.....)
I could be 100% wrong, Im not an expert by any means, just another user trying to join the community to help find a solution. Can anyone confirm Im wrong and they have been able to somehow flash the PH1 baseband firmware? Any and all help would greatly help me and the many others who have been held down by the man

SM-N930A Update
I have the N930AUCS1APH1_N930AATT1APH1_ATT_FULL_SAMFIRM.NET ROM with 4 .md5 files in it (BL, AP, CP, and CSP) and I can not get the phone to flash using Odin 3.12? Any ideas on what to do? This is my log, but basically just says failed!
<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> 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..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

next update will knock us all off the network. They are telling people that in the support calls to carriers and samsung.

Here is the PK1 firmware image
Hey guys, I am going to give you guys looking to get back to 100% charging a good new. I found the PK1 image for AT&T Note 7 N930A version. I just re-flashed my phone and it worked just fine. Got to charge my phone back to 100%. Got the green battery sign back. Here is the firmware image.
androidfilehost.com/?fid=312978532265363403 (I had to skip the www prefix because I am not allowed to post url at the moment. You guys know what to do with it. Just copy and paste.
Had to use Odin 3.12.3 version. I tried with Odin 3.10.7 version but got Odin protocol version error. So use Odin 3.12.3 version. Good luck.
---------- Post added at 09:58 AM ---------- Previous post was at 09:53 AM ----------
Sorry, my previous post should have said PKE firmware image.
---------- Post added at 10:03 AM ---------- Previous post was at 09:58 AM ----------
Got to check my spelling. PHE. Not PKE.

Thanks hachika88, that worked great. Does anyone know what I need to disable to prevent it from updating again. I have disabled com.samsung.knox.appsupdateagent and com.ws.dm, but is there anything else that should be disabled?

Use this link to go back to 100% on Rev 2 Firmware flash win Odin 3.12.4 or 3.12.3
androidfilehost.com/?fid=457084094631641284
Use Samsung Package Disabler Pro to disable Software Updates apk but you must do it fast after you reset your phone because once your phone checks for updates you can no longer disable it. Keep your SIM card out the phone and disconnect from wifi until absolutely necessary to get it disabled.
Good Luck

I used abd script to block th updates instead. A friend had her phe firmware pulled so that people could use it. If you look
http://www.n7r.co/

im looking for SM-N930A pl2 firmware. anyone?

Bootloop. NO root, NO custom os, 100% stock

Hey guys,
I'm kinda lost here, I bought this phone a few months ago on a black friday sale in the US.
A few weeks it started bootlooping (the 'preboot logo' kept flashing) it got worse and worse. Remember, I never tried to root, install a custom recovery/OS, nothing!
The only way to get it out of the bootloop was to do a factory reset or sometimes a clear dalvik. But it got worse and worse, and booting into recovery was getting harder and harder...
5 factory resets further, and dozens of dalvik clears, it it bootlooping again!! And it is now impossible to boot into recovery, only download mode.
So I reinstalled the os through odin using these files: https://forum.xda-developers.com/at.../nougat-odin-files-g928a-g928at4eqc6-t3596180
When that didn't work, I used these files: https://forum.xda-developers.com/at...odin-files-g928a-g928aucs4cqa1-build-t3576469
Same bootloop, and still impossible to boot into recovery via power+vol up+home.
You might ask, why don't you repair it under warranty?
Well, I live in france and samsung france refuses to even touch an american device!
Ps: here are the options I had ticked in odin:
1st time: F reset and re-partition
2nd flash: NAND erase, F reset and re-partition
3rd flash: bootloader update, NAND erase, F reset and re-partition
Here is a log, md5 checks included, in case you wonder:
<ID:0/006> 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/006> Odin engine v(ID:3.1207)..
<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..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> userdata.img
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I would greatly appreciate your help as I'm lost,
Many thanks in advance,
nxss4

I hope you receive a solution to this problem, I'm currently having the same problem and it literally appeared overnight.

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.

Firmware flashing problem with Samsung Galaxy Note 10 plus (SM-N975F)

Dear readers,
I tried to root my Note 10 plus (Dual SIM) via modifiying the firmware with the magisk manager, later on I have realized that I have downloaded and tried to install a not supported version of the firemware on my device.
Now I am struggling to flash a blank firmware, to revive my phone, but every time I am trying to flash a firmware that is made for my Note 10 plus version (SM-N975F [dual SIM] Germany), odin stucks while flashing and my phone reports a not valid version, that was tried to be installed.
Information:
-My phone shows me on the download mode (SM-N975F)
-I have downloaded and tried to flash the firmware for SM-N975F (Android 9)
-My Android version, before trying to root my device was Android 10 (June update)
-And I have removed the OEM lock,
download mode shows, while odin is stuck: SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4, BINARY: 1
Pit_flash_binary – Unsupported Version.
Odin information:
<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.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 8350 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> uh.bin
<ID:0/004> vbmeta.img
<ID:0/004> boot.img
Has it to do something with the dual SIM variant, what can I do?
I’m so thankful for every answer

I think Android 10 version has higher BL version and you cannot downgrade to android 9 with lower BL version.
Try flashing the latest FW version for your phone.

Try flashing the latest version of the version of the firmware. You are trying to flash a firmware that cannot be flashed to your phone as it has an older (unsupported) bootloader.

How did this turn out for you ? It sounded correct to me but last i had this problem i was on a s7 edge dual sim exynos . I was able to downgrade at lease from 8 to 7 or some variation of nougat to a much earlier one by mixing the new modem and bootoader with the older firmware of nougat that was previosly working. I learned my lesson about upgrading the modem only when absolutly neccesary or if i am completely done playing with the older roms that are not compatible if you upgrade the modem and bootloader. If youll notice alot of times devs pf ressurection leave thier modem and bootloader on a older version than most while still bringing the newest android to all the zombie phones. It doesnt hurt to mix and match in this particular way just a little bit but be sure you understand what a modem bootloader flash and a firmware flash are and read around a bit to make sure theres no red flags and i have never went backwards more than say one version of android. But i DON'T EVER UPDATE MODEM UNLESS THERES NO OPTION TO DO IT SEPERATE AND IVE DECIDED ITS TIME TO MOVE ON to the newer set of roms that has presented itself. Good luck
I was curious if this worked for you because i just got my note 10 plus today.

Zaraio said:
Dear readers,
I tried to root my Note 10 plus (Dual SIM) via modifiying the firmware with the magisk manager, later on I have realized that I have downloaded and tried to install a not supported version of the firemware on my device.
Now I am struggling to flash a blank firmware, to revive my phone, but every time I am trying to flash a firmware that is made for my Note 10 plus version (SM-N975F [dual SIM] Germany), odin stucks while flashing and my phone reports a not valid version, that was tried to be installed.
Information:
-My phone shows me on the download mode (SM-N975F)
-I have downloaded and tried to flash the firmware for SM-N975F (Android 9)
-My Android version, before trying to root my device was Android 10 (June update)
-And I have removed the OEM lock,
download mode shows, while odin is stuck: SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4, BINARY: 1
Pit_flash_binary – Unsupported Version.
Odin information:
<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.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 8350 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> uh.bin
<ID:0/004> vbmeta.img
<ID:0/004> boot.img
Has it to do something with the dual SIM variant, what can I do?
I’m so thankful for every answer
Click to expand...
Click to collapse
What happened now. did you fixed it...