[Q] S2 i9100 wont boot - Android Q&A, Help & Troubleshooting

Hello,
My wife has this phone and the phone accidentaly turned off and after that he was not able to boot. It was stucked on samsung logo. I tryied recovery mode and wipe phone, but it not helped. After that phone started stucking on galaxy S2 logo (before samsung logo). I was able only to go into download mode. I tried to follow this guide: wccftech.com/install-latest-android-412-jelly-bean-galaxy-s2-i9100-official-firmware but in odin (v3.07) it failed after some time (while progress bar is not moving from beginning, I see only one px of it). And now phone is showing message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Please can you help me how can I recover phone back? thanks a lot for any help
it is czech version bought in samsung shop. So I downloaded XEZ-I9100XWLSD-20130301125313 (but I am not totaly sure about version, this should be for czech)
On load PDA
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100XEZLS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
After press Start
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> cache.img
After some time
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

dawee said:
Hello,
My wife has this phone and the phone accidentaly turned off and after that he was not able to boot. It was stucked on samsung logo. I tryied recovery mode and wipe phone, but it not helped. After that phone started stucking on galaxy S2 logo (before samsung logo). I was able only to go into download mode. I tried to follow this guide: wccftech.com/install-latest-android-412-jelly-bean-galaxy-s2-i9100-official-firmware but in odin (v3.07) it failed after some time (while progress bar is not moving from beginning, I see only one px of it). And now phone is showing message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Please can you help me how can I recover phone back? thanks a lot for any help
it is czech version bought in samsung shop. So I downloaded XEZ-I9100XWLSD-20130301125313 (but I am not totaly sure about version, this should be for czech)
On load PDA
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100XXLS8_I9100XEZLS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
After press Start
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> cache.img
After some time
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Seems like you have brick bug but I have no idea how to fix it.

Next I have tried to follow this guide: http://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
I am not totaly sure about kernel version, but because this phone was pursached on his release, I have downloaded GINGERBREAD VERSION. I have tried to flash it but without success too. Green progress bar is moving to the end and after some time it writes "fail"
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Kernel_I9100XXKI3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> zImage
<ID:0/010> NAND Write Start!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Related

[Q] Phone bricked? How do I recover?

I've been using OmniROM and TWRP for quite some time now.
I put the phone on charge and a few minutes later it was stuck on Samsung initial Screen with the usual red triangle. (Showing SAMSUNG Galaxy SIII GT-I9300)
I removed the charger and battery and restarted, it was still stuck on Samsung Boot Screen.
Any ideas how to recover the phone?
I have tried going through some of the other forum threads but most of them can't go to download mode. I can go into TWRP and download mode both. I tried recovering the phone using Kies "Firmware Initialization" but it generates "your phone cannot be upgraded to the latest version" and stops.
falconflyer82 said:
I've been using OmniROM and TWRP for quite some time now.
I put the phone on charge and a few minutes later it was stuck on Samsung initial Screen with the usual red triangle. (Showing SAMSUNG Galaxy SIII GT-I9300)
I removed the charger and battery and restarted, it was still stuck on Samsung Boot Screen.
Any ideas how to recover the phone?
I have tried going through some of the other forum threads but most of them can't go to download mode. I can go into TWRP and download mode both. I tried recovering the phone using Kies "Firmware Initialization" but it generates "your phone cannot be upgraded to the latest version" and stops.
Click to expand...
Click to collapse
Download stock rom from Sammobile and flash in Odin..
tallman43 said:
Download stock rom from Sammobile and flash in Odin..
Click to expand...
Click to collapse
Downloaded latest stock rom ML4 and this is what I get in Odin 3.09:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XWUGML4_I9300ODDGML4_I9300DDUGMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/038> Added!!
<ID:0/038> Odin v.3 engine (ID:38)..
<ID:0/038> File analysis..
<ID:0/038> SetupConnection..
<ID:0/038> Initialzation..
<ID:0/038> Get PIT for mapping..
<ID:0/038> Firmware update start..
<ID:0/038> SingleDownload.
<ID:0/038> sboot.bin
<ID:0/038> NAND Write Start!!
<ID:0/038> FAIL!
<ID:0/038>
<ID:0/038> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
falconflyer82 said:
Downloaded latest stock rom ML4 and this is what I get in Odin 3.09:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XWUGML4_I9300ODDGML4_I9300DDUGMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/038> Added!!
<ID:0/038> Odin v.3 engine (ID:38)..
<ID:0/038> File analysis..
<ID:0/038> SetupConnection..
<ID:0/038> Initialzation..
<ID:0/038> Get PIT for mapping..
<ID:0/038> Firmware update start..
<ID:0/038> SingleDownload.
<ID:0/038> sboot.bin
<ID:0/038> NAND Write Start!!
<ID:0/038> FAIL!
<ID:0/038>
<ID:0/038> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Nand write fail usually means dead emmc chip. You can try rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but I think you need to send it fto service for repair.
tallman43 said:
Nand write fail usually means dead emmc chip. You can try rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but I think you need to send it fto service for repair.
Click to expand...
Click to collapse
I tried the rescue firmware, similar result:
Code:
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I finally took to a repair shop, they say it is my fault since I rooted it (they can see the red exclamation mark), and will charge extra for "software change".
Any idea how to reset the counter in download mode, revert to stock recovery and remove the red exclamation mark in bootloader?
P. S. I read somewhere in case of dead emmc I shouldn't be able to see the device version in download mode. But I can..
bricked device i9300..
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.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> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
it gets stuck for hours without any response ... can any one help please
dupri11 said:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.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> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
it gets stuck for hours without any response ... can any one help please
Click to expand...
Click to collapse
Did you try Odin 3.09? I too get the same result as you with Odin 3.07. With 3.09 I get the write fail error.
falconflyer82 said:
Did you try Odin 3.09? I too get the same result as you with Odin 3.07. With 3.09 I get the write fail error.
Click to expand...
Click to collapse
I used the 3.09 still same problem am stuked up really
If the rescue firmware and pit didn't flash then your emmc chip is damaged, either new motherboard or phone.
Sent from my GT-I9300 using Tapatalk
falconflyer82 said:
I finally took to a repair shop, they say it is my fault since I rooted it (they can see the red exclamation mark), and will charge extra for "software change".
Any idea how to reset the counter in download mode, revert to stock recovery and remove the red exclamation mark in bootloader?
Click to expand...
Click to collapse
There must be a way to reset the download count by installing stock recovery. Maybe @Chainfire can help here.
Sent from my XT1033 using Tapatalk
dupri11 said:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.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> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
it gets stuck for hours without any response ... can any one help please
Click to expand...
Click to collapse
what @boomboomer said is what you should consider.
If you keep on insisting, you will just damage the phone more ( i am talking from experience ) .
change motherboard or in some places, people can replace the emmc Chip for you.
Salam

