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.
Related
Hi all I'm having hard time time in finding a way to restore back to stock.
I'm on OOS 5.1.8 with twrp official and Magisk
Can you please share how to format the phone completely and again install 5.1.8 or 5.1.6 oos?
Reason for this is poor battery life after last few iteration of updates. Need to see whether it fixes it.
leonalewis said:
Hi all I'm having hard time time in finding a way to restore back to stock.
I'm on OOS 5.1.8 with twrp official and Magisk
Can you please share how to format the phone completely and again install 5.1.8 or 5.1.6 oos?
Reason for this is poor battery life after last few iteration of updates. Need to see whether it fixes it.
Click to expand...
Click to collapse
Here you go,this will restore the phone back to 5.1.5:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
leonalewis said:
Hi all I'm having hard time time in finding a way to restore back to stock.
I'm on OOS 5.1.8 with twrp official and Magisk
Can you please share how to format the phone completely and again install 5.1.8 or 5.1.6 oos?
Reason for this is poor battery life after last few iteration of updates. Need to see whether it fixes it.
Click to expand...
Click to collapse
Make sure you have your full ROM zip files on your phone. Disable secure lock screen in OS. Boot TWRP, backup data only. Wipe everything (data is optional) install ROM zip file, reflash TWRP zip, reboot. You can always restore data at any time after wiping it and it will be as you have it set up to your preferences. There aren't major differences in OOS versions so erroes shouldn't occur with data on any of them. If you want root, you can boot back into recovery and install magisk.
mikex8593 said:
Make sure you have your full ROM zip files on your phone. Disable secure lock screen in OS. Boot TWRP, backup data only. Wipe everything (data is optional) install ROM zip file, reflash TWRP zip, reboot. You can always restore data at any time after wiping it and it will be as you have it set up to your preferences. There aren't major differences in OOS versions so erroes shouldn't occur with data on any of them. If you want root, you can boot back into recovery and install magisk.
Click to expand...
Click to collapse
can someone confirm this procedure is valid which mikex has confirmed? Since on this post https://forum.xda-developers.com/oneplus-6/help/help-flashing-oos-5-1-8-zip-via-twrp-t3814614 he did the same and got BootLoop
stavros67 said:
Here you go,this will restore the phone back to 5.1.5:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Click to expand...
Click to collapse
Just use this, let OTA update run and you're done. There's no easier solution.
leonalewis said:
can someone confirm this procedure is valid which mikex has confirmed? Since on this post https://forum.xda-developers.com/oneplus-6/help/help-flashing-oos-5-1-8-zip-via-twrp-t3814614 he did the same and got BootLoop
Click to expand...
Click to collapse
You shouldn't get a bootloop if you flash stock firmware via TWRP unless the file itself is messed up. Bootloop can occur if you flash magisk right away, I think. You have to reboot recovery before flashing magisk.
Is there a guide on how to restore a backup made in TWRP? I did this the other day forcing me to reflash the entire phone because it failed. So was just wondering about the proper way to restore backups on this phone?
baxtex said:
Is there a guide on how to restore a backup made in TWRP? I did this the other day forcing me to reflash the entire phone because it failed. So was just wondering about the proper way to restore backups on this phone?
Click to expand...
Click to collapse
It is a real pain but it works.
1. Store TWRP backup off the phone.
2. In TWRP wipe everything, then flash the same room as your backup on both slots. If using OOS, using the fastboot roms will do this easily.
3. Go through the initial setup in the OS.
4. Install TWRP (and Magisk if you were using it in the backup)
5. Restore the backup.
I know it is a headache, but the way this phone handles encryption makes it this way.
tabletalker7 said:
It is a real pain but it works.
1. Store TWRP backup off the phone.
2. In TWRP wipe everything, then flash the same room as your backup on both slots. If using OOS, using the fastboot roms will do this easily.
3. Go through the initial setup in the OS.
4. Install TWRP (and Magisk if you were using it in the backup)
5. Restore the backup.
I know it is a headache, but the way this phone handles encryption makes it this way.
Click to expand...
Click to collapse
But this just sounds weird. I was on OOS 9 with TWRP and magisk. I app was misbehaving so I restored a backup I made the day before. Shouldn't that have worked? It sounds like this process would end up in the same situation. :S What about restoring only certain things, like the boot.img. Would that work?
baxtex said:
But this just sounds weird. I was on OOS 9 with TWRP and magisk. I app was misbehaving so I restored a backup I made the day before. Shouldn't that have worked? It sounds like this process would end up in the same situation. :S What about restoring only certain things, like the boot.img. Would that work?
Click to expand...
Click to collapse
I don't know to be honest. I did a lot of experimenting trying to port a rom (had to flash lineageos on the phone more than a few times) and would backup system, boot, and data. Then I would flash my failed rom, it would fail, and that process I wrote out earlier worked.
It is also possible that any and all Magisk modules we're causing your problem and starting with the fresh slate that the fastboot rom gives you would be important.
Also when you flashed OOS 9, if you didn't flash it twice you didn't have it on both slots, and you just restored your backup to the slot that didn't have OOS 9. The flash-all.bat in the fastboot rom will flash it to both slots.
Hey guys! Is there a way to roll back from OOS B10 to stable without wiping my data? Thanks for the answers!
From 1+
theaxis01 said:
From 1+
Click to expand...
Click to collapse
May be any unofficial way which utilises TWRP?
Well the obvious answer is to try a dirty flash. Mileage will vary. Official answer is to do a clean flash which is a part of the warning when first installing the OB.
coda00 said:
Hey guys! Is there a way to roll back from OOS B10 to stable without wiping my data? Thanks for the answers!
Click to expand...
Click to collapse
I did a factory reset in twrp, install 9.0.3, flash twrp, reboot twrp, flash magisk, reboot, all good...no loss pictures and music. I had to let google reinstall apps and settings from last Google backup, it's all automatic so no worries as long as you have previously let Google back up your apps and settings
Thanks! I've made an adb full backup and restored it later.
Hi,
after installing and uninstalling some Magisk modules, my device (OP6, OOS, blu spark TWRP, Magisk) randomly froze and after restarting, it keeps booting forever. I can still get into TWRP, so I tried a few things to fix this like:
Uninstalling and reinstalling Magisk
Flashing OOS, TWRP and Magisk again
Flashing just OOS,
but nothing seems to help. Is there a proper way of fixing this without wiping my data partition?
If there is not, how do I save as much of my data (like system settings, app data etc.) as possible from TWRP so I can restore it later?
Thanks for your help
cvfd said:
Hi,
after installing and uninstalling some Magisk modules, my device (OP6, OOS, blu spark TWRP, Magisk) randomly froze and after restarting, it keeps booting forever. I can still get into TWRP, so I tried a few things to fix this like:
Uninstalling and reinstalling Magisk
Flashing OOS, TWRP and Magisk again
Flashing just OOS,
but nothing seems to help. Is there a proper way of fixing this without wiping my data partition?
If there is not, how do I save as much of my data (like system settings, app data etc.) as possible from TWRP so I can restore it later?
Thanks for your help
Click to expand...
Click to collapse
This is exactly what happened to me! (and I thought it was related to edXposed).
Have you tried flashing only the boot img?
cvfd said:
Hi,
after installing and uninstalling some Magisk modules, my device (OP6, OOS, blu spark TWRP, Magisk) randomly froze and after restarting, it keeps booting forever. I can still get into TWRP, so I tried a few things to fix this like:
Uninstalling and reinstalling Magisk
Flashing OOS, TWRP and Magisk again
Flashing just OOS,
but nothing seems to help. Is there a proper way of fixing this without wiping my data partition?
If there is not, how do I save as much of my data (like system settings, app data etc.) as possible from TWRP so I can restore it later?
Thanks for your help
Click to expand...
Click to collapse
Boot to twrp
Flash magisk uninstaller
Flash oos full rom
Flash twrp zip
Reboot recovery
Flash oos full ROM
Flash twrp zip
Reboot recovey
Flash magisk.
yldlj said:
Boot to twrp
Flash magisk uninstaller
Flash oos full rom
Flash twrp zip
Reboot recovery
Flash oos full ROM
Flash twrp zip
Reboot recovey
Flash magisk.
Click to expand...
Click to collapse
Hmm, I just tried that and it didn't help. Is there anything else I can do?
Edit: Tried with official TWRP as well, no luck either.
davidperl99 said:
This is exactly what happened to me! (and I thought it was related to edXposed).
Have you tried flashing only the boot img?
Click to expand...
Click to collapse
Where would I find the newest boot.img? Also, isn't flashing the OOS Full ROM supposed to replace my boot.img with the stock one?
cvfd said:
Hmm, I just tried that and it didn't help. Is there anything else I can do?
Edit: Tried with official TWRP as well, no luck either.
Where would I find the newest boot.img? Also, isn't flashing the OOS Full ROM supposed to replace my boot.img with the stock one?
Click to expand...
Click to collapse
I think you might have to wipe if you can't get your phone to boot after dirty flashing ROM. I would try flashing your boot. Img first in case it's magisk related problem. What ROM are you on?
yldlj said:
I think you might have to wipe if you can't get your phone to boot after dirty flashing ROM. I would try flashing your boot. Img first in case it's magisk related problem. What ROM are you on?
Click to expand...
Click to collapse
Regular OOS 9.0.7.
cvfd said:
Regular OOS 9.0.7.
Click to expand...
Click to collapse
Stock Boot. Img can be found here
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Also try use the latest bluespark twrp
yldlj said:
Stock Boot. Img can be found here
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Also try use the latest bluespark twrp
Click to expand...
Click to collapse
So flash the boot.img through fastboot and then repeat the steps above?
cvfd said:
So flash the boot.img through fastboot and then repeat the steps above?
Click to expand...
Click to collapse
Flash boot. Img and see if the phone boots. I have never flashed a boot. Img so not sure exactly how. If not it might be time to use the fastboot rom. If you flash the boot. Img you will lose twrp.
yldlj said:
Flash boot. Img and see if the phone boots. I have never flashed a boot. Img so not sure exactly how. If not it might be time to use the fastboot rom
Click to expand...
Click to collapse
No luck with that either, so I guess it's time to reset. What's the best way to backup and restore as much of my data as possible, like system settings and app data?
cvfd said:
No luck with that either, so I guess it's time to reset. What's the best way to backup and restore as much of my data as possible, like system settings and app data?
Click to expand...
Click to collapse
You can backup data in twrp but that might be the reason you can't boot. Google backup should of backed up most things. At this point you should be more concerned about getting your phone to boot.
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.