Flashing froyo on ADP2

[Herb Jellinek]

I've been building Android and flashing it onto my ADP2 (HTC Sapphire,
among other names) with no difficulty up until the release of the
froyo branch.

I am still able to build froyo with no difficulty, but flashing
fails. It seems I need a copy of
ota-radio-2_22_26_07.zip. I didn't find one in <Android>/device/htc/
sapphire nor on the HTC developer site. Where can I find it?

Here's what I did; many thanks for your help.

$ repo sync
...

$ build/envsetup.sh
including device/htc/dream/vendorsetup.sh
including device/htc/passion/vendorsetup.sh
including device/htc/sapphire/vendorsetup.sh
$ lunch full_sapphire-userdebug

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.2
TARGET_PRODUCT=full_sapphire
TARGET_BUILD_VARIANT=userdebug
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
============================================

$ make clean; make -j4
...

$ fastboot -w flashall
--------------------------------------------
Bootloader Version...: 1.33.3007
Baseband Version.....: 2.22.19.26I
Serial Number........: HT9A4LVxyzzy
--------------------------------------------
checking serialno... OKAY
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... FAILED

Device version-baseband is '2.22.19.26I'.
Update requires '2.22.26.07'.

$

[Jean-Baptiste Queru]

There's a file "board-info-unsupported.txt" in device/htc/sapphire (in
master only), which you can copy as board-info.txt in the same
directory, and which will let you flash on top of the donut radio (run
"make" so that it's taken into account).

The same thing also applies to dream (same donut radio) and passion
(with the eclair radios).

JBQ

> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>

--
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.

[Herb Jellinek]

Thanks, JBQ. That solved that problem.

However, the donut radio seems to have a large hole: the phone doesn't
see the mobile network, Wi-Fi networks, and only 0-1 Bluetooth devices
- usually 0 - of the 5 or more discoverable devices scattered around.
I have attempted to enable Bluetooth and Wi-Fi in Settings.

Here are some relevant log entries:

I/Use2GOnlyCheckBoxPreference( 218): get preferred network type,
exception=com.android.internal.telephony.CommandException:
RADIO_NOT_AVAILABLE

E/wlan_loader( 624): Cannot open firmware file </system/etc/wifi/
Fw1251r1c.bin>: No such file or directory

(Not sure this is still the right group to post this to. Please let
me know if not.)

Herb

[ntremble]

Hi Herb,

I'm new to Android so excuse me if this is obvious stuff.

The first time I built 2.2 for my ADP2 I had no radio either so I
restored to 1.6. I then realised I needed the proprietary files from
the phone, most of which I obtained by running device/htc/sapphire/
extract_files.sh. Fw1251r1c.bin was one of those copied from the
phone, and make copies it straight through to the out directory. Did
you do this or is the system just not finding the file?

Having done that I'm now having trouble with libGLES_qcom.so and a
couple of others though; they are not present on my ADP2 but the make
insists they are required and aborts. I'm trying to find out how to
resolve that.

Neil

[Herb Jellinek]

Thanks, Neil. Yes, all of the stuff under vendor/ got clobbered in my
move from eclair to froyo. I reconstructed things such that I could
run extract_files.sh again and then ran make again.

My build broke due to missing libGLES_qcom.so, liboemcamera.so, and
liblvmxipc.so, which I'm assuming was your experience too. I managed
to dig up copies of those files. Now my build is complaining about

target Prelink: libsystem_server (out/target/product/sapphire/symbols/
system/lib/libsystem_server.so)
out/target/product/sapphire/obj/lib/libcamera.so: undefined reference
to `android::Mutex::Mutex()'
out/target/product/sapphire/obj/lib/libcamera.so: undefined reference
to `android::Mutex::~Mutex()'
...
out/target/product/sapphire/obj/lib/libcamera.so: undefined reference
to `android::Mutex::lock()'
out/target/product/sapphire/obj/lib/libcamera.so: undefined reference
to `android::Condition::Condition()'
collect2: ld returned 1 exit status

Any hints, anyone?

[袁嵩 Yuan Song]

I have the same problems with missing libGLES_qcom.so, liboemcamera.so
and liblvmxipc.so when I try building for dream. I succeeded in
finding libGLES_qcom.so from image provided by CyanogenMod for Dream/
Magic, but not the other files.

[Bryce Walter]

I'm having the same issue as you Herb. When searching the dir that it
is trying to pull files from, there is only 3 files. Is there a way to
have it skip this step, and I can manually push the camera.so files?

As for the 3 files it was unable to extract from my phone, I found
those files on the 2.2 SDK, as well as on XDA. I have a T-Mobile MT3G,
which is the ADP2.
I think this was due to my running the "make -j4" command last night,
and it getting all the way through the build up until it looked for
the sapphire proprietary files and failed on finding those 3. I am
going to try to resync the repo tonight, and give it another shot. (of
course backing up those missing files 1st)

[liuyu]

You can find liblvmxipc.so in SDK2.2's emulator, but I'm not sure
whether it can be used on a real phone.

[ntremble]

Herb,

I've been through the same process as you, with the same result. As
far as I can tell the undefined references in libcamera.so are the
result of using the 1.6 libcamera.so file with a 2.2 build. If this is
the case we need the correct versions of the proprietary files, and
they do not exist on our devices.

I tried pulling libcamera.so from the Cyanogen 6.0 alpha 1 build
(Nexus One) . That let the build complete, but when I flashed the
result to the phone it never proceeded past the IO 2009 screen. So I
restored from backup.

I tried asking HTC if they were intending to provide a straight 2.2
build for the ion for developer use. Their response was:

"Hi Neil, Thank you for your reply. With regard to Android 2.2
(FROYO), I want to inform you that we are actually considering an
upgrade for some models of our phones to FROYO, but we are still
analyzing the impact this will have on the user experience. We will
announce a full list of phones and dates once we are closer to
launching the upgrades. Currently, we are working closely with Google
and our other partners to ensure we have the earliest access to
everything we need to provide a complete and solid Sense experience on
FROYO. For future updates, please visit our website at http://www.htc.com/.
Please feel free to contact us again if you have any future questions.
You may give us a call at 1300 482 482. Our business hours are from
8:00 am to 8:00 pm SYDNEY Time, from Mondays to Saturdays and closed
on Public Holidays. Thank you and have a great day!"

The ticket is still open so I'll try asking for just the files I need
and see how that goes.

It appears that unless HTC or Google come to the party with the
correct versions these files we will be stuck on 1.6.

So much for the Google statement that 2.2 can be built for the ADP2
out of the box. Sure, it builds, and even runs on the phone. I've done
it. But without the proprietary files the phone does not work as a
phone, so it's useless for any real development testing.

If anyone can point to a source of suitable files we'd be grateful.

Neil