Database Users

HTC Magic Help - Cannot recover from failed ROM initialization

Hi Everyone
I must apologize if this is a annoying beginner question but I have a problem with my HTC Magic.
I attempted to load the Fatality Hero ROM onto my HTC Magic phone. I already had the daldroid ROM running on it but wanted to try out the Hero ROM. I followed the procedure as described by individuals on the web (and I have done it before to get the daldroid ROM working). The phone was working fine with adb. I followed the following steps:
- I Selected ‘Nandroid Backup 2.1′ from the menu.
- Then selected ‘Wipe Data/factory reset’.
- Then ‘Apply sdcard:update.zip’. (The update.zip file was the fatality Hero ROM)
- I then selected ‘reboot system now’.
The phone went to the flash screen and got stuck there very very long. I then went back to flashboot but now the phone does not show up on adb devices list. This was when I just used adb to load the new ROM.
What can I do to get back into my phone? I can see fastboot and hboot. I just cant use adb anymore
This is what is displayed in fastboot:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAP10000)
CPLD-12
RADIO-3.22.20.17
Please is there anyone that can help me? And sorry if this is a obvious problem but I cant find a solution anywhere.

Sorry for the double post. An update on my situation.
I tried getting everything working in UBUNTU and the system still picks up the phone with a strange device id (not the 0bb4: 0c02 or 0bb4: 0c03 everyone refer to but a device id 0bb4: 0fff) and it still does not show up in the adb device list.
I have tried getting it to work on 3 different windows machines and 1 linux machine and no love. Is there anyone out there that can help me with this?

G1 in weird limbo state

