Creating and Restoring Backups - Complete Guide

Discussion in 'Droid X Rooted Help' started by maderschramm, Nov 27, 2010.

  1. maderschramm

    maderschramm Member

    Joined:
    Jul 2, 2010
    Messages:
    672
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Madison, WI
    Ratings:
    +0
    You need Bootstrapper because the bootloader is locked.

    It's a highjacked recovery, not an application like titanium.

    A nandroid (clockworkmod) recovery is different from what you're thinking of. The nandroid backup backs up your /system, your /apps, everything. Titanium can only backup apps.

    If you brick your phone it can be resolved with a nandroid backup. Even if Titanium COULD restore your phone if bricked, you wouldn't be able to boot into the operating system to run it.

    That said, unbricking is actually usually done with an sbf flash (as booting into the clockworkmod recovery is problematic at times) and is sometimes the only way to go about restoring the phone.

    There's a link in my signature for sbf flashing instructions if you're interested. I'd read it if I were you because (no offense) I see a brick in your future.
     
  2. mikey4226

    mikey4226 Member

    Joined:
    Nov 25, 2010
    Messages:
    119
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    Ahh, that makes sense now. I actually just skimmed through and bookmarked the links in your sig just a little while ago, but after reading so many different threads the past few hours, I started getting everything jumbled up. Thanks for your help.
     
  3. Tippin

    Tippin New Member

    Joined:
    Dec 16, 2010
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    EDIT-I made a thread so its not cluttered.
     
  4. rfranken

    rfranken Member

    Joined:
    Jul 1, 2010
    Messages:
    154
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    my story.
    I'm on a DX and current with OTA.
    I had made a stock backup after rooting with z4 before doing anything else. just as your instructions say to do.
    (i did Not test that backup after making it though.)

    a week or so later i flashed rubix 1.9.5. love it. great rom life is good. a couple days later...being braver now that flashing a rom had such great results, i want to start flashing some themes onto my rubix rom. before i do so i make a new backup of my current setup because its exactly how i want my phone to be if i something goes wrong or i dont like the themes.

    so once thats done i start with the themes and only trying ones that say they are compatible with rubix 1.9.5. first two go well, but don't suit my fancy. on the 3 theme i try....frick. i get caught in a boot cycle. i do a battery pull. i try to flash the theme a couple more times....boot cycle.

    so i figure...forget about it...i've got Restores begging to be used. neither of my restores work. i was wiping cache wiping data. tried both my stock restore and rubix restore....and they get locked up half way through or so. (although the progress bar never actually moves)
    my rubix restore stalls out on this line
    cache_1669375730
    my other restore stalls out on some goofy number somewhat similar to above.
    CRAP.
    now i'm realllly worried.
    neither of my backups work....ugh.
    so next i try flashing the Rubix 1.9.5 rom again as its still on my sd card.
    it works. i'm had factory reset and have to recustomize my phone again...but at least its working. and after a night...i now have my phone exactly how i want it again.
    so i do another backup of my phone in bootstrap...and here i sit today.

    question.....what the bleep went wrong?? why would both of my backups fail me? now i'm quite concerned about when the next OTA comes....what if i want to upgrade to it? and i can't get back to stock? i haven't done any sbf'ing as it sounds scarier than what i have been doing.

    making a backup is pretty straight fwd right? you pretty much just get into bootstrap and make a backup...it says..complete and all that so you assume its good to go. the only thing that doesn't say complete or success or whatever is sd-ext.....is that significant or something i'm not using?
    also isn't doing a restore pretty straight fwd...or do you need to be doing some of the other options in bootstrap before starting your restore?

    thanks for any insight or help or recommendations!
     
  5. maderschramm

    maderschramm Member

    Joined:
    Jul 2, 2010
    Messages:
    672
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Madison, WI
    Ratings:
    +0
    don't know why it's not restoring for you. you're using the bootstrapper, not rom manager, right?

    also, on those themed bootloops, a facotry reset may have gotten you into the os.

    the sd-ext error isn't a problem, I think it's just a dx thing. I get it too.

    There isn't any real step you missed for the backup. I don't know what to tell you really. I'd say flash one with rubix, then attempt to recover it right away.

    You could try a factory reset before doing the restore....don't know if it will help or not though.

    Also, with otas, your previous restore won't work I think because the md5checksum won't pass if you're trying to nand between systems as far as I know - could be wrong though.

    good luck
     
  6. rfranken

    rfranken Member

    Joined:
    Jul 1, 2010
    Messages:
    154
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    thanks, i'll try to restore my rubix backup at some point....but won't for a few days as i finally have things good again. (i stress out when my phone isn't setup just so)

    correct...just bootstrap.....i haven't tried rom manager and don't plan on it unless u think it will help.

    and next time i get stuck i'll try a few things to get it to come back before reverting to a backup or reflashing the rom.
     
  7. maderschramm

    maderschramm Member

    Joined:
    Jul 2, 2010
    Messages:
    672
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Madison, WI
    Ratings:
    +0
    yeah man, sorry I'm no help, I didn't write the program after all. I'd uninstall and replace the logwrapper with the backed up one, then reinstall.
     
  8. rfranken

    rfranken Member

    Joined:
    Jul 1, 2010
    Messages:
    154
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    You lost me on the uninstall...replace logwrapper...reinstall??
     
  9. hookbill

    hookbill Premium Member
    Premium Member

    Joined:
    Nov 30, 2009
    Messages:
    19,491
    Likes Received:
    8
    Trophy Points:
    168
    Location:
    N.E. Ohio
    Ratings:
    +8
    I hope you don't mind if I make a suggestion to you. In your description of the menu for Bootstrap Recovery you say the following:

    apply sdcard:update.zip
    not very useful. applies update.zip from the root of your sdcard.

    Not very useful? This is how you would install a zip file for a manual update. That's very useful. I would suggest removing the "not very useful" part from your write up. Other then that it looks OK.
     
  10. maderschramm

    maderschramm Member

    Joined:
    Jul 2, 2010
    Messages:
    672
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Madison, WI
    Ratings:
    +0
    it's not very useful because the next option in that same menu is "choose zip from sdcard" which allows you to install any update.zip from your sdcard - even those not named simply "update.zip" - I've never actaully used "apply sdcard:update.zip" since the other one does the same thing but you don't need to rename the .zip - hence why it's not very useful.

     
  11. maderschramm

    maderschramm Member

    Joined:
    Jul 2, 2010
    Messages:
    672
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Madison, WI
    Ratings:
    +0
    uninstall the bootstrapper. use a root file explorer of your choice to navigate to /system/bin. delete "logwrapper" then rename "logwrapper.bin" to "logwrapper". reboot. reinstall bootstrapper

     
  12. rfranken

    rfranken Member

    Joined:
    Jul 1, 2010
    Messages:
    154
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    ok...i've just done this.
    would you recommend that i do another bootstrap backup since i did this? or don't bother?

    thanks
     
Search tags for this page
backup droid x before factory reset
,
bricked phone restore with titanium
,
droid x backup and restore
,
droid x root backup
,

galaxy s4 bootstrap.image

,
how to restore a backup on droid x
,
how to use droid x bootstrapper
,

superuser android wallpaper

,

superuser wallpaper

,

use titanium backup restore to bricked device