[Q] Clockwork Recovery Issue - EVO Shift 4G General

Alright well I've just recently rooted my Shift an am experiencing a bit of a problem...
All was well, I created a backup of the current (stock) ROM, went into recovery, saw it there. I tried to load it, said it was a success, but when I went to reboot the phone it shows the HTC white screen, blinks off, shows it again and goes back into recovery. I've tried creating an alternate backup and whne rebooting with that it just shows the white HTC screen and stays on it. Any help would be appreciated.

Avivator said:
Alright well I've just recently rooted my Shift an am experiencing a bit of a problem...
All was well, I created a backup of the current (stock) ROM, went into recovery, saw it there. I tried to load it, said it was a success, but when I went to reboot the phone it shows the HTC white screen, blinks off, shows it again and goes back into recovery. I've tried creating an alternate backup and whne rebooting with that it just shows the white HTC screen and stays on it. Any help would be appreciated.
Click to expand...
Click to collapse
Did you download the clockwork from rom manager?
If not, then most likely you'll HAVE to flash a new rom now. Though there are stock roms available. And an RUU if necessary.
Sent from my HTC Speedy (Gonzalez)

Yes, I did.

Related

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.

[Q] is my phone bricked?

noob help!
so i was just charging my phone. then all of a sudden my phone froze.
restarted it, then its just stuck at the htc logo. then the jetplane sound from the at&t intro.
tried doing a hard reset or entering recovery but after it reboots, still gets stuck at the htc logo.
(MORE INFO: im not sure if my phone is still rooted because i restored it my at&ts factory rom,cant change settings for usb debugging coz i ant get inside my phone,i still have my nandroid backups in my memory card from before)
is there anyway i could fix this? thanks in advance.
Try booting into recovery and deleting cache, reboot. If it still gets stuck, then try again, this time deleting user settings. If all else fails, restore your nandroid backup or restore the factory rom. If the problem is the rom, try flashing the RUU.
phone gets stuck at the htc screen when i choose recovery mode. also when i clear data.
tried re-flashing the phone with the stock rom from htc's website. it says its successful but still.. stuck at the htc startup screen.
if u flashed the factory rom back on it, then clockwork is gone is probably gone now. It most definitely is not rooted anymore either. Have you tried to reroot the phone?
rcmmartinez said:
phone gets stuck at the htc screen when i choose recovery mode. also when i clear data.
tried re-flashing the phone with the stock rom from htc's website. it says its successful but still.. stuck at the htc startup screen.
Click to expand...
Click to collapse
That was an un-wise decision to put the stock rom back on. Like stated above. Try a Re-Root. Then flash a CUSTOM ROM to your phone. If this doesn't work. Sounds like you are S.O.L.

[Q] Wildfire bricked! Sort of

