Database Users

XDA dead after RUU and RSU update

After upgrading a O2 (dutch) supplied RUU and RSU files my XDA is now totally dead. That is, it cannot recognise the craddle and connection, it only shows the O2 bubbles background screen. Hard and soft boot makes no difference.
Before the upgrade i did a total backup of the XDA, so I have a approx. 15 MB file BACKUP.STG, can I use that for something now ?
I have a SD card and a writer. I have downloaded the tools from this site.
When using the wallaby bootloader 5.14 I get a GSM ERROR, but I can still get to the place where I can write the rom to the SD card.
I can use the wallaby to get stuff of the XDA, so much is clear. I can load a new OS from the SD card and I can use the OSI tool to put something on the SD card.
My problem is HOW DO I GET SOMETHING USEFULL ON THE SD CARD.
Is there somewhere a default ROM thingy or can I create something myself?
I am new to this XDA stuff, but computer litterate so I do understand words with more than 5 letters, but if you want to answer to this cry for help then please write as if I am a IQ-17 XDA baby.
Thanks
Jan

http://www.xda-developers.com/forum/viewtopic.php?t=2489&sid=8c1aea80a41318c77a50013b562fe4df

Jan said:
After upgrading a O2 (dutch) supplied RUU and RSU files my XDA is now totally dead. That is, it cannot recognise the craddle and connection, it only shows the O2 bubbles background screen. Hard and soft boot makes no difference.
Before the upgrade i did a total backup of the XDA, so I have a approx. 15 MB file BACKUP.STG, can I use that for something now ?
I have a SD card and a writer. I have downloaded the tools from this site.
When using the wallaby bootloader 5.14 I get a GSM ERROR, but I can still get to the place where I can write the rom to the SD card.
I can use the wallaby to get stuff of the XDA, so much is clear. I can load a new OS from the SD card and I can use the OSI tool to put something on the SD card.
My problem is HOW DO I GET SOMETHING USEFULL ON THE SD CARD.
Is there somewhere a default ROM thingy or can I create something myself?
I am new to this XDA stuff, but computer litterate so I do understand words with more than 5 letters, but if you want to answer to this cry for help then please write as if I am a IQ-17 XDA baby.
Thanks
Jan
Click to expand...
Click to collapse
Hello Jan
please find these two links i guess they are usefull to resolve your problem and the posts are by chosl and wwb95
First link click here
Second link click here
good luck and best regards
Othman :roll:

