Related
This is a CWM zip which intended purpose is to make creating heimdall one click roms easier.
It will backup partitions using dd and put them in a folder on your internal SD card labeled partition-backup. You can then use these to create heimdall one-click versions of your own rom.
The partitions backed up are as follows:
Captivate Stock based roms:
/system (/dev/block/stl9)
/dbdata (/dev/block/stl10)
/cache (/dev/block/stl11)
kernel (/dev/block/bml7)
modem (/dev/block/bml12)
param.lfs (/dev/block/stl6)
Captivate MIUI/Cyanogenmod based roms:
/system (/dev/block/mtdblock2)
/datadata (/dev/block/mtdblock6)
/cache (/dev/block/mtdblock3)
/radio (/dev/block/mtdblock5)
kernel (/dev/block/mtdblock0)
recovery (/dev/block/mtdblock1)
modem (/dev/block/mtdblock5)
The data partition is not included.
This is not intended to be a backup for your Captivate, although it could be used as one. Again, it's intended for Heimdall rom creation.
For backups, it is preferable to use CWM. I personally, really like the 5.0.2.6 version by mtcarey as it tars up the data rather than dd's the entire partition which saves a lot of space (like the /data partition for example).
DISCLAIMER: I am in no way to be held responsible for what you do to your device. If you use it, whatever the consequences, they are your responsibility.
Now with that being said, this script doesn't do anything destructive but simply copies the partitions to the internal SD card for later use.
Here are the links:
Captivate Stock based - http://db.tt/tPGn42Pi
MIUI/CyanogenMod based - http://db.tt/rwy5WIel
Let me know if you have any issues with the scripts.
My bad...
10 char
b-eock said:
You have to include data on stock ROM's as it will run the check when it installs on reboot... it will fail because of the missing data partition..., so you might wanna put that into the SCRIPT!
Click to expand...
Click to collapse
you will only get the error if you re-partition
b-eock said:
You have to include data on stock ROM's as it will run the check when it installs on reboot... it will fail because of the missing data partition..., so you might wanna put that into the SCRIPT!
Click to expand...
Click to collapse
You don't need /data...
dbdata is the one that gives that error if you re-partition.
Have you given thought to writing a cwm script to backup efs, or adding it to this script?
mrhaley30705 said:
Have you given thought to writing a cwm script to backup efs, or adding it to this script?
Click to expand...
Click to collapse
I could be wrong on this point but as I understand it the IMEI number is contained there so this isn't probably the best idea.
I could add a separate script for it but I will need to confirm that this wouldn't cause issues for people replicating an IMEI number.
I was thinking of using it as a way to backup an efs.
Understood. I'll put one up later today. In the meantime, you can always copy the folder to your sdcard for safe keeping.
backing up of both EFS and Data, would be nice for PERSONAL backups, make a note not to redistribute efs or data in the heimdall one click packages.
any of your passwords/saved information will be in data..... unless you backup data immediately after flashing/pushing apps BUT before android OS setup...
efs is still a DO NOT DISTRIBUTE.
Tried using partition backup and it didn't make the backup file, or i can't find it.
in a folder on your internal SD card labeled partition-backup
Click to expand...
Click to collapse
how long did it take? a while? it should if it did something.
No, just a couple of second.
Edit
Mount system first?
It should take a minute or so to complete. Once done, reboot back into the OS and there should be a folder /sdcard/patition-backup/.
Within this folder you should have multiple images all ending in .rfs. Really they would typically end in .img but I had it save the images using an rfs extention to facilitate things with heimdall as that's what it expects.
What version of Android are you running?
MIUI. 1.11.18 w/Neo 17r18.
TRusselo said:
backing up of both EFS and Data, would be nice for PERSONAL backups, make a note not to redistribute efs or data in the heimdall one click packages.
any of your passwords/saved information will be in data..... unless you backup data immediately after flashing/pushing apps BUT before android OS setup...
efs is still a DO NOT DISTRIBUTE.
Click to expand...
Click to collapse
Agreed. /data has all your personal data and efs has your IMEI. You don't want to distribute either of these. That is primarily why I left them out of the script. Don't forget you can either copy the entire efs folder or just zip it up and save it somewhere off your phone as a backup. If you are just looking to backup the phone, CWM is much more efficient at backing it up, IMO.
mrhaley30705 said:
MIUI. 1.11.18 w/Neo 17r18.
Click to expand...
Click to collapse
Hmmm... I haven't tested it on either MIUI or Cyanogenmod. They may use a different partioning scheme. Can you please copy/paste the response of typing 'mount' from a shell?
( adb shell, then just simply type 'mount' from there )
How's this
Ok, I see the problem. It appears the MIUI and Cyanogenmod use /dev/block/mtdblock* whereas stock Captivate based roms use /dev/block/mmcblk*.
I'll see about making one for your setup.
Thanks for testing this!
No problem.
Hello everyone,
Yesterday evening I bought a Nook Touch with Glow, went home, backed it up, or so I thought (my backup in retrospect is only 75mb and when I restore it, it does try to boot but says "Install Failed"), then proceeded to install android with Glownooter. Most of the programs I tried to launch closed after a few seconds (though I followed the instructions and installed both .zip parts), so I was going to restore and try again.
Following the restore instructions, I blew out the entire Nook partition table in preparation and now I feel I am screwed without external help. I tried everything last night for three hours...
Could anyone upload a stock .img file for me please? I really want to use the device and don't think it would be right for me to return it to the store for an exchange because of a mistake I made. Currently my SD card has nooter on it, but last night I had CWM open with the factory.zip someone posted and tried installing that zip to no avail... I even tried the n2T-Recovery_0.2.
Thank you.
trimalchioinwestegg said:
Hello everyone,
Yesterday evening I bought a Nook Touch with Glow, went home, backed it up, or so I thought (my backup in retrospect is only 75mb and when I restore it, it does try to boot but says "Install Failed"), then proceeded to install android with Glownooter. Most of the programs I tried to launch closed after a few seconds (though I followed the instructions and installed both .zip parts), so I was going to restore and try again.
Following the restore instructions, I blew out the entire Nook partition table in preparation and now I feel I am screwed without external help. I tried everything last night for three hours...
Could anyone upload a stock .img file for me please? I really want to use the device and don't think it would be right for me to return it to the store for an exchange because of a mistake I made. Currently my SD card has nooter on it, but last night I had CWM open with the factory.zip someone posted and tried installing that zip to no avail... I even tried the n2T-Recovery_0.2.
Thank you.
Click to expand...
Click to collapse
The partition table of the NSTG is the same as the NST.
I am in the same situation, and so far I have not had a huge success reviving mine but perhaps this thread could assist you in the right direction. Remember to save /rom information before trying anything
http://forum.xda-developers.com/showthread.php?t=1805936
good luck!
srgarfi said:
The partition table of the NSTG is the same as the NST.
I am in the same situation, and so far I have not had a huge success reviving mine but perhaps this thread could assist you in the right direction. Remember to save /rom information before trying anything
http://forum.xda-developers.com/showthread.php?t=1805936
good luck!
Click to expand...
Click to collapse
I know - I read that thread front to back last night and made no progress either.
Am I correct to assume that a backup image from someone would restore all partitions and completely solve our problem?
If so, if someone would upload an image in virgin state it would solve problems for everyone. I'm completely surprised that such an image is so elusive.
Anybody's full backup image will wipe out all your personalized data in /rom and /factory/rombackup.zip.
Generally, AFAIK, all these Nooters can screw up your Nook but not re-partition it or format it.
Make an effort to get to get your /rom back.
Renate NST said:
Anybody's full backup image will wipe out all your personalized data in /rom and /factory/rombackup.zip.
Generally, AFAIK, all these Nooters can screw up your Nook but not re-partition it or format it.
Make an effort to get to get your /rom back.
Click to expand...
Click to collapse
Is /rom an item unique to each device, or are you worried about me losing books/login information in "personalized data"? I had done nothing with my device except get past initial startup when I rooted it, so I have no personal items (books or otherwise) invested. I'm sorry if this is a silly question, but I don't understand.
Edit: Also, I used the magic (something) application to delete all partitions from the nook prior to the restore because it would not let me restore until then. If I had known my backup was invalid I would never have done that.
Attached is an image of what my restore contains. It does try to boot, but then says "Install Failed."
Note there is a romrestore.zip.
trimalchioinwestegg said:
I know - I read that thread front to back last night and made no progress either.
Am I correct to assume that a backup image from someone would restore all partitions and completely solve our problem?
If so, if someone would upload an image in virgin state it would solve problems for everyone. I'm completely surprised that such an image is so elusive.
Click to expand...
Click to collapse
Yes, that's the idea.
But as Renate mentions, that would overwrite you /rom partition with invalid data from another device (mac address, serial, and things like that).
But in the same situation I managed to salvage my /rom partition, so if I ever install such an image from someone elses' NSTG i coudl overwrite /rom with the data from my own device.
It could be also possible to generate such an image of an NSTG and then carefully unpack, delete the most sensitive files from /rom and repack the image to share. That way no sensitive infromation would be shared/compromised.
If you happen to stumble on such an image, please let me know.
BTW, those /boot files you have, could you pack them in a zip file and send it to me or post it here in the forums? I formatted my /boot partition and I could make good use of yours (no sensitive/personal information contained in there)
srgarfi said:
Yes, that's the idea.
But as Renate mentions, that would overwrite you /rom partition with invalid data from another device (mac address, serial, and things like that).
But in the same situation I managed to salvage my /rom partition, so if I ever install such an image from someone elses' NSTG i coudl overwrite /rom with the data from my own device.
It could be also possible to generate such an image of an NSTG and then carefully unpack, delete the most sensitive files from /rom and repack the image to share. That way no sensitive infromation would be shared/compromised.
If you happen to stumble on such an image, please let me know.
BTW, those /boot files you have, could you pack them in a zip file and send it to me or post it here in the forums? I formatted my /boot partition and I could make good use of yours (no sensitive/personal information contained in there)
Click to expand...
Click to collapse
I'm throwing in the towel because my /rom partition is gone and I understand all of that now. Tonight I will exchange for another (against my conscience) and make a proper backup before I do anything going forward.
In my research I found this:
search.4shared.com/postDownload/2YsbIxQJ/nook_glow_partition_files__023.html
It is all of the files except rom, and you will find the boot files in the 0 directory.
Good luck, and thanks for the help everyone.
Did you check both the p1 (/boot) and p3 (/factory) partitions to see if you had rombackup.zip?
Of course check p2 (/rom) for devconf.
Try repartitioning your Nook. You'll need CWR on an SD card with ADB or Noogie and Linux tools.
The script nookpart.sh is in my signature.
trimalchioinwestegg said:
I'm throwing in the towel because my /rom partition is gone and I understand all of that now. Tonight I will exchange for another (against my conscience) and make a proper backup before I do anything going forward.
In my research I found this:
search.4shared.com/postDownload/2YsbIxQJ/nook_glow_partition_files__023.html
It is all of the files except rom, and you will find the boot files in the 0 directory.
Good luck, and thanks for the help everyone.
Click to expand...
Click to collapse
Are you sure you can't recreate the partition table and mount /rom to get access to your files?
It is explained in the thread I mentioned. If so, then it would be fairly easy to recover your device.
Be careful when returning the NSTG to B&N, some of the operations performed are not covered in the warranty and they could want to charge you....
Anyway, thanks for that pointer! I'll see if I can use it to revive my NSTG
srgarfi said:
Are you sure you can't recreate the partition table and mount /rom to get access to your files?
It is explained in the thread I mentioned. If so, then it would be fairly easy to recover your device.
Be careful when returning the NSTG to B&N, some of the operations performed are not covered in the warranty and they could want to charge you....
Anyway, thanks for that pointer! I'll see if I can use it to revive my NSTG
Click to expand...
Click to collapse
Good thing I bought it at Staples.
Renate NST said:
Did you check both the p1 (/boot) and p3 (/factory) partitions to see if you had rombackup.zip?
Of course check p2 (/rom) for devconf.
Try repartitioning your Nook. You'll need CWR on an SD card with ADB or Noogie and Linux tools.
The script nookpart.sh is in my signature.
Click to expand...
Click to collapse
I fired up CWR but saw no USB activity on the computer (for ADB). Could you please tell me how to get ADB running? I did download your script and was interested in trying, but only got USB Disk mode on Noogie (which I couldn't get ADB to work with).
Thank you!
ADB on CWR can be a bit tricky.
It seems like the daemon dies sometimes on disconnecting and stuff.
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/ADB
Boot it up on CWR first, then connect the USB cable.
In Windows it should show both Removable storage and ADB on the taskbar.
Code:
adb usb
adb shell
Make sure that you have the CWR with USB ADB and not Wifi ADB.
trimalchioinwestegg said:
I fired up CWR but saw no USB activity on the computer (for ADB). Could you please tell me how to get ADB running? I did download your script and was interested in trying, but only got USB Disk mode on Noogie (which I couldn't get ADB to work with).
Thank you!
Click to expand...
Click to collapse
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
And search for a file named "ADB + Fastboot + Drivers.zip" in the forum.
With all that you can get ADB running in a Windows machine in no time.
Renate NST said:
ADB on CWR can be a bit tricky.
It seems like the daemon dies sometimes on disconnecting and stuff.
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/ADB
Boot it up on CWR first, then connect the USB cable.
In Windows it should show both Removable storage and ADB on the taskbar.
Code:
adb usb
adb shell
Make sure that you have the CWR with USB ADB and not Wifi ADB.
Click to expand...
Click to collapse
Forgive me, but where would I find CWR with USB ADB? I currently have CWM-based Recovery v5.0.2.7 from the Glownooter thread. The 2gb image.
At the bottom of the black screen I have some errors, though:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Nothing reacts when I plug in USB.
srgarfi said:
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
And search for a file named "ADB + Fastboot + Drivers.zip" in the forum.
With all that you can get ADB running in a Windows machine in no time.
Click to expand...
Click to collapse
I did successfully install ADB and the Android SDK earlier, but it is not running on my Nook under CWM and I do not know how to get it on there. The guide says "The Nook must specifically have an adbd daemon running on either WiFi or USB. The stock Nook has no adbd."
Do you know how?
trimalchioinwestegg said:
I did successfully install ADB and the Android SDK earlier, but it is not running on my Nook under CWM and I do not know how to get it on there. The guide says "The Nook must specifically have an adbd daemon running on either WiFi or USB. The stock Nook has no adbd."
Do you know how?
Click to expand...
Click to collapse
You should have adb.exe somewhere. From a command window in windows (start menu, execute cmd.exe), go to the path where adb.exe resides and type "adb devices": this will tell if your nook is hooked and accessible.
srgarfi said:
You should have adb.exe somewhere. From a command window in windows (start menu, execute cmd.exe), go to the path where adb.exe resides and type "adb devices": this will tell if your nook is hooked and accessible.
Click to expand...
Click to collapse
I do.
C:\Users\XXXX\AppData\Local\Android\android-sdk\platform-tools>adb usb
error: device not found
C:\Users\XXXX\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
I don't believe ADB is running on the nook, which is currently booted into CWM.
I do see the showing USB Mass Storage Device in device manager, but I cannot access the device as I can in noogie.
You may have the CWR running WiFi ADB (which doesn't make sense to me because you can't select AP).
If you have USB ADB running on CWR you should see on the USB in the taskbar two things, Mass Storage and ADB.
Renate NST said:
You may have the CWR running WiFi ADB (which doesn't make sense to me because you can't select AP).
If you have USB ADB running on CWR you should see on the USB in the taskbar two things, Mass Storage and ADB.
Click to expand...
Click to collapse
How can I make CWR use USB?
http://onlybestandroidapps.com/the-new-multi-user-management-in-android-4-2/
recovery is still looking for backups in mnt/sdcard. filesystem only recognizes mnt/shell/emulated. big issue!!!!!!!!
xkwwwx said:
http://onlybestandroidapps.com/the-new-multi-user-management-in-android-4-2/
recovery is still looking for backups in mnt/sdcard. filesystem only recognizes mnt/shell/emulated. big issue!!!!!!!!
Click to expand...
Click to collapse
Yes, please post this in every 4.2 thread.
They are moved on the drive, as are all files. Recovery's will have to update, it's not the end of the world.
If you need them RIGHT NOW, boot into recovery, adb shell into the device, and go to /data/media/0/TWRP to find your backups. You can copy them to /data/media/TWRP or whatever, that's the absolute path where TWRP is looking.
CWM will be similar, different filenames.
I have no idea what that blog said as it was written by either a robot, a 3rd grader or babelfish.. You decide.
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
**Removed - wait for JCSullins official release**
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
For those not in the know, it is recommended to update your recovery and essential if you plan to update to cm10. This fixes s file system corruption bug that shows up when expanding the partition in preparation for cm10.
Sent from my HP TouchPad using Tapatalk 2
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
"Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here."
Click to expand...
Click to collapse
Open terminal
type
su
umount -o remount,rw /boot
then use es file explorer.
chadster1976 said:
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
Click to expand...
Click to collapse
Rom Toolbox lite will allow you to .
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
I flashed it and now I'm soft bricked. Can't boot into sk8's CWR6, CM10 or anything.
Lesson learned, ask developers before posting there work
Sent from my Galaxy Nexus using xda app-developers app
It likely not the CWM6 that did it but the boot partition full. If you have an extra webos kernel, some moboot themes, TWRP, and then this new larger uImage for CWM you will likely run out of space.
Probably should put that warning here it's pretty important people realize it and/or add a script to remove TWRP, to prevent issues with this zip.
@jcsullins +1 Feedback. Installed your CWM uImage manually. Mounted as mass storage in CWM, copied files, Installed latest CM10 12/05(over older CM10 installed with Acme3), Installed Gapps, Installed Camera Preview 3 patch, Installed WEBCM10, cleared both caches in CWM and noticed no issues during all the processes.
I ACMEU wiped and ACME3'd the whole deal back on w/new recovery. It needed the clean up anyways and I had a NAND from yesterday.
Nice, thanks JC.
Roland Makes oopsy
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Thank you for taking the time to create this great new CWM6. I have been really enjoying the new looks and graphics. I have tested flashing different zips and Roms. I have made and restored Nandroid backups and even restored older CWM5 backups with CWM6. I do this to try and help but sometimes I really step in $#@# trying to help, like with the 4.2gapps.
Sorry about being so anxious to get this out to the public. I have had a lot of complaints about Bricked TouchPads and would like to get the word out about the problem and how to fix/prevent it.
I feel very responsible for the people affected due to me making an install video without knowledge of the corruption issue beforehand.
I wanted to make a video explaining that there was an issue but to fix it they can, Backup, uninstall, reinstall and restore. To prevent future issues I want to included this in my install instructions. They would of course need your New CWM6 to do this and I have been eagerly awaiting this fix.
Sorry about all my stupid mistakes, I get a bit over excited about Tech stuff at times. Please accept my sincerest apologies.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
I'm sorry, but I didn't see your post in Rootzwiki or I would have posted there.
This cwm has worked flawlessly. I haven't had a chance to try all the new features, but the ones I did try worked fine.
Thanks so much for this. The old 5.0.2.6 was starting to show its age. I hope this cwm does away with the sporadic partitioning problems I'd been seeing.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
New Backup Options
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
webdroidmt said:
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
Click to expand...
Click to collapse
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
RolandDeschain79 said:
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
Click to expand...
Click to collapse
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
.dup & .tar enlightenment
webdroidmt said:
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
Click to expand...
Click to collapse
Thank you very much for the detailed response. I’m feeling good now that I am starting to understand the new recovery. I also really liked having those individual .tar backups:good:, I made one for each version of CM. I wonder how .dup backups will affect the free space on my device. I also backup a lot but I did find that i was able to restore the older CWM5 backups without a problem. I will probably just keep the older CWM5 .tars for CM7, CM9 and do my CM10 backing up with the newer .dup. Time to transfer some backups:victory:
Can we maybe get rid of the link in op? Jc has stated this was only for testing, you shouldn't host a devs work without permission, and maybe for the fact of it will soft brick a TP? Just saying....
Sent from my HTC VLE_U using xda app-developers app
Sorry for possibly misunderstanding but is it recommended to use this yet due to possible corruption issues with older versions of CWM or only intended for testing atm? I've been meaning to ACME uninstall the TP and reinstall CM10 clean again and if this newer version of recovery is recommended for flashing I'll throw it on there while I'm at it
Thx JCSullins! :fingers-crossed:
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Hello,
Sorry for that :/
I haven't seen your rootzwiki post and so far I was just willing to help users to install it
easily (seems that was my mistake :x) because after I gave it a try it solved the issues
I was having with the previous CWM one. There is just one thing that disturb me, in
Backup and Restore menu, 'choose backup format' should be rename in something like
"choose default backup format".
That's just my 2cents and besides this all functions work well, thanks for your hard work.
I'll remove the link from the OP post and wait for your public release
Sincerely, menthe.
Has anyone tried the adb sideload yet?
When attempting to sideload I get: * failed to write data 'protocol fault (no status)' *
Any other adb commands I issue are met with "error:closed"
I am stuck here because I don't have a power button to do a hard reset... please someone tell me this function is working and I am just doing something wrong. My TP has a full charge and I don't feel like waiting 8hrs for it to die so it can be reset.
Edit: just took the whole thing apart and pulled the battery
Hello,
I would like to get some help with my SD-Build Android MccM MIUI.
First it started random crashes of the lockscreen. I could power on the display but it kept being black. I only could reset my HD2 and reboot my Android.
Now my Android doesn't boot anylonger. It opens the HTC-Boot-Animation und nothing happens. I waited about an hour.
I replaced the Android-folder on my SD-Card and Android booted again. But my contacts and the apps (their stored data) which I installed after the backup aren't available. With the old version, Android don't boot. If I only replace data.img with my backup, Android boots but without the apps.
My question ist, how do I get the apps-data (e.g savegames) exported from data.img and imported in my backup version?
Could please someone help me?
Greetings Marco
PS: Sorry, my English is a little bit rusty.
Kaschparl79 said:
I replaced the Android-folder on my SD-Card and Android booted again. But my contacts and the apps (their stored data) which I installed after the backup aren't available. With the old version, Android don't boot. If I only replace data.img with my backup, Android boots but without the apps.
My question ist, how do I get the apps-data (e.g savegames) exported from data.img and imported in my backup version?
Click to expand...
Click to collapse
I am a little confused. Did you overwrite your data.img file or do you still have the original one? If you still have it your apps and data should be contained in there.
You should be able to read/view the file in Linux if you have a bootable Linux CD.
If you only have Windows copy the original data.img file to your PC and download/install this old program and unzip it. It should allow you to view the content of your data.img and extract things from it.
NYLimited said:
I am a little confused. Did you overwrite your data.img file or do you still have the original one? If you still have it your apps and data should be contained in there.
You should be able to read/view the file in Linux if you have a bootable Linux CD.
If you only have Windows copy the original data.img file to your PC and download/install this old program and unzip it. It should allow you to view the content of your data.img and extract things from it.
Click to expand...
Click to collapse
I'm sorry about your confusion.
I backuped the data.img file before overwriting it with an older backup to get Andoid working again. So I still have the file which seem a little bit corrupt.
These were my thoughts that the apps should be stored in there. I think I'll try both suggestions. Thanks.
Edit: Thanks for your help. I already had ext2explorer on my PC. And I could open data.img. Now I have to find the place where the apps stored (savegames ) their data and my phonebook. Any suggestions where to look for the phonebook and maybe the game tribez?
Greetings from Germany
Kaschparl79 said:
I'm sorry about your confusion.
I backuped the data.img file before overwriting it with an older backup to get Andoid working again. So I still have the file which seem a little bit corrupt.
These were my thoughts that the apps should be stored in there. I think I'll try both suggestions. Thanks.
Edit: Thanks for your help. I already had ext2explorer on my PC. And I could open data.img. Now I have to find the place where the apps stored (savegames ) their data and my phonebook. Any suggestions where to look for the phonebook and maybe the game tribez?
Click to expand...
Click to collapse
That gets a little more complicated.. Generally, the contacts are stored in a SQLite database. The location can vary depending on the ROM that is installed.
The simplest attempt, without getting too technical and installing a SQLite CLI is to look for the contacts database. Try something like this in the terminal window:
Code:
su
find /system -iname '*.db' |grep ontact
Hopefully, you will see something like this as a result:
Code:
/dbdata/databases/com.android.providers.contacts/contacts.db
/data/data/com.android.providers.contacts/databases/contacts2.db
You can try copying the files and see if they help.
Good luck!
NYLimited said:
That gets a little more complicated.. Generally, the contacts are stored in a SQLite database. The location can vary depending on the ROM that is installed.
The simplest attempt, without getting too technical and installing a SQLite CLI is to look for the contacts database. Try something like this in the terminal window:
Code:
su
find /system -iname '*.db' |grep ontact
Hopefully, you will see something like this as a result:
Code:
/dbdata/databases/com.android.providers.contacts/contacts.db
/data/data/com.android.providers.contacts/databases/contacts2.db
You can try copying the files and see if they help.
Good luck!
Click to expand...
Click to collapse
Thanks again.
Found the contacts in data/... but copying it into the other data.img caused some shutdown of ...acore process/program. The same problem with the savegame. Process tribez is unsepected stopped...
Maybe I'm doing something wrong mounting the data.img. Do know the exact command for mounting the file correctly for writing data?
Kaschparl79 said:
Thanks again.
Found the contacts in data/... but copying it into the other data.img caused some shutdown of ...acore process/program. The same problem with the savegame. Process tribez is unsepected stopped...
Maybe I'm doing something wrong mounting the data.img. Do know the exact command for mounting the file correctly for writing data?
Click to expand...
Click to collapse
You are asking good questions but not easy ones to answer. The mount command is specific to your device and rom. I do not have any sd roms to look at.
Let's try a few things.
First, try to clear cache for the contact apps. You can use ROM Toolbox or the system's app manager. This may help.
Second, you can try to look in the ROM's system folder and see if you have something like init.rc (probably in root, if there) If you find it look at it with a text viewer and search for Mount. You may find the proper command line.
Last, and this one needs to be modified, you can try something like these in the terminal window. Keep in mind that your device names and file systems are most likely different!
Code:
mount yaffs2 [email protected] /mnt/cache nosuid nodev
mount ext4 /dev/block/mmcblk0p2 /NativeSD wait noatime nodiratime barrier=0
---
Duct tape is like the force. It has a light side and a dark side and it holds the universe together. (via Tapatalk)
Thanks, solved
NYLimited said:
You are asking good questions but not easy ones to answer. The mount command is specific to your device and rom. I do not have any sd roms to look at.
Let's try a few things.
First, try to clear cache for the contact apps. You can use ROM Toolbox or the system's app manager. This may help.
Second, you can try to look in the ROM's system folder and see if you have something like init.rc (probably in root, if there) If you find it look at it with a text viewer and search for Mount. You may find the proper command line.
Last, and this one needs to be modified, you can try something like these in the terminal window. Keep in mind that your device names and file systems are most likely different!
Code:
mount yaffs2 [email protected] /mnt/cache nosuid nodev
mount ext4 /dev/block/mmcblk0p2 /NativeSD wait noatime nodiratime barrier=0
Click to expand...
Click to collapse
Thanks for your help. I made it work.
As I use an older SD-Version of Android your last code I couldn't use.
For those who will have a similar problem:
With the programm file I checked the data.img and it is an ext4 image which I mounted in linux. I mounted the workung data.img file, too.
Next I deleted the folders which contained the contacts and of cause the savegame from the good data.img. Then I copied these folders from the faulty data.img into the good data.img. But I had to use the terminal and cp with option -a to preserve the ownerships of the files and folders.
After that I used fsck on the unmounted data.img and copied the file back on my sd card. Everything worked fine.
Thanks again and greetings from Germany