Cannot downgrade or *gasp* flash CyanogenMod! :-)

12 views
Skip to first unread message

Andrew

unread,
Sep 30, 2009, 1:56:33 PM9/30/09
to Android-DevPhone-Updating
Now that I've installed 1.6 which contained the wrong keys and JBQ
tells us that we probably need to wipe our devices (and 1.6 probably
is the last version for the APD1 anyways) I thought I would take the
step and try out CyanogenMod (I know the controversy and think that
everything will be sorted out eventually) - but I couldn't install the
ROM nor Android 1.5 from HTC.

I had no problems in upgrading from 1.0 til 1.1 and from 1.1 to 1.5
and from 1.5 to 1.6 but now I am stuck!?!

When I try to install update.zip from the flash card CyanogenMod and
Android 1.5 just complains that the installation failed (Android 1.5
are missing 5 signatures!?!). :-(

/Andrew

Andrew

unread,
Oct 1, 2009, 6:57:38 AM10/1/09
to Android-DevPhone-Updating


On Sep 30, 7:56 pm, Andrew <andrewr...@gmail.com> wrote:
> When I try to install update.zip from the flash card CyanogenMod and
> Android 1.5 just complains that the installation failed (Android 1.5
> are missing 5 signatures!?!). :-(

Ah, I swapped the System Image and the Recovery Image so now I am
running Android 1.6 but still "DRC83 14721 test-keys" - even though
the System image was different from the one I downloaded yesterday!?!

/Andrew

lbcoder

unread,
Oct 2, 2009, 10:55:40 AM10/2/09
to Android-DevPhone-Updating
You're going to need to use fastboot.

honcheng

unread,
Oct 2, 2009, 10:07:56 PM10/2/09
to Android-DevPhone-Updating

I have the same issue with my ADP. Right now I still have 1.6
installed. Can I just use fastboot to flash cyanogenmod directly?

Or do I have to flash hard SPL doing it?

I posted in another thread that I also get this error.
E:can't open /cache/recovery/command
not sure If it is related to y I can't flash

Jean-Baptiste Queru

unread,
Oct 2, 2009, 10:24:03 PM10/2/09
to Android-DevP...@googlegroups.com
If you still have the original 0.95.3000 bootoader, it can flash all
the relevant partitions over fastboot, both the official images and
your home-built ones.

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.

Jakob

unread,
Oct 3, 2009, 9:36:01 AM10/3/09
to Android-DevPhone-Updating
I had the exact same experience. I wanted to go back to Cyanogenmod
4.1.11.1 because of the
possibility to install apps on the sd card and for the tether app (and
for the 5 home screens).

The only way I could find was to start all over by installing RC29 and
following this guide:

http://code.google.com/p/android-roms/wiki/Get_Root

When I got to the "Rooting your phone" page I used the recovery image
found here:

http://www.cyanogenmod.com/downloads/recovery-image

And used that recovery image (instead of the one in the guide) in the
following:

mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img

Remember to update the radio software before installing the
cyanogenmod image as mentioned
(still in the same guide) here:

http://code.google.com/p/android-roms/wiki/Install_Custom_ROM

Hope this helps. I got back on cyanogenmod after doing the above.

Jakob

honcheng

unread,
Oct 3, 2009, 10:12:17 AM10/3/09
to Android-DevPhone-Updating
I tried using fastboot to flash /MLIGN-HeroV2.1.5.zip
and I got this error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

Is there anyway I can get back to installing custom firmware normally
e.g. just put update.zip into my sdcard and flash them. I can no
longer do that. Everything fails. Mine is an ADP

Jean-Baptiste Queru

unread,
Oct 3, 2009, 10:19:50 AM10/3/09
to Android-DevP...@googlegroups.com
If you have a fastboot image that doesn't contain all the necessary
configuration files (or that doesn't pass the sanity-checks), you can
bypass the tests by extracting the individual filesystem images (e.g.
boot.img, recovery.img and system.img) and flashing them one by one:

fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img

JBQ

honcheng

unread,
Oct 3, 2009, 10:54:50 AM10/3/09
to Android-DevP...@googlegroups.com
I unzip the file but I can only fine boot.img
system is a folder, not an img
and there isn't a recovery.img as well

The structure after unzip is something like this
-boot.img
-META-INF (folder)
-system (folder)

honcheng

unread,
Oct 3, 2009, 11:00:01 AM10/3/09
to Android-DevP...@googlegroups.com
SInce this doesn't work, I tried using update.zip as well, and installation was aborted. 

Is there something very wrong with my phone after flashing that wrong 1.6.?

honcheng

unread,
Oct 3, 2009, 12:22:03 PM10/3/09
to Android-DevPhone-Updating
Looks like the problem is related to the error I got after all

E:can't open /cache/recovery/command

To fix this,
I reflash the recovery image

fastboot flash recovery recovery.img
from wget http://n0rp.chemlab.org/android/cm-recovery-1.3.img

now I can flash any ROM without problem. Thanks

On Oct 3, 11:00 pm, honcheng <honch...@gmail.com> wrote:
> SInce this doesn't work, I tried using update.zip as well, and installation
> was aborted.
> Is there something very wrong with my phone after flashing that wrong 1.6.?
>
>
>
> On Sat, Oct 3, 2009 at 10:54 PM, honcheng <honch...@gmail.com> wrote:
> > I unzip the file but I can only fine boot.imgsystem is a folder, not an
> > img
> > and there isn't a recovery.img as well
>
> > The structure after unzip is something like this
> > -boot.img
> > -META-INF (folder)
> > -system (folder)
>
> > On Sat, Oct 3, 2009 at 10:19 PM, Jean-Baptiste Queru <j...@android.com>wrote:
>
> >> If you have a fastboot image that doesn't contain all the necessary
> >> configuration files (or that doesn't pass the sanity-checks), you can
> >> bypass the tests by extracting the individual filesystem images (e.g.
> >> boot.img, recovery.img and system.img) and flashing them one by one:
>
> >> fastboot flash boot boot.img
> >> fastboot flash recovery recovery.img
> >> fastboot flash system system.img
>
> >> JBQ
>
Reply all
Reply to author
Forward
0 new messages