So I was trying to rollback to 4.4.4 from the latest Att update 5.0.1 that we got a week ago. Now my phone is stuck in Download mode and does not reboot. I even tried the Keis method with no luck. Still keeps going back to this screen with this error.
I kno this might not be much help, but with the latest AT&T update 5.0.1 COC5, I think you can't rollback to 4.4.4
I kno 100% Verizon latest 5.0.1 you can't rollback either...
But for all these reasons is why I'm still on 4.4.4 NK3 update had this update since day one I bought this phone
But hope the best luck to you... you might have to install 5.0.1 again
Sent from my SAMSUNG-SM-N910A using Tapatalk
Yes I hope someone can please help.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
If I need to return phone to fix? Who should I deal with AT&T or Samsung. I was going to blame it on the latest software update.
Sent from my iPod touch using Tapatalk
borijess said:
If I need to return phone to fix? Who should I deal with AT&T or Samsung. I was going to blame it on the latest software update.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
Flash the new firmware back onto your phone. ..
I could not flash anything. It just kept failing. I even tried kies method with no success.
So I called AT&T and blamed it on there latest update. Took it to an AT&T warranty store and they gave me a new note 4. They tried to flash with there software and had no success either.
So I walked out with new note 4. So beware people do not try to rollback if you accepted att latest update. You will brick device. [emoji20]
hi guys,
looks like i just did the same thing. I was trying to downgrade my wife's AT&T note 4 since she's been having tons of issues with this phone (this is actually her second note 4). anyways, long story short, i am now stuck at the same screen you are at. i've tried odin 3.09 and downloaded the COC4 files (4 files, BL, AP, CP, and CSC). and when i run odin i get an error message, and it fails to install.
here's the message i get:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910AUCU1COC4_CL4160876_QB4512549_REV00_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> AP_N910AUCU1COC4_CL4160876_QB4512549_REV00_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> CP_N910AUCU1COC4_CL4160876_QB4512549_REV00_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_ATT_N910AATT1COC4_CL4160876_QB4512549_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can anyone help me out here? should i start my own thread?
thanks in advance
Try just flashing system and nothing else
thanitos said:
Try just flashing system and nothing else
Click to expand...
Click to collapse
sorry for the dumb question, but which file is that?
Won't work. I had to return phone to att. They gave me a new one. I told them the latest update killed my phone.
Sent from my SAMSUNG-SM-N910A using xda premium
itsjustlenny said:
sorry for the dumb question, but which file is that?
Click to expand...
Click to collapse
Try with out BL file.
senseless returns like these two are what makes modders look bad in their eye; on the other hand if the bootloader was unlocked and they didn't lock it down so tight they wouldn't have these issues as well
Making up a lie and committing Fraud is not something I recommend doing.
It sucks but if you mess around with your device and ruin it/can't fix it then take responsibility for what you did.
davidstech11 said:
Making up a lie and committing Fraud is not something I recommend doing.
It sucks but if you mess around with your device and ruin it/can't fix it then take responsibility for what you did.
Click to expand...
Click to collapse
Get off your high horse. If att didn't lock this phone up so tight we wouldn't have these issues. If you don't want to do it don't go around judging others.
Sent from my SAMSUNG-SM-N910A using xda premium
borijess said:
Get off your high horse. If att didn't lock this phone up so tight we wouldn't have these issues. If you don't want to do it don't go around judging others.
Sent from my SAMSUNG-SM-N910A using xda premium
Click to expand...
Click to collapse
If you did your homework, you would have known not to downgrade. It's irresponsible people like yourself that have caused these phones to be locked down. It's also the reason we are now paying so much for them. And finally, davidstech11 was accurate with his comment. Course it's not human nature to do the right thing which is what makes those that do stand out from the rest.
are there a solution i have the same problem n910a
firebird7880 said:
are there a solution i have the same problem n910a
Click to expand...
Click to collapse
Read this whole thread. http://forum.xda-developers.com/showthread.php?t=3335880
Sent from my SM-N910T using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
itsjustlenny said:
hi guys,
looks like i just did the same thing. I was trying to downgrade my wife's AT&T note 4 since she's been having tons of issues with this phone (this is actually her second note 4). anyways, long story short, i am now stuck at the same screen you are at. i've tried odin 3.09 and downloaded the COC4 files (4 files, BL, AP, CP, and CSC). and when i run odin i get an error message, and it fails to install.
here's the message i get:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910AUCU1COC4_CL4160876_QB4512549_REV00_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> AP_N910AUCU1COC4_CL4160876_QB4512549_REV00_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> CP_N910AUCU1COC4_CL4160876_QB4512549_REV00_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_ATT_N910AATT1COC4_CL4160876_QB4512549_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can anyone help me out here? should i start my own thread?
thanks in advance
Click to expand...
Click to collapse
You're using the wrong files. You must use the same OS files that your phone is on or newer OS files. It's showing that the authorization is not letting it write to the system because it's not the right files.
Sent from my SM-N910T using Tapatalk
Related
Hello, I have been trying to fix my samsung galaxy s6 edge for it was damaged by someone in an attempt to unlock the phone.
(Custom binary blocked by FRP Lock) then the phone is not booting anymore, not even charging as well. Just giving boot loop then the error message on the upper left corner.
Samsung said they don't have the S/W for my device since it has been purchased in another country. I'm from the PH and the phone came from US(T-mobile)
Model #- Sm-G925T
Now I'm trying to Flash Stock ROM and it's giving me this error. I've tried multiple .tar.md5 file and I don't think the firmwares are the problem.
I'm guessing that ROM that he flashed is G925TUVU3EPD1(as shown in Recovery mode)
I have been trying to do this for the whole day. I am desperate for help. I never had a smartphone for 2 years after my Samsung GS3 got lost until when Someone sent me this as a gift.
Here is the Odin Log.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_G925TUVU1AOCG_CL4351282_QB4489203_REV02_user_lo w_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> CP_G925TUVU1AOCG_CL4351282_QB4489203_REV02_user_lo w_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_TMB_G925TTMB1AOCG_CL4351282_QB4489203_REV02_us er_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> AP_G925TUVU1AOCG_CL4351282_QB4489203_REV02_user_lo w_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I appreciate ANYONE who will help. Thank you in advance.
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?
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
Hi,
I tried to downgrade my Samsung Note 10+ Hong Kong Snapdragon edition. I am able to unlock the bootloader through developer mode, and during downgrading, I was able to:
Downgrade to release 2020-09-27 - Which was also One UI 2.5
https://www.sammobile.com/samsung/g...e/SM-N9750/TGY/download/N9750ZSU3DTI1/372284/
Attempted to downgrade to release 2020-06-23, but got this error: SW REV CHECK FAIL
https://www.sammobile.com/samsung/g...e/SM-N9750/TGY/download/N9750ZSU2CTF1/346913/
Is it possible to downgrade to One UI 2.1 somehow?
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> 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/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 8480 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> abl.elf
<ID:0/007> xbl.elf
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You will see from your post that the UI 2.5 has SU3 in its name and that the UI 2.1 has SU2 in its name. That is the bootloader version number and you can't go backwards (downgrade) that. So the simple answer would be no. Sorry.
Sent from my SM-N976B using Tapatalk
Painman1963 said:
You will see from your post that the UI 2.5 has SU3 in its name and that the UI 2.1 has SU2 in its name. That is the bootloader version number and you can't go backwards (downgrade) that. So the simple answer would be no. Sorry.
Sent from my SM-N976B using Tapatalk
Click to expand...
Click to collapse
Ah, that's the reason and how I can see it.
I realized there was another release on the 5th of August with SU3, so I tried to install it. It worked, and it came with One UI 2.1! Google Cam is back in business.
https://www.sammobile.com/samsung/g...e/SM-N9750/TGY/download/N9750ZSU3CTH1/363301/
Thanks for your help!
Recoda said:
Ah, that's the reason and how I can see it.
I realized there was another release on the 5th of August with SU3, so I tried to install it. It worked, and it came with One UI 2.1! Google Cam is back in business.
https://www.sammobile.com/samsung/g...e/SM-N9750/TGY/download/N9750ZSU3CTH1/363301/
Thanks for your help!
Click to expand...
Click to collapse
No worries. Glad you sorted it
Sent from my SM-N976B using Tapatalk
Recoda said:
Ah, that's the reason and how I can see it.
I realized there was another release on the 5th of August with SU3, so I tried to install it. It worked, and it came with One UI 2.1! Google Cam is back in business.
https://www.sammobile.com/samsung/g...e/SM-N9750/TGY/download/N9750ZSU3CTH1/363301/
Thanks for your help!
Click to expand...
Click to collapse
Hello, where did you download this software from? Sammobile is slow as hell
Also u use this recovery? With kernel or without? https://forum.xda-developers.com/t/...-4-0-17-snapdragon-n97x0-17-jul-2020.3975603/