Wrong 1.6 images on HTC's site

[Jean-Baptiste Queru]

The system images uploaded on HTC's site aren't correct (they were
signed with test keys instead of production keys). We'll be working
with HTC to upload the correct ones as soon as possible.

If you've flashed without doing a factory reset, none of the updated
system applications will be able to access their data. You'll need to
do a factory reset (both now and after a corrected image is
available).

I strongly recommend that you avoid flashing 1.6 until we have the
proper files available.

JBQ

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[ivaniclixx]

Too late for me :-(

[Stefan]

Just in case someone from HTC reads this:
The file checksum has changed from af5e4e1121bbb9828adfe5ffe85c501d to
a06a3d24ff4cbe5c81317e41891e6965
on HTC's site, but the file hasn't changed yet.

Stefan

[Stefan]

Just to be more precise, fro signed-dream_devphone_userdebug-
img-14721.zip the md5sum displayed
on the WEB page does not match the md5sum of the downloaded file. It
still has the old checksum.

Stefan

[ivaniclixx]

MD5 (signed-dream_devphone_userdebug-ota-14721.zip) =
acd9447fc7178f7048788096ba7f1486

( 45M 30 sep 01:07 )

[Jean-Baptiste Queru]

I believe that the files themselves as available from HTC's servers
are still the wrong ones.

md5sums af5e4e1121bbb9828adfe5ffe85c501d and
acd9447fc7178f7048788096ba7f1486 match versions of the images that
weren't properly signed.

JBQ

[ivaniclixx]

I had no other problem, but every time the system boots,
com.google.android.partnersetup crashes because of write permissions
or something related (says the logs).

[Andy]

I'm seeing the same thing after upgrading to 1.6, though haven't
looked through logs specifically.

[Mike]

I put the 1.6 firmware on my G1 yesterday and it definitely was the
test-keys version (as indicated in the About->Build number section of
the phone settings)

When I looked just now, here is what I saw on the HTC site:

Android 1.6
Radio Image ota-
radio-2_22_19_26I.zip 9181622
aeecdb49b74a0d4bb67f9d8af70c1889
System Image signed-dream_devphone_userdebug-img-14721.zip
40119463 a06a3d24ff4cbe5c81317e41891e6965
Recovery Image signed-dream_devphone_userdebug-ota-14721.zip
47247895 b3e12b004c155761a10b1a848288e0c3

These look new. So... now that I have the firmware with the test-
keys, is there anything special I need to do to flash the production
keys firmware to my phone?

- Mike

[Jean-Baptiste Queru]

When I checked a few hours ago, the web page had been updated, but the
files weren't. HTC told me they were looking into it.

JBQ

[pomacster]

On ons, 2009-09-30 at 13:05 -0700, Mike wrote:
> I put the 1.6 firmware on my G1 yesterday and it definitely was the
> test-keys version (as indicated in the About->Build number section of
> the phone settings)
>
> When I looked just now, here is what I saw on the HTC site:
>
> Android 1.6
> Radio Image ota-
> radio-2_22_19_26I.zip 9181622
> aeecdb49b74a0d4bb67f9d8af70c1889
> System Image signed-dream_devphone_userdebug-img-14721.zip
> 40119463 a06a3d24ff4cbe5c81317e41891e6965
> Recovery Image signed-dream_devphone_userdebug-ota-14721.zip
> 47247895 b3e12b004c155761a10b1a848288e0c3
>
> These look new. So... now that I have the firmware with the test-
> keys, is there anything special I need to do to flash the production
> keys firmware to my phone?

The really fun bit is that if you re-download them then you have:
af5e4e1121bbb9828adfe5ffe85c501d
signed-dream_devphone_userdebug-img-14721.zip

and
acd9447fc7178f7048788096ba7f1486
signed-dream_devphone_userdebug-ota-14721.zip

Which is still the wrong versions!

Just as a side note, i *never* downloaded the other system image so it
can't be a cache or anything.

Could someone please just fix this and put it somewhere where you can
actually download with another useful tool like say wget or like curl?

[Jean-Baptiste Queru]

HTC told me that they are investigating what might have happened.

JBQ

[pomacster]

On ons, 2009-09-30 at 14:27 -0700, Jean-Baptiste Queru wrote:
> HTC told me that they are investigating what might have happened.

Thanks and really thanks for the quick reply =)

[<>]

Ugh... now I'm seeing android.process.acore crashing constantly. This began after attempting to open Gmail (which worked), then the acore errors started occurring.

