Odin firmware writing issue - Galaxy S II Q&A, Help & Troubleshooting

Hi,
I've had the SGS2 for a couple of days. I pretty much feel I understand all the different concepts having been on htc android before hand.
Anyway my problem is that although I get the familiar yellow "0:[COM5]" in odin on win7 home premium x64, the phone refuses to take the firmware update.
So anyway when I first got the phone, I was pretty clueless on what I was doing, I followed this guide http://samsunggalaxys2tips.com/how-to-root-samsung-galaxy-s2-guide/ which seemed to work well enough and I do have root on stock. However after that, my odin mode on the phone now displays "CUSTOM BINARY DOWNLOAD: YES (1 counts)" as well as yellow triangle. So am I right in saying I can not write any firmware until I've USB jig'd my phone? I thought the jig would only be handy in case of sending the phone back to Samsung under warranty.
Here is some info about the phone, kies is convinced the phone is fully up to date on the following.
PDA:KE5
PHONE:KE1
CSC:KE2(VOD)
Carrier Orange
Phone was orignally bought on a Vodafone UK contract but unlocked and working fine on Orange UK
No clue on the exact product name, as I flashed root before checking. If someone knows how I can found out, that would great.
My last attempt almost looked like it was flashing firmware, however it stopped abruptly here:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
If anyone has any pearls of wisdom they would be willing to share on the matter, I would be very grateful.
****UPDATE****
I tried flashing I9100XWKDD_I9100XXKDH_I9100XEUKD1_HOME which did actually attempt to flash which was odd, however the result:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Now I just have a phone and computer icon with an explanation mark between the two in the middle of the screen and nothing else, hope I've not bricked it
Tried again over night and that failed too
<ID:0/005> Removed!!
<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> Sbl.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

phone is still accessible in odin mode, but only shows the above mentioned orange icon otherwise. please help!
Was the sodding usb dock in the end, using a different cable and its working!

novakry said:
Hi,
Anyway my problem is that although I get the familiar yellow "0:[COM5]" in odin on win7 home premium x64, the phone refuses to take the firmware update.
Usually due to a wrong file format or not a TAR file .
displays "CUSTOM BINARY DOWNLOAD: YES (1 counts)" as well as yellow triangle. So am I right in saying I can not write any firmware until I've USB jig'd my phone?
Totally wrong makes no difference at all to flashing .
Here is some info about the phone, kies is convinced the phone is fully up to date on the following.
Yes it probably is the latest firmware for that product code as updated by the vendor .
My last attempt almost looked like it was flashing firmware, however it stopped abruptly here:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
Repeat looks like wrong file format .
I
I tried flashing I9100XWKDD_I9100XXKDH_I9100XEUKD1_HOME which did actually attempt to flash which was odd, however the result:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Same answer
Makes no sense to ask about a topic on one forum that was posted on another forum .The post may be missing bits and is most definitely well out of date .
No idea what you are trying to achieve root or firmware upgrade .
Both are in the dev section .
jje
Click to expand...
Click to collapse

Related

[Q] White screen "Grey lines" bug again

