Database Users

Hard-Bricked Magic?

I think I bricked my Magic flashing ENG SPL-HBOOT-1.33.2004.
Starts, vibrates and gets stuck at splashscreen "HTC Magic". If I hold the ball when it starts then the blue led will shine forever, dont know why.
It charges when power is attached.
fastboot boot recovery.img does not work, it never finds the phone. Iv done all key combos I could find and it does not react.
I tried to add SAPPIMG.nbh to the memory card, but that did nothing. Not sure that I have the right .nbh, iv got a 32A.
Anyways, iv done anything I can think of, nothing works.
Any suggestions? Dont say JTAG....
Edit: I saw the Arrow box thing after it had flashed the new SPL and restarted, but I only saw it once and it just flashed fast on the screen. Blink and I would have missed it.

Found something very very interesting!
If the device is off and I plug in the USB to my PC after about 2minutes if finds a Unknown Device.
The info I can get from the device is this:
Capabilities:
00000044
CM_DEVCAP_REMOVABLE
CM_DEVCAP_RAWDEVICEOK
Power data:
Current power state:
D3
Power capabilities:
0000005D
PDCAP_D0_SUPPORTED
PDCAP_D2_SUPPORTED
PDCAP_D3_SUPPORTED
PDCAP_WAKE_FROM_D0_SUPPORTED
PDCAP_WAKE_FROM_D2_SUPPORTED
Power state mappings:
S0 -> D0
S1 -> D2
S2 -> D2
S3 -> D2
S4 -> D2
S5 -> D3
Device Instance Path:
USB\VID_0000&PID_0000\5&2EAB04AB&0&1
DevNode status:
01806400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_REMOVABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Click to expand...
Click to collapse
Still cant reach if with Fastboot and as soon as I power it up the Unknown Device disappears.
Edit: Im going to try to connect to it as a Raw device, see whats what.

Any luck?
I'm gona follow this :0)

No luck yet.
Cant really get it recognized in any of my USB RAW software cant get any drivers installed instead of the Unknown Device and its hard since it does not have a PID.
Not done yet, but its not looking very good.

Subscribed.
If it's powering on (sort of) that's a good sign! If the computer sees it at all that's also a good sign.
Good luck to you! Here's a link to a sappimg file that's known to work on mytouch 1.2 which is sort of a 32a. Can anyone verify that this file will work for him?
Also I thought 32a had to be sappimg.zip and not sappimg.nbh? Try that...
Anyway, here's your link.
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
EDIT - this article is specifically for the Rogers Magic.
http://theunlockr.com/2009/10/06/how-to-unroot-the-htc-magic-non-mytouchget-back-to-cupcake/

Ill try sappimg.zip
Can anyone remind me what buttons to hold when I want to to load the sappimg? VolumeDown + Home + Power?

pompom said:
Ill try sappimg.zip
Can anyone remind me what buttons to hold when I want to to load the sappimg? VolumeDown + Home + Power?
Click to expand...
Click to collapse
Vol Down + Power. Good luck!
Make sure you double-check on whether the file I linked you is compatible with 32a. That file works with the myTouch 1.2 which is a 32a board that uses 32b radio. I have no idea which spl it uses, so do your research first! Since you're a standard 32a (aren't you?) that file may or may not be compatible.

Yes, its a standard 32A.
Cant I build my own zip with the required files?
Edit: No reaction what so ever on the VolDown. When I think of it, right before I unplugged the phone from my PC the last time it worked I actually had a device named HTC Dream installed. Since I was playing with recovery roms etc I did not care much about it. But now, seeing that its dead, is it possible that it will react to dream.zip or whatever file name is used?
Edit2: Found it, dreaimg.

