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.
Related
Hi. I've been using a ROM for the last little while (SlimICS), and I like it, more or less. There's a feature in another ROM (ParanoidAndroid, per-app density), that I'd really like to try out, but this ROM also has a lot of features I don't want (tablet mode) and doubt I would like. I use TWRP as my recovery...if I use TWRP to make a backup of System, Data, Boot, Recovery, .android_secure, and EFS, will I be able to flash this other ROM, then restore the backup to go back to my old ROM after I play with the new one a bit? Will the backup of these items bring me back to exactly how it was before, if I do a Wipe Cache/Dalvik Cache/Factory Reset?
Sorry if these questions are answered elsewhere, I'm just trying to make sure that my limited understanding of all this isn't incorrect, in my specific situation.
If you make a backup through recovery, when you restore, it'll be exactly where you left off, settings and all, when you shut the phone down.
When backing up in Recovery, you are backing up the OS and apps. This is called a nandroid. This does not backup anything on the sdcard.
Yesterday, I flashed a different kernel version on my NS. Before flashing, I did a nandroid backup using Reovery. Unfortunately, the kernel failed to load properly and I was stuck in a boot loop. I restored my backup I have done previously, and my phone was back where it was, few minutes before. It is very easy to do and backups/restores and verified using MD5 checksum.
Keep in mind that some apps put stuff on the sdcard. So if you flash your phone to a new ROM, upgrade apps and then go back to another ROM, it is possible that some apps won't work anymore. I've never seen this happen but this is a possibility.
Throughout my phone's lifetime, I've made a lot of backups, most of which have ended up saved on my hard drive. I recently wanted to go back to stock from a custom rom, so I copied one of the emui backups over and restored to it. Everything seemed to go smoothly, no error messages, but attempting to boot only got stuck on the blue honor boot animation. Tried several other backups, some rooted and heavily customized, some fresh unmodded installs, but all of them did the same thing. Meanwhile, all my custom rom backups work just fine. What gives?
I tried it too and it doesn't work. I think its because to install a custom ROM we format the data using twrp which also removes the encryption of some sorts, when we restore the backup that encryption is lost so it stays stuck at the blue Honor logo. That's my two sense on this. I don't know the real details.
asaditya379 said:
I tried it too and it doesn't work. I think its because to install a custom ROM we format the data using twrp which also removes the encryption of some sorts, when we restore the backup that encryption is lost so it stays stuck at the blue Honor logo. That's my two sense on this. I don't know the real details.
Click to expand...
Click to collapse
That does make more sense than anything I've thought of so far. So to restore from one of these backups, would I just have to reinstall emui from scratch first to get that encryption back? Is there another way to restore them without first having emui? Or are they just useless now?
Gannondalf said:
That does make more sense than anything I've thought of so far. So to restore from one of these backups, would I just have to reinstall emui from scratch first to get that encryption back? Is there another way to restore them without first having emui? Or are they just useless now?
Click to expand...
Click to collapse
I haven't been able to find a solution to this. What I do is use firmware finder to download the firmware+region zip and then install them together in any order via twrp. By this process you lose the data and twrp too as it is replaces by stock recovery. Before booting you must try to get into the stock recover and hit factory reset. You'll get EMUI back but no matter what you do you won't get your data back. Twrp backup is helpless I think because I've tried all sorts of things to get my data back.
asaditya379 said:
I haven't been able to find a solution to this. What I do is use firmware finder to download the firmware+region zip and then install them together in any order via twrp. By this process you lose the data and twrp too as it is replaces by stock recovery. Before booting you must try to get into the stock recover and hit factory reset. You'll get EMUI back but no matter what you do you won't get your data back. Twrp backup is helpless I think because I've tried all sorts of things to get my data back.
Click to expand...
Click to collapse
I've tried flashing emui firmware through twrp before and the region zip always works, but I've never gotten it to load the update.zip (using adb sideload for everything). But I'll try a few different things and see if I can get that to work. Getting back to emui is my primary focus since most of my data is backed up somewhere else, but if I find a way to successfully restore data from backups I'll let you know.
Gannondalf said:
I've tried flashing emui firmware through twrp before and the region zip always works, but I've never gotten it to load the update.zip (using adb sideload for everything). But I'll try a few different things and see if I can get that to work. Getting back to emui is my primary focus since most of my data is backed up somewhere else, but if I find a way to successfully restore data from backups I'll let you know.
Click to expand...
Click to collapse
What I'm telling is probably the easiest way let me break it down for you again.
1. Download firmware+region zip file from firmware finder.
2. Go to twrp, clear everything (format data).
3. Install the two downloaded zip I usually flash firmware and then the region zip.
4. After installation is over don't reboot go back to twrp home screen and reboot to recovery, which will be stock.
5. Format data using stock recover and then clear cache.
6. Restart and everything should work.
And if you find a way to get the twrp backups do post here.
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.
First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).
First of all, I'm impressed that you have done as much as you have (or even wanted to for that matter) at 82. Most older people I know (I'm 42 btw)barely know how to use there phones in the os, much less know what recovery is, lol.
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?
BarrySamuels said:
First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).
Click to expand...
Click to collapse
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.
b.huss2 said:
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?
Click to expand...
Click to collapse
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
MrSteelX said:
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.
Click to expand...
Click to collapse
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
BarrySamuels said:
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.
b.huss2 said:
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.
Click to expand...
Click to collapse
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11
MrSteelX said:
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11
Click to expand...
Click to collapse
I think that's kind of understood at this point. However, I see no problem with restoring a Oreo backup once he's back on Oreo.
BarrySamuels said:
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
Almost. You are missing one thing.
1. Flash the roll back firmware
2. Install TWRP using fastboot
3. Flash, using TWRP, OxygenOS 5.1.11
4. Before rebooting, FLASH TWRP IN TWRP (This is important, as flashing 5.1.11 will overwrite recovery)
5. Use your TWRP backup
6. Do what you need for files you want on internal storage.
Don't forget to flash TWRP after you update to 5.1.11.
Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.
BarrySamuels said:
Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.
Click to expand...
Click to collapse
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Use the fastboot ROM recovery. It works (I've used it twice) no data wipe.
chazey2 said:
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.
BarrySamuels said:
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.
Click to expand...
Click to collapse
Your welcome good luck
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.