Hi all,
I've been trying to install an OS on a G1 for about 2 hours now. I have gone through about 20 posts and followed instructions to the T. I own a pc repair company and I post regularly to some windows and general computer repair forums, so I'm pretty technical. Since I'm 100% stuck, I'm hoping one of you can help.
I don't know anything about the history of the phone, but it currently boots to the rainbow bootloader screen:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Serial0
I can drop the NBH file from DREAIMG-RC29.zip off of google's android file list into the root of the SD card and get the radio back to 1.22 no problem. I have actually tried 4 different versions of RC29 and all seem to work the same.
I have downloaded about 5 different versions of Android 1.5 (as well as 2 versions of 1.1, and a few of 1.6), changed them to update.zip, and attempted to load the OS and every single one of them fails*(see below for error) in the step "Verifying update package..." EXCEPT signed-kila-ota-148830.de6a94ca.zip. This one actually goes through all of the installation steps without erroring, tells me to hit home+back to reboot, says its updating the radio, goes to a screen with an image of a box pushing an arrow into a phone.... but then it reboots to the rainbow bootloader screen again!
*Error from above: E:Failure at line2: assert file_contains("SYSTEM:build.prop".... MORE ... Installation aborted.
When I reboot the phone now, it immediately tries to reload dreaimg.nbh. If I delete dreaimg.nbh off the SD card, the rainbow screen flashes (very quickly) to a gray screen that says "Loading.... No Image File!"
I know the phone isn't technically "bricked" because I'm able to interact with it, it reboots when I hold green+red+menu, but it sure seems like I'm in an infinite loop at this point.
My only goal is to get an OS loaded on this phone. ANY OS at this point.
Any suggestions on steps I can take? Need any other information?
Thanks alot for taking the time to read my post. I appreciate your time.

Thread moved inside G1 General.

sffan15 said:
Hi all,
I've been trying to install an OS on a G1 for about 2 hours now. I have gone through about 20 posts and followed instructions to the T. I own a pc repair company and I post regularly to some windows and general computer repair forums, so I'm pretty technical. Since I'm 100% stuck, I'm hoping one of you can help.
I don't know anything about the history of the phone, but it currently boots to the rainbow bootloader screen:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Serial0
I can drop the NBH file from DREAIMG-RC29.zip off of google's android file list into the root of the SD card and get the radio back to 1.22 no problem. I have actually tried 4 different versions of RC29 and all seem to work the same.
I have downloaded about 5 different versions of Android 1.5 (as well as 2 versions of 1.1, and a few of 1.6), changed them to update.zip, and attempted to load the OS and every single one of them fails*(see below for error) in the step "Verifying update package..." EXCEPT signed-kila-ota-148830.de6a94ca.zip. This one actually goes through all of the installation steps without erroring, tells me to hit home+back to reboot, says its updating the radio, goes to a screen with an image of a box pushing an arrow into a phone.... but then it reboots to the rainbow bootloader screen again!
*Error from above: E:Failure at line2: assert file_contains("SYSTEM:build.prop".... MORE ... Installation aborted.
When I reboot the phone now, it immediately tries to reload dreaimg.nbh. If I delete dreaimg.nbh off the SD card, the rainbow screen flashes (very quickly) to a gray screen that says "Loading.... No Image File!"
I know the phone isn't technically "bricked" because I'm able to interact with it, it reboots when I hold green+red+menu, but it sure seems like I'm in an infinite loop at this point.
My only goal is to get an OS loaded on this phone. ANY OS at this point.
Any suggestions on steps I can take? Need any other information?
Thanks alot for taking the time to read my post. I appreciate your time.
Click to expand...
Click to collapse
I don't fully understand the issue.. You can get to the stock SPL, you can get to recovery to flash an update.zip, but you can't get it to boot the main system?

Yes, I guess that is the issue.
It seems to load the 1.5 OS I mentioned in my original post just fine, but the phone wont boot into anything but the SPL.
It acts as if there isn't a main system to boot to.
I'm also wondering if there is anything else that should be on the SD card other than update.zip and DREAIMG.spl?
Thanks for your help golden

thats weird, fist time ive seen a problem like this...

I've never seen this either.. usually when dreams get stuck in an spl loop a broken button is the culprit, but since you can get into recovery normally that seems unlikely. This is going to be really hard to diagnose and fix from a stock spl and recovery as well..
Did this phone ever work or did it come to you in this state?

Right? I have really done alot of work previous to posting here, and I only found one other person with the exact same issue. Unfortunately no one had an answer for him either. I never like to bug forums if I don't absolutly have to :/
According to the eBay post, the phone worked fine but broke when the previous owner tried to root it himself.
My dad purchased the phone assuming I would be able to fix it (laughs).

I would be willing to try just about anything at this point, if anyone has any crazy suggestions on how to get the phone to boot to an OS.
Is there any way to 100% wipe everything on the phone, like EVERYTHING, and start fresh? Or is that essentially what you're doing when you boot to recovery mode, tell it to reset to factory, and then reinstall the DREAIMG file?

Bricked Magic 32B, Any chance of repair?

After installing the latest cyanogen mod my phone started to act sluggishly. So I decided to try and unroot the device, restoring the device to its factory status using fastboot. However, I accidently used the wrong .nbh file for this. I used Sappimg.nbh (which is designed for 32A models). Chaos ensues.
The phone picked up the sappimg and overwrote the system/recovery/spl succesfully, but since it's the wrong image, my phone is bricked. It can still boot, but it will not do anything once you enter your PIN-code, an error pops up after any second of activity, force closing everything. The only thing I am able to do is connect the SD-card to my computer trough quick use of the notification bar. I can't get to my recovery or create a goldcard since it will no longer accept fastboot commands (remote: not allowed error).
Model: HTC Magic Vodafone (Netherlands)
Hboot info:
Sapphire PVT 32B SHIP S-ON G
HBOOT-1.33.006 (SAPP10000)
CPLD-10
RADIO-2.22.19.261
Does anyone have any suggestions? I haven't really tried the goldcard method yet, and I have an additional android phone available it this helps in a way.

You can make a GoldCard with the other phone and it will work in your's. You'll need to get an engineering SPL loaded on your phone before you'll be able to reflash the correct SPL. Go the GoldCard route.

Alright, I've created a working goldcard using my spare android phone. I have never used a goldcard before though, and I'm not really sure how to use it. What are the steps nescessary to flash a new spl?

You just need to grab the correct sapping.nbh for your phone, copy it to your goldcard, put the goldcard in your phone, and boot into fastboot pressing back and power. The phone will check the image then tell you to press the trackball to flash if your goldcard is working right.
Sent from my HTC Magic using XDA App

Using the Sappimg extracted from the Vodafone NL RUU.exe still gives me CID incorrect errors. I have a goldcard inserted; are there certain steps necessary to guarantee its succes? If your pc can still read it after altering the hex values it should be working right?
Meanwhile, I've poked around a bit after booting the phone up, and it turns out I can still get to certain apps, but anything that requires the home screen results in an error that force closes everything, so I can't get into setttings. I can only get to items that are presented in the notification bar like text messages or e-mails. If only I could get to USB-debugging settings I could fastboot my way out of this mess...

I've managed to fix the software part by installing a home replacement app, so I'm good for now; I'll just have to see how I can re-root the device if I want to fix the default launcher I guess

For the incorrect CID, your GoldCard may not be any good. I ran into a problem when I first made mine and it didn't work. I ended up redoing everything, including reobtaining the CID via ADB and it worked the second time around.

Yep, that did the trick! It worked this time, I managed to get the code from my own phone this time through adb, and went through the steps of creating a goldcard again. Thank you, almighty goldcard, my phone is now up and running again Even managed to re-root and re-install cyanogenmod now.
\o/

[Q] HTC Magic stucked/spoiled /bricked!! :@

Hi all, I bought a 2nd hand HTC Magic with Mytouch 3g rom. It's the old model (without 3.5mm headphone jack) and its made in Taiwan.
Been using well for 3 months until what happened I tried doing system update from 1.5 to 1.6. Success!! Then I tried doing 1.6 to 2.1 update.
Halfway while updating it, the phone blacked out ( guess I didnt have more than at least 50 % battery power)
And from that point onwards, whenever and everytime I switched on my handphone it boots up and stucked at the Mytouch 3G green screen.
I cant get access into my handphone like how I normally do. All I can ever go far is just the stucked Mytouch 3g screen.
I've read alot from lots and other Android users and tried to do it myself.
1) Tried unrooting it by downloading the sappimg.nbh file, copy into a newly bought 2GB micro SD, pressing (VOL DOWN+POWER) and let the phone do its job.
Manage to get to the parsing, updating and checking signature part but it just say 'Model ID incorrect! Update Fail!'
2) Next I read is about doing GOLDCARD METHOD. I did as instructions and follow it step-by-step and carefully.
3) I can and able to download all needed files like 1.33.2005 HBoot, Amon Ra's Recovery Image, SappiMG.zip and all others.
BUT the only problem is that I cant get it in sync with the comp.
4) I cant get access at all into my phone to go to Settings > Applcations > Make sure Unknown Sources is checked on as required to.
5) I cant get access into my phone at all to go to Market and download the required File Manager App.
6) I tried installing all kinds of files for update.zip by pressing (HOME+POWER) still to no avail.
Tried all kinds of HBOOT, FASTBOOT still cannot.
7) The only thing I'm able to do is just (VOL DOWN+POWER) , (BACK+POWER) , (HOME+POWER) , (TRACKBALL+POWER) which emits the blue LED light, i don't know the reason. But still, nothing can be done.
And by pressing (BACK+POWER) this is what my phone's motherboard or whatever they call it.
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP10000)
CPLD-12
RADIO-2.22.28.25
Oct 21 2009,22:33:27
So what should I do now? Is this what they called it a bricked phone? I tried everything and really at lost. Is there someone out there who's able to help me with this? Been like this the past 4months. And Im really a noob with Android Gadgets as Im new to it. Do pardon my ignorance.
Thanks! really need your help. I'll do my best as long there's other alternative methods unless like I've stated the methods that I'm unable to do.

