andoird213
Android Expert
Wow. I would do almost anything to have this work with TWRP. http://forum.xda-developers.com/showthread.php?t=1620255 *sigh*
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Wow. I would do almost anything to have this work with TWRP. Online Nandroid Backup / Nandroid Backup without re-booting - xda-developers *sigh*
First of all, I think you should have started a new thread for this so we don't hijack this one. (MOD!)
Second, I don't see why you can't do this if you have a device with lots of ram and at least a dual core cpu. My concern would be if you have TWRP instead of CWM, that might break it. There are apps that can create an icon and run a script. The problem is how to add a custom name, but that's something that can be done later.
That thread is old enough where we should know by now if there are issues when restoring those nandroids.
Still reading, thanks for the post. Think I need to try this this weekend.![]()
Just thought it could turn into a big thread if it works. I know I appreciate the heads up and want to check it out.Not hijacking! Just something I read and wanted to mention briefly..and yes, the "if you have TWRP instead if CWM, that might break it," that's what I'm saying, I wish it would work
How did you manage to remount /data read-only without hosing the entire system?
If you're not mounting /data read-only prior to backing it up you're always at a significant risk of having a corrupted backup. If one of the databases are getting written to at the same time it gets backed up it'll likely result in a corrupt DB. It usually won't happen but it's not possible to ensure that it doesn't.
Since you can't use the device during a backup (unless you want your backup to be in an unpredictably inconsistent state due to changes being made to the filesystem after parts of it are backed up but not the whole thing), it's safest to just do it from recovery anyway. Shortcuts like this lead to users screwing up their device, and a user will spend FAR more time recovering when the backup goes wrong than they will by performing a backup in recovery, which ensures a clean backup due to the filesystem not being modified at any point during the backup (Unless you do something silly like mucking around in an ADB shell while the backup is going.)
Anyway, the most common use case for a CWM backup is immediately prior to flashing something new in recovery - so you need to be in recovery anyway.