Jump to content


Photo

Not getting into Recovery Mode anymore

- - - - -

  • Please log in to reply
17 replies to this topic

#1
ElKidd

ElKidd

    Newbie

  • MoDaCo Silver
  • Pip
  • 8 posts
  • Devices:ZTE Blade
Hi everyone,

have been in this forum for 2 month and now I'm having some problems with my SF.

I installed one month ago ClockworkMod Recovery 2.5.0.9 and tested different ROMs.

Yesterday I wanted to install my first Froyo ROM, but I don't get into the Recovery Mode anymore. It gets into an infinite loop. (Restarts everytime)
I have to take the battery out to end this loop. But the phone works normally.

I tried to install different ClockworkMod Recovery versions, but it didn't help.

Maybe someone has some idea to solve this.

Thanks in advance.

/ElKidd

  • 0

#2
ElKidd

ElKidd

    Newbie

  • MoDaCo Silver
  • Pip
  • 8 posts
  • Devices:ZTE Blade
Nobody has an idea???

  • 0

#3
Phoenix Silver

Phoenix Silver

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 1,839 posts
  • Gender:Female
  • Location:Strasbourg.
  • Devices:ZTE Blade Orange France
  • Twitter:@phoenixbjp
reflash clockwork with fasboot
try 2.5.1.3 version or 2.5.1.8 version

  • 0
Si le corps est mortel, l’âme elle est éternelle.

#4
ElKidd

ElKidd

    Newbie

  • MoDaCo Silver
  • Pip
  • 8 posts
  • Devices:ZTE Blade
