fastboot binary for windows!

Sumanitu · Jan 5, 2009

"cache: 70 megs, supposed to be temporary storage (/cache) but actually never used except by T-mobile OTA updates."

So is it possible that a future custom build of android could allow that partition to be used for apps or something else? 70MB is alot of wasted space for those of us that will never ever get an OTA again.

JesusFreke · Jan 5, 2009

Sumanitu said:
"cache: 70 megs, supposed to be temporary storage (/cache) but actually never used except by T-mobile OTA updates."

So is it possible that a future custom build of android could allow that partition to be used for apps or something else? 70MB is alot of wasted space for those of us that will never ever get an OTA again.

Cache is wiped when you install a new bootloader (or radio image) via recovery. It's not a good idea to put anything in /cache that you want to keep around.

It might be possible to tweak the partition map in the SPL, to make /cache smaller, and give that space to /data. But I'm not keen on trying out mods to the bootloader. If you mess that up you've got a brick. A brick brick. An "it won't boot at all" brick. The kind you build walls with.

.

Sumanitu · Jan 5, 2009

JesusFreke said:
Cache is wiped when you install a new bootloader (or radio image) via recovery. It's not a good idea to put anything in /cache that you want to keep around.

It might be possible to tweak the partition map in the SPL, to make /cache smaller, and give that space to /data. But I'm not keen on trying out mods to the bootloader. If you mess that up you've got a brick. A brick brick. An "it won't boot at all" brick. The kind you build walls with. .

I can definitely see why you wouldn't want to mess with the SPL, but someone had to tweak the SPL to get hardspl out, no? Giving the /data partition another 70 megs would solve most people's worries of not enough space for a good long time, until google or someone else releases a proper way to install apps on the sdcard.

And besides, doesn't it bug you that 70 of your phone's 256MB of flash will forever sit around idle?

jashsu · Jan 5, 2009

Sumanitu said:
And besides, doesn't it bug you that 70 of your phone's 256MB of flash will forever sit around idle?

jbq (Android team member who designed the download manager) did mention possibly opening up /CACHE to other usages other than a place to store temporary download data.

https://groups.google.com/group/and...read/thread/5a06ff2e95acb552/b564ac092ea470ac

Of course that doesn't really fix the problem that any data stored in cache is ephemeral-- it can at any time be removed to make space for an OTA update.

texasaggie1 · Jan 5, 2009

Fastboot and other OS's

JesusFreke said:
http://www.gotontheinter.net/content/fastboot-cheat-sheet

Ok. Got it. This looks pretty powerful. 2 questions:

1) Could we use fastboot to load other ROM's, just for fun of course, like iphone roms, wm6 roms, or who the heck knows what else...

2) Did you write fastboot? If so, great job.

jashsu · Jan 5, 2009

texasaggie1 said:
Ok. Got it. This looks pretty powerful. 2 questions:

1) Could we use fastboot to load other ROM's, just for fun of course, like iphone roms, wm6 roms, or who the heck knows what else...

No.

2) Did you write fastboot? If so, great job.

He compiled the windows version. The code itself is part of the Android Project (source code).

Sumanitu · Jan 5, 2009

jashsu said:
jbq (Android team member who designed the download manager) did mention possibly opening up /CACHE to other usages other than a place to store temporary download data.

https://groups.google.com/group/and...read/thread/5a06ff2e95acb552/b564ac092ea470ac

Of course that doesn't really fix the problem that any data stored in cache is ephemeral-- it can at any time be removed to make space for an OTA update.

But if OTA updates never come due to having a modded recovery image and modded RC whatever, then the cache is more permanent.

jashsu · Jan 5, 2009

It will download; it just won't apply the update. And even if it didn't download, due to the design intention, the system would still treat /cache as a temporary storage area.

sinbot · Jan 6, 2009

So wouldn't it maybe be better to use /cache for the browser and market cache?

Sumanitu · Jan 6, 2009

sinbot said:
So wouldn't it maybe be better to use /cache for the browser and market cache?

