[myTouch 3G, Magic Android Development] hause:
I don't recommend my procedure for a device that still is in a good condition.

You can give it a try if your device is dead and you have nothing to loose.

My 32B is totally messed up since I flashed the wrong (a 32A) rom and on it.

After that I was able to flash a newer 32B SPL and 63% of a 32B radio with the goldcard method.

Now the goldcard method no longer works for me.

My magic shows 32B but no 32B recovery or rom works on it.

You will need:

recovery-RA-sapphire-v1.5.2G.img (32B)
recovery-RA-sapphire-v1.5.2H.img (32A)
daldroid-htcmagic1-signed.zip

If you have a serial-console for your magic then fire it up before the procedure.

If your magic is in the "blue-led-mode" (ARM9_BOOT_MODE1) you will need a serial-console to bring it in ARM9_BOOT_MODE0.

1. Copy daldroid-htcmagic1-signed.zip on a fat32-partition on your sdcard and put it in your magic.

2. Connect the magic to your pc's usb (and serial-console if you have).

3. Remove battery.

4. Now you have to boot your device into FASTBOOT mode.

If you had a failed rom-upgrade before and you still got stuck in the RUU USB:

Insert the battery and you should see RUU USB on the display.

If the RUU USB stuck is not the problem, try:

Press VOL-DN or HOME and insert the battery. Maybe FASTBOOT boots. Maybe HBOOT boots and you can get into FASTBOOT USB.

If you can't get into RUU USB/FASTBOOT USB, stop here.

Maybe the ARM9_BOOT_MODE is set wrong. Then you will need a serial-console to fix this first. For me worked ARM9_BOOT_MODE0 ("setboot 0").

5. Try out if one of the recovery-RA images boots. First the one that is for your board. If it does not boot, try the other one.

./fastboot boot recovery-RA-sapphire-v1.5.2H.img

6. If one of the recovery-RA images boots up fully, wait 10 seconds and try out if you can access the device via adb shell.

./adb -d shell

8. If you get a shell try out if you can mount and access the sdcard on the device.

mount /sdcard
ls /sdcard

If you can't see daldroid-htcmagic1-signed.zip, stop here.

Maybe your magics sdcard reader is messed up.

9. Remove and insert the battery again, enter RUU USB/FASTBOOT again.

10. Erase the nand partitions

./fastboot erase cache
./fastboot erase userdata

If you get a failure like 'remote not allow', stop here. Otherwise go on.

./fastboot erase boot
./fastboot erase system

If you have a serial console you can see if your magics nand flash is good.

Mine is not. I have a bad block on the end of my system partition.

This keeps me from flashing larger images and makes nandroid-restore unusable for me.

(Maybe it's only marked bad. Manufacturers can do so to make it unusable.)

If you have bad blocks in any of the partitions then do some om-mani's.

11. Boot recovery-RA

12. On your magic choose to apply zip from sdcard: daldroid-htcmagic1-signed.zip

Watch the serial-console for nand write errors in the boot or system partition.

13. Reboot the magic.

If you got stuck in the RUU USB then try:

./fastboot oem boot

That worked for me to bring daldroid up.

If daldroid works on your magic (wifi, calls) and your only problem is the RUU/RUU USB stuck on boot,

look at my post about modifying the misc partition.

This worked for me to bring my magic back from RUU to a normal boot.

Now you can try to apply non-full-flash-updates.

I updated my magic to eclair 2.1 with the "eugenes & manup wrk" rom.

KiNgxKxlicK AOSP 2.1/1.6.1 wont work for me. When I try to install, recovery-RA says: bad!

Good luck!