I was doing a nandroid backup to test some features. but to my surprise when I tried to restore sd-ext is unable to be restored.
I am using clockwork 3.0.0.5. I even tried the advanced restores, but it seems to just get "stuck".
I looked on the backup folder, and I do see the sd-ext with a 600mb size.
How do I manually get that uncompressed and into my sd-ext partition?
I'm having this same issue. I thought it was just taking awhile... its still recovering an hour into it. Seem to be wrong on that assumption. I'm worried that this might be a severe bug in 3.0.0.5.. I guess I can always downgrade and try again.
My sdext somehow became corrupted. I had to run the command in terminal:
mke2fs /dev/block/mmcblk0p2
However replace mmcblk0p2 with the one applicable to your phone.. it could be different although I think unlikely but you could end up formatting the fat 32 partition. I ended up formatting my sdcard to FAT32 first then made the partition and did it via the alternative recovery, not clockwork. I think it depends on what partition was created first.
The command mk2fs formatted and fixed the sdext partition. Afterwards did a restore (using the old recovery 2.5.1.4 and a backup made with that recovery) and it worked.
Unfortunately I still have a md5 checksum error on my very latest backup with the latest clockwork recovery and the old 2.5.1.4 recovery. I'm back on cyanogen 6 as the one made right after flashing 7 is gave me the md5 checksum error.
I believe there might be issues with the new clockwork 3.0.0.5 on restoring backups made by the previous version (which caused the corruption in either the sdext and/or the backup file itself) and/or issues with the cyanogen 7 nightlies making proper backups on the previous version of clockwork. I don't have any other cyanogen 7 backups to test this theory nor do I have the time with a test tomorrow. Could just be back luck. I'm just glad I finally figured it out and have my phone back to the way it was.
Will backup more often for sure...
Hello All
I'm aware that the virtual SDCard is on data/media/0 with assorted symlinks and mountpoints
Now, I see file changes on /data/media/0 being shown also on /sdcard and on /storage/emulated/0 etc as expected. For example, Titanium backups or Downloads,
Except for a TWRP backup I did earlier today. This is only shown in /data/media/0
An older TWRP backup inb the same parent folder is present on all mount points
I flashed TWRP this morning after a full wipe and flash of Lollipop.
The 2 TWRP backups are "before" and "after" upgrade backups.
Why is the later backup only visible on /data/media/0?
related to this
http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749
Read posts at the end too
i did a restore last night so did a format /data /cache /system /dalvik /internal memory and did format data type yes command in TWRP. After doing the restore the phone on first boot said it was encrypting the phone!! i hadnt issued any such command so i dont know why it did that on its own. because of this one other nandroid backup on SD card has become corrupted and giving an error 255 when doing a restore. It is using the 'default' TWRP encryption password, whatever that is. I want to recover the corrupted nandroid backup. How can that be done?
I keep trying to do backups but it gets about half way through and the error 255. I don't understand what I'm doing wrong. Is it not possible to backup through twrp on xt1955-5. If not any suggestions on other means. Something that would include my accounts as well would be great. I have an google acct that google refuses to give back. Be cause they say can't verify. I know password but 2sv got messed up. Which is a bunch of bs. They track everything. I would prefer to never have to go through this again. Any help would be great.
First question. What all are you trying to backup? Second, to where? Third, do you have adequate space for said backup?
Also, if you have a pin or code enabled for access to the device I would disable it for the backup process.
I'm trying to back up system and data only to my ext sd with 50g avail but only needing 12g
Pbsipher1 said:
I'm trying to back up system and data only to my ext sd with 50g avail but only needing 12g
Click to expand...
Click to collapse
I was able to use TWRP to create a backup on an SD card. I'm running Android 10 and rom RR.
You might try other avenues like titanium or migrate. A quick internet search might lead you to a better procedure and app.
I've been having the same trouble. I just restored my XT1955-5 to stock RETAIL. Then installed TWRP and Magisk. I set my phone up as I like it, and want to back it up - everything I can possibly backup - boot, data, system, system image, efs, persist1, persist2, fsg, vendor, vendor image, dsp, and boot logo.
Before I tried to backup anything, I made sure that I mounted all of the partitions in TWRP.
The first few times I tried to back them all up at once, I got the error 255. So I started backing up the partitions one by one. The only partition that would NOT backup was the data partition. I still get the error 255 on the data partition backup. But all the others worked fine. I even went back and selected all the partitions except the data partition, and it backed up in one large backup just fine. So I don't know what the deal is with the data partition, but I can grab it with adb pull, so I guess I'm good to go.
I even booted back into the system and turned off the screen lock PIN - changed it to none. But I still couldn't backup the data partition via TWRP.
This should work for you from adb to backup your data partition:
Code:
adb push mmcblk0p64-data.img /dev/block/mmcblk0p64
Thanks tom2112 I'll give it a try what can it hurt. I also heard u have to be decrypted in order to backup data but can't seem to get decryption to stick
i was no able to backup using that command got
adb: error: stat failed when trying to push to /dev/block/mmcblk0p64: permission deni
Tom2112 said:
I've been having the same trouble. I just restored my XT1955-5 to stock RETAIL. Then installed TWRP and Magisk. I set my phone up as I like it, and want to back it up - everything I can possibly backup - boot, data, system, system image, efs, persist1, persist2, fsg, vendor, vendor image, dsp, and boot logo.
Before I tried to backup anything, I made sure that I mounted all of the partitions in TWRP.
The first few times I tried to back them all up at once, I got the error 255. So I started backing up the partitions one by one. The only partition that would NOT backup was the data partition. I still get the error 255 on the data partition backup. But all the others worked fine. I even went back and selected all the partitions except the data partition, and it backed up in one large backup just fine. So I don't know what the deal is with the data partition, but I can grab it with adb pull, so I guess I'm good to go.
I even booted back into the system and turned off the screen lock PIN - changed it to none. But I still couldn't backup the data partition via TWRP.
This should work for you from adb to backup your data partition:
Code:
adb push mmcblk0p64-data.img /dev/block/mmcblk0p64
Click to expand...
Click to collapse
ed
Hmm... if it is "permission denied" that sounds like you need root permissions to back it up. I'm sorry, but I'm not good enough with ADB to tell you how to get higher privs. Maybe ADB SHELL then SU, but I don't honestly know.
In approximately 30 seconds after launch my Redmi note 7 pro reboots into twrp. The backup section in TWRP shows that the data size is 0MB. I tried to make a backup via TWRP, but I get a message "set_policy_failed:/data/system". The phone was rooted by Magisk. As far I understand the data is encrypted? Can "Repair or Change File System" help in this case or will it erase all the data? How can I recover the data?
I found this line in the recovery.log:
Got arguments from boot message
Startup Commands: '--prompt_and_wipe_data' '--reason=set_policy_failed:/data/system'set_policy_failed:/data/system
After that I restored System from a backup which was made several months ago.It didn't help.
Then I tried to make an image of my data block via adb with the help of dd command, but by mistake I started to write into the /sdcard which is also mmcblk0p87 - just as my data block. When I realized this, I stopped the process by unplugging the usb cable. Still 29 Gb data.img was written into my sdcard and can be found at /sdcard.
I used the following command:
dd if=/dev/block/mmcblk0p87 of=/sdcard/data.img
After that free space decreased and became 80337MB instead of 109531MB, while Data backup size remained 0MB:
I: Data backup size is 0MB, free: 109531MB. (before)
I: Data backup size is 0MB, free: 80337MB. (after)
Finally I managed to create an image of my data. The file system is f2fs. I tried to restore the files with the help of R-Studio, but it didn't find anything except for some unknown text files with partly readable text. Does it mean that the information is not encrypted?
After that I restored Boot from backup and looked at the recovery.log again. There is no 'prompt_and_wipe_data' anymore. But the phone keeps on booting into TWRP.
Is there any way to restore information from the data block (I had photos and videos there)?
Here are the logs (1971 is the older one and 1970 is the last one - I don't know why the dates are so strange).