yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] snoslicer8:
Here's the update-script:

assert getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,release-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,release-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,release-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,test-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,test-keys" || getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,test-keys"
assert compatible_with("0.2") == "true"
assert getprop("ro.product.device") == "dream" || getprop("ro.build.product") == "dream"
assert getprop("ro.bootloader") == "0.95.0000"
format BOOT:
show_progress 0.1 0
write_radio_image PACKAGE:radio.img
show_progress 0.5 0
format SYSTEM:
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:
set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
symlink dumpstate SYSTEM:bin/dumpcrash
set_perm 0 3004 02755 SYSTEM:bin/ping
symlink toolbox SYSTEM:bin/dmesg
symlink toolbox SYSTEM:bin/df
symlink toolbox SYSTEM:bin/getevent
symlink toolbox SYSTEM:bin/getprop
symlink toolbox SYSTEM:bin/hd
symlink toolbox SYSTEM:bin/id
symlink toolbox SYSTEM:bin/ifconfig
symlink toolbox SYSTEM:bin/iftop
symlink toolbox SYSTEM:bin/insmod
symlink toolbox SYSTEM:bin/ioctl
symlink toolbox SYSTEM:bin/kill
symlink toolbox SYSTEM:bin/ln
symlink toolbox SYSTEM:bin/log
symlink toolbox SYSTEM:bin/ls
symlink toolbox SYSTEM:bin/lsmod
symlink toolbox SYSTEM:bin/mkdir
symlink toolbox SYSTEM:bin/mkdosfs
symlink toolbox SYSTEM:bin/mount
symlink toolbox SYSTEM:bin/mv
set_perm 0 3003 02755 SYSTEM:bin/netcfg
symlink toolbox SYSTEM:bin/netstat
symlink toolbox SYSTEM:bin/notify
symlink toolbox SYSTEM:bin/ps
symlink toolbox SYSTEM:bin/printenv
symlink toolbox SYSTEM:bin/reboot
symlink toolbox SYSTEM:bin/rm
symlink toolbox SYSTEM:bin/renice
symlink toolbox SYSTEM:bin/rmdir
symlink toolbox SYSTEM:bin/rmmod
symlink toolbox SYSTEM:bin/route
symlink toolbox SYSTEM:bin/schedtop
symlink toolbox SYSTEM:bin/sendevent
symlink toolbox SYSTEM:bin/setconsole
symlink toolbox SYSTEM:bin/setprop
symlink toolbox SYSTEM:bin/sleep
symlink toolbox SYSTEM:bin/smd
symlink toolbox SYSTEM:bin/start
symlink toolbox SYSTEM:bin/stop
symlink toolbox SYSTEM:bin/sync
symlink toolbox SYSTEM:bin/top
symlink toolbox SYSTEM:bin/umount
symlink toolbox SYSTEM:bin/vmstat
symlink toolbox SYSTEM:bin/watchprops
symlink toolbox SYSTEM:bin/wipe
symlink toolbox SYSTEM:bin/cat
symlink toolbox SYSTEM:bin/chmod
symlink toolbox SYSTEM:bin/cmp
symlink toolbox SYSTEM:bin/date
symlink toolbox SYSTEM:bin/dd
set_perm 1002 1002 0440 SYSTEM:etc/dbus.conf
set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh
set_perm 1002 1002 0440 SYSTEM:etc/hcid.conf
set_perm 1014 2000 0550 SYSTEM:etc/dhcpcd/dhcpcd-run-hooks
show_progress 0.2 0
write_raw_image PACKAGE:boot.img BOOT:
show_progress 0.2 10
[G1 Android Development] dtmcnamara:
lol...awesome...what the link to the forums? i love ranting and raving
[G1 Android Development] dtmcnamara:
can you not just do settings / SDcard& phone storage / factory data reset?
[G1 Android Development] snoslicer8:
Factory reset works, but it just erases all data and brings you back to a blank phone with the latest software you've installed...ie mine is the test version of RC29

A factory restore doesn't bring you back down to RC19
[G1 Android Development] dtmcnamara:
damn...that sucks...hope things work out for ya...maybe the next released update will work and get rid of that beta version for ya
[G1 Android Development] Darkrift:
Or maybe he is lucky and has some super cool features that the gen public is not supposed to get. That is what id be looking/hoping for ;)
[G1 Android Development] dtmcnamara:
does it do anything cool now....aka

pocket knife, bottle opener, tradmill...etc etc