When i came home my phone would bot respond to unlocking the screen so i've pulled the battery and powered on and then the screen was white and full of horizontal lines . At first i thought that there was something wrong with the screen connector becaus the scrreen lokked different when phnone was off charger was plugged in and different than normally turned on. But with hope i've tried booting to recovery again lines. but booting to download mode worked.
Then i've searched over xda and few other sites (mostly linking here)
I've tried flashing single file stock rom:
Code:
<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> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
then i've downoaded mx.pit file tried with repartition and there was:
Code:
<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>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've pulled battery for 15 min ant the same thing happend.
I even tried updating via KIES in download mode but there was an error . in the begining of the update.
The warranty of the phone was voided few months ago.
Is there anything I can still do at this point (maybe finding proper pit file .... bit i dont know how to match it to my gt-i9300 16GB version)
Will someone better equipped will be able to repair it or i have to brace myself for the cost of a new phone (mainboards are as expensive ad used s3)?
is this what you have ?
przemo-c said:
When i came home my phone would bot respond to unlocking the screen so i've pulled the battery and powered on and then the screen was white and full of horizontal lines . At first i thought that there was something wrong with the screen connector becaus the scrreen lokked different when phnone was off charger was plugged in and different than normally turned on. But with hope i've tried booting to recovery again lines. but booting to download mode worked.
Then i've searched over xda and few other sites (mostly linking here)
I've tried flashing single file stock rom:
Code:
<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> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
then i've downoaded mx.pit file tried with repartition and there was:
Code:
<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>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've pulled battery for 15 min ant the same thing happend.
I even tried updating via KIES in download mode but there was an error . in the begining of the update.
The warranty of the phone was voided few months ago.
Is there anything I can still do at this point (maybe finding proper pit file .... bit i dont know how to match it to my gt-i9300 16GB version)
Will someone better equipped will be able to repair it or i have to brace myself for the cost of a new phone (mainboards are as expensive ad used s3)?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2379256
idanohh said:
http://forum.xda-developers.com/showthread.php?t=2379256
Click to expand...
Click to collapse
yes that's exactly the same problem
przemo-c said:
yes that's exactly the same problem
Click to expand...
Click to collapse
Well not exactly .. mine doesnt get stuck on :
Code:
Get PIT for mapping..
it goes further but fails anyway.

[Q] Can't unroot my galaxy s4 verizon

I have tried many different tutorials and followed them exactly and carefully but no matter what happens Odin gets stuck on "get PIT for mapping" any ideas on what to do to fix this problem?
jonahgerber1 said:
I have tried many different tutorials and followed them exactly and carefully but no matter what happens Odin gets stuck on "get PIT for mapping" any ideas on what to do to fix this problem?
Click to expand...
Click to collapse
I got the same issue as well. One thing I noticed while in ODIN mode was that "Write Protection" is "On". Perhaps this is the reason why.
Here's what I have in ODIN
<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> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> boot.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
What build are you guys on and what Odin files are you using?
Have either of you tried using the PIT file Surge provided?
Sent from my SCH-I545 using Tapatalk

[Q] Odin: Stuck at NAND Write Start

Hey everyone
Having read many threads on this issue I would appreciate help for my specific case. I got a defective device from a friend that wouldn't start anymore (introductory Samsung animation was playing repeatedly). I then tried to flash "GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9" to eventually install CM 10.1.3 and then factory reset to make sure the brick bug is not an issue. However, I was not able to flash CWM, because it gets stuck at "NAND Write Start" and eventually fails (see below). Interestingly, I flashed another i9100 flawlessly only a few days ago with the exact same setting. Nonetheless I tried different Odin versions as well as different usb ports and cables.
I have no idea what kind of kernel or android version was running on the device and I can now only get into download mode.
When reading this guide I came across two problems. First, flashing a kernel - some other thread recommended "Siyah-s2-v5.0.1" - was unsuccessful. Second, I wasn't sure if I should try to flash the ICS version mentioned in this thread.
Some mentioned falling back to flashing PIT-files, but because recovery mode is not available, I cannot use the "emmc partition scanner" to identify the correct PIT-file to flash.
I would really like to save this device, so someone else may enjoy using it again in the future. Thanks in advance for any help!
Cheers
sNiXx
ODIN 3.09
Code:
<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> SingleDownload.
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ODIN 1.3
Code:
<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> Firmware update start..
<ID:0/004> zImage
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Could anyone please help me out with this issue? I would appreciate it, if I could get the device running again.
Thanks in advance for help or tips!

I got softbrick I think and I cannot fix it

