[PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.3.0 Available) - Captivate Android Development

Original Thread:
What is Heimdall?
Heimdall is a cross-platform open-source tool suite used to flash ROMs onto Samsung Galaxy S devices.
How does it work?
Heimdall uses the same protocol as Odin to interact with a device in download mode. USB communication in Heimdall is handled by the popular open-source USB library, libusb-1.0.
Why “Heimdall”?
The flashing software Odin is named after the king of gods in Norse mythology. Loke, the software component on the Galaxy S that provides functionality to flash, may also to be named after an important character in Norse mythology, often translated as Loki. As such I have named my flashing software Heimdall, after the Norse god, and guardian of the Bifrost Bridge.
What platforms does Heimdall run on?
Linux, OS X and Windows (XP, Vista, 7 etc.)
Why use Heimdall when we can use Odin?
Odin is generally unreliable and only runs on Windows systems. Furthermore, Odin is leaked Samsung software that is not freely available or well understood by the community.
Is Heimdall safe?
No matter what method you chose, flashing firmware onto your phone has a lot of potential for disaster. We have tested Heimdall with a variety of phones flashing several different firmware versions resulting in a 100% success rate. As such we believe that Heimdall is generally reliable. However keep in mind, just like any flashing software, Heimdall has the potential to brick your phone if not used correctly.
How do Galaxy S phones get bricked when flashing?
Besides the inherent risks like power outs, accidental removal of the USB cable etc. The Galaxy S appears to be running extremely unreliable USB control software.
A failure to flash does not automatically equate to a bricked phone. However if you're extremely unlucky and the flash fails whilst transferring the primary boot-loader, secondary boot-loader or params.lfs (all quite small) than you've got yourself a paper weight that you're hoping Samsung will replace.
Please be extremely careful mixing files from different firmware releases. Don't do so unless you're certain it will work!
What Galaxy S variants has Heimdall been tested with?
We’ve tested Heimdall with a Galaxy S GT-I9000 (8 GB) from the United Kingdom and Galaxy S GT-I9000 (16 GB) from Australia. We don’t personally have access to any other devices to test with, however users have confirmed Heimdall functions correctly with the AT&T Captivate, Bell Vibrant, Telstra GT-I9000T, Epic 4G and the Galaxy Tab.
Enough talk, where can we get it?
The latest release is available here. Please read the instructions and README files included in the archives.
I love you, man. Will you have my baby?
No, but I will very gladly accept donations. If you appreciate my work and would like to support future development you can make a donation here. If you think you have something else to offer, then feel free to shoot me a PM or contact me via the contact form on the Glass Echidna website.
Click to expand...
Click to collapse

Haven't seen this thread get too much attention, but it is a really cool idea especially for non-windows users. Just to kick it off:
Phone Name: Samsung Captivate (JH3 Firmware)
Country: United States
Carrier: AT&T
Hardware IDs:
USB\Vid_04e8&Pid_681c&Rev_0400
USB\Vid_04e8&Pid_681c

It would be nice if someone was willing to see if the Captivate works with this app. Having a cross-platform standardized program is a good idea.
Right now there seems so be a number of different ways to achieve a goal. What we need is a standardized app that devs can make "packages" for where we can select what we want and a rom, zip file or whatever could be built on the fly. easy peezy I say.

Phone Name: Samsung Captivate (JH2 Firmware)
Country: United States
Carrier: AT&T
Hardware IDs:
USB\Vid_04e8&Pid_681c&Rev_0400
USB\Vid_04e8&Pid_681c

Phone Name: Samsung Captivate I897 (JF6)
Country: USA
Carrier: AT&T
Hardware IDs:
[email protected]:~$ lsusb
Bus 001 Device 027: ID 04e8:681c Samsung Electronics Co., Ltd
seems all of the captivate IDs are 681c, which mirrors the international version.

Just to throw in my 2 cents:
I'm a linux user (have windows on dual boot on one machine, but hate going into it just to flash), so I really hope this project moves forward. I'd be willing to test any early linux builds once they're ready.
Phone Name: Samsung Captivate
Country: USA
Carrier: AT&T
Device ID: 04e8:681c Samsung Electronics Co., Ltd

