Skip to main content

How I unbricked my Samsung Galaxy S I9000 and installed a new firmware with Odin

The Samsung Galaxy S I9000 is one of the best smartphones and a real iPhone killer. Unfortunately the firmware update is done through a Samsung program called Kies wich is really bad.

How Kies bricked my Galaxy S during firmware update

I would like to report how I recovered from a really bad flash (actually a brick) caused during firmware update using Samsung Kies on the Galaxy S I9000. First of all, I was not prepared that official Samsung firmware flashing could cause me such problems and could brick a smartphone at the end of 2010! But this is what happened to me! Really bad what Samsung gives to its customers. BTW, I would describe myself as a computer pro, programmer and hardware developer, so I am not a complete newbie regarding firmware updates ;)

I had bought my Galaxy S I9000 in Germany and its official firmware stated:
pda: i9000xxjm1, phone: i9000xxjm1, csc: i9000xajm1, pccode: gt-i9000hkddbt

I had installed multiple progs on the phone but had NOT modded it in any way. When Andoid 2.2 (Froyo) came out I decided to wait for the upgrade to become available through Kies (rinning it under Win XP) because I wanted to flash it the official way. I thought that this would be more secure (it is not as you will see later). I had not experienced any serious problems with Kies until then, although I had not worked a lot with it. So when the XXJPO Update arrived through Kies, before beginning with flashing I restarted my phone (normal mode, not recovery mode) and plugged in the phone. Kies recognized the phone and I started flashing the firmware. The download screen with the digging android appeared on the I9000. If I remember correctly at this point Kies or the phone itself disconnected for short and maybe some drivers tried to reload but I am not sure about this.

When I looked at the phone at some point, the digging Android was NOT there anymore - instead the whole screen was green (or yellow). Kies did not report any error but the firmware update progress bar did not move on. After some time I realized that the phone had crashed. So I disconnected the phone and restarted it. Now the only thing that appeared on the screen was a phone icon connected to a PC icon with an exclamation mark icon inbetween - I call this the screen of death ;-) The phone could not be recognized anymore by my PC. Kies offered me some kind of firmware recovery option (which will disappear if you try to uninstall and reinstall Kies) but Win XP and Kies just did not see the phone anymore so I could not recover anything.

Trying to get the Samsung Galaxy S into recovery mode by pressing Volume Down + Home + Power (or any other key combos) did not work, no matter how many times I tried. Most of the forums reported that the phone is bricked when you can't get into download mode and the only way to get it back to life is to give it back to Samsung for repair. At this point I want to emphasize that the recovery mode key combination must have worked on that phone previously, because my brother has the same phone (bought them at the same time) and his download mode combination works!

How to unbrick the Galaxy S I9000 - Download mode

So it turned out that the phone has been bricked - thank you Samsung! I decided to call Samsung but then I suddenly found an amazing thread and a video stating that with a modified micro USB plug and a resistor one can bring the phone back to life. I was a bit sceptical first BUT IT IS TRUE, IT REALLY WORKS! So a colleague of mine prepared the USB jig and it really brought the phone right into download mode when I inserted the battery. The phone had been unbricked! Now Windows recognized the phone again but Kies was still not able to connect (I had not expected anything else).

How I installed a new firmware on the Galaxy S I9000 using Odin

Now I finally decided to try Odin (the unofficial but much better alternative to Kies) and flash the latest official Samsung firmware I9000XFJP7 (many thanks to Richthofen) that I downloaded from So once again I used the USB jig to get into download mode and flashed the I9000XFJP7 firmware with the Germany only CSC CSC_I9000DBTJP3 as described here:
After the first repartitioning-only step with Odin where Richthofen says "Plug out your phone, remove the battery, put it back in and put phone to download mode again." the phone seemed completely dead. It was another shock for me. Nothing happened, even the phone + PC + exclamation mark icons did not appear anymore - the screen remained black and pressing power, home, vol down did not do anything. But then I put in the "magic" USB jig again and the phone started in download mode again. So I continued flashing the firmware as described in Richthofen's thread. Finally the phone restarted and the new Android 2.2 Froyo booted.