[fdimeglio]

Those firmware work, but you need to wipe your user data partition
first. I have done it on my Google I/O phone and I am pretty happy
about it.

As JBQ said that's not great because those firmwares use the test keys
instead of the production keys and that you will need to wipe out
again when they are correctly released.

One way to go around this, is to make a user partition backup thru
nandroid that you will be able to restore later.

Fabrice

[david.lygagnon]

I just download the recovery image and the checksum gives me this :

b3e12b004c155761a10b1a848288e0c3
signed-dream_devphone_userdebug-ota-14721.zip

which is the same as the one posted on the website. So I guess now the
right versions have been updated.

I will try reinstalling now, doing a factory reset.

[Jean-Baptiste Queru]

I'm getting some hints that the correct images might be there.

Once you flash, can you go to settings -> about phone and check which
version is mentioned all the way at the bottom
(dream_devphone-userdebug DRC83), please let me know whether it says
"test-keys" or some other value there.

(I'm at home and I'm not equipped to test it myself right now).

JBQ

[david.lygagnon]

Has anyone tried the new radio?

When I install it, the installation gets aborted...
I have the correct checksum, and I tried the process a couple of
times, but without success... I have also done a factory reset and
wiped cache.

This is my checksum:
aeecdb49b74a0d4bb67f9d8af70c1889
ota-radio-2_22_19_26I.zip

Cheers,

[Jay]

I flashed boot.img and system.img from
a06a3d24ff4cbe5c81317e41891e6965 signed-dream_devphone_userdebug-
img-14721.zip. The version says 1.6 DRC83 14721 test-keys.

Thanks,
Jay

[Andrew]

On Oct 1, 8:54 am, Jay <pathomp...@gmail.com> wrote:
> I flashed boot.img and system.img from
> a06a3d24ff4cbe5c81317e41891e6965 signed-dream_devphone_userdebug-
> img-14721.zip. The version says 1.6 DRC83 14721 test-keys.

I flashed signed-dream_devphone_userdebug-ota-14721.zip which I
downloaded today so now I am running Android 1.6 but still "DRC83
14721 test-keys".

/Andrew

[Jean-Baptiste Queru]

Hmmm, that still doesn't sound right. I'm gonna have to look into it
deeper before I send the "all clear".

JBQ

[Stefan]

$ md5sum /opt/android/images/signed-dream_devphone_userdebug-
img-14721.zip
a06a3d24ff4cbe5c81317e41891e6965 /opt/android/images/signed-
dream_devphone_userdebug-img-14721.zip
$ bin/fastboot update /opt/android/images/signed-
dream_devphone_userdebug-img-14721.zip
....
It still says "dream_devphone-userdebug 1.6 DRC83 14721 test-keys" on
the About phone sceen.

Stefan

[Shane]

I have successfully updated to the image from HTC's site. I
downloaded it about 10:30 pm PST. Everything worked great and I am
now running 1.6 on my Dev phone G1.

It stills says "test-keys".

Shane

[Zap]

On Oct 1, 6:54 am, Jean-Baptiste Queru <j...@android.com> wrote:
> I'm getting some hints that the correct images might be there.
>
> Once you flash, can you go to settings -> about phone and check which
> version is mentioned all the way at the bottom
> (dream_devphone-userdebug DRC83), please let me know whether it says
> "test-keys" or some other value there.

Odd, I downloaded signed-dream_devphone_userdebug-ota-14721.zip
(md5sum: acd9447fc7178f7048788096ba7f1486) at 2009-09-29 15:36
(European time) and
apart from the mentioned startup message everything appears to work
beautifully - a
lot faster than before overall. Mine says test-keys.

I think I'll stick to this one for now...

Best / Jonas

[John Doe]

Flashed signed-dream_devphone_userdebug-img-14721.zip with checksum
a06a3d24ff4cbe5c81317e41891e6965, About phone, Build number is
dream_devphone-userdebug 1.6 DRC83 14721 test-keys. At startup,
com.android.setupwizard still crashes. Calendar/Market/etc do not
crash immediately anymore, but start google account signin, which
crashes when it tries to really sign in:

java.lang.SecurityException: caller pid XXX uid 10013 lacks
com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD

java.lang.SecurityException: Permission Denial writing
com.google.android.providers.settings.GoogleSettingsProvider uri
content://com.google.settings/partner from pid=XXX, uid=10065 requires
com.google.android.providers.settings.permission.WRITE_GSETTINGS

