Database Info

System Update advise

My XT1540/rooted/stock 6.0 ROM/ stock recovery now has an update available. I assume I can not accept this system update, even if I un-root my device. I do have a pre-rooted TWRP back up. I can reload that image, but my concern is the best way to get all my apps and data reloaded. I do have TB backups, but I thought that may not be a good option after system update. I am looking for advise how to proceed getting the latest system update and preserving all my current apps and data.

No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.

acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.

MrTooPhone said:
Thanks. I have read conflicting information on the use of Titanium Backup, and that was my main reason for my post. My understanding of your reply is that TB would not be a recommended choice to restore apps&data (using either update.zip or batch mode) and that I have an 80% chance of restoring user apps and data by flashing the /data partition from my pre-OTA TWRP backup. And yes, I will make a pre-rooted backup prior to rooting or restoring apps.
I never heard of Magisk and will read more. In the mean time I will stick with SuperSU unless there is strong advise to go with Magisk.
Click to expand...
Click to collapse
I dislike TiBU... It is best to reinstall from scratch each time if possible, if not, this is a simple security update to TWRP should suffice.
Magisk is good, and it appears to be the root method most ROMs are going to because with Magisk Hide and a few tweaks that are built in, the device can still pass SafetyNet API checks, and there is no special process for systemless installing (it is the only way it can be done with Magisk). But if you are on SuperSU now and want to restore the data partition, do NOT switch that way... Get clean ROM and flash Magisk then install Magisk Manager. It has it's own community here: https://forum.xda-developers.com/apps/magisk
I am not saying Magisk is superior, but it is quite versatile and most ROMs seem to be switching to it so devices can pass SafetyNet checks.

I was also thinking this would be simple. Pleasant surprise after almost a year and a half to get a security update. So I uninstalled SuperSU (Tried Full Unroot option & it failed, so then just uninstalled the app.....Looks like I may still be rooted), re-installed the stock recovery, and with absolutely no other modifications to this phone, performed the update. So it failed. I thought I was able to do this on my Nexus 4, but that was a while back, and I always did it with a file, not OTA; maybe that was just OS update, who knows. I was just looking for some security peace of mind while waiting for Nougat to become a bit more stable. If I am going to have to go through hoops to do this, then I guess I will just wait; not going to go through this twice. Besides, will it be another year for the next security update; heck, they are already 1 or 2 months behind already.

The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.

Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Oh well. On a side note, always grateful for making Nandroid backups before I start playing around with anything though. Things were acting up after haphazardly trying various SuperSU options, so I had to do a restore.
These constant OTA update messages every few minutes that I have to keep canceling are brutal! I might have to install an app to kill them.

Rohi09 said:
The answer is what others said, plus you can try flashing OTA updates with flashfire, and don't choose to wipe data.
Click to expand...
Click to collapse
Are you saying OTA updates can be flashed successfully without unrooting.

MrTooPhone said:
Are you saying OTA updates can be flashed successfully without unrooting.
Click to expand...
Click to collapse
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?

Rohi09 said:
that's the idea, I have never tried it on moto g 2015 though. As far as I know every root solution had its own Uninstaller. which root interface do you use? magisk or supersu?
Click to expand...
Click to collapse
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.

MrTooPhone said:
I have SuperSU. It would be great to flash an OTA over my current system, but I have heard many reports including @pjc123 above where it did not work.
All my searches resulted in suggestions in going back to stock, accept OTA, then use TB or some other similar program to restore saved apps & data. Tomorrow I will try @acejavelin 's above suggested method of flashing the /data partition. If that does not work, I will try TB. I will report my progress.
Click to expand...
Click to collapse
you can flash unsu zip or magisk Uninstaller and try to install ota via flashfire, won't hurt trying, might save you some time.

acejavelin said:
No offense, but did you Google it or search here? There are several tutorials in this device section and other similar Moto devices of the same generation that tell you different ways to do it...
Easy way... boot (not flash) TWPR, backup in TWRP, restore pre-root backup, accept OTA and allow it flash and fully boot, boot TWRP, flash your root of choice that you were using prior (Magisk or SuperSU), reboot and verify operation, then restore data partition backup you did prior to OTA, clear caches, and reboot.
This works 80% of the time... if your data partition is important then make an alternative backup.
Click to expand...
Click to collapse
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?

MrTooPhone said:
Another dumb question, I am in the process of installing OTA. When I loaded the pre-root rom, I did not see any option to clear clear caches. I did see a wipe data and cache option which I understand to be a factory reset. I know I have seen it before but can't find it, so where do I clear cache after restoring data partition?
Click to expand...
Click to collapse
Another simple Google question...
Open TWRP, go to Wipes - Advanced, and select Cache and Dalvik cache (a misnomer today, it should be called ART cache) and swipe to wipe, then reboot.

