I'd like to back up my new Nook and also backup periodically the rooted Nook. I'm aware of a method using diskimage and mini-partition wizard, but that seems overkill because it requires deleting all partitions of the Nook, thus if anything goes wrong with the backup the nook is destroyed. Besides, I think the image produced by diskimage will be a total backup whereas I think only the rooted part needs to be backup up periodically.
Is there any way to do periodic backups without using the diskimage/partition wizard procedure?
Well, you only need to delete all the partitions to restore the backup.
Or you can use CWM
won't Titanium work on the nst / glowworm?
backups
Yes, I have titanium backup and back up all my apps, etc. Works very well. But what if the system root becomes corrupt? I'm not very knowledgeable about android, but by analogy with a windows system, backing up up my programs and data will make it easier to restore many things after a system crash, but won't help to restore the system to working condition.
As I understand rooting, the original nook system is not altered but some partitions are changed or added by rooting. Only the boot program is changed to allow choice of either nook original or nook rooted. Is that correct?
What I'm looking, then, for is some way to restore all the rooted partitions only, without first destroying all the nook partitions if the root becomes corrupted (but not the original nook part of the system). If I knew which were the root partitions, I could choose those partitions that had been backed up with diskimage, but how would I restore only those partitions - mini partition wizard won't do that apparently. It requires all partitions be deleted before it will restore the disimage backup; I can't pick and choose partitions, as far as I understand from directions about that app.
I'm worrying about in destroying all the nook partitions is that something goes wrong with my restore procedure. If that happens, then the nook is bricked, probably forever. If only the rooted partitions were replaced, then the restore could be repeated (or I could re-root the Nook).
Perhaps cwm does what I need?
The image based backup (boot from noogie; dd the image of the complete device) is your complete backup.
The Titanium backup is your incremental backup.
Keep a couple of full image backups around and back up more often with Titanium. Restore your rooted backup, then run Titanium to restore your apps.
Rooting changes /boot, /system and /data and the best way to get a reliable /boot backup is to boot from a different disk (noogie) and do the full backup.
As long as you have a viable restore to how the device was shipped, you should in a pinch be able to re-root, reinstall Titanium and then restore your programs and data. I have ~36 gig of NST and glowworm backups in the house and am very glad that I do. Disk is cheap and I think the restore is faster from an image based backup than from a CWR backup.
Related
This is probably a really dumb question but how do I use the backups I've created?
When I flash a ROM that I don't like and I try to restore to an earlier backup I've created it is not working. It either says something about the MD5sum or just aborts in general...
What process do I take in order to restore the phone to an earlier backup?
And better yet, if I install a new ROM and don't want to go through the process of installing all my apps again is there a way to just restore my files from a backup?
You can do an advanced restore and restore only data to get your apps, etc. back. There is also titanium backup that is great for backing up and restoring between roms (the only way to restore apps when using a different rom... restore data from one rom onto another can cause serious issues).
If you're getting MD5 sum errors, the backups are being corrupted. So unless your messing with them on your sdcard, then there may be some bad areas on that sdcard and it might be time for a new one.
danaff37 said:
You can do an advanced restore and restore only data to get your apps, etc. back. There is also titanium backup that is great for backing up and restoring between roms (the only way to restore apps when using a different rom... restore data from one rom onto another can cause serious issues).
If you're getting MD5 sum errors, the backups are being corrupted. So unless your messing with them on your sdcard, then there may be some bad areas on that sdcard and it might be time for a new one.
Click to expand...
Click to collapse
Wait so in order to keep my apps I can go to advanced restore and restore only data but it could cause serious issues? So basically it is possible but risky?
and normally should my restore points flash just like a rom when I go to "Restore"? do I need to wipe everything before I restore?
I did copy and paste them onto my computer so I had them in two places... maybe that corrupted them. Anyways a new, bigger, faster SD card is in the mail so that's kind of a coincidence.
a restore in clockwork is an image restore, so everything in that partition will be wiped anyways.
My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempting to restore a backup (which I didnt know was bad at the time)
Notes
1. I have two backups:
a) the first is 239mb which contains my ebooks and pdfs
b) the second is the boot partition (77mb) - I backed up again when when noogie was on micro SD
2. So basically (both backups) I backed up the NST without selecting the whole physical drive.
3. After a failed root, I tried to restore the backup (and seeing it fail), I decided to wipe the whole partition before attempting to restore again :crying:
4. Are there any restorable backup images that can be downloaded online? Or anything which can restore the partition table including the ROM partition with the serial address etc.
5. Please help me restore the Nook back to factory or any working state. Cos AFAIK i've bricked the device.
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen. N2Tsecurity doesnt work without the ROM partition.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
Did you really wipe all the partitions (like write zeroes over the entire physical drive)?
Or did you just try to repartition it?
The question is whether you truly wiped out the /rom and /factory partitions.
Sometimes partitioning them correctly you can rediscover the file system.
The /rom partition is necessary, even ClockworkMod needs to be able to see it.
The /rom info is replicated in /factory/rombackup.zip
Renate's solution may work.
Also, there is a tool called testdisk available for linux that I've used to recover data and partition layouts before; I would expect that it may work a champ for situations like yours.
To use it, you would need a linux box or find a windows port and boot the NSTG or NST from the noogie disk.
Testdisk can recover deleted partitions automatically, including the all-important /rom partition.
That one's important because it contains device-specific info for your NST. It'll do it automatically, but you do need to read up on what commands to give it. You can also rebuild the table manually using fdisk (and I've done so successfully before.)
A windows file recovery utility might let you recover /rom as well (or the files from it.)
You most need the contents of /devconf, and there are lots of files there. I am not sure which ones are absolutely required.
Hello,
we already have 3 Nooks in the family, all of them rooted. One with Touchnooter on 1.1 about a year ago, two of them with Nookmanager on 1.2 and 1.2.1.
There are more to come for friends, so I wanted to know if there is a possibily to use the Nookmanager backup and change the B&N and Google account setting later on ?
I did them individually so far, as from memory I thought they are individual to some degree, but it get's a bit inefficient.
A) Is cloning in my case possible?
Another thing:
B) Could I update from 1.2 to 1.2.1 without going through the whole process again ? I tried making a backup with Nookmanager, reset to factory, manual update, restore backup - but after restoring the backup it shows 1.2 again. Maybe it's not worth the hassle (?)
Thanks for your help !
It's certainly possible, but I haven't done it so take this advice with a grain of salt.
Before you try any of this, please take a complete backup of the your device with NookManager so if you completely mess up your partitions, you'll still be able to restore your device to a working state. As you've noticed, NookManager does a complete backup of the entire Nook memory, so restoring a backup will take your device back to the exact state it was in at the the time of the backup, including firmware version, partition table, user data, etc. No matter how messed up your Nook is, your backup will get you back in the clear. You do not want to restore a backup made with NookManager to a different device, so with multiple devices make sure you've got your backups identified.
The Nook's internal memory is divided into seven partitions (1-7): boot, rom, factory, system, userdata, cache, and data
What you're looking to do is a backup/restore of selected partitions, which is do-able but you'll need to get your hands dirty. You'll want two SD cards, one with the NookManager, and one for your 'clone' backups.
I think you'll probably want to backup/restore the boot, rom, and system partitions while leaving factory, userdata, cache, and data alone.
To backup select partitions from your 'master' Nook, insert your 'backup' sdcard and use adb to run the following commands:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1
dd if=/dev/block/mmcblk0p2 of=/sdcard/p2
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4
This will create three files on your sdcard: p1 p2 and p4 containing the data from the boot, rom, and system partitions, respectively.
Use the NookManager card to boot the Nook you want to clone to, enable wireless and enable adb. Make a backup now if you do not already have one for this Nook. Remove the NookManager sdcard, insert the backup sdcard, and run the following commands with adb:
mount -t vfat /dev/block/mmcblk1p1 /sdcard
ls /sdcard # make sure you see the p1 p2 and p4 images
umount /system
umount /data
umount /cache
umount /rom
dd if=/sdcard/p1 of=/dev/block/mmcblk0p1
dd if=/sdcard/p2 of=/dev/block/mmcblk0p2
dd if=/sdcard/p4 of=/dev/block/mmcblk0p4
umount /sdcard
sync
reboot
If that works, your Nook should reboot and be very similar to your master device. If this is something you plan to be doing regularly, you can work the backup/restore procedures into scripts, and run them as a custom plugin for NookManager (details here). That way you'll just need the one SD card and you won't have to fuss with all the adb commands.
Good luck, and be sure to post your results when you've got this working.
Thanks a lot for that. I will get my sisters Nook on Thursday. She wants an update to 1.2.1, Relaunch and NoRefesh anyway. So I will make a Nookmanagerbackup, then update to 1.2.1 and then copy the partitions you suggested. I will let you know how that goes.
I have do admit that I already bricked a NSG, but the mistake was not doing my noogie backup correctly. With Nookmanager I fell a lot safer doing all this.
As I'm leaving user data alone I hope to keep the connection to google play and B&N intact with the old settings.
Hello. I have a problem. I've rooted my NST and after 2 months i wanted to get back it to stock so I've deleted all partitions on my Nook and then i realized my backup is wrong (it has only 245mb). Now i have intetnion to buy a 2nd NST and fix 1st one. How I can do it? Can I simply make a (proper) backup new NST and restore using it my old NST? I've readed other post and i know there might be a problem with registatrion. Is there any way to fix my nook using backup from antoher device and how cen i do this? Plese help and sorry for my english.
darksd87 said:
Hello. I have a problem. I've rooted my NST and after 2 months i wanted to get back it to stock so I've deleted all partitions on my Nook and then i realized my backup is wrong (it has only 245mb). Now i have intetnion to buy a 2nd NST and fix 1st one. How I can do it? Can I simply make a (proper) backup new NST and restore using it my old NST? I've readed other post and i know there might be a problem with registatrion. Is there any way to fix my nook using backup from antoher device and how cen i do this? Plese help and sorry for my english.
Click to expand...
Click to collapse
Hi darsd87,
Yes you will be able to fix your nook using the 2nd.
But, have another way to do this.
I do the same mistake, but my device is a NST Glowlight. I think you can do a backup of your nook now and try to recover using NSTG just in case. In the worst case you can overwrite your backup.
Considering what I do to recover, I sugest you do this steps:
1. create a image backup of NST.
2. recover the ROM partition with MiniTool Partition Wizard
3. write the NSTG backup image
4. copy the ROM partition to NSTG image
5. do a hard reset
The instructions and the backup image of NSTG are available in:
http://forum.xda-developers.com/showthread.php?t=2104145
If some post a image of NST without the rom partition would be better.
But, i think the only "problem" you will have is a useless glowlight button in the nook menu.
Best luck!
PS: sorry for my english... i´m from Brazil.
Thank you very much You saved my nook. I didn't have room partition so i've just used NSTG-backup-norom.img and then made a hard reset. I've registered my nook and now it stuck on the glow light screen "Give it a try" I'm pressing n button for 2 seconds but nothing happen co i can't move on. I can only turn on screensaver or turn off device. Is there any way to skip this screen? I think this is the last step of registering because when i restart nook the registration process starts again (only this time skips logging)
Edited.
I skiped registration using "Oobee method" and when I go to device info menu --> About Your NOOK it seems to be registered on me. Now the only thing what doesn't work is Screen menu, when I tap the screen button the screen flash once and nothing happen. Also i don't have internal storage but I think I can fix it using this method: http://forum.xda-developers.com/showthread.php?t=1374777. I have one more question. How I can unroot my nook? Hard reset doesn't work. My nook is still rooted. (I have *Development menu in settings and access to android launcher)
My NST Glowlight is getting replaced due to hardware failure.
When I get the new device, could/should I restore my existing backup that I made using NookManager? Or should I just restore the apps (using Titanium Backup, for instance)?
I am hoping I can be lazy and just restore my latest backup image.
Should be the same device, firmware, etc. Just different serial numbers, I assume.
Jonathan
jdbow75 said:
My NST Glowlight is getting replaced due to hardware failure.
When I get the new device, could/should I restore my existing backup that I made using NookManager? Or should I just restore the apps (using Titanium Backup, for instance)?
I am hoping I can be lazy and just restore my latest backup image.
Should be the same device, firmware, etc. Just different serial numbers, I assume.
Jonathan
Click to expand...
Click to collapse
NookManager will restore everything including your ROM partition which has all of your device specific stuff like the serial number and keys for communications with B&N. You don't want to wipe out your new devices ROM partition. The very first thing you should do with your new device is make a backup and save it somewhere safe. Then you can backup your ROM partition from your new Nook before you restore the NookManager backup and then restore the ROM partition after. Probably easiest to do this with ADB - adb shell to mount the partition and ADB pull it over to your PC. Then push it back after restoring the NookManager backup.
straygecko said:
then restore the ROM partition
Click to expand...
Click to collapse
OK, so the only partition I need to retain on the new device is the ROM partition? That makes sense.
This is how I imagine doing this:
Backup the new device using noogie or NookManager
Using dd (I am on Linux), extract the ROM partition to its own separate image
Boot new device using noogie
Use dd to restore the backup I had previously made from the old device
Used dd to put the new ROM partition on the new device, overwriting what I just put there
All should be well, then, yes?
straygecko said:
Probably easiest to do this with ADB - adb shell to mount the partition and ADB pull it over to your PC. Then push it back after restoring the NookManager backup.
Click to expand...
Click to collapse
Ah, now I understand your first suggestion. That may be easiest, and remove some of my steps. Thanks!
jdbow75 said:
OK, so the only partition I need to retain on the new device is the ROM partition? That makes sense.
This is how I imagine doing this:
Backup the new device using noogie or NookManager
Using dd (I am on Linux), extract the ROM partition to its own separate image
Boot new device using noogie
Use dd to restore the backup I had previously made from the old device
Used dd to put the new ROM partition on the new device, overwriting what I just put there
All should be well, then, yes?
Click to expand...
Click to collapse
Yep that's the ticket.
Hmmmm... The plot thickens.
Browsing around the backup, I notice that there are copies of the rom in factory/rombackup.zip and factory/factory.zip/romrestore.zip and boot/romrestore.zip, although rombackup.zip is the only full copy.
Do I need to worry about these, or will they automatically be updated from the new device?
Of course, I could just restore the NOOK, system and userdata partitions, leaving factory, boot, rom, and cache untouched.
Thanks so much for your input.
jdbow75 said:
Hmmmm... The plot thickens.
Browsing around the backup, I notice that there are copies of the rom in factory/rombackup.zip and factory/factory.zip/romrestore.zip and boot/romrestore.zip, although rombackup.zip is the only full copy.
Do I need to worry about these, or will they automatically be updated from the new device?
Of course, I could just restore the NOOK, system and userdata partitions, leaving factory, boot, rom, and cache untouched.
Thanks so much for your input.
Click to expand...
Click to collapse
Glad you're looking around. I never thought about those. They won't be a problem for day-to-day use. Those other copies are used for when you invoke the factory restore function.
The partitions you listed to restore will work except that /boot/uRamdisk is modified to root the Nook so if you don't restore the boot partition you'll lose root. Probably easiest to replace uRamdisk on the new Nook with the one from your current Nook.
Using GS4 I9505, and my internal storage is getting shorter shorter, day by day. almost like its vanished. i've check emulated 0 and legacy drives nothing there. but as i gethered it coz of CWM, now using twrp, uninstalled CWM but still storage isn't available for usage.
Your space is still lost because it's still allocated to CWM for nandroid backups, even though you no longer have CWM on the device. Therefore, you need to put CWM back on the device, go into its backups and storage menu, delete any existing backups it made, then free the allocated space.
When you put TWRP back on to the S4, your space should return.
He can delete the CMW folder from the storage. The backups are there and they are not hidden.
I provided an in-depth explanation of this in an earlier thread on the same topic, but in essence CWM protects the nandroid backups space so nothing else can write to that area. This is because CWM performs incremental backups by default, and deleting older restore points messes up all of them. The protection persists even after CWM is removed, so when switching recoveries, all backups need to be deleted in CWM, and all allocated space freed using the "free allocated space" option in the backup and restore menu.
EDIT: To point out the obvious, there would be no need for a "free allocated space" option in CWM if the space weren't protected.
Well, that's stupid. With TWRP I can simply go inside the folder and delete the backups (without the need of booting into recovery and deleting them from there).
Calling it stupid is a bit harsh, and besides, Koush probably will disagree with you.
By default CWM is set to do incremental backups and does this as a space-saving feature. For example purposes let's say a nandroid backup is 2GB. Using the standard .TAR method four nandroid backups would take up 8GB. Switch to .DUP and those same four backups may only take 3GB. This is because .DUP only backs up the files that have changed between the current system and the previous backups, rather than backing up the entire partition. Since CWM in .DUP doesn't back up the entire partition when making its backups, it's vitally important that the backups be protected. Otherwise, deleting an older backup makes it impossible to restore any later backups.
The example I used in my other discussion to illustrate this was four backups, labeled A through D. A is the master backup and B through D are the incremental backups. If the space wasn't protected, deleting backup C in a file manager would render backup D invalid because of missing files. Naturally, deleting backup A would render all subsequent backups invalid, as it is the master backup.
In CWM it is possible to switch from .DUP to .TAR and thus stop CWM from allocating space for backups. The OP didn't do that, which is why his space disappeared even after switching to TWRP. There may be a manual method of removing the allocation through a terminal, but it's simply easier to restore CWM, delete the backups, free the space, then switch back to TWRP.