lol
[G1 Android Development] speoples20:
I was going to use this but I just got the update from T-mobile.:) Guess I could use it if I decide to reset my phone.
[G1 Android Development] neoobs:
http://forums.t-mobile.com/tmbl?category.id=Android
[G1 Android Development] snoslicer8:
Can anyone that has RC29 installed from the SD card method OR from the official OTA update do something for me?

Make an AnyCut shortcut to an Activity of DeviceInfo, launch it, and give me the following info:

Build description:

Build id:

Build date:

Build type:

I'd REALLY appreciate it.

Thanks!
[G1 Android Development] dtmcnamara:
Build description:

kila-user 1.0 TC4-RC29 115247

ota-rel-keys,release-keys

Build id:

TC4-RC29

Build date:

Fri Oct 24 15:44:43 PDT 2008

Build type:

user
[G1 Android Development] neoobs:
Build description:kila-user 1.0 TC4-RC29 115247 ota-rel-keys,release-keys

Build id:TC4-RC29

Build date:Fri Oct 24 15:44:43 PDT 2008

Build type:user
[G1 Android Development] dtmcnamara:
first...lol
[G1 Android Development] neoobs:
better to have 2 to double check than just 1 don't you think LOL
[G1 Android Development] snoslicer8:
Thanks guys. So far, my info is the exact same as everyone else's EXCEPT the bold part below:

kila-user 1.0 TC4-RC29 115247

ota-rel-keys,for-testing,release-keys

Even my build date/time is the same, down to the second. It seems I just have an extra decryption key for updates.
[G1 Android Development] neoobs:
Is that a good or bad thing? LOL
[G1 Android Development] snoslicer8:
I hope it's a good thing.

At the very least, my build will be able to decrypt the next public build that is released, and I'll be out of this mess.
[G1 Android Development] neoobs:
Maybe you will always have for-testing on yours... maybe it adds more functionality in the end or maybe it gives you the ability to sign your own packages or verify different signed packages.
[G1 Android Development] quedijo:
The wiered thing is that it is the latest EVERYTHING...

It is exactly the same build as ours but with extras...

Now I want to flash mine to it
[G1 Android Development] neoobs:
what extras?
[G1 Android Development] rev_otto:
Eh...Now I have myfaves.

I'm thrilled that I've got the update and I'm tinkering with the guts of my G1. Not thrilled that I have myfaves and a persistant sms from T-Mobile saying my MyFaves contacts are being refreshed everytime I turn the phone off and on. Are there different firmware revs for MyFave vs. Non-MF users? Any clue how to make this "disappear" as you can't uninstall it? Will I still get the OTA to take care of this? (I haven't yet received it.)
[G1 Android Development] neoobs:
I don't see the MyFaves application. Try going to settings->applications->manage->myfaves->clear data
[G1 Android Development] rev_otto:
Clearing the data just makes me get another sms saying, "your myfaves blah blah blah is being updated". I never had this app before. I tried doing the flash again and it still reappears. Except this time it just has hour glasses in the faves circles instead of the add users. I know it's not a biggie, but it's pretty annoying having it on the list and not being able to delete it. Any clue if doing the sd style update before you get the OTA will prevent the OTA from coming?

Thanks.
[G1 Android Development] neoobs:
Everyone has that app installed... it just isn't visible unless you have myfaves. This is weird. Maybe a hard reset of the device will clear it.

The SD update will prevent the same OTA update from coming yes. The ota update only updates phones that don't have RC29 installed.
[G1 Android Development] rev_otto:
Thanks, I know I should dig for it, but I'm working a graveyard shift and I'm burnt, quick thoughts on hard reset, anything I should worry about losing and how do I do it. Don't know why, but seeing it there bugs me. Thanks....zzz

Postscript....Hard reset doesn't work, first thing to pop up was myfaves and the txt msg...eh, guess that's it for now, maybe the next fw will make it go poof.
[G1 Android Development] bitter1:
lol, ok, what part of "I'm not gonna try it" did everyone not get?

It's interesting that the build is RC29 and it's, well. . .not. I was hoping someone could dissect it for fun like they've done with WinMo forever. Caveat Emptor with anything here. Might be interesting to see what's there that isn't somewhere else.

Even as-is, not updating over the air makes me suspicious that there could be differences there we are unaware of. I live in an area with 2G unless I'm in town and given updates happen over night (when I'm trapped on my phone jobwise) makes me getting an OTA kinda rough.
[G1 Android Development] quedijo:
LOL... just saying :p