Thanks to @acejavelin recommendations, I have successfully applied the latest system update to my XT1540. My steps were as follows:
Booted to TWRP (3.0.2-r5.img)
restored original pre-rooted ROM
rebooted, accepted system updates
backed up new pre-rooted ROM
installed SuperSU 2.62-3, rebooted
updated SuperSU to 2.79 via Playstore
restored /data partition from last saved rooted ROM
wiped Dalvik/ART Cache
Reboot system
took a while, a couple of minutes on “Hand stitched by Peter Crawly”, several minutes optimizing apps. The phone booted succesfully then I got an error message the update failed (which I hit OK) But looking at about phone, latest security patch is listed. Phone looks configured (apps, data, configuration) exactly as it was prior to the update.
Rebooted phone, all still seems fine.

Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file

bradmoss said:
Hello, how do I restore original pre-rooted ROM? When I made the backup I got a folder with 6 files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win
system.ext4.win.md5
system.info
None of them seems to be the .img file
Click to expand...
Click to collapse
Your are not going to see an img file. Once booted into TWRP, select Restore, navigate and select your original ROM. Those files you have listed are within the restoration directory that you select with TWRP. Just select the directory with TWRP.

Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!

no idea? Am I the sad owner of a bricked phone?

bradmoss said:
no idea? Am I the sad owner of a bricked phone?
Click to expand...
Click to collapse
You could try a factory reset if you're not worried about losing your data. A factory reset solves most of the problems, though I'm a little doubtful because a factory reset won't uninstall the new update (given that it installed in the first place).

bradmoss said:
Bad news, I could restore pre-TRWP image using that folder and aplied the update.
But now I am in a loop, it tries to install (again) the update and then boots to TWRP
Is there any way out of this loop?
Thanks!
Click to expand...
Click to collapse
If it boots to TWRP, sounds like you didn't have a clean pre-root ROM as you did not have stock recovery. Did you try deleting Dalvik and ART cache?

TWRP problem / update

My OnePlus 7 Pro is rooted at 9.5.8 trying to update to 9.5.9
When i try to install OTA it removes TWRP as it would but i can't boot into the system again without booting into TWRP and switching back to slot A. And when i boot to the system settings say that update failed.
I've tried different update methods like
Install update (dont reboot) - Magisk install inactive slot
Download update zip with oxygen updater app - boot into recovery twrp - flash update zip
I rooted my phone a few days ago and for some reason it won't update and i'm stuck on 9.5.8
Slot b is also not readable. SDCARD shows 0mb

What I do is:
Download and install the update
Don't reboot
Then back out and go to magisk downloads
Search for twrp retention and install
Don't reboot
Then back out to magisk main screen and select the first install option
Then select install and then the 4th option ota install slot
Now reboot

Yayodroid said:
What I do is:
Download and install the update
Don't reboot
Then back out and go to magisk downloads
Search for twrp retention and install
Don't reboot
Then back out to magisk main screen and select the first install option
Then select install and then the 4th option ota install slot
Now reboot
Click to expand...
Click to collapse
Tried this too.
When I install oxygen update zip through TWRP and I reboot it goes over to slot b where I can't boot to the system and when I go back to slot a and boot to system update failed

First i disable all magisk modules then I download the full 2gb update, go into twrp, flash the update, flash twrp.zip then flash magisk.zip. Reboot and then re-enable the modules.

if you have Magisk module OOSNativeCallRecorder, you need to remove that module. If still issues then remove all modules.
Guide how to remove magisk modules via TWRP

equlizer said:
First i disable all magisk modules then I download the full 2gb update, go into twrp, flash the update, flash twrp.zip then flash magisk.zip. Reboot and then re-enable the modules.
Click to expand...
Click to collapse
This doesnt work. After flashing it reboots to slot b and update failed

Bradl79 said:
if you have Magisk module OOSNativeCallRecorder, you need to remove that module. If still issues then remove all modules.
Guide how to remove magisk modules via TWRP
Click to expand...
Click to collapse
Okay, this is weird
I chose to remove magisk, twrp and go back to stock with locked oem. Installed the new update perfectly fine. Then I regretted it. So I rooted my device again and set it up only to look under device info where it says that I now have 9.5.8. So basically my phone downgraded itself after rerooting and unlocking bootloader.
I'm now stuck in 9.5.8

PikachuLover said:
Okay, this is weird
I chose to remove magisk, twrp and go back to stock with locked oem. Installed the new update perfectly fine. Then I regretted it. So I rooted my device again and set it up only to look under device info where it says that I now have 9.5.8. So basically my phone downgraded itself after rerooting and unlocking bootloader.
I'm now stuck in 9.5.8
Click to expand...
Click to collapse
Probably switched back to old slot.