Tried all ClockworkMod versions, but no success. :(

  • 0

#5
StevenHarperUK

StevenHarperUK

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 1,431 posts
  • Gender:Male
  • Location:United Kingdom
  • Devices:Orange San Francisco

Tried all ClockworkMod versions, but no success. :(


Have you tried installing adb (tools for PC)

and running

adb reboot recovery

In a terminal on your pc

  • 0

#6
ElKidd

ElKidd

    Newbie

  • MoDaCo Silver
  • Pip
  • 8 posts
  • Devices:ZTE Blade
Problem remains. Recovery not starting. I don't understand that. :(

  • 0

#7
El Nino9

El Nino9

    Enthusiast

  • Members
  • PipPipPip
  • 171 posts

Problem remains. Recovery not starting. I don't understand that. :(


well take battery out wait a few mins, about 10 mintues.
holding volume+UP put the batter in and then press the power.
connect to pc.

cd to the fastboot directory if you have not set path rules

fastboot devices

it should show your device attached.
if so then try reflash the recovery as mentioned in the guide.
once that is done, remain in fastboot

fastboot erase system -w

then

fastboot erase boot -w

now instead of rebooting, type
fastboot boot *name of recovery*.img
it should boot the recovery up.

  • 0

#8
ElKidd

ElKidd

    Newbie

  • MoDaCo Silver
  • Pip
  • 8 posts
  • Devices:ZTE Blade
Mhhhhhh, that didn't work either.

The problem now is that my phone don't start anymore as I removed the boot & system partition.

And recovery keeps being in the loop.

And "fastboot boot *name of recovery*.img" didn't do anything. (Of course, I replaced the filename with the correct one)

So, how can I install a ROM without using Recovery???

  • 0

#9
ArXiLaMaS

ArXiLaMaS

    Newbie

  • Members
  • Pip
  • 7 posts
I have the same problem too from the beginning. I have flashed all versions and in every way but everytime I get the loop :(
Is there a way to flash a rom directly from the fastboot and if yes can someone tell me the command pls?

  • 0

#10
tcpaulh

tcpaulh

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,003 posts
  • Gender:Male
  • Devices:Coolpad F1, Moto G, G300
  • Twitter:@tcpaulh
ElKidd, removing those partitions could have been a nasty mistake. AT YOUR OWN RISK, you could try the hungarian SD update. http://android.modac...vices-to-512mb/

Doesn't seem like you've got much to lose at this point...but I'd wait for a while and see what someone else says.

  • 0

How To Provide Error Logs

 

There's a problem on KitKat with text wrap / reflow not working. Issue raised here. Please Star and Reply if you think it's a stupid regression


#11
StevenHarperUK

StevenHarperUK

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 1,431 posts
  • Gender:Male
  • Location:United Kingdom
  • Devices:Orange San Francisco

ElKidd, removing those partitions could have been a nasty mistake. AT YOUR OWN RISK, you could try the hungarian SD update. http://android.modac...vices-to-512mb/

Doesn't seem like you've got much to lose at this point...but I'd wait for a while and see what someone else says.


I agree its a big risk - but good as your last resort.

Be aware that you will (if it works) end up with STOCK HUNGARIAN device - and that afterwards you need to Install clockwork and then choose a custom ROM

Edited by StevenHarperUK, 29 December 2010 - 04:37 PM.

  • 0

#12
ArXiLaMaS

ArXiLaMaS

    Newbie

  • Members
  • Pip
  • 7 posts
I did the Hungarian update but still clockwork isn't working :(
Is there a way to flash the rom without clockwork?

  • 0

#13
jt_mcg

jt_mcg

    Diehard

  • MoDaCo Silver
  • PipPipPipPip
  • 319 posts
  • Gender:Male
  • Devices:Nexus 4, Blade, Nook Color
  • Twitter:@jtmcg_raw

I agree its a big risk - but good as your last resort.

Be aware that you will (if it works) end up with STOCK HUNGARIAN device - and that afterwards you need to Install clockwork and then choose a custom ROM


I just did that to see if the reports of Wifi sleep policy being fixed are true and My 512 MB OLED OSF is now hungarian! Going to reflash clockwork and restore backup, but I think this process could help this guy out!

update: clockwork 2.5.1.8 flashed, wiped data and cache and now installing backup

Edited by jt_mcg, 29 December 2010 - 05:06 PM.

  • 0

#14
ElKidd

ElKidd

    Newbie

  • MoDaCo Silver
  • Pip
  • 8 posts
  • Devices:ZTE Blade
The SD update worked and the phone is working again.

I installed again clockwork, but the loop is still there. So I have probably the same strange problem as ArXiLaMaS. In my case it worked one month ago and I haven't done anything special with the phone since then. So do you guys think we can fix this??? If not, how can I install a new ROM (froyo) without clockwork??? (like the SD update)

And thanks for your help tcpaulh, StevenHarperUK and jt_mcg!!!! :(

  • 0

#15
jt_mcg

jt_mcg

    Diehard

  • MoDaCo Silver
  • PipPipPipPip
  • 319 posts
  • Gender:Male
  • Devices:Nexus 4, Blade, Nook Color
  • Twitter:@jtmcg_raw

The SD update worked and the phone is working again.

I installed again clockwork, but the loop is still there. So I have probably the same strange problem as ArXiLaMaS. In my case it worked one month ago and I haven't done anything special with the phone since then. So do you guys think we can fix this??? If not, how can I install a new ROM (froyo) without clockwork??? (like the SD update)

And thanks for your help tcpaulh, StevenHarperUK and jt_mcg!!!! :(


I don't think there's any froyo available this way but some of the earlier 2.1 Custom roms were able to be installed using fastboot (not sure if any are still available either). At least that way, you could be off of the hungarian version (assuming you're not hungarian!!)

Have you done checksums on your clockwork versions? Maybe they've been corrupted, it's unlikely that they all have, but it's worth checking and possibly asking Sebastian404 in his thread about 2.5.1.8 what the problem could be and if he has a version of his de-orangenated 2.1 available for download that can be installed via fastboot.

  • 0

#16
El Nino9

El Nino9

    Enthusiast

  • Members
  • PipPipPip
  • 171 posts

The SD update worked and the phone is working again.

I installed again clockwork, but the loop is still there. So I have probably the same strange problem as ArXiLaMaS. In my case it worked one month ago and I haven't done anything special with the phone since then. So do you guys think we can fix this??? If not, how can I install a new ROM (froyo) without clockwork??? (like the SD update)

And thanks for your help tcpaulh, StevenHarperUK and jt_mcg!!!! :(


so is it only recovery causing the random restarts?
bad sectors on recovery partition me thinks...

  • 0

#17
ArXiLaMaS

ArXiLaMaS

    Newbie

  • Members
  • Pip
  • 7 posts
And is there something that we can do about those bad sectors? Like a format or something? Or it's hardware problem?

  • 0

#18
ElKidd

ElKidd

    Newbie

  • MoDaCo Silver
  • Pip
  • 8 posts
  • Devices:ZTE Blade
ArXiLaMas, I don't think there are bad sectors on the recovery partition. I also installed the recovery image to the boot partition and I got the same problem. I think there is some other problem.
But at least we have now a solution. The installation works. http://android.modac...01-02-oled-tft/

Good luck!!!!

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users