[Q] Galaxy SII stuck on boot screen - Galaxy S II Q&A, Help & Troubleshooting

Hi Guys,
I have the following problem:
I have an Samsung Galaxy SII and have never flashed anything on it, just did Upgrades via KIES to 4.1.2 (I think). It´s not branded by a Telekom Company or anything. Just a stock Phone from Samsung.
A few days ago I used that phone, put it into my pocket and after 2 hours when I wanted to use it again, it was stuck on the boot logo (you know the Galaxy GT9100 .... Screen)
If I have the power cable attached it just displays an empty battery and the circle is NOT "circling". Battery symbol is not getting "full"
Now I can´t get into the recovery mode BUT I can get into the download mode.
I already tried to Flash with ODIN but it always gives me an error like this:
<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> SingleDownload.
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Honestly I don´t care about the phone. I just want the data from my phone.
Does anyone have an idea?

---

Well you won't be getting any data of the phone unless you get it to boot/function normally, so first thing's first. Search for Hopper8's 'Odin troubleshooting' thread. Try the stuff in his thread until the phone successfully takes an Odin flash.

---

Hmm. How about you flash CWM on it and make a backup of the Stock ROM with it?
Sent from my GT-I9100 using XDA Premium 4 mobile app

---

seems like its bricked it self.. mYbe an emmc failure.. i got my s3 with the same problems.. tried everythng but nothing work.. send it to samsung and they tell me that motherboard replacement are the only solution.

---

lawong said:
seems like its bricked it self.. mYbe an emmc failure.. i got my s3 with the same problems.. tried everythng but nothing work.. send it to samsung and they tell me that motherboard replacement are the only solution.
Click to expand...
Click to collapse
Nah, I think he's just missing something while flashing via odin.
Sent from my GT-I9100 using XDA Premium 4 mobile app

---

but his issue are same as mine, except mine fails at odin with 'cant find any partition'

---

Hahaha, no partition is a screwed mobo definitely!
Sent from my GT-I9100 using XDA Premium 4 mobile app

---

lawong said:
but his issue are same as mine, except mine fails at odin with 'cant find any partition'
Click to expand...
Click to collapse
yeah , that s3 was a victim of exynos SDS ..

---

Gee there's been an awful lot of unfounded assumptions made in this thread over the past 15 minutes

---

lawong said:
seems like its bricked it self.. mYbe an emmc failure.. i got my s3 with the same problems.. tried everythng but nothing work.. send it to samsung and they tell me that motherboard replacement are the only solution.
Click to expand...
Click to collapse
just curious but isnt the emmc limited to 4.0.4 ?
Going through the hoppers guide now

---

Alright I can do whatever I want. Odin always Fails at the NAND write step.

---

Which means one of two things:-
1) I don't know how much of Hopper's thread you read, but I'm fairly sure he makes the point that fixing cases like these is often a matter of persevering. You keep trying stuff until it works. The first 11 flash attempts might not work, but for whatever reason the 12th works. You can keep doing that if you want, or it could be
2) The NAND really is borked. If that's truly the case, then yes, only a motherboard replacement is fixing it (either a new one by a service centre or a 2nd hand one by you/a local mobile repair shop), and you can kiss goodbye any chance of recovering data from the phone.
Now, if it was my phone, I know what I'd be doing before I gave up & declared it a case of option 2 (but YMMV, obviously).

---

MistahBungle said:
Which means one of two things:-
1) I don't know how much of Hopper's thread you read, but I'm fairly sure he makes the point that fixing cases like these is often a matter of persevering. You keep trying stuff until it works. The first 11 flash attempts might not work, but for whatever reason the 12th works. You can keep doing that if you want, or it could be
2) The NAND really is borked. If that's truly the case, then yes, only a motherboard replacement is fixing it (either a new one by a service centre or a 2nd hand one by you/a local mobile repair shop), and you can kiss goodbye any chance of recovering data from the phone.
Now, if it was my phone, I know what I'd be doing before I gave up & declared it a case of option 2 (but YMMV, obviously).
Click to expand...
Click to collapse
right, so is the storage fixed on the Mainboard and not a seperate module (like harddrives in Computers)?
So in case I switch the Mainboard I cannot take the old storage to the new Mainboard.

---

Correct.

---

MistahBungle said:
Correct.
Click to expand...
Click to collapse
not good
I am still trying here ...

---

phone can be fixed my booting to recovery mode and factory resetting the phone
OOORR
if u just want the data flash siyah kernel via odin and boot to recovery mode
go to mounts and storage
mount usb storage while phone connected to pc
Sent from my GT-I9100 using xda premium

---

iamtalha said:
phone can be fixed my booting to recovery mode and factory resetting the phone
OOORR
if u just want the data flash siyah kernel via odin and boot to recovery mode
go to mounts and storage
mount usb storage while phone connected to pc
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks for your answer but you lost me a little here.
As I wrote the recovery mode isn´t working at all. Only the download mode.
Already tried flashing the siyah kernel but still no difference in phone behaviour.
What exactly do you mean with "mount usb storage while phone connected to pc"?
When I connect the phone to the pc, Windows always tells me that there is a device that can´t be recognized (don´t know the exact error message) and that leads to no access to the phone by the Windows Explorer, Kies, ...

---

if the data in the phone is not much important than try this its my own fix.
http://forum.xda-developers.com/showthread.php?t=2400535
Sent from my GT-I9100 using xda premium