Bradl79 said:
Probably switched back to old slot.
Click to expand...
Click to collapse
So I should just try and flash the update, twrp and magisk in this order on the slot I am using now?

Having same problem. No work around?

The best way to update? Personally, I recommend taking full manual control of the update process. Use TWRP to update your ROM (that includes stock OOS) when you want to, and when you need to fix stuff.
- Flash ROM
If you are on slot A and flash a ROM, it goes to slot B.
- Flash TWRP installer zip
Keeps TWRP on both slots, patches boot.img
- Reboot to TWRP, not system
- Flash ROM again
This installs the ROM to the other slot, so now both slots are updated
- Flash TWRP installer zip again
Keeps TWRP on both slots, patches boot.img
- Flash Magisk
Patches the TWRP-patched ROM, allowing it to boot.
- Wipe dalvik
You can wipe data and dalvik instead for a clean flash
- Now reboot to system
Consider flashing BOTH slots (A and B) whenever you update OOS, for two reasons.
First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base.
The second reason is more compelling: the way the data partition changes encryption every update has nearly obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!

reaper000 said:
.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!
Click to expand...
Click to collapse
I was actually going to do this permanently for better performance, I did test it out for a while and definitely noticed things faster, boot is quicker, battery lasted longer also.
I just hate all the work required to keep decrypt between updates.
I wish Google allowed us to choose whether we want encryption or not.

This maybe a silly question and the form trolls may come out. However ??, decrypting, will we have to do it to both slots? A and B? Or will twrp take care of decrypting both slots. Coming from a one plus 5 we didn't have to deal with this whole slot a and b. Boy what a headache.

virtyx said:
I was actually going to do this permanently for better performance, I did test it out for a while and definitely noticed things faster, boot is quicker, battery lasted longer also.
I just hate all the work required to keep decrypt between updates.
I wish Google allowed us to choose whether we want encryption or not.
Click to expand...
Click to collapse
I'm thing about decrypting, if you don't mind, can you let me know what you mean by all that work?
On the 5t, after decrypting, I just had to make sure to flash no verity script in twrp and that was all.

harpin14789 said:
I'm thing about decrypting, if you don't mind, can you let me know what you mean by all that work?
On the 5t, after decrypting, I just had to make sure to flash no verity script in twrp and that was all.
Click to expand...
Click to collapse
He likely means backing up and starting fresh. I hated that process on my oneplus 5 but after works it was great. This whole slot A and B, is a pesky little bugga.

Yayodroid said:
What I do is:
Download and install the update
Don't reboot
Then back out and go to magisk downloads
Search for twrp retention and install
Don't reboot
Then back out to magisk main screen and select the first install option
Then select install and then the 4th option ota install slot
Now reboot
Click to expand...
Click to collapse
This is what I did as well. Worked beautifully.

harpin14789 said:
I'm thing about decrypting, if you don't mind, can you let me know what you mean by all that work?
On the 5t, after decrypting, I just had to make sure to flash no verity script in twrp and that was all.
Click to expand...
Click to collapse
I manually decrypted
I don't know if the zip works on the 7 Pro
I'd update via twrp
Flash twrp
Flash magisk (after echo KEEPVERITY=FALSE > /data/.magisk)
ADB pull both fstab files in vendor/etc to my pc
And change fileencryption to encryptable and move back
I always kept the fstab files on my internal storage so I didn't need a PC but I always did just incase.

What happens if you have and F2FS formatted /data and
A custom kernel?
Thanks in advance
reaper000 said:
The best way to update? Personally, I recommend taking full manual control of the update process. Use TWRP to update your ROM (that includes stock OOS) when you want to, and when you need to fix stuff.
- Flash ROM
If you are on slot A and flash a ROM, it goes to slot B.
- Flash TWRP installer zip
Keeps TWRP on both slots, patches boot.img
- Reboot to TWRP, not system
- Flash ROM again
This installs the ROM to the other slot, so now both slots are updated
- Flash TWRP installer zip again
Keeps TWRP on both slots, patches boot.img
- Flash Magisk
Patches the TWRP-patched ROM, allowing it to boot.
- Wipe dalvik
You can wipe data and dalvik instead for a clean flash
- Now reboot to system
Consider flashing BOTH slots (A and B) whenever you update OOS, for two reasons.
First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base.
The second reason is more compelling: the way the data partition changes encryption every update has nearly obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!
Click to expand...
Click to collapse

A/B slot questions

I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..

