Hi all,
I have A6000 with OOS 9.0.5. I installed magisk and TWRP with this guide. I did a full backup, however I cannot restore it. I get error 255 on tarExtractFork(). I use official TWRP 3.3.0. After failed restore I can still boot to (now freshly wiped after attempted restore) system. Even backups of this clean system cannot be restored.
For the record, I don't have a second profile, no "999" user id, I didn't change slots, I removed screen lock before making backup. I still have this problem even if I backup just data, with all other options unticked.
Any help? I come from a device, which didn't have any problems with backup/restore so this is a bummer for me. But I'm sure that users of OP6 can do backups and restores.
Thanks!
For anyone that also has the same problem:
This helped me. I have a feeling that flashing just data through fastboot could be enough, but I didn't have an occasion to check it, as even subsequent restores worked.
I used this to flash device in fastboot mode.
Related
So, everytime I restore my backup with twrp, I always get some errors after restore.
Sometimes systemUI error, sometimes restore doesnt run successfully, etc.
I just want to know, is there actually a proper way to backup and restaore using twrp (like wiping things first, etc) or just directly backup and restore?
Thanks!
I never managed to get backup done and restored, never on this phone, no matter what twrp i use
Hi,
I have tested the liquidremix rom which is great, but I still wanted to go back to my stock OSS
So I started TWRP, hit restore, everything seem to work fine, but when I reboot the system I'm stuck at the boot animation.
When I reboot the device to TWRP and check the file manager or my backup folder there are only cryptic and weird letters...
How do I restore my backup properly ?
Try to go back to TWRP 3.2.1.0 i think that that works
everything is gone, you will have to restore with the brick tool, happened to me last week and still not sure why, apparently backing up with TWRP you only need to ticket DATA and that's it.
You need to do two things whenever you restore with TWRP. First is factory reset in TWRP before the restore (that will wipe data). Second is restore system, boot, and data ONLY.
The weird file names and cryptic letters is from the encryption from the old rom. I strongly recommend that you invest in an OTG flash drive so you can store TWRP backups on it. Then you can properly wipe the phone. On the plus side this has happened to me before and I never needed anything special like the unbrick tool to get my TWRP backup up and running smoothly.
and there is a better twrp than twrp. The official is by Dees Troy and the un-official one by Joe Moss Jr. is here. https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Joe's big improvement is a usable 'mtp', ie. access that thumb drive.
Also puts the vibration back in to the key press.
First if you r seeing weired letters in twrp like xdjdhdhdhd folders. Then go to fastboot mode flash newest twrp. Img then ij recovery first flash your liquid remix furst, then flash twrp installer zip niw reboot to recovery.
Now factory reset your phone.
Now if you have oos backup. Then restore everything except system.
And then restore system alone at last now reboot it will work.
your gonna need the flashable oos 5.1x which is one here
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
fastboot to twrp
abd push the stock.zip to the phone <-assuming you know this.
and flash it from twrp.
reboot
fastboot twrp again and flash twrp.
this is where decryption comes in handy
Restoring backups with twrp will fail almost all the time. I've yet to do a successful restore and I've tried every method. You're gonna have to flash back to stock OOS and start over.
If anyone has successfully restored more than one backup then I would start a new thread with the exact method you used.
That worked.
I still wonder why not to restore system.
If I take a nandroid backup should one backup
system or system image, data or data image ?
I was trying a new rom the Resurection Remix V6.2.0 Android 8.1.0. i wanted to go back to my TWRP Backup of OOS 5.11 . I wiped data/cache/System . Tried to restore rom . it restored successfully but i didnt do wipe data thing. when i tried to reboot twrp blu, the recovery was lost. then i had to fastboot boot reovery. and lot of wierd folders were created on my phone internal memory. All data lost.
i had to flash the full 5.11 stock zip via twrp. tried to reboot again lost in bootloop. Switched back to stock recovery and make a factory reset then it booted.
switched off the phone back to Blu spark TWRP. again wipe data cache and system. Then restore the TWRP Backup previously double saved on a usb drive. This Time it restored successfully and booted as well fine.
i think i should have made a factory reset or format data before restoring from A Lineage OS Rom OS to OOS TWRP Backup
thats what made the whole internal drive mess and to be formatted as well
My Question is it only important to format data and then restore twrp or also backup and make restore of system.img of OOS backup as well
I'm testing various custom rom so often I want to go back from the custom rom to OOS. I have a twrp backup of my OOS, the problem is that i cannot restore it properly. If, from the custom rom, I reboot to recovery and restore the backup, the phone bootloops. I've also tried to format data and rebooting to recovery before restoring the backup, but this doesn't work either.
The only way I've found to properly restore the backup is to completely reflash OOS via MSM tool (or fastboot), but this takes really a lot of time, because apart from the MSM tool installation itself, it relocks the bootloader so I have to wait for the system to boot up, toggle oem unlock, unlock again the bootloader, wait for the wipe and for another system boot up, boot in twrp using fastboot command, transfer 13GB of data to the phone and then FINALLY restore the backup.
Is there an easier, and most important, faster, way to restore the backup?
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943
On this link scroll down and read the "tips", if you have backed up rom the way it says you shouldn't have any problems in restoring, hope this helps, cheers
Whenever I make a backup in TWRP, and later try to restore it, I get no errors, the restore seems to go fine, but when I reboot, I never get anything but a bootloop on the Mi logo. Even if the system was working when I made the backup, working before I do the restore, and haven't changed the encryption (same password, same ROM, no /data wipe) the restore breaks it. It's happened on Xiaomi.EU, it's happened on AOSiP, ArrowOS, several versions of mauronofrio's TWRP (including the latest) and Sky Hawk recovery - I've just never had a successful restore on this phone. Am I doing something wrong?
Installed Lineage 18.1 OS, TWRP 3.6.0_11-0 and Magisk, booted system, added PIN and fingerprints, all was good. Booted back into TWRP and made a full backup of all partitions. Tried a test restore of Super and Data partitions. Upon reboot, I get the lineage splash/boot screen, then "phone is starting" forever. From reading around, this is due to the system trying to access encrypted data. Questions: 1) I'd like to be able to use TWRP for two things: a) restoring to a new device should this one break, and b) reverting back to previously backed up state of operation on the same device. What partitions should I be restoring for each of these? 2) Is there a fix or proper method to make restorable backups using TWRP?
Exactly the same situation. And have exactly the same questions.
Had the same problem, wiped data, repaired data file system, rebooted into system to disable the pin. Then restored my TWRP data backup again, now it boots into system, just had to reboot twice because the gestures and staturbar didn't work first. Now I just have to tweak some little details again to get it how it was.
Didn't solve my main problem though, SMS not working. Wiped and repaired data again, now it works. Welp, guess I have to set it all up again from here.