If we had some documentation for the bml devices, it might be possible to provide a utility that could flash kernels from an update.zip. There its a flashing utility, vmlwrite, for the Moment, and it even runs on Galaxy S, but whatever mechanism it uses to map labels to partitions doesn't work. I've been looking for sources to see if they can be modified for our use, but I haven't found anything yet.
Sent from my SAMSUNG-SGH-I897 using XDA App

Just thought I'd drop by and let you all know a stable beta has been released. I've only personally tested with two GT-I9000's (UK and Australian models) so I'm not 100% certain what Galaxy S derivatives will work.
This release includes source code and Windows binaries. It compiles and runs brilliantly on Linux but unfortunately I haven't been able to get phones detected on OS X. If someone else would like to give it a try that would be great.
Please post any questions in the official thread so I can keep track of them.

---------- FORM ----------
Phone Name: Samsung Captivate i897
Country: USA
Carrier: AT&T
Hardware IDs:
USB\VID_04E8&PID_681C&REV_0400
USB\VID_04E8&PID_681C

I have been following and posting on the original thread. Windows 7 and Windows Vista pcs and a captivate-i897.
As i posted, i had a few problems at first,, but successfully used this to flash today. Will continue testing and reporting.

Always remember that bad things CAN happen when you mess with the areas this program messes with. Also, bad things can ALSO happen when you aren't VERY careful with beta releases in general. Therefore, if you put those things together, like you are doing with this program, you are doing a dangerous thing. YOU CAN KILL YOUR PHONE!!!
I'm not saying it WILL happen, just that it CAN..... so BE CAREFUL!! Don't be afraid to test, but carefully.....
And yes, I support this program, I just don't wanna see people willy-nilly jumping in and possibly damaging their devices, then saying it's not their fault.

Pulling from my phone directly to make own firmware odin using either Heimdall/odin
Hi, I tried to create this thread.
http://forum.xda-developers.com/showthread.php?p=15695721
The idea is how to make it own firmware after make custom ROM.
I'm still not sure for boot.bin and Sbl.bin if pulling from my phone will cause any problem or not.
Should I use from stock firmware to use your program while flashing?
Can I say Primary boot loader is boot.bin and while secondary boot loader is Sbl.bin?
It seem your program Heimdall will suitable to build package.
But I still having difficulties how to use your program to create a package firmware like stock firmware.

Heimdall Suite 1.3.0 is now available from the Heimdall product page.

heimdall saved me awhile back! Phone was really messed up, wouldn't connect to PC, windows didn't reckognize it so I booted up my linux install, downloaded heimdall and boom, phone is working well over a year down the road! Great for those who don't use windows or have problems with USB drivers on win 7

[Q] None Galaxy S Samsung devices?
Benjamin Dobell said:
Just thought I'd drop by and let you all know a stable beta has been released. I've only personally tested with two GT-I9000's (UK and Australian models) so I'm not 100% certain what Galaxy S derivatives will work.
This release includes source code and Windows binaries. It compiles and runs brilliantly on Linux but unfortunately I haven't been able to get phones detected on OS X. If someone else would like to give it a try that would be great.
Please post any questions in the official thread so I can keep track of them.
Click to expand...
Click to collapse
I get "Server not found" when clicking on the official thread link.
Nonetheless, I have a question: will this work with non-Galaxy S devices? I'd like to try it out on my Samsung Sidekick 4G, which should arrive this week.

Drat. Can't find heimdall packages for my Sidekick...

Is this the thread referred to above: http://forum.xda-developers.com/showthread.php?t=1104826 ?

Heimdall Kernel flash unreliable
I seem to have problems using Heimdall 1.3.0 on Mac OS X to flash my phone. I'm just trying to flash a kernel as follows:
Code:
heimdall flash --kernel zImage
But it often times can't find my phone even though it connected in Download Mode. When it does find my phone, it seems to get stuck at Kernel 0%. After that, it seems I need to restart Download Mode on my phone before I can attempt again, after getting stuck at Kernel 0% several times, I finally got it to finish the full flash, but it seems like it shouldn't take so much effort. Is this normal for Download Mode on a Samsung Captivate or might it just be a bad USB cable? I think I have the Gingerbread Captivate bootloaders currently installed, but do other bootloaders work better with Heimdall?
Here is the full log of a failure with Kernel 0%:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Beginning session...
Handshaking with Loke...
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
0%
ERROR: Failed to send file part packet!
KERNEL upload failed!
Ending session...
ERROR: Failed to send end session packet!