[Q] Main version older! Update fail!

Disclaimer: I have searched and searched, but found nothing that works.
Mytouch 3g, google branded.
Rooted about a year ago. Installed CM5(I think it was 5). Got greedy and messed it up. Tried to go back to stock. Failed. Bought a Vibrant. Put the mytouch in a drawer. Trying to get it to work again. Here is the problem(s):
The recovery installed was a vodafone. It booted up fine, but when on the welcome screen where it says "touch the android to begin" the phone would not recognize the fact that I was actually touching the screen. Track ball worked fine, but since it actually wanted me to touch the screen it was a no go.
Today while trying to fix the phone and trying to flash all kinds of recovery images I would get the "Main version is older! Update fail!" message. I finally found one (the 2.53.707.2_-_sappimg.zip) that would actually get past the update fail.
The phone now boots up to the main home screen. But it still does not recognize the fact that I am actually touching the screen. The only way I can navigate anything is by using the track ball.
When I click on the "dialer", "contacts", or "call log" icons I get the message:
"Sorry. The process android.process.acore has stopped...blah blah blah"
Does anyone have any ideas?
I have a gold card.

Download my fastboot commander from my signature and provide here all device info.
Just don't flash anything until i say so... you have been warned.

I have a similar problem.
Device info:
SAPPHIRE PVY 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Jun 2 2009, 17:28:28
Initially the device wouldn't boot up at all. I managed to flash an RRU and get Android to boot the phone but now the problem is the SDCARD isn't recognized, every time the device boots up it says SD CARD is ready to be removed. I found a command to fix the sdcard bit from the cyanogen mod forums even though I am not running it (I know) remote boot is not allowed on my phone so I can't even use that. Tried to flash the Engineering SPL 2.53.707.2_-_sappimg using a gold card but it pops up stating:
Main Version is older!
Update Fail!
Please help!
[EDIT]
Also, fastboot getvar version-main gives out the following:
version-main: 2.56.494.7
I understand that my version is higher. Is there a way I could modify it? or the sappimg to think otherwise?
[EDIT]
Cheers!
[UPDATE]
I have managed to root using one click method and now have busybox and su.
I have also managed to flash amon_ra recovery without sd card (well obviously since SD card isn't working for me). Recovery doesn't see the sd card either sadly.
[/UPDATE]