pompom said:
Yes, its a standard 32A.
Cant I build my own zip with the required files?
Edit: No reaction what so ever on the VolDown. When I think of it, right before I unplugged the phone from my PC the last time it worked I actually had a device named HTC Dream installed. Since I was playing with recovery roms etc I did not care much about it. But now, seeing that its dead, is it possible that it will react to dream.zip or whatever file name is used?
Edit2: Found it, dreaimg.
Click to expand...
Click to collapse
Damn, that sucks... Also no reaction from Home+Power? Do you have a dedicated camera button? Try camera button+power if you do.
Dream? Dream is the G1, totally different hardware. 32B.

Yes, I know the dream is G1 32B.
But my PC found a HTC Dream, the fastboot screen said 32A and the hardware is a Magic.
I would also want to know whats with this blue led. When I hold down the scroll ball and start the device the blue LED lights up but the screen does not. Device does not react to anything, need to pull battery to restart it. Ideas?

pompom said:
Yes, I know the dream is G1 32B.
But my PC found a HTC Dream, the fastboot screen said 32A and the hardware is a Magic.
I would also want to know whats with this blue led. When I hold down the scroll ball and start the device the blue LED lights up but the screen does not. Device does not react to anything, need to pull battery to restart it. Ideas?
Click to expand...
Click to collapse
Wow, that's weird, and beyond the scope of my knowledge, unfortunately.
No way to get into fastboot? If you can get the phone into fastboot you can sappimg back to life.

Check out this thread.
http://forum.xda-developers.com/showthread.php?t=571457

Yeah, I read that thread.
Iv done about 30 diff combos to get in to fastboot, no luck.

pompom said:
Yeah, I read that thread.
Iv done about 30 diff combos to get in to fastboot, no luck.
Click to expand...
Click to collapse
Nuts... Sorry bro.

pompom said:
I think I bricked my Magic flashing ENG SPL-HBOOT-1.33.2004.
Starts, vibrates and gets stuck at splashscreen "HTC Magic". If I hold the ball when it starts then the blue led will shine forever, dont know why.
It charges when power is attached.
Edit: I saw the Arrow box thing after it had flashed the new SPL and restarted, but I only saw it once and it just flashed fast on the screen. Blink and I would have missed it.
Click to expand...
Click to collapse
I´m rather new and read tons of documentation by now but it seems i have exactly the same Problem with my HTC Magic 32B.
Best solution is now to get a new phone?
Edit: Sometimes when i try to get into the Fastboot Mode, the HTC Magic splashscreen disappears after a few seconds and a "new" kinda blue background is sliding from the left to the right but without any other effect

JTAG seems to be the only other option right now.
Im not interested enought to find a solution to this.

HTC Magic 32B Black Screen, no response to anything

Hi there,
I have the following problem:
My cousin bought a brand new Magic 32B Vodafone.
I flashed it to latest CyanogenMod 6 for Magic.
The phone still has the Factory SPL + Radio on it,
i just put a custom recovery on it and flashed CM6.
I did the same with my Magic 32B, works fine since a year now.
It worked fine for about 2 weeks, with CM6 running stable and everything.
then suddenly after a reboot of the phone just went to black screen,
no vodafone splashscreen shows up or anything. It vibrates and then does nothing.
It doesn't show up at "fastboot devices" and "adb devices" shows no deveice either.
When i boot it up with volume down + power pressed (to get in fastboot) it doesnt vibrate (like when it works normally), but screen stays black.
I cant get in recovery either.
anyone ever had this problem? of course i googled for this problem but none of the "black screen" search results described my problem ..
is there a way to autoapply defaultrom (SAPPIMG.nhb) put on sd card (may have read something about that some time) or any other solution to this problem?
is this due to flashing the custom rom or maybe a broken device?
what are the chances to get it back from warranty?
i very much appreciate any help!
thanks

Sounds like the screen broke. If you install ANDROIDSDK you can probably grab screenshots to see what the phone is doing. That will allow you to flash the stock sappimg to get back stock and send in under warranty for repair.
Sent from my LG-P500 using Tapatalk

Does not work, phone doesn't respond to anything
ok, I'll just have to sent it to warranty then, and hope for the best
thanks anyway

did you ever fix this?

[Q] Stuck at bootloader at boot