Fixed!
Here is how I did it.
First how I made the mistake:
From the Dutch O2 site (now Telfort site) I downloaded 2 zip files. They contained 2 .exe files
·Radio_unit_upgrade_v31703.exe (xda_ruu.zip, containing program A)
·RSUv1.15(gprs_421_eng_o2).exe (xda_rsu-zip, containing program B)
I followed the instructions and the first file (Radio_unit….) was installed without problems, but the second one hung up the XDA. It was asking for the code for the SIM card at the time of error but more windows were overlaid and when I tried to remove these I must have done something that I was supposed NOT to do. The end result was that the XDA was dead as doornail. (see further description in the above link)
I searched the Internet for resources on XDA and came to this nice place. I searched using different criteria, but did not find something very useful, then I decided to create an issue and within 2 hours I had a response (Thanks FROG). It was the link you have above and here I found the solution. I did try to follow the exact path described but as usual the case is, my situation was not exact the same, but I still recommend reading THE FULL THREAD and my description before doing anything. Be sure you understand what you are doing, I think it is quite easy to make things worse, but if you are careful you should come out with a working XDA. I did!.
BEFORE YOU START DOING ANY THING, TAKE A BACKUP OF THE NON FUNCTIONING XDA. (look at this site for description of the wallaby-bootloader)
If everything fails you can at least restore the XDA to the initial error state, either if you need to perform another try or if you are “throwing the towel into the ring” and send the XDA to official repair.
Here is what I have learned.
To me it looks like the “Radio_unit….” File is the upgrade of the operating system, that’s why it is so big (15MB) and the “RSU….” Is an upgrade of the phone (which I have read somewhere here is using a separate CPU/thingy). To me it also looks like the “RSU….” File and thereby the phone part is somehow connected to the control of battery and recharging of the same, because one of the things I noticed was that the little yellow/green light that shows battery charging stopped working after the failed installation of the “RSU…” file, and during the whole recovery I had to struggle with having enough power on the XDA to perform the tasks at hand.
So a piece of advice, get the thing fixed while you still have some power on the XDA and if that fails use your AC charging cable connected directly to the XDA during the fixing of the problem. The fixing involves using the SD card as a boot mechanism and inserting and removing while having the power cable in is a bit tricky but manageable.
Power level on the XDA is obviously very important, one thing I have noticed is that it is impossible to switch the phone back on again if there is too little power on the XDA, to get it to switch on I will always have to connect the XDA to external AC power. As soon as it is on, I can disconnect and use the phone quite happily. So there is something fishy with the phone and battery power level.
I have later seen on another site that you are supposed to close the phone BEFORE installing the phone update. I did not do that, maybe that was the reason for the failure.
Here is what I did.
First step is to get the PC and XDA to synchronise again.
In my situation the XDA was so dead that no connection using the cradle was possible and then the only other way to get information into it was through the SD card.
First I downloaded the recovery.zip file from http://www.xda-developers.com/repair.zip.
It comes with a small explanation. Basically you place a file and a subdirectory containing another file on the SD card, and then by inserting the SD card in the XDA you can boot the XDA.
To get the XDA to a point where he will accept the SD card, you need to have a To-day screen showing, it will not be a working screen but at that stage the XDA should be able to locate the SD card and boot.
To get the To-day screen try soft-reset (the small pinhole on the left-hand bottom side of the XDA) and be patient, my XDA was very slow under the whole recovery operation and remember to give him power using the power cable not through the cradle.
You might try pressing the volume button, it did nor help in my situation, but I do not think it makes anything worse.
When you have the non functioning To-day screen insert your SD card (with the recovery files).
The XDA starts doing something, you see a progress bar, but it stops after 1% is done with a flash error. The trick here is NOT TO PRESS THE OK OR CLOSE THE ERROR MESSAGE WINDOW, just let it be as it is, showing the message.
Put the XDA in the cradle (and put the power cable back on the cradle too). What we are trying now is to get a working connection going with the PC. Here you have to be a bit creative, like taking the XDA out of the cradle and put it back in, maybe click somewhere outside the messagebox while it is in the cradle or when it is out of the cradle, but again DO NOT CLOSE THE ERROR MESSAGE WINDOW.
If you cannot get this to work, you can try to change the RSUpgrade.sa.cab on the SD card with the other one from the recovery.zip file (as suggested in the documentation coming with the recovery.zip) or by copying the file you were trying to install with the “RSU…” file. In my case it was placed under c:\program files\PROGRAMME B, or just search your whole PC for a file named “RSUpgrade.sa.ca”.
At this stage you should have had a successful syncronisation with your PC.
Every time you start your XDA it will try to finish the failed update and we do not want that to happened. As described elsewhere (see link above) there are several ways of doing this. What I did was renaming 2 files in the windows directory on the XDA.
You should now be able to view the content of the XDA from your PC (no magic in this, this is what you always have been able to do. You have a mobile device icon when opening “My Computer”) , open the windows directory and look for 2 files named RSUpgrade.exe and RSUpgrade.cp64.
Either delete or rename these 2. This will prevent the XDA from trying the upgrade again when you soft reset it.
A bit of ordinary info:
As in windows on your PC, you have a “startup” directory under the “windows” directory. In the startup dir. There is a link file to the RSUpgrade.exe file. This is how the XDA starts the upgrade every time you “boot” the XDA
Remove the SD card from the XDA and softreset it.
Put the XDA back in the cradle and hopefully you get a connection to your pc again.
Now run the installation of the “RSU…” file again, YES the one that failed the first time, we need that to be finished to get back to a working XDA. During the installation, a check on the power capacity of the XDA is done and if less than 70% loaded, the installation will stop.
If this happens, have patience while you recharge the XDA, at this point in time the yellow light should have come back on so now at least you can follow the power loading progress.
After this my PDA part worked but the phone would not switch on, I tried different things including a good whack with a big hammer…. After I had bought a new one (just kidding!), anyhow after a while I decided to try something totally different namely installing the much acclaimed XDA developers special edition ROM and after installing that I was asked if I wanted to open up my phone for access from other parties (or something like that) Boldly I answered YES and LOO AND BEHOLD, my phone was suddenly working (It is something with the SIM lock I think. But anyhow I can recommend the Special edition, if not for anything else that it makes the phone works, but it actually comes with a lot of nifty software. Recommended!
Now is the time to read the whole tread attached (if you have not already done that) and then, good luck.

Siemens SX-56 Dead Dead Dead!

ok...I'm really new to all this so please show a little patience towards me!
I was trying to load the XDA-developers-SER-v12 on my phone and just when it started with the progress bar moving at the top of the PPC screen, when it said "Do not Remove Device..." I accidently lifted the phone out of the cradle as dumb as I am...! After that I tried to hard start it by shoving a pin on the hole in the right side under the battery icon with the cross (hard-reset) and got the Bootloader 5.17 screen with the three colors and GSM (OK) there when I pressed the soft-reset and power buttons simultaneously.
But since I was the idiot and could not understand what was going on, as I was not in this forum nor even behind a computer, I reset it again and again a couple of more times. Now present situation; I have the same "Do not Remove..." screen everytime I do a hard or soft reset even if I keep the power on/off button pressed alongwith pressing the hot or cold boot buttons on the left and right corners respectively. In fact the screen has gotten badly distorted but the same "Do not Remove..." comes up in the totally distorted state on the screen and the Bootloader or the colors, nothing comes up anymore.
When I try to put the phone on the charger, the light goes orange just as if it is charging, in fact, after an hour or so, just as it normally would in the correct phone state, it turns green.
Is my phone toast or can I still do something about it?
Munz.

I'm no expert, but it seems to me that if there is a complication with the software when loading, one should try using the sd method of rom flashign. Cook or dl a rom, use XDA tools to load it to an SD, put the SD into the device, and then use the bootloader to load off of SD. Other than that, I know little to nothing.
Good luck!

Search in the forum after SD Card flashing for the Wallaby.
This would fix your device...
HTH
Stefan

Re: Dead SX-56
You guys are good and quick....but!!! As I mentioned, I can't even see the Bootloader even after a reset and power button combo...nothing comes up or happens...the screen just blinks and then goes blank...should I open it up and disconnect the battery or something...? Right now I am just seeing the screen saying "Do not Remove...." and that even in a totally distorted form....

Try pushing a pin in the hard reset, push once only, leave it overnight, I think that is good as removing battery as it disconnects the connection between battery and mainboard as fas as I know. Next morning push once with oin again, you never know your luck. Its weird that the bootloader should be affected however the good thing is that your gsm seems ok and the xda is charging.

XDA Dead!
Thanks for the reply...I have just pushed the pin and am leaving the XDA in that state for the whole day...hope it revives back...its presently just giving me a garbled screen and nothing else...even when I press the power and hard reset together, it comes back to the garbled screen and nothing else...I'll take your advice and not touch it after the above for the day and let you know what happens, if there is any other advice I would highly appreciate it...

Bootloader Malfunction
You mentioned that your bootloader seems to be screwed up. Download the full version of XDA tools WITH the bootloader and Programme A. Grab yourself a new ROM of your choosing, lumpistefan's kitchen, etc. Then use the XDA tools to write the bootloader and the rom to your SD card. After that hard booting the device with the SD card installed should ask you if you want to flash the device.
I noticed that if you have XDA tools without the bootloader file it will write the rom to your SD and you will NOT be able to get to the flash your device screen.
This is the only way to do it since your device will not boot to a rom. Upgrades from manufactures and roms prepared with Programme A all require MS Active Synch AND a good working connection.
If you have a SD card prepared with the ROM and the bootloader the right way, it should almost be foolproof from what I understand.
Hope this helps, I was in much the same situation

XDA Dead!
Yups! I tried to boot it from an SD Card, its not exactly an SD Card but an MMC Card (128MB). It still comes up to the same garbled screen which is more garbled than ever before! Does not ask me for anything; or even confirms anything...It does not do anything else besides the screen even after a soft reset/hard reset or a combo hard/soft power button reset.
I'm really totally stuck...Any ideas will be much appreciated!
Thanks.

Your XDA is completely dead; you screwed OS ROM and bootloader.
Forget SD or Details method, it won't work for you!

Re: Dead SX-56
Can you help me fix it please? What do I need to do?

Bootloader
The more experienced members of this forum can correct me on this, but I have been under the impression that the SD method of flashing does not require an intact OS ROM or bootloader on the device.
If you created the SD correctly, it should contain its own bootloader. Just putting it in the unit and then reseting it should come up with the screen to flash the device.
Did you create the SD card with XDAtools? Did you also have the bootloader file in the /bin directory when you did it?
If a properly created SD "flash" card cannot fix your problem, then you really might have no choice to but to get it professionally repaired where the remove the chips themselves and replace them.
I think you may even be in luck. www.pocketpctechs.com probably can do this and they are located in Fountain Valley, CA about 4 hours away from you. They can also put in bigger memory and batteries at the same time at a discount if you are getting it repaired

Re:
Thank you so much for the reply...I will try it once more; although, yes I have tried the same thing before and made the MMC Card through the XDATools, but never hurts to try again...I'll double check on the bootloader again too this time...
If you can, please send me the contact information for the people who fix the XDA's professionally as you mentioned in the USA somewhere near me preferably, I am in San Jose, CA...I'll try to contact them also...
Best Regards.

Contact Information
Their website is www.pocketpctechs.com.
You can find all the contact information right there. As far as I know fountain valley is about 4-5 hours away from San Jose.

Similar problem:
I have a XDA I here, which has a similar problem:
It boots with the welcome to T-Mobile screen, and
it shows at the bottom of the screen 4.01.16 after a while R4.06 and after a while G32S54. The machine locks-up and does not respond to anything except the touch screen. If i tap the screen, the backlight turns on, and a
rotating 'wait' icon appears. That's it. I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD.
I guess the former user has tried to reflash the unit, and had put the OS overwriting the bootloader, OTOH, the unit seems to run *some* code, since it responds to taps on the screen, by turning on the backlight.
Any guru have any clue on this one? I could not find anything in the forums, while the forums are VERY helpful in the past.
GreetingZ,
Richard

Bootloader
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up

Re: Bootloader
ed207_us said:
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
Click to expand...
Click to collapse
I also have a good working unit, and testing my SD card, created with XDARIT in this unit tells me i need to press power -> reset to be able to
flash the unit. if i do'nt hold the power button, the unit boots normally.
ed207_us said:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card.
Click to expand...
Click to collapse
It is there. 'press action to download ROM, or press record to exit'
ed207_us said:
<<
Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Click to expand...
Click to collapse
I cannot connect the unit to activesync.
ed207_us said:
<<
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
Click to expand...
Click to collapse
I don' know the contents of the SD, since i created it a long time ago, but i really would appreciate is if you can email me a image of yours. Hope you are right and i can use the bootloader on your card to start this unit.
email size is no problem upto 100Mb
ed207_us said:
<<
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up
Click to expand...
Click to collapse

<<ed207_us wrote:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. >>
<<<RichardRosenberger wrote:
It is there. 'press action to download ROM, or press record to exit' >>>
It is only there when you have the SD card in the device, otherwise you cannot find it by moving around through the different menus.
XDAArit is completely outdated. You need to get their new tool.
XDATools can be downloaded from the website here. The best thread that talks about the tool is:
http://forum.xda-developers.com/viewtopic.php?t=2189&highlight=xdatools
The exact link to get the tool and all the supporting files, including the bootloader is:
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
When you install this version of XDAtools you will find a directory called binaries. Under it there should be a file called "bootloader_v5_15.nb0"
Use the tool to create your SD card with a .nb1 file of your choice. After that it should only be a matter of powering on the device with the SD card inside the unit.

I have 2 XDAs. 1 good en 1 have problem with bootloader and rom.
I can't access Wallaby bootloader en the OS don't start.
I backup it from good XDA in the bootloader (ce+Boot) and i pushed my SD in the XDA where problems are..
He don't work. How can I fix my problem..
Please Help...

I am not aware of what the (ce+boot) actually creates on the SD card. If that is the exact ROM that you want, I would suggest downloading the full version of XDA tools, and I think you can use it to copy the ROM from the SD card to a .nb1 file on your computer. Then follow the instructions I have already posted to make the working SD card that will flash the XDA.
When it comes to the SD card, the only time I have ever been successfull is when creating it with XDAtools with a .nb1 file and the bootloader .nb0 file inside the binaries directory.
That's it. I have never been able to do it any other way. Programme A does not count since it requires an active and working OS and connection to the PC and most people that are in trouble don't have that.

Alpine R.I.P. Help please.

Alpine R.I.P.
Hello First of all to excuse the translation for the reason that my level of English is null and I must myself serve as tools like google to translate.
I have a problem and salary if some of you happens some solution to you since I no longer have but ideas. I have tried to change to the one language alpine (xdalli) and the result has been death.
The steps:
1: Copy original ROM (in English) with romupdate.
2: To pass copied ROM to the PC with ntrw.
3: Once copied to separate the ROM in three parts (header.nb1, ext.img and trailer.nb1) with split.
4: With the publisher hex workshop 4,2 to copy the head of the file header.nb1 removed from xdalli and to copy it in the file header.nb1 of 2020i_XDII_cambio_idioma_esp_by_ferdy (ROM in Spanish). Thus we would obtain that xdalli when loading the new ROM by SD in Spanish thought that this about English when really this in Spanish.
5: Once kept the file header.nb1 modified I have mounted rom.nb1 uniting the 3 parts with merge (before divided with split header.nb1, ext.img and trailer.nb1.) So it would be left header.nb1 modified, ext.img and trailer.nb1 are the original ones of xdalli.
6: To copy with ntrw in the SD.
7: To put xdalli bootloader with the SD inside and leaves message SD download press to power to flash.
8: Once fact this and finished updating reset.
9: And here it is where one dies.
These are the followed steps, now pda does not start neither in normal way nor in bootloader nor reset nor hard reset. KO
Some idea please, although is absurd since xda does not respond to anything.
Thanks and I wait for your ideas.
PS: of brave this the full cemetery. Who would command to touch xdalli to me. jejjejeje

Does it write anything on the screen? Or nothing at all? Try to remove and insert battery again.

get into bootloader, put in cradle n upgrade your ROM. g00d luck!
p/s:Enter to Bootloader Mode by press Power + Record Button and Soft Reset.

hi clustered,
The problem is that it does not enter nor bootloader. If it entered already she would be alive.
greetings

hi server
I cannot write nothing in the screen and believe that the reason went that when doing upload before described to him loaded bootloader to me.
I have tried to leave the battery that exhausted days and when I put it in the base ignites the red light of load nothing else but.
Also I have tried to put it in load without battery and to tighten the button of ignition and nothing.
I have put myself in contact with pof to comment the problem to him and it has commented to me that a serious solution jtag and to load to him to bootloader new but not it encounter for alpine.
If some solution is happened to you but it would be arranged to make it since this dead now.
Thanks and greetings

Newbz Rom/Cooking Questions & Answers

I'm a newb in the sense that I'm new to the whole Windows Mobile Devices. As my location of this thread, I have a T-Mobile Wing.
I'm a current web designer and I'm learning to program/code. Especially for mobile devices first. So I am computer literate just a newb using roms, windows mobile in general. I believe I can follow on very easily.
I will edit this post to add the answers and explain them in more details, etc. as I learn them for future cookers/newbies/etc.
I have searched around the forums, learned a lot but still have questions hopefully some pro cookers could answer and maybe use this as a ref for all beginner newbs. I have the link to the wing/herald xda wiki/atlas, etc.
BUT STILL....​
I'm on Windows Vista 64 bit. Maybe this is my problems? I take that into possibility. Within a week I'll have XP back on this computer as well.
[1]
I understand if your SPL/IPL is above 4.0+ you can hardspl your device. (DO NOT ATTEMPT TO HARDSPL YOUR DEVICE IF IT IS UNDER 4.0! IT WILL BRICK IT!)
I aslo heard of a uspl method where it hardspls your deivce JUST FOR THE NEW ROM YOU"RE INSTALLING.
I read that hardspl will hardspl your device forever but since then it's now reversable correct? Just curious about this, not a big deal either way.
NEWBS IF YOU WANT TO CHECK YOUR IPL/SPL VERSIONS : take your stylus out and soft reset your device by pushing your stylus into the small hole just under the volume slider on the left side of your phone and hold the camera button as it boots up until you see 3 grad colors. red blue, etc. it will then display your version numbers.
[2]
I wanted to learn how to cook, since I felt it wouldn't be too hard since I have a good background with computers, etc.
So.... I started following this thread:
http://forum.xda-developers.com/showthread.php?t=341243
I found a few others including the ones displayed with the hypercore download thread. But I stuck with this one as a first attempt and have not tried any others yet. I know I should but this one just bugged me, haha.
I did all steps accurately and did them again to double check...... but when I go to BuildOS.exe the top of the screen displays:
"the system cannot find the batch label specified"
Is this bad? I remember reading a long time ago about the format being unix and not dos, yatta yatta it would bring this error up but that can NOT be the possibility since everyone else has used this guys thread to create custom roms. Any ideas?
[3] (Cont'd from Question [2])
I also get some error trying to do step 2 in the BuildOS.exe menu, which is.... build OS.nb from SYS and Oem..... that error is file not specified... so i believe it has something to do with the batch error at the top, maybe? Ive tried this step 2 several times and actually got it to work and displayed new os.nb is saved in hypercore/build.... which i went there and didnt see it, but i see one inside the ROM folder... I assume this is the one I want? Perhaps?
[4] (Cont'd from Question [2])
When I try option number 3 in the BuildOS.exe menu I get this message
Save to desktop as........ as what? lol. I assumed the same name, leave it the same.... well the OS.nb was not at the location it specified. (hypercore/tools/convert) lol.
Again tho the save as problem.... I believe it all has to do with the batch file, it's like not fetching/displaying the file name.... if not it meant to leave it the same name? Anyway why is it not in the location specified?
[5]
This is what it displays after clicking enter, of course again no RUU folder found, I figured this with the previous errors. But heres what the flash option in the BuildOS.exe menu does err.... rather displays......
Again Place the _____ here..... still all the batch file problem?
[6]
Again dealing with this screen, is it ok that after Device: its blank? aka not displaying the propper htc model for the wing 3450 or whatever it is, I forget.

Dummy's Guide to update your I9000 from the stock software to the Official Froyo

After successfully;
researching, upgrading to the official build of my choosing, getting it to work and typing this tutorial out (for those that like me weren't knowledged in this),
I stumbled across this thread. I thought I should also share it here aswell.
Here's a N00b's (Dummy's) Guide to how to update your device from the stock software to the Official Samsung Froyo ROM (software/operating system) OF YOUR CHOICE!!
Why do this?
You get Froyo. So you get the latest version of Android to support more Apps.
It comes with some UI-tweeks, JIT-compiler, and FLASH 10.1 PLAYER!!!
Also you get a newer (better) kernel on your phone with some of Samsung's fixes for the lag and for the GPS.
You can get features/Apps not available in your native rom build and/or remove the bloatware.
This method (not incl E) can also be used to install custom ROMs (I personally can't wait for the Official English MIUI ROM).
** Denotes steps which I skipped, or was unable/unwilling to follow, or didn't quite understand
Here's the comprehensive, step-by-step, easy-to-follow breakdown/walkthrough (Section E only works on Windows Computers):
A) Remove your microSD card (this will prevent some weid issues later on)
A2) Make sure you have Kies downloaded and installed on your computer
A3) Make sure you have an extractor installed (for Windows 7, winRAR is a great free solution)
B) We need to root your device, for this goto "One Click Root/Unroot" by TGA_Gunnman at http://forum.xda-developers.com/showthread.php?t=742403
B1) Download (2.5MB) the software (depending on your computer, mine is Win7 Home Premium 64-bit) into your computer not phone
B2) Make a folder somewhere in your computer labelled "OneClickRoot" (or anything) and drag the .rar file (the one you just downloaded) into it
B3) Extract the contents of the files by Right-Click then "Extract Here" (If you don't have this option install WinRAR)
B4) Set your phone to USB Debug mode (on your phone goto MENU > Settings > Applications > Developement > USB debugging = Checked) and then connect the phone to the computer via USB cable.
B5) Open the "Galaxy S I9000 One-Click Root" application. (This step didn't work for me, so I instead opened "rootme" batchfile which started the command prompt).
B6) Your phone will shut itself off, and then turn on in a "recovery mode". DO NOT REMOVE THE CABLE. Use the Volume Up and Volume Down buttons to get to "install from " and then hit the Home button.
B7) Now your device should be restarting again but this time it will actually go to your lockscreen.
B8) Now, you have ROOT, Congratulations.
B9) Not sure? We can test to see if you have root. Goto Market on your phone and download two Apps (Superuser and Titanium Backup, use the search to find them fast).
B10) Install both and launch Titanium Backup. As soon as you turn it on it will come up with a pop up and say something like "Your device is not rooted" or "Root is not accessible" ... if you didn't get Root.
B11) If you have root it will say something like "Titanium Backup needs to gain permission from Superuser" here click Apply. If you get to the App, well done you have indeed Rooted your phone
C) Now if you want to Backup your device before the update (recommended) you can follow steps C, otherwise skip straight to Step D.
C1) On Titanium Backup if a pop up notification comes with something like "Download an updated BusyBox" allow it to do so.
C2) Now first thing you will want to backup your Apps (all paid and free and the levels/hiscores) make sure you don't have any emulator ROMs on there (they consume too much space) and delete all those unwanted Apps
C3) On Titanium Backup, hit the Menu button > More > Create "update.zip" ...
C4) On this screen select "User application" and "TitaniumBackup-3.6.2.zip" and UN-TICK the "Sign the ZIP file (with ZipSigner)"
C5) Hit the Create "update.zip"... on the bottom and Please wait
C6) Once it finishes it, exit Titanium Backup, go back to settings and disable USB debugging (as posted on B4).
C7) Connect your phone to your computer (through Kies or PC link) and then browse your My Computer until you find Galaxy S I9000.
C8) Open that folder and then open phone. Find "TitaniumBackup-3.6.2.zip" and copy that to somewhere on your computer.
C9) Now that we have backed up your applications, lets backup your ROM.
C10) According to TGA_Gunnman you can use Clockwork MOD Recovery to do this, but this is for a different (Galaxy S) device ie "Samsung Vibrant"
**C11) Follow the steps on http://forum.xda-developers.com/showthread.php?t=734164 to do so, personally I skipped doing so out of fear of bricking the device (there may be subtle differences between the devices that can make your phone a paperweight/brick)
C12) Now if you did follow the Clockwork MOD, be sure to copy the "update.zip" file somewhere into your computer (better be safe than sorry)
D1) Now we need to apply the 3-Button-Combo Fix (this is the only reason for steps A-C because it is highly recommended to have this before flashing ANY rom)
D2) I recommend the Fix by RazvanG http://forum.xda-developers.com/showthread.php?t=821698 because it seems to be the *safest*
**D3) Firstly check if your device is compatible. I wasn't successful to dump my BML1 block, so I couldn't test if the block reads "[email protected]"
**D3) RazvanG has provided some instructions on this method see his post for more information http://forum.xda-developers.com/showthread.php?p=9595936#post9595936
D4) So I took a leap of faith and continued anyways with the risk of bricking my device. I have it on contract/plan so if it fails I would just return it and say Kies was updating and it failed
D5) I followed the steps on the thread but I'll reitterate it here for your convnieance
D6) Download both files (RAZ-FiX-SGS and adbRecovery) from the thread.
D7) Make a new folder (adbRecovery) on your computer and extract the adb .zip file into there
D8) Connect your phone to the computer and copy the RAZ-FiX-SGS.zip into your phone's memory
D9) Delete the old Update.zip file AND rename the RAZ-FiX-SGS.zip to Update.zip
D10) Again, turn on USB debugging (you know how) and open "Recovery" batch file from your computer
D11) This will initiate a command prompt (on Win7) and restart your phone
D12) Your phone will go into recovery mode (like we've seen before)
D13) You need to navigate (Volume buttons) to "apply sdcard; update.zip" and hit the Home button
D14) Your phone will turn off and restart and should get to your lockscreen
D15) So you're at the lockscreen? SUCCESS! (mine didn't brick *pheww*)
D16) Now let's test to see if the 3-Button-Fix worked
D17) *IMPORTANT* Firstly browse into your phone's internal memory and delete update.zip (the one we put there from RazvanG)
D18) Now that you have done so, you can safely just turn off the device
D19) Hold the Volume Down + Home button ... then hold the power button, as soon as the device begins to turn on release the power button (keep holding Volume Down + Home)
D20) If you get a Yellow triangle with the Android robot and "Do not turn off Target", well done, you have the 3BF so you have a means to ensure that you can always recover your phone if you do brick, well done!
D21) You can *safely* remove the battery and restart your phone ONLY if you don't have a Update.zip in the root of your phone
D22) If you don't want to take a leap of faith try this method (safest method but doesn't work for some people): http://forum.xda-developers.com/showthread.php?t=860773
E1) Now is the fun part (we've just past the difficult parts)
E2) You need to hunt down the version of (official Samsung)software you wish to install ... just go through member's reviews and recommendations
E3) You need to find the product code of that build, you can do this navigating through this thread http://forum.xda-developers.com/showthread.php?t=846913
OR by asking members (they can find out with http://forum.xda-developers.com/showthread.php?t=787163)
E4) For me this was the Virgin mobile Australia build (XSA - an unbadged, no-bloatware, unlocked Froyo build with a free copy of Navigon Navigation)
E5) Make sure you update your Kies to "ver 1.5.3.10103_102" (latest as of the time I'm writing)
E6) Go visit this thread http://forum.xda-developers.com/showthread.php?t=835628 for information (the software may have been upgraded)
E7) Download (300KBs) the Kies Registry patcher 1.6.0.0 (latest as of writing) <<This only works on Windows computers, sorry Mac'ners>>
E8) Launch the Kies Registry Patcher WHEN KIES IS OPENED
E9) Click on File > Backup (and save this somewhere in your computer - this is your original product code - better safe than sorry)
E10) Make Enable Spoof to True
E11) Now where it says "Spoof Product Code as" type in the product code of your desire (mine is XSA)
E12) Hit Write Registry and it should say "Registry pathed successfully"
E13) Connect your phone via USB cable to the computer
E14) On your phone select "Samsung Kies" when the pop up comes ... it should be at the "Connected" screen (DO NOT HIT HOME BUTTON)
E15) On Kies it should find your phone, and a pop up on the corner will say "There is a firmware update available for your phone" hit that pop up
E16) Now you will see another pop up and it's asking if you want to "Back up contacts before upgrading firmware" ... seems like a good idea, tick the box and hit Upgrade
E17) If the screen on the phone shuts (ie standby) don't be alerted. Hit the power button to wake it up. DO NOT HIT THE HOME BUTTON!
E18) Another pop up will come to name the contacts file - I just hit save so its the original filename in original (Samsung)folder
E19) Another Pop up will come to say "Save to PC completed" - hit OK, its just letting you know the contacts saved properly
E20) Now you get another Pop up to start the Firmware Upgrade - This is an important area, note down the: Model Name, Current Version and Latest Version (if something goes wrong this info maybe valuable for developers)
E21) Mine is (model)GT-I9000, (current)PDA:JG4 / Phone:JG3 / CSC:JG2 and (latest) PDA:JP5 / Phone:JP3 / CSC:JP4 ......... notice they are diffirent, this is what I was looking for
E22) Hit Upgrade! (Allow Kies to function when Windows 7 or Windows Vista prompts you)
E23) Tick the "All information has been verified" and Click Next
**E24) Let Samsung record your phone number in their database? I don't care (I'm on insurance/contract/plan) and I hit "Allow saving" ad Clicked Next
E25) Wait patiently, its downloading the rom from the server, DO NOT UNPLUG THE DEVICE
E26) A progress bar will appear, your USB will get disconnected, reconnected several times, the phone will be stuck on the yellow triangle screen - these are normal
E27) The progress bar will slowly be filled from grey to blue and a progress bar will appear on your phone - almost there!
E28) The progress bar on the computer will finish and the pop up will read "GT-I9000 Upgrade completed" - Click Close
E29) Your phone will restart and will enter "recovery mode" some yellow texts will appear and scroll forward
E30) The phone will reboot again and you will see the boot image with the Galaxy S logo
E31) The phone will be stuck on that logo for awhile - be patient
E32) The phone will now get to your lockscreen, unlock it
E33) You will have to go through your initial setup firstly its the Swype tutorial, then data settings, and finally the account settings emerges
E34) If the Kies connection screen comes up: hit the home button
E35) Now you should have come to your Homescreen go and test everything (all your passwords, all your bookmarks, all your contacts, all your images/music/videos and all your apps (except bloatware) should be there but the order of all the widgets/apps in TouchWizz will be reset to abc-order)
E36) Goto Settings > About Phone Does it say Android 2.2?
E37) Well done you have passed Android Hacking 101, you are officially smarter than 50% of iPhone and Blackberry users
E38) Donate me a beer, nah just kidding, enjoy everything for free but feel free to donate to the developers that help make this possible

