1. DroidForums.net is currently undergoing a major software upgrade. If you are experiencing any problems logging in please: Contact Us

Rooted droid boot problems

Discussion in 'Android Hacks and Help' started by gaviono, Jul 5, 2010.

  1. gaviono
    Offline

    gaviono New Member

    Joined:
    Jul 5, 2010
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    0
    hey i have been having trouble switching roms. I have used rom manager to search for a new rom and tried to boot one from the sd card neither have worked. i am currently using the Onix 1.2.5 rom and just today my phone will not boot up past the boot animation and will not go into boot recovery. ANY IDEAS??

    thanks,
    \m/Gaviono\m/
  2. gavron
    Offline

    gavron New Member

    Joined:
    Jan 29, 2010
    Messages:
    555
    Likes Received:
    0
    Trophy Points:
    0
    Probably you should stick with one that works...

    1. ROMs don't boot from the SD card.
    2. "neither have worked" is not a description of a problem that allows diagnostics.

    1. Pull the battery.
    2. Hold down the X key
    3. Put the batter in
    4. Press power button until the Motorola logo shows
    5. Do not release the X key until it is done.

    6. Once in recovery, adb push an update.zip rom to your sdcard (e.g. $ adb push SimplyStunningv4.2-update.zip /sdcard/update.zip)
    7. Select "install" then "allow update.zip" then "install update.zip(deprecated)"
    8. Select reboot.

    If it ain't broke... don't fix it.

    E

    thanks,
    \m/Gaviono\m/[/QUOTE]
  3. gaviono
    Offline

    gaviono New Member

    Joined:
    Jul 5, 2010
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    0
    ok well that rom was doing really well until my apps were force closing alot and some not even coming up. so i fixed permissions and that didnt seem to work at all. i have done those steps about a million times before this thread and i held the X button in for about 5 minutes and usually boot loader takes no more than 20 30 secs. The motorola logo would come and go as i was pushing it in. after 5 minutes i gave up and let go and now it is back to the same ONIX boot animation and not booting up. is my phone bricked?

    thanks,
    \m/Gaviono\m/
  4. gszeman
    Offline

    gszeman New Member

    Joined:
    Apr 8, 2010
    Messages:
    506
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Novi, MI
    Pull the battery and allow the phone to boot up normally...if it does, all you have to do is open ROM manager and flash clockwork recovery and then flash clockwork recovery again. It's a well known issue with ROM Manager.

    If your phone doesn't boot up normally...check with the Rescue Squad, they can guide you in the right direction to get your phone working again.
  5. gavron
    Offline

    gavron New Member

    Joined:
    Jan 29, 2010
    Messages:
    555
    Likes Received:
    0
    Trophy Points:
    0
    Your phone is not bricked.

    Sounds like you may have ruined your recovery image.

    1. Power droid off
    2. adb wait-for-device && adb push recovery-0.99.3.img /sdcard/recovery-0.99.3.img
    3. adb shell and enter in
    flash_image recovery /sdcard/recovery-0.99.3.img
    4. adb reboot recovery

    E
  6. gaviono
    Offline

    gaviono New Member

    Joined:
    Jul 5, 2010
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    0
    i dont consider myself a noob but would you explain those steps to me plz
  7. gavron
    Offline

    gavron New Member

    Joined:
    Jan 29, 2010
    Messages:
    555
    Likes Received:
    0
    Trophy Points:
    0
    1. Power droid off

    With the droid powered off, it will return to a known state (off).

    2. adb wait-for-device && adb push recovery-0.99.3.img /sdcard/recovery-0.99.3.img

    adb wait-for-device
    is a command that will hang until adb can talk to the droid. When the M logo is displayed the droid will respond to adb.

    adb push recovery-image-name /sdcard/recovery-image-name
    will send a new copy of the recovery image. I use SPrecovery. Some people have managed to use ClockWork Recovery without errors... but they're in the minority.

    3. adb shell and enter in
    flash_image recovery /sdcard/recovery-0.99.3.img

    adb shell
    will give you command line access on the droid.
    The flash_image command will allow you to flash that "img" file into the recovery partition, thereby restoring the "hold X to get SPrecovery upon boot" feature.

    4. adb reboot recovery

    adb reboot recovery
    tells the droid to reboot IN recovery, you could try this first anyway just to see if this will get you in... then restore your nandroid backup. You DID do a nandroid backup, didn't you?

    Ehud
  8. gaviono
    Offline

    gaviono New Member

    Joined:
    Jul 5, 2010
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    0
    my phone still isnt reading in rsd and the sprecovery is saying there is an iso error once i install it which doesnt let me extract it
  9. gaviono
    Offline

    gaviono New Member

    Joined:
    Jul 5, 2010
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    0
    ok can anyone else help me out?
Search tags for this page
adb reboot bootloader error closed
,

adb reboot bootloader error: closed

,
adb reboot bootloader returns error:closed
,

adb reboot-bootloader closed

,
droidboot sd card problem
,
push to sd card to fix boot problem
,
rooted android boot up problem
,
rooted android bootup problems
,
using adb to fix android boot issues