Easy guide to update to Galaxo or GAOSP!

***
There are other ways to install the custom recovery, but this method probably is the most used. If you want to use the Drakaz application, you will have to root your phone first using the easyroot method by Drakaz. The easiest way to get the custom recovery would be to Odin the JC6 firmware with integrated recovery, but you shouldn't mess with any of that if you don't really know what you are doing.***
____________________

The guide is now updated for Galaxo 1.6.3.4 or GAOSP Beta 3!

Ladies and gentlemen, here's a complete idiot's guide to updating to Galaxo/Gaosp! It seems long and complicated, but it really isn't. I was using the JC6 firmware on my phone before updating to Galaxo, but you don't need any specific firmware. You don't ever need to use an external SD card during this process.

THIS WORKS FOR BOTH I7500 AND I7500L

**I suggest downloading and saving every folder directly on your desktop, so everything is easy to find.**

This guide takes for granted that you can access your phone via USB from your computer. If the device isn't detected properly, you should install Samsung New PC Studio (NPS). You don't need to use the software at all, but it will install the correct drivers. To access your phone from your PC, plug it in and then move the notification bar down, select the USB notification and then select "Mount".

STEP 1 (ADB drivers):

You need to install the ADB drivers, which mean Android Debug Bridge. You&#8217;ll need those to operate the Android SDK correctly. You don&#8217;t understand what I&#8217;m saying? No worries, just follow the tutorial, and if you have a problem, post your question saying what went wrong and what happened.

I&#8217;m using Windows 7 (32 bits), so maybe the steps aren&#8217;t exactly the same for other versions of Windows.

Open your Galaxy, go into the Settings, select Applications, then Development, then tick USB debugging. Now plug it into your computer. Open up the device manager.

You should see an unknown device with a yellow exclamation mark. Right-click it and select update drivers.

Select Browse my computer.

Select Let me pick from a list of device drivers on my computer.

If you see a list of devices and you have to pick one, don&#8217;t select any and just click next again. Then, click &#8220;Have Disk&#8221;. Browse to the &#8220;usb_driver&#8221; folder, then select the x86 folder (which means 32-bits) and in it select &#8220;android_usb.inf". If you have a 64 bits version of Windows, instead of going into the x86 folder, get the &#8220;android_usb.inf&#8221; that is in the amd64 folder.

Your device should now have the required drivers. More on that later, but for now just stick to the guide. If none of the three "android_usb.inf" seem to be working, you should try this one, it might solve your problem.

I suggest saving all of those to the same place, to avoid confusion.
Start by placing the &#8220;android-sdk-windows&#8221; folder to the root of your C drive. The place doesn&#8217;t really matter, but you&#8217;ll have to type the path into a command prompt later, so if you follow my example, place it in the root of your C drive.

Extract &#8220;RECOVERY_version number.zip&#8221;. You now have &#8220;recovery.img&#8221; and &#8220;RECTOOLS.tar.gz&#8221;. Take &#8220;recovery.img&#8221; and place it in the &#8220;tools&#8221; folder of the &#8220;android-sdk-windows&#8221; folder, which should now be located right into your C drive.

Mount your phone, you&#8217;re going to be placing stuff on it.

Take &#8220;GAOSP-2-PUBLIC-BETA-3.zip" or "Galaxo_1.6.3.4.zip&#8221;, &#8220;Gapps_light.zip&#8221; and &#8220;RECTOOLS.tar.gz&#8221; (the last one was in RECOVERY_version numbers.zip), and place them on the internal SD card of your phone. I placed the three of those in no folders, directly on the phone, just in case. Alright!

STEP 3 (Recovery and update):

Power off your phone. It should still be connected via USB.