penguin359 said:
I seem to have problems using Heimdall 1.3.0 on Mac OS X to flash my phone. I'm just trying to flash a kernel as follows:
Code:
heimdall flash --kernel zImage
But it often times can't find my phone even though it connected in Download Mode. When it does find my phone, it seems to get stuck at Kernel 0%. After that, it seems I need to restart Download Mode on my phone before I can attempt again, after getting stuck at Kernel 0% several times, I finally got it to finish the full flash, but it seems like it shouldn't take so much effort. Is this normal for Download Mode on a Samsung Captivate or might it just be a bad USB cable? I think I have the Gingerbread Captivate bootloaders currently installed, but do other bootloaders work better with Heimdall?
Here is the full log of a failure with Kernel 0%:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Beginning session...
Handshaking with Loke...
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
0%
ERROR: Failed to send file part packet!
KERNEL upload failed!
Ending session...
ERROR: Failed to send end session packet!
Click to expand...
Click to collapse
I seem to have more issues flashing with Heimdall 1.3 then I did flashing with 1.1 as well. Similar issue as the one you're having granted I don't think it's ever failed a flash once Heimdall's seeing my phone...

Are you using heimdall front end 1.3.0, or are you using command line. In the front end version under utilities there is a detect device feature. I always check to insure it sees my phone before I flash. Also what version of OSX are you on, because I'm pretty sure its not compatible with lion just yet
Sent from my SAMSUNG-SGH-I897 using xda premium

Related

[Q] Install DJ05 via LINUX terminal (w/o Odin)

How might one apply the DJ05 update without using Odin v3?
Clearly the ROM and Kernel can be updated through CWM, but all searchable info seems to indicate that the modem file can only be altered via Odin on M$ Windoze. What is the methodology behind applying this kind of change using only tools available on a Linux platform?
Can I just overwrite a file on the Fascinate via adb?
cheers
I have only ever heard of modem.bin being flashed via Odin. I could be wrong, but I think it occupies its own partition, hence the need to actually flash rather than copy an individual file.
You can use redbend_ua to flash without Odin, but I recall (perhaps incorrectly) reading in IRC that redbend doesn't work for modem flashes in practice, at least not yet.
Hopefully someone can give more authoritative info, but I think you are stuck with Odin for good reasons. Just be nice to one of your friends with a PC. Don't have any? Shame! Windows users need love too ya know.
Swyped w/ XDA App. When in doubt, mumble.
Google search keyword: heimdall
Sent from my SCH-I500 using XDA App
Heimdall:
http://forum.xda-developers.com/showthread.php?t=755265
Awesome. That's a good question, why don't we just speak in terms of Heimdall in general... and use that instead? Strangely more soothing to say anyway, like "goos fraba"
You might find post 3 here useful as well.
That thread Soba49 posted is about 60 pages now, but reading through it all will give you a lot of good info on how it works. About page 56 or 57, you will see some specific questions I posed regarding flashing DJ05 modem.bin onto the Fascinate. It's almost too simple to use, so best to understand it as this is also the tool that will be saving your arse if you 'almost' brick your phone.
Heimdall actually emulates Odin in some areas & Kies in others and aims to eventually do more than either of those tools, w/o all the buggy Samsung coding. I believe the modem.bin is flashed using Kies methodology, FWIW.
So, I've been searching all over this forum and through the 60 pages of the Heimdall thread, but can't find an answer to this simple question - how do I just flash DJ05 onto my fascinate from OSX 10.6? When I try to connect in download mode and turn on Heimdall frontend, I just get "no compatible device connected" Do I need to flash bootloaders too or some other complicated stuff? Or am I just missing something easy?
SupraLance - What happened when you commanded: "heimdall flash --verbose --modem modem.bin"?
That command flashed the new modem for me. I am running DJ05 now and my phone has never been violated by a Windows device, lol.
I just re-read a bit of that thread regarding OSX, and it seems that Samsung released these phones with a crappy secondary boot loader. It will communicate with Linux and Windows, but not OSX. The only way around this is to flash a fixed boot loader through Linux or Windows, then you can use OSX from there out. Big problem is the only fixed boot loader verified to work with Heimdall & OSX is for the International Galaxy S. You need one specific for the Fascinate.
So this leaves American OSX users hoping that Samsung fixed this in the 2.2 Froyo code they have released. Heimdall & Odin cannot be made to work on OSX without it and boot loaders are not something you want to experiment with. Messing with the boot loader = quickest way to truly brick your phone.
If I was at your computer trying to do this, I would set up a dual-boot on your Mac with Ubuntu (completely free and similar to OSX interface) and do it through Ubuntu.
Heimdall Success!
fragmented post
Code
fragmented post
Notes on Code.
fragmented post
Next step.
fragmented post
fragmented post
Heimdall Success!
Installed Heimdall 1.1.0 for Debian.
http://www.glassechidna.com.au/products/heimdall/
Flashed modem using:
Code:
heimdall flash --verbose --modem modem.bin
Making sure that SF is in DL mode and the current directory contains "modem.bin" file.
Then flash ROM (and Kernel) via CWM.
Additional possibly helpful info here:
http://mobiletech.knguyentu.com/2010/12/fascinate-rom-dj05-and-beyond-all-you.html
Cheers