AWWWWW... They removed the link, even though it didn't work...

You want to send it to me;)
[G1 Android Development] Yos025:
I already manually install mine, but this is what the official t-mobile forum moderatos is saying...

http://forums.t-mobile.com/tmbl/board/message?message.uid=24158#U24158

I guess when my OTA download gets send from t-mobile I will just decline the update...
[G1 Android Development] M9x3mos:
thinking about flashing rc29

hello everyone. Was looking on alot of posts here and wanted to get all your input so I don't end up brinking my phone like I have done many times with my wing in the past.

I found a few posts already on the topic and seems like there are alot of odd end results but hopefully someone has an idea

I found the link from one of the previous posts as:

https://android.clients.google.com/updates/signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip

and I was going to download and flash right away until I read some of the other posts. Was curious if this will show up as a test build under device information or if this is the actual approved update from google for the phone. Alot of the posts I read that state when checking after the update it says for testing. whats that about? since this is coming direct from google i don't think that there will be an issue but I want to make sure that it is ok and that flashing this won't get me stuck on a test build and not able to recieve any further updates from google. any input would be greatly appreciated. Long live XDA!
[G1 Android Development] quedijo:
The link that you posted is the correct one. Your good to go.
[G1 Android Development] neoobs:
They aren't being sent from T-Mobile. They don't have any idea what they are talking about. You won't get the OTA update because your phone is up to date.
[G1 Android Development] gospeed.racer:
I was tired of waiting for the OTA update. I just did it, took about 10 minutes maybe including the download. Very painless, just follow the instructions
[G1 Android Development] Darkrift:
If you read the posts about the test build, you should have seen my warnings in the same threads about the difference in filenames.
[G1 Android Development] M9x3mos:
yeh I read your post and was just a little confused so I wanted to make sure I thank you all greatly for your input. Updating now :-P

ps 16gb sd card formated fat32 and going
[G1 Android Development] RyeBrye:
don't wory about the for-testing

Apparently, the for-testing is just a tag.

Talking to the android people from google, they said that it just means that the build was approved to go on to QA - and it means nothing about what keys you have installed.

You could download the other build and look at the signatures of the files and do a diff on them to verify they are the same - but it's likely that your build is the same except for those strings.
[G1 Android Development] Darkrift:
The way that convo (between ryebrye and the google devs) went, he almost made it sound like that tag was accidentally left in there during manuf. or that device might have skipped QA. I wonder if that could be the case, or if the update added it in there.
[G1 Android Development] SmartBrother90:
problem

neoobs u kno about my problem

i have tried 2 cards

tried BOTH FAT and FAT32

tried update.zip.....update...i even unzipped the file

i have did the whole camera button thing

and still it wont update

i am very lost
[G1 Android Development] gospeed.racer:
I may not be much help, but bear with me here:

1) to be safe, format the sd card inside your G1 using the data cable. (DO NOT REMOVE IT TO FORMAT)

2) grab the update file and name it simply "update". If it says something about "if you change a filenames extension it may become unusable..." then rename it as udpate.zip. This is all dependant on how your PC is set to show extensions. I suspect before the filename may have been update.zip.zip

3) unplug the usb cable and uncheck the usb box.

4)power down and follow the instructions provided in the thread
[G1 Android Development] SmartBrother90:
format it to what exactly
[G1 Android Development] gospeed.racer:
I am personally on fat32 but it may be dependent on your card more than anything. I would try fat32 first.
[G1 Android Development] SmartBrother90:
fat32 and using name update didnt work
[G1 Android Development] gospeed.racer:
you did format the card inside the g1, not via a card reader then, correct? The update is placed at the root of your storage card? You are powered down when you try to start the update process? (I made that mistake:) )

When you say it doesnt update, does it do anything? Remains off?

I cant think of anything else right now....
[G1 Android Development] SmartBrother90:
im gonna try formating to FAT through my phone and ill try all the file names
[G1 Android Development] neoobs:
I went over most things with him and still no luck... I have to beg to ask... what SD card are you using? Size, Brand, any other info?
[G1 Android Development] SmartBrother90:
im using a sandisk 1gb
[G1 Android Development] Darkrift:
One guy on here had the same problem for a while and finally he used the usb link to copy the file to the card instead of a card reader and it worked. If you know how to get to a shell, i recommend you copy the file over then go to a shell and do "ls -l update*" and look at the filename. Make sure it is update.zip (no caps, no extra .zip etc) and then try again. Also give errors or tell us what you are seeing that tells you its not working.
[G1 Android Development] quedijo:
After you're completly shutdown, you are using the "hold down the HOME button and power on the G1" rite?
[G1 Android Development] SmartBrother90:
ok right now...i jus formated to the card FAT through a usb cable