Open a Command Prompt (search for &#8220;cmd&#8221; in the start menu, and click on &#8220;cmd.exe&#8221.

Type &#8220;cd C:\android-sdk-windows\tools&#8221;, of course without the &#8220; &#8221;. If you didn&#8217;t put the Android SDK on the root of your C drive, you&#8217;ll have to modify this line and put the actual path. Press enter.

Boot your phone into fastboot mode, do so by pressing and holding both the Call button (bottom left) and Power button (bottom right) at the same time, until you see on the phone that you are in fastboot mode. You&#8217;ll have about 15 seconds to press enter on the command prompt on the computer. If it works, you&#8217;ll see something else than &#8220;waiting for device&#8221; appear in the command prompt.

Fastboot on the phone (picture took by Chronodekar and his brother, thanks!):

When I tried to do so, it wouldn&#8217;t do anything. It would wait for the device, then my Galaxy would boot normally. To solve this, open the device manager on your computer and turn the Galaxy off again. You are going to boot into fastboot mode again, but you&#8217;ll have about 15 seconds to check the device manager (open it beforehand), and see if there&#8217;s a new device that needs drivers. Mine was something like Android 1.0 (with a yellow exclamation mark, meaning that there are no drivers). You&#8217;ll do the exact same thing as you did with the ADB driver, using the exact same driver (right click the unknown device, update the driver, select from a list, next, Have disk, Browser, then find the same &#8220;android_usb.inf&#8221;. Check the beginning of the guide if you don&#8217;t remember what to do.) You'll need to do this during the 15 seconds the Android 1.0 will appear, so you have to be quick.

During the process, on the phone (picture took by Chronodekar and his bro):

Success (command prompt):

If it worked, well great, now power off your phone again. Boot it again, but this time in recovery mode. Do so by holding the &#8220;Lower volume button&#8221;, the Call button and the power button. If it works, you&#8217;ll see a green menu with lots of choices. You&#8217;re almost done.

Go down and select &#8220;Nandroid backup&#8221;. It will take a short while but it sure is worth it. You'll have to press the Home button to confirm, just follow the instructions on-screen.

Now, select &#8220;Wipe data/Factory reset&#8221;. It&#8217;s going to erase all your applications and settings, but it shouldn&#8217;t touch anything saved on your SD card (such as pictures, music, saves, etc). It&#8217;s important to do so, else the phone will not work properly.

After that, select "Apply any zip". Now on the list find either the GAOSP.zip file or the Galaxo.zip file, depending on your choice. Right after that, select "fix package permissions", then "apply any zip" again but this time pick the Gapps you previously downloaded, which will restore the Google Applications on your phone. I do not recommend to wipe again at this point, it seems pointless to me.

You can now reboot and enjoy Galaxo or GAOSP!

**Now if you want to switch between GAOSP and Galaxo or if you want to change version of GAOSP or Galaxo, you simply have to put the new .zip on your phone, boot into recovery, wipe, apply the zip, fix package permissions, apply the Gapps and you're good to go. The "hard" part is to install the custom recovery for the first time.**

If the phone gets stuck on the Android screen, wait for about 10 minutes, and then if it's still stuck, pull out the battery and boot again. If it still doesn't work, you can try again, or boot into recovery and try to apply Gaosp.zip or Galaxo.zip again, rebooting, and then fix package permissions and apply the Google apps.

______________________________________

Have questions, comments? Post them here!

You want to thank me? Screw me, donate some money to DRAKAZ! He did all the hard stuff!

Thanks so much for this. I've not tried Galaxo yet despite having my Galaxy for months, but this should make it much easier. I haven't really understood what to do (or even exactly what Galaxo, Recovery, etc all do).

I have been afraid to ask for a guide like this as I know someone would go "read the FAQ". I'm not a newb with the phone or computers, I just find some of this Android stuff a bit confusing.

hmm I really cant seem to get past the waiting for device screen... did all the steps you said but the android 1.0 figure kept coming back even if I kept installing the driver all the time... weird :S

Click to expand...

Just to be sure, did you install the driver during the 15 seconds time lapse? I don't know if it's necessary, but that's what I did, and I had to do it quick. (You can only see Android 1.0 during those 15 secs, right?)

Just to be sure, did you install the driver during the 15 seconds time lapse? I don't know if it's necessary, but that's what I did, and I had to do it quick. (You can only see Android 1.0 during those 15 secs, right?)

Click to expand...

Yup keep at it. Remember that you can just hit "UP ARROW" in the CMD box to repeat the last command so you do not have to retype that long string or paste it. Alternate installing Android 1.0 devices as they appear and hitting that ENTER key on the CMD command. Eventually you will get the OKAY message but it will take a few attempts and many lengthy reboots.

Just to be sure, did you install the driver during the 15 seconds time lapse? I don't know if it's necessary, but that's what I did, and I had to do it quick. (You can only see Android 1.0 during those 15 secs, right?)

Click to expand...

Well I always seem to run out of time. I kinda figured it had to be in those 15 seconds, but nevertheless it seems like thats almost impossible :S

What I did was: During the 15 sec I had time to find the android 1.0 in devicemanagement and access it before it vanished. Once I had clicked on it and had it open, I had all the time in the world to install the drivers that was needed.

Edit: sorry about the "til". Fixed it. The phone replaces words from time to time

alright, great got it work now. Had to install the driver in the 15 second time stamp, which worked in the dying moment . Anyways flying through 1.6.3.1. now with 614 mhz... seriously feels like a new phone! Thanks for the great guide!

after successfully rooting my wife's g1, i wanted to update to galaxo on my i7500. i bought it already rooted (baseband XXII5, kernel 2.6.27, firmware 1.5, and says "galaxy with MCR 1.2). before i update to galaxo, is it still necessary for me to flash a new recovery image or is that already done for me?

what steps should i take from here, besides the new update.zip??? please help a new guy break into the android universe. (you can email me at kyle.grealis@gmail.com also)

after successfully rooting my wife's g1, i wanted to update to galaxo on my i7500. i bought it already rooted (baseband XXII5, kernel 2.6.27, firmware 1.5, and says "galaxy with MCR 1.2). before i update to galaxo, is it still necessary for me to flash a new recovery image or is that already done for me?

what steps should i take from here, besides the new update.zip??? please help a new guy break into the android universe. (you can email me at kyle.grealis@gmail.com also)

Hi, have been stuck for a day or two on apply sdcard:update zip I get this message.....
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.
I've tried putting a dummy update .zip file on the sd card and instead of no such file it just says "Bad"
I have reformatted the card and followed the very clear instructions to the letter.
On the computer the card's letter is G and not E but I think that it is just windows giving that letter. I have tried galaxo 1.6.3. but the same thing happened any idea's anyone
edit: I have just noticed although I installed JC6 the Baseband version shows I17500XXIJ1 could this be the problem ?

Hi, have been stuck for a day or two on apply sdcard:update zip I get this message.....
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.
I've tried putting a dummy update .zip file on the sd card and instead of no such file it just says "Bad"
I have reformatted the card and followed the very clear instructions to the letter.
On the computer the card's letter is G and not E but I think that it is just windows giving that letter. I have tried galaxo 1.6.3. but the same thing happened any idea's anyone
edit: I have just noticed although I installed JC6 the Baseband version shows I17500XXIJ1 could this be the problem ?

Click to expand...

Are you putting the file on the removable SD card or the internal memory poorly called \sdcard\ ? The latter is correct.