Hi everyone i hope somebody can help me my problem is that i was on Stock Rom 2.3.6 and i want to put a custom rom so i root it, i did it everything good.
But then following a tutorial of how to put cwm i did it like the video flashing with odin and mine said success but i have bootloop. I never tought trying to enter cwm so i tried to flash stock rom again but didnt have success.
It started but have only fails in odin and now i dont know how but it haves a NAND rw corruption and doesnt let me flash roms only kernels.
When i try to flash a rom i have that problem. So looking on internet now i know that is a soft brick because only i can enter download mode not recovery.
I already tried to do what a thread over here says about how to recover from a soft brick with a recovery package and a kernel, also tried to flash a bootloader that came with that but it doesnt let flash. It stills turns on but only download mode.
I take it to repair but here in Mexico cant even tried something they gave me back my phone and they have it 3 days there for nothing, is it hard brick or something like that because it doesnt come back with that tutorial of soft brick
PS: It haves the triangle i know that is something normal when you flash it, but in the download mode my count number is 24 ._. too much i know but thats because i already tried everything i found and still like that, is there a problem with all that counts? i dont have a jtag
I think this is the LONGEST sentence I've ever read in my life.
Would you mind if you put some periods? I'm having a hard time decoding what your post means.
Sent from my GT-I9100 using xda premium
jantonio23 said:
I think this is the LONGEST sentence I've ever read in my life.
Would you mind if you put some periods? I'm having a hard time decoding what your post means.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I put enters dont know why it go out there like that, but sorry the point of my problem is that:
1.- I was on Stock Rom 2.3.6.
2.- Rooted and everything fine.
3.- Tried to flash cwm following a tutorial and didn't start had a bootloop.
4.- Then i tried to flash back the stock rom and there came the problem:
- I can only access to download mode.
- No recovery mode.
- Sometimes it said on the screen when turning on "Samsung Galaxy S II" with the triangle, but other times says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
- Always says fail in Odin when i tried to flash a Rom (Only Kernel success), the problem is the Nand rw is corrupted.
- Already did a tutorial to recover a soft brick but no success it gaves the same error of nand rw.
- Cant flash an old bootloader that cames with the tutorial of soft brick.
I don't have a Jtag but i can put it in download mode so i think i dont need it or im wrong?
DarkCloud7 said:
I put enters dont know why it go out there like that, but sorry the point of my problem is that:
1.- I was on Stock Rom 2.3.6.
2.- Rooted and everything fine.
3.- Tried to flash cwm following a tutorial and didn't start had a bootloop.
4.- Then i tried to flash back the stock rom and there came the problem:
- I can only access to download mode.
- No recovery mode.
- Sometimes it said on the screen when turning on "Samsung Galaxy S II" with the triangle, but other times says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
- Always says fail in Odin when i tried to flash a Rom (Only Kernel success), the problem is the Nand rw is corrupted.
- Already did a tutorial to recover a soft brick but no success it gaves the same error of nand rw.
- Cant flash an old bootloader that cames with the tutorial of soft brick.
I don't have a Jtag but i can put it in download mode so i think i dont need it or im wrong?
Click to expand...
Click to collapse
You should not flash with bootloader. Try flash the recommended .pit file instead. After a successful flash, flash the ROM.
ksilver89 said:
You should not flash with bootloader. Try flash the recommended .pit file instead. After a successful flash, flash the ROM.
Click to expand...
Click to collapse
Actually im doing that, the .pit file has success but then when i flash a rom its still haves a nand rw problem doesnt pass from there, is there a .pit file different? i have "u1_02_20110310_emmc_EXT4.pit".
notsmartenough said:
that's GREAT NEWS that you can go to download mode,
flash another firmware using odin just to be sure
Click to expand...
Click to collapse
I tried a lot of roms stock roms, unbranded ones, even the cm9 resurrection because they said that it could work but no success, feel so bad i only had 1 week with my S2 i bought it used from a friend so it doesnt have warranty, and i killed it but im not new on this flash stuff i used to do it with my Ace.
DarkCloud7 said:
Actually im doing that, the .pit file has success but then when i flash a rom its still haves a nand rw problem doesnt pass from there, is there a .pit file different? i have "u1_02_20110310_emmc_EXT4.pit".
I tried a lot of roms stock roms, unbranded ones, even the cm9 resurrection because they said that it could work but no success, feel so bad i only had 1 week with my S2 i bought it used from a friend so it doesnt have warranty, and i killed it but im not new on this flash stuff i used to do it with my Ace.
Click to expand...
Click to collapse
With the problem you described, it seems you device is hardbricked.
But since you can still get to download mode, Visit this thread: fforum.xda-developers.com/showthread.php?t=1841099
Swyped from my Samsung Galaxy SII
Jokesy said:
With the problem you described, it seems you device is hardbricked.
But since you can still get to download mode, Visit this thread: fforum.xda-developers.com/showthread.php?t=1841099
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
I tought that when is Hardbricked it was when it doesnt turn on or go to download mode, but maybe your right.
Im gonna try that thanks, but I think it will have fail because it says to flash PDA .OFFICIAL XWLPG and as I said it doesnt let flash any rom with that NAND rw problem.
Anyway if i try only flashing Siyah Kernel could it help? I was reeding something about dual boot or something like that
DarkCloud7 said:
I tought that when is Hardbricked it was when it doesnt turn on or go to download mode, but maybe your right.
Im gonna try that thanks, but I think it will have fail because it says to flash PDA .OFFICIAL XWLPG and as I said it doesnt let flash any rom with that NAND rw problem.
Anyway if i try only flashing Siyah Kernel could it help? I was reeding something about dual boot or something like that
Click to expand...
Click to collapse
no.
-Nand corruption is also hard enough to make your phone useless.
-that method should work since you are only flashing kernel as pda
I'm waiting for your feedback
Swyped from my Samsung Galaxy SII
Jokesy said:
no.
-Nand corruption is also hard enough to make your phone useless.
-that method should work since you are only flashing kernel as pda
I'm waiting for your feedback
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Now I know it, gonna try Im downloading the XWLPG when I finish trying Im gonna reply thanks for Your help
Jokesy said:
no.
-Nand corruption is also hard enough to make your phone useless.
-that method should work since you are only flashing kernel as pda
I'm waiting for your feedback
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Well I just give up think Im gonna throw to the garbage my S2 it didn't work it doesnt flash either with that it haves the same problem:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLPG_I9100XXLPX_I9100OXXLPL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I think it doesnt flash any kernel there, so I can continue with the other part of the tutorial with it says about Siyah Kernel, anyway thanks for all help to everyone, that NAND rw problem was a nightmare all days for me.
No more S2 for me, I waste my money for this
DarkCloud7 said:
Well I just give up think Im gonna throw to the garbage my S2 it didn't work it doesnt flash either with that it haves the same problem:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLPG_I9100XXLPX_I9100OXXLPL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I think it doesnt flash any kernel there, so I can continue with the other part of the tutorial with it says about Siyah Kernel, anyway thanks for all help to everyone, that NAND rw problem was a nightmare all days for me.
No more S2 for me, I waste my money for this
Click to expand...
Click to collapse
The Siyah kernel tutorial I recommended should work.
Anyway, if your phone is still under warranty, you can probably send it for repairs
Swyped from my Samsung Galaxy SII
Jokesy said:
The Siyah kernel tutorial I recommended should work.
Anyway, if your phone is still under warranty, you can probably send it for repairs
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
It didn't work for me because it needs to flash the XWLPG first but i can't flash roms, so I couldn't pass from there to Siyah Kernel.
Thanks anyway, I can't take it I bought it used from a friend, RIP my S2
Youll still get around £120 for it on ebay.
Sent from my GT-I9100 using xda premium
theunderling said:
Youll still get around £120 for it on ebay.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Haha its something hope that, im going to start over again to buy a S2 i like that phone
Related
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_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> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Sbl.bin
I flashed rom through Odin and its return is like this.
The Sbl.bin is likely to be related to the bootloader.
I cannot access to the recovery or normally reboot.
What can I do?? I tried flashing for several times.
Zillions of thanks if you guys can help me!!!!
What is your device?
aceofclubs said:
What is your device?
Click to expand...
Click to collapse
i9100 of course.
superfan' said:
i9100 of course.
Click to expand...
Click to collapse
Why did you start a new thread? You already had a perfectly good thread going for the same problem here: http://forum.xda-developers.com/showthread.php?p=24175814.
And you've apparently decided to ignore all the advice in that thread that said to flash back to a stock GINGERBREAD firmware, since you again are trying to flash LPQ, which is one of the earlier ICS releases.
superfan' said:
i9100 of course.
Click to expand...
Click to collapse
Not of course. Because the problem you describe is what happens when you try to flash I9100 firmware on a model like I9100G or others that are called SGS2 but are different hardware. Only true way to tell is read the sticker under the battery.
Anyway forget this thread and take the advice in the other thread and report back there.
Good luck.
ctomgee said:
Why did you start a new thread? You already had a perfectly good thread going for the same problem here: http://forum.xda-developers.com/showthread.php?p=24175814.
And you've apparently decided to ignore all the advice in that thread that said to flash back to a stock GINGERBREAD firmware, since you again are trying to flash LPQ, which is one of the earlier ICS releases.
Click to expand...
Click to collapse
I tried to flash KI3, the gingerbread, it still fails. I think it is a new problem, and it is related to the NAND rw corruption mentioned by others. Therefore, I started a new post but not ignoring others' advice.
If you can help me with my problem, zillions of thanks then.
Flash a stock GB rom and see what happens .
jje
Given you say you've tried everything suggested, and given you think it's a bootloader issue, there are literally dozens and dozens of posts on here about same.
Do a Google search (rather than using XDA search), and append 'XDA' to whatever your search terms are.
This problem you're having is not common, and you're not going to find a fix easily for this (as you're discovering) short of having it JTAG'd or sending it to a Samsung service center.
Is samsung customer service accepted to handle this, even i have some custom binary no?
Or if i pay some money, they wll fix that for me??
Sent from my GT-P7500 using XDA
Yep. They'll fix it, but you'll more than likely end up paying for it. A JTAG repair might be a cheaper option. Here's one in the US, I'm sure there are many others around the world (maybe near you, search Google).
Can you still enter download-mode (Vol. down + Home Button + Power Button)? If so, you can try these steps in this Guide here
Be careful with Re-Partition..i ruined my device some days ago with it after try to fix nand rw corruption.
I have tried all of those before. But i even can't flash things through. Even vthe kernel, recovery and bootloaders.
Sent from my GT-P7500 using XDA
So when you try to flash a 3-Part Firmware (without Re-Partition) it stucked again?
PS: Be very careful .. I has a very similar problem and with Re-Partition I shoot it up -.- (http://forum.xda-developers.com/showthread.php?p=24115788#post24115788)
What have you done to shoot it up??
I stucked even i flashed a three part firware without repartition and pit file
Sent from my GT-P7500 using XDA
Hey,
I'm sorry but i didn't solve the problem for me. With "shoot it up" I mean "i killed my phone". Sorry for that mistake!
I followed the guide too but at first step I flashed with Re-Partition and PIT file. Odin stucked at "Partitioning" so after 10min I closed Odin and restart S2...after that my device was completly dead. Screen stays black. Sorry don't know how to fix it. My S2 is on the way to rapaircenter now.
Aur0r4 said:
Hey,
I'm sorry but i didn't solve the problem for me. With "shoot it up" I mean "i killed my phone". Sorry for that mistake!
I followed the guide too but at first step I flashed with Re-Partition and PIT file. Odin stucked at "Partitioning" so after 10min I closed Odin and restart S2...after that my device was completly dead. Screen stays black. Sorry don't know how to fix it. My S2 is on the way to rapaircenter now.
Click to expand...
Click to collapse
I can access to the download mode but I can't flash anything through my beloved s2.
I am going to send it to the repair centre, u suggest me to send them to Samsung's or others??
Go into recoverymode and install a rom in ur memory internal or extaernal
Just do that turn off phone...and them volume up+power+home button u will enter in recovery mode not in download mode...now just search the rom ...notice u do this if its rooted... Look if u just put insecure kernel by odin i sugere u take sd card out download a rom by computer to sd card. input again in phone and turn on in recovery mode... i think will works im not responsabile for nothing can happened but im pass the same like i write...tell something
Sent from my GT-I9100 using XDA
Look the guy up say to you a dificult way to do and also u may brick ur phone...u do somethings in odin i just never do...i just saw now otherwise u already fix it if i put this earlier
Sent from my GT-I9100 using XDA
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.
Ok so last night my phone froze up while I was browsing the web (it froze just after rotating, if that's of any significance) so I held the power button down until it turned off. Trying to turn it on again, it just sat at the galaxy s 2 logo before any bootanimations etc start playing.
I thought I'd try to just re-flash the ROM (CM10 nightly 26/9/2012) and it seemed to just freeze up near the end of the flash, so I left it to do it's thing.
When I returned to the phone, it was showing me a kernel panic screen, so I held the power button to turn it off again and since then it won't boot into the ROM, it won't boot into recovery, and until just now it wouldn't be recognised by odin in download mode.
I had tried installing the USB drivers for the phone etc and it wouldn't work, however while writing this topic I just got a notification on my PC saying USB drivers had been installed and Odin seemed to recognise my phone, so I tried flashing cm9 resurrection, however it seems to be stuck. These are the messages in Odin, for reference:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
and it's just been stuck there since I pressed start. There is no progress bar or anything on the phone either. Oh, and Odin's progress bar thing at the top just says "KERNEL" with a blank bar under it and "0:[com3]" with a yellow background below that.
Is it safe to unplug the phone and try again with a different USB cable?
EDIT: After trying different methods to recover it (with the same result from Odin):
Orkane1989 said:
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Click to expand...
Click to collapse
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
So it's safe to unplug the phone?
D3_ said:
So it's safe to unplug the phone?
Click to expand...
Click to collapse
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Orkane1989 said:
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Just tried this, getting the same thing, Odin gets the first "bar" in the progress bar completed and seems to get stuck. Same output as above.
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
You will have to consult someone with some more knowledge about this than me. You could have a corrupt data partition... but its honestly out of my league now lol. Sorry I couldn't help.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
Click to expand...
Click to collapse
According to the output it gives me (in the OP) it does successfully check the MD5 though.
I'll admit, I haven't actually used Odin since I first rooted this phone (back in december last year) so I'm back to knowing basically nothing about how it works.
Yes it does confirm the md5
But after that it sends the commands to start running the new kernel (basically installing it on the device firstly)
Which is where it gets stuck.
Sent from Jelly Fuelled SGS2
Just tried this: http://forum.xda-developers.com/showthread.php?t=1457458
Same issue with flashing those files.
I don't want to try the .pit because if it doesn't flash then I'll be pretty f*cked, right?
I would try what ever else you could find because if you get that guide wrong you could end up turning your phone into a paperweight. But if you so have to use the guide take note that you ahould try flashing the files WITHOUT .pit or repartition first. If that doesn't succeed than your last option is to use the .pit file and repartition.
Sent from Jelly Fuelled SGS2
I did try it, without the .pit/repartition as the guide says to try it without it first, but again, it won't flash anything (which is why I don't think I'll try the .pit/repartition)
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Sent from Jelly Fuelled SGS2
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
'<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Baraa01 said:
Hey guys,
First up, this is what I was running.
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
-RootBox v3.8
So I installed RootBox v3.8 a few weeks ago and the update for v3.9 appeared on my phone along with the GAPPS update. I made the mistake of ONLY flashing the first update. So when my phone rebooted it kept on giving me the error 'Android.process.acore has stopped unexpectedly'. I was forced to then revert back to v3.8 and everything seemed peachy. Up until the other night where I turned on my phone and it showed, 'Firmware upgrade encountered an issue. Please select recovery mode in kies and try again'. I accessed 'Download Mode' and tried to flash my stock rom back on but it failed in ODIN and gave me this error.
' Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9300XXEMA2_I9300OPSEMA1_I9300XXELLA_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:7)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Removed!!'
Also if I switch on my phone, this is what appears, I can still access 'Download Mode'. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Heya!
Your SIII looks bad with this stripes!
Have you flashed your StockROM via Odin while you were in DownloadMode? If it don't be in DownloadMode, it also can't be flashed.
Try to download a firmware from samfirmware.com and to flash it via Odin in the PDA field while your device is in DownloadMode!
And when you have finished, go to Recovery and Wipe your Data&Cache!
Greetings...
Sent from my GT-I9300 using xda app-developers app
Of course I used ODIN to flash stock rom, it didn't work.
AW: [Q] [HELP] Soft-Bricked Galaxy S3-I9300
Of course I used ODIN to flash stock rom, it didn't work.
Click to expand...
Click to collapse
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
TheRealFelix0212 said:
Sorry that I ask, but have you flashed it in Downloadmode?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you read my first post, yes, I did flash it in Download Mode via ODIN.
Well, it obviously had a problem writing the rom into the phone (nand write failed). You may have a hardware fault. Do you have the nand chip that suffers from sds?
Sent from my GT-I9300 using xda premium
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
ratatattata said:
I've had similar issues before, not that exact screen, but issues with Odin. It worked eventually.
Try Odin3 v.1.85 from here (CF-Auto-Root thread).
Next, be sure you got a valid file, those from sammobile (Choose your country for).
Next, use only PDA button, nothing else, make sure it's the same settings as in root thread above.
Also make sure all Kies processes are closed.
Now, try until it works. It might take a few tries. This is what worked for me, hope it does for you too.
Click to expand...
Click to collapse
Still failed in ODIN. You reckon the eMMC chip is damaged?
Baraa01 said:
Still failed in ODIN. You reckon the eMMC chip is damaged?
Click to expand...
Click to collapse
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
jmpmjmpm said:
That's what it sounds like keep trying to flash, try a different usb cable and computer if you can. Also remove any sim or sd card.
Also maybe the partition table is messed up but emmc is Ok?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Same isssue here, same screen and everything.... I tried for over a month and nothing... got an expensive door steep. If you have any lights about this... let me know!!
try flashing recovery only and then flash 3.8 again through recovery.
try flashing the resurrection rom from the checkrom site through odin in download mode..
galaxys3lover said:
try flashing the resurrection rom from the checkrom site through odin in download mode..
Click to expand...
Click to collapse
Been there, done that. Nothing happens. Same error, Re-Partition failed.
please help?
-Samsung Galaxy S3 GT-I9300
-FCC ID: A3LGTI9300A
-SSN: -I9300GSMH
I hope I've not ended up with this phone mentioned in this thread....purchased a phone from ebay and the seller said its stuck on Android SIII logo...I can get into download mode but before I attempt anything can someone tell me if this is a UK phone so I can apply the correct ROM (if it works!).
Also, currently the phone does not charge, battery is fine as i've tried the battery from own s3 and vice versa...both batteries are fine but the phone does not appear to charge...I'm hoping this is ROM related....
Any help will be much appreciated otherwise its an expensive gamble!
BTW...In the download mode the product bit is blank and does not say Samsung galaxy s3 like my own working phone does...
Hi,
I've got this problem with a friends(girl) phone.
Her phone was stuck at the firmware upgrade screen(the one with firmware upgrade encountered an issue). So she searched the internet for a solution and did some things with kies and odin. But nothing worked so i offered to help her.
So i searched and found this article. i followed all the instructions and downloaded 3 different versions of odin V3.07, V1.3 and V1.85.
Specifications of the phone:
samsung Galaxy S II GT-I9100 16GB
what i've tried so far:
i followed the instructions from te link above and tried it with the following roms
-I9100GXXLB1_I9100GATOKL1_ATO
-I9100XWLP9_I9100KPNLP1_KPN
-I9100XXLSJ_I9100OXXLS1_OXX
i also tried the gingerbread and the ICS version
i also tried the pit file. but nothing works, the progress get stuck like in this example
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLB1_I9100GATOKL1_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone help me with this problem? I also have a JTAG programmer but don't know how or what to do with it.
Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
Look for hopper8's thread.
And stop flashing pit files.
Sent from the little guy
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Basseytje said:
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Click to expand...
Click to collapse
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
when u go to download mode, does it show your model number??
Hopper8 said:
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
Click to expand...
Click to collapse
I've already tried that one but odin is stuck at data.img.
tornado92 said:
when u go to download mode, does it show your model number??
Click to expand...
Click to collapse
Yes it shows the product name.
Basseytje said:
I've already tried that one but odin is stuck at data.img.
Yes it shows the product name.
Click to expand...
Click to collapse
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
tornado92 said:
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
Click to expand...
Click to collapse
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Basseytje said:
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Click to expand...
Click to collapse
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
tornado92 said:
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
Click to expand...
Click to collapse
kies won't recognize the phone. the only 3 screens i can access are showed in the pics below. i've got 2 stock roms which don't work. after i tried kies, i immediately uninstalled it and left the drivers on the pc.
i40.tinypic.com/29gkdi1.jpg
i40.tinypic.com/qsnluc.jpg
i41.tinypic.com/2aep3yx.jpg
can't post any files yet.
I hope there is still someone who can help me...
odin is still stuck on data.img
If you say you've 'tried everything' (which everyone always says), then it's a service centre job. What else do you want anyone here to say ? No miracle fixes. If it were me I'd keep trying, it's almost always something really simple/small/obvious that's causing the flash not to work, and as we're not there looking over your shoulder at what you're doing, it's going to be almost impossible for anyone to say what that is (you have 'tried everything' after all).
is there a way to fix this with jtag?
Basseytje said:
is there a way to fix this with jtag?
Click to expand...
Click to collapse
Maybe. No one can say for sure mate. If you motherboard is really borked, it would have to be replaced nevertheless.
Remember that Jtagging leaves marks on your device, so you can kiss goodbye any warranty u might have.
"To err is human, to forgive is divine."
Sent from my SGS II
hey.. i had this problem too.. the only solution that i had is to use the galaxy note pit file and a stock rom for i9100 ... then the phone went back to normal ..but the memory went from 16 tb to 11.5 gb .. it was the only thing that made my phone work again..
i installed pit from galaxy note ..with and original stock firmware 4.1,2 then after install I did a factory reset via stock cwm and a clear cache ..and it worked.. a few bootloops and it went on:|
alexandru.j91 said:
hey.. i had this problem too..
Click to expand...
Click to collapse
You got so ridiculously lucky that I can't comprehend that it worked. Please don't advise others to do the same, I'd say what you did is normally a recipe for a hard brick. Don't flash files for other phones, let alone a pit file for another phone. Yes I know the note has the same hardware as i9100 but you know what? It's not an i9100.
Edit: Look at what you posted in your other thread:
alexandru.j91 said:
I hardbricked my phone about 3 months ago with the original firmware from orange 4.0.4 and I resolved the problem by putting samsung note PIT file ..but I don't have acces to all the memory on my phone ..I have almosst 12 gb from 16.. and my phone is getting wired ..and it is shutting off randomly since then .and to get it on again i have to remove the battery ..
Does anybody know how to get all my memory back for my phone? tx
Click to expand...
Click to collapse
I'd say that's a reason not to flash files from another phone.
i was just telling him that i had the same problem..not to do the same thing..because of the problem that I have got! i have told in my other post whathappened to my phone! and i know that my problem can be solved by rewriting the memorybut i don't know how!..
---------- Post added at 06:04 AM ---------- Previous post was at 05:05 AM ----------
what I did.. i did because of some threads on xda ..so I am not crazy ..I just told him what I have did.. I haven't advised him to do that ..because of the problem that i had .. and when I wrote what I have did to make my phone worked .. i hace told the fact that it shrinked my memory from my phone..
maybe i'm getting a little progress. when i try to flash a new bootloader. i see a progress bar on the phone. but odin is halfway stuck at sbl.bin
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> Sbl.bin
everywhere i read, people are saying use different cables. i already tried the samsung s2 cable, a htc desire cable, 3 deal extreme cables and an other htc(dont remember the model) cable. but i'm getting the same problems. stuck at zimage or something else...
anyone?