Develop Bugs

I can't recover any nandroid backup

Hi all, I've already read several similar posts, but none of them could help me. I have a HTC Wildfire S, and I installed a custom ROM (latest version of Marvellous Based in jelly bean 4.2.2 and CM10 made by djolivier. The ROM cames with Obackup which make the backup of entire ROM, included the partition EXT2. Such partition have 2 GB and works perfectly so far. I'm using EXT2INT script to increase de Internal memory, but the thing is that when I want to recover a backup, always throw "Error while formatting /data!"
this is the log:
....
uiautomator.jar
android.policy.jar
end of image
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2013-07-01.13.59.39/data.ext2.tar
Restoring data...
I:Formatting unknown device.
I:Formatting ext2 device.
mke2fs 1.41.12 (17-May-2010)
Could not stat userdata --- No such file or directory
The device apparently does not exist; did you specify it correctly?
Error while formatting /data!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/2013-07-01.13.59.39", "boot", "system", "data", "cache", "sd-ext")
I've tried to recover the backup with ROM Manager which install Nandroid Manager, but I still have the problem, and I can't do it at all. I hope you can help me with this, and if you need more information please let me know. Thanks in advance!

corrupted memory?

Hi guys have weird problem with my phone. Sometimes when I want to make nandroid I can see error 255 always on system partition . When I restore system partition I can do nandroid.
Next thing, when I want to delete any system app using titanium backup, after restart app is back again and im not getting free spacer in system partition. Also very often when I restore nandroid system doesn't want to boot, it just stuck on boot logo.
It is happening since last few weeks. What should I do to fix it?
Format all partitions then clean flash of rom?

joloxx9joloxx9 said:
Hi guys have weird problem with my phone. Sometimes when I want to make nandroid I can see error 255 always on system partition . When I restore system partition I can do nandroid.
Next thing, when I want to delete any system app using titanium backup, after restart app is back again and im not getting free spacer in system partition. Also very often when I restore nandroid system doesn't want to boot, it just stuck on boot logo.
It is happening since last few weeks. What should I do to fix it?
Format all partitions then clean flash of rom?
Click to expand...
Click to collapse
That would work if you arent rooted with otg ...the you could image the system and fix it on a Linux box with fsck
Sent from my ONEPLUS A3000 using Tapatalk

uudruid74 said:
That would work if you arent rooted with otg ...the you could image the system and fix it on a Linux box with fsck
Click to expand...
Click to collapse
Could you please tell me How can I fix IT?

joloxx9joloxx9 said:
Could you please tell me How can I fix IT?
Click to expand...
Click to collapse
The method you mentioned will work. Format everything and reload. I wish that recovery systems for Android supported fsck. Actually, if you have busybox installed, even under tmpfs, you might be able to get to a shell to run fsck. I can't try it now, but it worth a shot.
Sent from my ONEPLUS A3000 using Tapatalk

uudruid74 said:
The method you mentioned will work. Format everything and reload. I wish that recovery systems for Android supported fsck. Actually, if you have busybox installed, even under tmpfs, you might be able to get to a shell to run fsck. I can't try it now, but it worth a shot.
Click to expand...
Click to collapse
No Way to run fsck. I will try to format everything later then send files from PC and install fresh system on the phone.

joloxx9joloxx9 said:
No Way to run fsck. I will try to format everything later then send files from PC and install fresh system on the phone.
Click to expand...
Click to collapse
for future reference, there is a "Repair filesystem" option in twrp. It says it runs e2fsck, which works for ext4. It won't hurt an f2fs filesystem, but I don't think it will repair it either. I'm seriously considering switching my /data to ext4 just so I have proper recovery tools.
My OP3T does have fsck.f2fs on the system, which means you can fix your data by opening a Terminal session from TWRP and then running :
Code:
fsck.f2fs /dev/block/dm-0
should fix your data corruption should you see this error again. For ext4, you use e2fsck rather than fsck.f2fs. This is also what you would use on /system (which is /dev/block/sde20 on my phone) should that ever be mounted read/write and get corrupted (pretty low chance even if you do mount it read/write as writes are low frequency and ext4 has a rock solid journal).
WARNING: Device numbers are for my OP3T and may be different on other devices or even on non-US devices.