Heimdall or Odin

I see in the sticky that heimdall is recommend but all everyone talks about is odin does anyone really use heimdall and is there any difference.....noob here on flashing so I'm gathering all the info I can as to avoid bricking.
Sent from my SGH-T959 using XDA App
They both do the same thing, Odin was the first on the market been around and most ppl (like me) started out with Odin. Heimdall also has a Linux and Apple version, so for those people who have problems with Odin or use other platforms, it is a good Alternative. I am the one who posted the Heimdall thread, that said I still use Odin but my friends who are mac junkies needed help, so I started using this to help them. My recommendation is to get familiar with both for this reason
The more systems you work with, it will improve your understanding the tools, both in logic and approach.
Hope that helped...........
Thanks I appreciate it I'm going to go with odin since there are tutorials using it
Sent from my SGH-T959 using XDA App
Heimdall seems to work faster and more accurate for me...using the same computer.
Sent from my SGH-T959 using XDA App
___bump___
Spokenblurb said:
I see in the sticky that heimdall is recommend but all everyone talks about is odin does anyone really use heimdall and is there any difference.....noob here on flashing so I'm gathering all the info I can as to avoid bricking.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I'm the developer of Heimdall but I'll try give some non-bias pros for both options.
Odin
Uses the official Samsung driver (no need to manually install a driver).
More tutorials.
Firmware tends to be distributed in a format (3 archives) more suited towards Odin.
Better device compatibility due to Samsung's knowledge about the PIT file. This means you can flash all files described in the PIT file.
Note: When I finally get some free time to finish off Heimdall 1.2 it will include substantially improved PIT file awareness and add support for all files/partitions in the PIT file.
Heimdall
Cross-platform (Windows, Linux and OS X)
Flashes substantially faster (no 15ms communication delay like Odin).
More reliable (less failed flashes).
Can easily flash just one or any combination of file.
UI or command line options depending on personal preference.
Command line allows one step scripts to be written more easily.
Open source.
Developer support.
On another note Odin is, as far as we can tell, leaked Samsung software. Samsung haven't (to my knowledge) brought any legal action upon anyone using it, however there is always the issue of copyright infringement.
Heimdall is licensed under the MIT open-source license, which essentially means you're free to use and redistribute the software however you please, as long as you don't attempt to claim that you created it.
Thanks for this thread, I'm also a noob trying to not brik things up.
So, when I read the posts that describe how to do something in Odin, can I use the same files to do the same thing in Heimdall? I use a Mac and I believe I could set up a VM with Windows to run Odin, but I really don't want to. Besides, I don't have Windows.
Thanks.
Odin
Use Thor. Or Odin is fine too.

Linux tools for the S3?

