Database Users

Hong Kong 16GB Note 3 SM-N9005 softbrick

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.

Note 3 retail failed flash, please help

Hello,
I had Alliance ROM and tried to flash Jasmine 5.0, but the phone restarted before it finished and now the phone only show either the "Samsung Galaxy Note 3" logo or download mode, recovery is gone.
When I try to enter recovery mode, the phone vibrates once and the screen stays black if i release the power button, but keep holding volume up and home.
If i dont release power, it keeps vibrating and a black screen.
I tried restoring to any possible image, MJE, NC2, NC4 and OB6, using Odin 3.09. All fail.
Tried using a Pit file, since the other error states that it cant find a pit file, that also failed.
Odin log is with Pit file:
ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900VVRUEOB6_N900VVZWEOB6_N900VVRUEOB6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Without Pit file:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900VVRUEOB6_N900VVZWEOB6_N900VVRUEOB6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone, it says the following:
odin mode
product name: sm-n900v
current binary: Samsung official
system status: official
knox kernel lock:0x0
knox warranty void:0x0
qualcom secureboot: enable (csb)
AP SWREV: S1, T1, R1, A2, P1
write proctection: Enable
UDC start (this is in red)
MMC: mmc_write fail
odin: flash read failure (This is in red)
That list is the same, no matter what.
Is anything else I can try or this phone just gone?
Please help!:crying:

Anyone??

NeoMorpheus1337 said:
Anyone??
Click to expand...
Click to collapse
Go to either a Verizon Company store or to Best Buy and go to the Samsung experts (at the Samsung section) and have them do a complete flash.
They can flash it to pure stock. There should be no issues since Knox and Warranty fuses are not blown
Just tell them it got knocked off the desk in the middle of an upgrade and the battery popped out.
Sent from my Note 3 via Tapatalk

Damn, thats a good advice and it didnt occur to me before.
I actually called Samsung and after talking to one of their techs, they recommended to send it to them.
Sadly, it will cost 80 bucks, but per one of the devs here, it does looks like a part of knox locked the storage and only a new motherboard can fix this.
Either way, 80 bucks is not that bad, given that the alternative is buying another phone for 250 or so.

Galaxy Prime Bricked?

So, a friend of mine brough me his phone; he told me that it just didn't turn on again and it hasn't no waranty so i decided to try to do something to fix it.
Is not the first time that i worked with samsung phones, so i technically know what to do; i downloaded Odin v3.12, the latest Samsung drivers and the correct firmware
The phone boots inmediately to download mode but it shows that doesn't find some JPG images. The exact text is below:
NO IMAGE: warningmessage.jpg
NO IMAGE: download_image.jpg
ODIN MODE (MULTI CORE DOWNLOAD)
PRODUCT NAME SM-G531m
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
FAP LOCK: OFF
KNOK WARANTY VOID: 0x0
Secure Download: Enable
RP SWREV: S0, L0, M0
I tried to flash an oficial firmware but ODIN tells me that there is no pit partition. I understand that this error means that PIT partition is screwed or something. I have no pit file for this phone so i searched the internet and found the Pit file for the 531F variation. I couldn't find any descriptive information that explains me if there's a diference in the internal memory between 531M and 531F so y decide to take the risk.
What i found is that ODIN give's me error every time y try to flash with de PIT file, saying that there were an error whith the repartition.
<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..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded another versions of ODIN and the only one tha't doesn't give me error is the 3.07 version but the flash process stuck at <ID:0/004> NAND Write Start!!
The only clue that i have is an hipothesis: Maybe the pit file is not the correct one, but more than that, i don't know anything else. The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M.
- is there a chance that some of you could helpme to find a correct pit file?
- could this happend for another reasons rather than a pit partition screwed out?
- is there something else that i should do?
-is this phone bricked?