Question about TWRP backup/restore partition selection

Just moved from an old Galaxy S6 to the Pixel 2 Xl and I am confused about what partitions i need to select to make a proper backup with TWRP.
Is boot/sytem/data enough?
I dont know what to do with the remaining partitions: system image/vendor/vendor image.

Boot, System, Data is all I ever backup, and I've never had an issue when restoring :good:

Az Biker said:
Boot, System, Data is all I ever backup, and I've never had an issue when restoring :good:
Click to expand...
Click to collapse
I'm getting an error every time I try running a backup using TWRP. There always seems to be a createTarFork() error, specifically for the data partition. How did you work around this? Have tried doing doing the backup with the data partition both mounted and unmounted, still get the same thing,
Running TWRP 3.3.0-0
Kudos in advance
-D

ProoN said:
I'm getting an error every time I try running a backup using TWRP. There always seems to be a createTarFork() error, specifically for the data partition. How did you work around this? Have tried doing doing the backup with the data partition both mounted and unmounted, still get the same thing,
Running TWRP 3.3.0-0
Kudos in advance
-D
Click to expand...
Click to collapse
I believe things and processes have changed with Android 10 (Q) as far as TWRP and backups.
Post your question here as it is permitted here by the OP and there is a lot of help here.

TWRP backup editing

Hello,
I have edited files in my twrp backup (only data backup) and now i cant restore it, i get an error:
Code:
[color="red"]
extractTarFork() pocess ended with ERROR: 255
[/color]
What must i do that I can this restore?

Format data (format not advanced wipe) and try the restore again

TheFixItMan said:
Format data (format not advanced wipe) and try the restore again
Click to expand...
Click to collapse
Must I nothing change like shasum?

lucki1000 said:
Must I nothing change like shasum?
Click to expand...
Click to collapse
Think it's to do with available space (yes I know you are restoring what's already there)
I've found a format of the data partition (this will also format internal storage) will solve it
I already gave the above as a possible solution on my official twrp thread in the faq section

Nandroid backup - System and vendor won't mount

Hello folks,
Now that Pixel XL is not going to get any updates from google, I am ready to switch over to the ROMs. I thought I should take a nandroid backup before proceeding. This device has unlocked bootloader and rooted with Magisk. Its running September update. I didn't install the October update.
Booted Pixel XL into TWRP using fastboot. Used twrp-3.3.1-3-marlin.img. When I try to backup, I get an error
Failed to mount '/system' (invalid argument)
Failed to mount '/vendor' (invalid argument)
It manages to generate the digest but again gives an error, failed to mount system. Backup failed.
I even restored the phone to factory settings and I get the same error.
Is there anything else I should be checking?
Edit: Tried older TWRP, 3.3.1.0. Now I get an error with the same two, device or resource is busy.
Thanks in advance.

You probably only need to backup your data (which may require you to remove your screen lock before boring into TWRP). Optionally backup the boot partition so you have any custom kernel and Manish backed up as well.
The system, vendor, and other partitions can be restored by fastboot. Less than ideal, but that's what I've been doing.

NZedPred said:
You probably only need to backup your data (which may require you to remove your screen lock before boring into TWRP). Optionally backup the boot partition so you have any custom kernel and Manish backed up as well.
The system, vendor, and other partitions can be restored by fastboot. Less than ideal, but that's what I've been doing.
Click to expand...
Click to collapse
Thanks. So you started having this problem with Android 10 only or it was before android 10 as well?
The second question I have, if it won't mount system, is that partition the same as the data, because android has Slot A and B. This is the first phone I am dealing with that has 2 slots. Any idea if this create any issues at the time of ROM / Lineage OS install?

fuzzychicken said:
Thanks. So you started having this problem with Android 10 only or it was before android 10 as well?
The second question I have, if it won't mount system, is that partition the same as the data, because android has Slot A and B. This is the first phone I am dealing with that has 2 slots. Any idea if this create any issues at the time of ROM / Lineage OS install?
Click to expand...
Click to collapse
Myself I haven't tried mounting either as writable, but read only for system is fine. I've never flashed a custom rom. I do see posts from other people with the issue though.
There is only one data partition, and it is completely separate from system etc, and slots don't affect it.
Just follow the instructions for the custom rom you end up installing.