Database Users

Is my HTC Magic totally bricked?

I bought a Rogers HTC Magic for a pretty cheap price. It had The Rogers 1.5 Sense UI update on it. I decided I wanted to root it and load other ROMs, etc. So I read that the easiest method was to use Universal Androot to root it, and ROM Manager (from the Market) to flash the appropriate recovery image.
So, I installed both apps. I first ran Universal Androot and rooted. I confirmed root through ADB and also Super User permissions. I then restarted the phone just for peace of mind. After the restart, I ran ROM Manager. It automatically popped up and asked me if I was running an Ion/My Touch or an HTC Magic. I selected HTC Magic, because that's what this is. So then it flashed the recovery image and restarted the phone. When it restarted it went to the Rogers boot screen for a few seconds, and then started a loop of restarts. That's all it does now. It shows the Rogers screen for a few seconds, goes black and reboots over and over. I have tried booting into HBOOT, Fastboot, and into recovery. I cannot boot into any of them. One thing I did notice is that when I'm pressing any of the combinations (volume down + power, home + power, menu + power) for a very brief half a second right before the phone restarts, the bottom of the screen says "ClockwordMod ..." where ... is the version of the image (I'm at work without the phone, so I don't recall the exact number there).
So, is this thing officially a paperweight now, or is there some sort of hope?
Thanks.
Paul

Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.

adrift02 said:
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
Click to expand...
Click to collapse
Okay. That's weird. I mean, my phone is a Magic so choosing the option for the Magic instead of the Ion/MyTouch seemed to make sense.
Anyway, I cannot get anywhere. Holding vol+ and power does nothing, neither does home and power or back and power. Are there any other tricks to getting anywhere beyond this endless restart loop?
Thanks.

Starting to think I'm screwed.

PaulieORF said:
Starting to think I'm screwed.
Click to expand...
Click to collapse
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.

ezterry said:
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
Click to expand...
Click to collapse
Thanks for the reply!
Right, I cannot get into fastboot or hboot. I'll try running the battery down when I get home today. Interesting idea.

Unfortunately running the battery dead with restarts didn't do the trick.
Any idea if there's any place I can send it to who has the smarts to jtag recover this thing?
Thanks.

me too
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.

tmokeith said:
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
Click to expand...
Click to collapse
I don't think it's the same thing.
I rooted, loaded ROM Manager and installed the recovery. I was never even able to get into recovery in order to try to load any ROMs.

I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App

nate_benji said:
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
The phone does not identify itself to the computer, so this doesn't work.

The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App

nate_benji said:
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Oh yes. I've gone crazy trying every key combination with every combination of taking battery out, plugging it in, USB cable attached, detached, etc.
The phone never identifies itself as a piece of hardware to the computer in the 5 seconds between reboots.

I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.

naparstekk said:
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
Click to expand...
Click to collapse
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.

PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
I wasn't able to get hboot or fastboot. I pluged off and on the battery in the exact moment when the Logo came out after restarting. The logo was on the screen for the whole time, even while battery plugged off. I guess, i've done it so quickly that phone didn't switched off.
I think i was holding the power+home or power+back buttons all the time.
Can't really rember the exact way, sorry.

PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
Try removing the SD card and booting if its not restarting due to the wrong radio too soon that may help.. if you get into android restore the SD card and run the exploid process I posted a bit back for rogers magics, or the older goldcard method.

I've played around with taking the battery out and putting it right back in at all different times during the booting and can't get the phone to behave any differently. Iv'e tried it with SD card in and SD card out, USB cable in and USB cable out. I can't get anywhere.
I did notice that the phone does show up as an Android device for a second when it's booting. Tried to catch it in adb but no luck.
Starting to think this thing is shot. Any other ideas?

Just so everyone can see what's happening, I recorded a video and uploaded it. Linked below:
http://www.youtube.com/watch?v=hPoxMzm0MVU&hd=1

try to hold and KEEP holding the back + power... Not volume down!
Don't push and release like you did in the video.

Have i bricked my phone?

Hi. I were running a rooted stock rom with the newest radio and spl and ra recovery. I decided to try rom manager(i think thats what its called). I flashed the recovery, i believe it is called clockwork. When i rebooted my phone it just keeps rebooting at the htc logo. I cant enter recovery or anything. Is there a way out of this or can i just throw it in the dumpster?