Hi
A friend of mine has a HD2, never HSPL or anything and still running on 1.42 rom.... Now everytime it boots it goes straight into the bootloader. Since its never been messed around with I find it odd, seen it before with people with other phones. Would this just be a corrupted ROM and therefore it goes there, would if poss a stock rom flash be able to restore the phone, if that is not the case then a warranty return is still valid, but obv not wanted.
What do you think, will this work? I did search but everyone's posts come up with I task 29 and now stuck... etc and not from a stock bootloader as well!
Cheers any help will be appreciated, my first thing I will get him to try is a rom reflash but that will be tonight, I'll update on the progress then!

First thing I would check is if his volume button is stuck for some reason. Second would be to see if it detects a USB connection, then hard spl and new rom from that point. Keep us posted.
Sent from my GT-P1000 using XDA App

chris10230 said:
Hi
A friend of mine has a HD2, never HSPL or anything and still running on 1.42 rom.... Now everytime it boots it goes straight into the bootloader. Since its never been messed around with I find it odd, seen it before with people with other phones. Would this just be a corrupted ROM and therefore it goes there, would if poss a stock rom flash be able to restore the phone, if that is not the case then a warranty return is still valid, but obv not wanted.
What do you think, will this work? I did search but everyone's posts come up with I task 29 and now stuck... etc and not from a stock bootloader as well!
Cheers any help will be appreciated, my first thing I will get him to try is a rom reflash but that will be tonight, I'll update on the progress then!
Click to expand...
Click to collapse
The post above me is correct check and make sure the volume down button is not stuck/Hung in the down position. If it is stuck in the down position like it is being held down at boot then this is the cause of it going straight to bootloader at boot up. If there is no problem with the volume down button then try a hard reset of the HD2. Warning this will reset your friends HD2 tolike it was fresh out the box so any photos, videos, documents, and etc that is not on the SD card they will lose. Also any contacts that are not backed up withan app like Microsoft My Phone will be lost. To do the reset while the HD2 is off bold the volume up and the volume down buttons down and press and bold the power button down. When you see the tri color screen come up release the volume and power buttons and follow the instructions on the screen (hint: you will want to press the vume up button). Now if after the Hard reset your friends HD2 still goes to bootloader at boot up then download and flash the stock ROM for their HD2 you can find it on HTC.com but make sure you varifiy that it is for their HD2 by entering the serial number of their HD2 you can find the serial number look under the battery. To flash the ROM let the HD2 boot up to the bootloader and then connect it to the computer via USB cable and wait for the Serial in the white bar of the boooader screen to change to USB and for your computer to show it recognize the pbone and then run the .exe or RUU wich everone the ROM has.

Never thought of the key being held done will try that first.
Also I won't HSPL'ing as its in warranty and a half HSPL'ed phone is well useless

OK so i feel like a bit of an idiot for this one. Turns out what I call a bootloader and he does is totally different. For me Its the tri-colour screen, for him its the red/orange windows boot screen. So it was all solved by a HR. Great..
Sorry for those who offered the advice but it really was not needed. but solid advice it was, you always can rely on help in here

[Q] mytouch 4g bootloop bricked? no recovery

Hi everyone I Have a mytouch 4g that was given to me stuck in a bootloop. I do not know the history of the phone the only thing I know is that its stuck in the bootloop. I can access HBoot but I can't go into recovery the phone just reboots itself and goes into the loop. Factory reset does not work either. I put the PD15IMG.zip and the blue bar goes up and the phone reboots and continues with its loop. I really need help I would hate for this phone to be stuck like this help is appreciated. I am willing to do instant message with someone skype, twitter, facebook what ever you're comfortable with I just need some help. I have searched all around and I cannot find a answer and all this new android stuff is overwhelming. I also tried to use adb with the noob method didnt work. Thanks in advance
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59

Find the correct PD15IMG. It should be ~300MB in size.
Check MD5 sum on it.
Flash it in bootloader.
If it still bootloops - your phone is dead, and you should return it for replacement or warranty repair.