this is a guide for I9000 international
I9000M owners please be advised that the I9000 might cause you to lose the 850 band, and might also trigger the internal SD problem

AllGamer said:
this is a guide for I9000 international
I9000M owners please be advized that the I9000 might cause you to lose the 850 band, and might also trigger the internal SD problem
Click to expand...
Click to collapse
You made it into a thread, thanks!
Hopefully this might help fellow xdanians

Aww Mate this is awesome, I have the same Carrier and I had OPTUS crap on my Phone from custom roms, Now I'm back to Stock Froyo!!!!
A great tool to Start from afresh.....
But
At Instruction E11 - Select your product code from the drop down Box and it will populate the next field for you.

Gonna put into my favorites

Wow.
I don't think anybody that don't now much would read that.
I know allot and i would never use it either.
You should stick a warning sign on this tread.
I did read about half of it and then i just stop and shake my head.
I hope this tread is a joke.....
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram

DamianGto said:
Wow.
I don't think anybody that don't now much would read that.
I know allot and i would never use it either.
You should stick a warning sign on this tread.
I did read about half of it and then i just stop and shake my head.
I hope this tread is a joke.....
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
Click to expand...
Click to collapse
Can you elaborate?
Joke? No it's no joke but I should disclose (as always) this is a tried-and-true way of getting you to update your software but in no way can I be held responsible for damages.
Things may vary slightly in between different phones which is why the links for each source/thread is up there.
I found myself knowing what to do, but always guessing how to do it.
This is a step-by-step process of how and what I did to upgrade my phone to any ROM I want.
If this was posted up before I attempted my upgrade, I would've been so happy that someone really simplified it for me