Bricked galaxy s2

I tried reverting from Cyanogenmod to official firmware. Whilst flashing my dog jumped on my I9105P and disconnected my phone. Now when i connect it to a charger or USB port it says "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again". Tried flashing with Odin but i get this:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9105PXXUBNG1_I9105PVVTBNG1_I9105PXXUBNG2_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> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also can't go to download mode. It says "Low battery, can't download". I left it to charge all night.
Help?

how to enable usb debugging mode

hi guys,
my phone is soft-bricked and it freezes samsung logo screen on the startup.
How can I enable usb debugging mode on this situation ? Do you have any solution ??
My phone is: Samsung Galaxy S3 GT-I9300 International..
husamba said:
hi guys,
my phone is soft-bricked and it freezes samsung logo screen on the startup.
How can I enable usb debugging mode on this situation ? Do you have any solution ??
My phone is: Samsung Galaxy S3 GT-I9300 International..
Click to expand...
Click to collapse
There is no way how to enable USB debugging mode if is device soft bricked.. Download official FW ,then go to download/bootloader mode and flash it via Odin.
DejVidKo said:
There is no way how to enable USB debugging mode if is device soft bricked.. Download official FW ,then go to download/bootloader mode and flash it via Odin.
Click to expand...
Click to collapse
Hi DejVidKo,
I just get official FW from sammobile, I went to download mode and I am getting an error like below on ODIN. Do you have any guess about what I am doing wrong.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
husamba said:
Hi DejVidKo,
I just get official FW from sammobile, I went to download mode and I am getting an error like below on ODIN. Do you have any guess about what I am doing wrong.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md 5 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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If you have another version of Odin,try Odin v3.04
DejVidKo said:
If you have another version of Odin,try Odin v3.04
Click to expand...
Click to collapse
No wayyy. I tried it too. And I am getting same error. There are more than one rom in sammobile. May I download the wrong rom from sammobile.. :S
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB6_I9300OJVGNB3_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

Galaxy s6 edge stuck in setupconnection

Tried rooting my phone, stuck on startup screen and download mode.
Didn't work so I am now trying to install stock firmware.
When in Odin3, there are different things that happen. It says "Added!!" Sometimes I get stuck at setupconnection, but other times it initializes and i get a nand write start fail.
I am using Odin3 v3.10.6
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU1AOCV_G925FH3G1AOC1_G925FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also get this failure sometimes
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU1AOCV_G925FTEF1AOC1_G925FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
SM-G925F
I have already tried different USB ports, different cables
I can't restart because on the boot screen i get a "recovery is not seandroid enforcing" message.
I'm having the same issue with a non-edge S6, did you find a way to solve it? How did you solve it?
how long does it take normally to flash a rom? I'm trying to flash a stock rom from a hard brick and my odin just sits at setup connection and doesn't move and doesn't get an error either.
If it is hard bricked then nothing short of a jtag will save it.

soft bricked

my latest isue with the samsung sgh-1337 that i have been posting various questions about. i got my new sd card and moved mt titanium bkups from the internal storage including the "update.zip" that i had made and tested with removed bloatware and handful of user apps that i installed and converted over to system apps and included to the update zip. i removed a couple user apps i no longer needed. i read while browsing these forums that the "touchwiz" app is not needed and provides little features, ect. I removed this then rebooted the phone and was going to make a frswh update zip and leave it in the internal storage. the phone then did not want to boot and kept freezing at a blank dark screen. i tried to again do a sytem restore which allowed me to one of the many times i rebooted and kept getting stuck in boot loops or the blank screen. even after the one succesful reset it still stuck at a blank screen.i then tried flashing with oden with the stock replacement rom for this specific model from:androidmtk.com/download-samsung-stock-rom. again i have had the same unsucessful results with oden as follows from odins log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1205)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> boot.img
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
<ID:0/009> Added!!
is this due to a locked bootloader? what can i do to fix this? also have the current version of samsung drivers installed.
different phone and different problem than above phone....the bkrd to how this happened with s3mini being stuck in download/oden mode...installed twrp app from playstore and let it pick the proper rom ect and due its thing but once it rebooted it has been stuck in oden mode
if anyone has seen i have been posting questions and problems with 3 phones that i have the s4 and 2 s3mini sm-G730A with 4.4.2. i was unable to find the oem rom for this but have tried the one for the s4 that also has 4.4.2 along with various others all that fail with the same error as follows from oden log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Removed!!
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1205)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> boot.img
<ID:0/009> FAIL! (Auth)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Categories

Resources