Database Users

Help!! I can not use Odin to Flash anymore

Help please
My tab is stuck at downloading
<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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
***never mind*** I restarted the computer and used another usb port....everything was fine again

[Q] CF Auto-Root Failures

I am trying to use CF Auto-Root for my GS-4 i9500. I power up my phone in "download mode" but as soon as i do it already says 'Downloading... Do not turn on target!!'. I waited for a while (watched a tv show so probably 40-45 min) and nothing changed. The upper left says; Odin mode, ..., Write Protection: Enabled, eMMC BURST MODE enabled. I turn it off and back on in download mode (still says 'Downloading...'), load up the binary, connect the phone to my comp (odin says 'Added!!' and recognizes the COM port it is connected to), and click start. About half the time i get:
<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> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried 4 different USB ports and 3 different cables. I can simply click restart in odin and try again when i get this error
The other half i get:
<ID:0/005> Added!!
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
in the upper left on my phone I get, in red; start [224, 1440], secure magicode check fail : recovery. This requires me to reboot the phone for another attempt. I have clicked the PIT button in odin and there are no files there.
I have found some similar threads for the first failure but they all seem to require re-partitioning and re-make (?) the PIT file which is apparently "extremely risky". As for the second failure, I found several threads with a similar failure but they were regarding going back to stock and seemed to be caused by a bad recovery image?? On the up side my phone will still boot into factory software just fine, but I would really like to figure out what I'm f-ing up.
What am I doing wrong?
Thanks in advance for any help

If I were you, I would look for a custom recovery and flash this. I use Philz Touch Recovery, you can root it from it and it works perfect.
Links here: http://d-h.st/users/philz_touch/?fld_id=16644#files
flash it in Odin using AP.

PIT file for SC-04E

I have a SC04E (Japanese NTT Docomo Galaxy S4) and I failed to flash Cyanogenmod and bricked my phone. When I try to put the original ROM from sammobile.com, I get this error on Odin:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
From that I think I need a PIT file to flash but I couldn't find any pit file on the web.
I really need a pit file for it or if there's any way I can fix this problem, please reply.
Thank you in advance.

taichiksto said:
I have a SC04E (Japanese NTT Docomo Galaxy S4) and I failed to flash Cyanogenmod and bricked my phone. When I try to put the original ROM from sammobile.com, I get this error on Odin:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
From that I think I need a PIT file to flash but I couldn't find any pit file on the web.
I really need a pit file for it or if there's any way I can fix this problem, please reply.
Thank you in advance.
Click to expand...
Click to collapse
You probably do not need a .pit file.
In 99% of the cases the error is resolved by the following:
- Different usb port
- Different usb cable.

Lennyz1988 said:
You probably do not need a .pit file.
In 99% of the cases the error is resolved by the following:
- Different usb port
- Different usb cable.
Click to expand...
Click to collapse
Thank you for your quick reply,
I have tried changing usb ports and checked all the cables I had and I even used different computer but I couldn't get it to work and always got the same message...
*sigh*

taichiksto said:
Thank you for your quick reply,
I have tried changing usb ports and checked all the cables I had and I even used different computer but I couldn't get it to work and always got the same message...
*sigh*
Click to expand...
Click to collapse
Are you trying to flash the latest firmware available? If you try to flash the latest firmware then it's still either one of these thing.
- Different usb cable
- Different usb port

Lennyz1988 said:
Are you trying to flash the latest firmware available? If you try to flash the latest firmware then it's still either one of these thing.
- Different usb cable
- Different usb port
Click to expand...
Click to collapse
I downloaded the latest firmware and there wasn't any errors but it gets stuck where the samsung logo appears. Is there any step that I missed?

it also says Recovery Mode on the carrier logo in blue and then reboots, next time without the message and shows samsung logo and shows the battery charging

nvm I redownloaded a latest rom and it fixed the issue

Need help with flash my S8+ with odin

Hi guys,
I'm trying to flash back to stock firmware with Odin on my phone. I have downloaded the stock firmware and loaded with Odin.
I put my phone to download mode and connect to computer. But every time when I hit start, the phone restarts and Odin shows failed. Below is the message I got:
<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> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<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> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Any ideas?

note 4 can not flash the rom Please HELP

hi, i was using my samsung galaxy note 4 for nearly 4 years without any problems. today It went to black screen where was some info about "panic Karnel". I removed battery and everything was fine. 2 hours later when I was using snapchat phone restart and went to bootloob. I connected note 4 to odin to flash stock room and I get a massage in odin every time when I want to flash rom:
<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!!
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
on my phone there is massage:
"mmc_write fail"
Please help dear experts, i it any chance to fix my phone??
P.s. I tryed to use this>>> https://forum.xda-developers.com/no...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
but did not work, still get a massage:
""mmc_write fail""

x7nofate said:
hi, i was using my samsung galaxy note 4 for nearly 4 years without any problems. today It went to black screen where was some info about "panic Karnel". I removed battery and everything was fine. 2 hours later when I was using snapchat phone restart and went to bootloob. I connected note 4 to odin to flash stock room and I get a massage in odin every time when I want to flash rom:
<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!!
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
on my phone there is massage:
"mmc_write fail"
Please help dear experts, i it any chance to fix my phone??
Click to expand...
Click to collapse
Flash Twrp recovery via odin
In twrp Go to wipe
Wipe "system+data+cache+dalvic cache+internal storage you have to wipe 3 times or more to make sure all partations are wiped cleaned.
Then you have to download repair firmware for your specific model.
Repair firmware comes with 5 files "BL+AP+CP+CSC+PIT"
you have to extract and upload all files in odin with PIT file.
Then go to odin options and check on "nand eraseall" and "re partition"
Now boot your device into odin download mode
Now hit start and wait until finish
Then dont let phone reboot you have to boot into stock recovery and do wipe cache & factory reset then reboot.
If this method fails then there is no way to fix it unless changing logic board because your internal storage is dying thats why it shows "mmc_write fail".
You can download repair firmware from www.tsar3000.com

thank you for reply. I tryed to Flash Twrp recovery via odin but it failed. I get massage in odin:
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tryed few times and I am sure I was flashing the right recovery
I also did try to flah Repair firmware which comes with 5 files "BL+AP+CP+CSC+PIT" but it failed, I get message:
<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> Erase...
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help

x7nofate said:
thank you for reply. I tryed to Flash Twrp recovery via odin but it failed. I get massage in odin:
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tryed few times and I am sure I was flashing the right recovery
I also did try to flah Repair firmware which comes with 5 files "BL+AP+CP+CSC+PIT" but it failed, I get message:
<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> Erase...
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help
Click to expand...
Click to collapse
Try to put your phone in freezer without battery for an hour then try this method again.
Keep trying if it doesn't work then as i told you you have to replace logic board because your internal memory is dead.