Database Info

[Q] Need help restoring ROM manager backup

Ok so I decided that I wanted to see what all the Froyo fuss was about, so I started getting my phone ready following instructions on the site. I own a Samsung i-9000m (in canada from bell - actually sasktel but we get phones from bell). anyways, I figured i'd do a rom manager backup. I did one, had some trouble with my phone and now I need to do a restore. Reading on the web they all point to an update.zip file. All I have is the following on my internal SD
ClockworkMod\2010-11-24-14.32.54\ and the following files in that folder:
cache.img
datadata.img
system.img
data.img
nandroid.md5
I tried restoring from rom manager but it doesn't find any files, I've booted into recovery but doesn't recognize the img files......any help would be amazing. Am I missing a step, google is no help

loooks like i needed the recovery update.zip file i'm assuming.....for some reason I didn't have it in the clockworkmod folder....

[Completed] [Q] Unknown Serial, Cannot Wipe, or Factory Reset. Stuck in Boot Logo Screen

Hi
I have an Asus Fonepad 8 (K016 or FE380CG. 2GB RAM, 16GB ROM), I know it's not popular around here.. But any help is very welcome.
My initial device's state
- Stock rom 4.2.2
- Root (installed: Greenify, App Ops, Coolify, System App Remover (Jumobile))
- I uninstalled about 20 system apps
then I received OTA update to Lollipop and it displayed the infamous android "error" with the red exlamation mark. so i uninstalled every root app, EXCEPT System App Remover (silly me i forgot the most crucial part), probably meaning that some system apps are still gone. I also did full unroot inside SuperSU.
I tried factory resetting in order to successfully update to Lollipop, but once I get to the setup Welcome screen, these dreaded messages show up. ENDLESSLY
Unfortunately, com.android.phone has stopped working
Unfortunately, com.android.systemui has stopped working
Unfortunately, com.process.acore has stopped working
Click to expand...
Click to collapse
One time, the endless torture stopped and I was able to access Settings. I opened Applications and there was very (infact, too) few apps installed. Less than 200MB of RAM is used. I thought the factory settings failed, so I tried doing the same thing again in fastboot mode. But still a no-go.
Then I tried
Code:
fastboot -w
and it did say "success" but it couldn't format. "File system not supported". I forgot the exact message but that, i think is the point.
In Droidboot Provision OS, there is an option called "SD download". I put the official ROM for my device (.zip) in my SD card, then tried doing exactly that. Still no-go. Below is the entire (not exact) process
Copying E:\ASUS_UPDATE.zip to /cache (i renamed my firmware .zip file to that)
Copying asus update file (i have no idea where this file (if it even is a file) is located)
then my device reboots
a brief "no command" error appears
reboots back to my faulty state
Click to expand...
Click to collapse
I then tried to erase cache and userdata, and ran
Code:
fastboot update fw.zip
This appears
archive does not contain android-info.txt
archive does not contain android-product.txt
Click to expand...
Click to collapse
Desperate enough, I tried to again erase cache and userdata and system (probably my worst decision). and the device is now stuck in boot logo screen.
My awesome representation of my device's boot logo screen
ASUS
powered by
ANDROID
Click to expand...
Click to collapse
I booted my device back to fastboot, and my serial number was shown as "unknown". The same appeared when i type below code in cmd in my PC.
Code:
fastboot devices
One thing to be noted. I am really confused with ASUS's official firmware.
There is no recovery.img, system.img, userdata.img or cache.img
Here is a list of files and directories inside of it:
META-INF (folder)
recovery (folder, 2 files: recovery-from-boot.p and install-recovery.sh)
system (folder, a lot of folders inside like "app", "bin", "etc", "fonts")
boot.img
fastboot.img
splash1.img
splash1_s.img
splash2.img
splash2_s.img
splash2.img
splash2_s.img
ifwi.zip
modem.zip
Click to expand...
Click to collapse
I do not have nandroid or any kind of backup.
I have googled and tried everything I could find for the past 9 hours. So, i think it's high time I ask experts about this.
I am thinking of taking it to the service center. But any more knowledge regarding this beforehand is very valuable to me.
I know this is too long but I've highlighted the most important parts.
Any kind of help is welcome.

