Database Users

nandroid on multiple devices?

Think this may be my first post...thanks to all the devs out there for making things happen! Consider myself an above average user, though I don't really have the knowledge to code a ROM (though I'm sure I could tackle it if I put my mind to it). I just very good at following instructions and can reasonably trouble shoot if things go wrong.
Tried doing a search for this & came up a little blank...could have been I didn't know exactly what to search for. In any case, my question is about nandroid backups. Currently on a CDMA Hero "with Google" rooted & running RegawMOD v2.0.1...PRI 1.70_003...PRL 60663...RA-heroc-v1.6.2 recovery. My wife's phone (for all intents & purposes) is exactly the same, however, I'm the technical one here and have spent a lot of time tweaking my phone. Once I get my phone exactly how I want it, could I flash my nandroid to her Hero to save time in tweaking hers? Or is the nandroid backup tied to one unique piece of hardware/phone #/google log-in?

Im pretty sure that's how droid users share roms, via nandroid.

u can do it, i have done it...a while back the first week i had my hero i bricked it, but i had a nandroid backup. After i got a new phone i rooted it and restored with a nandroid backup worked perfect.

Thanks...and just one more question. I was actually doing a Google search on this one & couldn't find one concrete, concise, answer. In the recovery image, I have 3 different backup choices (Nand, Nand+ext, BART). It's my understanding that Nandroid vs. BART is essentially 2 different ways of doing the same thing...with the ext portion being useful if you are using a2sd (which I'm not using yet). The first choice of Nand backup should make a snapshot of my entire system (ROM, apps, settings, etc...everything on the phone itself, not installed to SD), right?
Ultimately, what I'm trying to accomplish is making a snapshot of my entire phone, mirroring it onto my wife's and then doing some minor tweaks to make it her's (i.e. change the google log-in to her's).
*edit*
n/m, found it in the root cheatsheet. Nand = onboard system, Nand+ext = onboard system + a2sd.
Still not exactly sure what the benefit of BART is, though.

yeah your correct, bart is just a alternative....personally i always use nandroid. Just use nandroid, make a nandroid backup then mount your sd to your computer. Open the nandroid folder, then you will see something like HT.... folder open it. Then you will see all your different nandroids, copy the one of your choice to your desktop. Mount your wife's go to the same place paste the folder there. Boot into recovery home+power nandroid restore tada you done go in change the settings you need to (gmail account)

Does nandroid backup also restore the PRI and PRL or does it leave that untouched?

dkaile said:
Does nandroid backup also restore the PRI and PRL or does it leave that untouched?
Click to expand...
Click to collapse
It should leave it untouched. Though it has a chance to change your pri. I dont know much about it. As long as you flash the most current roms we have know, it will leave it untouched.

Flashing a new ROM on rooted Eris and other questions

I know there are tutuorials for this. I found a few and most of them either expect me to fully understand adb shell commands or understand linux, of which I do very little. I have the rooted 2.1 OTA on my Eris currently. I wanted to start trying out other ROMs on the phone. I've done a nandroid backup, but from searching around I read that it doesn't back up apps or user data, to an extent.
1) I get the error message "Run Nandroid +ext via adb!" when trying to backup everything using nandroid + ext. I also get the same message when trying to use a BART backup.
2) What is the difference between the two? (BART and nandroid)
3) What are the adb commands to use these?
4) How can I make a complete "screenshot" of my phone to restore everything back to its current state? Is this what BART/nandroid+ext do? I need to be sure in case I need the phone restored to working status very quickly.
5) Is apps2SD really that useful? I only run like 45 apps.
6) Does overclocking have any downsides? (I know the phone can lock up if you push it too far, so other than this.)
I think that's it. I've softmodded consoles and a few random electronics but phones are a new one. Sorry if half of these have been answered. I haven't been able to find much about this stuff in laymen's terms.

