Hi
Got a Hong Kong 16GB Note 3 SM-N9005 which someone has attempted to flash with N9005XXUBMJ3_N9005OXABMJ3_N9005XXUBMJ2_HOME.tar.md5 in ODIN which obviously failed because of different region, now it's stuck in download mode. Trying to flash back to the only stock ZHU Hong Kong firmware available N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar fails in ODIN, Kies firmware recovery fails as well.
any suggestions?
ODIN:
<ID:0/033> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/033> Odin v.3 engine (ID:33)..
<ID:0/033> File analysis..
<ID:0/033> SetupConnection..
<ID:0/033> Initialzation..
<ID:0/033> Get PIT for mapping..
<ID:0/033> Firmware update start..
<ID:0/033> SingleDownload.
<ID:0/033> NON-HLOS.bin
<ID:0/033> NAND Write Start!!
<ID:0/033> aboot.mbn
<ID:0/033> FAIL! (Auth)
<ID:0/033>
<ID:0/033> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone when flashing with ODIN or Kies
SW REV CHECK FAIL : [abort]Fused 2 > Binary 1
etoko said:
Hi
Got a Hong Kong 16GB Note 3 SM-N9005 which someone has attempted to flash with N9005XXUBMJ3_N9005OXABMJ3_N9005XXUBMJ2_HOME.tar.md5 in ODIN which obviously failed because of different region, now it's stuck in download mode. Trying to flash back to the only stock ZHU Hong Kong firmware available N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar fails in ODIN, Kies firmware recovery fails as well.
any suggestions?
ODIN:
<ID:0/033> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/033> Odin v.3 engine (ID:33)..
<ID:0/033> File analysis..
<ID:0/033> SetupConnection..
<ID:0/033> Initialzation..
<ID:0/033> Get PIT for mapping..
<ID:0/033> Firmware update start..
<ID:0/033> SingleDownload.
<ID:0/033> NON-HLOS.bin
<ID:0/033> NAND Write Start!!
<ID:0/033> aboot.mbn
<ID:0/033> FAIL! (Auth)
<ID:0/033>
<ID:0/033> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone when flashing with ODIN or Kies
SW REV CHECK FAIL : [abort]Fused 2 > Binary 1
Click to expand...
Click to collapse
i am currently having the same phone model and same problem with you at the moment. Stuck at the Odin mode screen. I've been working on it in the last 5 - 6 hours but still cant file the solution. Please anyone help?
blackj30 said:
i am currently having the same phone model and same problem with you at the moment. Stuck at the Odin mode screen. I've been working on it in the last 5 - 6 hours but still cant file the solution. Please anyone help?
Click to expand...
Click to collapse
I had a silmarly issue with my N9005 but UK version. I flashed ITV (Italy) firmware and was stuck on Download Mode.
I have now managed to restore my phone back to UK (BTU) factory firmware.
1) Boot in Recovery Mode (Power Off, Vol+ & Home + Power On)
- Wipe Date/Factory Reset
- Wipe Cache
2) Boot into Download Mode (aka ODIN MODE) (Power Off, Vol- & Home + Power On)
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE
Note: REACTIVIATION LOCK: OFF - This must be off or you can not perform a restore.
3) Using Odin to flash your stock firmware - ODIN flash will fail
4) Using Kies 3 beta go to 'Tools -> Firmware Upgrade and Initalisation' (Follow the instructions on the screen, your will need your S/N of the phone) - You should now be back to factory firmware.
toker_X1 said:
I had a silmarly issue with my N9005 but UK version. I flashed ITV (Italy) firmware and was stuck on Download Mode.
I have now managed to restore my phone back to UK (BTU) factory firmware.
1) Boot in Recovery Mode (Power Off, Vol+ & Home + Power On)
- Wipe Date/Factory Reset
- Wipe Cache
2) Boot into Download Mode (aka ODIN MODE) (Power Off, Vol- & Home + Power On)
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE
Note: REACTIVIATION LOCK: OFF - This must be off or you can not perform a restore.
3) Using Odin to flash your stock firmware - ODIN flash will fail
4) Using Kies 3 beta go to 'Tools -> Firmware Upgrade and Initalisation' (Follow the instructions on the screen, your will need your S/N of the phone) - You should now be back to factory firmware.
Click to expand...
Click to collapse
Hi, i can't go in to stock recovery. And when i did Firmware upgrade, downloaded the firmware, then went to emergency recovery, after a while, it fail again.
blackj30 said:
Hi, i can't go in to stock recovery. And when i did Firmware upgrade, downloaded the firmware, then went to emergency recovery, after a while, it fail again.
Click to expand...
Click to collapse
same problem here :crying:
after i put my s/n its says its not good
ARIEL80 said:
same problem here :crying:
after i put my s/n its says its not good
Click to expand...
Click to collapse
One final try would be to use Odin and flash the Kernel and CSC files for your stock firmware if this fails then you probably need to take it Samsung Repair Center.
toker_X1 said:
One final try would be to use Odin and flash the Kernel and CSC files for your stock firmware if this fails then you probably need to take it Samsung Repair Center.
Click to expand...
Click to collapse
now its ok with the keis, but when its start to upgrad with the keis' its fail..
i try what you say now
If I'm not mistaken, attempting to flash MJ3 has upgraded the bootloader thefore the MI7 firmware will not flash because it has old bootloader? (aboot.mbn(?)
but there is currently no Hong Kong firmware higher than MI7, therefore its ****ed (Kies emergency recovery tries to flash MI7.
No other region firmware flashing.
No firmware downgrading.
What a joke Samsung.
etoko said:
If I'm not mistaken, attempting to flash MJ3 has upgraded the bootloader thefore the MI7 firmware will not flash because it has old bootloader? (aboot.mbn(?)
but there is currently no Hong Kong firmware higher than MI7, therefore its ****ed (Kies emergency recovery tries to flash MI7.
No other region firmware flashing.
No firmware downgrading.
What a joke Samsung.
Click to expand...
Click to collapse
Yup. So if I flash the stock bootloader together with stock rom it should work?
no.
NISIM2337 said:
no.
Click to expand...
Click to collapse
No it didn't work!!! What should i do now?
From Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_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> BL_N9005ZHUBMI7_1626679_REV03_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_N9005ZHUBMI7_1626679_REV03_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_N9005XXUBMI5_REV03_CL1252918.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_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<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> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yeah the aboot.mbn fail.
On the device, it said "SW REV CHECK FAIL: [aboot]Fused 2 > Binary 1"
Please help. Or I have to use new BL with stock AP, CSC, CP? I think it will hard brick the phone?? hehe
blackj30 said:
No it didn't work!!! What should i do now?
From Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_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> BL_N9005ZHUBMI7_1626679_REV03_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_N9005ZHUBMI7_1626679_REV03_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_N9005XXUBMI5_REV03_CL1252918.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_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<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> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yeah the aboot.mbn fail.
On the device, it said "SW REV CHECK FAIL: [aboot]Fused 2 > Binary 1"
Please help. Or I have to use new BL with stock AP, CSC, CP? I think it will hard brick the phone?? hehe
Click to expand...
Click to collapse
You have a brick until the stock firmware is updated with the new bootloader.
ultramag69 said:
You have a brick until the stock firmware is updated with the new bootloader.
Click to expand...
Click to collapse
true hehe it's one of the ways to keep my phone brandnew
blackj30 said:
true hehe it's one of the ways to keep my phone brandnew
Click to expand...
Click to collapse
You simply have to flash the firmware MJ3 UK and you're done.
It 'happened to me, I resolved as I told you.
frilli said:
You simply have to flash the firmware MJ3 UK and you're done.
It 'happened to me, I resolved as I told you.
Click to expand...
Click to collapse
i've done that to get to my current situation. Now basically i get the same error message on both phone and odin if i flash any kind of rom:
aboot.mbn fail
sw rev check fail
any other thing that i can do or i really have to wait for my stock rom update to launch?
pathetic that you have a new good phone but cant use
blackj30 said:
i've done that to get to my current situation. Now basically i get the same error message on both phone and odin if i flash any kind of rom:
aboot.mbn fail
sw rev check fail
any other thing that i can do or i really have to wait for my stock rom update to launch?
pathetic that you have a new good phone but cant use
Click to expand...
Click to collapse
You have 3 options:
1) Take to Samsung Repaire Center - They will charge you (in the UK its £29.99 for software faults)
2) Wait until HK Firmware gets upgraded to MJ3 (as Samsung doesnt allow downupgrade of Bootloaders)
3) Flash CWM or TWRP and install a custom rom (this will volid warranty)
toker_X1 said:
You have 3 options:
1) Take to Samsung Repaire Center - They will charge you (in the UK its £29.99 for software faults)
2) Wait until HK Firmware gets upgraded to MJ3 (as Samsung doesnt allow downupgrade of Bootloaders)
3) Flash CWM or TWRP and install a custom rom (this will volid warranty)
Click to expand...
Click to collapse
"3) Flash CWM or TWRP and install a custom rom (this will volid warranty)"-THAT OPTION DONT WORK
Have you tried flashing back to the stock HONG KONG ODIN tar file?
that should make it work again.
AllGamer said:
Have you tried flashing back to the stock HONG KONG ODIN tar file?
that should make it work again.
Click to expand...
Click to collapse
I did try flash HK TGY firmware back in many ways, but still not working. I think I will wait for TGY firmware to be upgraded. It will take forever.
blackj30 said:
I did try flash HK TGY firmware back in many ways, but still not working. I think I will wait for TGY firmware to be upgraded. It will take forever.
Click to expand...
Click to collapse
did you try flash the full firmware,not 1 file,that should be 5 files,including the bootloader and pit file.download from the chinese address.
Related
I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl3.mbn
<ID:0/008> rpm.mbn
<ID:0/008> aboot.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3
I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english
C4scade said:
I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1
In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3
I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english
Click to expand...
Click to collapse
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Ricardo_Is said:
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Click to expand...
Click to collapse
Sorry for my bad english but
i also got the same error with odin :
aboot.mbn
FAIL! (Auth)
got no sound and got a black screen when calling mic also not working
flashing custom roms wont fix it any way to install stock i9505 rom without odin or kies ?
's it fixable any ideas ??
Ricardo_Is said:
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Click to expand...
Click to collapse
Man, i don't think that a nandroid backup can solve a binary error.. and yes, i checked the firmware md5, it's ok, it is from sammobile.com
I'd say if you've got aboot fail then your trying to flash older rom on a phone that's had newer rom on it aka Knox already.
Sent from my GT-I9505 using xda app-developers app
Flash the ''i9505 pit'' file on odin in pda. That will fix
DONE!!!
mr.biceps said:
Flash the ''i9505 pit'' file on odin in pda. That will fix
Click to expand...
Click to collapse
Hi
I like to share how I fixed my S4 using ODIN 3.09
1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!
mgolejnik said:
Hi
I like to share how I fixed my S4 using ODIN 3.09
1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!
Click to expand...
Click to collapse
Hi there,
Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??
I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware
Or have I completely misunderstood your resolution/fix?
CarlM34 said:
Hi there,
Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??
I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware
Or have I completely misunderstood your resolution/fix?
Click to expand...
Click to collapse
But I never wrote that I had installed version 4.3 / 4. This is the version which is installed this time: I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar after this I flash CF-Auto-Root-jflte-jfltexx-gti9505.tar and now it is rooted and it is KNOX (but not for long)
Maybe I made a mistake. If so, sorry
...
I MADE MISTAKE!!! I am so sorry for that!!!
I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar it is newest version it's 4.4.2!!! I am sorry again.
I'm Also Having a problem with my samsung s4 gt-i9505 (INS)
i was trying to flash my phone with 4 files of firmware with Odin3 v3.10.6
and while flashing i got this problem
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9500DDUHPE1_REV01_CL1856465_SIGNED.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_ODD_I9500ODDHOJ1_CL5979820_QB6580299_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if you have any solution please reply
I was updating my samsung galaxy grand prime duos (SM-G531H) with kies, not knowing my cable was broken while the updating the phone disconnected and i ended up with a screen saying "firmware upgrade encountered an issue. please select recovery mode in kies and try again" i changed the cable and decided to flash the update with odin... process went through and the phone booted up normal with the new update installed... now i decided to factory reset so i went into the stock recovery and did but it came up with a bunch of errors which i didn't take note of... i flashed twrp and repaired the file system, wiped system and then i flashed the the firmware together with the pit file on odin once more... the phone booted up normal and i was using it and eveything when i put it to charge and came back 10 mins later the phone was off.... when i powered it on it just stays on the "samsung galaxy grand prime" screen and doesn't boot... it doesn't go into recovery anymore it just hangs whe're it says "recovery is not seandroid enforcing" i tried flashing the firmware with odin again but every single time i tried it keeps failing at...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried the repair firmware together with the pit file and it gets stuck at
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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!!
it's been like that for over an hour now... any help would be much appreciated guys.
No
Try with orignal firmware
nihu.46 said:
Try with orignal firmware
Click to expand...
Click to collapse
I tried everything and nothing seems to work
I also get this problem. Does anyone know how to fix it?
Ghettovybz said:
I tried everything and nothing seems to work
Click to expand...
Click to collapse
Remove kies. Reinstall samsung drivers.
Find and flash TWRP 3.0.0 with odin ( on recovery is not SEAndroid enforcing hold volume up and home for 5-10 seconds. Also flash the Custom Kernel by eyeless95 on the forum, its sepermissive.
u0aol said:
Remove kies. Reinstall samsung drivers.
Find and flash TWRP 3.0.0 with odin ( on recovery is not SEAndroid enforcing hold volume up and home for 5-10 seconds. Also flash the Custom Kernel by eyeless95 on the forum, its sepermissive.
Click to expand...
Click to collapse
What about for SM-G530H?
Do u have the link for the kernel?
After installing kernel what should I do then?
Two ways. Find stock rom in Sammobile and install via Odin (newest). Or try once again install it via Kies. You sould can restore it with Kies, but dont plug phone to computer. Write down S/N or something like that (it's under battery) and model, and Kies will download system
argounaut said:
What about for SM-G530H?
Do u have the link for the kernel?
After installing kernel what should I do then?
Click to expand...
Click to collapse
I have a g531h so I'm not sure. I'm below ten posts so i cant post links.
There are kernels and recoverys in the development section that work fine for your phone .
Can someone help me with my issue. Im getting error "sw rev. check fail. device: 2, binary: 1" when flashing back to 6.0.1 stock rom.
This is the log from Odin. I accidentally flashed a 7.0 stock firmware and cannot get back to 6.0.1 anymore.
my model SM-G935FD, came from Dubai UAE manufactured in Vietnam.
My phone frequently freezes on samsung logo when booting up and restarts then goes to bootloop.
My phone has also heating on the right front side of the screen when booting up. Is my phone having fried motherboard already?
<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> 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/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
U probably updated, bootloader and cp.Flash again 7.0,and then flash twrp,and install custom 6.0.1.
As mentioned, your 7.0 before you tried flashing back to 6.0.1 was with bootloader ending DRA#, that's why you have this error.
MS420 said:
U probably updated, bootloader and cp.Flash again 7.0,and then flash twrp,and install custom 6.0.1.
Click to expand...
Click to collapse
Thank you for the response. yes I wento to 7.0 but I dont like its because 7.0 gives me random freezes. When can i get custom 6.0.1 rom for s7 edge?
Cholek3 said:
As mentioned, your 7.0 before you tried flashing back to 6.0.1 was with bootloader ending DRA#, that's why you have this error.
Click to expand...
Click to collapse
Thank you for the response, Yes I think having an newer version of Bootloader wont let you flash back to the previous version because of that error :
You still can flash back, but you need to use newest bootloader and modem files, where CSC and AP files can be from older firmware. I got back to 6.0.1 that way, although vibration no longer works. It works only on 7.0
Jefjefy88 said:
Thank you for the response. yes I wento to 7.0 but I dont like its because 7.0 gives me random freezes. When can i get custom 6.0.1 rom for s7 edge?
Click to expand...
Click to collapse
Rom section,and watch for older versions.
Cholek3 said:
You still can flash back, but you need to use newest bootloader and modem files, where CSC and AP files can be from older firmware. I got back to 6.0.1 that way, although vibration no longer works. It works only on 7.0
Click to expand...
Click to collapse
My phone wont let me get into the Setup stage, it automatically freezes on Samsung logo whatever official rom I install. Do you think its a hardware issue?
There is a possibility, but you have to flash the newest possible firmware with the CSC version you had before it stopped working (so before first flash).
"Only officially released binaries..." error and I can't flash the stock firmware
I sort of bricked my phone (i think this is considered bricked anyway) after rooting it and getting the "only official binaries allowed" message. I tried to flash the stock firmware via odin, and it was stuck at "NAND write start" with the box reading "set partition". The only options ticked in odin were f.reset time and auto reboot. I'm really scared I've messed it up permanently somehow, please help if you can.
Model: SM-G950F, Exynos (I don;t know what other info to include or how to find that info without my phone on, if anything is needed, please tell me and Ill try and find it)
LOG:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<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> SingleDownload.
<ID:0/005> sboot.bin.lz4
<ID:0/005> NAND Write Start!!
UPDATE: tried again, three lines were added
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I also tried it on another machine, got the same thing including those three lines but in a different order:
<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> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007>Complete(write) operation failed.
<OSM> All threads complete. (succeed 0 / failed 1)
<ID:0/007> Removed!!
In addition, I'm not certain if this was there before, but a line in my download mode says:
"SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 3, BINARY: 2"
I saw a similar line on one of the threads, so I realise that may be important
Thanks for any help in advance
--End Update
Exact steps taken to root the phone:
I decided to root my phone via magisk. I installed TWRP via odin, didn't quite immediately boot into recovery, so I flashed it once more, and this time managed to. I kept it read only, and then formatted the phone via TWRP, rebooted into recovery again, flashed the no-verity file (no-verity-opt-encrypt-6.0). I did not flash that RMM file I've seen after looking for solutions, and then rebooted my phone. It worked fine, magisk was installed, I went through the initial setup, restored my stuff from a backup etc. and then, I tried to install the xposed module in the magisk repo. Rebooted, and got the whole "Only official released binaries are allowed to be flashed" message and couldn't boot up past the initial "samsung galaxy 8 - powered by android" screen, nor into my recovery. So, I went looking for solutions, and did something dumb. I tried to flash this file here (Nougat G950FXXU1AQL5 bootloader) before restoring the original firmware. I'm not sure what problems that might have caused, and the flash failed anyhow, but I don't know still. Moving on,
twinsniper said:
I sort of bricked my phone (i think this is considered bricked anyway) after rooting it and getting the "only official binaries allowed" message. I tried to flash the stock firmware via odin, and it was stuck at "NAND write start" with the box reading "set partition". The only options ticked in odin were f.reset time and auto reboot. I'm really scared I've messed it up permanently somehow, please help if you can.
Model: SM-G950F, Exynos (I don;t know what other info to include or how to find that info without my phone on, if anything is needed, please tell me and Ill try and find it)
LOG:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<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> SingleDownload.
<ID:0/005> sboot.bin.lz4
<ID:0/005> NAND Write Start!!
UPDATE: tried again, three lines were added
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I also tried it on another machine, got the same thing including those three lines but in a different order:
<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> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007>Complete(write) operation failed.
<OSM> All threads complete. (succeed 0 / failed 1)
<ID:0/007> Removed!!
In addition, I'm not certain if this was there before, but a line in my download mode says:
"SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 3, BINARY: 2"
I saw a similar line on one of the threads, so I realise that may be important
Thanks for any help in advance
--End Update
Exact steps taken to root the phone:
I decided to root my phone via magisk. I installed TWRP via odin, didn't quite immediately boot into recovery, so I flashed it once more, and this time managed to. I kept it read only, and then formatted the phone via TWRP, rebooted into recovery again, flashed the no-verity file (no-verity-opt-encrypt-6.0). I did not flash that RMM file I've seen after looking for solutions, and then rebooted my phone. It worked fine, magisk was installed, I went through the initial setup, restored my stuff from a backup etc. and then, I tried to install the xposed module in the magisk repo. Rebooted, and got the whole "Only official released binaries are allowed to be flashed" message and couldn't boot up past the initial "samsung galaxy 8 - powered by android" screen, nor into my recovery. So, I went looking for solutions, and did something dumb. I tried to flash this file here (Nougat G950FXXU1AQL5 bootloader) before restoring the original firmware. I'm not sure what problems that might have caused, and the flash failed anyhow, but I don't know still. Moving on,
Click to expand...
Click to collapse
For starters use latest Odin 3.13.1 it supports the lz4 compression.
Device 3 binary 2 error means you are trying to flash early version firmware use the same or later version firmware
Oh wow, okay, I didn't realize I was flashing an earlier firmware, it's one I flashed earlier in the year and still the latest on updato for vodafone, but yeah there was an update to that. Thank you, so, so much. I was terrified and up till like 5 am last night trying to fix it, sick to my stomach etc. thinking I'd permanently messed things up.
For anyone reading this in the future, as of right now, the latest Vodafone SM-G950F Firmware (Australia) on updato is not the latest firmware (from what I understand you don't want to flash anything with XXU2. you want XXU3), but if you go to sammobile or use samfirm (helluva lot faster download speed for the record) you can get the latest firmware.
Anyway, thanks a lot spawnlives, really appreciate the help, and its good to know for the future If i ever do anything like this again what that message means.
twinsniper said:
Oh wow, okay, I didn't realize I was flashing an earlier firmware, it's one I flashed earlier in the year and still the latest on updato for vodafone, but yeah there was an update to that. Thank you, so, so much. I was terrified and up till like 5 am last night trying to fix it, sick to my stomach etc. thinking I'd permanently messed things up.
For anyone reading this in the future, as of right now, the latest Vodafone SM-G950F Firmware (Australia) on updato is not the latest firmware (from what I understand you don't want to flash anything with XXU2. you want XXU3), but if you go to sammobile or use samfirm (helluva lot faster download speed for the record) you can get the latest firmware.
Anyway, thanks a lot spawnlives, really appreciate the help, and its good to know for the future If i ever do anything like this again what that message means.
Click to expand...
Click to collapse
Glad you got sorted out.
I am aware of the new firmware with ver3 bootloader it has been out for a while. Samfirm is probably the best for latest versions. I am using XSA (Australian unbranded) firmware i try not to use branded firmware like Telstra,Optus or Vodafone.
After rooting my Samsung Galaxy S8 I accidentally wiped all data including the OS. I'm completely new to this and wish for some detailed help from a professional.
Odin keeps giving a fail at param.bin using different ROMs. I've heard it might be the bootloader version that's incompatible but I'm not sure what to do and which bootloader version I have. I'm using the same firmware I've downloaded from sammobile before for my model number SM-G950F and even an extra one with Android pie on it, the same android version before this happened, but to no avail. Here is the log from Odin. Appreciate all help since I wiped the data after being stuck in the bootloader with a Samsung logo on it (alone) but after wiping everything it's the screen before it with the samsung logo AND "powered by android".
It may be relevant to note that I'd rather use Odin than an SD-card.
Edit: I checked the download screen on my s8 and found an error saying that SW REV. Failed Bootloader device 6 binary 4. I checked next to SWREV: B:6
So it apparently is a binary incompatibility for bootloader. Now my question is where can I find the suitable binary? All I see while downloading firmware is the model version and the date but not the binary.
<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> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5716 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> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance!
It worked!
So as a beginner's guide you need to check the error code given after failing in Odin in the download screen in the phone itself at the end of these codes.
My error code was as mentioned in the edit that I was trying to install a firmware with a binary version 4 whereas my device's version is 6. To find the correct firmware version you need to look for the part in the PDA code where it says U6 or U5 or U4 (binary version 6, 5 or 4 as examples respectively).
PDA code is for example: G950FXXU6DSK9 as in my case. This is different from the CSC code, you can find both in the sammobile website. You just have to compare your device's binary version found next to SWREV and identified with a B up among the codes in the download screen of your phone (after holding volume down power and bixby at the same time).
That's it. Special thanks to ZeroXO who contributed to the resolution of the issue and was very helpful ^^
Kindly share your experiences after you rooted your device. What are the pros n cons?