java.lang.RuntimeException: Unable to start receiver
com.google.android.partnersetup.GooglePartnerSetup:
java.lang.SecurityException (the same exception as above, complaining
about WRITE_GSETTINGS)

java.lang.RuntimeException: Unable to start receiver
com.google.android.partnersetup.GooglePartnerSetup:
java.lang.IllegalArgumentException: Unknown URL content://com.google.settings/partner

[MiGri]

Same here. Abort of the Installation after approx. 3/4 of the progress
bar.

But do we really need to update the radio?
Its the same name and checksum like the radio for 1.5 (which I already
have on my adp1).

[daveco]

Yeah, I got same as Jay. I downloaded the new signed-
dream_devphone_userdebug-ota-14721.zip
(b3e12b004c155761a10b1a848288e0c3), and when i applied it to the
phone, it still says

dream_devphone-userdebug 1.6 DRC83 14721 test-keys

This is definitely a new file from the HTC site. The original one I
downloaded had checksum acd9447fc7178f7048788096ba7f1486.

The ota-radio-2_22_19_26I.zip file hasn't changed, which I presume is
why it won't install.

cheers,
Dave

[Jean-Baptiste Queru]

There's no need to update the radio image between 1.5 and 1.6, it's
the exact same one.

JBQ

[Teck Choon Giam]

Mine is dream_devphone-userdebug 1.6 DRC83 14721 test-keys

I modified to include my self compiled kernel and wlan.ko. I also
renamed the following:

In order to disable first boot up to install stock 1.6 recovery to my
ADP1, I done the following:

/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.disabled
/system/recovery-from-boot.p /system/recovery-from-boot.p.disabled

Removed the line related to update radio.img:
/META-INF/com/google/android/updater-script
/META-INF/com/google/android/update-script

Removed the line "set_perm 0 0 0544 SYSTEM:etc/install-recovery.sh" in
/META-INF/com/google/android/update-script

Lastly check_preq line in /META-INF/com/google/android/updater-script
or /META-INF/com/google/android/update-script cannot remember :p

Partial logcat below which previous firmware 1.6 caused
com.google.android.partnersetup to force close with keystone
read/write/initialize error for /data/misc/keystone if I remember
correctly without wipe. Now it isn't and I tried with few reboots and
everything looks fine. So from the logcat it looks like
com.google.android.partnersetup is being uninstalled after the first
reboot of the upgrade?

D/dalvikvm( 89): GC freed 3463 objects / 170168 bytes in 338ms
D/dalvikvm( 236): GC freed 1738 objects / 98712 bytes in 643ms
I/ContactsProvider( 236): Processed 139 contacts.
D/HomeLoaders( 236): load applications
D/HomeLoaders( 236): loading user items
D/HomeLoaders( 236): --> starting workspace loader
D/HomeLoaders( 236): ----> running workspace loader (1)
I/ActivityManager( 89): Stopping service:
com.android.providers.downloads/.DownloadService
D/LauncherProvider( 236): onUpgrade triggered
D/ActivityManager( 89): Uninstalling process
com.google.android.partnersetup
D/ActivityManager( 89): Force removing process
ProcessRecord{4389fc78 327:com.google.android.partnersetup/10045}
(com.google.android.partnersetup/10045)
I/Process ( 89): Sending signal. PID: 327 SIG: 9
D/HomeLoaders( 236): aborting loaders
D/ActivityManager( 89): Received spurious death notification for
thread android.os.BinderProxy@439285a8
W/ResourceType( 89): No package identifier when getting value for
resource number 0x7f060000
D/HomeLoaders( 236): --> aborting workspace loader
W/ResourceType( 89): No package identifier when getting value for
resource number 0x7f060001
D/GpsLocationProvider( 89): state: CONNECTED apnName: e-ideas
reason: gprsAttached
D/HomeLoaders( 236): ----> worskpace loader was stopped
D/GpsLocationProvider( 89): state: DISCONNECTED apnName: e-ideas
reason: dataDisabled
D/HomeLoaders( 236): load applications
D/HomeLoaders( 236): loading user items

Thanks.

Kindest regards,
Giam Teck Choon

[Jean-Baptiste Queru]

I made a small mistake in identifying the correct build - both the
"wrong" one and the "correct" one say test-keys. Sorry about that
confusion.

See http://groups.google.com/group/Android-DevPhone-Updating/browse_thread/thread/5b7c52f40d91d2ef
for more details.

JBQ