fastboot binary for windows!

JesusFreke

Inactive Recognized Developer
Oct 23, 2008
736
54
0
Dallas
I've compiled a fastboot binary for windows from the git source, using cygwin.

I had actually compiled it a couple of weeks ago, but I never could get it to work. I was looking into it again tonight and discovered that windows had installed the USB Mass Storage driver for the phone in SPL mode, instead of the android driver. So after updating it to the android driver, it worked! woot :)


Instructions:

(note: you have to check the USB device in Computer Manager when the phone is in fastboot mode. The computer sees the phone in fastboot mode as a different device than the phone in normal mode)

Download the file and extract it in the same folder as adb. (if you don't have adb yet, it's included in the android SDK for windows. go download it!)

Take out the usb cable and boot up your phone into the SPL (back + power). You have to have the dev bootloader for this to work (white background with 3 skateboarding androids).

Plug in the usb cable, and make sure the display on the phone changes from "Serial0" to "FASTBOOT". If it doesn't, try pressing the back button.

If it asks you to install drivers, then go ahead and use the same usb drivers that you used to get adb working. You can skip the rest of the instructions. Fastboot should be working for you now.


If it doesn't ask you to install a driver, you need to figure out if the correct driver is loaded already.
Right click on My Computer, and click Manage, then go to the device manager

If you see an "ADB Interface" category at/near the top, with "HTC Dream" under it, then you're good to go. Fastboot should be working for you.

If you don't see an "ADB Interface" category, then it's likely that windows loaded the USB Mass Storage driver for it automatically. In the device manager, go down to "Universal Serial Bus Controllers", and see if you have at least one "USB Mass Storage device". If you have multiple ones, you'll need to go through each to find the correct one.

To find the correct one, right click on the USB Mass Storage device and click Properties. Go to the Details tab. In the combo box at the top that says "Device Instance Id", bring up the pull down and choose "Compatible Ids". If that is the correct device, then you will see 3 entries:
  • USB\Class_ff&SubClass_42&Prot_03
  • USB\Class_ff&SubClass_42
  • USB\Class_ff

Once you find the correct device, go to the driver tab, and click "Update Driver". Choose "No, not this time", then "Install from a list or specific location", then "Don't search, I will choose the driver to install", and then choose the same usb driver that you used to get adb to work.

After that's done, you should be good to go. Open a command prompt and type fastboot devices and it should list the phone.
 

Attachments

Last edited:

afbcamaro

Senior Member
Dec 23, 2006
209
18
0
Thanks JF, not for the files, I already had them compiled but because I found out why they weren't working...

USB MassStorage driver was as well on! :) LOL Its the simple things sometimes.
 

pablizzo

Senior Member
Nov 9, 2008
57
1
0
That's fantastic thanks JF. Now since we got fastboot in windows how does that change the process for having our custom boot image. I could not for the life of me get fastboot to recognize my device in ubuntu no matter what I did.
 

JesusFreke

Inactive Recognized Developer
Oct 23, 2008
736
54
0
Dallas
That's fantastic thanks JF. Now since we got fastboot in windows how does that change the process for having our custom boot image. I could not for the life of me get fastboot to recognize my device in ubuntu no matter what I did.
Let me take a shot in the dark and say that it would allow you to do the "fastboot flash splash1 image.rgb565" part from windows instead of ubuntu? :D

Don't forget about koush's .NET application to convert an image to the correct format: http://forum.xda-developers.com/showthread.php?t=462489
 

momentarylapseofreason

Senior Member
Apr 29, 2007
1,080
18
68
Chicago
Pardon my ignorance, but all that I can see with search about fastboot is it allows us to flash cupcake and new splash screens.

Can someone enlighten me as to what exactly this is? Does it simply bypass key signatures or error checks? Being that I don't turn my phone on and off a lot, a custom splash is really not necessary and being that cupcake is severely limited, don't want to even toy with that until it has more work in it.

Thanks in advance!!!
 

JesusFreke

Inactive Recognized Developer
Oct 23, 2008
736
54
0
Dallas
Ha, thanks. But it's not like I wrote it or anything. The windows code is all there. I just figured out how to get it to compile in cygwin. (and figured out the driver thing, of course)
 

Stericson

Retired Senior Mod / Retired Senior RecDev - Godfa
Nov 10, 2008
1,203
417
0
:) I think your givin me too much credit....JF could handle the app shop all by himself, he's just that good ;)

Stericson
 

yiyunzhi

Member
Dec 25, 2008
7
0
0
hi,can i use this tool flash the cupcake to my G1?the driver is good,fastboot is good work,but when i use the command that FLASHALL,its told the products specified and android-products-out must be setted。i dont know whats that means~
 

damien667

Senior Member
Oct 27, 2008
147
42
0
I've had issues with fastboot depending on which USB cable I used (I have different kinds with different shielding)... I assume my "cheap" cables didn't have enough shielding and corruption happened when trying to communicate... also noticed that this happened as well while using a USB hub... I now have a good cable connected to the BACK port of my PC... I used the back port because front ports have extensions running from the motherboard through the inside of the case that were making interference as well... hope this helps!