This is a noobs guide??!!! Simplified??!! I think that everyone will appreciate the time you have spent typing this up and trying to help, but I'm with DamianGto, dude this guide is scary and just explains how YOU got YOUR particular phone running froyo and lets face it, you certainly didn't go about it the easy way!
Once again I think the time you have spent and the willingness to help is admirable, but there are much simpler and noob friendly guides out there

nagrom78 said:
This is a noobs guide??!!! Simplified??!! I think that everyone will appreciate the time you have spent typing this up and trying to help, but I'm with DamianGto, dude this guide is scary and just explains how YOU got YOUR particular phone running froyo and lets face it, you certainly didn't go about it the easy way!
Once again I think the time you have spent and the willingness to help is admirable, but there are much simpler and noob friendly guides out there
Click to expand...
Click to collapse
Well you need root + busybox to get the 3 button fix.
If anything a n00b did, they can recover with 3 button trick otherwise they will have a brick.
This is why this guide is long, to ensure things are a-ok.
If you found a friendlier guide can you post the link, much apprecated ;D

How do I exit downloading mode if I forgot to erase update.zip ?

What is it ? Kies
A2) Make sure you have Kies downloaded and installed on your computer
Thanks

Well I think this is an excellent guide that has great potential!
However, a couple of crucial mistakes, which if fixed could help make the guides less confusing...
At beginning of (D) you talk about (A-C) being solely so you could fix your 3 button download (which I don't think is actually true!)
.... But, you should mention 3 button download at the very start of the guide anyway!!
Also, you should include a quick test at the very start to check for 3 button download, because mine is already fine, so a newbie might run all those extra steps when they already had working 3 button download anyway! (The more sections that can be skipped the better!). You can then steer people to the sections they uniquely will need.
However, titanium backup isn't needed for 3 button download fix, but is a wise step before running a rom update. And this works best with root anyway. Hence I don't think your opener for (D) is very accurate. You didn't just complete those steps JUST to get download mode. The backup was important anyway!
Do others think there should be a stage added for backing up contacts etc?
A stage for backing up efi?
Anything else wise that should be in here?