New ADP1 Update – Official With Google Voice And More!

Posted on February 10th, 2009 in Android Hacking, Android News by Disconnect  Tagged , , , , , , ,

Thanks to eagle-eyed posters over on XDA-Dev, we have an official ADP1.1 update.zip image! (Update: Now there is a version with no device/version checks. Enjoy!)

Update 2: Now we know what it is!

Changelog is, as always, unavailable. First impressions are that it is exactly like you would expect the ADP1 version of RC33 to be – Latitude, voice search, etc but no myfaves or mp3 store.

Update 2: Working with a goog on IRC, we figured out what this is. :) The “adp 1.1″ image that was leaked to me last month is actually the stock system image from the Google holiday-bonus phone.  (With a very early, not-necessarily-complete SDK 1.1 image).  And this update brings all the new, fun features along, plus a fastboot-enabled tricolor bootloader. (So if you go into fastboot mode and see the rainbow, don’t panic, Just pretend it is skateboards and proceed as normal..)

Get it while it’s hot, straight from the horse’s mouth :)

Holiday Phone 1.1 Image (was ADP1.1) v1.0 (1513 downloads)
* Update.zip Format * RC33-equiv * Google Voice Search * Google Latitude * Signed by Google*

If you don’t have an ADP1 with stock firmware AND stock bootloader, you want this one: (Update: If you don’t have a “holiday dream” with stock firmware/bootloader, you want this one:)

Holiday Phone 1.1 Image (No Device Checks!) (was ADP 1.1) v1.0 (1928 downloads)
* Update.zip Format * Does NO device/bootloader checks * RC33-equiv * Google Voice Search * Google Latitude




35 Responses to 'New ADP1 Update – Official With Google Voice And More!'

