So I flashed my T959 with a T959V kernel and now I'm stuck in the booting screen. I could get into download mode. What can I do to get my phone working again?
What version of android are you running? The easiest thing to do would be to flash a kernel via Odin, but I can't really suggest one unless I know what exactly you're running.
Sent from my SGH-T959
I updated my phone from 2.1 to 2.2 via kies mini, then I rooted the phone with SuperOneClick. Finally I flashed this kernel http://forum.xda-developers.com/showthread.php?t=1080871 with SGS kernal flasher (something like that) from the play store. Now I'm stuck on the boot screen whenever I boot.
I see. Well, let's try something.
Have you ever used Odin before? If not, you can download it here:
ODIN
You're also going to need to download this kernel:
Overstock Kernel
Now, once those two files are downloaded, you're going to wanna' run the Odin executable I linked above. More than likely, there's going to be a check mark checked for Re-partition, F. Time Reset, and/or Auto Reboot. Although regardless of what's checked, you're going to want to uncheck everything. Once everything is unchecked, your going to want to click PDA and select the OverStock kernel you previously downloaded. Put your phone into download mode, an ID:COM should light up yellow, then hit Start. Once it has finished, giving you the message PASS!, you're going to want to pull your phone from the computer and remove the battery pack. Then, put the battery back in and finally, reboot your phone.
Sorry if my steps are confusing. I'm not by my computer, so I'm going off of memory. Please, don't hesitate to ask any questions. I'll be glad to help or explain anything.
Sent from my SGH-T959
I followed your instruction and once I click start, it failed. Here's the log
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Now my phone has phone to computer icon with a yellow caution sign. Have I successfully hard bricked my phone?
edit: I have a jig if that would help.
I tried to flash the kernel through Odin again and it worked. Now my phone is up and running, but I can't seems to download any apps from the play store. I wipe all the cache in recovery and try to start things fresh, but the play store just wouldn't let me download any apps. It just starts the download, pause and cancel my download as if nothing happened. I tried to install again and the entire play store crashed. At this point how can I download apps and flash custom ROMs?
I think this might help you if you soft brick your device One-Click UnBrick
Regarding the play store issue check this
Hope this will help
tc
After a night of flashing, I returned to JFD and started all over. Everything is running great now. I didn't realize SGS was such an amazing phone until I flashed a custom rom yesterday. Sleeping at 5 am yesterday was well worth it. Thanks for all your help.
Related
So, I tried to root my phone, following Chainfire's guide. I did everything EXACTLY as I was supposed to, but after flashing the kernel in Odin, with XWKDD_insecure.tar, the device no longer worked. It rebooted into a screen with a grey battery and the loading loop, but nothing happened. I didn't even get a chance to use SuperOneClick, because the program just stalled when it said "Waiting for device...". After about 5 minutes, I held down the power button, and then the GS2 logo appeared with a yellow exclamation sign underneath it. And SuperOneClick still didn't register the phone.
I pulled the battery out, booted into download mode again, then tried to install the factory firmware I downloaded from samfirmware.com. But then this happened:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XWKDF_CL170898_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKDJ_REV_02_CL996627.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXXKDD.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> factoryfs.img
<ID:0/004> data.img
<ID:0/004> cache.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response form LOKE
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
When I saw it, I actually felt physically ill.
So what do I do now? I have a choice of booting into download mode, or turning the phone on normally, and getting a screen that says the update fail to load. Is there something else I can do to reset factory settings, or is that the end of my brand new phone
U could still try to reflash the rom again, check if the file u downloaded is not corupted.
You have to bear in mind that Odin can be temperamental, redownload a firmware and flash it again.
Going off memory here as im not at my pc but it looks like you have too many things in to your odin program.
first thing i notice is that you have the "Re-Partition" box selected, it was my understanding you only need Auto Reboot and F.Reset Time checked.
You could also try getting the most upto date version of Odin too which is v1.85.
Also you have entered something in to the PIT section, when i flashed my device with the firmwear from samfirmware (I9100XWKDF) i didnt put anything in the PIT section.
Maybe try changing them and i hope it works.
Crucio
Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
Why do you have Re-Partition,phone,css selected ?
Prey that you dont bricked it
Looks like you get first to brick an SGS 2 prize any way .
jje
Not a prize i would like to win heh..
Lets just hope it can be flashed again.
moparman said:
Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
Why do you have Re-Partition,phone,css selected ?
Prey that you dont bricked it
Click to expand...
Click to collapse
They have Phone and CSS selected as they were flashing the firmware with the version from samfirmware.com (the one that removes branding and updates the battery usage part) not just the kernel to root the device.
Surely if this device is in a limbo it would make sense to flash this (stock firmware) before flashing a rooted kernel?
id guess the first attempt of the root failed due to the re-partition box being checked but im not 100% on that.
im a rookie to
I just read the instructions to root...
Maybe it works if repartition is not checked and reflash?
I hope someone with better skills then me can help.
If i had done this i wouöd die of a broken hearth
I remember how afraid i was to flash my TyTn2 the first time..And i didnt have any problem
yeah im a rookie also, lets hope someone with a bit for knowledge can help this guy out if we havent ^^
my heart would sick too, it did a bit when i flashed the firmware and it was german that was fixed easy tho lol.
The repartition basicly changest the size of some system partitions based od the PIT file, its not recomended to use the repartition, but that shouldnt be the problem why the ODIN failed.
As he said he is able to go to download mode so he should be safe, just reflash the rom or try other rom versions and flash them.
Crucio_ said:
They have Phone and CSS selected as they were flashing the firmware with the version from samfirmware.com (the one that removes branding and updates the battery usage part) not just the kernel to root the device.
Surely if this device is in a limbo it would make sense to flash this (stock firmware) before flashing a rooted kernel?
id guess the first attempt of the root failed due to the re-partition box being checked but im not 100% on that.
Click to expand...
Click to collapse
The screenshot I posted was from after the damage was done. I had already given up on trying to root my phone, and was trying to install the firmware from SamFirmware, in the hope that it would get my device back to factory settings.
Initially, when I flashed the kernel with Odin, nothing was selected except for "Auto reboot" and "F. Reset Time", and the only file loaded was the XWKDD_insecure.tar on the PDA line. I was also using Odin3 v1.85 at the time. The firmware I downloaded from SamFirware came with v1.83 and I didn't even notice that it wasn't the latest version.
Can someone give me a step by step of what I can do to completely wipe the device, and restore it to factory settings, as that's what I was trying to do, and it clearly didn't work?
rheedan said:
Can someone give me a step by step of what I can do to completely wipe the device, and restore it to factory settings, as that's what I was trying to do, and it clearly didn't work?
Click to expand...
Click to collapse
that's exactly what you're doing when you're flashing a complete new firmware with repartition ;-)
(which is what you did/ or tried to)
that is on your screen you're flashing modem/csc/full pda etc aka complete wipe and factory setting reset
repartition formats the memory by wiping the partition table and creating a new one (its like "quick format" on a pc)
bilboa1 said:
that's exactly what you're doing when you're flashing a complete new firmware with repartition ;-)
(which is what you did/ or tried to)
that is on your screen you're flashing modem/csc/full pda etc aka complete wipe and factory setting reset
repartition formats the memory by wiping the partition table and creating a new one (its like "quick format" on a pc)
Click to expand...
Click to collapse
I don't know if I should be comforted by the fact that I tried to do the right thing, or disheartened by the fact that doing the right thing didn't solve my problem.
Is there perhaps another way to go about the whole process? Should I try another ROM? The one I used was a European XWKDF Gingerbread 2.3.3, but I also have the Russian XEKDB firmware from http://forum.xda-developers.com/showthread.php?t=1057535 - I think it's 2.1.1.
there is not much experience with the SGS2 yet and I don't have one yet personally. Never saw that one error but form the SGS1 experience i'd say try reflashing, and try flashing other SGS2 firmwares ;-)
i havnt flashed mine yet but will wait till i get insurance for the phone because (and i mention this so that people can do the same thing if they wish).. if it does brick then the option of it "accidentally falling onto a busy motorway" is open to me lol
OK, looking at your screenshot, you flashed too many files, and reformated.
Follow this guide.
http://androidadvices.com/how-to-up...ii-i9100-to-gingerbread-xwkdd-2-3-3-firmware/
Make sure you download the files from there as well. I have flashed mine with them after I broke a few things playing, and it worked fine after.
This will get you up and running again.
Then for Root, go to this thread
http://forum.xda-developers.com/showthread.php?t=1056334
Download the XWKDD_insecure.tar file
Odin, Without repartion checked.
Only files to link are the pit file, in pit and XWKDD_insecure.tar in PDA
Then you can use SuperOneClick to add root.
Don't panic, I doubt its a brick.
Good luck
Broomfundel said:
Don't panic, I doubt its a brick.
Click to expand...
Click to collapse
It is fairly hard to brick a Samsung properly, without actually trying... Hope that's some reassurance.
The fact you can get into download mode is a reassurance, as that should be the key. I've not owned a Samsung device, so I won't try and advise how to fix it, but I'd agree about trying that above link to install the "beta" firmware.
ODIN is pretty good, but there isn't much experience in flashing these yet, as I don't know of any devs with them. I might go out at the weekend and get one, but I'll not be starting properly on it until June realistically...
Let us know if the fine folks here have resolved the problem. Looking and learning from peoples experience before I make the leap and root.
(Still waiting for launch in India)
dhruvmalik said:
Let us know if the fine folks here have resolved the problem. Looking and learning from peoples experience before I make the leap and root.
(Still waiting for launch in India)
Click to expand...
Click to collapse
now i will never root my s2 when i will get it, faced the same sitution with my n8 once
I tried flashing US boot loader and I receive this:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> param.lfs
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I received the file from this thread. http://forum.xda-developers.com/showthread.php?t=1531850
did you try turning the device on and off again?
Try redownloading the file you're trying to flash, sometimes they get corrupted.
Why are you trying to flash bootloaders anyway? Is your player seriously screwed up?
Ill try that. The player boots straight into recovery, that's my primary issue.
dktfoster said:
Ill try that. The player boots straight into recovery, that's my primary issue.
Click to expand...
Click to collapse
If you're getting recovery your bootloaders should be fine. Probably just need to reflash kernel/rom.
I've done that and it still boots straight into recovery
Are you sure you have the right kernel and rom? Maybe try a different one from the dev section?
I have the 4.0 us, I'm 100% sure I have the right rom. I might just send it back to Samsung. This whole problem started after flashing over to Klins Klassic and doing a factory wipe.
Try a different rom for your device.. it shouldn't be irreversibly screwed up.
Sent from my SGP5
dktfoster said:
I have the 4.0 us, I'm 100% sure I have the right rom. I might just send it back to Samsung. This whole problem started after flashing over to Klins Klassic and doing a factory wipe.
Click to expand...
Click to collapse
Redownload the Us restore pack. Ensure that re-partition is checked.
YP-GP70CWY
Hello,
I just encountered the same problem with my SGP5. It got stuck and reboots to the Android Recovery. I was trying to install a tweak on it after rooting and it just happened. I could go to kies no problem. But the main is, I can't get the OK/Power button to confirm so that I can wipe everything. Vol+- works but no confirmation. What should I do?
It is really hard when someone is on a learning curve. This is totally different for me.
Thank you very much for the devs and help.
....................................
I thought I had bricked it. I made it working again by reinstalling a rom.
thank you anyway.
I had one of my players that kept booting into recovery after resurrection from hard brick. Flashing a different rom fixed it. Flash a rom with CWM and use CWM to factory reset the device and retry. It took me a couple of tries, but I managed to get it to boot correctly.
cvcduty, I have read your little guide to restore the Galaxy Player on AdamOutlers' thread but it still won't work.. If you can please help me out, I'd be very grateful/appreciative. Thanks!
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<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> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
I found that sometimes its all in the technique of how you plug things in and the usb used. Try different usb cords. Try different usb ports. and then for some reason what worked for me is have odin open plug usb into computer, and then put the phone into download mode and finally connect the microUSB into the phone. Hope it works, hit back if it does or doesnt
[email protected] said:
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<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> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
Click to expand...
Click to collapse
How long did you let it go for on the factoryfs.img?
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
creepyncrawly said:
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
Click to expand...
Click to collapse
I have tried it on all usb ports that I have on my laptop.
OK here's exactly what I did to my phone:
I downloaded the ICS version for i777 from sammobile and flashed it using ODIN. Then, I installed Siyah kernel using mobile odin. I then installed triangle away to get rid of the flash counter. I used my phone like this for a couple of days. Then today, I installed the AOKP rom. To do this, I first back up using CWM, then i booted in CWM recovery mode, did a complete wipe, deteled cache and dalvik, and then I proceeded to install the rom. Installation worked fine and everything, however the data wasn't working on my phone. So I then tried to enter the T-Mobile APN settings (it's an unlocked phone), however I couldn't save the APN settings. Tried to enter them multiple times and selected save from the menu, but it just wouldn't show up on the APN list. So, I tried to restore to my back up in CWM restore, however that failed. Admittedly, I should have asked for help at this point. However I was frustrated, so I decided to just use Odin again to flash the ICS stock firmware that I got from sammobile. However, it failed and had some error along the lines of completed writing but operation failed? I tried switching to different USB ports and restarted Odin with run as administrator, but kept getting the same error. On one of these numerous tries, I also tried to check the re-partition option just to see if that would change anything (probably not a very smart idea). Anyways, at some point during these numerous attempts, it got to the point where the phone wouldn't boot up and asked me to connect to samsung kies to restore. I tried that but my phone won't connect with kies. I then found your one-click odin stock firmware thing on these boards and used that. Tried multiple times at different ports, but it keeps getting stuck at factoryfs.img. I have left it in there for a good 30 minutes in this current try (4th). Also, this may or may not be relevant, the flash counter keeps going up.
PS: This is my first android phone so I'm pretty new at this, but I did try to read up a lot before trying anything (well, except for when I randomly checked re-partition that one time).
Edit: Sorry I should have made this clear - even though the phone will not boot, I can still get into download mode.
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
creepyncrawly said:
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
Click to expand...
Click to collapse
'
Thank you for the swift response. No, I am unable to get into recovery mode. It goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
While I didnt have your issues. I also recently bought an i777, my install went very smooth, everything worked more or less on the first try tried diff cords, ports and then finally it was the plug sequence that did it for me. Upon flashing AOKP, I immediately unlocked the phone via that galaxy S unlocker, I followed the steps to the T and my IMEI is still the same. I am also on tmobile, with working edge. I still have the pesky triangle, but I havent read too many good things about the triangle remover.
Perhaps you have a bad rom download? It might sound silly but flashing AOKP for a friend when I redownloaded the rom, everything worked fine. What the guy above me said, try recovery mode instead and then go from there. Good news is that your phone doesnt sound borked
creepyncrawly said:
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
Click to expand...
Click to collapse
Ok I tried this, and it completed successfully in Odin, however, the phone now gets stuck on the "Samsung Galaxy SII GT-I9100" screen.
But will it boot into recovery now?
creepyncrawly said:
But will it boot into recovery now?
Click to expand...
Click to collapse
No, it still does not boot into recovery.
OT: How long will I have the 5 min restriction on posting?
Also, I don't know if this is relevant, but when I try to turn off the phone, it turns off but then it'll automatically start back up within a few seconds and then get stuck on the samsung galaxy sII screen
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
creepyncrawly said:
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
Click to expand...
Click to collapse
No, I didn't put a pith file. Also just to make sure I'm flashing the right file, is it the one called "I777 UCKH7 stock param.lfs"?
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
creepyncrawly said:
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
Click to expand...
Click to collapse
It was the UCLE5 file. I'll try this one.
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.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> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
[email protected] said:
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.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> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
Click to expand...
Click to collapse
OK I tried it on all the USB ports that I have on my laptop. No luck. Still getting stuck at Sbl.bin. Any more ideas?
Yes. If it were my phone, I would start by flashing the param.lfs by itself and see if that allows it to boot, or makes progress.
If not, then I would flash the sbl.bin by itself and see if that allows it to boot, or makes progress.
If still not, then I would try the full UCKH7 package with the PIT file, and repartition checked.
You can get all the files from the Download Repository. Please bear in mind that there is risk in everything you are doing, (and have been doing.)
Hi,
I've looked everywhere to solve this problem but with no solution.
Yesterday I decided to flash my firmware from the leaked Jelly Bean from last November to the stock ICS in order to have my phone back to the normal update way.
However, when I try to flash with Odin, it gets stuck and has this:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I have PhilZ Touch 3 on the phone and chose "Clean Before Flash New ROM" in recovery. Problem is that this didn't help with Odin and now my phone just sits on the "Samsung Galaxy SII GT-I9100" screen and doesn't move.
Apologise for my noobishness
The 'Odin doesn't work' thing gets covered more times in a week than pretty much anything else on here. You need to search for/read those threads & find the set list of troubleshooting steps you need to try & keep trying those until the flash works. It is almost always (in 99.99999999999999999999999% of cases) something very simple/obvious not being done or being skipped that causes the flash not to work.
MistahBungle said:
The 'Odin doesn't work' thing gets covered more times in a week than pretty much anything else on here. You need to search for/read those threads & find the set list of troubleshooting steps you need to try & keep trying those until the flash works. It is almost always (in 99.99999999999999999999999% of cases) something very simple/obvious not being done or being skipped that causes the flash not to work.
Click to expand...
Click to collapse
Yeah thanks. I've looked over and found a whole list on here such as try different computer, different ports, run as admin etc etc and they didn't work after trying them over and over. They seemed quite generic :crying: I thought it might have been a problem with the fact that PhilZ is on there. Or should that not make a difference?
JackJack94 said:
Hi,
I've looked everywhere to solve this problem but with no solution.
Yesterday I decided to flash my firmware from the leaked Jelly Bean from last November to the stock ICS in order to have my phone back to the normal update way.
However, when I try to flash with Odin, it gets stuck and has this:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I have PhilZ Touch 3 on the phone and chose "Clean Before Flash New ROM" in recovery. Problem is that this didn't help with Odin and now my phone just sits on the "Samsung Galaxy SII GT-I9100" screen and doesn't move.
Apologise for my noobishness
Click to expand...
Click to collapse
Did you install KIES PC software? If yes, try following:
On your PC:
ctr+alt+del > start task manager > processes > find all processes with "kies" in their names (there should be two or three running) > kill all of them.
Then try odin again.
Whatever firmware (rom or kernel) you currently have on the phone is irrelevant/won't affect anything you try to do in download mode.
That advice is generic for a very good reason. In the overwhelming majority of cases where this happens, it's one of those steps not being done (or people saying they've 'tried everything' when they haven't). You haven't said anything to indicate your case is any different, I would suggest you find an actual thread that has all the steps listed rather than just a couple of them (Immortalneo was the last person to list the lot of them recently, search his posts); there's about 10-12, and keep trying them. That's the only way you're fixing your phone.
Many40 said:
Did you install KIES PC software? If yes, try following:
On your PC:
ctr+alt+del > start task manager > processes > find all processes with "kies" in their names (there should be two or three running) > kill all of them.
Then try odin again.
Click to expand...
Click to collapse
Yeah I tried that to. I removed the Kies and KiesTrayAgent. Still no luck
MistahBungle said:
Whatever firmware (rom or kernel) you currently have on the phone is irrelevant/won't affect anything you try to do in download mode.
That advice is generic for a very good reason. In the overwhelming majority of cases where this happens, it's one of those steps not being done (or people saying they've 'tried everything' when they haven't). You haven't said anything to indicate your case is any different, I would suggest you find an actual thread that has all the steps listed rather than just a couple of them (Immortalneo was the last person to list the lot of them recently, search his posts); there's about 10-12, and keep trying them. That's the only way you're fixing your phone.
Click to expand...
Click to collapse
Okay thanks for that. I'll check that out. And thanks for clearing up about the current firmware to. Makes me feel a bit more relieved :fingers-crossed:
JackJack94 said:
Yeah I tried that to. I removed the Kies and KiesTrayAgent. Still no luck
Click to expand...
Click to collapse
OK, then just follow the advice given already by MistahBungle (you must have missed something)
BTW what is exactly firmware you are trying to flash, is it made for your device, might be bad download ....
I had a S2 i777, then I got a S3 so I gave the S2 to my mother. I just installed fresh ShoStock because I thought that would work well. It worked ok, but after about a month I came home and she said it wasnt working.
It appeared to be bootlooping at the ShoStock logo. I downloaded a new rom for it on my phone the put the SD card in her phone, booted into clockwork and tried flashing it. Trying to wipe or flash at all results in hanging for a few minutes then rebooting and getting stuck at the Samsung S2 logo now. Since then I've tried various odin methods for flashing to unbrick around xda. Every time I try to flash with odin, it either says error or it just hangs until I manually stop it after 30+ minutes. I've even got as desperate as to have Kies revert it to stock, it also hangs at 2%.
At this moment, you can see the screen its stuck it in the attached screenshot, its probably worth noting its been at this screen ever since the first Odin flash failed.
I do have a microUSB jig so I can kick it into download mode if I have to. Anyone got any ideas :f
Try the following procedure exactly as written. In case the problem is nand read/write corruption, this should clear it and get the phone working again.
1) Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.
2) Successful? Nice. Next, flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
When I try and flash Siyah in Odin for step 1, it just hangs.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
Click to expand...
Click to collapse
The box at the top says kernel and the progress bar goes all the way across, it will never get past this.
Since it won't flash the kernel, the next thing to suspect and try to find out if the cable is faulty. Or anything in the path from the computer to the phone. So...
Try a different cable, or as many different cables as you can put your hands on.
Try different ports on the computer, and use the ones attached directly to the motherboard if it is a desktop.
Try a different computer.
In some cases where there is a connection problem, just flashing repeatedly may eventually result in a pass, as some have reported.
Tried it on two different laptops, with three different microUSB cables on each, no dice.
I tried flashing the kernel from step one you gave, I also tried the I777UCKH7-CL503881 FULL Odin3 One-click from the Download Repository and it hangs at:
<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> boot.bin
<ID:0/003> sbl.bin
<ID:0/003> param.lfs
<ID:0/003> cache.img
Click to expand...
Click to collapse
I don't have any additional suggestions for trying to fix it yourself. The problem could be one of several things. It doesn't seem like a simple soft brick. Maybe it could be damaged memory or some other hardware failure. Or maybe not.
If you are close to an AT&T service center, maybe you could take it by and ask them to flash it back to stock for you. If that fails, then at least you are pretty sure the problem is in the phone, not the connection. I realize it is not under warranty any longer, but they should at least try that for you.
You could send it to Samsung repair center to be worked on. They would probably fix it, but it won't be free, and it will also take two to three weeks. If it were me, I would call them first and discuss the issue with them.
Give these guys a call or message them and tell them your problem and they can most likely fix it. I have had work done by them in the past there quick and there professional...
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-at-t/
Sent from my SGH-I777 using xda app-developers app