From Android Wiki
Thanks for this! However, I don't think it's working for Asian phones yet. I tried it and after the fastboot step it hangs at "HTC Magic". Thankfully I was able to shut off my phone and turn it back on, and nothing was affected. Hope for a version that works on Asian builds soon! =)
I got down to step 12, now my phone loops around the sequence where it displays the word "Android"
12 - Apply your update, reboot (using HOME+BACK, or via selection), and allow it to boot fully.
I rebooted using the "selection", pressing the trackball. After watching it loop for 10 minutes, I started button mashing. Could not get it to respond, so, I pulled the battery and let it sit for a few minutes. Put it back together, pressed the POWER key, and it ended up looping again. Tried the button mashing to reboot, no response. Pulled the battery again. This time I held the BACK key when I pressed the POWER key, and it came up in the fastboot mode.
Any help would be appreciated.
repeated steps 8 through 12, same results
I repeated steps 8 through 12, and got the same results. The screen loops around the display "android". It swipes a white diagonal bar across the word about 5 times, pauses for a few seconds, then "blinks" and starts again.
repeated steps 8 through 12, same results (Confiq)
I gave similar behavior.But my screen doesn't loop. It simply shows "HTC Magic" and it's stuck. That's after i type
fastboot boot recovery-new.img
The only way to make it work is to take out the battery...
--Confiq 16:14, 4 July 2009 (UTC)
Solution: repeated steps 8 through 12, same results (Confiq)
If you have the same problem as Wysie, Confiq or "different guy" go to: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking A bit more reading but worth it.
The trick for me to get it run was to fetch an alternative recovery image RAv1.2.0H from http://forum.xda-developers.com/showthread.php?t=530492
went to a different image
Luckily I was able to install this (rooted) image instead. Ion CRB43 Full Image vCRB43-1.2 from: [Android Blogging Network]http://andblogs.net/2009/05/ion-update-available/
different guy, exact same problem
I'm getting the exact same symptoms as David above. Has any of this been tested successfully on a real magic phone?
Being the complete gphone n00b that I am, I am now going to try and figure out how to get the other image David linked to installed instead.
Ok, random tidbits:
- you can use adb while the phone is stuck in its endless "android logo" boot sequence. Handy for pushing new files to the sdcard.
- the phone is in fact rooted, as shown by an "adb shell". yay. kinda.
- I think I know how to put new images up now. I'll update once I'm back with a working phone.
Phone is back to working. Putting the new update.zip alone didn't do it, I also had to fastboot boot with the ion-rooted-boot.img given at the URL above.
All my installed apps were giving me unhappy errors, so I had to wipe. I now have a rather virginal system, but rooted, and now with a patched su command to get root from terminal.
Here's one vote for updating the update and boot files this wiki page points to.
Rooting the Magic/Sapphire (Method 2) disables wi-fi
I don't know about the rest of guys, but when i root it by method 2 it disabled my wi-fi :(
This method should be deleted!!!
--Confiq 17:23, 4 July 2009 (UTC)
I tried method 1 on my HTC Magic bought in Norway(Europe,) and I had the same result as the people above; it just hangs at the HTC logo (boot.) Then i tried method 2 which gave me an "ok" on everything, but nothing changed. Not that I could see. Certainly didn't disable my WIFI, so that must have been a fluke. Although, I did wipe my phone just to be sure - maybe that made the difference.
I will try the different image listed above later, and report back.
My reason for doing this is because I want to run the "market-enabler" app. It makes available paid apps, as far as I have understood. --The Don 13:42, 6 July 2009 (UTC)
Method 1 worked!
HTC Magic Vodafone Australia - method 1 worked, however I haven't done any of the steps after applying the Update. So no "adb shell flash_image recovery /sdcard/recovery-new.img" or anything after --Jason 14 July 2009
Canadian (Rogers Branded) Magic Update
I have a Canadian Magic sold by Rogers. It seems to have a problem with the recovery-new.img file.
Rogers is intentionally altering their hboot to disable system changes.
Their updates page
has the update
That update makes further changes to the hboot, incrementing the version to HBOOT-1.33.0010 (SAPP50000)
After updating FASTBOOT returns
downloading 'boot.img'... FAILED (remote: not allow)
looks like they don't support the openness android is supposed to be... corporate tools...
The process is successful through step 10
Step 11, command prompt says "Waiting for device"
When I shutdown then restart the device I see the fast boot screen for a moment or two
then the phone automatically displays the ROGERS logo and a black screen
At this point the adb software loses the connection with the device.
adb devices no longer displays my devices serial-number and the command from line 12 returns 'error: device not found
The phone sits on the ROGERS logo indefinitely until hard reset.
Changing the order a bit,
Step 11 revised attempt
shut down phone,
Restart holding back and power
I reach FASTBOOT screen
SAPHIRE PVT 32A SHIP S-ON H
May 8 2009,21:02:32
<VOL DOWN> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to Hboot
<MENU> Power Down
Attaching the USB cable at this point changer the header from 'FASTBOOT' to 'FASTBOOT USB'
adb devices does not show my device
>fastboot boot recovery-new.img
downloading 'boot.img'... OKAY
I get the Rogers screen again. nothing further. I do not get an option to apply update.
Disconnecting USB and popping battery is the only way to exit the rogers screen that Fastboot command opens.
I also tried
Holding the Home and Power as the device starts normally brings up a caution triangle
releasing then depressing the home and power buttons again brings up the Android System Recovery Utility
When I 'apply sdcard:update.zip [Alt+S]'
I get the messages
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (439 files)
--Mrjunix 21:16, 2 September 2009 (UTC)
Source(s): Android solutions