rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
If you have recovery, you should be fine. Just flash your favorite image and wipe your userdata.
DOD1 said:
rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
Click to expand...
Click to collapse
Holding Home + Power is supposed to take you into the recovery image.
At the bottom of your recovery image does it say Amon Ra 1.5.2 or 1.6.2 or something like that?
If your phones rooted then just wipe and reinstall you rom.
Like lets say your doing the new cyanmod
you apply zip
DR83
With out rebooting apply zip
Cyanmod-rom 1.4xxxx
If it boots back into Android System recovery Utility just hold home and back again.
Give it time to write its radio and its first time rebooting it says on the boot screen for a awhile some longer then others.
This site has always helped me its better to see the instructions rather then read them.
http://www.google.com/search?q=the+...s=org.mozilla:en-US:official&client=firefox-a
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.
I'm having an irritating problem.
I've rooted my wife's Gen 1 Orange SF with Androot, even repeated it when I started having problems to make sure the root had worked. SuperUser is installed and working so I know it has gone OK.
I've installed Recovery Manager v0.36, which has root access.
The current recovery is listed as "unrecognised"
I flashed the following CWM - recovery-clockwork-3.1.0.1-blade-gen1.img (MD5 checksum correct)
I get an "installing" message, then back to the Recovery screen and the recovery is still listed as "unrecognised".
One of the guides I found on Modaco is quite specific about using Recovery Manager v0.34 (though I suspect it just hasn't been updated with the latest release) so I've also tried this using that version and no joy.
So... I thought I'd try the FASTBOOT method. I turn the phone off, remove and replace the battery. Turn the phone on whilst holding the up volume button, and the phone just boots up normally. I've tried this repeatedly, I don't get the big grey square that people report when FASTBOOT fails, I just get no response at all.
Grrrrr!
Any thoughts?
Hmm, when you power up holding volume up key (held for a couple of seconds) does you phone show a static green android logo, or does it boot up fully to the lockscreen?
If only to the android logo, means you're in fastboot.
Edit: you can replace the green android logo with Orange's logo in the above comment if you haven't flashed an alternate ROM on the phone as yet.
I also had the same while trying to flash a recovery to my friend's Blade. I understood that i have been flashing the wrong recovery all this time (though it showed for gen1 and i had a gen1). I used the given recovery(link provided below), and it worked for me like a charm. Use the link download on root of sd card. Use recovery manager to install it. If the recovery manager shows that it has identified the cwmod version then its done or else if it again says unrecognised try different versions of cwmod.
Preferably after getting cwmod to working convert your gen1 to gen2 (wbaw method). Then you can flash a custom rom and use ROM manager to upgrade your cwmod recovery.
http://android.podtwo.com/recovery/archived/recovery-clockwork-3.0.2.8-v9-gen1.img
To Convert gen1 to gen2:
http://forum.xda-developers.com/showthread.php?t=1103096
harmohn said:
Hmm, when you power up holding volume up key (held for a couple of seconds) does you phone show a static green android logo, or does it boot up fully to the lockscreen?
If only to the android logo, means you're in fastboot.
Edit: you can replace the green android logo with Orange's logo in the above comment if you haven't flashed an alternate ROM on the phone as yet.
Click to expand...
Click to collapse
He hasnt been able to install CWmod yet so no green logo will appear. Due to unrecognised version only DELL logo appears and hangs or it reboots normally. And yes FASTBOOT is not enabled in gen1 devices so thats why i say to convert to gen2 as soon as possible.
Hi Be4con,
I flashed a batch of 10 blades the other day, and wrote my own little guide for it. I had exactly the same problem as you with the first two i tried to flash.
The guide on modaco does work, but i found i had to use a much older version of clockwork mod. I used 2.5.0.8 (if i remember correctly) not at work just now so cant see my notes. This was picked up by the recovery no problems and i was able to move on from there.
Hope that helps
Hi
You have try to flash directly to your device with a terminal emulator
type SU
accept SuperUser autorisation
type flash_image recovery /sdcard/recovery_xx_xx.img (you find the good version on the recovery on internet)
reboot your phone with volume + down
if you have any problem to find the fine recovery or to flash the recovery contact me on pv . this method work with my zte gen1
Hi folks, my HD2 just went south. whenever I try and boot the phone it just sits at the CLK loading screen, I can access it with fasboot, but not ADB. I have tried to re-flash recovery, and to boot it from files on my PC, but it then just stops at 'cmdline:'. No matter what button combination I try it just goes to the CLK screen, even hard reset.
Does anyone have any idea how to get past this ?
have you installed CWM or any rom on the phone ?
Yeah, I have CWM & CM7 nightlies. I can still flash recovery as fastboot works at this stage, but I cant get the phone to boot to any other stage, ie the rainbow screen. I am actually begining to think that I have a hardware issue, possibly relating to the button cable or so.
stuck on cLk loadning screen
UbuntuBhoy said:
Yeah, I have CWM & CM7 nightlies. I can still flash recovery as fastboot works at this stage, but I cant get the phone to boot to any other stage, ie the rainbow screen. I am actually begining to think that I have a hardware issue, possibly relating to the button cable or so.
Click to expand...
Click to collapse
this my 3th phone with the same issue. never got a good answer.
Guys,
I installed CM10 (official) onto my Nexus 7. The ROM was running perfectly, no problems whatsoever. I then decided to flash the Elite kernel. I made a back up via Clockwordmod before hand, just in case anything went wrong.
I then installed the kernel and now all I get is the CM10 spinning green boot screen. That's it! I've installed Wug's tool, to try try and boot into recovery, but I can't even get the drivers to install to even use the tool... which is massively annoying.
Spent an hour last night searching for a solution and trying to get this thing to boot into recovery.
I've tried the obvious by holding down the volume rockers and then holding power, I get to the screen (I can't remember it's name) where you can toggle through different selections via the volume rockers, I select Recovery but it doesn't work.
Any ideas?
Make sure your Nexus is plugged into your PC, then you'll be able to get into recovery from the bootloader. This is the well known workaround for the problem with the original bootloaders.
Also, upgrade your bootloader to 4.13 as that version fixed the problem of getting into recovery.
Sent from my Nexus 7
Thanks.
Daft question, I'm not 100% on upgrading the boot loader. Can this be done on the device itself? If so, how?
Yes. There's a flashable zip file that you can install using recovery. Search the Development section.
Sent from my HTC Desire S