Have TWRP installed on XT1031, but backup indicates "Failed" at end of process. I have tried v2.6.3.1 and v2.6.3.3, all with the same results.
CWM recovery works, but I prefer TWRP.
Any ideas?
more info on backup failure
CapeData said:
Have TWRP installed on XT1031, but backup indicates "Failed" at end of process. I have tried v2.6.3.1 and v2.6.3.3, all with the same results.
CWM recovery works, but I prefer TWRP.
Any ideas?
Click to expand...
Click to collapse
Moto G
Android 4.4.2
TWRP 2.6.3.1 or 2.6.3.3
The backup only fails when backing up Data -and- fails at the same point each time.
Here's an excerpt from the log showing the error:
Code:
I:tar_append_tree '/data/property' as '/property'
==> tar_append_tree(0xb7063e10, "/data/property", "/property")
setting selinux context: u:object_r:system_data_file:s0
E:Error appending '/data/property' to tar archive '/data/media/0/TWRP/BACKUPS/TA881017Z0/2024-03-17--13-14-40 KXB20.9-1.10-1.18//data.f2fs.win'
I:createTarFork() process ended with ERROR=255
I hope someone can figure out what the problem is.
You should try flashing the twrp from dhackers cm11 page. That one worked for me. But I never had a single trouble with either twrp or cm.
Sent from my XT1031 using Tapatalk
Resolved: Issue with TWRP
Had to Wipe - Format Data from TWRP then all was OK.
Fortunately I had Titanium backups to restore apps.
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
UPDATED:
After some testing the problem only occurs when i take back up for all partitions which isn't mandatory, but when i take back for (system, boot, data) which is enough for working backup and the restoring process is flawless
I did not disable security (PIN code) and restoring was successful
Short answer:
Only take backup for data, system, boot
R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
What about security? Did you have to disable all security before the backup?
I did not disable security (PIN code) and restoring was successful.
R1skNt said:
I did not disable security (PIN code) and restoring was successful.
Click to expand...
Click to collapse
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
lollyjay said:
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
Click to expand...
Click to collapse
Please see the 1st post (update)
PeterGuru said:
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
Click to expand...
Click to collapse
For what it's worth, I think I found a solution to why I couldn't restore the data partition. I can't explain why, but now it's working.
Previously, and historically, whenever I did a restore, I always wiped my device: system, data, boot.
This time; however, I did not wipe the device. I simply did the restore and everything worked. Therefore, the problem is somehow associated with the wipe.
Peter
I did a nanroid backup (boot, system, data only as per the instructions) of 5.1.8, rooted with magisk 16.6, ROM, installed lineage OS, than restored my backed up OOS ROM the restore process completed successfully but got stuck on boot logo, flashed magisk again along with the custom kernel but all to no joy, keeps bootlooping, however lineage restored fine and booted, any help be much appreciated, cheers.
joemossjr said:
You guys are crazy and I feel I need to answer your questions. So here we go. So just becuase there's multiple partitions doesn't mean you can dual boot or set up other things. So the way it works is the userdata partition is one partition. There are 2 system partitions for seamless updates two boot partitions for seamless and two firmware slots. In theory yes you can have two roms on both slots. Will they work? No. They will both use the same userdata partitions. So it will be incompatible.now you could in theory have lineage on one slot and oos on the other and if you ever want to go back just format userdata and fastboot --set-active=other to get to the other slot. But that doesn't really seem like a good idea. If you guys have other questions feel free to ask me!
Click to expand...
Click to collapse
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Bonito77 said:
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Click to expand...
Click to collapse
totally irrelevant to this thread, cheers.
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
bannannn said:
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
Click to expand...
Click to collapse
I assume you're in the directory twrp.img is in and are using the img file instead of the zip file? Also you renamed the img file to twrp.img?
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
kingwicked said:
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
Click to expand...
Click to collapse
I followed your guide. But I'm stuck at the boot animation...
RheinPirat said:
I followed your guide. But I'm stuck at the boot animation...
Click to expand...
Click to collapse
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
I was on 9.0.2
I restored the phone with the MSM tool and updated the ROM to 9.0.2 via manual system update like before.
Question:
Is it not possible to restore the whole system? Or only Data like you said under point 8?
Do I need verity? Because I think my phone is encrypted (flashed never a verity file)
Could I restore the whole system from a full TWRP (all partitions included) - only select data, system?
restoring system and other never worked for me. always failed. but only restoring data partition always worked
when you restore only data. your all apps. settings messages everything will restore even magisk modules.
im not sure about encrypted because. encrypted phone when restoring twrp messed up my whole internal memory. and i had no choice but to wipe it.
so there is no issue with no verity. as it helps not to scramble the internal memory of your device and you wull not loose any data or get stuck on qualcomm dump mode
but remember the steps to verity when installed on already used rom with data. you have to format data to remove encryption
only restoring data is the best option. you can try without no verity to restore i think may work but follow all options i mentioned
but i dont recommend to use with no verity.since using no verity i have never got to wipe my internal memory
I've bricked my device twice after trying to restore and always resorted to just a clean flash of stock using the MSMDownloadTool... wish I'd found this thread sooner as you just solved my third backup restore soft-brick!
I'll also remember to just backup system/data/boot going forward...
Thanks!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
Thanks buddy, It worked like a charm.
About the pin removal, as you siad there is a good tutorial in below link which can be used.
https://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
Thank you!!!
You saved my phone (and life).
I can confirm your procedure is working with my back up made on 10.3.2 using a usb c key.
I just restored the DATA. Nothing else!
Thank you so much!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
Can anybody help?
My HTC U11 still run on Nougat.
Yesterday I want to update with the newer version of Nougat (Not Oreo)
I already make a data backup with TWRP, big backup 22Gb.
Then I update the new stock Rom from PC, it had no problem.
Go to download mode, and then install TWRP again with ADB from PC.
Go to TWRP Recovery, it still works.
The last thing I do is to try to restore the 22Gb data back to my phone.
And it always get error on 9% with "extractTarFork() process ended with ERROR: 255"
I already change with difference TWRP from 3.1.1.0 to 3.2.3.0, still the same.
Restore to previous version of Nougat with TWRP (system, system image, boot image, recovery). Try to restore backup data again with no luck.
Try to check MD5 with the backup data, and it said matched, no corrupt.
Already try searching in the web, but with no solution too.
Do anyone ever have the same problem and solved it?
Not me here, but you can try RUU manually flash Oreo
Hi there, Thaught, I was on the save side for 2 years, having my TWRP, made a backup after every change on the 12+, now I had to recover it...
Steady installed TWRP 3.3.1.0 on 1.68.401.6 does a restore without errors, restart ends with bootloop.
So I flashed new with 1.53.401.5, tried to fastboot boot twrp.3.2.3.3 and restore my backup -> bootloop
Flashed 1.53.401.5 again, made a backup of that fresh system with booted TWRP, to test that restore, brings the same bootloop.
Have to say, the twrp versions are the right ones for the used SW versions. Decryption is working.
Where is the blind spot in my brain??
Please delete my ask here, I'll try my luck in TWRP thread. Still my problem.
Hello!
I am trying to restore a TWRP backup of the whole phone but after the restore, I always get booted into the recovery.
I took the backup by:
Bash:
adb backup --twrp backup.ab
Here is how I am trying to restore the backup
Reflash stock android firmware (same version as the backup)
Boot into stock android and setup pin
Boot into recovery
Connect to PC
Bash:
adb restore backup.ab
Wait until the restore completes. It seems that there is no error during the restore.
Reflash Magisk v24.1
Try to reboot
Upon reboot into TWRP I am greeted with this message:
Android Rescue Party trigger! Wipe data and caches and/or clean-flash you ROM!
The reported problem is:
'--reason=set_policy_failed:/data/misc'
E: Unable to decrypt FBE device
Failed to decrypt data.
Unable to decrupt with default password. You may need to perform a Format Data.
Click to expand...
Click to collapse
Is there anything I am doing wrong? How could I debug this problem?
Here are some relevant info about the phone:
Android 11.0.0 (RQ3A.211001.001, Oct 2021)
Pixel 3a
TWRP 3.6.0 : twrp-3.6.0_11-0-sargo.img
Magisk v24.1
Thank you
Same here. I've spent a few days trying different methods and nothing works. Looks like it's a bug in TWRP.