I know this is the wrong form but sorry I can't write in the right form
I am using Redmi Note 7
So I was trying to install a custom ROM (corvus os v9.5)
Link to it : https://forum.xda-developers.com/redmi-note-7/development/rom-corvus-8-5-t4153687
I took backup and chose everything to stay safe but now I can't recover the backup
I wiped dalvik/art cache, Cache, Data, System
In the beginning it said that it can't wipe system
So I wiped all data from my phone and copied the backup files back to my phone and tried to recover but it didn't work too and showed the same error then I tried to install the last version of TWRP to fix the problem but now it shows this error
"extractTarFork() process ended with signal: 9"
I didn't find any solution on the internet
Help please :crying:
LilKeroo said:
I know this is the wrong form but sorry I can't write in the right form
I am using Redmi Note 7
So I was trying to install a custom ROM (corvus os v9.5)
Link to it : https://forum.xda-developers.com/redmi-note-7/development/rom-corvus-8-5-t4153687
I took backup and chose everything to stay safe but now I can't recover the backup
I wiped dalvik/art cache, Cache, Data, System
In the beginning it said that it can't wipe system
So I wiped all data from my phone and copied the backup files back to my phone and tried to recover but it didn't work too and showed the same error then I tried to install the last version of TWRP to fix the problem but now it shows this error
"extractTarFork() process ended with signal: 9"
I didn't find any solution on the internet
Help please :crying:
Click to expand...
Click to collapse
Hey, did you find a solution to this? I have the same error ("extractTarFork() process ended with signal: 9").
I was trying to restore a backup of, I think, a correct stock version.
Related
I've been trying to backup my ROM the past few days but I keep getting an error when nandroid tries to make an image of my /cache/ partition. I tried wiping the cache, but still no luck. I looked if there was anything in it but it seems to be empty.
Has anyone else had this problem? How do I solve it? Should I backup my apps in Titanium and do a full wipe/reinstall?
Thanks in advance.
*EDIT*
This is the exact message I'm getting when it fails:
Code:
Backing up cache...
Error while making a yaffs2 image of /cache/!
*bump*
Same here.
Try wiping dalvik cache too. Or go to rom manager and flash clockwork mod again.
Tried that but it never helped. The only way I got it going was doing a full wipe and flashing everything again from scratch.
I had the same problem and all I tried was unmounting the cache like 3 times and after that the backup worked again, tho it still showed the cache was mounted..
hope I could maybe help..
EDIT:
I tried to backup again and it showed the cache error.. again..
then I unmounted the cache (3 times again )
but no luck.. still recieved the error message..
after that I tried wiping the cache..
then it didn't even start the backup..
it gave me a "did not find boot" error or sumthin,.
well, I guess it might work sometimes with the unmount cache thing but then again it didn't work twice..
anyone have a fix for this? I cant make a nandroid backup...
So i have twrp 2870, and i tried to install VIBEUI_V3.0_1553_7.394.1_DEV_K50-T5_WC47569FBB but i got this error: "Error executing updater binary in zip(location of zip)"
Now i did all the necesery steps i wiped cache, dalvik, system, data and i went to install it and it gave me that error.And i didnt back anything up because i thought everything would work since everyone told me those were the steps but because of my awesome luck my phone is now without operating system since i wiped all and i cannot install the vibeui, so can anyone help me?
i FIXED IT, DELETE THIS THREAD
i am having following error in twrp. due to this i cannot take backup. any way to fix this.
just now i wiped data completely, still it didn't fixed the error.
please help me to resolve this.
What version of TWRP are you using and exactly what were you trying to do before you got the error?
That looks like some encryption stuff to me.
This error displays as soon as I go to TWRP and i was unable to do nandroid back up.
I went to wipe advance wipe and selected data, instead of wipe, there was a button above the swipe option, i clicked that and repaired partition, and i think it fixed the issue.
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
skorpien said:
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
ashyx said:
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
Click to expand...
Click to collapse
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
skorpien said:
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
Click to expand...
Click to collapse
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
ashyx said:
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
Click to expand...
Click to collapse
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
skorpien said:
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
Click to expand...
Click to collapse
Did you back up the efs partition with twrp?
If so try restoring it.
ashyx said:
Did you back up the efs partition with twrp?
If so try restoring it.
Click to expand...
Click to collapse
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
skorpien said:
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
Click to expand...
Click to collapse
Don't restore everything just EFS No need to keep wiping dalvik it serves no purpose when formatting or wiping the data partition.
Also FORMAT not wipe the data partition (note this wipes internal storage)
If it still doesn't boot install the combo firmware. Let it boot, factory reset from settings then reboot to download mode and install the stock firmware again.
Hello,
when I try to restore my TWRP backup of Lineage 17 on my Samsung Galaxy A5 2016 I run into the
extractTarFork() process ended with ERROR: 255​issue, and have tried several methods which I have found when googling for fixes, but none has worked so far.
This is what I've tried:
- unmount the data partition before restoring backup
- just restore system, data and boot, tick off the others
- wiped data/system/cache, flashed rom+gapps, flashed backup with all sections activated (radio, system, data,...)
- wiped data/system/cache, flashed rom+gapps, flashed backup with only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, wiped dalvik/cache after, flashed backup w/ only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, reboot, clicking next on every configuration screen, reboot to recovery, restore only data from backup
The issue seems to always occur at the same point in the process, in the progress bar its either at ca 45% or 58%, depending on if only data or everything is supposed to be restored. Restoring everything _BUT_ the data partition works, but the stuff I need to access is the data.
Kind regards
Hello,
I managed to fully restore the backup follwing this guide
Now my phone boots up to the point right after the Lineage logo is shown, where it says "starting the phone" and would probably ask for sim pin if I had a sim card in it. Then it reboots and does the whole thing again.
Does anyone have an idea how to fix this?
Kind regards