Raikalo said:
I know there are tutuorials for this. I found a few and most of them either expect me to fully understand adb shell commands or understand linux, of which I do very little. I have the rooted 2.1 OTA on my Eris currently. I wanted to start trying out other ROMs on the phone. I've done a nandroid backup, but from searching around I read that it doesn't back up apps or user data, to an extent.
1) I get the error message "Run Nandroid +ext via adb!" when trying to backup everything using nandroid + ext. I also get the same message when trying to use a BART backup.
2) What is the difference between the two? (BART and nandroid)
3) What are the adb commands to use these?
4) How can I make a complete "screenshot" of my phone to restore everything back to its current state? Is this what BART/nandroid+ext do? I need this in case the ROM doesn't work/I screw something up.
5) Is apps2SD really that useful? I only run like 45 apps.
6) Does overclocking have any downsides? (I know the phone can lock up if you push it too far, so other than this.)
I think that's it. I've softmodded consoles and a few random electronics but phones are a new one. Sorry if half of these have been answered. I haven't been able to find much about this stuff in laymen's terms.
Click to expand...
Click to collapse
1) if you get that message on restore 99% of the time that means your battery is low.
2) I have no idea what the difference is, but NAND always works great for me.
3) You would need to flash the parts of a NAND Backup via fastboot (correct me if I'm wrong). It's a pain in the ass for the most part.
4) NAND backup and restore makes a "screenshot". It will turn your phone to exactly how it was when u made the backup (make sure you wipe first though )
5) APP2Sd is only if you feel you need it. I use it, but is not required at all. If you have enough free space that why bother, but if not it's good utility to have available.
6) OC is awesome only downside is battery and that is barely their. You can also bork your phone if you set it to high. Some phones can handle over 710 some cannot. The only way you will know for yourself is if you try!
Go for the aloysius rom if you need a or want a new rom to flash

Awesome, thanks. I'll check that ROM out and see if I can get to flashing after work.
1) This isn't when restoring, it's when I'm trying to actually make a backup. Nandroid works fine, but nandroid +ext and BART both give me errors about adb.
Any other suggestions/answers?

Oh, one more question I forgot.
Code:
adb pull data/app desktop
Was using this to pull apps from my phone to the computer. After I did, I couldn't find them on the computer. I assumed they'd go to the desktop, but apparently I was wrong? Where are they?

Raikalo said:
Awesome, thanks. I'll check that ROM out and see if I can get to flashing after work.
1) This isn't when restoring, it's when I'm trying to actually make a backup. Nandroid works fine, but nandroid +ext and BART both give me errors about adb.
Any other suggestions/answers?
Click to expand...
Click to collapse
You only have to do nandroid without the +ext. You only use ext when you have a partition on your sd card (for running apps2sd). Try a plain ole nandroid. As far as bart goes, I've never heard of anybody using it.

is there a way to name the nandroid backups so you know which one is which when you go to restore? or can you only have one at a time?

duscar said:
is there a way to name the nandroid backups so you know which one is which when you go to restore? or can you only have one at a time?
Click to expand...
Click to collapse
You can have as many as your sd card will hold. They will be in folder on your sd card called "nandroid" and you can rename however you see fit, just make sure you Do Not put any spaces in the name.

rentjr said:
You can have as many as your sd card will hold. They will be in folder on your sd card called "nandroid" and you can rename however you see fit, just make sure you Do Not put any spaces in the name.
Click to expand...
Click to collapse
if i rename them there, does it rename them in the restore menu so i know which is which?

duscar said:
if i rename them there, does it rename them in the restore menu so i know which is which?
Click to expand...
Click to collapse
yes
10char

Okay, if a nandroid backup makes a total system image incl. apps and user data, I should be good to go.
Still wondering about how to pull apks and where they go. Any ideas there? See one of my above posts about it.
Also, I need to backup my ENTIRE SD card before a wipe, right?

Dalvik Cache, CM7, and backups (general questions)

