Danger Spl install ... possibly bricked? - G1 General

I just tried to flash the latest danger Spl. After wiping the phone and reinstaling cyanogen's 4.2.11 I was stuck at the G1 screen and I can only get into the recovery screen after a battery pull. running Amon ra's 1.5.2 right now. Any help will be appreciated.

Hey. Here's what I did when I installed Haykuro SPL on my G1. Remember when you first installed Cyanogen you had to flash the HTC ADP1 image first. Try flashing that first, and then CM 4.2.11.1 and see if that works any better for you.

Blackcobra95 said:
I just tried to flash the latest danger Spl. After wiping the phone and reinstaling cyanogen's 4.2.11 I was stuck at the G1 screen and I can only get into the recovery screen after a battery pull. running Amon ra's 1.5.2 right now. Any help will be appreciated.
Click to expand...
Click to collapse
yeah if you can boot into recovery, are are NOT bricked.

solved
Booted back into Recovery
inable usb toogle
plug in usb cable
install any os of your choice( I recommend something besides what was on there)
Safely eject from computer
disable usb toogle
remove usb cable from phone
Console
hit enter
Type reboot recovery
enter
When phone reboots
wipe phone
Flash O.S from sd card
Reboot phone

Related

Have I brick my Magic?

Hi,
I have a rooted 32b magic. I tried many roms and it worked fine every time.
-But...Then
I got a grey screen after install and reboot if i tried to install anything else as Cyanogen.
I tried to unroot and downgrade to 1.5 to solve this problem...But i did not find a "how to"....
-Now....
If i try to get in recovery mode i get a big "!" - another press on Home+Power brings me to a special kind of
recovery mode...(normally i have amon-ra 1.2.1)...this one has blue letters and has only 3 options (reboot, apply update.zip, wipe).
If i try to install any rom with apply update.zip...it says verification failed...installation aborted.
What have i done?
It seems somehow you have the original recovery image back, I'd say fastboot back into Amon Ra's and apply another ROM, see how that works.
Thanks Dixi789, this solved the problem!

Rom Manager Killed my recovery....help? (32B)

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??

[Q] Needing to get froyo on my HTC Magic

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

[Q] stuck in boot loop after flash

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)

[Q] Booting into clockwork recovery

I'm running an old version of GummyJAR and am trying to switch over to CM7 official nightlies. My phone is already rooted and I installed Clockwork Recovery from ROM Manager. However, when I boot into bootstrap from poweroff it just says:
Bootloader
30.04
Battery OK
OK to Program
Connect USB
Data Cable
There's no options to select from or anything. When I boot into Clockwork with ROM Manager, my phone just reboots and starts up normally again. Am I missing something here?
When you say you are booting into bootstrap (the screen that says 30.04) you are actually booting into the bootloader that we use to sbf the phone, not recovery.
Now as for not getting into recovery from bootstrap on the phone, you may want to go into rom manager and reflash the latest recovery, and then boot into recovery from rom manager. That may solve the problem.
I hope this helps!

Categories

Resources