the i renamed the file (update)

i unpluged the usb

unchecked the usbbox

powered down

home+end

alt+l

alt+s

then its says

Instaliing from sdcard...

finding update package...

E: cant mount dev/block/mmcblk0p1

(No such file in directory)

cant moutn sd card:update.zip

installation aborted
[G1 Android Development] Darkrift:
Ok, your problem is the card itself, not the file. It isnt even able to mount the card for some reason. How about this.... Instead of following the steps really fast, after the first boot when you get the exclamation point screen, let it sit there for about a minute before you do the next few steps. Maybe the sd card isnt getting mounted fast enough or soemthing. Also on the emulator, the sdcard is /dev/mmcblk0 i believe. do you have multiple partitions on your card?
[G1 Android Development] SmartBrother90:
nope only the one that created by the format if im correct...ill try that
[G1 Android Development] SmartBrother90:
no that didnt work
[G1 Android Development] Darkrift:
If that did not work, its almost gaurunteed to be an sd card issue. either the card itself, the formatting or the partition. Not sure there is anything else we can help you with. If you wait for the OTA it should work because that appears to be saved in /cache and not /sdcard. Good luck to you though.
[G1 Android Development] SmartBrother90:
quick question

can u name the folders that are on the sdcard
[G1 Android Development] elcanela:
sounds like card itself.....

First off, I tip my hat ( if I was wearing one) to darkrift & other members for their willingness to help & contribute to the g1 community. As stated before, it sounds like the card has ruled itself out as being the culprit. I would bet that if you try another card, (not the one supplied with the phone) it will probably work seamlessly. I experienced the same issues, but I was on the sidelines reading every post, trying to figure out what I was doing wrong. I switched to another card (4GB) and everything went smoothly. Thanks to all the helpful people at XDA DEV's for their hard work.
[G1 Android Development] SmartBrother90:
im starting to think its not a issue with card and i think it HAS TO DO WITH 1Gb cards cause it seems does that had problems with the suplied card used a bigger one and it worked
[G1 Android Development] SmartBrother90:
i think the problem is 1Gb card cause all those who said they switched there card and the card size was biiger..it worked for them
[G1 Android Development] Darkrift:
Being as I do not even own a g1, I am unable to test a lot of this but I do want to know all about this so when I do get mine I can start tweaking it straight off. I used to have a blast changing roms on my Wizard and I know that the G1 will make that seem like changing a theme once its ready. I also know what its like to have a new thing like this not work and nobody knows why because of the lack of information.

I have been reading around and I am 99% sure its the card. I would like someone who was able to get the update working to tell me what their sdcard shows as (mmcblk0 or mmcblk0p1) so I can tell if my idea is correct. For now, I would suggest just trying a different card if you can (go to walmart, buy it, use it, return it) because others have had this SAME issue.
[G1 Android Development] SmartBrother90:
i dont think there is a walmart in brooklyn...lol
[G1 Android Development] gospeed.racer:
Actually....its only 6 miles :p
[G1 Android Development] Darkrift:
note the "Removal requested (No such place)" in the bubble
[G1 Android Development] gospeed.racer:
DOH! I guess he should have been quicker then LMFAO:D
[G1 Android Development] quedijo:
That's interesting... I never knew of that function... I have a butt load of Removal request to do :-P

Did da guy get it to work yet?
[G1 Android Development] Darkrift:
After more reading and testing and reading and talking to some g1 users on freenode's #android it seems that its narrowed down to the bootloader not liking the factory supplied 1GB SD card. As I said, this will not stop OTA updates because those arent stored on the card but still isn't a good thing.
[G1 Android Development] snoslicer8:
Just an FYI:

I did both of my updates (the smart one and the stupid one) from the stock/included 1GB SD card. I wasn't going to format all my music off the 8GB.

The 1GB card worked fine for me.

I had it formatted as FAT (not FAT32), and it worked.
[G1 Android Development] LPChris:
Mine wouldn't work off of the stock 1GB card either. I pulled the 4GB out of my Kaiser (FAT32) and threw it on there and it worked just fine.
[G1 Android Development] SmartBrother90:
i think there is and issue with 1gb cards overall cause it seem like all card over 1gb let the update install
[G1 Android Development] jriley60:
lucky