I have three basic questions I've been wondering about for a while and in my research, I couldn't find consistent answers so I though I'd ask a community I trust. I have a rooted Kindle Fire running Android 2.37, CM7 ROM and GoEx Launcher.
1. What is dalvik cache? Why does it take up so much space? Can I delete it?
2. Is there a more stable ROM com Kindle that anyone prefers over CM7? I have problems with my device rebooting frequently for no apparent reason and sometimes freezing up to where my ADB won't even recognize it.
3. What's your opinion on keeping a backup on your SD card at all times? It takes up about 1G of space. I've never had to use it yet, but I can see where it would be extremely helpful if I accidentally do something stupid and need to reboot into recovery and restore my device. I also keep backups of my Kindle on my PC, but the question I guess, is whether its worth the 1GB of space just in case or if I'd be able to push a backup from my PC to the device if I ever need it. What do you think? Do you keep a full backup on your device at all times?
Any opinions, answers, or helpful tie bits would be appreciated. Thanks!

nogloww said:
I have three basic questions I've been wondering about for a while and in my research, I couldn't find consistent answers so I though I'd ask a community I trust. I have a rooted Kindle Fire running Android 2.37, CM7 ROM and GoEx Launcher.
1. What is dalvik cache? Why does it take up so much space? Can I delete it?
2. Is there a more stable ROM com Kindle that anyone prefers over CM7? I have problems with my device rebooting frequently for no apparent reason and sometimes freezing up to where my ADB won't even recognize it.
3. What's your opinion on keeping a backup on your SD card at all times? It takes up about 1G of space. I've never had to use it yet, but I can see where it would be extremely helpful if I accidentally do something stupid and need to reboot into recovery and restore my device. I also keep backups of my Kindle on my PC, but the question I guess, is whether its worth the 1GB of space just in case or if I'd be able to push a backup from my PC to the device if I ever need it. What do you think? Do you keep a full backup on your device at all times?
Any opinions, answers, or helpful tie bits would be appreciated. Thanks!
Click to expand...
Click to collapse
I can help with #3.. Another option instead of a backup would be just put a ROM on your SDcard.. that's what I do.

But if I had to restore my device, I would only be able to flash the ROM again and would loose all my settings, apps, etcetera, right?
Sent from my Kindle Fire using Tapatalk 2

