Database Users

Stuck on startup screen (provider logo: proximus)

Hello there,
I got my HTC Magic (from belgian operator "Proximus") stuck on the first boot sceen. I can no longer acces the fastboot nor recovery.
The only thing i can do is put the phone in radio bootloader (screen off + blue led).
I have searched the forums alot and some have reported being able to send fastboot comands in this state but i did not manage so as the fastboot shell waits for the phone...
Here is what i got installed / did:
- rooted
- cyanogen mod 4.1.3
** t this point the phone was working great and used several months. then i tryed the following: **
- recovery-RA-sapphire-v1.5.2H.img (worked, wiped the memory and installed the following from here)
- signed-google-ion-ota-14721 (installation worked, auoupdate the radio, reboots and...just the logo) I intended to then go to cyanogen 4.1.9
Any idea what went wrong and even better, if i can make the phone boot again ?
Thanks in advance for your help !

What probably went wrong is that you installed a 32B Radio (the ion's) on a 32A device.
Now if you can't get into fastboot, hboot or recovery then there isn't anything you can do, unfortunately
Try to get the device replaced if it's still under warranty.

pelaon said:
Hello there,
I got my HTC Magic (from belgian operator "Proximus") stuck on the first boot sceen. I can no longer acces the fastboot nor recovery.
The only thing i can do is put the phone in radio bootloader (screen off + blue led).
I have searched the forums alot and some have reported being able to send fastboot comands in this state but i did not manage so as the fastboot shell waits for the phone...
Here is what i got installed / did:
- rooted
- cyanogen mod 4.1.3
** t this point the phone was working great and used several months. then i tryed the following: **
- recovery-RA-sapphire-v1.5.2H.img (worked, wiped the memory and installed the following from here)
- signed-google-ion-ota-14721 (installation worked, auoupdate the radio, reboots and...just the logo) I intended to then go to cyanogen 4.1.9
Any idea what went wrong and even better, if i can make the phone boot again ?
Thanks in advance for your help !
Click to expand...
Click to collapse
I'm pretty sure your phone is finished but you didn't happen to mention what you were doing in the first place? Were you just updating your ROM or flashing a new Radio?

Hum, i fear it has become a very expensive white brick indeed.
I confirm it was a 32A...and i tryed to flash an ion rom wich is 32B.. gasp !
My bad... sould have waited to have my head clear before doing this :/
i'll try to see if i can get the unit replaced/fixed by official means..but idoubt it
Anyone interrested by replacement parts ?
Oh, and what is the radio bootloader mode for (action+power => blue led)...?

Several qustions as i am deseperately trying to revive my Magic:
- Is there anyway to make the phone pick up a special boot on the sdcard Without accessing recovery/fastboot ? If so what file do i need on the sdcard (sappimg ?)
- What is the radio bootloader mode for ???

Try to connect your phone to your computer using USB. Start it in different ways, and see if fastboot or adb finds your phone. As you said you can start it in radio bootloader, try boot in that too, to see if fastboot or adb finds your phone.
If it does, post your radio and hboot, maybe I can help.

Did try all possible boot method, but the phone never registers on the usb with fastboot or adb. It just keeps showing me the operator splashpage.
The last thing i installed on the phone was the "signed-google-ion-ota-14721" (now i see this was for 32B...didn't pay attention enough that day). This overrode the radio with another one included in the zip.
The installation went quite smoothly but when the phone rebooted, it froze on that logo screen...

well i'm here in the same situation...
there must be something to do...
cmon where is the nerd within you, solve this and get a ****load of respect from me

I think I might have bricked. Please help me :(

So.. I had CM6.0.0 Stable running on my 32A HTC Magic. All fine and dandy. Then I saw the Smoki ROM and I decided I wanted to flash that, but only one problem. It required a different radio and SPL. So no problem, right? I flashed the required SPL and Radio through fastboot. Looks good right now! Then I turn off the phone and boot into recovery.. but wait.. it just doesn't boot into recovery and just decides to hang at the HTC Magic logo.
I no longer have a ROM installed since I wiped. So I can only go into fastboot. Is there any way I can fix this, or did I just brick the **** out of my phone?

Ok. So chill out. You can drop one of the old updates onto the SD card and then, after entering recovery mode, just update from SD.
This is also considering you have a clue what I'm talkin about lolz.. let me know, I'll try to help more.

webmastertroi said:
Ok. So chill out. You can drop one of the old updates onto the SD card and then, after entering recovery mode, just update from SD.
This is also considering you have a clue what I'm talkin about lolz.. let me know, I'll try to help more.
Click to expand...
Click to collapse
That's the thing, I can't get into recovery. I can only get into fastboot.

BUMP I really need help, please...

Have you tried accessing recovery manually? By turning phone off, then powering on while pressing "Home" button..?
***Update: sorry, just reread your initial post. You've obviously tried that.. I'm trying to think of what else you can do..

Here, try this! Since you can get into boot loader mode, you should be able to reflash..
http://forum.xda-developers.com/showthread.php?t=463779

My magic is stuck on vodaphone logo

hey guys help me my HTC magic is stuck on vodaphone logo..
i just buy it second hand ..i dont know ether it is b31 or b32..or even i dont know that it is rooted or not..
i found something that fastboot or recovery Img can solve this problem ..is this true?.
and i also it is necessary that phone must be rooted for fastboot or recovery IMG flashing?
tell me the exact method and IMG files link by using which i can recover my magic back..
one thing i am sure that its android 1.5...
waiting for reply and thank you in advance
help me

I have the same thing.
I can still enter fastboot but it's a SHIP SPL so I cannot use flashboot (remote: now allow). Only way to fix is put SD in other phone, get original update.zip and update? I cannot enter custom recovery (clockwork / amon_ra)

how to go to fastboot ? or recovery mode?
danslo said:
I have the same thing.
I can still enter fastboot but it's a SHIP SPL so I cannot use flashboot (remote: now allow). Only way to fix is put SD in other phone, get original update.zip and update? I cannot enter custom recovery (clockwork / amon_ra)
Click to expand...
Click to collapse
hey friend please tell me how to go to fastboot mode and recovery mode..??
i dont have another phone to take original update...
hey can i find it that original update on internet? or in this fourm?
please reply

swapniladsure said:
hey friend please tell me how to go to fastboot mode and recovery mode..??
i dont have another phone to take original update...
hey can i find it that original update on internet? or in this fourm?
please reply
Click to expand...
Click to collapse
Turn off phone first, then turn it on by holding BACK+Power.
That will get you fastboot.

will i need rom for recover
danslo said:
Turn off phone first, then turn it on by holding BACK+Power.
That will get you fastboot.
Click to expand...
Click to collapse
ok i will use these button but is it rom require in MMC?
if yes can u give me link of that rom ??

do u have any original rom for magic?
danslo said:
Turn off phone first, then turn it on by holding BACK+Power.
That will get you fastboot.
Click to expand...
Click to collapse
hey friend do u have any original rom for magic vodaphone??
if yes than please reply link

U need to know what board 32a/32b your on first n if ure rooted, u can find out that by holding volume down n power
Sent from my HTC Magic using XDA App

[Q] Please Help! I Bricked My T-Mobile G2 Attempting To Perm Root!

I think I just bricked my G2! The phone wont start up anymore, it gets stuck at the htc loading screen. What can I do to fix this?

another scaremongerer....
its NOT BRICKED!
such a drama queen.
Just run an official RRU EXE or go into your recovery and flash a different custom rom (if you have a recovery).

i think that I have a similar problem..
I was doing some flash rom( in case Flykernel-11c)...after the process, the android had a strange behavior:
1. The SD card stopped to work.
2. And ALSO, the USB connection stopped. But the power connection is working.
I can't use the adb shell to connect because it doesn't find the device.
So, i cant use the recovery of backup, because i can't acess the backup allocated in SDCARD.
Just a note: I tested the SDCARD in another device, and its WORKING.
Any ideia?

That happened to me a while ago. Unless you have an engineering spl where you can access the sd-card reset command (or whatever it is) I think you're knackered. Someone else feel free to correct me if I'm wrong though.

doubt
TheReverend210 said:
That happened to me a while ago. Unless you have an engineering spl where you can access the sd-card reset command (or whatever it is) I think you're knackered. Someone else feel free to correct me if I'm wrong though.
Click to expand...
Click to collapse
What do you mean? "Unless you have an engineering spl"

Turn your phone off, then turn on whilst holding the back button. There is a white screen and a few lines of text at the top. If it says s-on, you have a normal, locked spl, if it says s-off its an engineering one. Anyway, the engineering spl has a few more commands you can access, one of which resets access to the sd card and usb. Unless you have an engineering spl and can access that command, I don't think there is too much you can do.

[Q] Desire Z Stuck on HTC Logo

Hello Forum,
I bought an HTC Desire Z from ebay a few months ago. I think it's a great phone, and I'm gutted that I seem to have killed it. It was working fine on purchase, so I can't return it. The problem is: About 6 weeks ago, it decided to do an OTA update (Not sure if it was of apps only, or the OS).
It got locked up half way through, and I had to pull the battery.
Following this, it no longer boots. It gets stuck on the HTC logo. I have tried to follow all the advice on various threads, but they all seem to assume scenarios that aren't possible in my case. (eg. I can't use ADB because USB debugging was never enabled, I can't create a goldcard, because I can't boot the phone up, and my SD card adaptor doesn't seem to work with ReadCID):
As far as I know, it is completely stock, though I can't see any carrier branding. It isn't rooted, and has S-ON. I don't know what version it is, but I think the details below will help this:
I can get to the Fastboot menu.
'Factory Reset' just causes it to lock up.
'Recovery' causes it to shut down, show an icon of arrows encircling a phone, then buzzes about 7 times, then locks up, powered off.
ADB doesn't recognise the phone.
RUU stops every time on 'Rebooting Bootloader' and doesn't move further.
Fastboot does recognise the phone but I can't seem to do anything through it.
The best result I've had was that I was able to extract the most up to date ROM.ZIP from the RUU, which I put on an SD card, as PC10IMG.zip. This did load up, and started updating, but got stuck on 'Updating' the Bootloader, until the battery was completely flat. (4-5 hours). This has happened three times.
The text on the bootloader screen is:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
HBOOT
Parsing ... [SD ZIP]
[1] BOOTLOADER - Updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] SPLASH2
[7] USERDATA
[8] TP
[9] TP
[10] RADIO_V2
[11] RADIO_CUST
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Update is in progress
Do not power off the device!
Can anybody offer any advice on what I might still be able to do from this position?
Thanks in advance for any help, and apologies if I've missed any important information!
Ian.

ok, fasboot doesn´t help if you do not have eng hboot.
you could type fastboot oem boot and the phone will try ro boot into the rom and will probably also get stucked on htc screen.
did you try to push power & volume up if the icons comes up after enter recovery?
other thing you could try is to find a ruu that is similar to the version you had on your phone before and try the pc10img thing...
EDIT: or first enter bootloader and then start the ruu on your pc

Hi,
Thanks for your reply.
I tried the 'Power and Volume Up' when the icons came up doing recovery. The screen seemed to go slightly duller than normal, but it then just buzzed 7 times, turned off, and won't turn off again at the moment. Does it need to be left for a period of time after starting this procedure?
FYI - I tried two other ROM.ZIP files from two other RUU's before I got this one to even attempt to load, and both came up with 'Main version is newer than rom' (Or similar). The only one that seems to do anything is the very latest one from the Shipped ROMS website.
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
All the other ROM's have Radio versions lower than that mentioned on the Bootloader screen, so I guess I won't be able to use any earlier ROM.
I'll try the fastboot oem when it starts responding again from the recovery procedure.
Fingers crossed !

I'm afraid that the 'recovery' method doesn't seem to have made any difference to previous attempts.
The 'fastboot oem boot' comes up with:
fastboot oem boot
.. FAILED (status malformed (1 bytes))
finished. total time: 0.000s
Any other ideas?

Hmm. I think I'm out of ideas.
Does anyone have any other thoughts before I list it on eBay for parts?
Thanks,
Ian

The same thing happened to my phone during an OTA 2.3 update, thankfully for me I still had warranty so sent it off to the shop, when it came back I noticed the void tag has been broken, so I'm guessing the fix may of required replacing the internal memory or something along those lines.

Thanks Greg.
At least it's starting to confirm my fears.
The only other thing I just remembered, was that the SD card failed a couple of weeks before the problem happened, and I replaced it with a new one. Maybe this is tied in with the problem. Do any of the experts have a view on whether the OTA update could have failed because the SD card wasn't the original?
The RUU is able to see what the image version is on the device, so there is some connectivity, but it can't seem to reboot the bootloader.
As a result, I can confirm that the image on there currently is 2.42.405.2.
Similarly, the PC10IMG approach seems to get to the point of updating the bootloader, but then hangs.
Could any of the experts confirm whether this would happen if I didn't have a goldcard in, but need one? I can't seem to create one with any of the methods I've found online so far, and want to know whether this is the best line of attack to move things forward, or whether this will be likely to be a similar waste of time.
As far as I can tell, I can't install an ENG bootloader without being able to boot the phone to turn on ADB, I can't do anything with fastboot without the ENG bootloader, and I can't do anything with ADB whilst the phone won't boot up.
In short, I think I'm stuffed. Any other ideas?
Thanks,
Ian.

Update:
I contacted HTC, and apparently, it's still in warranty, even though I wasn't the original purchaser, so there may be a positive conclusion to this story. Will be back in 7-10 days to let you know what happened
Fingers crossed.

there is really not too much to worry about, if you private message me, I can give you Josh's information here on XDA - he can unbrick pretty much any G2/Desire-Z for $40 and has done 100's of them - he has like almost 500 Thanks on here -
the only thing he can't fix is a fried emmc chip, but thankfully those are relatively rare!
(and if the emmc chip is fried, then HTC will fix it, because that truly is their fault, so no worries!)
(HTC knows of the emmc chip failures, and that is why in this case they are not giving you a hassle about the warranty, sort of like when an auto company has done a silent recall, so to speak)

Cant help
Sorry cant really help you much... i wouldnt want that to happen with me...

Thanks anyway for all responders
I just have to wait a few more days for HTC to pick it up and take it to the phone hospital. So long as the previous owner hadn't done anything to invalidate the warranty, I think I may be OK. I definitely haven't.
I'm starting to wonder if it's a bad pin in the USB socket that's preventing it from communicating with the PC properly. I found an error in the RUU log when trying to do a 'fastboot oem rebootRUU':
... FAILED (status read failed (Too many links))
Apparently, this is linked with bad USB cables or drivers, but I know the USB cable and drivers are OK, because I can communicate properly with my Wildfire S using the same set-up.
Anyway - Thanks again for the advice, and fingers crossed