• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[Q] Boot loop stock

Search This thread

SnowRaptor

Senior Member
Sep 18, 2012
149
36
Hello, folks!

I have a Milestone with stock android (2.1 I guess, after an OTA update from the provider) that was in the drawer for ca. 2 years because the POWER/VOL/CAM flat cable was bad. I changed the cable, was able to boot normally one or twice.

Now the phone freezes with the white motorola symbol.

When I turn it on with PWR + D-pad UP, I get into the bootloader v. 90.73.

Werid thing is that when I try to boot into recovery (PWR + CAMERA), I still get into the bootloader, so I can't get into recovery to try installing another rom to circumbent the boot lock-up.

Ideas to solve this?

Thanks!
 

Erovia

Senior Member
Sep 16, 2012
820
262
It seems like your bootloader is corrupted.

If i were you, i would upgrade it to the latest version (90.78) and try with it.
(Also you should consider using CM7 or even CM10.)
 
  • Like
Reactions: SnowRaptor

Erovia

Senior Member
Sep 16, 2012
820
262
I dont know exactly, i didnt have to do it before.

I'm pretty sure, you can brick your device with this if something goes wrong.

I think you will need the following:
-Drivers
-RSDLite
-proper SBF file from here

But i dont know if you need to boot into bootloader mode or something.

Please, be very-very careful, maybe you should wait if someone with more knowledge gives you any advice.
 
  • Like
Reactions: SnowRaptor

Tal_Star

Member
Oct 21, 2012
22
1
Did you manage to get the Device manage to take the new boot loader via usb?

If it did load the SBL try loading the vulnerable recovery sbf then put open recovery on to your SD card. If you can get that fair then I'd imagine you could load a new OS on to it without much issue. Lots of guides out there.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    It seems like your bootloader is corrupted.

    If i were you, i would upgrade it to the latest version (90.78) and try with it.
    (Also you should consider using CM7 or even CM10.)
    1
    I dont know exactly, i didnt have to do it before.

    I'm pretty sure, you can brick your device with this if something goes wrong.

    I think you will need the following:
    -Drivers
    -RSDLite
    -proper SBF file from here

    But i dont know if you need to boot into bootloader mode or something.

    Please, be very-very careful, maybe you should wait if someone with more knowledge gives you any advice.