When I try to restore the stock MIUI 12.5.2 backup with OrangeFox, I get "extractTarFork() process ended with error: 255" error. When this happens, it's very tedious to try custom roms. Is there a good solution for this? I'm using OrangeFox version R11.1_4 and I'm getting this error when restoring data. I've tried the following for this problem; I took a backup without screen lock, I removed MIUI account but the result is negative.
Related
Hello
I've installed a couple of ROMs via TWRP. Some work, some don't.
But now, even when I try to install ROMs I had already installed previously, the installation fails.
I get a message "Update process ended with signal 7
Error installing file"
What to do ?
I guess this happens if you not wipe data and reboot before installing. But only if TWRP version installed on your phone and the TWRP version from the phone that made the backup are different.
You van use this http://forum.xda-developers.com/showthread.php?t=2522762
It helped me.
I was trying a new rom so I made a twrp backup, I was on MIUI 9 stable, It was an Oreo based rom, flashed gapps, custom kernel and magisk and MIUI firmware
Trying to restore the twrp backup after formatting (Tried Every option to format) It basically shuts off the phone while restoring, just the system (or system Image) partition, restoring data was working fine. I had to flash the system manually, then restoring data, which worked fine. Just for testing I tried to recreate a backup and restoring It Just After and the same behaviour happened! Even without flashing anything. Whats happening?
lukypuie said:
I was trying a new rom so I made a twrp backup, I was on MIUI 9 stable, It was an Oreo based rom, flashed gapps, custom kernel and magisk and MIUI firmware
Trying to restore the twrp backup after formatting (Tried Every option to format) It basically shuts off the phone while restoring, just the system (or system Image) partition, restoring data was working fine. I had to flash the system manually, then restoring data, which worked fine. Just for testing I tried to recreate a backup and restoring It Just After and the same behaviour happened! Even without flashing anything. Whats happening?
Click to expand...
Click to collapse
There is a new twrp version (3.2.0.0) which is supposed to show better oreo support. Are you on that version?
Sounds a little confusing how you described what you flashed in which order ... Also I don't get exactly which rom you're trying to restore. Can you give more accurate and precise info?
The newest TWRP 3.2.3.-1 does not let me boot into ROM, just brings me back to TWRP again. I have to restore a backed up boot image (with 3.2.3-0) to boot normally. Even flashing TWRP 3.2.3-0 in TWRP does not bring me back.
Anyone else having experiencing this? I have attached my recovery logs.
I was on stock ...and just install los16 without problem... So i dont have problems with TWRP.
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
jhedfors said:
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
Click to expand...
Click to collapse
There is always a risk when flashing your device. One of the reasons why I prefer to flash using Linux was that Windows would have so much going on in the background that I risked the data transfer being corrupt. That said, if you're using Windows, I'd close all programs and especially disable any anti-virus running in the background. Sure, Linux may have a few things running, but I have always found it did a better job multitasking resources than Microsoft Windows with a fewer chance of data loss.
It is probably because after installing Google Apps, your /data partition gets corrupted.
So after installing Google Apps, go to TWRP > Wipe > "Format Data" & reboot.
I've the same problem & this resolves the issue for me.
For me, this did not help. I had to reflash everything from bootloader.
Funny thing is: it just has downloaded and installed an OTA update. With open bootloader.
I ran into this issue yesterday when a bad flash caused the infamous "no bootable A/B" error. After I resolved it and install TWRP I kept being rebooted back into TWRP. The 3.2.3-0 version resolved everything. I really do believe 3.2.3-1 is a bit buggy. I mean it works, but once you really start to use it more than the average user, you start to notice little things.
I too had this same issue. Eventually realized that updating TWRP by flashing zip from TWRP caused it. I had to flash stock boot partition, then follow the process for flashing TWRP as if you are flashing it for the first time (first boot into TWRP and then flash the corresponding zip). This resolved the issue.
After installing at least one Magisk module the phone bootloops every 2nd reboot and it is consistent. Flashing a no-verity zip gives a few more reboots before bootlooping but the issue is quite annoying because I need to restore a backup from TWRP every time a bootloop occurs, so I have to reinstall everything again.
Maybe returning to full stock firmware (I have the original boot image, but not the original recovery) can help, but the lolinet mirrors do not have the latest firmware available.
Apparently, wiping data after restoring backup helped a lot, phone has survived 5 reboots so far with 2 Magisk modules flashed
Nevermind, latest reboot was a bootloop, but I think the culprit here is the Magisk Manager for Recovery Mode, I will restore backup again and see if that module is the cause of it
If it helps, TWRP showed an error before cleaning caché:
"E:Error creating fstab"
On my phones I have always used the backup's function offered by TWRP's recovery .
I've always been able to restore the nandroid's backups without any problems.
However, whenever I try to restore a backup on my Note 9, the phone always goes into bootloop.
I've never had this happen with my other phones (S3 and LG G5).
I wouldn't want to have to do other things to do a successful restore.
I can't restore a nandroid backup as well on my Note 9 exynos. I think it had something to do with force encryption of the phone.
I found in an XDA thread a zip to disable dm-verity and force encryption, flashable via twrp.
After successfully disabling ecryption of my Note 9, I was able to successfully restore a previous nandroid backup.
XTrail02 said:
I can't restore a nandroid backup as well on my Note 9 exynos. I think it had something to do with force encryption of the phone.
I found in an XDA thread a zip to disable dm-verity and force encryption, flashable via twrp.
After successfully disabling ecryption of my Note 9, I was able to successfully restore a previous nandroid backup.
Click to expand...
Click to collapse
Thank you for your reply.
I mean, let me get a better understanding of what you did.
Did you first flash the "Disable_Dm-Verity_ForceEncrypt"'s zip and then restore the nandroid backup?
These are the steps I did, but not sure of the exact order:
1. Format data & reboot to Recovery
2. Flash rom (I'm using LOS 17.1 w/ microG) & reboot to Recovery
3. Flash magisk & reboot to Recovery
4. Flash the zip below
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
5. Reboot to System, complete the start up of the new Rom and confirm that the phone is now decrypted.
6. Go to Recovery and restore my nandroid backup (I created this nandroid backup when my phone is already decrypted. I haven't tested restoring a previous backup with my still encrypted phone).
I successfully restored my nandroid backup finally. Before I always fail, giving me a hard time restoring my individual apps using TBackup or Migrate.
XTrail02 said:
These are the steps I did, but not sure of the exact order:
1. Format data & reboot to Recovery
2. Flash rom (I'm using LOS 17.1 w/ microG) & reboot to Recovery
3. Flash magisk & reboot to Recovery
4. Flash the zip below
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
5. Reboot to System, complete the start up of the new Rom and confirm that the phone is now decrypted.
6. Go to Recovery and restore my nandroid backup (I created this nandroid backup when my phone is already decrypted. I haven't tested restoring a previous backup with my still encrypted phone).
I successfully restored my nandroid backup finally. Before I always fail, giving me a hard time restoring my individual apps using TBackup or Migrate.
Click to expand...
Click to collapse
I already do all this when I install the new rom. So, my phone should be decrypted.
Then after some time I make a nandroid backup. However, when I go to restore the backup the phone goes into bootloop.
So, it means that with the restore the phone comes back encrypted again. That's why it goes into bootloop.
Before, I'm flashing the 'no-verity-opt-encrypt-6.1.zip' but always ended up encrypted after reboot. Only after I flashed 'disable_dm-verity_forceencrypt.zip' that my phone became decrypted, and perform a successful nandroid restore later. I'm using twrp 3.4.0.
XTrail02 said:
Before, I'm flashing the 'no-verity-opt-encrypt-6.1.zip' but always ended up encrypted after reboot. Only after I flashed 'disable_dm-verity_forceencrypt.zip' that my phone became decrypted, and perform a successful nandroid restore later. I'm using twrp 3.4.0.
Click to expand...
Click to collapse
If I understand correctly, before restoring a nandroid backup you flashed 'disable_dm-verity_forceencrypt.zip' and then did the restore.
Right?