Hey everyone. Today I downloaded the .apk that flashes your recovery for my HTC Magic, it flashed the recovery successfully so I used the recovery to flash a new rom, the latest cyanogen. Now my phone is stuck at the boot screen, Vodaphone one. Not sure what's wrong, or how I can fix it. Running adb devices shows nothing, even in recovery mode.
Lock/Delete. Phone is now bricked.
I tried to flash cyanogenmod onto my vodafone 32B HTC Magic and now it's stuck on a boot loop. I rooted it with super one click, then used amon-ra recovery to load up cyanogenmod. It got to the vodafone red screen then just keeps restarting once every 20 secs or so. I suspect it's because I didn't do a full wipe before flashing, I only clearled dalvik cache. So I tried booting up to recovery but amon-ra isn't loading up and its going back to the android default recovery, which I cant use to reflash another rom. I can't communicate with the phone via ADB (does not recognise device). fastboot can recognise the phone but I can't push anything onto it since I didn't update my SPL (it's at s-on).
So is there any way for me to get amon-ra recovery back onto it or otherwise boot up my phone again?
Find a sappimg.zip and flash that and start over is what I would suggest
I concur :0)
I just got the new CWM recovery update through Rom Manager today, and it said it was successfully flashed, but the phone only hangs on the HTC logo when goingto recovery. I can still do fastboot and boot to Android tho, so I'm now gonna try to figure out how to get my recovery back before something bad happes xD
anyone have advice or know where I can download a standalone copy of CWM 5.0.0.1 for G2?
Wish me luck I'll keep updating as things progress
okipokey, solved my own issue. Just had to reflash back to an older recovery and try again a couple times before it stuck.
Time to test out the new recovery!
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Same here just reinstalled the new version and it worked second time round
must be a bug they havn't quite worked out. Next time I'll do a fastboot flash instead for a low build number.
First time I flashed I tried it from a battery pull through HBOOT and it still hung. Reflash to 3.5 and then back to 5.0 fixed it like you guys
epolaris said:
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Click to expand...
Click to collapse
try just reflashing version 5 I had the same problem,but rebooted the phone reflashed version 5 from the rom manager and now is all good
I just sent the dev a comment about it on his Google+
maybe he'll have a fix out soon
Nice one, seems a "double flash" fixes it have just tested 3 or 4 times,seems to be working
yessir, seems to me that if it's a bug its really minor. I can see this being a problem if someone accidentally screws up something on their phone right after flashing the recovery, but not very likely and they'd still be able to reflash through fastboot
Seemed to flash the new version ok. But then, when trying to boot into recovery for the first time, the phone hung on the HTC logo boot splash. Pulled battery, and booted into recovery ok after that.
that's interesting that some of you didn't hang after the battery pull while mine did. Maybe it depends which version we're upgrading from?
stuck at htc
hey i also had this problem and i can't get my g2 to boot up at all. It hangs at the htc screen. I don't know how to fix this issue as i was trying to restore a backup from recovery right after the update. i can't get into recovery or anything else...all i get is the htc screen. Any ideas how I can fix this?
Luis
Any sign of a changelog?
I have no idea how to get to a changelog...can you tell me how?
biglou421 said:
I have no idea how to get to a changelog...can you tell me how?
Click to expand...
Click to collapse
found this
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
So far no issues here while playing around.
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
biglou421 said:
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
Click to expand...
Click to collapse
can you get into the HBOOT?
pull the battery, put it back in, hold the volume down button and then hit the power button. you should come to a white screen with some options
In the case you want to update your recovery using fastboot method, heres what you'll need:
CWM 5.0.0.1 for G2 (Vision)
HTC Sync drivers
ADB fastboot from Android SDK
Make sure your phone is all the way off by pulling the battery. Get into the HBOOT by holding down the volume down button and then hitting the power. use the volume keys to navigate and the power button to select. Choose "FASTBOOT"
Rename the recovery that you downloaded from CWM to "recovery.img" and put it in your ADB and Fastboot folder
plug your phone into your computer and pull up a command line for your adb/tools/ or adb/platform-tools/ folder where you should have ADB and Fastboot.
under the command line type in:
fastboot devices
<list of devices>
If you do not see your device make sure the cable is plugged in and your drivers are installed. if still nothing try a different cable til you get it to be recognized by the computer.
Once it's recognized do:
fastboot flash recovery recovery.img
when its done:
reboot
I flashed through ROM manager. On suggestion, I checked the box for "erase recovery - recovery will be erased prior to flashing". On first reboot to recovery it sticks at HTC screen. Pulling battery and vol. up+power then entering recovery the 2nd time works just fine.
Hope this helps.
hi there so i have a g2 and i rooted it no problem and then i decided to change over to the desirez hboot however something went wrong so i tried to boot into recovery, however i forgot that i still had the PC10IMG in my sdcard and it loaded the radio .... i believe it erased the rom and now i'm stuck in a bootloop on the HTC screen. I tried this method found on
cynogenmod's forum on how to fix a semi-bricked g2 and I am on the process of trying to load the bootloader however whenever i go into selecting bootloader it searches for PC10img and then it doesn't do anything. It won't allow me to update or anything it just goes back to the screen and i have to choose again and it becomes an endless cycle.
on the bootloader screen the top says
Vision PVT Eng S-off
HBOOT -0.84.2000 (PC10000)
MICROP-0425
Radio -26.02.01.15_M2
eMMC-boot
Sep 8 2010, 15:56:38
I don't know what any of it means besides security off. Someone please help! Is there anything I can do??
take out the SDcard put it in your computer and remove the PC10IMG.zip from the card.
Then put it back in the phone and proceed to boot into recovery and restore your backup or re-flash your ROM.
I also have CM Recovery 3.0.2.4 and I can't even flash the stock rom img because it says there is an errror
Amend scripting is no longer supported
Amend scripting was deprecated by Google in Android 1.5
It was necessary to remove it when upgrading to Clockworkmod 3.0 Gingerbread based recovery
Please switch to Edify scripting to create working update zip packages
I'm not sure if this is bootloader problem or a rom problem
Don't flash a PC10IMG through recovery.
Download another custom rom, put it on your sdcard and flash that through recovery.
Flashing the DZ hboot causes a bootloop because the phone looks in different places for the files.
-Nipqer
My friend was trying to install Bad Boyz Rom on my phone. Idk what he did but now, my phone is stuck on boot loop. I can enter bootloader but can't enter download, RUU, or system mode. sometimes I can enter recovery mode but it reboots after a while (sometimes I can even install a rom).
My phone was S-Off and unlock bootloader
UPDATE: After trying to flash the firmware from the bootloader, I was able to access download and RUU mode. But everything stops there, my phone keeps rebooting automatically while I'm trying to install cook - stock rom or flash firmware. I don't think it's the battery or hardware fault because when in bootloader my phone never reboots!
Can anyone help my phone work again?
Thanks!