Related
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?
Good evening, I saw some questions similar to this one in the forum, but none had my kind of doubt.
When a new ROM comes out for both S7 and S8, I install via ODIN using the CSC HOME option, so as not to lose the data.
The problem is in the installation of TWRP whenever I install the same by ODIN, when entering the app and trying to install example no-verity ja start I get the message that the DATA folder has been corrupted and can not be mounted.
This way it only works once again doing WIPE DATA, but then I lose my data and I have to start from scratch.
Is there a way this does not happen or will it always be like this when updating a ROM?
Thank you.
costafabiof said:
Good evening, I saw some questions similar to this one in the forum, but none had my kind of doubt.
When a new ROM comes out for both S7 and S8, I install via ODIN using the CSC HOME option, so as not to lose the data.
The problem is in the installation of TWRP whenever I install the same by ODIN, when entering the app and trying to install example no-verity ja start I get the message that the DATA folder has been corrupted and can not be mounted.
This way it only works once again doing WIPE DATA, but then I lose my data and I have to start from scratch.
Is there a way this does not happen or will it always be like this when updating a ROM?
Thank you.
Click to expand...
Click to collapse
Have you tried backing up data with twrp before you wipe and copying it to your pc so you can do a full wipe then put the backup onto the phone and flash It? You can back up data folder only
godkingofcanada said:
Have you tried backing up data with twrp before you wipe and copying it to your pc so you can do a full wipe then put the backup onto the phone and flash It? You can back up data folder only
Click to expand...
Click to collapse
Good afternoon,
Thanks for the reply.
So from what I mentioned above, I do a full backup as I normally do, and I also do a separate from the DATA folder.
Then I install the ROM and TWRP, will it corrupt the DATA folder so I restore only it? Would it be this?
If so, will it work out, in relation to being a ROM different from the other?
costafabiof said:
Good afternoon,
Thanks for the reply.
So from what I mentioned above, I do a full backup as I normally do, and I also do a separate from the DATA folder.
Then I install the ROM and TWRP, will it corrupt the DATA folder so I restore only it? Would it be this?
If so, will it work out, in relation to being a ROM different from the other?
Click to expand...
Click to collapse
The main rom info needed is contained in the system folder. The data folder is application data and whatnot. Reboot into twrp and use the backup option, then copy to pc. Do a full wipe of all, pit backup of data folder and new rom on internal or sd. Go into terp and flash the rom and data folder. Do not flaah system or it will overwrite the new rom. u will restore everything even if you don't have the APK installed in your system. It will return the data, you may need to reinstall the APK. Gmail for example will return will email addresses and messages, contacts and texts will come back to what they were at backup. You should back up modem and efs and boot as well and keep them safe. What I do is I get my phone set up fully, all apps I need and any games and data and then back it up again so any issues and I restore it to a fully functional state and don't need to install tons of things
godkingofcanada said:
The main rom info needed is contained in the system folder. The data folder is application data and whatnot. Reboot into twrp and use the backup option, then copy to pc. Do a full wipe of all, pit backup of data folder and new rom on internal or sd. Go into terp and flash the rom and data folder. Do not flaah system or it will overwrite the new rom. u will restore everything even if you don't have the APK installed in your system. It will return the data, you may need to reinstall the APK. Gmail for example will return will email addresses and messages, contacts and texts will come back to what they were at backup. You should back up modem and efs and boot as well and keep them safe. What I do is I get my phone set up fully, all apps I need and any games and data and then back it up again so any issues and I restore it to a fully functional state and don't need to install tons of things
Click to expand...
Click to collapse
Good afternoon,
I'm sorry for the text I'm using Google Translate.
I believe that I did not understand correctly, because the error happens in the following way, I install a ROM, reinstall the TWRP, yes yes it corrupts the folder DATA!
If I understood mistake, I apologize.
costafabiof said:
Good afternoon,
I'm sorry for the text I'm using Google Translate.
I believe that I did not understand correctly, because the error happens in the following way, I install a ROM, reinstall the TWRP, yes yes it corrupts the folder DATA!
If I understood mistake, I apologize.
Click to expand...
Click to collapse
Is it a custom Rom or a stock rom? Also you can backup via ADB
https://forum.xda-developers.com/an...oid-sdk-adb-backup-apps-t3467560#edit68829721
godkingofcanada said:
Is it a custom Rom or a stock rom? Also you can backup via ADB
https://forum.xda-developers.com/an...oid-sdk-adb-backup-apps-t3467560#edit68829721
Click to expand...
Click to collapse
The ROM I use is provided by Samsung, with no modifications, when I install it I use the CSC option the HOME file, in order not to lose the data, and of course, I do not lose anything I only update the ROM.
The problem is that I need to reinstall TWRP after installing ROM, and when I access TWRP it has corrupted the DATA folder.
costafabiof said:
The ROM I use is provided by Samsung, with no modifications, when I install it I use the CSC option the HOME file, in order not to lose the data, and of course, I do not lose anything I only update the ROM.
The problem is that I need to reinstall TWRP after installing ROM, and when I access TWRP it has corrupted the DATA folder.
Click to expand...
Click to collapse
You can extract the samsung md5 and repack it as a zip with superrs kitchen and then flash it from twrp. Just remove the recovery.img from the extracted files before zipping it up. Then you can simply flash twrp. Then the rom and not have to worry about the fact that you are stuck in a loop of being locked out because you don't need odin for the rom and it won't overwrite your recovery. If that's too much work try using a custom Rom from xda
godkingofcanada said:
You can extract the samsung md5 and repack it as a zip with superrs kitchen and then flash it from twrp. Just remove the recovery.img from the extracted files before zipping it up. Then you can simply flash twrp. Then the rom and not have to worry about the fact that you are stuck in a loop of being locked out because you don't need odin for the rom and it won't overwrite your recovery. If that's too much work try using a custom Rom from xda
Click to expand...
Click to collapse
Thank you very much for your patience. But I'm not clear, or you do not understand.
The problem is not in the ROM, but in the TWRP installation. If I install the ROM with the option CSC HOME I do not lose anything, everything is working correctly.
When I install TWRP it corrupts the DATA folder. The problem is there!
costafabiof said:
Thank you very much for your patience. But I'm not clear, or you do not understand.
The problem is not in the ROM, but in the TWRP installation. If I install the ROM with the option CSC HOME I do not lose anything, everything is working correctly.
When I install TWRP it corrupts the DATA folder. The problem is there!
Click to expand...
Click to collapse
I was saying to use a zip rom because then you can reflash the rom without reflashing twrp. So you flash twrp, it says data error and then you flash rom from zip, which reinstall system and data but will not copy stock recovery over twrp. So you will not have to reinstall it and be stuck. Or try a different version of twrp might also help. Stock firmware overwrites recovery and the rom. You need to modify it to remove recovery from the firmware, or use a custom Rom to stop it from erasing twrp
godkingofcanada said:
I was saying to use a zip rom because then you can reflash the rom without reflashing twrp. So you flash twrp, it says data error and then you flash rom from zip, which reinstall system and data but will not copy stock recovery over twrp. So you will not have to reinstall it and be stuck. Or try a different version of twrp might also help. Stock firmware overwrites recovery and the rom. You need to modify it to remove recovery from the firmware, or use a custom Rom to stop it from erasing twrp
Click to expand...
Click to collapse
I think I understood, more or less, since I translate for Google.
But assuming I want to use normal ROM, you have to back up the DATA folder before installing the ROM and after installing the new ROM and TWRP, restore only the DATA?
Thank you again.
Yes a new rom will overwrite data, you need a backup before. You should be able to connect your phone to a linux operating system and use adb to connect and back it up, if twrp will not let you take a back up.
godkingofcanada said:
Yes a new rom will overwrite data, you need a backup before. You should be able to connect your phone to a linux operating system and use adb to connect and back it up, if twrp will not let you take a back up.
Click to expand...
Click to collapse
In my case I can back up the DATA folder by TWRP. Is there doubt, if I back up the DATA folder in one version of Android and then restore in another version, will it be compatible?
costafabiof said:
In my case I can back up the DATA folder by TWRP. Is there doubt, if I back up the DATA folder in one version of Android and then restore in another version, will it be compatible?
Click to expand...
Click to collapse
Yes it will be, marshmallow and nougat are completely compatible from the boot loader up. You can also turn your stock samsung md5 into a zip file so you do not need odin to install it. You will be able to flash it from twrp
godkingofcanada said:
Yes it will be, marshmallow and nougat are completely compatible from the boot loader up. You can also turn your stock samsung md5 into a zip file so you do not need odin to install it. You will be able to flash it from twrp
Click to expand...
Click to collapse
Again thank you very much.
I'll test it and put it here.
Note: The Thank you button is not working.
costafabiof said:
Again thank you very much.
I'll test it and put it here.
Note: The Thank you button is not working.
Click to expand...
Click to collapse
You are welcome. If you want to have a stock zip file instead of the md5 use this link.
https://forum.xda-developers.com/showthread.php?t=2387941
...
costafabiof said:
...
Click to expand...
Click to collapse
Can you not read the website?
I know what you mean. Twrp can't access the data folder because it's encrypted. But you do have to format it to gain proper access. You have to copy the files out or back them up
godkingofcanada said:
Can you not read the website?
Click to expand...
Click to collapse
I believe that because I am a new user I can not exclude publications, I already tested in CHROME and IE. In the same way I can not give THANK YOU.
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.
The problem is kinda complicated. Previously, I flashed a custom ROM on my phone (a modified version of Oxygen OS). Just now, I updated my phone using the official ROM downloaded from Oneplus's official site (no idea what I was thinking), and I was only able to boot into the stock recovery. So, I tried reinstalling the TWRP recovery. I was able to boot the phone, but upon boot, it would say something like "Settings stopped working" and it would shut down immediately. I tried flashing a couple of different ROMs using the Install option in TWRP, but I still get the same error when booting my phone. Is there anyway to solve this problem? If not, would there be any way for me to recover my files at least?
Go back to factory stock using the MSM tool. If you can get to TWRP you can backup your stuff.
CosmicInsight said:
Go back to factory stock using the MSM tool. If you can get to TWRP you can backup your stuff.
Click to expand...
Click to collapse
I am able to get to TWRP right now. However, I did noticed that the Data partition in the TWRP Backup option is only 76MB. Does this mean that my data's gone already somehow?
leniumC said:
I am able to get to TWRP right now. However, I did noticed that the Data partition in the TWRP Backup option is only 76MB. Does this mean that my data's gone already somehow?
Click to expand...
Click to collapse
Yeah, probably.
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.