What and how to backup before Ubuntu Touch install? - ONE Q&A, Help & Troubleshooting

Hi everyone,
I'm a noob to the OPO and also a bit of a noob to backing up and restoring individual partitions, although I have some experience with flashing the Nexus 5 and Z3C with B2GOS and /e/.
I'd like to put Ubuntu Touch on my OPO. I'd like to make sure I can return the phone to stock afterwards, if needed (e.g., I want to sell it as stock). I was thinking of taking partition images with TWRP first, will this be sufficient? I see there's a tool for backing up the EFS as well, so I suppose I should do that.
Or maybe I need to do nothing! Will it be sufficient just to reflash stock firmware when I want to return to stock? If a combination of both flashing stock firmware and TWRP images, EFS backup, what order does it need to be done in?
Thanks for your help in advance.
Cheers

madb1lly said:
Hi everyone,
I'm a noob to the OPO and also a bit of a noob to backing up and restoring individual partitions, although I have some experience with flashing the Nexus 5 and Z3C with B2GOS and /e/.
I'd like to put Ubuntu Touch on my OPO. I'd like to make sure I can return the phone to stock afterwards, if needed (e.g., I want to sell it as stock). I was thinking of taking partition images with TWRP first, will this be sufficient? I see there's a tool for backing up the EFS as well, so I suppose I should do that.
Or maybe I need to do nothing! Will it be sufficient just to reflash stock firmware when I want to return to stock? If a combination of both flashing stock firmware and TWRP images, EFS backup, what order does it need to be done in?
Thanks for your help in advance.
Cheers
Click to expand...
Click to collapse
Hi,
I don't have much time at the moment. I tested Ubuntu Touch just a few weeks ago. Some (not all) bacon users have broken Wlan. I'm one of them. Because of that I went back to Android. So it's possible.
It was a bit tricky. Of course I recommend a full nandroid backup. Copy it to a save place (for example your PC). Don't change any partitions on your phone during installation.
To go back (if I'm remembering wright):
- flash latest recovery via fastboot
- reboot in recovery (for me it was still the Ubuntu recovery)
- anywhere there was an option to boot Android
- take this option and you will reboot in the Android recovery
- there you can restore your previous backup
Hope I could help. If you try Ubuntu Touch, please report, of Wlan works for you.
Good luck. And add said: I don't really remember the whole procedure, so at your own risk.

Hi!
Gaukler_Faun said:
Hi,
I don't have much time at the moment. I tested Ubuntu Touch just a few weeks ago. Some (not all) bacon users have broken Wlan. I'm one of them. Because of that I went back to Android. So it's possible.
It was a bit tricky. Of course I recommend a full nandroid backup. Copy it to a save place (for example your PC). Don't change any partitions on your phone during installation.
To go back (if I'm remembering wright):
- flash latest recovery via fastboot
- reboot in recovery (for me it was still the Ubuntu recovery)
- anywhere there was an option to boot Android
- take this option and you will reboot in the Android recovery
- there you can restore your previous backup
Hope I could help. If you try Ubuntu Touch, please report, of Wlan works for you.
Good luck. And add said: I don't really remember the whole procedure, so at your own risk.
Click to expand...
Click to collapse
Thanks for the tip about WLAN, I didn't know about that. If I have any issues I'll post here and in the UBPorts forum.
Okay, a full Nandroid backup I can do. But don't I have to flash TWRP to the recovery partition to do that? If so, do I need to backup the recovery partition somehow first?
Thanks

madb1lly said:
Hi!
Thanks for the tip about WLAN, I didn't know about that. If I have any issues I'll post here and in the UBPorts forum.
Okay, a full Nandroid backup I can do. But don't I have to flash TWRP to the recovery partition to do that? If so, do I need to backup the recovery partition somehow first?
Thanks
Click to expand...
Click to collapse
No, I don't think you need. It would be good to have the original recovery file... But I never backed up my original recoveries. One of the first things I make with a new phone is flashing twrp. So I would just download the latest image for Bacon and flash it via fastboot.
I recommend to back up your personal data (pictures, documents, ...) ton tour PC. Who knows.

Gaukler_Faun said:
No, I don't think you need. It would be good to have the original recovery file... But I never backed up my original recoveries. One of the first things I make with a new phone is flashing twrp. So I would just download the latest image for Bacon and flash it via fastboot.
I recommend to back up your personal data (pictures, documents, ...) ton tour PC. Who knows.
Click to expand...
Click to collapse
Thanks, that's helpful. I don't actually know how to backup the recovery partition other than using root access and presumably some ADB command, so if it's not needed then that's good news. I will of course backup my data first, but a reminder is always a good thing!
Cheers

Related

Corrupt internal SD Card

Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.

What is a custom recovery?

Hi
I know it's in the words. So that I can recover my phone to where it was, if something fails while flashing.
But if I don't got "much" on the phone, does it matter then? Can't I just recover it back to factory?
All Roms to say how important it is and you need to do it and so on.
Am I missing something?
Thanks in advance
Faspaiso said:
Hi
I know it's in the words. So that I can recover my phone to where it was, if something fails while flashing.
But if I don't got "much" on the phone, does it matter then? Can't I just recover it back to factory?
All Roms to say how important it is and you need to do it and so on.
Am I missing something?
Thanks in advance
Click to expand...
Click to collapse
Yes custom recovery is probably the most important thing to install onto the phone as it is what ALLOWS you to flash a custom ROM to your device, also the recovery doesn't just backup your data it backups the entire device with a nandroid backup, that means if everything thing goes wrong but you can still get to custom recovery you can restore the device to a usable.
So you NEED a custom recovery to install a custom ROM
TechMinerUK said:
Yes custom recovery is probably the most important thing to install onto the phone as it is what ALLOWS you to flash a custom ROM to your device, also the recovery doesn't just backup your data it backups the entire device with a nandroid backup, that means if everything thing goes wrong but you can still get to custom recovery you can restore the device to a usable.
So you NEED a custom recovery to install a custom ROM
Click to expand...
Click to collapse
I downloaded Nandroid and did a recovery. Is that enough or do I need to do it from the computer?
Thanks
Faspaiso said:
I downloaded Nandroid and did a recovery. Is that enough or do I need to do it from the computer?
Thanks
Click to expand...
Click to collapse
Copy it to the PC just incase something goes wrong, other than that it's fine

Flashing 6039Y to MM advice

Hi All,
I have an o2 UK 6039Y on Lollipop and want to upgrade to MM. OTA won't work with this version. So far I managed to root, install TWRP and recover fastboot commands (they were missing). I have not seen any official MM roms on the forum, there are some like:
https://forum.xda-developers.com/idol-3/development/rom-android-6-0-1-marshmallow-t3397546
https://forum.xda-developers.com/idol-3/general/rom-6-0-1-version-010-01-kernel-3-10-49-t3518041
Can someone explain to me please if I'm going to lose root, TWRP and fastboot by using the above? I assume you do with the first link and then it is hard to get these back, but I would not with the second link? I am after as stock experience as possible, using the phone for work and I need stuff to just work. Also if anything goes wrong or I can't use any apps I will need, will I be able to restore the backups of Lollipop I have taken with TWRP to roll back to Lollipop?
Many thanks in advance, if this has been covered somewhere please send me links, I've been reading the forum for about 24 hours and getting dizzy now
Ps Does anyone know how to get rid of the ugly o2 splash screen on boot?
Hi!
If you use the second link ( https://forum.xda-developers.com/idol-3/general/rom-6-0-1-version-010-01-kernel-3-10-49-t3518041 ):
*need twrp 3.0.0-0 or above to flash it
* fastboot - ok
* Loose root but can be rooted thrue TWRP
*It have TWRP
.
Thanks for confirming, I'll give it a go later on today. Btw if I need to restore the old system, do I need to restore the system image partition or only system and data? not sure which partitions are being overwritten when flashing a different os version...
nyx007 said:
Thanks for confirming, I'll give it a go later on today. Btw if I need to restore the old system, do I need to restore the system image partition or only system and data? not sure which partitions are being overwritten when flashing a different os version...
Click to expand...
Click to collapse
Backup those two in Recovery. If you want your data back, Backup /data. If not just backup /system. You might have to factory reset the phone though. Again, might.
ended up using Person78 script to do the full backup. Flashed his Rom, all working well.
Thanks folks

install twrp without losing data

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.

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.

Categories

Resources