Playing around got myself into trouble...

Discussion in 'Android Hacks and Help' started by sandfreak, Oct 3, 2010.

  1. sandfreak

    sandfreak Member

    Joined:
    Mar 22, 2010
    Messages:
    533
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Washington Coast
    Ratings:
    +0
    Hey everybody, I could use some help.

    I've been running custom roms for about 6 months now and decided i wanted to go back to stock rooted froyo for a change.

    So in rom manager I flashed "stock images droid 2.2" with superuser add on.

    well i decided that was a bad idea and wanted to try another custom rom

    so i downloaded one and when it went to reboot an exclamation point in a triangle next to a phone image popped up.

    so i tried to reboot into recovery and the same image popped up

    so i rebooted normally and went back to rom manager to restore a back up and i got the same image.

    what did i do wrong and what do i do to fix it?

    Thanks in advance
     
  2. superglen99

    superglen99 Member

    Joined:
    Nov 15, 2009
    Messages:
    779
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Auburn,WA
    Ratings:
    +0
    I would suggest going into ROM manager and rebooting into recovery and selecting nandroid then restore
     
  3. lloyd2398

    lloyd2398 Member

    Joined:
    Oct 2, 2010
    Messages:
    107
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Beaverton, OR
    Ratings:
    +0
    very well said thats exactly what i would do also
     
  4. sandfreak

    sandfreak Member

    Joined:
    Mar 22, 2010
    Messages:
    533
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Washington Coast
    Ratings:
    +0
    sorry, forgot to mention i tried that also with no luck
     
  5. hiphopvenom

    hiphopvenom Member

    Joined:
    Dec 12, 2009
    Messages:
    120
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    You need to re flash clockwork or spr recovery
     
  6. sandfreak

    sandfreak Member

    Joined:
    Mar 22, 2010
    Messages:
    533
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Washington Coast
    Ratings:
    +0
    wow i feel dumb, just flashed an older recovery and that worked.

    wish i woulda thought of that before posting.

    thanks for the advice
     
  7. ndoren

    ndoren Member

    Joined:
    Nov 7, 2009
    Messages:
    85
    Likes Received:
    3
    Trophy Points:
    8
    Ratings:
    +3
    I'm guessing what happened is that the "stock 2.2 image" still contained the boot script /system/recovery-from-boot.p . This is built into the stock kernel to replace any custom recovery with the original stock recovery at boot time.

    Thus, when you installed and rebooted the stock ROM, it replaced your recovery. Then, when you went to install another ROM, you then had the stock recovery and you were stuck. Obviously, you found the solution, which was to reflash a custom recovery. The trick is then to flash a custom ROM or remove the forementioned boot script before rebooting into the previous stock ROM, or face having the custom recovery removed yet again. I just thought I'd shed some light on why it happened.

    This scenario also applies to those who root but keep a stock ROM. It will repeatedly replace any custom recovery with the original, until the /system/recovery-from-boot.p. script is renamed or removed. Many "multiple step" rooting procedures remove this file as a matter of course. The one-step rooting tools do not, so this file has to be removed or renamed manually after rooting. Otherwise, your custom recovery will "mysteriously" be replaced by the stock version at reboot time, for as long as you keep the stock ROM in place. Neall
     
  8. Dave12308

    Dave12308 Silver Member

    Joined:
    Nov 15, 2009
    Messages:
    3,253
    Likes Received:
    50
    Trophy Points:
    113
    Ratings:
    +50
    Don't feel dumb, sometimes these things can be a bit confusing until you really get the hang of them. After that, fixing little issues such as these become second nature.

    You had to make this thread, and thus it now exists and may help someone else out in the future.
     
  9. mtz_gto

    mtz_gto Member

    Joined:
    Dec 12, 2009
    Messages:
    230
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Left Coast
    Ratings:
    +0
    Glad you got it all figured out, I would of been crying in a panic. lol :)