Related
My OP6 has the TWRP 3.2.2 installed, with OOS 5.1.9 and Magisk. I would like to try out the new HAVOC rom, so i have done a full TWRP backup of all the partitions of the phone, and another one with only the BOOT, SYSTEM and DATA partitions.
But I have many doubts about the reliability of the TWRP restore: I read several posts related to bootloop and failures. I would like to avoid having to reinstall the whole phone from scratch.
Has anyone successfully full backed up and restored on the OP6 with TWRP? If so, which partitions did you backup?
The alternative would be to use Titanium backup, but the restore procedure would be much more complex.
I want answers about this as well. What partitions do we backup? What's the process to restore? I tried backing up everything then restoring it and i got a blank screen when I was suppose to see the boot animation.
Marlenio said:
My OP6 has the TWRP 3.2.2 installed, with OOS 5.1.9 and Magisk. I would like to try out the new HAVOC rom, so i have done a full TWRP backup of all the partitions of the phone, and another one with only the BOOT, SYSTEM and DATA partitions.
But I have many doubts about the reliability of the TWRP restore: I read several posts related to bootloop and failures. I would like to avoid having to reinstall the whole phone from scratch.
Has anyone successfully full backed up and restored on the OP6 with TWRP? If so, which partitions did you backup?
The alternative would be to use Titanium backup, but the restore procedure would be much more complex.
Click to expand...
Click to collapse
Our TWRP is very buggy i tried to restore whole backup using twrp and it failed showing error. But somewhere i got solution in xda.
Backup only data, system and boot and restore it will work.
But for safety always keep one extra full backup of all things like efs,modem, data, system, boot, vendor. Because sometime if something goes wrong u have rescue operation always there
Since this device is super easy to unbrick if needed I personally only keep a data backup of each ROM I use on my flash drive.
So I don't need to do a full setup when flashing a different rom.
Otherwise if something crazy happens and the device gets bricked, it's fixable with a PC.
Sent from my LG-H932 using XDA Labs
Trying to get a clean backup before I go mucking about trying different ROMs, and I can't get it to work like I am used to. Just came from Nexus 5 for my wife and Onplus One for myself, backup was very simple. I am sure it's because I don't quite understand how A/B partition affects the backup, but I am not succeeding on solving this myself.
I am full stock updated to 9.0.3, unlocked no problem got BluSpark 9.93 TWRP and Magisk 18. If I make a backup, using default partitions or all partitions doest matter, when I restore it gets stuck on boot animation, and no matter what I do from there it ends up hard bricked. I have gotten quite fast at MSM Tool fix, and no major data loss because I have manual backup on computer, however I dont want to MSMTool every time I try a new ROM.
The ONLY restore I have succeeded at is to do a complete MSMTool fix, update back to 9.0.3, get TWRP and Magisk back in place, then restore JUST the data partition. that brings back my settings, apps, logins etc, but it is a huge hassle to do. I want to get to the point where I can say "meh I dont like LineageOS, lets just restore my clean Stock backup" and be done in five minutes.
I3ig Al said:
Trying to get a clean backup before I go mucking about trying different ROMs, and I can't get it to work like I am used to. Just came from Nexus 5 for my wife and Onplus One for myself, backup was very simple. I am sure it's because I don't quite understand how A/B partition affects the backup, but I am not succeeding on solving this myself.
I am full stock updated to 9.0.3, unlocked no problem got BluSpark 9.93 TWRP and Magisk 18. If I make a backup, using default partitions or all partitions doest matter, when I restore it gets stuck on boot animation, and no matter what I do from there it ends up hard bricked. I have gotten quite fast at MSM Tool fix, and no major data loss because I have manual backup on computer, however I dont want to MSMTool every time I try a new ROM.
The ONLY restore I have succeeded at is to do a complete MSMTool fix, update back to 9.0.3, get TWRP and Magisk back in place, then restore JUST the data partition. that brings back my settings, apps, logins etc, but it is a huge hassle to do. I want to get to the point where I can say "meh I dont like LineageOS, lets just restore my clean Stock backup" and be done in five minutes.
Click to expand...
Click to collapse
hi same problem and a quick fix is to back up system image instead of system and vendor image instead of vendor
ps if you have a problem with password after flush this
https://androidfilehost.com/?fid=818070582850506962
I3ig Al said:
Trying to get a clean backup before I go mucking about trying different ROMs, and I can't get it to work like I am used to. Just came from Nexus 5 for my wife and Onplus One for myself, backup was very simple. I am sure it's because I don't quite understand how A/B partition affects the backup, but I am not succeeding on solving this myself.
I am full stock updated to 9.0.3, unlocked no problem got BluSpark 9.93 TWRP and Magisk 18. If I make a backup, using default partitions or all partitions doest matter, when I restore it gets stuck on boot animation, and no matter what I do from there it ends up hard bricked. I have gotten quite fast at MSM Tool fix, and no major data loss because I have manual backup on computer, however I dont want to MSMTool every time I try a new ROM.
The ONLY restore I have succeeded at is to do a complete MSMTool fix, update back to 9.0.3, get TWRP and Magisk back in place, then restore JUST the data partition. that brings back my settings, apps, logins etc, but it is a huge hassle to do. I want to get to the point where I can say "meh I dont like LineageOS, lets just restore my clean Stock backup" and be done in five minutes.
Click to expand...
Click to collapse
Just backup data partition and flash your OOS zip when you want to return to OOS in TWRP. After you flash it, restore data and you'll be golden.
mikex8593 said:
Just backup data partition and flash your OOS zip when you want to return to OOS in TWRP. After you flash it, restore data and you'll be golden.
Click to expand...
Click to collapse
I tried that before but it either got me stuck in a boot animation or completely corrupted the phone with random gibberish named folders and having to MSMtool to recover. If I was on Havoc ROM, my understanding is that you cannot just flash the stock OOS zip over the top to return to stock.
Even if it did work that still takes out TWRP and Magisk, which is what i'm trying to avoid. I know it works different than it used to on the old partition setup, but is it possible to just swap back and forth between different ROMs using recovery backups? I would like to give Havoc and Liquid a week of use each but I dont want to nuke and restart my whole thing every time I switch. its fun to try other things but at the end of the day I still want to have a phone that doesnt need to be set up yet another time.
I3ig Al said:
I tried that before but it either got me stuck in a boot animation or completely corrupted the phone with random gibberish named folders and having to MSMtool to recover. If I was on Havoc ROM, my understanding is that you cannot just flash the stock OOS zip over the top to return to stock.
Even if it did work that still takes out TWRP and Magisk, which is what i'm trying to avoid. I know it works different than it used to on the old partition setup, but is it possible to just swap back and forth between different ROMs using recovery backups? I would like to give Havoc and Liquid a week of use each but I dont want to nuke and restart my whole thing every time I switch. its fun to try other things but at the end of the day I still want to have a phone that doesnt need to be set up yet another time.
Click to expand...
Click to collapse
I only backup data, but I'm also decrypt, which helps. There really isn't a simple flip flop like you used to do. I backup data, then install OOS zip, flash TWRP, reboot recovery, flash noverity (for decrypt), magisk then kernel and reboot and all is the same as it was before.
mikex8593 said:
I only backup data, but I'm also decrypt, which helps. There really isn't a simple flip flop like you used to do. I backup data, then install OOS zip, flash TWRP, reboot recovery, flash noverity (for decrypt), magisk then kernel and reboot and all is the same as it was before.
Click to expand...
Click to collapse
thats a shame, it was really nice to be able to quickly change roms on my phone.
Regarding decrypt, I noticed one of my backup attempts was hampered when I had pin/fingerprint enabled before backup and since then I just make sure to remove all locking before backup. is this noverity thing used to strip the password from a backup or?
EDIT: so just to make sure I am understanding, when I do a backup in TWRP I can only really make use of the Data partition backup. and if i want to flash a ROM i basically have to do it as if it was a fresh install, get TWRP/Magisk back in, THEN restore my partition, every time I change ROM?
I3ig Al said:
thats a shame, it was really nice to be able to quickly change roms on my phone.
Regarding decrypt, I noticed one of my backup attempts was hampered when I had pin/fingerprint enabled before backup and since then I just make sure to remove all locking before backup. is this noverity thing used to strip the password from a backup or?
EDIT: so just to make sure I am understanding, when I do a backup in TWRP I can only really make use of the Data partition backup. and if i want to flash a ROM i basically have to do it as if it was a fresh install, get TWRP/Magisk back in, THEN restore my partition, every time I change ROM?
Click to expand...
Click to collapse
The best way to flip between ROMs is to take a data backup specifically for each ROM, but install the ROM as per instructions every time.
The noverity just maintains decrypt after you decrypt your data partition.
Restore your data any time while in recovery, and it'll be fine as long as it's data for that specific ROM. The order in which you do everything does not matter when restoring data and flashing the ROM.
EDIT: the order doesn't matter in regards to your data restore. Everything else matters in those steps, in their specific order, but you can restore data at any time as long as the other steps are in order.
mikex8593 said:
The best way to flip between ROMs is to take a data backup specifically for each ROM, but install the ROM as per instructions every time.
The noverity just maintains decrypt after you decrypt your data partition.
Restore your data any time while in recovery, and it'll be fine as long as it's data for that specific ROM. The order in which you do everything does not matter when restoring data and flashing the ROM.
Click to expand...
Click to collapse
Alright that makes sense, thanks for the help. again, shame it's not as easy as it used to be, maybe this will finally get me to settle on a single ROM and just be happy with the phone I paid so much for lol.
I3ig Al said:
Alright that makes sense, thanks for the help. again, shame it's not as easy as it used to be, maybe this will finally get me to settle on a single ROM and just be happy with the phone I paid so much for lol.
Click to expand...
Click to collapse
The a/b partition is a failsafe that also makes updates easier overall. OOS is a solid ROM. I would recommend xXxNoLimits. That's what I use along with Smurfkernel. It's all preference.
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Encrypted?
arkansawdave74 said:
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Click to expand...
Click to collapse
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Skippy12359 said:
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Click to expand...
Click to collapse
I noticed when installing RR that it actually needs that Lineage recovery to factory reset after the install. A TWRP factory reset wouldn't help it, and it wouldn"t boot after the install. Funny how they try so hard to stop us tinkerers, then steal all our cool ideas for their stock ROMs. I see Linux phones in my future.
I wonder if a factory reset with that Lineage recovery would help after a TWRP restore? Next time I may try that.
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
WoKoschekk said:
Encrypted?
Click to expand...
Click to collapse
Just saw this. No. I had flashed dm-verity. Good thinking.
arkansawdave74 said:
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
Click to expand...
Click to collapse
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Skippy12359 said:
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Click to expand...
Click to collapse
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
arkansawdave74 said:
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
Click to expand...
Click to collapse
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Skippy12359 said:
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Click to expand...
Click to collapse
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
arkansawdave74 said:
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
Click to expand...
Click to collapse
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
Yup. I've restored it twice and made another with boot included and it booted as well. I hope it works with RR too, but I've got a helluva headache. I may stop messing with it for now.
Oh, I had wiped dalvic (actually ART), system, and data. I don't think boot was an option during wipe.
You know, I've only had one device before thar force encrypted, and back then, TWRP couldn't decrypt /data except by formatting. Now it can. That's why I didn't suspect it was an encryption issue.
I was still using a Galaxy S5 with crDroid 7.1.2 built by me until last week. It died, may it rest in peace.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
My goal was to have twrp backup of stock pie which is really great in my opinion and also be able to flash Q gsi's like I do on my Moto g6. So far any backup restore of stock just bootloops and any gsi just hangs at boot logo or boots back to recovery.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Skippy12359 said:
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Click to expand...
Click to collapse
For stock, I wonder if you could boot TWRP after all those fastboot commands and flash dm-verity before booting stock. You may be able to keep stock from encrypting. I don't know for sure though.
I've been using Beta 19 OOS with all of my apps configured for quite a while now. But, I'd like to try some custom roms. If I don't end up caring for the custom roms, I'd like to easily restore back to OOS Beta with all of my apps. I've never tried a full restore with TWRP. Does it work successfully? Are there any "gotchas" that I should know about?
Yeah, I did it over the weekend.
Tried crdroid and lineage Android 11. Ran into some issues and was fed up.
I don't think you can fully restore photos and music and so on on your internal storage, so I backed up mine.
My steps were:
In twrp, format device,
Reboot to bootloader and reflash twrp using adb.
Reboot to twrp and copy over twrp installer, oos beta19 and Magisk.
Flash Oos beta 19,
Flash twrp installer,
Flash Magisk,
Reboot to twrp
Flash Magisk,
Reboot to system.
Your device will then be on stock oos 19 and start the setup process. You don't have to complete it, so just skip all the steps. When you can, restart to twrp and use the restore functionality.
Everything should then be as it was when you made the backup, except for the music and videos I think.
Pierre413 said:
Yeah, I did it over the weekend.
Tried crdroid and lineage Android 11. Ran into some issues and was fed up.
I don't think you can fully restore photos and music and so on on your internal storage, so I backed up mine.
My steps were:
In twrp, format device,
Reboot to bootloader and reflash twrp using adb.
Reboot to twrp and copy over twrp installer, oos beta19 and Magisk.
Flash Oos beta 19,
Flash twrp installer,
Flash Magisk,
Reboot to twrp
Flash Magisk,
Reboot to system.
Your device will then be on stock oos 19 and start the setup process. You don't have to complete it, so just skip all the steps. When you can, restart to twrp and use the restore functionality.
Everything should then be as it was when you made the backup, except for the music and videos I think.
Click to expand...
Click to collapse
Thanks! What issues did you have with the custom roms?
ledvedder said:
Thanks! What issues did you have with the custom roms?
Click to expand...
Click to collapse
I couldn't get lineage 18.1 working with Magisk and Twrp.
Crdroid I could use for a while, but when I tried to update it, my phone would only boot to Twrp.
Pierre413 said:
I couldn't get lineage 18.1 working with Magisk and Twrp.
Crdroid I could use for a while, but when I tried to update it, my phone would only boot to Twrp.
Click to expand...
Click to collapse
Which method did you use for updating crdroid? OTA or flashing from TWRP?
ledvedder said:
Which method did you use for updating crdroid? OTA or flashing from TWRP?
Click to expand...
Click to collapse
Ota.
When I rebooted I was dropped into lineages' recovery mode! Wtf
When you first went from OOS to custom rom, where you able to restore your apps and settings from TWRP, or did you have to start fresh?
I started fresh.
I think you can backup app settings with titanium backup, and just restore it on the new rom.
Pierre413 said:
I started fresh.
I think you can backup app settings with titanium backup, and just restore it on the new rom.
Click to expand...
Click to collapse
Yeah, that's my biggest concern. I don't want to have to reinstall and reconfigure all of my apps.
ledvedder said:
Yeah, that's my biggest concern. I don't want to have to reinstall and reconfigure all of my apps.
Click to expand...
Click to collapse
Try it and see how it goes. Make a Twrp backup and a titanium backup. Copy those files to a pc or something.
If you install a rom and you see the titanium backup isn't restoring all your apps, go back to OOS and restore using Twrp. You'll have your phone in the same state as when you started, only now with the benefit of experience.
In the past I've always backed up my complete ROM incl. appdata with twrp. I didn't have to competely setup my device if flashing went wrong and reverted to stock. I had some bad luck flashing roms because the A/B slots are new to me. I now have my bootloader unlocked and everything setup on stock OOS, and made a twrp backup of super, recovery and data.
Before flashing another ROM I just want to make sure I can revert easily to the previous OS without doing a complete setup of app settings and stuff
My question is
Can I wipe/factory reset and then just restore with twrp?
Do I restore when in the active slot where current os is?
Are there any issues with password/encryption when restoring?
Expected scenario;
I'm on stock OOS, wiped and want to restore appdata, settings, homescreen, etc...
I failed to install custom ROM and want to revert to stock OOS without having to redo the entire setup
I did search google and this forum for an answer or guide but couldn't find one (please correct me if I missed a thread)
yusisushi said:
In the past I've always backed up my complete ROM incl. appdata with twrp. I didn't have to competely setup my device if flashing went wrong and reverted to stock. I had some bad luck flashing roms because the A/B slots are new to me. I now have my bootloader unlocked and everything setup on stock OOS, and made a twrp backup of super, recovery and data.
Before flashing another ROM I just want to make sure I can revert easily to the previous OS without doing a complete setup of app settings and stuff
My question is
Can I wipe/factory reset and then just restore with twrp?
Do I restore when in the active slot where current os is?
Are there any issues with password/encryption when restoring?
Expected scenario;
I'm on stock OOS, wiped and want to restore appdata, settings, homescreen, etc...
I failed to install custom ROM and want to revert to stock OOS without having to redo the entire setup
I did search google and this forum for an answer or guide but couldn't find one (please correct me if I missed a thread)
Click to expand...
Click to collapse
Did you read the first 3 posts of https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2022-03-09.4302449/ ?
BillGoss said:
Did you read the first 3 posts of https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2022-03-09.4302449/ ?
Click to expand...
Click to collapse
HI, yes I did
I am still confused because it says before a restore I have to disable screenlock, if my phone is softbricked or has no OS does that count as not having fingerprint/lockscreen enabled?
yusisushi said:
HI, yes I did
I am still confused because it says before a restore I have to disable screenlock, if my phone is softbricked or has no OS does that count as not having fingerprint/lockscreen enabled?
Click to expand...
Click to collapse
When you start TWRP, does it prompt you for a password/pin/pattern?
If Yes, then you have a lock screen password set. And if you can't get into the system to disable it, you'll have to format data (completely wipes all data).
If No, then you're good to go.
BillGoss said:
When you start TWRP, does it prompt you for a password/pin/pattern?
If Yes, then you have a lock screen password set. And if you can't get into the system to disable it, you'll have to format data (completely wipes all data).
If No, then you're good to go.
Click to expand...
Click to collapse
Hi, first of all; thank you for taking time to help me!
I managed to completely wipe the phone including data, and afterwards I restored it by copying the backup (which was now on my computer) and restoring it. SUCCESS! All appdata seems to be there, homescreen, and after second reboot my fingerprint still worked as before.
I just have one more question if you don't mind;
Below partitions I backed up;
Data
Boot
DTBO
Super
However, I'm not able to copy over the "super" partition from my computer to my phone, is this normal? it's almost 8GB and I was convinced I wasn't going to get to the OS without restoring it but apparently I didn't need it (?)
I suppose with the Fastboot Enhance Tool I'll be able to also restore this?
You really only need to backup the "system" partitions (boot, dtbo, super) if you're changing to custom ROMs. If you're always on OOS then you can forget about backing them up.
You should be able to copy the full backup, including super files from your PC to your phone using ADB. I've done that lots of times.
I've never used the tool you referred to. But I do know that you can't use fastboot to flash the super partition - it's too big.
However, if you break it up into chunks (I did it in 512MB chunks) using SparseConverter (https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/) then you can successfully flash it.
Just to confirm, if a ROM bootloops and I don't have access to a computer, there's no way to restore the TWRP backup? Seems like this defeats the point of even making on-device backups (AFAIK encryption can't be disabled for many roms)
tech.central said:
Just to confirm, if a ROM bootloops and I don't have access to a computer, there's no way to restore the TWRP backup? Seems like this defeats the point of even making on-device backups (AFAIK encryption can't be disabled for many roms)
Click to expand...
Click to collapse
If you can enter TWRP (even if your rom bootloops) there is a great chance you can restore backup in TWRP.