Hello Guys,
Any idea, if we have any Alternatives to Nandriod Backup?
Drawbacks of Nandriod Backup as I know:
1. It does not backup EFS binary/image which contains IMEI details
2. It does not backup Modem binary/image which is useful to camp to the networks
FYI: I know there are tools like EFS Pro and kTool to backup EFS
I wonder if there is any tool which can dump my entire ROM's partition on to sdcard "as it is" and re-storable using CWM.
Please delete this thread
Please delete this thread. I am supposed to use Q & A section instead of General...
EDIT: Great, moved to Q & A section. Thanks Mod Hulk
Raghunan said:
Hello Guys,
Any idea, if we have any Alternatives to Nandriod Backup?
Drawbacks of Nandriod Backup as I know:
1. It does not backup EFS binary/image which contains IMEI details
2. It does not backup Modem binary/image which is useful to camp to the networks
FYI: I know there are tools like EFS Pro and kTool to backup EFS
I wonder if there is any tool which can dump my entire ROM's partition on to sdcard "as it is" and re-storable using CWM.
Click to expand...
Click to collapse
Found Alternative to Nandriod Backup
Guys, found some useful info @ forum.xda-developers.com/showthread.php?t=1667886
-------------------- backup
before messing with the partition table, everyone should make backups of all partitions that can be accessed.
-------------------- efs backup
The most important backup is the efs partition, which very crucial, it includes your IMEI number, bluetooth MAC etc., and without this individual information, your phone cannot be used as a phone again.
For most supported phones, you can do this via adb:
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/efs.img
please look at forrest1971's thread for details about using adb.
If your phone uses another partition number for efs, then use this instead of the "1" in mmcblk0p1.
Perhaps you have to mount your sdcard first, to be able to save it there.
Then you should copy the backup to your PC (the recovery should have the option to mount usb).
-------------------- backup files from internal sd before repartitioning
the repartitioning will clear all data in the affected partitions, so all data in your big partition (internal sd etc.) will be lost.
You can try to backup your data, if the partition is accessible. The different methods below may have different success, depending which parts of your phone are usable.
* you can use aroma file manager, which is a full fledged gui file manager which starts standalone by being flashed in CWM. So it should be completely independent (sorry, I could not test it for this kind of backup myself).
For the following possibilities you should first ensure, you have a working recovery with working adb support.
Mount your external sd in recovery (which might be /emmc or /sdcard, please check), to be able to copy files.
* you can use QtAdb to copy files to your PC:
* you can use adb pull to copy any files or directory tree to your PC, e.g.:
adb pull /emmc/. emmc
* you can use tar from adb to archive files to a file on sdcard:
adb shell tar cvjf /sdcard/emmc.tar.bz2 /emmc/.
* you can use a copy command in adb shell to copy files to a folder in sdcard:
adb shell cp -ra /emmc/. /sdcard/emmc.backup
Note: you will loose file attributes and owner information if emmc is formatted with ext2/ext3/ext4, because vfat cannot handle these.
This may matter for system and some app related files.
Click to expand...
Click to collapse
Related
WHAT DO YOU THINK GUYS WILL THIS WORK :
EFS Pro - For Samsung Android Devices
Advanced Backup and Restore of your Device's '/efs' folder!
Important: Make sure your device screen is on as you will be prompted for Superuser permissions whilst using Backup and Restore features of EFS Pro!
Also make sure your device is NOT in Mass Storage Mode or Backup and Restore functions will fail.
Features:
Supports Backup and Restore of Partition Image (*.img) and Compressed TAR Archive (*.tar) formats.
Automatically detects saved EFS Backups on Device and PC for hassle free restoring.
Re-Scan option to refresh Backup list for restoring Backups.
Automatically Re-Mounts '/efs' folder with Read/Write permissions during restore for users 'stuck' with Read Only permissions.
Automatic detection and prompting of Mass Storage Mode.
Automatic detection and termination of SAMSUNG Kies application on startup.
Supports Multiple Backup handling.
Option to Format '/efs' partition before restoring an EFS Backup.
Displays Device, ROM and BusyBox information on startup.
Make sure you have Microsoft .NET Framework 4.0 installed on your PC.
Compatible with Windows XP, Vista, 7.
http://forum.xda-developers.com/showthread.php?t=1308546
thx for sharing it
We don't have /efs, I can't see that folder.
we do have efs partition, but its not mounted during boot.
android sdk in necessary?
mounting system in CWM recovery can see efs folder but CWM recovery doesnt have function to mount efs so when enter that folder, there is nothing
I am using Android SDK Manager Revision 22.2.1 with my Samsung Galaxy S3 GT-I9300 International which is running a leaked copy of the Official Samsung 4.2.2 Stock Jellybean ROM dated 24th June 2013. It is rooted.
I wish to copy my entire TWRP backup folder to my PC and in preparation I read several threads which purport to explain how to do it but I only succeed in copying 16Mb worth of .md5 and .win files out of a backup folder which is 2.56Gb in size.
All folders in the TWRP folder are readable, writable and not hidden.
I have used the commands adb pull/sdcard/TWRP/ D:\111. I also tried adb pull/sdcard/TWRP D:\111.
The best I have got so far is to copy BACKUPS/4df1bd936aae7f4b/Leaked_Samsung_4.2.2_stock-15.10.13 which contains the following files:
boot.emmc.win
boot.emmc.win.md5
cache.ext4.win.md5
data.ext4.win000.md5
data.ext4.win001.md5
recovery.log
recovery.emmc.win
recovery.emmc.win.md5
system.ext4.win.md5
There are four missing files including the following large files.
data.ext4.win000
data.ext4.win001
system.ext4.win
Admittedly I am not a developer and am new to ADB so I am presumably doing something wrong.
Can anyone assist please.
If you are wondering why I wish to do this I have twice tried to flash Cyanogenmod 10.1.3 Stable version to my phone but get errors both times. I thought it may help to format my phone but before doing that I want to copy the backup of my ROM so that I can recver back to stock if CM still causes problems.
Simple method would be to make backup to ext sd card or even int sd card .
Then via USB windows explorer copy and paste .
Although I have selected the "Use External Storage" option in ROM manager, it still does not allow me to choose the backup location and gives only the option to save the backup to the sdcard.
I also have TWRP recovery so I will boot into Recovery and see if that gives me the option to backup to my external sdcard which is my preferred option anyway.
matrixmainframe said:
Although I have selected the "Use External Storage" option in ROM manager, it still does not allow me to choose the backup location and gives only the option to save the backup to the sdcard.
I also have TWRP recovery so I will boot into Recovery and see if that gives me the option to backup to my external sdcard which is my preferred option anyway.
Click to expand...
Click to collapse
Thank you JJEgan! I have found an option in TWRP Recovery to save my ROM backup to my external MicroSDCard which is what I needed.
thanks again.
Hello,
I did a Nandroid backup (system, data, etc. using CWM) and a Titanium backup (user apps), wiped my phone, and installed a new ROM.
Q: Does a Nandroid backup include the /ProgramData/Language/ folder?
I'm trying to restore files I 'hid' using the Hide It Pro app. A developer blog post mentions that this folder is the 'vault location'. As a result, I'd like to find this folder and restore it if possible.
A Titanium Backup restore of the Hide It Pro app+data didn't of course work due to this. I'd like to avoid restoring everything from the Nandroid backup if possible and just restore the individual folder. I have of course tried looking through the folders and files to find it, to no avail.
Many thanks,
Chris
CM11 on Galaxy S3 i9300
I'd also like to know where (and if) the 'Download' folder is backed up to in a Nandroid backup.
Anyone with knowledge of the Android partitions structure and may know where to find these folders, your assistance would be much appreciated. I can't seem to find any of this on the net unfortunately.
ChrisLoz said:
I'd also like to know where (and if) the 'Download' folder is backed up to in a Nandroid backup.
Anyone with knowledge of the Android partitions structure and may know where to find these folders, your assistance would be much appreciated. I can't seem to find any of this on the net unfortunately.
Click to expand...
Click to collapse
I have been using "Audio Manager" aka "Hide it Pro" for many months (maybe 2 years)
(DON'T THINK OF WEIRD HIDDEN THINGS !!! I use only encryption feature to encrypt my script files. :laugh::highfive
Hide it Pro stores its main locker in /sdcard/ProgramData/Android/.Language/.fr
and fake locker in /sdcard/ProgramData/Android/.Language/.xx (escape pin locker)
After new ROM they are not deleted if you did not format SD Card.
Reinstall "Hide it Pro" (any version) and set password like first time. But all old hidden files will be there.
(During new ROM install, Hide it Pro files are not harmed if SD Card is not formatted, just follow above method to get files back)
They are not deleted unless you format SD Card. (internal or external whatever you have)
Unfortunately Nandroid backup does not backup /sdcard.
So you Hide it Pro hidden files (top secret!!! ) and Download folder is not backed up in Nandroid.
If you have any other question, ask me. I know thoroughly about that app.
Press Thanks if helped.
hnkotnis said:
I have been using "Audio Manager" aka "Hide it Pro" for many months (maybe 2 years)
(DON'T THINK OF WEIRD HIDDEN THINGS !!! I use only encryption feature to encrypt my script files. :laugh::highfive
Hide it Pro stores its main locker in /sdcard/ProgramData/Android/.Language/.fr
and fake locker in /sdcard/ProgramData/Android/.Language/.xx (escape pin locker)
After new ROM they are not deleted if you did not format SD Card.
Reinstall "Hide it Pro" (any version) and set password like first time. But all old hidden files will be there.
(During new ROM install, Hide it Pro files are not harmed if SD Card is not formatted, just follow above method to get files back)
They are not deleted unless you format SD Card. (internal or external whatever you have)
Unfortunately Nandroid backup does not backup /sdcard.
So you Hide it Pro hidden files (top secret!!! ) and Download folder is not backed up in Nandroid.
If you have any other question, ask me. I know thoroughly about that app.
Press Thanks if helped.
Click to expand...
Click to collapse
Hi, thanks for your reply.
It is to my understanding that /sdcard/ is the *internal* SD card, isn't it? ProgramData and Download are both folders on /sdcard/, which are currently empty due to the factory reset. I did not format my external SD card - the files on that still remain, but do not include either of these folders.
I have previously reinstalled Hide It Pro, the files did not reappear.
I would like to restore the two mentioned (internal) folders from my Nandroid backup.
ChrisLoz said:
Hi, thanks for your reply.
I have already reinstalled Hide It Pro, the files did not reappear.
It is to my understanding that /sdcard/ is the *internal* SD card, isn't it? ProgramData and Download are both folders on /sdcard/, which are currently empty due to the factory reset. I did not format my external SD card - the files on that still remain, but do not include either of these folders.
I would like to restore these two internal SD card folders from my Nandroid backup.
Click to expand...
Click to collapse
Depending on device's CWM (this varies with device) backed up folders change.
Copy CWM Backup to your PC and open that folder. You will see some/all following files. ext4 and rfs different based on ROM.
boot.img
data.rfs.tar
system.rfs.tar
.android_secure.tar
cache.rfs.tar
If there is sdcard.vfat.tar you are lucky. Internal SD Card is backed up. (unfortunately this is not for 99% CWM)
Otherwise I am afraid data is lost.
In case of data loss, try there to apps (require root) which can recover deleted photos. (I don't know about internal card, but I have tested them on external card.)
https://play.google.com/store/apps/details?id=fahrbot.apps.undelete
https://play.google.com/store/apps/details?id=com.defianttech.diskdigger
Press Thanks if helped.
hnkotnis said:
Depending on device's CWM (this varies with device) backed up folders change.
Copy CWM Backup to your PC and open that folder. You will see some/all following files. ext4 and rfs different based on ROM.
boot.img
data.rfs.tar
system.rfs.tar
.android_secure.tar
cache.rfs.tar
If there is sdcard.vfat.tar you are lucky. Internal SD Card is backed up. (unfortunately this is not for 99% CWM)
Otherwise I am afraid data is lost.
In case of data loss, try there to apps (require root) which can recover deleted photos. (I don't know about internal card, but I have tested them on external card.)
https://play.google.com/store/apps/details?id=fahrbot.apps.undelete
https://play.google.com/store/apps/details?id=com.defianttech.diskdigger
Press Thanks if helped.
Click to expand...
Click to collapse
Ah I see. Thank you.
I have already moved the backup to my PC, I'll check to see if that file is there tomorrow but I don't recall it being unfortunately. I had presumed Nandroid backed up everything, so it's quite an annoyance if I have lost everything from /sdcard/, but it's nothing too important thankfully.
Thank you for the link to the data loss recovery apps, I will give those a try if needed.
ChrisLoz said:
Ah I see. Thank you.
I have already moved the backup to my PC, I'll check to see if that file is there tomorrow but I don't recall it being unfortunately. I had presumed Nandroid backed up everything, so it's quite an annoyance if I have lost everything from /sdcard/, but it's nothing too important thankfully.
Thank you for the link to the data loss recovery apps, I will give those a try if needed.
Click to expand...
Click to collapse
Use these data recovery apps as soon as possible, because if the storage space where previous data was is overwritten, then data recovery is not possible.
Press Thanks if helped.
hnkotnis said:
Use these data recovery apps as soon as possible, because if the storage space where previous data was is overwritten, then data recovery is not possible.
Press Thanks if helped.
Click to expand...
Click to collapse
Neither worked unfortunately.
I'll give this method a go: http://forum.xda-developers.com/showthread.php?t=2143188
hnkotnis said:
Use these data recovery apps as soon as possible, because if the storage space where previous data was is overwritten, then data recovery is not possible.
Press Thanks if helped.
Click to expand...
Click to collapse
I'm trying to follow this guide to recover the 'sdcard' folder.
[GUIDE] Internal Memory Data Recovery - Yes We Can!
It's aimed at Galaxy Nexus, so I'm trying to change it for S3.
I've installed all the software and apps: BusyBox, Cygwin, Netcat, ADB (Android SDK + Java JDK), VHD Tool, Recuva, etc.
The internal 'sdcard' folder doesn't appear to be a partition, so when it comes to the first command main step:
5. Open a Cygwin terminal and enter (This assumes your BusyBox installation is at [/system/bin/busybox]. It may be at [/system/xbin/busybox]):
Code:
adb forward tcp:5555 tcp:5555
adb shell
/system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p12
Click to expand...
Click to collapse
...I don't know what to enter.
Any assistance would be appreciated!
Edit: Continued in this thread - http://forum.xda-developers.com/galaxy-s3/help/recover-files-sdcard-t2704117/
Sometimes files could be lost after you hide them with Hide It Pro. You may see this guide: Recover data in Hide It Pro
Good Luck.
Hi,
I have a Wiko Lenny 3 phone and need to recover the pictures. The unlock code is lost, the touchscreen doesn't work anymore. My ideas so far:
1. I used the "Backup user data" feature of the stock recovery to a SD card.
Since I cannot upload an image until I have 10 posts, the recovery is like
"
Android Recovery
alps/full_v3702/v3702
6.0/MRA58K/1453981211
user/release-keys
Volume down to move highlight;
enter Volume up key to select.
----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Backup user data ---> this is what I used
Restore user data
Root integrity check
Mount /system
View recovery logs
Power off
----------------------------------------
SD card free space: 29564MB
User data allocated: 11893MB
backup file: userdata_20190929_172118.backup
Backup user data complete.
"
But how to access the data? Tutorials which I found didn't help (merging the files in Linux, remove 512 Bytes and rename to zip to be able to extract "some" data: it isn't recognized as zip file). Is it possible to restore this user data to a virtual device somehow to access the data?
2. Removing the code: Following a German instruction (I'm not allowed to link it, sorry).
ADB doesn't recognize the device. Probably because USB debugging is turned off and I cannot turn it on without unlocking the device.
I don't do this very often, so my knowledge about ADB and Android is limited.
Does someone have a helping hint? Thank you in advance!
Regards
Martin
Martin_2 said:
Hi,
I have a Wiko Lenny 3 phone and need to recover the pictures. The unlock code is lost, the touchscreen doesn't work anymore. My ideas so far:
1. I used the "Backup user data" feature of the stock recovery to a SD card.
Since I cannot upload an image until I have 10 posts, the recovery is like
"
Android Recovery
alps/full_v3702/v3702
6.0/MRA58K/1453981211
user/release-keys
Volume down to move highlight;
enter Volume up key to select.
----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Backup user data ---> this is what I used
Restore user data
Root integrity check
Mount /system
View recovery logs
Power off
----------------------------------------
SD card free space: 29564MB
User data allocated: 11893MB
backup file: userdata_20190929_172118.backup
Backup user data complete.
"
But how to access the data? Tutorials which I found didn't help (merging the files in Linux, remove 512 Bytes and rename to zip to be able to extract "some" data: it isn't recognized as zip file). Is it possible to restore this user data to a virtual device somehow to access the data?
2. Removing the code: Following a German instruction (I'm not allowed to link it, sorry).
ADB doesn't recognize the device. Probably because USB debugging is turned off and I cannot turn it on without unlocking the device.
I don't do this very often, so my knowledge about ADB and Android is limited.
Does someone have a helping hint? Thank you in advance!
Regards
Martin
Click to expand...
Click to collapse
MartÃn only way you could access them pictures is if you had twrp
([emoji3590]09-09-18[emoji3590])
Thanks. Is it possible to flash TWRP without losing data and without access via ADB?
Martin_2 said:
Thanks. Is it possible to flash TWRP without losing data and without access via ADB?
Click to expand...
Click to collapse
If your phone has twrp available and it's a Samsung you can flash it and you won't be able to do a twrp backup without formatting data to have data partition mountable in twrp to flash decrypt zip to do a backup however you don't need to format to be able to mount system partition once system is mounted you can use the twrp file explorer to delete files to delete your screen lock so you can enter the phone
([emoji3590]09-09-18[emoji3590])
PoochyX said:
If your phone has twrp available and it's a Samsung you can flash it and you won't be able to do a twrp backup without formatting data to have data partition mountable in twrp to flash decrypt zip to do a backup however you don't need to format to be able to mount system partition once system is mounted you can use the twrp file explorer to delete files to delete your screen lock so you can enter the phone
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
It's a Wiko Lenny 3, no Samsung. Sorry, I don't get it without punctuation.
Do I get it right, that
- If TWRP is available for my phone I can flash it, but I need to format all my data (no option)
- I can flash a "decrypt zip" to do a backup (what is it, where do I get it?)
- I can mount the system partition and can use the TWRP file explorer to delete files (how can I mount it?)
Thanks.
Problem solved, I could access all the data in the backup from the stock recovery!
This is how it worked:
In short: Make a backup of all user files in the stock recovery to a MicroSD card, put it to a Linux desktop, merge the backup files by skipping the first 512 bytes of each file, copy the merged file to Windows, extract it with 7zip.
In long:
1. I put an empty 32GB FAT32 formatted MicroSD card in the MicroSD slot of the Wiko Lenny 3
2. I used "Backup user data" from the Stock Recovery (see my first post). It took a few minutes until ~12GB of user data were written to the card. The stock recovery told me when it was done.
3. I copied all files (6 files, userdata_20190929_172118.backup to userdata_20190929_172118.backup5) to a Linux environment (Linux Mint 19.2)
4. The rest is explained in this video: https://www.youtube.com/watch?v=cY4cKKimEFU. If it is offline, I will explain here.
Do not use something like "cat userdata_yyyymmdd_HHMMSS.backup* > userdata_yyyymmdd_HHMMSS.backup" to merge all files into one because it will add the unnessesary 512 bytes header of all .backup files to the merged file. Instead copy all content except the first 512 bytes to another file and append the content from the other files to it, also by skipping the first 512 bytes.
5. This command will copy the content of the first file "userdata_20190929_172118.backup" to a new file "img.ext4":
Code:
dd if=userdata_20190929_172118.backup skip=512 bs=128k iflag=nocache,skip_bytes oflag=nocache,append conv=notrunc of=img.ext4
6. Repeat using the same command to append the content of all other files to the file "img.ext4" by skipping the first 512 bytes. Be sure to increase the number of the source file extention in the command. Next one therefore is:
Code:
dd if=userdata_20190929_172118.backup1 skip=512 bs=128k iflag=nocache,skip_bytes oflag=nocache,append conv=notrunc of=img.ext4
7. Repeat with all files
8. Copy the file "img.ext4" to a NTFS formatted USB stick or an external hard drive and go on with a Windows environment. The reason is that Linux will prevent opening some important folders
9. Install 7zip
10. Extract the file "img.ext4" with 7zip. If you are searching for pictures, you will find them in the subfolder "\media\0\DCIM\Camera"
Martin_2 said:
Problem solved, I could access all the data in the backup from the stock recovery!
This is how it worked:
In short: Make a backup of all user files in the stock recovery to a MicroSD card, put it to a Linux desktop, merge the backup files by skipping the first 512 bytes of each file, copy the merged file to Windows, extract it with 7zip.
In long:
1. I put an empty 32GB FAT32 formatted MicroSD card in the MicroSD slot of the Wiko Lenny 3
2. I used "Backup user data" from the Stock Recovery (see my first post). It took a few minutes until ~12GB of user data were written to the card. The stock recovery told me when it was done.
3. I copied all files (6 files, userdata_20190929_172118.backup to userdata_20190929_172118.backup5) to a Linux environment (Linux Mint 19.2)
4. The rest is explained in this video:
. If it is offline, I will explain here.
Do not use something like "cat userdata_yyyymmdd_HHMMSS.backup* > userdata_yyyymmdd_HHMMSS.backup" to merge all files into one because it will add the unnessesary 512 bytes header of all .backup files to the merged file. Instead copy all content except the first 512 bytes to another file and append the content from the other files to it, also by skipping the first 512 bytes.
5. This command will copy the content of the first file "userdata_20190929_172118.backup" to a new file "img.ext4":
Code:
dd if=userdata_20190929_172118.backup skip=512 bs=128k iflag=nocache,skip_bytes oflag=nocache,append conv=notrunc of=img.ext4
6. Repeat using the same command to append the content of all other files to the file "img.ext4" by skipping the first 512 bytes. Be sure to increase the number of the source file extention in the command. Next one therefore is:
Code:
dd if=userdata_20190929_172118.backup1 skip=512 bs=128k iflag=nocache,skip_bytes oflag=nocache,append conv=notrunc of=img.ext4
7. Repeat with all files
8. Copy the file "img.ext4" to a NTFS formatted USB stick or an external hard drive and go on with a Windows environment. The reason is that Linux will prevent opening some important folders
9. Install 7zip
10. Extract the file "img.ext4" with 7zip. If you are searching for pictures, you will find them in the subfolder "\media\0\DCIM\Camera"
Click to expand...
Click to collapse
I have the exact same problem with an older 2017 ALCATEL Pixi Unite A466BG. The code is lost and there's some photos we need off of it. I followed these instructions but when I got the img.ext4 file on Windows and tried extracting it with 7zip, I got an error that "ext4" is not an archive file.
I was hoping to see if anyone else had ideas of possibly why 7zip wasn't recognizing it? I had 3 backup files to merge (backup, backup1, backup2).
Hi all,
I'm tinkering with my OnePlus 6 and trying to backup so I can restore after I soft-brick it by removing bloatware.
I'm using OxygenOS 10.3.2 and seems that TWRP doesn't backup/restore as it should, it always bricks my phone whenever I restore /system or /data.
I'm trying to save and restore data via terminal at the moment, I mounted /system and I see I have access to dd.
Is it possible to just copy everything from /system and /data to /sdcard, move it to my pc, and whenever I brick the phone, just stock install OxygenOS 10.3.2 then TWRP and restore via terminal?
Anyone done this?
I presume the risk is low if I'm only touching /system and /data?
edit:
Managed to backup /system with DD but I don't know how to backup /data, as /data is the same device as /sdcard, and it would create a file equal to the whole partition size. I would not be able to store it on the same partition since /sdcard is basically a subfolder of /data.
Any way of backing up /data? on the same partition?
I would have tried with rsync then zip the whole thing and extract it on my pc. I know rsync keeps the file/folder permissions intact. But rsync is not available in TWRP recovery.
I tried to make a tar archive while inside /data, excluding the media folder, like this:
Code:
tar -pzcvf data.tar.gz --exclude=media *
The -p option should preserve SELinux attributes. I then copy data.tar.gz to /sdcard and pull it on my PC.
But, when I move it back, delete everything in /data except media folder, then unpack the archive and reboot, it goes into recovery.
I don't understand why wiping all files then putting them back from the archive breaks the system. What am I missing?
edit:
Apparently /data backup and restore work from TWRP modified by Mauronofrio, only the /system backup/restore is broken, but that can be done with DD from TWRP.
So my issues are solved at the moment.
mad_rock said:
I tried to make a tar archive while inside /data, excluding the media folder, like this:
Code:
tar -pzcvf data.tar.gz --exclude=media *
The -p option should preserve SELinux attributes. I then copy data.tar.gz to /sdcard and pull it on my PC.
But, when I move it back, delete everything in /data except media folder, then unpack the archive and reboot, it goes into recovery.
I don't understand why wiping all files then putting them back from the archive breaks the system. What am I missing?
edit:
Apparently /data backup and restore work from TWRP modified by Mauronofrio, only the /system backup/restore is broken, but that can be done with DD from TWRP.
So my issues are solved at the moment.
Click to expand...
Click to collapse
I'm not sure if -p is sufficient to also backup the selinux rights.
Have you tried the tar option --selinux ?
From the man1 page:
Code:
--selinux
Enable SELinux context support.