So here's the problem, I wanted to flash the cyanogenmod rom to my wildfire, which was running the sunaabh rom. Nothing wrong with it though, just wanted to try something new. So I made a nandroid backup. All's well and I wiped clear and proceed with the flashing. After a while the installation seemed to stopped at a point, I thought it was just installing so I left it there. After a whole hour it was still stuck. So I did the stupid thing a pulled the battery out. Now when I boot the screen is black but the vibrate noise of the startup is still there (silent boot) and the buttons light up, which I'm thinking it boots up fine. The problem is that the screen is blank even when I go to the HBOOT menu. Tried flashing a RUU but the program couldn't recognise the phone. I'm stumped now.
So what should I do?
nachos011 said:
So here's the problem, I wanted to flash the cyanogenmod rom to my wildfire, which was running the sunaabh rom. Nothing wrong with it though, just wanted to try something new. So I made a nandroid backup. All's well and I wiped clear and proceed with the flashing. After a while the installation seemed to stopped at a point, I thought it was just installing so I left it there. After a whole hour it was still stuck. So I did the stupid thing a pulled the battery out. Now when I boot the screen is black but the vibrate noise of the startup is still there (silent boot) and the buttons light up, which I'm thinking it boots up fine. The problem is that the screen is blank even when I go to the HBOOT menu. Tried flashing a RUU but the program couldn't recognise the phone. I'm stumped now.
So what should I do?
Click to expand...
Click to collapse
try taking sd card out and boot into hboot
May be restoring the nandroid could help. I am not sure, but you can try.
Sent from my HTC Wildfire using Tapatalk
he can't get to the nandroid though if he can't get into recovery,
have you had any luck nachos?
Well, it seems that the screen is the problem. It took a lot of reboot and pulling battery's but finally the screen was fine. Cyanogenmod seems to run fine too. But the screen would respond really slowly when I wake it and when I power it off, I'll have to be lucky again to get the screen running again. I did the smart thing and flashed a RUU (it can detect the phone now) and sent it to the shop to get it repaired. Oh well, thanks for your help! I really appreciate it
Quite strange...I had similar issue when I first flashed my HTC Desire where the screen was just blank, but it was at the time when the Desire moved from AMOLED to SLCD and some of the flashing caused it not to work...I thought I also bricked my phone but then flashed again then worked. Created a GoldCard just in case...good luck and just be aware that some phones may require a GoldCard to flash properly.
nachos011 said:
Well, it seems that the screen is the problem. It took a lot of reboot and pulling battery's but finally the screen was fine. Cyanogenmod seems to run fine too. But the screen would respond really slowly when I wake it and when I power it off, I'll have to be lucky again to get the screen running again. I did the smart thing and flashed a RUU (it can detect the phone now) and sent it to the shop to get it repaired. Oh well, thanks for your help! I really appreciate it
Click to expand...
Click to collapse
So what you were facing was the black screen and everytime you put the battery back in and hit power it would vibrate 3 times? I am having the same problem. I was actually flashing it with this and it shut down and now I can't get it back on. But you say that after pulling the battery and replacing it numerous times it came back on?

Phone screen black, fastboot loads ok.

Hi guys,
I recently tried to flash a rom on my phone and when the process was done, all I got was a black screen.
Fastboot still works and I can flash euro roms like on the tutorias fine but the phone simply wont boot.
I can go into emergency mode to flash in it in KDZ, the flashing works fine but still, the phone only displays a black screen.
When I press the power button it vibrates, the PC recognizes the device fine, so I know the phone isnt bricked, I just cant get it to display anything on the screen! please help!
Which rom did you try ?
Using swiftdroid RC4 2.0, but I found out what the problem was. Since on flashboot factory reset was in German, "reset und wipe" or something like that, I did not check it. Reflashed it and it is now working, the only problem is taht tehre are no boot animations whatsoever. only a black screen between pressing the button and going into android. any fix for that?
thank you for the replies!
EDIT: Also, by going into reboot > Recovery, nothing is displayed. this only happens on boot. I flashed originally with Euro+fast.kdz, and that is when this problem begun.
Flash this boot.img
and for the recovery, ace you installed??
I installed CWM for recovery, if that is what you asked.
Going to try to flash it and let you know, hope it does break anything
EDIT: nothing. No boot images. Going to leave it alone until I need it for something. I use an X10 mini, I just bought this phone for testing. Not liking the resistive screen!
you tried to flash an X10 with Rc4 ?
No, I have an X10 which is my default phone, I boght this optimus for testing, I flashed RC4 on the optimus, not the mini. not that stupid
You're not the only one with this problem, this will fix it.
http://forum.xda-developers.com/showpost.php?p=10238074&postcount=41
Did you tried with another ROM ?
Yep, follow this... since I can't post links, I can't help......

Clockwork doesn't respond

Hi!
It's been a while when I flashed my Blade with Swedish Spring and now when I'm trying update to Elite S2, the Clockwork seems to freeze with everything I'm trying to do with it.
First I tried with the old one I had already installed -> Factory reset, nothing happens, only the orange arrow with hat pops on to the screen and about half hour later it was still the same.
Same thing happens when I'm trying to go and select zip, only the arrow comes to screen, nothing happens after that.
And even when I'm trying to reboot or turn my phone off, the arrow shows up but nothing happens. Removing the battery and turning my device on again and my old rom (SS) works like it should and every app are still on their places.
Same thing happens with the newest Clockwork which I updated today, only the color of the clockwork-menu changed from orange to blue, but not the color of the arrow.
I'm not sure should I try straight flash the new rom with Rom Manager? I'm scared that it might brick my device becouse isn't Rom Manager based on Clockwork, so if the old fashioned-way doesn't work, the Rom Manager won't either?
If you got any ideas, please share them. I'm eager to try Android 2.3

Categories

Resources