Android Tablets Forum banner
1 - 2 of 2 Posts

· Registered
Joined
·
18 Posts
Code:
adb pull /system <location to back up files to>
example in your adb directory
Code:
md backup
then
Code:
adb pull /system backup
The Novel's files from /system will be copied to the "backup" directory.
 

· Registered
Joined
·
18 Posts
You are correct, we can't zip it up and go through the normal firmware update this way. I believe the easiest way to backup the firmware to be able to restore is do dd, the partition and restore it.I'm new to Android, so I don't know how to package and sign a rom yet.The other post is not linux based, I created the script to be OS agnostic. I used the Novel shell to echo to the files. This way I do not have to use a batch file and the script because OS agnostic. The user can just cut and paste into either a DOS shell or a Linux terminal and the script will still be created on the Device.I didn't do a push, I used the ADB shell to echo the commands to the file. The root user on the sdcards umask had execute permissions, so I didn't need to chmod the scripts to give them execute permissions.Hope that clarifies it.[quote name='clockworx;16617]Yeah' date=' that's what I was going to say, but I'm not sure if he can necessarily restore from that without bundling it up and signing it in an update.zip, right? From your other posts, it sounds like your working with Linux....do you happen to know if adb shell keeps the the correct file permissions when pushing from linux? I'm currently using Windows, and everything I push over gets reset to root permssions without proper chmod, which I have to go and fix after the fact. So if I push over a "backup" I will lose "sh" permissions shortly thereafter.[/QUOTE']
 
1 - 2 of 2 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top