I was going to flash a new pit file and a kernel along with that but somehow it didn't work, I got stuck at Samsung Galaxy S2 logo and couldn't boot into recovery. I assume I soft bricked my device. Then I searched some guides on how to fix it but I couldn't, and the download links are often broken in those guides. In Odin3 flash get stuck at "<ID:0/005> NAND Write Start!!" and then ERROR. Is this fixable and in that case how? Please provide download links that work if I need any file.
This is the Odin3 log when I try to flash. I try to flash the files (PDA,PHONE,CSC) in this thread ("Another option for i9100" section). I have tried with pit file and without (I think it was wrong pit though) but same result...
<ID:0/005> Added!!
<ID:0/005> Removed!!
<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> 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> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Well after having this problem in over 24 hours I try to flash my old stock gingerbread rom with odin and it worked. I then flashed CWM kitkat compatible Kernel and that also works. So no help needed here anymore I think.

Odin failure at "spl.img" - Samsung J320FN

Hi helpful people!
I have a Samsung J320FN which I'm trying to flash the original firmware back over in order to root. The firmware type is UK BTU - I'm trying to use this one: sammobile.com/samsung/galaxy-j3-2016/firmware/SM-J320FN/BTU/download/J320FNXXU0ARH1/276931 (apologies, can't post hyperlinks as new user), which I'm 99.99% sure is the right one.
Odin keeps freezing up at Set Partition, "spl.img".
I then tried using this one: samfrew.com/download/Galaxy__J3__/2pac/BTU/J320FNXXU0ARH1/J320FNBTU0ARH1/which is a single file that's loaded into AP. Using this I got a similar failure after "boot.img".
First few times with either wasn't an issue particularly, but I eventually (obviously) ended up bricking the goddamn phone.
Can someone explain what might be going on here? I note that in each case the file the process is failing on is the first one to be transferred - could it simply be the cable? Bearing in mind that the cable was perfectly sufficient for installing the drivers and such, this seems unlikely but possible?
Is there something else at play? Have I forgotten something?
A few time saving answers to questions:
- Yes, I'm using the CSC version that the phone was already working on
- Yes, I've completed this process before successfully (not with this phone) - I am not a complete newbie, but I'm certainly no expert
- Odin v 3.14.4, Windows 7
Code:
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1859 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> spl.img
Thanks in advance for you help!
Sean
sjoh said:
Hi helpful people!
I have a Samsung J320FN which I'm trying to flash the original firmware back over in order to root. The firmware type is UK BTU - I'm trying to use this one: sammobile.com/samsung/galaxy-j3-2016/firmware/SM-J320FN/BTU/download/J320FNXXU0ARH1/276931 (apologies, can't post hyperlinks as new user), which I'm 99.99% sure is the right one.
Odin keeps freezing up at Set Partition, "spl.img".
I then tried using this one: samfrew.com/download/Galaxy__J3__/2pac/BTU/J320FNXXU0ARH1/J320FNBTU0ARH1/which is a single file that's loaded into AP. Using this I got a similar failure after "boot.img".
First few times with either wasn't an issue particularly, but I eventually (obviously) ended up bricking the goddamn phone.
Can someone explain what might be going on here? I note that in each case the file the process is failing on is the first one to be transferred - could it simply be the cable? Bearing in mind that the cable was perfectly sufficient for installing the drivers and such, this seems unlikely but possible?
Is there something else at play? Have I forgotten something?
A few time saving answers to questions:
- Yes, I'm using the CSC version that the phone was already working on
- Yes, I've completed this process before successfully (not with this phone) - I am not a complete newbie, but I'm certainly no expert
- Odin v 3.14.4, Windows 7
Code:
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1859 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> spl.img
Thanks in advance for you help!
Sean
Click to expand...
Click to collapse
Tried using a different cable which I knew should be able to handle this (a micro-USB that came with a graphics pen/pad, so definitely able to carry data!), and still the same issue.
However, somehow (honestly have no idea how) managed to unbrick the phone whilst playing around in recovery mode.
Further to this, tried to flash TWRP recovery onto this device after giving up on the above, and I get a similar failure - this time ODIN fails at recovery.img.
Can somebody please shed some light on what I might be doing wrong here? I really am stumped!
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 14 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<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> recovery.img
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

Categories

Resources