sounds like i got lucky my 1gb card worked like a charm. :confused:
[G1 Android Development] SmartBrother90:
lucky u unlucky me..lol
[G1 Android Development] neoobs:
Smartbrother can you use a card reader to read the cards that didn't work and let us know how it is partitioned? Go to my computer -> manage -> Disk management -> and look for your device in the top... if it isn't there look down below and you should see "Disk x" (x being a number) It should be unpartitioned. However if you do see it at the top can you tell us the Layout, status, file system, and Type. Thanks.
[G1 Android Development] SmartBrother90:
unfortunately it wont open through the card reader only the phone
[G1 Android Development] neoobs:
Try doing the same through the phone... what does it say? Cause this is weird. This might be the issue.
[G1 Android Development] SmartBrother90:
how do u do that on vista
[G1 Android Development] SmartBrother90:
i right clicked and went to properties

type: removable disk

format: FAT32

the pie graph shows it seprated to used and unused space
[G1 Android Development] Darkrift:
We have already basically figured out the problem in a seperate thread. From what I can tell, there are 2 different models/brands of sd cards being bundled. Sandisk cards seem unaffected (I think) and are formatted properly. The other cards have invalid partition tables and while they are readable on most devices, the compact nature of the bootloader probably didnt have support for them. This means that the invalid partition cards are not being mounted by the bootloader even though they can be mounted by the actual os and other computers (not all, but most)
[G1 Android Development] neoobs:
That is why I am having him check the partition tables.
[G1 Android Development] SmartBrother90:
i only have one partition though
[G1 Android Development] SmartBrother90:
on my 3rd sdcard now hopefully it works
[G1 Android Development] Gadzks:
RC29 Success!

I just did mine per instructions here prior to unlocking with code purchased through vendor from HTC.

Smooth as silk...:D
[G1 Android Development] SmartBrother90:
i called tmobile told them that my phone wasnt reading the sdcards...they gave me 2 choices

1) send it bac...wait til they credit my account and by another one

2) call them bac on the 5th wen the warranty begins....and they will send me one and then ill send mines bac

I CHOSE #2..lol
[G1 Android Development] cjmandrake:
I had a 4 GB card from my Wing. I plugged the phone into my mac, and transferred the update.zip to the SD card, and tried the update. The loader said it was a bad image. I tried using the 1 GB card that came with my G1, and it didn't even recognize the card, since it wasn't a sandisk. I then changed the name of the file to just "update". Still no go.

I booted into Windows XP (intel mac) and formatted the 4GB card right in the G1, put the update.zip on it, and rebooted. It loaded just fine. It formatted as fat32, so it definitely will load on a fat32 card. It might just be that your card is not formatted exactly how the G1 wants it. I copied all my files to a folder on my desktop, did the format, copied them back, and it worked just fine.

It probably won't work if you reformat the non-sandisk 1GB cards that come with the G1.

-Cameron
[G1 Android Development] obijohn:
Well, it's now almost 7PM CST, Nov 2nd, and I STILL haven't gotten my update, so I used the method described in this thread. Worked perfectly.

Just for those interested in the SD card issue, I used a new PNY 4GB card. I left it in the phone, plugged the phone into my Mac, and put the file in the root directory of the SD card with the name of "update.zip". I think the people who are using the name "update" (without the "zip") are using Windows with the default setting of hiding the extension, and for those people who try to name it "update.zip" and get an error, it's really named "update.zip.zip" because of the hidden extension, which is why it's failing for them. Anyway, my $0.02 on that issue.

xda is definitely the best forum for intelligent discussions about the G1. I registered just to post my appreciation to everyone here.
[G1 Android Development] Darkrift:
Thanks for registering. I agree with you about XDA, its been THE place to go for HTC device hacking and modification for years now.
[G1 Android Development] RyeBrye:
Can someone PM me the link to the google URL that has the testing update image? I'm not going to flash it, just curious what it contains and where it comes from to see if that will help us ferret out any other testing images.
[G1 Android Development] SmartBrother90:
would the root folder be

for example

G1:/

if u named the card
[G1 Android Development] neoobs:
It would be the drive letter. For example if it is your F drive it would be

F:/
[G1 Android Development] pof:
same request here :) PM me if you have the link to the testing image!
[G1 Android Development] SmartBrother90:
jus bought a 4g sdcard...hope this works...neoobs pray for me