I have no objections to booting into my Windows partition if it'll help prevent bricks, but I'd like to have the flexibility of flashing or recovering from either OS.
I know programs like Heimdall are around, but are they as fault tolerant or informative as their Windows equivalents?
LLStarks said:
I have no objections to booting into my Windows partition if it'll help prevent bricks, but I'd like to have the flexibility of flashing or recovering from either OS.
I know programs like Heimdall are around, but are they as fault tolerant or informative as their Windows equivalents?
Click to expand...
Click to collapse
AFAIK, Heimdall isn't working 100% yet. I tested 1.3.1 and 1.3.2 for myself, and both versions failed. The developer is working on it, though
You really only need to use Odin or Heimdall ONCE, though, and from there on you can just use CWM to wipe and flash new ROMs (which won't trip the flash counter). With my old Captivate, I didn't actually need to use odin/heimdall at all, because I was able to flash a rooted update.zip directly from Samsung's own recovery (before it got replaced with ClockworkMod).
I'm not going to let Windoze touch my ATT SGS3 on principle.

Not sure which rooting method to use please help

Being a newbie I cannot post in the developer forums until I have at least 10 posts. So I am asking here for now.
I am very new to rooting on an android and very good with JailBreaking on an Iphone. I am currently experimenting a lot work with Micro controller hardware and software such as Adruino hardware etc. Also doing a lot of jtag experiments to understand more about it fully.
Good with linux customizing kernels etc and running OSX on all my PC's
This is sort of the thing I would like to do to my Andorid. Not to play games on but to root it to use it for development software and connecting micro controllers to it either by dongle, bluetooth or even WIFI!!
Enough on that.
So my Dilemma is which method do I use below or should say which is the overall best and safest one for now.
Also will the TriangleAway work if I use it on a JB or ICS custom ROM/kernel?
I do have ODIN Mobile Pro but not installed onto the tablet yet and I don't think I put a link up using that method. If you know of one please let me know using that method or should I stay away from that one?
http://forum.xda-developers.com/showthread.php?t=1746794
http://forum.xda-developers.com/showthread.php?t=1722745
http://forum.xda-developers.com/showthread.php?t=1791193
http://forum.xda-developers.com/showthread.php?t=1722304
http://forum.xda-developers.com/showthread.php?t=1657056&highlight=4+04+triangle
http://forum.xda-developers.com/showthread.php?t=1788625
The Last link is for rooting only I believe?
For now I will do this on a Samsung Tab 2 7 inch. Its has ICS stock 4.04 with the latest update since today!!
I am starting to grasp a few things like Mobile ODIN and Desktop versions and that the stock Samsung ODIN which when I first saw thought my previously owned unit was rooted already.
I am assuming I will need CWM6 etc. A lot of acronyms to go through on these tutorials one would think just a page on them alone should be viewed before moving onto the hard core stuff.
Its too bad there is not a real basic thread on all these steps that one can view and choose from as well as all the acronyms used on these threads.
Thanks!!
If you have a Samsung Galaxy TAB 2.0 - 7" - then i'd say go with this :
http://forum.xda-developers.com/showthread.php?t=1722745
Works fine - And far as you wanting to experiment with android etc - explore on!
As far as i can think, the reason there is not one simple thread to explain rooting / flashing roms etc is because every phone / tablet etc has is different and as such has to be rooted / customized according to its hardware / software specs etc -
http://forum.xda-developers.com/showthread.php?t=1880010
Thanks,
Those were the two I was concentrating on.
@ketut,
Where do you run those scripts? If the android is not rooted yet I have to guess your running them from a Linux box or laptop? I have to read your thread more carefully.
I am a bit confused on the prepping scenarios.
1. Download and then install Heimdall package for OSX
2. Type in console:
Code:
# heimdall flash --recovery recovery.img --cache cache.img
recovery.img and cache.img extracted from P31xx_CWM*.tar.md5.zip or P31xx_SAMSUNG*.tar.md5.zip depend on your device and your choice to install CWM or Samsung recovery.

[GUIDE][Troubleshoot a failed Odin flash]

This guide is provided for information only. I will not be held responsible if you cause any damage, software or hardware, to your phone by following the guide. You are choosing to follow this guide, and as such, you choose to accept any responsibility for any mishap that may occur.
WARNING: Do not follow this guide if you think (or even suspect) that your USB port may be faulty in any way (ie, slow charging, loose connection among other faults). If your USB port is faulty, it must be fixed before flashing, or you are in danger of hard-bricking your phone. If the connection to the computer fails even for a moment, at best the flash will fail, and at worst the phone will need a new motherboard. Either send it to a service centre, or here is a good place to start if you want to DIY.
WARNING #2: If at all possible, make sure you have a backup of your efs folder (using Hellcat's app, "kTool" from playstore). Efs is the folder which contains your imei. No imei =no signal. Flashing a ROM may corrupt the efs folder, in which case the backup will be invaluable. If you do not have a working backup of your efs folder, I am not responsible if you choose to follow this guide and your efs becomes corrupt.
Symptoms
This guide is for people who find themselves in the situation where:
The phone currently will not boot.
The phone can only enter download mode (If it can’t do that, see the section below.)
If, for whatever reason, an Odin flash fails.
It assumes you know the basics of Odin flashing. If not, see here.
No download mode?
If your phone won’t enter download mode, you can try three things:
A USB jig. Don’t pin your hopes on this, they rarely succeed in this scenario.
‘Jump starting’ – You might need someone else to give you a hand for this. Take the battery out of your phone and wait 30 seconds. Now, press the button combination to enter download mode, and with this combination still depressed, get someone to put the battery back in. Hopefully this will jolt your phone into download mode.
Take out the phone battery, and re-insert it, but don’t turn the phone on. Now, plug in the charger while holding the volume down button. Keep holding volume down till you enter download mode.
If your phone won’t enter download mode, and will do nothing but get hot when you attempt to do anything to it (charge it, turn it on), then your motherboard is in need of replacement.
Your options
I’ve seen a lot of people, when their Odin flash fails, either:
Give up. Not a good option.
Flash a .pit file. That should be used as an absolute last resort. There’s a lot to try before getting to that stage! If a flash of a .pit file fails in Odin, your phone is well and truly unrecoverable, and you will need a motherboard (MB) replacement.
Send their phone to a service centre. That costs money (& you’re without a phone for a week or so).
Read on and hopefully you will be able to recover your phone without spending anything.
What to do
Keep flashing via Odin. You don't really have a choice. As for the files to flash: It’s worth trying to flash a range of stock ROM’s and custom kernels. I recommend downloading a stock firmware from Samfirmware for your device; either ICS 4.0.3 or JB 4.1.2. Stay away from 4.0.4 (research emmc brickbug if you’re interested.) See here for the stock ROM’s. Alternatively you can also download firmwares from xda. Make sure you’re using the correct firmware for your device variant and region (i9100, i9100g, i9100p etc).
As for custom kernels: If you manage to flash a custom kernel onto your phone, that gives you recovery (usually CWM for i9100), from which you can either restore a nandroid backup, or flash a custom ROM. ONLY for i9100: See here for Siyah kernel. If you were previously on ICS, flash ‘siyahkernel s2-v5.01’ from that link. If you were previously on JB stock, flash the ‘S2-v6.0beta5’. You want the .tar extension in both cases. If you were on a 4.2.2 or 4.3/4.3.1 ROM, see here. You want the file called "Kernel_Dorimanx-V9.43-[12-16]-[24-10]-TAR-FOR-ODIN.tar". None of the other files downloadable from that mirror are Odin-flashable. All files linked are for international I9100. Even still:
Your best bet is to continue to attempt to flash Stock ROMs for your model variant and region.
Another option for i9100
If you have an i9100, probably the best option to flash is to flash 4.1.2 JellyBean leak. Huge thanks to It_ler for providing the file after it was lost during the shutdown of hosting site hotfile.com and re-hosting on his dev-host, and for keithross39 for re-hosting the file on his storage. Download it here: (Android File Host link) or here: Mega link. This is a 3-part firmware. It will wipe your device as it flashes, and in many cases this extra wipe while flashing contributes to a successful flash. To set this file up in Odin (as it is 3 parts): PDA = CODE_I9100XXLSJ.tar, PHONE = MODEM_I9100XXLS6.tar, and CSC = CSC_HOME_OXX_I9100OXXLS1.tar. As usual, do not tick 'repartition'.
Now that you have chosen a file to flash, continue on.
If Odin won't recognise the phone ...if it does, continue to 'Preliminary Steps'
Firstly, keep trying. Many users will find that Odin will recognise the phone in download mode eventually, but this will take perseverance. Note that if you do get Odin to recognise your phone in download mode, attempt to flash a stock ROM then. Don't unplug it thinking 'you'll try again later'.
Things to try if the phone isn't recognised by Odin:
Open Odin without the phone plugged in. Enter Download mode without the phone plugged in. Now, plug the phone in and wait a few seconds.
Didn't work? Try again in a different USB port. Still didn't work? Try all the USB ports, and then a different computer. If that doesn't work:
Uninstall the USB drivers using Revo Uninstaller. This program can remove the registry edits from the drivers, giving you a completely clean install of the drivers. Reinstall the USB drivers: Latest version here, or a "tried 'n true version here". Both are worth trying. If you are using Windows 8, I strongly recommend you try Windows 7/XP. These drivers don’t usually work with Windows 8. (See here if you’re on Windows 8.) Otherwise, use the linked file to the Samsung USB drivers.
If you're still not having any luck, then follow these steps: (Credits to 4-2ndtwin)
1. Turn off both the computer and phone. Fully shut down.
2. Disconnect phone from computer: the USB cable from both the computer and phone.
3. Boot up the computer. Log in and let it settle.
4. Start up Odin and let it settle.
5. Put phone in download mode.
6. Connect phone to a USB port.
If that doesn't work, keep repeating those steps, with different USB ports on your PC/laptop. Change the USB cable you're using, multiple times (preferably use the cable that came with the phone). If all that doesn't work, start again at 'If Odin won't recognise the phone' on a different computer. Keep persevering
Now assuming you can get your phone into download mode, and is recognised by Odin:
Preliminary steps
Odin failing a flash usually isn’t a failure of the software itself. It’s usually to do with the way the flash is set up. Before we get on to the troubleshooting steps: you must always- i.e. every flash:
Run Odin as an administrator in Windows (only for Windows 7. This doesn’t apply for Windows XP). Yes, Odin is Windows only. If you use Linux/a Mac, you’ll need to use someone else’s Windows computer.
Ensure Kies is installed on your computer but you must kill all Kies running services in the Windows task manager. Most people have 4 running continuously. I personally only have 2, so don’t stress if you can’t find 4 to kill.
Make sure you're not using a USB hub of any description.
Remove your phone case, if you're using one. I've seen cases which make it not possible for the cable to correctly sit in the USB port.
If you haven’t done those steps on your previous Odin flash, it’s worth flashing again making sure you do those three things. Still didn’t work?
Troubleshooting steps
Things to do:
Change the USB cable you’re using. Preferably, use the original cable that came with the phone. If you’re already using the original cable, change to another, genuine, S2 cable. Try at least 3 different cables.
Remove your phone case, if you're using one. I've seen cases which make it not possible for the cable to correctly sit in the USB port.
Try different USB ports on your computer. You have to be using a mainboard (powered) port. Try as many of those as you have on your computer.
Use different versions of Odin: Attached at the bottom of this post is a zip file containing versions 1.3, 1.83, 1.85, 3.04 3.06, and 3.07. Try them all, but particularly 1.3, 1.85, 3.04 and 3.07. Make sure to extract the Odin files before using them.
Reinstall the Samsung USB drivers. If you are using Windows 8, I strongly recommend you try Windows 7/XP. These drivers don’t usually work with Windows 8. (See here if you’re on Windows 8.) Otherwise, use the linked file.
Turn off all antivirus/antimalware/antispyware/firewalls. I advise downloading all files you need before doing this step so you’re not without antivirus whilst downloading files. I’m not responsible if you do manage to get a computer virus during this time.
Check the rom/kernel you download, making sure it’s not a corrupted file. The best way to do this is to check the MD5 sum using md5summer. If you don’t have the MD5 sum, then you can use WinRar, 7Zip, or IZarc to test the file. If any tests (MD5 or the 7Zip test) fail, then you need to re-download the file. Test the new file before using it.
Run Windows update on the computer you’re using.
What now?
Ok, so if you’ve got to the bottom of the list, but you’re still having failed flashes:
Use a different computer. Now, run through the list again. Yes, the whole list. Try everything all over again on the new computer. Didn’t work? Try again on one more computer. Keep persevering, the feeling you’ll get when your S2 is back to life will be worth it
Last Resort
What if… Ok, so you genuinely can’t get anything to work. This really is a last resort. It’ll be either up to you to choose whether:
You research the flashing of .pit files. If you are going down that route and have an I9100, two good places to start are here and here.Note that your phone will be stuffed if it fails. Full stop. Motherboard replacement. Ask yourself “if Odin won’t flash a ROM without failing, why will it flash a .pit successfully?” Only click that link if you have tried the steps over and over and over again as stated.
You take your phone to a service centre.
Many thanks to keithross39 for proofreading & editing this guide, and re-hosting the 3-part firmware.
Also many thanks for It_ler for providing and hosting the 3-part firmware, after it was lost during the shutdown of hosting site hotfile.com.
Credits:
MistahBungle, on whose posts these troubleshooting steps are based.
keithross39, for his guide on replacing the USB port.
Intratech, for his guides on the basics of Odin flashing & stock ROM collection.
4-2ndtwin, for his troubleshooting steps if Odin won't recognise the phone.
SamHaLeKe, for the updated Samsung USB drivers.
ApriliaM3, for the USB driver hosting.
daerragh, for the Windows 8 drivers.
king_below_my_lord, for his guide on I9100 .pit file flashing.
metalgearhathaway, for his thread containing .pit files
Nice hopper, let's make this a sticky
Sent from the little guy
This is going to be VERY useful.....
I agree, it needs to be stickyed....
I can see myself referring a lot of folks to this thread.....
Excellent work mate......
Edit.....mods, get the glue out please.....lol
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
keithross39 said:
I agree, it needs to be stickyed....
Edit.....mods, get the glue out please.....lol
Click to expand...
Click to collapse
I've PM'd a mod, so hopefully it can be stickyed
I thought thanks/credit is supposed to be given to the originators of the info.
Maybe a mod could look into that as I dont see any of that here.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
theunderling said:
I thought thanks/credit is supposed to be given to the originators of the info.
Maybe a mod could look into that as I dont see any of that here.
Click to expand...
Click to collapse
All of the information in this guide is freely available on the internet, a lot of it XDA. If you are referring to the steps MistahBungle wrote, he has specifically stated there is no need to credit him for those steps as the info is freely available on the internet. If it makes you feel better, I can credit him anyway. I used over 20 XDA threads as well as info from outside XDA to write this guide. Would you like me to credit every single one of them?
Edit: Have credited MistahBungle in OP. I hope that puts your mind at rest.
It wasnt only mistahbungle I was thinking of,eg the 1st link is from Intratech.
I am not the one making up guides so I dont need to know what the correct protocol is regarging credits,this is up to a mod to decide.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
OP edited, new section with troubleshooting steps if Odin won't recognise the phone. Also, many many credits are added, for all linked files/guides.
Good job Hopper, everyday I find that many people here are doing a great job of answering people in trouble, the best are Gastonw(watch out this guy answers anything) , Mistahbungle, Keith, The Underling, you, I hope these guy's will be around for some more time(before the device becomes obsolete) I find myself quite unnecessary, as all the above mentioned guys are tackling all possible problems with great success. I am happy to be a part of such a great forum.
Sent from my GT-I9100 using xda app-developers app
But custom, I don't do custom.
Sent from the little guy
OP updated with a warning not to flash anything if USB port is faulty in any way. Thanks to Keithross39 for the suggestion to add this.
Sponsor it with a "don't flash without backing up EFS" banner
Sent from the little guy
gastonw said:
Sponsor it with a "don't flash without backing up EFS" banner
Sent from the little guy
Click to expand...
Click to collapse
I'm not sure many people following this are in a position to back up efs? I've started at the point that they can only enter download mode.
You'd be surprised....
Sent from...this is not even my S2
gastonw said:
You'd be surprised....
Sent from...this is not even my S2
Click to expand...
Click to collapse
OP updated. Thanks for the suggestion
Whow whow, that was a joke.
The whole banner thing...damn, the meme thread &%#@*+ me up.
Edit: nevermind, fitted nicely
Sent from the little guy
This is rapidly turning into one helluva guide......
Pretty soon, everyone's going to be able to find out everything about their phone.....right here.... lol
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
The DeLorean is coming too.
Sent from the little guy
keithross39 said:
This is rapidly turning into one helluva guide......
Pretty soon, everyone's going to be able to find out everything about their phone.....right here.... lol
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
Just hoping it can still be stickyed...
Sent from my GT-P7510 using Tapatalk 4 Beta
It will.
Sent from...this is not even my S2

Categories

Resources