[SOLVED] my i9100 died on me, what now! - Galaxy S II Q&A, Help & Troubleshooting

well guys seems my sgs2 i9100 died on me.
I'm an experienced user so I know what I'm doing, but this time seems it died.
what happened.
flashed new LQ5 sammy rom via odin for a quick test drive, all went smooth and tested all I had to test.
then it was time to flash another rom via odin.
as always before flashing another rom, I boot into fake recovery using cwm 5.8.1.5 and erase all partitions, system,data & cache and then reeboot straight to download mode to reflash the other rom via odin.
well this time, after erasing partitions I reebooted but it just went dead.
I tried about everything, even booting with usb jig into download mode, but it just doesnt work. screen is always black no message no signal no nothing.
what can I try to before RMA this Sucker ?
edit: solved by repair center replacing PBA MAIN
tks in advance,
remorema

---

remorema said:
well guys seems my sgs2 i9100 died on me.
I'm an experienced user so I know what I'm doing, but this time seems it died.
what happened.
flashed new LQ5 sammy rom via odin for a quick test drive, all went smooth and tested all I had to test.
then it was time to flash another rom via odin.
as always before flashing another rom, I boot into fake recovery using cwm 5.8.1.5 and erase all partitions, system,data & cache and then reeboot straight to download mode to reflash the other rom via odin.
well this time, after erasing partitions I reebooted but it just went dead.
I tried about everything, even booting with usb jig into download mode, but it just doesnt work. screen is always black no message no signal no nothing.
what can I try to before RMA this Sucker ?
tks in advance,
remorema
Click to expand...
Click to collapse
Well nothing, there are only to things that can resurrect this paperweight for you, and my guess is that you have neither of them
1. Fix it using JTAG
2. Change the PCB
So send it off to a repair centre near you mate
Best regards
Sendt fra min GT-I9300 med Tapatalk2

---

Ratata82 said:
Well nothing, there are only to things that can resurrect this paperweight for you, and my guess is that you have neither of them
1. Fix it using JTAG
2. Change the PCB
So send it off to a repair centre near you mate
Best regards
Sendt fra min GT-I9300 med Tapatalk2
Click to expand...
Click to collapse
I have good soldering skills but For jtag looks like there´s a box needed, and since its still under warranty I guess I'll try to RMA before opening and permanently void my warranty.

---

Sounds like you hit the eMMC brick. I know this sounds cruel but it gave me the heads up as I was about to flash the new LQ5 ROM. Might think twice about it. Don't mess about with it, just send it off for repair and play dumb.
Sent from my GT-I9100 using Tapatalk 2

---

themadba said:
Sounds like you hit the eMMC brick. I know this sounds cruel but it gave me the heads up as I was about to flash the new LQ5 ROM. Might think twice about it. Don't mess about with it, just send it off for repair and play dumb.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I think it has to do with the fake recovery. once this LQ5 firmware as a new pit file different from the older gingerbread one. and the fake recovery might not be prepared to deal with the partitions the way this new pit repartitoned
If you stay off the recovery, the rom works flawlessly, its my bad habbit of formatting the partitions before flash that screwd me
its nice that I have a usb jig and the counter is zero that way they cannot acuse me of using non official firmware.

---

Can you explain to me what the “fake" recovery is? Do you mean custom recovery?
Sent from my GT-I9100 using Tapatalk 2

---

themadba said:
Can you explain to me what the “fake" recovery is? Do you mean custom recovery?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
this http://www.clockworkmod.com/rommanager
you can boot into stock recovery and from there boot into fake recovery without the need to having a custom recovery installed in your phone.

---

Interesting. You didn't have ClockworkMod Recovery then? Because ROM Manager and CWMR don't get on together. Just return your phone to Samsung and say the update failed in Kies. It's a 50/50 chance they will fix it. But it's worth a try.
Sent from my GT-I9100 using Tapatalk 2

---

The same has happened to me after an LQ5 NanDroid backup. Phone is dead, cannot boot, get recovery to start, no Odin, no Jig; nothing. Will it have to be sent for repair peeps?
Sent from my HTC Desire using XDA App

---

fs1023 said:
The same has happened to me after an LQ5 NanDroid backup. Phone is dead, cannot boot, get recovery to start, no Odin, no Jig; nothing. Will it have to be sent for repair peeps?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
either that or a jtag box.
Sent from my STM712HCZ using Tapatalk 2

---

Well if it is the eMMC brick, even a JTAG repair won't save it. A new motherboard is in place. Just send it to Samsung and play stupid
Sent from my GT-I9100 using Tapatalk 2

---

This is really bad if Samsung enabled MMC_CAP_ERASE in this new kernel, they absolutely should not have done this given the known consequences...
Sent from my GT-N7000 using Tapatalk 2

---

themadba said:
Well if it is the eMMC brick, even a JTAG repair won't save it. A new motherboard is in place. Just send it to Samsung and play stupid
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
if jtag cant save it does that mean samsung wont be able to confirm what appened to the board?
Sent from my STM712HCZ using Tapatalk 2

---

remorema said:
if jtag cant save it does that mean samsung wont be able to confirm what appened to the board?
Sent from my STM712HCZ using Tapatalk 2
Click to expand...
Click to collapse
if ur phone is bricked samsung will not knw wat u had done
just act stupid in front of them
i did the same thing when i had bricked by phone
i told them i was updating the phone in kies and after that my phone din start

---

What build did you die on? Saying "LQ5" is useless - with ICS you MUST include the FULL build identifier including region code when talking about a given build.

---

Well now I might be little more cautious, but I have wiped multiple times using the dial code and it worked fine.
Might be the touch recovery done something or you!
Have to be sure before everyone gets Bizzurk about the Emmc brick, which we didn't have until now.

---

Fix it by JTAG / univ on Samsung Centre
Sent from my GT-I9100 using xda premium

---

neerajganga said:
if ur phone is bricked samsung will not knw wat u had done
just act stupid in front of them
i did the same thing when i had bricked by phone
i told them i was updating the phone in kies and after that my phone din start
Click to expand...
Click to collapse
yep
will do that
Sent from my STM712HCZ using Tapatalk 2

---

The LQ5 release the OP is talking about is the leaked Samsung release of 4.0.4 for the GS2. Leaked a few days ago by sammobile.com. Is there any way to tell if the MMC_CAP_ERASE is still present in Samsung's new kernel? Or that is is at least equal to 0?
Sent from my GT-I9100 using Tapatalk 2

---

Mobile Odin Pro
Just a heads up. I purchased and used Mobile Odin Pro from since the release and have always used that ever since to flash leaked or official samsung roms due to the fact the pc version bricked my i5800 years back. Happy to say, It never failed me, Also it has support for Wipe Data and Also Dalvik cache. Options to Enable Ever Root, Inject Super Su (Best), And Mobile Odin so your always ROOTED :good:. Gotta hand it to Chainfire for his awesome works. I would suggest for everyone to use it for a worry free Day anytime changing non custom recovery roms, also I have had problems using superuser in the past when trying to install CWMR. Never with Super SU Pro, That's why I use it. Before thinking this post is not useful, think about it, you would be able to wipe data before flashing with no need to worry and perform it via fake recovery or CWMR. Also Odin performs MD5 checksum at your request to ensure its official.