So right now I'm using CWM to do my nandroid backups. I make one after I make any major updates or changes - call me a worry wort. I also use Titanium Backup.
With doing this, obviously it takes up a bit of room so I offload them to my computer. The issue here is if I do something detrimental and need to restore, I don't know of a way to get the backup files back onto the internal memory since you can't access them via CWM, if that makes sense.
I guess I can simply keep just the latest backup saved on the phone itself but I'm wondering if there's another method that I'm not aware of. Is there a way to get files copied to the internal memory if you can't fully boot into the OS?
Oh and one other question: Does a nandroid backup include every single item? Basically is it a 100% clone of the device or are some thing left out? Basically if I tried a completely different rom and then decided to go back to an entirely different rom, would I simply be able to restore it and be up and running? The last restore I did seems to indicate it does but that was going from different versions of the same rom.
nandroid is a clone of ur system.
diablo009 said:
nandroid is a clone of ur system.
Click to expand...
Click to collapse
Ok that's what I figured; read something a bit ago which seemed to say something else.
So if I want to test a few completely different rom setups and make a nandroid backup of each one, I could essentially swap between them whenever I want by simply restoring them and I'll get back to the exact state as I was at the time they were made? Menus and all?
So apparently a kernel change will not get reverted via nandroid. Anything else? Just tried Entropy's daily driver and apparently it's a no go for me. Restored via nandroid and still freezes during 'X' boot animation.
I was running Infusion 1.1 and made sure to reset the VC O/C back to stock and reboot before updating...
Related
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
fatkitty420 said:
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
Click to expand...
Click to collapse
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
thecodemonk said:
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
Click to expand...
Click to collapse
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
fatkitty420 said:
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
Click to expand...
Click to collapse
No sweat! If you look at my join date and postcount, you can see I'm not exactly the veteran around here either.
The MoDaCo ROM doesn't modify very much yet...just adds functionality (it's not the heavily optimized kernel that the GSM users have for example). I'm finding it fairly stable...there's a few quirks but those have fixes pretty easily found so far.
I can still purchase from the market...the stuff you purchased already is tied to your google account, not your phone. I bought Docs2Go before I rooted and flashed and I was able to redownload and install without any hassle or added cost.
On a custom ROM, future updates do depend on the person who is building the ROM. However, MoDaCo has proven pretty reliable thus far in keeping up with releases so it's a bit of a trust thing, do you trust MoDaCo to continue that trend or would you rather place your trust in the manufacturer? (It's a preference thing and willingness to risk either way).
The upside is that once you root to a recovery image (Not even changing your OS), you can take a Nandroid backup of your phone, which is an image you can drop back on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
thecodemonk said:
k on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
Click to expand...
Click to collapse
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
fatkitty420 said:
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
Click to expand...
Click to collapse
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
thecodemonk said:
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
Click to expand...
Click to collapse
Great, this really clarified things.
I love technology but, like most of these things, it's very overwhelming at first.
So my stock Infuse 4G is now Infused 2.1 and I LOVE it. So happy with the change. With that said, what is the number one BEST option to backup the phone in case I do anything stupid? I'm usually very thorough but sometimes I act too quickly.
I'm assuming booting in Recovery and doing the backup there is a good step, is there anything better? Never used Titanium but I see it mentioned a good deal but it seems that you can use it for some things yet not others. I just want a verified safe and secure method.
Also, another question if I may. Since I didn't do any type of backup to begin with, is it safe to assume I can't get back to Froyo at this point? Not that I really want to but I'd like to know either way.
Thanks!
Kadin said:
So my stock Infuse 4G is now Infused 2.1 and I LOVE it. So happy with the change. With that said, what is the number one BEST option to backup the phone in case I do anything stupid? I'm usually very thorough but sometimes I act too quickly.
I'm assuming booting in Recovery and doing the backup there is a good step, is there anything better? Never used Titanium but I see it mentioned a good deal but it seems that you can use it for some things yet not others. I just want a verified safe and secure method.
Also, another question if I may. Since I didn't do any type of backup to begin with, is it safe to assume I can't get back to Froyo at this point? Not that I really want to but I'd like to know either way.
Thanks!
Click to expand...
Click to collapse
You can get back to Froyo but not without wiping your data.
Nandroid backups (from Recovery) can restore your phone to an EXACT state - apps, data, and ROM.
TiBu is fairly flexible and, for example, can take all of your installed apps, back them up along with their data, and restore the missing apps when you switch ROMs. (Be EXTREMELY careful restoring system data or data for non-missing apps - 90% of the time it will break.)
I use Call Logs Backup and Restore and SMS Backup and Restore to back up what TiBu can't
Ok so if I simply want to make one big global backup, the Nandroid backup is a good way to go? I'm not too concerned with backing up stuff individually, more of a 'once a month' type of backup so if something disastrous happens, I can get back to a working state.
Also, if I were to do something that maybe caused a boot loop or some other type of bricked scenario, what is the process for restoring the backup? As in, how do you get back into the Recovery option if you can't boot into the OS to begin with?
Kadin said:
Ok so if I simply want to make one big global backup, the Nandroid backup is a good way to go? I'm not too concerned with backing up stuff individually, more of a 'once a month' type of backup so if something disastrous happens, I can get back to a working state.
Also, if I were to do something that maybe caused a boot loop or some other type of bricked scenario, what is the process for restoring the backup? As in, how do you get back into the Recovery option if you can't boot into the OS to begin with?
Click to expand...
Click to collapse
For that, you have the Ultimate brick solution though I've never had the need to try it.
I've been switching roms quite a bit lately. For each and everytime I :
(1) Do a Tibu backup of all system and apps
(2) Do a Nandroid backup (either from red cwm or from ROM mgr)
The Tibu is the logical backup while the Nandroid is the physical image backup.
So far, I've gone to Serendipity (too many issues) back to my trusted 1.6 without much effort. The Nandroid restore is initially not 100%, some of my shortcuts like gosms and my unlocker setup was messed up. But then I'll go into Tibu, check to see what apps are missing and just restore those. In my case, after restoring gosms and reboot, all is good. I think the apps that have a system equivalent, will need to be restored individually.
However, that said, I haven't been too successful with Tibu on restoring *all* apps installed under Froyo (Infused 1.6) to GB (S7). This is even with the pro's automated method. This is likely so because those apps don't work well with GB and nothing to do with Tibu.
I've been using Titanium Backup for over a year. Third different phone, and maybe 30 different ROM's. I've never had a problem what so ever. Just remember rule #1, when switching ROM's with TitBU... restore "missing apps and data" ONLY! And you'll be fine.
Jep56 said:
I've been using Titanium Backup for over a year. Third different phone, and maybe 30 different ROM's. I've never had a problem what so ever. Just remember rule #1, when switching ROM's with TitBU... restore "missing apps and data" ONLY! And you'll be fine.
Click to expand...
Click to collapse
+1
I second this. Moved between multiple phones, and hard-to-count number of roms, and TiBu was always there to help me out
Hi Folks,
I am running Infinity 1204. I love it, stable as can be. Think I am gonna stay with this version after reading all the problems people are having with the 1211 version.
I am on CWM v5.0.2.7 and when I go to do a nandroid backup, it halts with an error sayin 'unable to create image of' on time it was system and the other was of data.
Has anyone else encountered this? Is it possible due to the ext4 formatting? any pointers?
Also: I have successfully done a backup with rom manager. It seems as though cwm sees this as a valid backup for restoring. Does anyone know if you can use a rom manager backup to restore in CWM?
I'm not much help, but I have successfully restored to CWM backups on 4.0.1.4 on Gummycharged FE 2.0 with IMO 13.6 kernel and I believe Humblecharged 5.0 RC2 with IMO 4.0 kernel.
Check the Infinity ROM thread from known issues with CWM 4.0.1.4. You may be able to use that version to create and restore backups. To my knowledge, people have successfully used the new version of CWM with Infinity to create and restore backups.
I don't know this for certain, but I haven't heard of a single successful instance of ROM manager working on this phone regarding backup and restore. I suspect it will not work, although it would be interesting to see.
Even if you soft-brick your device, you could easily get back to working order via Odin. I've soft-bricked a few times- as long as you can get into download mode, you should be fine.
You could try P3Droid's Odinmaker from the market. I haven't really used it much because I have been able to restore from CWM.
Yeah ... I'm pretty comfortable with Odin and CWM for flashing and installing zip files and such. I've had this phone since the weekend it hit the market and I have recovered from numerous brick jobs in learning my way around the phone.
But I've never played with nandroid until now and the phone hasn't completed a nandroid backup the couple of times I've tried it. Was just wondering if it was an issue maybe with this combination of ROM and CWM.
Edit: Now that I'm home I decided to try it with the cable plugged into desktop to ensure max power source. It goes through the whold backup process and at what I would assume is the end of the process it pukes up;
"Error while making a backup image of /datadata!"
But!! If I go back into the restore section of cwm, it does show a copy with today's date that I just performed. I just don't know if it is a valid full backup with the error I got.
I just flashed the new Avatar Rom and after playing aroung with it for a while decided to go back to Embryo 6.2 which i did from a backup. Is it as clean when you install from a backup as it is doing a complete wipe and starting from scratch. Just curious.
restoring a backup puts the phone to pretty much whatever state u had it in, so if it was a dd running well, that's what u get.
I personally don't use ROM backups, and when I switch ROMs its to switch DD's, just my two cents
Thanks, it might be my imagination but when i installed the backup it seems a little slower than before. It may be my imagination. I guess I will let it run for another day before I start from scratch.
I found that my results differed when I did a full wipe before restoring (better) and when I restored without doing so (worse).
Others have reported different results though.
Hey guys,
I've broken my Nexus 4, it felt out of my table and the front glass is cracked and the touchscreen unresponsive. However, I can see everything on it and can power the phone normally and such.
The phone is unlocked and rooted, running the stock Android 4.2.1.
I'll send the phone back to the repair center so they can give it a new screen and, obviously, wipe out the phone.
I've already used adb to copy my /sdcard into my computer, but I would like to backup everything that could make the process of using the phone after the repair less painful. I'm unable to run the adb backup utility since I can't unlock the phone as it requests.
I'm right now trying to copy /data into my computer. Is it of any use?
Is there anything else that I can backup before sending the phone out?
Ideally I would like to be able to, after getting the phone back, unlock it, maybe install the Paranoid Android ROM, root it, and then put back applications, settings, pictures, etc etc
Thanks in advance!
igorsantos07 said:
Hey guys,
I've broken my Nexus 4, it felt out of my table and the front glass is cracked and the touchscreen unresponsive. However, I can see everything on it and can power the phone normally and such.
The phone is unlocked and rooted, running the stock Android 4.2.1.
I'll send the phone back to the repair center so they can give it a new screen and, obviously, wipe out the phone.
I've already used adb to copy my /sdcard into my computer, but I would like to backup everything that could make the process of using the phone after the repair less painful. I'm unable to run the adb backup utility since I can't unlock the phone as it requests.
I'm right now trying to copy /data into my computer. Is it of any use?
Is there anything else that I can backup before sending the phone out?
Ideally I would like to be able to, after getting the phone back, unlock it, maybe install the Paranoid Android ROM, root it, and then put back applications, settings, pictures, etc etc
Thanks in advance!
Click to expand...
Click to collapse
since the phone itself still works, and the unresponsive screen is the only issue, you might be able to make a nandroid backup (complete backup of everything on phone-apps, settings, etc.)
I assume you probably have a touch based recovery on your phone like twrp or cwm touch. This is obviously an issue.
To counter this you could try using fastboot to flash clockworkmod non touch recovery. This allows you to use the volume rockers and power button to navigate.
To flash the recovery install all the correct drivers, and download the non touch cwm and place it your fastboot directory. Then boot the phone into the bootloader, and use this command:
Code:
fastboot flash recovery "name of recovery file.img"
Then from there you can boot into recovery, go to backup and restore, and finally make a nandroid backup. From there you could copy the backup using adb onto your computer. (the backups are stored in sdcard/clockworkmod/backups)
Thanks! I'll try that.
I think I tried before but it didn't work because I had little free space, and for some reason I gave up (thinking I was doing something wrong or going to try something else, I tried a lot of things during those days).
And then to restore that backup into the fixed phone I'll flash CWM again and use it's restore function, right?
Would there be any issue to install a custom mod (such as Paranoid Android) and then restoring this backup?
On a sidenote: on my Nexus 4 (without real sdcard) the clockworkmod folder is located at /mnt/shell/emulated/clockworkmod.
igorsantos07 said:
Thanks! I'll try that.
I think I tried before but it didn't work because I had little free space, and for some reason I gave up (thinking I was doing something wrong or going to try something else, I tried a lot of things during those days).
And then to restore that backup into the fixed phone I'll flash CWM again and use it's restore function, right?
Would there be any issue to install a custom mod (such as Paranoid Android) and then restoring this backup?
On a sidenote: on my Nexus 4 (without real sdcard) the clockworkmod folder is located at /mnt/shell/emulated/clockworkmod.
Click to expand...
Click to collapse
Yep once you get the phone fixed/replaced, you may need to reflash cwm and copy the backup back onto the phone (if they wiped it)
Then just use the restore option in cwm.
If you install paranoid android, then restore the backup, it will restore to whatever rom you had when you took the backup.
chromium96 said:
If you install paranoid android, then restore the backup, it will restore to whatever rom you had when you took the backup.
Click to expand...
Click to collapse
Boo =(
Ok, let me try another idea: I could get the phone back, restore it normally as we said with CWM, and then use TitaniumBackup to backup apps and settings, then save that to my computer, install Paranoid and then use TB to restore the useful stuff back into the new ROM?
I should just take care on not backing up system stuff, right?
igorsantos07 said:
Boo =(
Ok, let me try another idea: I could get the phone back, restore it normally as we said with CWM, and then use TitaniumBackup to backup apps and settings, then save that to my computer, install Paranoid and then use TB to restore the useful stuff back into the new ROM?
I should just take care on not backing up system stuff, right?
Click to expand...
Click to collapse
Yep thats probably your best bet. Although I would avoid backing up/restoring system stuff with TB as it causes lots of bugs.
Just use TB to backup apps+app data, and you can restore them after installing PA. There shouldnt be any problems