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.
Related
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?
Hello,
I am unable to flash stock firmware back to my J200GU with Odin since it always gives me a fail.
So I was trying to flash directly on TWRP or ADB sideload but I always get an error with my zip firmwares.
Does anyone knows where to get the zip firmwares ready for ADB sideload or TWRP?
Sorry if it is a stupid question but I am really newb on this.
Thanks.
use noblerom/hydrarom meta-inf folder in your rom.
RevolverRz said:
use noblerom/hydrarom meta-inf folder in your rom.
Click to expand...
Click to collapse
I have tried what you recomended and TWRP proceeds to install hydrarom, however it is installed very fast and when it reboots i am stuck at bootloop. I believe it has sucessfully installed hydra but not the stock rom I wanted.
I have currently no OS on my phone or any firmaware so my guess is that to be able to install this custom roms (hydra and noble) i need to already have a stock firmware an this will be just an add on. Correct me if I am wrong.
Are the firmwares from SAMMOBILE ready to be used on TWRP? I am starting to think the are not to be used on TWRP but ODIN instead, but ODIN always gives me a fail. SO my question is: IS there a way to make roms downloaded from SAMMOBILE install on TWRP or adb sideload? Any guide about this?
Thanks. I appreciate any help since I have my J2 completly useless now
Can you post your Odin log?
or use the 4 files repair firmware.
https://www.androidfilehost.com/?fid=24407100847293886
RevolverRz said:
Can you post your Odin log?
or use the 4 files repair firmware.
https://www.androidfilehost.com/?fid=24407100847293886
Click to expand...
Click to collapse
Just tried the repair files and got this error on ODIN:
<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.1203)..
<ID:0/004> File analysis..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any more suggestions?
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
Means this rom is not for you j200gu.
Use the most recent version of rom from here..
http://updato.com/firmware-archive-select-model?q=SM-J200GU&rpp=15&order=date&dir=desc&exact=1
pic upload edit
This is my phone. It was bought in Thailand and its dual sim. I am not sure which is the correct firmware for my phone since its dual sim. Can anyone guide me?
RevolverRz said:
Can you post your Odin log?
or use the 4 files repair firmware.
https://www.androidfilehost.com/?fid=24407100847293886
Click to expand...
Click to collapse
Thank you! Finally!
I have tried flashing using just the AP file instead of all 4 files and it worked. When I tried to use the 4 files together in Odin it failed but instead using only the AP I was able to install the firmware and get a PASS.
Thanks alot for all the help in this forum
sushyoshi said:
Thank you! Finally!
I have tried flashing using just the AP file instead of all 4 files and it worked. When I tried to use the 4 files together in Odin it failed but instead using only the AP I was able to install the firmware and get a PASS.
Thanks alot for all the help in this forum
Click to expand...
Click to collapse
Glad to hear that
FRP/FAP Locked
RevolverRz said:
Glad to hear that
Click to expand...
Click to collapse
I accidentally turned off the oem unlocking in dev options(couple of hours earlier) and then when i tried to change my emoticon pack it says FAP Lock. Thank you so much!!! :good: :highfive: (I use Samsung J200GU)
my a3 was having issues, and after a few mistakes i ended up with no os on the phone, TWRP is installed.
Ive tried countless times to flash a stock ROM using odin and im just about ready to pull my hair out.
heres whats on my screen when in download mode:
current binary: samsung official
system status: custom
FRP lock: off
secure download : enabled
CCIC: S2MU004
warranty void: 1 (0x030c)
RP SWREV : B5 K3 S3
this is all the stuff from ODIN:
<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.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 4287 M
<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> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and when i try to flash the error on my phone is SW REV. CHECKFAIL (BOOTLOADER) DEVICE 5 BINARY 4
if anyone could help me i would greatly appreciate it, thanks in advance.
Your firmware which you trying installing is latest oreo firmware with all latest secury patches? I had similar issue when my a3 had installed oreo with all updates and i was trying to install older oreo firmware and odin failed everytime. Then i decided to download latest oreo firmware and latest firmware flashed without any issues.
Try latest firmware it will work and donot play with pit just flash firmware bl cp ap and simple scs instead of home scs
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
Try latest firmware it will work and donot play with pit just flash firmware bl cp ap and simple scs instead of home scs
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.
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