nogloww said:
But if I had to restore my device, I would only be able to flash the ROM again and would loose all my settings, apps, etcetera, right?
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
I believe what fiddlefaddle meant is that in case something happens (e.g. his current rom won't boot) and he needs to start over - he can install the rom he has on the sd card. That's of course assuming he can still access recovery. Once that's done he'll put a backup he probably keeps on his PC back on the sdcard and restores it.
I actually like that approach - since my kids KF backup is about 1GB ... lots of games...

Ooh, yeah that does make sense. My back up is about 1GB too and there's not a ton of space on the Kindle Fire to start with. Could the same be done with Titanium Backup? Just keep the app, but put the backup file on a PC and transfer it over only when you need it?
Sent from my Kindle Fire using Tapatalk 2

twa_priv said:
I believe what fiddlefaddle meant is that in case something happens (e.g. his current rom won't boot) and he needs to start over - he can install the rom he has on the sd card. That's of course assuming he can still access recovery. Once that's done he'll put a backup he probably keeps on his PC back on the sdcard and restores it.
I actually like that approach - since my kids KF backup is about 1GB ... lots of games...
Click to expand...
Click to collapse
Exactly
---------- Post added at 03:39 PM ---------- Previous post was at 03:34 PM ----------
nogloww said:
Ooh, yeah that does make sense. My back up is about 1GB too and there's not a ton of space on the Kindle Fire to start with. Could the same be done with Titanium Backup? Just keep the app, but put the backup file on a PC and transfer it over only when you need it?
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
To tell you the truth I really don't know lol... Another option would be just to backup your data in TWRP and move it to a PC.. Not the ROM JUST the data..

Can't delete or restore Clockworkmod backup

EDIT: Just realized I posted this to the S4 forum instead of the S3. Should I post again in the proper forum, or wait for the thread to be moved?
Hi,
After running the latest stable Cyanogenmod for a little while, I've decided to go back to stock. I've flashed custom roms and used CWM to restore my backup before, so I was comfortable with it. But this time, CWM couldn't find my backup. Eventually I figured out that it (and all my other original files) are in /0/0/0/0/clockworkmod. I understand this is because of 4.2's changes, but I don't know why I have so many 0 folders. Perhaps from flashing MIUI and CM so many times?
Anyway, I updated CWM to be compatible with 4.2, but also tried moving the clockworkmod folder to the root of the internal memory. Something went wrong, though, because although CWM can see the backup, it always fails at restoring /data. I noticed that instead of moving the clockworkmod folder, Windows had only copied them - perhaps partially. My phone now only has about 1GB of internal memory left due to the multiple folders, and I can't delete, move, or copy any of them. I do have my CWM backup copied to my computer, but not the blobs folder, so I'm worried that if I somehow manage to reformat my device, I won't be able to restore it without the blobs.
Also, I should mention that I'm not able to use adb, it tells me it can't find the device. I'm running Windows 8 64-bit.
If anyone has any ideas, I'd really appreciate it. This is really frustrating.
Update: After a bit of waiting, I finally managed to copy my blobs and backup folders to my desktop and got adb working, so I reformatted the entire device and managed to restore it. No idea why I was having trouble before, but at least it's working again.

Vertimyst said:
EDIT: Just realized I posted this to the S4 forum instead of the S3. Should I post again in the proper forum, or wait for the thread to be moved?
Hi,
After running the latest stable Cyanogenmod for a little while, I've decided to go back to stock. I've flashed custom roms and used CWM to restore my backup before, so I was comfortable with it. But this time, CWM couldn't find my backup. Eventually I figured out that it (and all my other original files) are in /0/0/0/0/clockworkmod. I understand this is because of 4.2's changes, but I don't know why I have so many 0 folders. Perhaps from flashing MIUI and CM so many times?
Anyway, I updated CWM to be compatible with 4.2, but also tried moving the clockworkmod folder to the root of the internal memory. Something went wrong, though, because although CWM can see the backup, it always fails at restoring /data. I noticed that instead of moving the clockworkmod folder, Windows had only copied them - perhaps partially. My phone now only has about 1GB of internal memory left due to the multiple folders, and I can't delete, move, or copy any of them. I do have my CWM backup copied to my computer, but not the blobs folder, so I'm worried that if I somehow manage to reformat my device, I won't be able to restore it without the blobs.
Also, I should mention that I'm not able to use adb, it tells me it can't find the device. I'm running Windows 8 64-bit.
If anyone has any ideas, I'd really appreciate it. This is really frustrating.
Update: After a bit of waiting, I finally managed to copy my blobs and backup folders to my desktop and got adb working, so I reformatted the entire device and managed to restore it. No idea why I was having trouble before, but at least it's working again.
Click to expand...
Click to collapse
Glad you got it worked out..

[Q] Nook loses track of glow light status

This weekend my Nook Simple Touch with Glowlight has begun losing track of the status of the light. Turning the light on works fine by all means and the light works normally. After you exit the Glowlight dialog, if you go back in to adjust the intensity of the light or turn it back off, it indicates that the light is "off" even when it is "on". At this point, in order to do anything, I have to check the "on" box again before I can change the intensity of the light or turn it off.
The device is rooted using my own combination of "NookManager" and "Tweaked Modded ROM". I have not made any changes to the device in the last month
Has anyone run across this before? Is there a solution? .

@David0226,
That is so interesting that you're having that problem, because I'm having a similar one! Thread: A minor bug/problem?
I haven't currently come across a fix, but I'm working on it. I'll let you know when/if I find one.

I know from several different threads where using sqlite is mentioned that the Nook saves certain pieces of information in database files. Perhaps the database that saves glowlight status is corrupt on both of our Nooks. While our issues appear to be exactly the opposite of each others, they essentially are the same. The Nook is losing track of glowlight status.
Perhaps somehow rebuilding the correct database would fix the issue. The problem is I don't know which database nor how to rebuild it.
Perhaps Renate could help if this is the case as she seems to appear in a large number of the threads relating to Nook databases.
If I don't get an answer by tomorrow, I think I will return my Nook to stock and follow Renate's Minimal rooting - back to basics thread. I really should be able to do everything I actually use with just basic root access.

David0226 said:
I know from several different threads where using sqlite is mentioned that the Nook saves certain pieces of information in database files. Perhaps the database that saves glowlight status is corrupt on both of our Nooks. While our issues appear to be exactly the opposite of each others, they essentially are the same. The Nook is losing track of glowlight status.
Perhaps somehow rebuilding the correct database would fix the issue. The problem is I don't know which database nor how to rebuild it.
Perhaps Renate could help if this is the case as she seems to appear in a large number of the threads relating to Nook databases.
If I don't get an answer by tomorrow, I think I will return my Nook to stock and follow Renate's Minimal rooting - back to basics thread. I really should be able to do everything I actually use with just basic root access.
Click to expand...
Click to collapse
Is one problem with the GlowLight really worth all of the data you have accumulated since you first rooted?
I mean, I know it's not really my business, but I don't think I'd go so far as to factory reset and reroot if I came across that problem.
Just my personal opinion. I do hope we can get a little help from @[color=green][u]Renate NST[/u][/color] in here.

Actually, 95% of the data I have accumulated since rooting is on an SDcard. So after re-rooting, I can simply put the SDCard back in and my data will be there.
One reason I am considering this is that since rooting the device, I have installed many apps and edited many system files without keeping a good record of what I have done. So I really don't know where I am at. If the Nook ran on Windows I would have had to re-install months ago.
I have found that there is really very little I actually use. Lightning Launcher and ALReader is pretty much it. I have tablets, so I don't need/want to turn my Nook into one.

David0226 said:
Actually, 95% of the data I have accumulated since rooting is on an SDcard. So after re-rooting, I can simply put the SDCard back in and my data will be there.
One reason I am considering this is that since rooting the device, I have installed many apps and edited many system files without keeping a good record of what I have done. So I really don't know where I am at. If the Nook ran on Windows I would have had to re-install months ago.
I have found that there is really very little I actually use. Lightning Launcher and ALReader is pretty much it. I have tablets, so I don't need/want to turn my Nook into one.
Click to expand...
Click to collapse
Ah, then there's the difference between you and I. I don't have any other tablets, so that's why I use my NTG as a full tablet.
A good tip I'd recommend to you, if you're currently doing any "risky" modding (like me), make a fresh Noogie backup once a week or so. That way, if you do soft-brick my Nook, you can really restore to the way you were recently.

I typically use NookManager to make a backup before each "risky" mod. If you connect your Nook to your computer via USB while booted into NookManager, you can see the backup partition and copy off the backup files. I then rename them so that I can copy them back and restore from them if needed. I find restoring using NookManager much easier that restoring a Noogie backup.

David0226 said:
I typically use NookManager to make a backup before each "risky" mod. If you connect your Nook to your computer via USB while booted into NookManager, you can see the backup partition and copy off the backup files. I then rename them so that I can copy them back and restore from them if needed. I find restoring using NookManager much easier that restoring a Noogie backup.
Click to expand...
Click to collapse
Yeah, I used to use NookManager for backing up, too, but after looking at how the Noogie method vs. the NookManager method works, I discovered that the Noogie method actually makes a more complete backup than the NookManager method.
Plus, for some reason whenever I try to use the NookManager method, I get "Backup failed", so I can't do it anyway.

I bit the bullet and restored to factory default and followed Renate's Minimal rooting - back to basics instructions. It did take care of my glowlight problem.
I discovered that for my situation this is a perfect method. It allows me to make changes and install apps using ADB over WIFI, yet essentially I only have 'root' when using ADB. I can make all the changes I want over the ADB connection but nothing has root permissions if I (or one of my family) am using the Nook "normally". Thus, I have less chance of messing anything up during "normal" operation.
(I also carefully documented everything I did so I now know where I am at.)