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.
> 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.
> 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.
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
On Sep 29, 7:06 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> 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.
> 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.
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
On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
> 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
> On Sep 29, 7:06 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> > 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.
> > 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.
> 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
> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
> > 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.
> > > 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.
> > > 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.
> On 30 sep, 16:16, Stefan <sgre...@gmail.com> wrote:
>> 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
>> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
>> > 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.
>> > > 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.
>> > > 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.
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).
On 30 sep, 17:13, Jean-Baptiste Queru <j...@android.com> wrote:
> > On 30 sep, 16:16, Stefan <sgre...@gmail.com> wrote:
> >> 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
> >> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
> >> > 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.
> >> > > 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.
> >> > > 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.
> 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.
> 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).
> On 30 sep, 17:13, Jean-Baptiste Queru <j...@android.com> wrote:
> > 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
> > On Wed, Sep 30, 2009 at 8:05 AM, ivaniclixx <ivanicl...@gmail.com> wrote:
> > > On 30 sep, 16:16, Stefan <sgre...@gmail.com> wrote:
> > >> 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
> > >> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
> > >> > 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.
> > >> > > 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.
> > >> > > 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.
> > 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.
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
On Sep 30, 9:13 am, Jean-Baptiste Queru <j...@android.com> wrote:
> > On 30 sep, 16:16, Stefan <sgre...@gmail.com> wrote:
> >> 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
> >> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
> >> > 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.
> >> > > 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.
> >> > > 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.
> 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.
On Wed, Sep 30, 2009 at 1:05 PM, Mike <michaeldouglaskra...@gmail.com> 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:
> 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
> On Sep 30, 9:13 am, Jean-Baptiste Queru <j...@android.com> wrote:
>> 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
>> On Wed, Sep 30, 2009 at 8:05 AM, ivaniclixx <ivanicl...@gmail.com> wrote:
>> > On 30 sep, 16:16, Stefan <sgre...@gmail.com> wrote:
>> >> 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
>> >> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
>> >> > 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.
>> >> > > 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.
>> >> > > 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.
>> 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.
> 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:
> 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?
> On Sep 30, 9:13 am, Jean-Baptiste Queru <j...@android.com> wrote:
> > 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
> > On Wed, Sep 30, 2009 at 8:05 AM, ivaniclixx <ivanicl...@gmail.com> wrote:
> > > On 30 sep, 16:16, Stefan <sgre...@gmail.com> wrote:
> > >> 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
> > >> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
> > >> > 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.
> > >> > > 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.
> > >> > > 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.
> > 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.
On Wed, Sep 30, 2009 at 2:17 PM, pomacster <pomacs...@gmail.com> wrote:
> 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:
>> 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?
>> - Mike
>> On Sep 30, 9:13 am, Jean-Baptiste Queru <j...@android.com> wrote:
>> > 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
>> > On Wed, Sep 30, 2009 at 8:05 AM, ivaniclixx <ivanicl...@gmail.com> wrote:
>> > > On 30 sep, 16:16, Stefan <sgre...@gmail.com> wrote:
>> > >> 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
>> > >> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
>> > >> > 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.
>> > >> > > 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.
>> > >> > > 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.
>> > 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.
> On Wed, Sep 30, 2009 at 2:17 PM, pomacster <pomacs...@gmail.com> wrote:
> > 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:
> >> 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?
> >> - Mike
> >> On Sep 30, 9:13 am, Jean-Baptiste Queru <j...@android.com> wrote: > >> > 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
> >> > On Wed, Sep 30, 2009 at 8:05 AM, ivaniclixx <ivanicl...@gmail.com> wrote:
> >> > > On 30 sep, 16:16, Stefan <sgre...@gmail.com> wrote: > >> > >> 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
> >> > >> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
> >> > >> > 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.
> >> > >> > > 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.
> >> > >> > > 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.
> >> > 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.
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.
On Wed, Sep 30, 2009 at 4:27 PM, Jean-Baptiste Queru <j...@android.com>wrote:
> HTC told me that they are investigating what might have happened.
> JBQ
> On Wed, Sep 30, 2009 at 2:17 PM, pomacster <pomacs...@gmail.com> wrote:
> > 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:
> >> 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?
> >> - Mike
> >> On Sep 30, 9:13 am, Jean-Baptiste Queru <j...@android.com> wrote:
> >> > 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
> >> > On Wed, Sep 30, 2009 at 8:05 AM, ivaniclixx <ivanicl...@gmail.com>
> wrote:
> >> > > On 30 sep, 16:16, Stefan <sgre...@gmail.com> wrote:
> >> > >> 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
> >> > >> On Sep 30, 12:16 pm, Stefan <sgre...@gmail.com> wrote:
> >> > >> > 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.
> >> > >> > > 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.
> >> > >> > > 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.
> >> > 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.
> 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.
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.
> 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.
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).
> 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.
> On Sep 30, 6:38 pm, fdimeglio <fdimeg...@gmail.com> wrote:
>> 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.
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,
On Sep 30, 9:54 pm, 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.
> (I'm at home and I'm not equipped to test it myself right now).
> > 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.
> > On Sep 30, 6:38 pm, fdimeglio <fdimeg...@gmail.com> wrote:
> >> 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.
> 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.
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
On Oct 1, 11: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.
> (I'm at home and I'm not equipped to test it myself right now).
> > 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.
> > On Sep 30, 6:38 pm, fdimeglio <fdimeg...@gmail.com> wrote:
> >> 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.
> 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.
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".
> On Oct 1, 11: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.
> > (I'm at home and I'm not equipped to test it myself right now).
> > JBQ
> > On Wed, Sep 30, 2009 at 9:38 PM, david.lygagnon
> > > 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.
> > > On Sep 30, 6:38 pm, fdimeglio <fdimeg...@gmail.com> wrote:
> > >> 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.
> > 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.
On Thu, Oct 1, 2009 at 4:02 AM, Andrew <andrewr...@gmail.com> wrote:
> 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
>> On Oct 1, 11: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.
>> > (I'm at home and I'm not equipped to test it myself right now).
>> > JBQ
>> > On Wed, Sep 30, 2009 at 9:38 PM, david.lygagnon
>> > > 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.
>> > > On Sep 30, 6:38 pm, fdimeglio <fdimeg...@gmail.com> wrote:
>> > >> 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.
>> > 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.
> 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).
> > 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.
> > On Sep 30, 6:38 pm, fdimeglio <fdimeg...@gmail.com> wrote:
> >> 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.
> 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.
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
On Sep 30, 9:54 pm, 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.
> (I'm at home and I'm not equipped to test it myself right now).
> > 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.
> > On Sep 30, 6:38 pm, fdimeglio <fdimeg...@gmail.com> wrote:
> >> 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.
> 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.
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.
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: 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
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.
> (I'm at home and I'm not equipped to test it myself right now).
> > 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.
> > On Sep 30, 6:38 pm, fdimeglio <fdimeg...@gmail.com> wrote:
> >> 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.
> 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.
