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.
Ok so this use to work like 2 days ago, havent changed anything on on my phone.
For some reason when I try to boot into clockwork recovery, the phone going through the boot process once and shuts off, then trys again a second time and it just boots the normal way into the system.
I tried reflashing clockwork and it said it was succesful, but it still keeps doing the same thing.
any help is appreciated.
My current ROM is-Ice Glacier
Make sure you aren't plugged into a charger. Go into ROM Manager and click reboot into recovery. If that doesn't work plug the USB back in and turn the phone off. I have mine set to charge only and it boots automatically into recovery without me doing anything. See if that works.
HTC Glacier Running CyanogenMod 6.2
nope does not work, i have tried every method i could find on the web
turn phone off... hold vol down press power... select recovery when the menu comes up
I flashed to CM 6.1.1 and made a backup beforehand with both Titanium Backup and Clockwork Mod Rom Manager 2.5.1.3.
the problem I'm having is when I tell the phone to shutdown it will shutdown, unless I plug my mini-usb charger in (or have it in already) and then when it's plugged in it will automatically switch back on and go into CWM Recovery console and hang at the reboot option.
I've flashed back to my original backup of the T-Mo OTA OS and I get the same profile I had before, but again when I go to shutdown with the USB cable plugged in it always pops back into the CWM Recovery console.
anyone have any idea's where I'm going wrong ? Thanks in Advance!
Buster!
It's a known issue with clockwork that it will boot into recovery when you charge it while powered off. It is a clockworkmod issue and there is nothing you can do to fix it aside from flashing back stock recovery.
Sent from my HTC Vision using XDA App
RE: Wierd Problem G2
Wow, now that was extremely fast answer, Thank You.
Is there I sticky that tells me how to go back to where I started from?
I've read so much in the past three weeks just to get here that now I don't even know where the h*ll I am?
Thanks again Ratchet !
During my flash to CyanogenMod somehow my phone set itself to boot into cwm whenever the phone was connected to my computer. I should stipulate this only happens when the phone off. When plugging it in, while phone is on, no problem.
tomween1 said:
During my flash to CyanogenMod somehow my phone set itself to boot into cwm whenever the phone was connected to my computer. I should stipulate this only happens when the phone off. When plugging it in, while phone is on, no problem.
Click to expand...
Click to collapse
This has been a known issue with ClockworkMod. It did not happen when you flashed CM. The original battery charging screen was located in HTC recovery image and that is what was shown when you were charging your phone with it powered off (it never really is powered off; more like a hibernated state). Since ClockworkMod has now replaced the original HTC recovery, that battery charging screen is no longer available, so CWM displays its screen when you are charging the phone in a powered off state.
tpbklake said:
This has been a known issue with ClockworkMod. It did not happen when you flashed CM. The original battery charging screen was located in HTC recovery image and that is what was shown when you were charging your phone with it powered off (it never really is powered off; more like a hibernated state). Since ClockworkMod has now replaced the original HTC recovery, that battery charging screen is no longer available, so CWM displays its screen when you are charging the phone in a powered off state.
Click to expand...
Click to collapse
You say it's a known issue, is there a known fix?
tomween1 said:
You say it's a known issue, is there a known fix?
Click to expand...
Click to collapse
There is nothing to fix. If you leave your phone on while it's charging it's not an issue, because the screen will turn off and a few minutes. If you power it off while it's charging, it will display the CWM screen. It's still charging, but the screen will stay on.
If you want the battery charging screen back, then you need to replace CWM with the stock HTC recovery image.
tpbklake said:
you need to replace CWM with the stock HTC recovery image.
Click to expand...
Click to collapse
1) I'm not uninstalling cwm though, am I?
2) Never done this procedure, "replace CWM with the stock HTC recovery image", how would I do this?
tomween1 said:
1) I'm not uninstalling cwm though, am I?
2) Never done this procedure, "replace CWM with the stock HTC recovery image", how would I do this?
Click to expand...
Click to collapse
1. Yes, you would be removing CWM and replacing it with the stock HTC recovery.
2. Run the original HTC RUU (ROM update utility) and reflash the phone back to stock.
tpbklake said:
1. Yes, you would be removing CWM and replacing it with the stock HTC recovery.
2. Run the original HTC RUU (ROM update utility) and reflash the phone back to stock.
Click to expand...
Click to collapse
Not looking for stock, that's why I flashed it
tomween1 said:
Not looking for stock, that's why I flashed it
Click to expand...
Click to collapse
Well, in other words, this is known behaviour for CWM and there is no fix. If you don't want it to happen, as tpbklake was trying to get across to you, either don't plug your phone in while it's off (i.e. charge while it's on) or go back to stock.
If you're looking to just flash a custom ROM then never mess with again, you could try using unrevoked to flash the stock recovery image. But as all of the other posters have said, if you want the useful recovery features of CWM there's no getting around the USB issue.
I looked into this awhile ago myself and picked up the stock recovery image, but never tried it out. (stock recovery image is attached)
I find it kinda funny how many people can turn off their phone and plug it in to charge and see a giant animated battery icon and somehow think that the phone is still completely off? That should be the dead give away that its on, in some state anyway. But enough goofin, like was said above, whether you're seeing that battery icon or seeing the cwm screen, the phone is charging and either way its not really off.
I just partitioned my SD card and flashed a new rom (RunnyBliss HybriD) tonight. Everything was working fine, I just reinstalled all of my apps and everything was perfect. I went to unplug my phone from the computer (which was on charge only) and just unplugged it. After that, all of the apps I downloaded were gone and the home screen pages that I just setup were gone. I decided to reboot and see what happens and to my surprise it wouldnt boot back up. It is stuck at the white "htc evo 4g" screen. I tried to boot into recovery and it vibrates 3 times and then does nothing. I assume that the phone was actually in USB mode and I corrupted the usb by removing it without ejecting it. Long story short, I have an Evo that doesn't work and I dont know what to do. My computer wont recognize it so I cant access the SD card. Please help.
Correction: If I press volume down I can get into hboot. What do I do from here?
try to install a recovery via the bootloader
How would I do this?
npreisler08 said:
Correction: If I press volume down I can get into hboot. What do I do from here?
Click to expand...
Click to collapse
I'm kind of new to this but, in HBOOT there should be a recovery option, select that and recover the latest backup.
EDIT: If Recovery doesn't load then I'm at a lose, sorry.
I figured it out. I got a new micro usb and placed AmonRA on it and then booted into recovery, then went to usb mode and dropped a new rom on it and flashed. Big bam all fixed