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)
Related
I'm having some problems with my Magic 32a. I flashed it, and loaded a JACHeroski Magic ROM from http://theunlockr.com/downloads/android-downloads/android-roms/ and it all worked fine, if a little slowly. I figured I would try to load a newer hero rom on insted, so I got the MyHero 1.1.3 rom and loaded the zip file onto my sd card. I then went booted holding end and home, selected wipe phone, then load any zip. However, I got an error saying Update failed, no signature (or something along those lines).
Unfortunately, instead of loading my nandroid backup, made just before I wiped, I accidentally backed up again. Then, stupidly, I deleted both backups on my computer.
I followed the instructions on http://forum.xda-developers.com/showthread.php?t=537508 to set up fastboot on my ubuntu 9.10 computer, and tried to flash the recovery image RA-magic-v1.2.3 (stored in the same folder as the fastboot program file) using the command .../android-sdk-linux_x86-1.5_r3/tools/fastboot flash recovery recovery-RA-magic-v1.2.3H.img after booting the phone into fasboot mode, and I get the error that the file could not be found. I also have the file stored in the root of the sd card in the phone, but I get the same error. Although before I could boot into recovery mode using end and home, this now doesn't work. I can still however boot into fastboot mode.
I've tried wiping, loading a myhero rom named update.zip from both the sd card and the .../android-sdk-linux_x86-1.5_r3/tools folder but with no success.
If I just leave the phone to boot, the same thing happens as did when I first tried to load the myhero rom: It shows the HTC logo, then goes to the Hero logo and plays a sound. Then the screen goes black, and then the hero and sound happens again. It loops between the hero logo and the sound ad infinitum, as far as I can tell.
I'm a bit crap at all this terminal command stuff, and I am pretty new to ubuntu, and this is my first android phone (which I only had for a day before it stopped working).
Is it possible to fix myself, or will I have to send it off to HTC? It seems to just be a software problem, and I haven't done anything to the phone other than what I said above.
Thanks to anyone who can help
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.
After flashing my phone in Amon RA's recovery the phone will go to the black HTC screen and just stay there. Immediately after flashing I rebooted within recovery and the phone began to reboot, but then shut off. I had to remove the battery to get it to power on again, and it's just stuck at the HTC screen.
Tried to flash boot, recovery, and misc images, but on boot I get no space on device write error. Help?
When you flashed something did you wipe first?
Yes, I wiped, and have wiped the several times I have attempted to do it again.
Basically i desided i would give the Rom manger and Clock Work Recovery a try, So i downloaded the App from the market and installed it then used it to flash the recovery. However now when i try to boot into recovery it just hangs at the Vodafone Screen at boot up.
I tried to reflash RA Recovery however if i do it within the Rom Manager it does the same and hangs when trying to boot to recovery mode. I tried flashing it by the terminal but that did work either.
So does anyone know what i should do!
try flashing via fastboot
how do i use fastboot? when i boot to fast boot the only options i have are
HBoot Mode
Reset device
Restart to HBoot
Power down
OK i tried flashing using fastboot but i got an error 'FAILED (remote: signature verify fail)'
same problem
i got the saame problem as youu!
Damn rom manager killd my recovery , not even the clockwork recovery will boot up! which sucks because now im stuck on superbad 1.3, i want to go back to cynagoen !!!
can you go back to cupcake using the guide below then come back up from scratch
hxxp://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/
I have been able to fix my problem hope this helps for you to!
i downloaded Amon_RA's recovery and trying installing using the terminal method. I got memory errors saying i was out of memory etc. so i turned SWAP on with 128mb and then swappyness to 60 an tried again, and this time it worked!
Couldnt be complete luck but i would give it a try if i was you
What worked for me.
I had this same problem. I spent hours and hours trying everything under the sun. This happened to me on Cyanogen 5.0.7 DStest7. I notice a lot of people on the cyanogen forum claiming that's what they use. I purchased the pro version and installed clockwork recovery through the app. I tried a lot of things and they all failed. I tried droid explorer exe to flash the recovery, fastboot method, I tried reflashing clockwork, terminal with and with out memory managers running. Finally, I tried flashing the Amon 1.6.2 recovery 3 times in a row with the clockwork app. I did a reboot every time. The last one took and I uninstalled clockwork. I'll probably never change it.
it has only killed your recovery because you selected the wrong option, you must flash the first option (Ion/MyTouch 3G) this is the version for the vodafone 32B handset
I was also frustrated when i chose the HTC Magic option and it hanging on the red voda splash screen
Hope i helped
please somebody helps me with the recovery as well..
im using motorola milestone..
i rooted my phone using UNIVERSAL ANDROOT.. the rooting went fine... plus flashing the clockwork recovery via rom manager went fine.. but everytime i reboot into recovery the recovery triangle logo just blinks for a second and my phone reboots and comes back normally to the homescreen.. how to ablolish this problem?
Best Regards.
I too am experiencing this problem. Flashed CWM Recovery today, then later flashed amon ra. Got into amon ra and successfully did a nand backup, then left it for a few hours. Just now tried to boot into recovery and got the oem android recovery 2e. Wtf is that about??
So I downloaded Clockwork Mod onto my phone and I have root access (thanks to AndRoot) -- so I've been able to flash the ClockworkMod recovery or the RA recovery onto my phone.
However it won't let me boot into the recovery mode (HOME+POWER).
The odd time I can boot into the Clockwork recovery, but as soon as a screen comes up it immediately reboots and then it won't let me boot up.
With RA recovery it wont' get me into anything....
Any suggestions? It's an HTC Magic (Rogers), so it's a 32A phone (as far as I know) and it's really a pain living with just 2.1.
When flashing RA recovery, are you using H? G is for 32B.
yup it was like 1.70h or whatever... made sure of that
but it would never boot into recovery mode...
Dwnload rom manager from market. The app has an option to reboot into recovery. I haven't tried it personally but hope it helps.
i've tried rebooting into the mode that way... still when it reboots and just as i see something it reboots automatically again... and then it'll just come up with that warning screen and i'll have to pull the battery