The Galaxy S - Back to life :)

The biggest surprise for me was that all my 3rd party programs were still there. Only some of Samsungs built-in progs seemed to have been updated and had lost their data. Also some widgets on the front-screen were missing but these can be reinserted on the I9000 desktop.

On the one hand I hope that Samsung will get a lot of negative feedback from its customers in order to finally rewrite and improve its bad software. On the other hand I hope that this report will help other people to solve the firmware upgrade problems and show them how to unbrick their Samsung smartphones (the Samsung hardware is really nice). I also encourage people to support the firmware contributors at XDA Developers (



  1. USB dongle for those who do not have the tools or time build USB dongle jig.
    Or just what one they know will work and not mess up the phone more.
    Buy it here
    How to use USB dongle Jig.

  2. I unbricked my phone thanks to you, but its now Froyo 2.2 (Europe Version), is there a way i can upgrade mine to 2.3.4 (Asian Version), can give me the required files too. thanks again and help me pls.

  3. Thanks for your idea. Will try it. Right now my phone is bricked and given to Samsung's service center. See what they say? But this topic will surely help many needed people.


Post a Comment

Popular posts from this blog

SOLVED: Making Wake-on-Lan (WOL) work in Windows 10 / 8.x

THIS FIX ALSO APPLIES TO WINDOWS 10, IT IS EVEN MORE IMPORTANT,  BECAUSE WINDOWS 10 TURNS "FAST STARTUP" (read below) BACK ON AFTER UPDATES (yes, Microsoft does not stop creating nonsense features / bugs).
HKLM\System\CurrentControlSet\Control\Session Manager\Power\HiberbootEnabled
and set its value to 0 !

I had very serious problems getting Wake-On-Lan (WOL) to work on my new Dell Optiplex 9020 MT (MiniTower) on Windows 8.1 Pro. I finally got this to work and would like to share my experience here.

Note: At the time of this writing the current Dell BIOS for Optiplex 9020 MT was A05.
UPDATE: The same behavior is also observed with DELL BIOS A07. Maybe Dell needs to comply with some power saving requirements and therefore enables Deep Sleep instead of Wake-On-LAN? Whatever the reason is, it is extremely annoying that this is the default and it is not clearly docu…

Changing the Reserved IP Address in a Static DHCP Reservation in Windows Server

Static IPs preferred DHCP is a good thing if it works - set and forget. But what happens if the DHCP server is down for some reason? Exactly - the whole network stops working. Another problem of DHCP are those random IPs a client gets each time. This is very bad for printers that use DHCP. Therefore I prefer static IPs over dynamic.
Windows Server 2012 R2 Essentials: You cannot stop Windows LAN Configuration Service anymore
Unfortunately, there is some strange behavior on Server 2012 R2 Essentials if you just enter static IPs on your Windows clients - your Windows OS will show exclamation marks on your network connection from time to time, etc. There is actually a Windows Server LAN Configuration service which keeps overwriting your manual settings and the bad thing is that you cannot stop that service in Server 2012 R2 any more for some reason...So, instead, I decided to use DHCP on the server and add an Alternative IP Configuration with all static data as a fallback if my serv…

Windows Server 2012 R2 ESSENTIALS: Virtualization How-To, Physical Hyper-V Host and Virtual Server (VM)

This is intended to be a guide how to install Microsoft Windows Server 2012 R2 ESSENTIALS as a virtual server, i.e. inside a virtual machine (VM). This VM will run on a physical Hyper-V host which will be again Windows Server 2012 R2 ESSENTIALS itself. This type of installation is allowed by Microsoft but they have not included a tool to simplify the process. In order to achieve our aim, we need to modify the original ISO by removing the Essentials Role and Essentials Setup using Microsoft's own tools.

DISCLAIMER: To my best knowledge everything described here complies with the MS license terms. It worked for me but does not mean that it will work for you as is. So make sure that you have understood everything and check if each step applies to your system. There is no liability for damages.
Physical Hyper-V Host vs Virtual Server (Guest VM) Windows Server 2012 R2 Essentials is a very interesting operating system for small businesses. What many people don't know: Microsoft now …