Jump to content

my blade refuses to go to recovery mode


Recommended Posts

Guest chaosfoevr
Posted

hi m runing ss rls5 n i tried to go to recovery mode for another install....its just keeps getting stuck in the droid screen..

can some someone direct me to relevent page or help me out??

Guest MrBod
Posted
hi m runing ss rls5 n i tried to go to recovery mode for another install....its just keeps getting stuck in the droid screen..

can some someone direct me to relevent page or help me out??

Don't take this the wrong way. Not trying to teach you to suck eggs, but just to check - you are booting while holding volume -, not volume +?

Sitting at the droid screen is what I would expect if you were using volume +

Guest Phoenix Silver
Posted

you can download quick boot in market free too

hit app quick boot

select menu boot in recovery mode

Guest chaosfoevr
Posted
Don't take this the wrong way. Not trying to teach you to suck eggs, but just to check - you are booting while holding volume -, not volume +?

Sitting at the droid screen is what I would expect if you were using volume +

lol..thank fo ur concern anyway

Guest chaosfoevr
Posted
you can download quick boot in market free too

hit app quick boot

select menu boot in recovery mode

i tried that from rom manager app but didnt work...let me try quick boot...

Guest chaosfoevr
Posted
you can download quick boot in market free too

hit app quick boot

select menu boot in recovery mode

it doesnt work....it only reboots.....

m trying to install a new rom, i tried rom manager but it say install manually...na i cant access rcovery ...

Guest ZTE_Blade
Posted

I had a similar problem when using ROM Manager. It seems no matter what version of Clockwork I installed, I couldn't boot into recovery. Here's what I did: Using Recovery Manager (here) I installed the Clockwork version from the sanfranciscoandroid.co.uk guide (http://tinyurl.com/clocknow). After that I could boot into recovery fine, either using Recovery Manger, QuickBoot, or vol-power. I did retry installing the latest version of Clockwork with Recovery Manager afterwards, but again I couldn't boot into recovery, so I reverted back again.

Guest chaosfoevr
Posted
I had a similar problem when using ROM Manager. It seems no matter what version of Clockwork I installed, I couldn't boot into recovery. Here's what I did: Using Recovery Manager (here) I installed the Clockwork version from the sanfranciscoandroid.co.uk guide (http://tinyurl.com/clocknow). After that I could boot into recovery fine, either using Recovery Manger, QuickBoot, or vol-power. I did retry installing the latest version of Clockwork with Recovery Manager afterwards, but again I couldn't boot into recovery, so I reverted back again.

installed the older recovery from rom managr n it worked....thanks for reminding....cheers

Guest Pelemane
Posted

New versions of clockwork are for Gen2.

  • 3 weeks later...
Guest chinnmann
Posted (edited)

i had the same problem as well, i tryed to use an older version of recovery mode to install a newer version of cyanogen mod but it just semi-bricked my blade (if thats possible) and had to recover it in recovery mode... has anyone actually been able to install a new version of cyanogen mod? and if so, how?

EDIT: just realised my stupidity that i will have to upgrade to gen 2 for any more upgrades :D

Edited by chinnmann
Guest Daveatwork
Posted
i had the same problem as well, i tryed to use an older version of recovery mode to install a newer version of cyanogen mod but it just semi-bricked my blade (if thats possible) and had to recover it in recovery mode... has anyone actually been able to install a new version of cyanogen mod? and if so, how?

EDIT: just realised my stupidity that i will have to upgrade to gen 2 for any more upgrades :D

Hi there,

to enter into recovery mode try hitting +vol/menu button/on button at the same time... it worked for me...

have fun

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.