I have previously successfully installed CWM (using Odin) and flashed two version of the GENNXT ROM 4.1.2 using CWM on my i9082L. However, I have not been able to flash leaked 4.2.2 (using Odin) and now I can't flash the official 4.2.2 (using Odin) either. Any ideas? 4.2.2 not compatible with i9082L?
Thanks
Update:
Oh, and I now can't get back into 4.1.2 either. Did a nand restore: stuck at Samsung logo. Was able to flash CWM again using Odin and flashed 4.1.2 GENNEXT: stuck at Samsung logo. Does the 4.2.2 update repartition? If so, will flashing official 4.1.2 using Odin get me back into my phone? Am downloading 4.1.2 Odin package now.
Using Odin to flash official 4.2.2 results in this:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9082XXUBMGA_I9082OXEBMGA_I9082XXUBMGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> vc-firmware.img
<ID:0/011> NAND Write Start!!
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response from boot-loader
<ID:0/011> boot.img
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response from boot-loader
<ID:0/011> recovery.img
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response from boot-loader
<ID:0/011> BcmCP.img
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response from boot-loader
<ID:0/011> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
And flashing the leaked 4.2.2 results in this:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOT_I9082XXUBMF2_REV05.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9082XXUBMF2_871997_REV05_user_mid_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9082XXUBMF2_REV05.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9082OXABMF2_871997_REV05_user_mid_noship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> BcmBoot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Finished downloading 4.1.1 stock and tried to flash using Odin:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9082XXAMF7_I9082ODDMF3__I9082XXAME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Do I need a 4.1.2 pit file? If so, can someone share?
Thanks!
The 4.2.2. Release by samsung is not supported by 9082L model and it's only for 9082 model .
Just flash back to official 4.1.2 rom of ur fone model which is 9082L through pc odin then after process completes just goto Stock recovery <3e> and wipe data and factory reset from there then u able to bootup ur fone as normal again .
Sent from my GT-I9082 using Tapatalk 2
balliboxer said:
The 4.2.2. Release by samsung is not supported by 9082L model and it's only for 9082 model .
Just flash back to official 4.1.2 rom of ur fone model which is 9082L through pc odin then after process completes just goto Stock recovery <3e> and wipe data and factory reset from there then u able to bootup ur fone as normal again .
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. So I'll try to flash the 4.1.2 stock firmware I am downloading right now through Odin.
Interestingly, your 4.1.2 GENNEXT roms worked flawlessly on my i9082L. I'll keep using your latest 4.1.2 rom than for the time being, until Samsung releases a 4.2.2 for the 9082L (and maybe you will make a ROM?).
Solved
rikponne said:
Thanks. So I'll try to flash the 4.1.2 stock firmware I am downloading right now through Odin.
Interestingly, your 4.1.2 GENNEXT roms worked flawlessly on my i9082L. I'll keep using your latest 4.1.2 rom than for the time being, until Samsung releases a 4.2.2 for the 9082L (and maybe you will make a ROM?).
Click to expand...
Click to collapse
I managed to flash i9082L 4.1.2 firmware through Odin, and my phone is working again. Thanks for the advice!
Is there anything against flashing your 4.1.2 GENNEXT Rom over this? I have done it before in the past, as mentioned, and it has been running fine as far as I have been able to tell.
I want to know can I have permanent cwm on my galaxy grand after root?
Sent from my GT-I9082 using xda premium
Hey sir I want to knw can I have a nice flare and light effect in my galaxy grand?
Sent from my GT-I9082 using xda premium
---------- Post added at 12:59 PM ---------- Previous post was at 12:50 PM ----------
balliboxer said:
The 4.2.2. Release by samsung is not supported by 9082L model and it's only for 9082 model .
Just flash back to official 4.1.2 rom of ur fone model which is 9082L through pc odin then after process completes just goto Stock recovery <3e> and wipe data and factory reset from there then u able to bootup ur fone as normal again .
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Balliboxer can I have nice light and flare effect on my galaxy grand?
Sent from my GT-I9082 using xda premium
Anirudh2 said:
Hey sir I want to knw can I have a nice flare and light effect in my galaxy grand?
Sent from my GT-I9082 using xda premium
---------- Post added at 12:59 PM ---------- Previous post was at 12:50 PM ----------
Balliboxer can I have nice light and flare effect on my galaxy grand?
Sent from my GT-I9082 using xda
U r asking on wrong thread bro
Go Here
http://forum.xda-developers.com/showthread.php?p=42541219
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
Related
i tried to flash stock GB 2.3.6 with odin pc
my phone not rooted
when i connected it via odin and flash
it stop here
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8150JPLM7_I8150OJPLM4_I8150XXLMB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
no more
what can i do with this problem ????
U need to use odin v 4.43
Anyway here's a how to flash via odin
http://forum.xda-developers.com/showthread.php?t=1467128
From My GWonder
Previous versions of Odin 4.43 were reported with problems...thatswhy you will have to use Odin 4.43 in order to flash rom or recovery too...otherwise it may get messy....
Sent from my GT-I8150 using xda premium
How can I downgrade from 4.3 to 4.1.2 Galaxy S3 TMobile, I keep on trying but I cant. I keep getting the errors below ...
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999LUVAMB7.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
If you updated via Ota or Odin, you're hosed AFAIK. Unless you used doc's ROM and special kernel setup, that's not possible to go back
Sent from my SGH-T999L using Tapatalk
I used this from Doc's (T999NUVUBMK7_T999NTMBBMK7_T999NUVUBMK7_HOME.tar) ... So there is no way to go back?
thetolsonator said:
If you updated via Ota or Odin, you're hosed AFAIK. Unless you used doc's ROM and special kernel setup, that's not possible to go back
Sent from my SGH-T999L using Tapatalk
Click to expand...
Click to collapse
You can only downgrade by flashing a 4.1.2 rom with custom recovery.. And your warranty bit will get tripped
Sent from my SGH-M919 using Tapatalk
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
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.