I know several of you guys will be loling at me here...
Everything was working fine until I tried to flash Siyah Siyah 4.1.5. I went into normal recovery mode (Not using Rom Manager) and used a kernel cleaning script then flashed the zip for Siyah. Rebooted and couldn't get past the AOKP loading screen. I tried using I777UCKH7 OCD With Root.exe but it wouldn't work. Everything else I've tried to flash has failed.
After doing some research I found out that my bootloaders may have been messed up with some previous crap I did. I can only get into download mode and it states Product Name: GT-i9100.
I tried to flash the I777UCKH7-CL503881-Full.exe but every attempt gets stuck on <ID:0/003> Sbl.bin.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCKH7-REV02-home-low-CL503881.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> Sbl.bin
I tried using Odin 1.85 and I777UCKH7-REV02-home-low-CL503881.tar.md5 but still the same issue. Can't get past Sbl.bin.
I read in another post that I should flash the param.lfs file first and then use I777UCKH7-CL503881-Full but that doesn't work either. I just get stuck again.
<ID:0/003> Added!!
<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> param.lfs
Ah you have I9100 bootloaders, when the hell did you manage to do that?
Sent from Team Pirate! Using Tapatalk 2
First thing I would try, go to the Download Repository and flash the sbl.bin only. If successful, then try the stock again. You may or may not need to flash the param.lfs separately as well.
AngelsNecropolis said:
I know several of you guys will be loling at me here...
Everything was working fine until I tried to flash Siyah Siyah 4.1.5. I went into normal recovery mode (Not using Rom Manager) and used a kernel cleaning script then flashed the zip for Siyah. Rebooted and couldn't get past the AOKP loading screen. I tried using I777UCKH7 OCD With Root.exe but it wouldn't work. Everything else I've tried to flash has failed.
After doing some research I found out that my bootloaders may have been messed up with some previous crap I did. I can only get into download mode and it states Product Name: GT-i9100.
I tried to flash the I777UCKH7-CL503881-Full.exe but every attempt gets stuck on <ID:0/003> Sbl.bin.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCKH7-REV02-home-low-CL503881.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> Sbl.bin
I tried using Odin 1.85 and I777UCKH7-REV02-home-low-CL503881.tar.md5 but still the same issue. Can't get past Sbl.bin.
I read in another post that I should flash the param.lfs file first and then use I777UCKH7-CL503881-Full but that doesn't work either. I just get stuck again.
<ID:0/003> Added!!
<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> param.lfs
Click to expand...
Click to collapse
I'm sorry, I really am laughing here :laugh:
jthatch12 said:
I'm sorry, I really am laughing here :laugh:
Click to expand...
Click to collapse
Do you need help?
Did you try flashing the sbl.bin?
creepyncrawly said:
First thing I would try, go to the Download Repository and flash the sbl.bin only. If successful, then try the stock again. You may or may not need to flash the param.lfs separately as well.
Click to expand...
Click to collapse
I did try flashing the sbl.bin only and Odin only gets stuck and doesn't proceed just like the previous attempts.
Nick281051 said:
Ah you have I9100 bootloaders, when the hell did you manage to do that?
Sent from Team Pirate! Using Tapatalk 2
Click to expand...
Click to collapse
I'm not entirely sure when this happened. Not recently at least.
I also went to Sammobile and downloaded the "Firmwares for SGH-I777 - USA (AT&T)" I777UCLE5 but it gets stuck.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCLE5_I777ATTLE5_I777UCLE5_HOME.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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
Oh gawd... after the sammobile firmware failed I tried to use the I777UCKH7-REV02-home-low-CL503881.tar.md5 again and Odin finally completed something. Now I'm stuck in a boot loop but can at least boot. I'll try download mode again and see if the unbrick files will work this time.
OK. My phone rebooted successfully... crisis over. lol
I lol'd.
Glad you got it sorted... No more ROM manager for you!
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
Yeah... I'm on my GS3 now that I just got today. Rooted already so I'm preparing for those roms now. My gs2 will hopefully run without any hiccups for my gf. I appreciate all the support everyone provides here. =)
Sent from my Galaxy S II running AOKP Jellybean
Yes.
Sent from my SGH-I777 using Tapatalk 2
Wow.... Rom manager is cool...
Sent from my SAMSUNG-SGH-I897 using xda premium
Related
Phone is 'bricked', and gets stuck on Samsung logo. How do I fix this? I'm trying to follow threads on how to get back to stock, but most of the links are dead - so if anyone can help, that would be great! When following some guides, I get the following error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> param.lfs
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> recovery.bin
<ID:0/003> zImage
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!
Click to expand...
Click to collapse
lolreconlol said:
Phone is 'bricked', and gets stuck on Samsung logo. How do I fix this? I'm trying to follow threads on how to get back to stock, but most of the links are dead - so if anyone can help, that would be great! When following some guides, I get the following error:
Click to expand...
Click to collapse
If you're coming from ICS or CM7, you need pit file for re-partition.
jhssal said:
If you're coming from ICS or CM7, you need pit file for re-partition.
Click to expand...
Click to collapse
Ah! Thanks, worked that time.
First, I know you are going to ask me to search threads started by other people. I did.
And almost every single one of them wanted me to go to "download mode". The problem is I cant go into download mode no matter how long i pressed the 3 button combination.
So, I tried to root my Samsung Galaxy SII, and things got out of control. It went to "Firmware upgrade encountered an issue..."
I've tried other methods in the forums too, and nothing works. Flashing firmwares dont work for me too.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_SIN_I9100DXLP9_I9100OLBLP9_I9100DXLP9.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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
Can anyone help me?
chipzx said:
First, I know you are going to ask me to search threads started by other people. I did.
And almost every single one of them wanted me to go to "download mode". The problem is I cant go into download mode no matter how long i pressed the 3 button combination.
So, I tried to root my Samsung Galaxy SII, and things got out of control. It went to "Firmware upgrade encountered an issue..."
I've tried other methods in the forums too, and nothing works. Flashing firmwares dont work for me too.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_SIN_I9100DXLP9_I9100OLBLP9_I9100DXLP9.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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
Can anyone help me?
Click to expand...
Click to collapse
I had the Exact same problem as you this is what you need to do.
1. Take everything out of your phone micro sd ,sim battery disable kies process as well
2.Get your Usb Port and connect the first side to your pc but not to the phone
3.Insert Battery
4.Hold the vol down butt and at the same time connect the Other side of the cable into the phone then you will see
DOWNLOAD MODE!!!!!
5.From there install your stock rom again using samfirmware.com
6.Done
For 2 minutes it worked, then this came out
<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> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Is it just because my phone has low battery?
THANKS, IT WORKED
Have been fixing it for one whole day, THANKS!!!
custom kernel
chipzx said:
For 2 minutes it worked, then this came out
<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> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Is it just because my phone has low battery?
Click to expand...
Click to collapse
Why don't you install custom kernel..
Go gokhanmoral.com then download latest S2 4.1+ for ICS and JB...
mizzeeboy said:
I had the Exact same problem as you this is what you need to do.
1. Take everything out of your phone micro sd ,sim battery disable kies process as well
2.Get your Usb Port and connect the first side to your pc but not to the phone
3.Insert Battery
4.Hold the vol down butt and at the same time connect the Other side of the cable into the phone then you will see
DOWNLOAD MODE!!!!!
5.From there install your stock rom again using samfirmware.com
6.Done
Click to expand...
Click to collapse
you are GOD!!!
my galaxy s2 is working again, not anymore a dummy
thanks
eheheh said:
you are GOD!!!
my galaxy s2 is working again, not anymore a dummy
thanks
Click to expand...
Click to collapse
glad to help
Not sure which CWM I was coming from, but I wanted to go back to stock. Here is what I did:
C:\Users\Brian\Downloads\Cell Phone\CI500_VZW_EH03_GB_CM.tar.md5
C:\Users\Brian\Downloads\Cell Phone\atlas_v2.2.pit
I select the partition box and got this error.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> param.lfs
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> recovery.bin
<ID:0/003> zImage
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help. I dont know what else to do. Thanks so much.
I literally have tried everything. Not sure if the .tar is incorrect, or what is happening. Phone wont turn on though, its stuck on the samsung logo boot.
Have you:
Tried a different usb cable (or several)?
Tried a different usb port?
Tried a different OS?
Tried a different version of Odin?
Tried redownloading the files?
Tried stock 2.2 Froyo instead?
Looks like it was the USB cable. Damn i spent like 2 hours researching and trying everything . Thanks for the response bro. Have a good one.
No problem, it's always the last thing you think of. Glad you got it though
Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
xMopx said:
Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
Click to expand...
Click to collapse
You can't flash backwards. Flash me7.
gnubian said:
You can't flash backwards. Flash me7.
Click to expand...
Click to collapse
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
xMopx said:
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
Click to expand...
Click to collapse
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
xMopx said:
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
Click to expand...
Click to collapse
Just go to the safestrap app in app drawer on stock slot and uninstall it.
gnubian said:
Just go to the safestrap app in app drawer on stock slot and uninstall it.
Click to expand...
Click to collapse
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
xMopx said:
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
Click to expand...
Click to collapse
What happens when you start the phone?
gnubian said:
What happens when you start the phone?
Click to expand...
Click to collapse
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
xMopx said:
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
Click to expand...
Click to collapse
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
gnubian said:
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
Click to expand...
Click to collapse
Positive. I had installed the rom/recovery before anything newer than me7 was released. And I remember when I upgraded from whatever it shipped with to ME7 because the upgrade window popped up and I tapped Install by accident. I had this installed: http://forum.xda-developers.com/showthread.php?t=2351840.
Edit: to confirm, I found my old post asking about the modules to get that rom to work on ME7: http://forum.xda-developers.com/showthread.php?p=46944438
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
gnubian said:
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
Click to expand...
Click to collapse
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
xMopx said:
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
Click to expand...
Click to collapse
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
gnubian said:
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
Click to expand...
Click to collapse
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
xMopx said:
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
Click to expand...
Click to collapse
Try finding a stock recovery tar for your build and just flashing that in odin.
gnubian said:
Try finding a stock recovery tar for your build and just flashing that in odin.
Click to expand...
Click to collapse
I had the thought of doing this, but wasn't able to find one.
xMopx said:
I had the thought of doing this, but wasn't able to find one.
Click to expand...
Click to collapse
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
gnubian said:
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
Click to expand...
Click to collapse
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
xMopx said:
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
Click to expand...
Click to collapse
I believe it has to be a tar. If you can get it on there and wipe data/factory reset it may get rid of safestrap and allow you to odin the full stock tar.
Hello everyone,
I have installed Resurrection Remix (Resurrection_Remix_KK_v5.1.5-20140609-i9100) and suddenly my phone turned off and stucked at the boot logo.
I can't start the recovery mode only the download mode is possible.
I have tried to reflash the recovery but it doesn't work. I have tried different cables and PCs without any success. I also tried different odin versions.
I think I have a NAND rw issue.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XWLSD-OXX-4.93.6.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!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
I have read different threads about stucked phones, but I am unsure which recovery package would be the right one, f.e. http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571
I just want to save as much as possible.
Every help is appreciated.
h3llghost said:
Hello everyone,
I have installed Resurrection Remix (Resurrection_Remix_KK_v5.1.5-20140609-i9100) and suddenly my phone turned off and stucked at the boot logo.
I can't start the recovery mode only the download mode is possible.
I have tried to reflash the recovery but it doesn't work. I have tried different cables and PCs without any success. I also tried different odin versions.
I think I have a NAND rw issue.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XWLSD-OXX-4.93.6.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!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
I have read different threads about stucked phones, but I am unsure which recovery package would be the right one, f.e. http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571
I just want to save as much as possible.
Every help is appreciated.
Click to expand...
Click to collapse
Do you installed Samsung drivers firstly? If no, download this and install. Restart PC.
If yes,
Download this kernel (Apollo kernel with TWRP) and flash it! after, you can install what ROM do you want! If you want KK install CM11-M12.
Hit Thanks button if I helped you!
IonutGherman said:
Do you installed Samsung drivers firstly? If no, download this and install. Restart PC.
If yes,
Download this kernel (Apollo kernel with TWRP) and flash it! after, you can install what ROM do you want! If you want KK install CM11-M12.
Hit Thanks button if I helped you!
Click to expand...
Click to collapse
Same odin output as before.
h3llghost said:
Same odin output as before.
Click to expand...
Click to collapse
What version of ODIN do you use?
I have tried 1.8.3, 3.1.6 and the latest one.
try this: http://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
IonutGherman said:
try this: http://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
Click to expand...
Click to collapse
I have two issues with that, which package should I choose and the downloads are not available for Germany. Is there another mirror?