okay so last night it I told the phone to not update with the PD15IMG and the phone stopped rebooting but then a few hours later it shutoff and was back in the bootloop. So then I flashed it this time and stopped the reboot but I'll keep you posted.

so the phone still gets stuck in bootloop anytime it completely shuts off either by turning it off myself or pulling the battery. Is there anything else besides flashing PD15IMG

Cr8tiveDre said:
so the phone still gets stuck in bootloop anytime it completely shuts off either by turning it off myself or pulling the battery. Is there anything else besides flashing PD15IMG
Click to expand...
Click to collapse
Well if the phone has never been rooted and you are having these problems, it should still be under warranty. Anyway to get it to HTC to get the warranty honored?

if it has a Sd card in it try to pull that then restart. that fixed mine..... worth a shot

I heard you need proof of purchase for the htc warranty so I'm not sure I will try though

Cr8tiveDre said:
I heard you need proof of purchase for the htc warranty so I'm not sure I will try though
Click to expand...
Click to collapse
At this point it sounds like your only option, it's a paperweight currently.
Sent from my HTC Glacier using XDA Premium App

Cr8tiveDre said:
I heard you need proof of purchase for the htc warranty so I'm not sure I will try though
Click to expand...
Click to collapse
You don't. They can (and do) check the warranty eligibility by your phone's S/N.
Talking from experience - used the HTC warranty to exchange the bad screen for good one, having the phone second hand from eBay.

Cr8tiveDre said:
Hi everyone I Have a mytouch 4g that was given to me stuck in a bootloop. I do not know the history of the phone the only thing I know is that its stuck in the bootloop. I can access HBoot but I can't go into recovery the phone just reboots itself and goes into the loop. Factory reset does not work either. I put the PD15IMG.zip and the blue bar goes up and the phone reboots and continues with its loop. I really need help I would hate for this phone to be stuck like this help is appreciated. I am willing to do instant message with someone skype, twitter, facebook what ever you're comfortable with I just need some help. I have searched all around and I cannot find a answer and all this new android stuff is overwhelming. I also tried to use adb with the noob method didnt work. Thanks in advance
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59
Click to expand...
Click to collapse
I truly believe a phone could never be bricked with all the awesome info in the dev forum.... first .... LEARN ADB! and use it to install the latest CW recovery on your phone... next boot into recovery... volume down plus power at the same time.... choose recovery..... when you get to recovery... should be orange... wipe everything... factory wipe... cache wipe... go to advanced wipe dalvik and battery stats... go back and look for mounts and then format everything... cache, data, sdcard, system.... then plug in your usb cable to your computer and copy whatever rom you would like... i prefer doing footballs 2.2.1... that way i can re-root... ***make sure the rom is "PD15IMG.IMG"... then unmount.... go back a few in recovery until you see power down... then power down... pull battery... replace battery..... power into bootloader ( volume down and power button at the same time ) then sit back and let it do its magic... when it asks you to update... select yes.... let it do its thing..... that's it..... no more bricked phone..... enjoy and re-root.... but seriously..... read all the info in the dev section.... lots of really good stuff!

just realized that you have s=on..... so try just using the stock recovery to do what i suggested..... wiping everything and so on.... if still does not work..... really learn adb and fastboot by going through the dev forums..... good luck!

The link to guide for solving bootlooping/freezing MT4G or determining its death (and unluckily, most of those WILL be terminal cases and the phone WILL be determined as dead beyond any repair), is now in MyTouch 4G Wiki, under "Troubleshooting". The link to (updated and sorted) Wiki is in my signature.

did you tell them you bought the phone from eBay because i did to thinking the phone had a small problem but now it seems like a impossible one to fix.

Yes, I told them the phone was bought from eBay. It didn't matter to them at all.

So I'm sending my phone to HTC still have warranty on it. The hotline was no help so for ppl with a similar problem that doesn't know what to do call htc during the day do not call their repair hotline that is a waste of time just call the listed number for your carrier.

[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