Hi, thank you for using XDA Assist. Unfortunately there is not a dedicated forum and there is very little information about your device on XDA. There is nothing on how to flash the stock firmware. But it sounds like that's what you need to do right now. Looking at ASUS's web site it looks like there should be another zip file. ifwi.zip, in the one you extracted. That's most likely where the image files you are missing reside.

jd1639 said:
Hi, thank you for using XDA Assist. Unfortunately there is not a dedicated forum and there is very little information about your device on XDA. There is nothing on how to flash the stock firmware. But it sounds like that's what you need to do right now. Looking at ASUS's web site it looks like there should be another zip file. ifwi.zip, in the one you extracted. That's most likely where the image files you are missing reside.
Click to expand...
Click to collapse
Hi. Thank you so much for replying and taking the time to read my long "story".
Sadly, yes. There is little to no community for my device.
Regarding ifwi.zip, below is part of the content of the file.
FE380CG_16_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_16_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
FE380CG_1_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_1_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
FE380CG_2_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_2_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
FE380CG_32_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_32_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
Click to expand...
Click to collapse
I doubt that it's the system image. The file size is just way too small.
The folder with the largest size is System, and inside there are a lot of folders (app (system apps and asus's bloatwares are inside), bin, etc, fonts, framework, etc, and build.prop). It almost looks like ASUS doesn't package system into a .img file, rather in a folder. That's why I am also looking for a script file that "copies" this folder into the device, if it exists.
I am now downloading the latest (was just uploaded by ASUS) firmware, which is Lollipop.
I'll dig in the file and see if I can find anything interesting.

Ok, download's finished.
Below is the root directory of the new firmware.zip
META-INF (folder)
recovery (folder)
system (folder)
boot.img
droidboot.img
splash.img
file_contexts (no extension)
l_recovery.fstab
partition.tbl
ifwi.zip
modem.zip
Click to expand...
Click to collapse
ifwi.zip has the same contents, only a newer version.
I tried fastboot update fw.zip and the same error pops up
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
I have attached a screenshot of updater-script I found inside META-INF/com/google/android. and screenshots of the directories of the firmware zip's contents. Hoping any is helpful to solve this.

First, I know nothing specific about your device. But do you have a custom recovery on your device? CWM or TWRP. The updater-script looks like it should be flashed in a custom recovery, not with fastboot. Edit, also, what's in the system folder, etc. Are there image files in there?

jd1639 said:
First, I know nothing specific about your device. But do you have a custom recovery on your device? CWM or TWRP. The updater-script looks like it should be flashed in a custom recovery, not with fastboot. Edit, also, what's in the system folder, etc. Are there image files in there?
Click to expand...
Click to collapse
Sorry for the late reply.
I just got the device back from the service center.
I inquired about where I can get the firmware file, and the guy said ASUS's website, but to flash it I need a tool.
It seems that this tool then copies the entire system folder to the device.
Anyways, the problem is solved now. Thank you very much for your help.

Glad you got it fixed. I'll close this thread.

Persist image corrupt ?

Hi, i own an Oneplus 8 India Version.
As soon as i purchased the first thing I did was to take the persist.img backup as that seemed to be an important thing to do from my reading through the articles.
After a few months now, I seem to be in need of using this image and realized the image file is not accessible. from the articles and videos I read/seen, everyone is able to EXTRACT the image file using the 7zip or similar tools. However, i am unable to extract using any of the tools.
I took the latest persist.img from the already troubled device and that too is not working. 7zip says "Can not open the file ...."
command i used was this :
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
similarly, i manually copied the file using root file manager aad that too is giving the error

Please help

Fastboot flash persist persist.img
I believe that's how you would restore persist.
I could be very wrong. Proceed with caution and I'm not liable if you break it.

crazynapkinman said:
Fastboot flash persist persist.img
I believe that's how you would restore persist.
I could be very wrong. Proceed with caution and I'm not liable if you break it.
Click to expand...
Click to collapse
Hi thank you. The concern is related to the image not being extracted. From what i have read and seen in YouTube too is they are able to extract the img file. But my files are not readable.

firoz3321 said:
Hi thank you. The concern is related to the image not being extracted. From what i have read and seen in YouTube too is they are able to extract the img file. But my files are not readable.
Click to expand...
Click to collapse
Does anyone know if he can flash someone else's backed up persist.img?

crazynapkinman said:
Does anyone know if he can flash someone else's backed up persist.img?
Click to expand...
Click to collapse
There was a thread in this forum that mentioned the persist cannot be shared or doesn't work with others. Apparantly it contains sensor calibration data which usually will be unique.
Can someone confirm if your persist image is extractable with 7zip or similar. If so what am i doing wrong.

firoz3321 said:
There was a thread in this forum that mentioned the persist cannot be shared or doesn't work with others. Apparantly it contains sensor calibration data which usually will be unique.
Can someone confirm if your persist image is extractable with 7zip or similar. If so what am i doing wrong.
Click to expand...
Click to collapse
You need to be unlocked and rooted. Then you will reboot to fastboot. From there, BOOT twrp (fastboot boot twrp.img)
Once booted, use TWRP to backup persist.img

crazynapkinman said:
You need to be unlocked and rooted. Then you will reboot to fastboot. From there, BOOT twrp (fastboot boot twrp.img)
Once booted, use TWRP to backup persist.img
Click to expand...
Click to collapse
Using root explorer i copied the persist image but that too was un extractable. The persist image that i took backup using the command in OP when i bought the device also doesn't extract.
And one more thing is TWRP doesn't seem to be working with 11 OS yet.

firoz3321 said:
Using root explorer i copied the persist image but that too was un extractable. The persist image that i took backup using the command in OP when i bought the device also doesn't extract.
And one more thing is TWRP doesn't seem to be working with 11 OS yet.
Click to expand...
Click to collapse
Need to downgrade to 10.
I pulled my persist image off of 10.
---------- Post added at 07:20 PM ---------- Previous post was at 07:08 PM ----------
From what I've read there's not reason to unzip the persist.img
If you backed it up with a WORKING persist present, then you simply need to boot to fastboot and flash your persist.img
It will replace the corrupted partition and you're good to go. No one on any forum I read said they actually extracted anything from the persist.img file itself.
They all had to extract (see backup) the WORKING persist.img and flash that with fastboot command.
You can extract working persist.img with the following command in adb:
dd if=/dev/block/by-name/persist of=/sdcard/persist.img
This will save it to your sdcard. Transfer that backup to your adb folder on pc. Reboot into fastboot and use the following command to flash it:
fastboot flash persist persist.img

I do have working persist. There is a youtube video regarding same issue and ye extracted files from working persist. Your steps are clear and thank you for that .
My reason for asking was. If my files are corrupted i may damage more than solving. Hopefully the files i have are good.

firoz3321 said:
I do have working persist. There is a youtube video regarding same issue and ye extracted files from working persist. Your steps are clear and thank you for that .
My reason for asking was. If my files are corrupted i may damage more than solving. Hopefully the files i have are good.
Click to expand...
Click to collapse
Hopefully you're using the good backup you made and not something you downloaded...
GL!

crazynapkinman said:
Hopefully you're using the good backup you made and not something you downloaded...
GL!
Click to expand...
Click to collapse
Today i gave it to service.
Un rooted, locked boatloader and sent to service. Just wasn't daring enough as i wasn't sure if my image backup was safe.

firoz3321 said:
Today i gave it to service.
Un rooted, locked boatloader and sent to service. Just wasn't daring enough as i wasn't sure if my image backup was safe.
Click to expand...
Click to collapse
Received the mobile back and the FP reader is working fine. :angel:

Help RESTORING backup, "extractTarFork() process ended with ERROR: 255"

NOTE THIS IS NOT "UNABLE TO BACK UP" THIS IS "UNABLE TO RESTORE"
Lots of people on this forum, and lots of people on the internet have errors trying to back up because of this dreaded error 255. But, for me, the backup was fine, but now I can't restore. This is a huge problem because I just tried out a custom ROM (which turned out to be a huge fail), and I want to go back to stock.
So I switched back to the other slot (A/B ftw), wiped all data, formatted SD card, set up the OS to have the same lock pattern as the backup, transferred the backup onto the phone and tried to restore, and, well, fuck.
Code:
[RESTORE STARTED]
Restore folder: '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR'
Skipping Digest check based on user setting.
Calculating restore details...
Restoring 4 partitions...
Total restore size is 11276MB
Restoring Vendor Image...
[Vendor Image done (3 seconds)]
Restoring Boot...
[Boot done (0 seconds)]
Wiping Data (excl. storage)
Wiping data without wiping /data/media ...
Done.
Restoring Data (excl. storage)...
extractTarFork() process ended with ERROR: 255
It failed, and there is absolutely nothing I can do about it. TWRP is using buggy commands to extract the backup and I don't know what's triggering the bug.
As a result, right now all my data is in limbo. TWRP cannot restore this backup as-is. I can't just go back in time and use `pm remove-user 999` or `pm remove-user 10` because the backup has already been created. Any solution that has to be done before the backup phase is inaccessible to me now.
My hope is that some smart person here can help me find a way to get this backup back onto the phone. Right now the internet does not have a solution to this problem, no matter how many naive users spam discussion boards with "pm remove-user 999 totally worked". Serious answers only.
Relevant section in the recovery log:
Code:
==> extracting: //data/vendor_de/10/ (mode 40771, directory)
Cannot find key for 10
error looking up proper e4crypt policy for '//data/vendor_de/10/' - 1DE10
tar_extract_file(): failed to extract //data/vendor_de/10/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR/data.ext4.win000'
Error during restore process.
I:Error extracting '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR/data.ext4.win000' in thread ID 0
I:Error extracting split archive.
Error during restore process.
pigz: write error code 32
pigz: abort: write error on <stdout>
extractTarFork() process ended with ERROR: 255
I suppose the solution is to make it "find a key for 10", but how? Do I just need to somehow recreate the 10 user before restoring the backup?

EDIT NOTICE: THIS DIDN'T WORK, DON'T MAKE IT WORSE BY TRYING
ORIGINAL POST IS BELOW
Alright. Well, I found a solution. That was quick.
The error is triggered by the backup containing a user that isn't present during the restore, I think. One solution is (theoretically) to create the missing user... another solution is to remove the missing user from the backup.
Turns out, backups are not so hard to modify, even in their compressed form. However, it is a little bit unintuitive at first.
You can't use the `tar` command to modify the backup, at all. TWRP's tar doesn't even support the --delete flag, nor does the BSD tar command (what ships with macOS). Even after installing GNU tar, it still refuses to work on a compressed archive (probably for the better).
You either need a Windows system with WinRAR/7zip (allows opening/modifying compressed files without extracting them), or a macOS/Linux system with FUSE and archivemount. If you're on Windows, you will have to manually search every single folder for 10 or 999 folders and delete every single one. If you're on macOS/Linux, the process is a bit more technical but also a bit more automated. And in both cases you will have to do this many times, and it can easily take half an hour or more and many restore attempts.
First and foremost, you need the recovery log to find out where the process failed. Every time it fails you will need to go to Advanced > Copy Log, copy them to the SD card, then use the flipping horrible Android File Transfer program to transfer the recovery.log to your PC, then use the cat/tail command or a text editor of your choice to read the log file.
Somewhere around the end of that file you will find something that looks like this:
Code:
==> extracting: //data/misc_de/10/ (mode 41771, directory)
Cannot find key for 10
error looking up proper e4crypt policy for '//data/misc_de/10/' - 1DE10
tar_extract_file(): failed to extract //data/misc_de/10/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR/data.ext4.win003'
This contains all the info you need: the archive where the tar command gave up, and the file it gave up on.
Destroy that file with extreme prejudice.
Make a mount point with `mkdir mnt`, and mount the archive with `sudo archivemount data.ext4.win003 mnt`. (Of course, substitute data.ext4.win003 with the culprit archive file.)
If you're like me and have this problem with 10 folders, or 999 folders, you can find every single one of its kind with `sudo find mnt -name 10`. You can then use `sudo rm -rf` to delete every one of them. If you're brave, try `sudo find data -name 10 -exec sudo rm -rf \{\} \;`. I'm not responsible for any data losses incurred by using powerful commands that don't prompt you for confirmation.
Notice how I'm repeatedly using `sudo` for this: FUSE is kind of quirky and so is the kernel about multi-user filesystems. If you don't use sudo to mount the archive, then the user won't have permission to represent files it doesn't own, even if root is the one asking. You'll get weird "No such file or directory" errors for files and directories that are contained in parent directories' file listings. If you don't use sudo for the find or rm commands, you won't have permission to look inside folders or delete folders. Really, do everything with sudo because it's the only way to do this correctly.
Once you're done scrubbing the problem files away (be careful, do not use a file explorer of any kind, especially macOS's, which generally craps .DS_Store files all over your filesystem), unmount and save the archive with `sudo umount mnt`.
The next part is very important because recompressing files is not instant.
You will need to run `watch -n 1 du -hs data.ext4.win003` and WAIT.
Watch the file size slowly grow; only continue once it has stayed the exact same for at least one minute. Yes, it can definitely stop for 30 seconds at a time and then resume. You will need to give it time to recompress. It's also probably normal for the recompressed file to be about half the size of the initial file; that's just an artifact of TWRP not using very good compression to begin with. archivemount will create a backup of the archive with .orig appended, so you can try again if your backup ends up getting corrupted. (I just created an entirely separate copy of the backup to use archivemount on)
Of course, if you're on Windows you can skip all this and simply delete the problem file from WinRAR/7zip, and it'll be gone instantly and you can just proceed to copy the archive over to your device and retry the backup. You will have to do all the searching manually though, or perhaps you could try your luck with WSL. (Does WSL support FUSE?)
Expect this process to fail multiple times, but all at different points; whenever it fails at a different file, you know it got past the one you just removed. all you need to do is repeat this process over and over, slowly fixing your backup until it restores properly. This is what needs to be done if you can't reproduce the event that created that user in the first place. I'm sure if the user is important, it'll get created again.

Also, looks like user 10 is what happens when Google Play updates Device Personalization Services. Is this the generic "updates for system apps" user or is it specifically for that app?
EDIT: But updating that app doesn't create user 10. Interesting...
EDIT 2: User 10 is the guest user!! All I needed to do was create user 10 and that allowed me to restore my backup!
My post above is still good to see what I tried at first but it actually bricked my device until I factory reset it again, so :/

LoganDark said:
Also, looks like user 10 is what happens when Google Play updates Device Personalization Services. Is this the generic "updates for system apps" user or is it specifically for that app?
EDIT: But updating that app doesn't create user 10. Interesting...
EDIT 2: User 10 is the guest user!! All I needed to do was create user 10 and that allowed me to restore my backup!
My post above is still good to see what I tried at first but it actually bricked my device until I factory reset it again, so :/
Click to expand...
Click to collapse
Glad you managed to get your device back!
I had the same problem on another phone. The reason I got the error was because I tried to restore a decrypted backup on an encrypted device. After choosing the option "Format" in TWRP and typing 'yes' to confirm the decryption process, I was able to restore my backup.

Im having the same error in my realme xt...
sir..please help me.. I have a twrp backup of system image vendor image data boot recovery persist but im unable to recover because it shows an "error extract tar fork process ended up with error 255".during backup i had a pincode for screenlock.
i also have a backup of my internal storage in twrp but im not able to restore because of this error

LoganDark said:
Also, looks like user 10 is what happens when Google Play updates Device Personalization Services. Is this the generic "updates for system apps" user or is it specifically for that app?
EDIT: But updating that app doesn't create user 10. Interesting...
EDIT 2: User 10 is the guest user!! All I needed to do was create user 10 and that allowed me to restore my backup!
My post above is still good to see what I tried at first but it actually bricked my device until I factory reset it again, so :/
Click to expand...
Click to collapse
Hi. Did you create user 10 in Source, or in destination?
How did you do that in source?
If in destination, then is it possible to do it via TWRP?
EDIT: disregard. Mine user in the error path is 0 :-( '//data/system_de/0/'

just use option format data when entering wipe selection

erosman23 said:
just use option format data when entering wipe selection
Click to expand...
Click to collapse
doesnt work
redmi k20 davinci

Help with TWRP backup createTarFork() error 255

Hello,
I have Huawei Mediapad T5 tablet AGS2-W09 with Lineage 16.0 installed. I wanted to do backup in TWRP but I’m getting the error : createTarFork() process ended with ERROR : 255
I browsed to the backup location and found in the recovery.log that the problem is with the file :
/data/misc/bluedroid/pwxCDGSOXfhjCjV95kpJ7B
When I browse to /data/misc/bluedroid/ folder with Root Explorer, I see 3 files in it: bt_config.bak , bt_config.conf , macbt
When I browse to /data/misc/bluedroid/ folder with TWRP file explorer, I see again 3 files but names are completely changed, files are : pwxCDGSOXfhjCjV95kpJ7B , Fxe1ZW1HOXwv5qJD9v2MGD , yoVsIPDhhbKzaMIWc7rggD
I tried to delete this file through adb, but I get a message : permission denied. I tried to delete the file with TWRP file manager, but it didn’t work (there is no error message while deleting but the file is still there). Now after trying to delete this file, another problem appeared: when I’m in TWRP and want to do backup, the size of my data partition is now shown as 6969766643856MB !!!. Obviously it doesn’t let me do the backup because there is no enough space on my storage.
Is it safe to remove these 3 files by Root Explorer ?
Or at least the file “macbt” (same as pwxCDGSOXfhjCjV95kpJ7B) which is causing the problem ?
Is it safe to remove complete bluedroid folder ?
Any idea how to solve this without formatting the tablet ?

Look inside here:
createTarFork() process ended with ERROR=255
OOS 5 Oreo, non rooted, stock kernel, TWRP 3.2.1 blue_spark 8.61 every time i try to make a nandroid backup i get this error: createTarFork() process ended with ERROR=255 and backup fails any ideas?
forum.xda-developers.com

jwoegerbauer said:
Look inside here:
createTarFork() process ended with ERROR=255
OOS 5 Oreo, non rooted, stock kernel, TWRP 3.2.1 blue_spark 8.61 every time i try to make a nandroid backup i get this error: createTarFork() process ended with ERROR=255 and backup fails any ideas?
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, I saw this before. It is a problem related to multiple users, I do not have them.
I checked many threads and I couldn’t find similar one. My problem is related to files in the folders /data/misc/bluedroid/ which are maybe corrupted.
Can I just delete this folder ? Or the files which are inside? What does bluedroid folder and files inside do ?

having the exactly same problem as you, could not backup data in twrp because it errors out
I:Error adding file '/data/misc/bluedroid/8h7VnJk1nlucU5cHQERctB' to '/external_sd/TWRP/BACKUPS/8UE5T18301007382/2021-10-03--10-27-53/data.f2fs.win000'

Did you find a solution. I've the same problem on the same device.