dumbl3 said:
I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..
Click to expand...
Click to collapse
Yoo.. So Many Questions. Will try to explain in easiest way..
1. Yes. It Does Flash OOS in Both Slot via Qualcomm Download Mode which is mainly for Manufactures to restore Device..
2. Let me clear that Most people's who face issue in booting custom ROM have their data encrypted by previous or stock ROM.
Here is Link Thread to know how to decrypt your device..
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
My own Instructions to Flash Custom ROM (Strictly for Decrypted Device):-
Boot Into Recovery
Wipe Cache, Data & System
Flash Latest Stable/Beta OOS10 & Recovery
Reboot Into Recovery(Ignore No OS Installed Warning)
Flash Latest Stable/Beta OOS10 & Recovery again
Reboot Into Recovery
Now flash Custom ROM + Recovery(If Not Included)
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
For Installing Update on Same Custom ROM :-
Download the Update
Reboot Into Recovery
Flash Update ZIP & Recovery
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
3. Fastboot Don't always work if You try to Upgrade/Downgrade Android Version as it won't flash Critical Partitions.. Meanwhile MSMDownload tool Use Download mode which is more powerful.
4. Nope. Both are Different AS both use different mode to flash ROM.
5. Clean install required while flashing new custom ROM because Not All ROM uses Same Base. Some uses Stable OOS or some uses Beta OOS... Now, your answer is in these two build Types...
In my Opinion, Custom ROM have nothing to do with your System partition but it most like to related to Vendor Partition... Both Stable & Beta OOS Have little difference in Vendor partition data..
When any dev Build Any ROM, he uses any one of those Build as base for which he tweak/fix bugs.. That's why always Use Dev specified OOS build for avoid Bootloop/bugs..
6. I prefer last option as it's more reliable..
7. It's like when you clean install any ROM.. When you install Any ZIP, It get installed in an Inactive Slot which make those ZIP data Allowed to use in Active slot..
But when you update ROM for 1st time, You install Gapps as well.. So i don't think you need to Install Gapps on 2nd Update as it already installed in both slots.
1st time when Clean installed & 2nd time when Updated 1st time...
8. It's Because how A/B Partition works... Any zip you flash get installed in inactive slot & this applies to both Stock OOS & Custom ROM...
That's why we have to flash OOS twice before flashing any custom ROM.. Which confirms you will have same Vendor partition regardless to your current slot so when you flash custom ROM it will get booted anyways even after an update..
Hope that's helpful.. Any question or help, you can DM or reply here..

Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?

dumbl3 said:
Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?
Click to expand...
Click to collapse
Well, In my Opinion Every Device is Vulnerable to Hackers.. Doesn't matter if it's bootloader is Locked or Unlocked...
Your device is more Vulnerable at the time you unlocked bootloader because after that you can execute advanced commands with fastboot.....
If your device have pin/pattern, Thief gone reset your device anyway to reset pass.. Eventually your data get wiped as well....
Well, you can encrypt your data but you might face issue while migrating to other ROM if you face any bug + decrypting your encrypted device again is time taking process if you have alot of data..

I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?

dumbl3 said:
I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?
Click to expand...
Click to collapse
you can.. But do it only if you gone use it for long term....
Not fine to waste your whole day transfer your date from mobile to PC then PC to mobile..

Can I backup & restore including appdata with TWRP?

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.

Upgrade to LineageOS 19.1

Hi All,
since a couple of days the new LineageOS 19.1 is available for the Moto g7 Power.
A manual upgrade is needed to get it onto the phone.
Since I did the installation but not yet a manual upgrade of LOS to a new major version I have some questions about it:
When reading the upgrade guide there is no info about .... :
will I lose apps or any data when simply sideloading the new version?
will I have to newly install/sideload Magsik?
are there any other important things to consider when doing such an upgrade?
Thanks a lot in advance.
Cheers

1. From my experience of dirty flashing roms via twrp, I can tell you that if you flash a newer lineage zip after ONLY wiping the cache and dalvik partitions, you'll keep your data and settings etc.
2. You most likely won't have to flash the newer version of gapps (as it gets updated upon restart).
Magisk and (maybe) magisk mods are cleared as the boot image gets replaced when flashing a rom.
3. Make a full TWRP backup of your current rom just incase things go sideways with the new one (during installation, or if you want to revert back later).
Since "dirty flashing" via twrp is basically sorta sideloading, I'd assume that these would apply for you as well. I can confirm the magisk one, as that will get removed regardless.

PhotonIce said:
1. From my experience of dirty flashing roms via twrp, I can tell you that if you flash a newer lineage zip after ONLY wiping the cache and dalvik partitions, you'll keep your data and settings etc.
2. You most likely won't have to flash the newer version of gapps (as it gets updated upon restart).
Magisk and (maybe) magisk mods are cleared as the boot image gets replaced when flashing a rom.
3. Make a full TWRP backup of your current rom just incase things go sideways with the new one (during installation, or if you want to revert back later).
Since "dirty flashing" via twrp is basically sorta sideloading, I'd assume that these would apply for you as well. I can confirm the magisk one, as that will get removed regardless.
Click to expand...
Click to collapse
Great, all worked fine, thanks!