Can you get into fastboot? Take the battery out and pop it back in. Then try powering on holding down back+power. You should get a screen with three Androids skateboarding. If you can get the port the information here. If you can and it just does the boot loop, do the battery again hitting the back button repeatedly, give that a few tries and see where it gets you.
Sent from my HTC Magic using XDA App

DonJuan692006 said:
Can you get into fastboot? Take the battery out and pop it back in. Then try powering on holding down back+power. You should get a screen with three Androids skateboarding. If you can get the port the information here. If you can and it just does the boot loop, do the battery again hitting the back button repeatedly, give that a few tries and see where it gets you.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Thanks for your reply but i cannot get into fastboot either. Ive tried holding every single key while booting xD. It just keeps doing the same thing. Reboot at the "HTC Magic" screen. I hangs for some seconds so ive also tried to see if i could grab it from adb but without success.

same incident happened to me. cannot reboot back at last sent back to htc centre.....

rickytjp1107 said:
same incident happened to me. cannot reboot back at last sent back to htc centre.....
Click to expand...
Click to collapse
Did they take it back under the warranty? Did you mod your phone?

Do you get the blue led & black screen when pressing trackball + power at boot?

I get blue led but no fastboot or recovery
Sent from my HTC Desire using XDA App

Can u fix this
Sent from my HTC Desire using XDA App

So that means your device isn't fully bricked - your hardware seems to be working, and you should be able to restore the device using JTAG (search the forums). Though I managed to restore mine by resetting some stuff with draining battery and repeatedly trying again. I'd recommend you to try too.

[Q] Is it bricked?

ok so i am hoping i have not bricked phone but i think i did. i booted to recovery console by holding the home+power and ran the danger spl and when i reboot it just goes to black screnn with white g1 screen and stays. cant even get back into recovery by holding home+power or holding camera+power. so am i done?

i dont see the words "battery pull" have those been done? what happens when u put battery back in? what rom or what were u running before? what radio?
theres a LOT of info i just cant glean off your post.

androidcues said:
i dont see the words "battery pull" have those been done? what happens when u put battery back in? what rom or what were u running before? what radio?
theres a LOT of info i just cant glean off your post.
Click to expand...
Click to collapse
I did pull the battery several times.
the story of how it happened:
I got my g1 unlocked via unlock code from tmobile, I the proceeded to root the phone. All of which worked fine. I then wanted to load cyanogenmod 6 so i downloaded the dangerspl and moved it to sdcard. i then powered off the phone and booted holding home+power and did an install script form sdcard. it installed and completed and i chose reboot and it went to black screen with white G1 and then just sits there. i have pulled the batt several times and just back to that screen. i have tried booting holding home+power and camera+power and both result in the same screen.

jcdeuce said:
I did pull the battery several times.
the story of how it happened:
I got my g1 unlocked via unlock code from tmobile, I the proceeded to root the phone. All of which worked fine. I then wanted to load cyanogenmod 6 so i downloaded the dangerspl and moved it to sdcard. i then powered off the phone and booted holding home+power and did an install script form sdcard. it installed and completed and i chose reboot and it went to black screen with white G1 and then just sits there. i have pulled the batt several times and just back to that screen. i have tried booting holding home+power and camera+power and both result in the same screen.
Click to expand...
Click to collapse
Yip your bricked, you'll need to jtag it im afraid or buy a new one.

[Q] HTC Rogers Magic+ keeps restarting

Hi
I own a HTC magic from rogers. Im on android 2.1 and 32a motherboard. I tried to root my phone today by using super one click, and it said it was successful. So then i tried to install a rom using Rom manager from the market. I made a custom recovery then tried to install a cyanogen mod 6.1 EB1. It told me to restart my phone so i did. Now my phone just show the rogers screen and restarts. I have tried to hold the power button with the back/home/volume button to no avail. Is my phone bricked?
Thanks for your time

patel1 said:
Hi
I own a HTC magic from rogers. Im on android 2.1 and 32a motherboard. I tried to root my phone today by using super one click, and it said it was successful. So then i tried to install a rom using Rom manager from the market. I made a custom recovery then tried to install a cyanogen mod 6.1 EB1. It told me to restart my phone so i did. Now my phone just show the rogers screen and restarts. I have tried to hold the power button with the back/home/volume button to no avail. Is my phone bricked?
Thanks for your time
Click to expand...
Click to collapse
Pull the battery, put the battery back in, and hold (home+power) until you get into the recovery or the phone starts bootlooping again and let me know what happens.
Sent from my HTC Glacier using Tapatalk