Subscribe to comments with RSS

  1.    bsander said,

    on February 10th, 2009 at 10:08 am

    Just rename it to update.zip, copy to sd card and reboot? Or do I have to do something more?

    Reply

  2.    Disconnect said,

    on February 10th, 2009 at 10:35 am

    Thats all there is to it. Just rename, reboot while holding down ‘home’ and hit alt-s (or alt-l alt-s if you are on stock adp1 firmware – jf’s defaults to logging on, so alt-l is unnecessary.)

    Reply

  3.    Morten said,

    on February 10th, 2009 at 10:52 am

    Does this image contain German localization? Would be great… American formatting of German phone numbers is a little odd ;)…

    Reply

  4.    albemuth said,

    on February 10th, 2009 at 11:06 am

    What makes this ‘official’ could you provide a link to the original source?

    Reply

  5.    Disconnect said,

    on February 10th, 2009 at 11:58 am

    if you click the first link, you’ll notice thats where it sends you.

    Reply

  6.    profediego said,

    on February 10th, 2009 at 12:17 pm

    if i install this image into my g1 dev phone, the market continue to work? everything will be working fine??
    And if i want to go back to previous build, can i do it? How?

    Thanks.

    Reply

  7.    springroll said,

    on February 10th, 2009 at 2:57 pm

    is the root access still available with this update?

    Reply

  8.    Marc said,

    on February 10th, 2009 at 4:46 pm

    I am getting an error when updating from JF1.41 on ADP1:

    Failure at line 4:
    assert getprop(“ro.bootloader”)
    …..
    Installation aborted.

    Any idea?

    Reply

  9.    profediego said,

    on February 10th, 2009 at 5:44 pm

    Got an
    E:failure at line 4:
    assert getprop(“ro.bootloader”) == “0.95.0000″
    Installation aborted.

    Somebody help here, thanks.
    regards.

    Reply

  10.    Marc said,

    on February 10th, 2009 at 6:15 pm

    prefediego, just get the 2nd link (no device checks). I need to do a wipe to make it work. After installation, ‘adb devices’ can’t seem to detect the device anymore.

    Reply

  11.    Karolis Pocius said,

    on February 10th, 2009 at 8:00 pm

    So what about root? Will I still have it after upgrading from JFv1.41 to this?

    Reply

  12.    ericsk said,

    on February 10th, 2009 at 9:04 pm

    @Marc,
    Go to Settings > Applications > Development and turn on the “USB debugging”, then you can see the device in `adb devices`

    Reply

  13.    in2code said,

    on February 10th, 2009 at 9:48 pm

    When I try the 2nd link, I get E:Corrupt file:
    system/fonts/DroidSansFallback.ttf
    and then it aborts, any thoughts anyone? I also, tried the 1st link with adp v1.0 and i get the same error as above, “ro.bootloader”.
    Thanks.

    Reply

  14.    profediego said,

    on February 11th, 2009 at 9:06 am

    What is ‘adb devices’?
    Marc, you were rigth secon link works just fine even without a hard reset, i just have to wait or the phone, seems it reboot like 3 o more times. At the end it was ok.

    Thanks

    Reply

  15.    okänd said,

    on February 11th, 2009 at 12:09 pm

    It gave me the assert getprop(”ro.bootloader”) == “0.95.0000″ error too. The strange thing is that I haven’t even installed anything else than what was on the phone before so it should have worked. It was just as it was from the package except I had some market apps on there.

    I tried doing a wipe and then installing the update but that didn’t help.

    Reply

  16.    android fan said,

    on February 11th, 2009 at 12:45 pm

    tried the second link and everything worked well except Google Latitude, I thought it comes with the maps

    do we need to do something ?

    Reply

  17.    Jack said,

    on February 11th, 2009 at 1:53 pm

    I got this OTA on my ADP1 via my JF 1.41 rom. I said what the hell and let it update, which (of course) removed my music store, multi-touch and autorotate.

    It took two steps, reflashed the radio then the firmware.

    No ill effects so far.

    Reply

  18.    Chuck said,

    on February 11th, 2009 at 3:46 pm

    I’ve got a stock ADP1 with stock firmware and bootloader. I’m getting the assert “ro.bootloader” error when trying to use the update from Google. Why would this update check to see that you have the original T-Mobile G1 bootloader instead of the engineering bootloader?

    http://forum.xda-developers.com/showthread.php?t=455860

    That doesn’t make any sense.

    Reply

  19.    cpedia said,

    on February 12th, 2009 at 5:00 am

    I met the same problem. The update check the bootloader to be .95.0000\, but my bootloader is .95.3000\.

    Reply

    iein Reply:

    @cpedia, here is the link to the bootloader you need that is part of the holiday update

    https://android.clients.google.com/updates/hboot-0.95.0000.zip

    Reply

  20.    Maurizio said,

    on February 12th, 2009 at 5:10 pm

    Hi,
    I have received it yesterday from 2 pop up messages on my phone.
    The first one was for the bootloader and the second one was for the system.
    Fastboot work, but the bootloader is very strange because it has the same colours of the G1 bootloader, but with fastboot activated.
    From what I can red not all ADP1 recived the update from the 2 pop up messages, isn’t?

    Reply

  21.    iein said,

    on February 13th, 2009 at 1:35 am

    Maurizo – you are correct about the bootloader. It does have fastboot, but looks exactly like the original one. The like to get it if you are looking for it is:

    https://android.clients.google.com/updates/hboot-0.95.0000.zip

    Reply

  22.    McLin said,

    on February 17th, 2009 at 4:58 pm

    It says unpacking and abort with not sign???

    German G1 with RC33

    Reply

    Disconnect Reply:

    @McLin, What would lead you to believe this works on a G1 with tmobile software? It says “adp1″ all over it.

    Reply

  23.    McLin said,

    on February 17th, 2009 at 5:09 pm

    Yes but “No Device Check”

    Reply

    Disconnect Reply:

    @McLin, that doesn’t magically make it signed with the tmobile keys.

    Reply

  24.    Deaj said,

    on February 17th, 2009 at 7:15 pm

    Downloaded the official Google version (1st link), renamed, copied across, held home button while rebooting then Alt S (all after downloading the other boot zip & inserting those files into update.zip, replacing the other versions of the same file) but can’t install due to ‘no signature file. Any ideas? (Am I doing it all wrong?)

    Reply

  25.    McLin said,

    on February 18th, 2009 at 5:44 am

    Can anybody sign it for G1 T-Mobile pls?

    Reply

    Disconnect Reply:

    @McLin, The whole POINT of signatures is that, for retail devices, only google/tmobile can do that. (Tech note: it looks like the actual key is held by HTC.) If you have a US/UK g1, you can downgrade to rc29, flash a new recovery image that uses the test keys, and then use these updates (signed with the same test keys.)

    Reply

    McLin Reply:

    @Disconnect,
    No from Germany. And when I buy a device with Linux on it, I will have root, its my Hardware, I paid for that…

    Reply

    Disconnect Reply:

    @McLin, Don’t argue with me. Seriously. Go talk to tmobile or whomever you bought it from. Not my problem, in any way shape or form. I have less than nothing to do with the closed source mess you have on your phone.

  26.    McLin said,

    on February 18th, 2009 at 2:07 pm

    This was not against you, that was generally meant

    Reply

  27.    McLin said,

    on February 23rd, 2009 at 8:53 am

    Dev phones will ever have root access, right?

    Reply

  28.    jon anderson said,

    on March 18th, 2009 at 10:32 am

    This page needs updating!!!

    Reply

  29.    jon anderson said,

    on March 21st, 2009 at 3:57 pm

    I’ve discovered the real meaning of the ‘fractal-like’ design etched into the Dev phone!!
    Where shall i reveal it??$34

    Reply

Post a comment