jhonatann989 said:
So, a friend of mine brough me his phone; he told me that it just didn't turn on again and it hasn't no waranty so i decided to try to do something to fix it.
Is not the first time that i worked with samsung phones, so i technically know what to do; i downloaded Odin v3.12, the latest Samsung drivers and the correct firmware
The phone boots inmediately to download mode but it shows that doesn't find some JPG images. The exact text is below:
NO IMAGE: warningmessage.jpg
NO IMAGE: download_image.jpg
ODIN MODE (MULTI CORE DOWNLOAD)
PRODUCT NAME SM-G531m
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
FAP LOCK: OFF
KNOK WARANTY VOID: 0x0
Secure Download: Enable
RP SWREV: S0, L0, M0
I tried to flash an oficial firmware but ODIN tells me that there is no pit partition. I understand that this error means that PIT partition is screwed or something. I have no pit file for this phone so i searched the internet and found the Pit file for the 531F variation. I couldn't find any descriptive information that explains me if there's a diference in the internal memory between 531M and 531F so y decide to take the risk.
What i found is that ODIN give's me error every time y try to flash with de PIT file, saying that there were an error whith the repartition.
<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..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded another versions of ODIN and the only one tha't doesn't give me error is the 3.07 version but the flash process stuck at <ID:0/004> NAND Write Start!!
The only clue that i have is an hipothesis: Maybe the pit file is not the correct one, but more than that, i don't know anything else. The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M.
- is there a chance that some of you could helpme to find a correct pit file?
- could this happend for another reasons rather than a pit partition screwed out?
- is there something else that i should do?
-is this phone bricked?
Click to expand...
Click to collapse
Download odin from this thread:- https://forum.xda-developers.com/grand-prime/general/tut-how-to-install-xposed-framework-t3508071
And download stock recovery for your device model and add open odin add the stock recovery to pda and flash it.
Note: make sure u have samsung drivers installled and do not add pit file

Owen007 said:
Download odin from this thread:- https://forum.xda-developers.com/grand-prime/general/tut-how-to-install-xposed-framework-t3508071
And download stock recovery for your device model and add open odin add the stock recovery to pda and flash it.
Note: make sure u have samsung drivers installled and do not add pit file
Click to expand...
Click to collapse
Did it, but still have the problem that i described earlier. Odin3 from the thread that you suggested, gives me the above text:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I didn't test with the pit file that i found for the 531F variation
->EDIT: tried to flash the pit file and it didn't work. It says Repartition Failed

jhonatann989 said:
So, a friend of mine brough me his phone; he told me that it just didn't turn on again and it hasn't no waranty so i decided to try to do something to fix it.
Is not the first time that i worked with samsung phones, so i technically know what to do; i downloaded Odin v3.12, the latest Samsung drivers and the correct firmware
The phone boots inmediately to download mode but it shows that doesn't find some JPG images. The exact text is below:
NO IMAGE: warningmessage.jpg
NO IMAGE: download_image.jpg
ODIN MODE (MULTI CORE DOWNLOAD)
PRODUCT NAME SM-G531m
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
FAP LOCK: OFF
KNOK WARANTY VOID: 0x0
Secure Download: Enable
RP SWREV: S0, L0, M0
I tried to flash an oficial firmware but ODIN tells me that there is no pit partition. I understand that this error means that PIT partition is screwed or something. I have no pit file for this phone so i searched the internet and found the Pit file for the 531F variation. I couldn't find any descriptive information that explains me if there's a diference in the internal memory between 531M and 531F so y decide to take the risk.
What i found is that ODIN give's me error every time y try to flash with de PIT file, saying that there were an error whith the repartition.
<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..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded another versions of ODIN and the only one tha't doesn't give me error is the 3.07 version but the flash process stuck at <ID:0/004> NAND Write Start!!
The only clue that i have is an hipothesis: Maybe the pit file is not the correct one, but more than that, i don't know anything else. The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M.
- is there a chance that some of you could helpme to find a correct pit file?
- could this happend for another reasons rather than a pit partition screwed out?
- is there something else that i should do?
-is this phone bricked?
Click to expand...
Click to collapse
odin only works with the correct version is on the device

