Help - Bricked - NAND write fail - Galaxy S II Q&A, Help & Troubleshooting

Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_HOME.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks

---

It doesn't seem like a hard brick so that is kindo of lucky! However I have never cime across anyone with that problem! Why don't you try using odin to flash latest siyah kernel then try entering recovery and wipe data+cache and re-flash rom, hopefully it will work!
Sent from my GT-I9100 using xda premium

---

insat3d said:
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_HOME.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
Click to expand...
Click to collapse
I have had the same problem few months ago. Finally, I have managed to kill it when I tried to flash the bootloader - it got stuck at the beginning (just like with everything else that I tried to flash - ROMs, kernels...), no more signs of life (no charging, no download mode, nothing), andd after that Samsung service center replaced the motherboard. I think that's the only way, but you may try everything before you send it for repair. There's a thread in this forum dedicated to unflashable phones, try to get help there.

---

insat3d said:
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_HOME.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
Click to expand...
Click to collapse
sounds to me like your internal storage is damaged. I guess it's a warrenty issue

---

alexkno said:
sounds to me like your internal storage is damaged. I guess it's a warrenty issue
Click to expand...
Click to collapse
I hope it is not a warranty issue. I spoke to sammy (US), they said they don't cover warranty from outside US. (
Is there any way to confirm hardware damange??
UltimateAnas said:
It doesn't seem like a hard brick so that is kindo of lucky! However I have never cime across anyone with that problem! Why don't you try using odin to flash latest siyah kernel then try entering recovery and wipe data+cache and re-flash rom, hopefully it will work!
Click to expand...
Click to collapse
pilgrim011 said:
I have had the same problem few months ago. Finally, I have managed to kill it when I tried to flash the bootloader - it got stuck at the beginning (just like with everything else that I tried to flash - ROMs, kernels...), no more signs of life (no charging, no download mode, nothing), andd after that Samsung service center replaced the motherboard. I think that's the only way, but you may try everything before you send it for repair. There's a thread in this forum dedicated to unflashable phones, try to get help there.
Click to expand...
Click to collapse
But my phone is not dead. I am able to boot it into download mode. So I am guessing it is softbricked right? Also, i tried flashing Siyah kernel (latest and the one before). It updated the binary count. So the binary counter is not stuck as I had mentioned earlier. But it still got stuck at the NAND write step.
From what I understand, the kernel does change from "Samsung official" when I flash stock ROM to "Custom ROM" when I flashed Siyah and back to "Samsung official" when I re-flashed it. But it gets stuck after that. Any ideas why?
Thanks

---

insat3d said:
I hope it is not a warranty issue. I spoke to sammy (US), they said they don't cover warranty from outside US. (
Is there any way to confirm hardware damange??
But my phone is not dead. I am able to boot it into download mode. So I am guessing it is softbricked right? Also, i tried flashing Siyah kernel (latest and the one before). It updated the binary count. So it is not stuck as I had mentioned earlier.
Any other ideas guys?
Thanks
Click to expand...
Click to collapse
Visit this thread: forum.xda-developers.com/showthread.php?t=1457458
If your phone doesn't work after that, then it's as good as dead
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II

---

Jokesy said:
Visit this thread: forum.xda-developers.com/showthread.php?t=1457458
If your phone doesn't work after that, then it's as good as dead
Click to expand...
Click to collapse
I tried both ICS and GB mentioned on this link. It always gets stuck after zImage when I try without PIT file or set partition when I try partition.
Is JTAG going to be of any help here?

---

insat3d said:
I tried both ICS and GB mentioned on this link. It always gets stuck after zImage when I try without PIT file or set partition when I try partition.
Is JTAG going to be of any help here?
Click to expand...
Click to collapse
have you tried everything there?
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II

---

Jokesy said:
have you tried everything there?
Click to expand...
Click to collapse
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know

---

insat3d said:
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
Click to expand...
Click to collapse
I don't think so. You might have to replace your motherboard.
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II

---

insat3d said:
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
Click to expand...
Click to collapse
if I am not mistaken JTAG will give access to core, but I guess (but I am not a technician) that if the internal storage is corrupted and not even repartition helps, then I guess only replacing it might help.
I'd advise to watch out for a repaircenter near you and ask

---

Ok...so the phone is 2 months old.....
Purchased in India but being used in the US?.......
I don't care what Samsung says.....it sounds to me like they are trying to 'fob you off'. I personally would take this further. ....contact Samsung HO, contact your local trading standards department (or whatever it's called).
No warranty. ....that's just corporate bulls**t.......the age of the phone (if it can be proved) is what's important.....I think you have a very strong case here.....go with it.
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app

---

Similar problem i9100T
I have the same problem in that the phone stops at nand write when attempting to install package. I can only get into download but it will flash a bootloader but that is all. I believe that it may be necessary to reload the .pit file but I cannot find where this would be found. I presume if this were included it would reinstall this and would fix the internal storage. Any advise on this would be gratefully received.

---

Galaxy S2 stuck at NAND WRITE START
MODS.... please delete this post.