hey thanks for the quick response
Ive tried what you said, it keeps on bootlooping, do you have any other suggestions?
Thanks so much

patel1 said:
hey thanks for the quick response
Ive tried what you said, it keeps on bootlooping, do you have any other suggestions?
Thanks so much
Click to expand...
Click to collapse
Did you leave the battery out for a few seconds. Does it go right back into the bootloop or does it start to boot normally and then starts the loop? Did you try doing the same thing holding back and power?
Sent from my HTC Glacier using Tapatalk

yea, ive tried all the possible of holding buttons (home, back, volume down) and pressing power and none of them have any effect. The phone keeps boot looping. Basically what happens is then i press power, it shows the rogers logo for about 10 seconds, then turns off, then turns back on and shows the rogers logo again. This cycle keeps going on and on. Do you have any more suggestions
Thanks

This has happend to many people trying to use the rom-manager. It's mainly because RM is more for the 32B devices.
But you can still save the phone... just keep pushing the back button and keep restarting..'
I know someone who did for an hour, but he managed to get into fastboot :0)

Hey thanks for the advice
When you mean press back and restarting, do you mean constantly press back while the phone is in bootloop, or take out the battery and put it back in and press back

patel,
i have had the same problem as you. forget rom-manager with phone =\
Google "htc magic keeps restarting" should find info on how to get it into fastboot - i think.
I fixed my problem by downloading the 1.5 sense update from htc's website.
Plug my constantly rebooting phone to my computer and run the RUU update.
Then the phone should automatically grab 2.1 ota - i did this back in december.
So it fixed this problem and i never dared to try and put a custom rom on this phone again.
good luck.

What is the RUU update youare speaking of is it the regular download from HTC?

[Q] Bricked? Please help if possible

I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.

Could you give more info on Rom recovery kernel you were attempting etc?
Sent from my HTC Glaciee using XDA Premium App

Jay10826 said:
I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.
Click to expand...
Click to collapse
Um sorry to say but your screwed. Sounds like a true brick to me
Sent from my HTC Glacier using XDA Premium App

Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?

TeeJay3800 said:
Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?
Click to expand...
Click to collapse
He already stated that he could not boot into h boot
Sent from my HTC Glacier using XDA Premium App

mark manning said:
He already stated that he could not boot into h boot
Click to expand...
Click to collapse
He did? I only saw that he could not boot into recovery. I was thinking if his recovery is screwed up, he could still use fastboot to flash a new recovery and then be able to wipe and start over. If he can't get into the bootloader or recovery, then yeah, it's the dreaded B word.
I'd really like to know what kernel he was trying to flash.

TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
Me too......

TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
First thing I asked.. still no reply kinda sucks when they can't help by responding so we can help them..
Sent from my HTC Glaciee using XDA Premium App

I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....

Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
Unfortunatly its the same procedure, hold volume down and power on. So if when u do that nothing happens and adb doesn't work your phone is done.
Sent from my HTC Glacier using XDA Premium App

A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.

Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
I'm not sure what the exact status of your phone is, but usually flashing a kernel does not brick the phone. If anything the ROM won't run right or there will be other problems, but never do they prevent the phone from booting into recovery (the recovery partition uses a completely different kernel). When you try turning it on again, don't bother trying to let it boot normally. Hold down power and volume down and see if you can get into recovery. Then run all three wipe options and flash a new ROM.

Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
It's happened to me before where I thought I had completely bricked the phone. It crashed in CM7 RC2 when I tried to mess with the DSP settings. After that, I went through the same situation as you. I got tired of it, left it charging overnight while it was stuck on the splash screen. The next morning, it was on like nothing happened. I'm thinking it just needed to sort itself out. Not really a fix or suggestion, but at least an indication that there is hope.

Nah, its dead man. Not on its entirety but virtually. I know that JTAG could be an option albeit, im not sure.
I can assure you though that there must be something extra u must have missed that caused this, did you play with radio's or SPL's? Cause that is how i bricked a magic lol
blah

mine bricked on restoring. got to the point of not responding to anything - power button and even charge indicator no longer worked.
sorry to hear OP. it's bricked.

Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
By saying that you used the visionary app to obtain root, is that all you did? Then installed rom manager and etc etc etc? Did you go through the full root method to get S=OFF as well?

Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?

Jay10826 said:
If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Yes it probably is
Sent from my HTC Glaciee using XDA Premium App

Jay10826 said:
Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Not really, if you were able to run a custom ROM with no problems before then you were rooted properly. Somwhere after you must have gone wrong, not sure where
blah