I think the bookmarks and other browser settings are stored in the broser cache files too, but I'm not sure.

apfroggy0408 · Jun 2, 2009

Instead of windows loading it as a usb storage device it's loaded as android 1.0 and it won't allow me to update the driver from the sdk. Any ideas to this?

MonkySlap · Jun 2, 2009

apfroggy0408 said:
Instead of windows loading it as a usb storage device it's loaded as android 1.0 and it won't allow me to update the driver from the sdk. Any ideas to this?

Just download the Android 1.5r2 SDK from googles website. You need the updated drivers if you are running 1.5 i believe.

apfroggy0408 · Jun 2, 2009

That was it thanks a lot.

pensive · Jun 29, 2009

fastboot with JF1.51

I am currently running JF1.51 the US version. Apparently I have the dev bootloader (I get the androids screen when I boot with camera+end call), but for some reason when I boot my device into the fastboot mode
(with fastboot on the screen) the Windows fastboot just does NOT see it.
fastboot devices produces no output, fastboot reboot produces a line which
says it is waiting for the device. I did check the windows drivers and it looks ok. When NOT in bootloader mode the ADB can see the device.

Any thoughts anyone?

JesusFreke said:
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

THE REST OF INSTRUCTIONS DELETED FOR BREVITY'S SAKE.

Seanambers · Jun 29, 2009

Your're sure you are using the latest .dll?

pensive · Jun 29, 2009

fastboot with JF1.51 US (dll)

Well, I have to believe my senses, right? I looked at the .dll in the SDK1.5, it seems the same size as the one in the /windows/system32. I am assuming the dll we are talking about is 1,419,232 wdfcoinstaller01005.dll. The strange thing is that when the g1 is in normal state, not bootloader then adb can see it, and I can actually connect it via "adb shell". But the moment I put the phone into the bootloader state neither the fastboot not adb can see it anymore.

Seanambers · Jun 29, 2009

Well im no expert but i belive fastboot.exe uses AdbWinApi.dll

I suggest starting from scratch and follow the relevant parts from this guide:
http://androidcommunity.com/forums/f10/adb-fastboot-for-rookies-18124/

If this dosnt work; i am sorry to say i have exhausted my troubleshooting skills =)
Good Luck

pensive · Jun 30, 2009

Still no success fastboot[ing] JF1.51

Thanks for the advice, but following that "how-to" did not get me anywhere.
I even reloaded the eng/dev bootloader with the same behavior. It seems that
after I boot the device in bootloader mode it will not go to "fastboot" screen until I plug in the USB connector, pressing the back just paints the same screen
with serial0. When I plug in the usb it automatically goes to fastboot. Sadly the PC fastboot still cannot control the g1.

Perhaps someone else has some idea.

pensive · Jun 30, 2009

Ok, I have resolved my problem with fastboot vs. JF1.51

Hopefully this helps others who have problems with Windows drivers. I am using 32bit XP on Dell Vostro.

It seems Windows treats normal G1 boot mode differently than fastboot mode.
You may have to install drivers twice. Once with G1 in normal mode, connected to the USB port. THen a second time with G1 in fastboot mode.
Even if it appears that the device/drivers have been successfully installed
when G1 was in normal mode, it may not be enough to use the fastboot under windows.

pensive said:
Thanks for the advice, but following that "how-to" did not get me anywhere.
I even reloaded the eng/dev bootloader with the same behavior. It seems that
after I boot the device in bootloader mode it will not go to "fastboot" screen until I plug in the USB connector, pressing the back just paints the same screen
with serial0. When I plug in the usb it automatically goes to fastboot. Sadly the PC fastboot still cannot control the g1.

Perhaps someone else has some idea.

KingMe26 · Sep 9, 2009

i need help

ok i accidentally re-imaged the dreaimg.nbh while trying to flash a new startup pic. now it won even boot up to the android logo. please tell me i didnt brick my phone.

fastboot binary for windows!

Member

Inactive Recognized Developer

Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

New member

Similar threads

Top Liked Posts