tran nam hoang said:
odin only works with the correct version is on the device
Click to expand...
Click to collapse
i wrote this:
The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M
Click to expand...
Click to collapse
then i asked for this:
- is there a chance that some of you could helpme to find a correct pit file?
Click to expand...
Click to collapse
If you have a PIT partition for the SM-G531M i will be gratefull if you share it with me
PD: BTW I HAVE the Correct firmware, my problem is PIT partition as i can conclude

Samsung Galaxy S7 Edge stuck in boot mode

I tried to root my phone for the first time. I saw a guide on Youtube and decided why not. It was relatively easy to follow and I am sure I followed it 100% correctly. I managed to see SuperSU, however, it failed to install the proper packages and would always tell me to reboot. Other problems I encountered were Google Play would not open, and every couple of seconds a service would stop working along with it. So I decided to un-root my phone. I found a factory version SM-G395PVPU2APC5, went into download mode, and as of right now it has been stuck here every since. I can alternate between download mode and boot mode but that's about it. I couldn't properly install the factory version because this message pops up every time I try:
ODIN MODE (HIGHSPEED)
PRODUCT NAME: SM-G395P
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FAP LOCK: OFF
WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE
AP SWAEV: B4(2,1,1,1,) K1 S3
SECURE DOWNLOAD: ENABLE
SW REV CHECK FAIL: [system]Fused 3 > Binary 1
On Odin it has a similar message:
<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> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please, please help. I have looked everywhere for hours to try and find a solution. I have downloaded gigabytes upon gigabytes of different factory versions, I think I am going insane because of this problem.

Endless boot loop/no recovery mode

I tried to root my Sprint variant with Odin (Credo mobile is the carrier). Although Odin said it PASSED, the phone went into a boot loop. I tried the Sprint firmware to unroot it - Odin said it FAILED. If I hold Volume-up/home/power, I do not get a recovery menu, but just another loop, with "Recovery Booting" flashing in blue at the top. Held the buttons a long time, did everything over, etc. I can get to download mode, and the recovery mode loop, but nothing else. Suggestions?

Kanzeon said:
I tried to root my Sprint variant with Odin (Credo mobile is the carrier). Although Odin said it PASSED, the phone went into a boot loop. I tried the Sprint firmware to unroot it - Odin said it FAILED. If I hold Volume-up/home/power, I do not get a recovery menu, but just another loop, with "Recovery Booting" flashing in blue at the top. Held the buttons a long time, did everything over, etc. I can get to download mode, and the recovery mode loop, but nothing else. Suggestions?
Click to expand...
Click to collapse
Go into download mode and try flashing the firmware again. Tell us the error and I can try and help you fix your phone. By the recovery booting error, I assume you need the pit file to repartition your phone.

Here's the whole sad story, according to Odin:
<ID:0/003> 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/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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone says:
SV REV CHECK FAIL: [system]Fused 3 > Binary 1
I don't know about pit files, but at this point I will try pretty much anything. Thank you!

im having same issue
please help

I had the same issue happened to me when trying to use Odin to flash my Galaxy S7 G930p
It would boot the very first Samsung logo in a shutdown restart and do it again repeatedly I then went back and downloaded a different firmware and it resolved the issue but now shows a unlocked padlock Below Samsung and says modified and I still don't have TWRP recovery installed but at least it fixed my boot.img I think you have flashed the wrong boot image to your phones both of you guys tell me the full model of your phone and firmware version and maybe I could help you resolve your phones
My Galaxy S7 g930p I have the Chinese version Qualcomm Virgin Mobile phone
Odin img TWRP recovery ? does anyone have the proper boot.img I need.
I'm the on android version 7.0 nauget.
Not the S7 Edge
Thank you much