Database Develop

SwitchRom.sh Question Help

Ok
i posted a question in the switchrom thread, but no one help
so my question is:
If i have Cyanogens ROM currently tagged using the script whatever
I want to install a new build(Elitev0.5 DrizzyHero)
But my question is
In order to install hero with no hicups, your supposed to wipe,wipe ext2/3,reboot recovery,then wipe again, then check filesystems, then flash.
But my question is with Switchrom.sh script
Do i need to just wipe with alt+w
then flash
or do i need to do something els, like...
Wipe(alt+w)
then erase the app folder/dalvik chache
then reboot recovery, then wipe again
then check filesystems (wouldn't that corrupt the script???)
then flash
then to return back to cyan
use the same method??

jf4888 said:
Ok
i posted a question in the switchrom thread, but no one help
so my question is:
If i have Cyanogens ROM currently tagged using the script whatever
I want to install a new build(Elitev0.5 DrizzyHero)
But my question is
In order to install hero with no hicups, your supposed to wipe,wipe ext2/3,reboot recovery,then wipe again, then check filesystems, then flash.
But my question is with Switchrom.sh script
Do i need to just wipe with alt+w
then flash
or do i need to do something els, like...
Wipe(alt+w)
then erase the app folder/dalvik chache
then reboot recovery, then wipe again
then check filesystems (wouldn't that corrupt the script???)
then flash
then to return back to cyan
use the same method??
Click to expand...
Click to collapse
I had to read your question about 4 times to understand what you're asking and I'm still not too clear.
I don't even know how many questions your asking. Perhaps it just the layout of your post.
Anyway. I'll give it a try because I often use the script to bounce between CM ROMs and Hero ROMs. If your currently using a stable NON-Hero build then store your build by performing a nadroid backup and then use the console:
# mount system/sd
# sh system/sd/switchrom.sh -s ROMNAME
And if your going to install a new rom like Hero it's recommended to first wipe everything on your ext partition like it was freshly formated. Wipe in Recovery then flash your Hero build (make sure you meet all the requirements first). Depending on your Hero build you may need to push the app_s folder onto your ext partition. Other builds do it for you (such as the one I'm using. Ref to my signature.) Once you have that all set up and you want to store it reboot back into Recovery and go back into console again:
# mount system/sd
# sh system/sd/switchrom.sh -s HEROROMNAME
This will backup the necessary files for your Hero rom. It is now okay to simply enter:
# sh system/sd/switchrom.sh -r ROMNAME to restore your original Non-Hero rom. You do not need to remove any folders (such as app_s) because the script does this for you.
To return to your Hero ROM it is the same way:
# mount system/sd
# sh system/sd/switchrom.sh -r HEROROMNAME
Once you have to two ROMs set it and properly stored then you should easily be able to switch between the two.
Advice:
Before you use the script ALWAYS make sure that you have significant battery remaining. Failure to do so (based on my experience) may cause your apps to be restored but not your Nandroid Recovery which may result in issues.
Always remember to do a Nandroid backup BEFORE running the script as it is necessary for the script to work properly. Otherwise you may find your recent saved rom may possibly become a crossbreed of apps with a different ROM.
Remember to delete your old Nandroid files. Since they are copied over to the SwitchROM directory, they are not necessary (except for the most recent one).
I personally do not always do a filesystem check but it is recommended.

Binary100100 said:
I had to read your question about 4 times to understand what you're asking and I'm still not too clear.
I don't even know how many questions your asking. Perhaps it just the layout of your post.
Anyway. I'll give it a try because I often use the script to bounce between CM ROMs and Hero ROMs. If your currently using a stable NON-Hero build then store your build by performing a nadroid backup and then use the console:
# mount system/sd
# sh system/sd/switchrom.sh -s ROMNAME
And if your going to install a new rom like Hero it's recommended to first wipe everything on your ext partition like it was freshly formated. Wipe in Recovery then flash your Hero build (make sure you meet all the requirements first). Depending on your Hero build you may need to push the app_s folder onto your ext partition. Other builds do it for you (such as the one I'm using. Ref to my signature.) Once you have that all set up and you want to store it reboot back into Recovery and go back into console again:
# mount system/sd
# sh system/sd/switchrom.sh -s HEROROMNAME
This will backup the necessary files for your Hero rom. It is now okay to simply enter:
# sh system/sd/switchrom.sh -r ROMNAME to restore your original Non-Hero rom. You do not need to remove any folders (such as app_s) because the script does this for you.
To return to your Hero ROM it is the same way:
# mount system/sd
# sh system/sd/switchrom.sh -r HEROROMNAME
Once you have to two ROMs set it and properly stored then you should easily be able to switch between the two.
Advice:
Before you use the script ALWAYS make sure that you have significant battery remaining. Failure to do so (based on my experience) may cause your apps to be restored but not your Nandroid Recovery which may result in issues.
Always remember to do a Nandroid backup BEFORE running the script as it is necessary for the script to work properly. Otherwise you may find your recent saved rom may possibly become a crossbreed of apps with a different ROM.
Remember to delete your old Nandroid files. Since they are copied over to the SwitchROM directory, they are not necessary (except for the most recent one).
I personally do not always do a filesystem check but it is recommended.
Click to expand...
Click to collapse
i was kind of curious about this as well. thank you for the detailed guide. will try this out soon
also just out of curiosity, how is the 69mb swap size treating you on hero? also what about when you go back to cyanogen's rom?

david1171 said:
i was kind of curious about this as well. thank you for the detailed guide. will try this out soon
also just out of curiosity, how is the 69mb swap size treating you on hero? also what about when you go back to cyanogen's rom?
Click to expand...
Click to collapse
I love the 69mb swap. Much better then 32mb.
I don't see any difference using the 69mb on Cyanogen Roms then when I was using the 32mb. The most I ever had my phone on since the adjustments was 34 hours and for some reason I was getting a few FC/Waits and I decided that it was about time for a reboot. I was going to try it with Hero but then Cyanogen 4.1 came out and I only made it to about 12 hours or so.

Calkulin's FORMAT ALL Flashable Update

Calkulin made this flashable update to clear data/cache/dalvick all in one step. Just by simply flashing this update, then your rom of choice. Big thanks to Calkulin for making it easy on everyone.
NilsP made it work with CWM3.0.0.7 and up. Big thanks to NilsP
So, try these scripts and see if this doesnt make wiping easier. It wouldnt hurt to install the update a few times. Install like any other update.
There have been alot of people complaining of clockworkmod3 not wiping correctly or clearing data. Expecially 3.0.0.5
Everyone needs to make sure if your using CWM3, it needs to be at least 3.0.0.7 and up.
3.0.0.7 seems to be most stable.
I've even had problems with 3.0.0.8 not wiping everthing sometimes. This may cause unwanted issues with roms. So even installing the update may not work the first time. Install a few times to be sure
Until we get a new recovery that actually does what is supposed to, we will have to be sure that everything is wiping correctly.
No dissrespect to anyone that has had a hand in making our recoveries. I just want to make sure everyone is starting with a fresh rom.
Remember, cwm2 updates are not compatible with cwm3
Remember, cwm3 updates are not very compatible with cwm2. Even though it doesnt error out.
Remember, cwm3 is a nessasary change that will eventually be our only option.
NilsP said:
I just did a bunch of testing and the CWM that appears to be most consistent with wiping data is 3.0.0.7
3.0.0.5 = Never completely wipes data
3.0.0.8 = Wiped data once in awhile
3.0.0.7 = Wiped data every time
Test process:
Added an app to /data/app/ that was not in my ROM /data/app/ folder and entered other than default settings in apps. When it was not there after a data wipe I call it success and if it was still there I called it failed.
Also when a full wipe did not force the fresh install setup to run since it did not reset the first run bit it was a fail.
The fact that data is not being wiped is what causes most problems for people trying to do a fresh install and either seeing stuff there that should not be there or more likely getting lots of FC's and other erratic behavior. In severe cases won't boot the new ROM.
It never failed to boot but most likely because I was booting my ROM over my ROM.
SIDE NOTE: If you try to install a ROM that is set up to run on CWM v3 and try to install on CWM v2 it will look like it ran and installed but don't expect good results with the new ROM since it more than likely did not run everything in the script.
Click to expand...
Click to collapse
Calkulin's FORMAT ALL CWM2
Calkulin's FORMAT ALL CWM3

This is just what the Dincster community needs right now... big thanx to everyone with this!!!
___________________________________
badseedcustoms.webs.com

Thanks bro.
BTW, I think it's calkulin, not calculin.

wdfowty said:
Thanks bro.
BTW, I think it's calkulin, not calculin.
Click to expand...
Click to collapse
woops, thanks

I am thinking of putting something like this at the top of my ROM scripts going forward. Other ROM builders may want to do something similar
Code:
ui_print("This install script is designed to run on");
ui_print("ClockWorkMod Version 3.0.0.7 or higher");
ui_print(".");
ui_print("If you experience any problems with the");
ui_print("installation or the ROM is acting funny verify");
ui_print("which version of CWM you have installed");
ui_print("---------------------------------------");

NilsP said:
I am thinking of putting something like this at the top of my ROM scripts going forward. Other ROM builders may want to do something similar
Code:
ui_print("This install script is designed to run on");
ui_print("ClockWorkMod Version 3.0.0.7 or higher");
ui_print(".");
ui_print("If you experience any problems with the");
ui_print("installation or the ROM is acting funny verify");
ui_print("which version of CWM you have installed");
ui_print("---------------------------------------");
Click to expand...
Click to collapse
yeah, i was thinking of making my roms wipe eerything during insatall but figured there would be tons of backlash.

incubus26jc said:
yeah, i was thinking of making my roms wipe eerything during insatall but figured there would be tons of backlash.
Click to expand...
Click to collapse
Hey, if they want a proper install with minimal bugs, its a price to pay for a good Rom. I say do it....
___________________________________
Yup.... The ones yoe momma told ya about.... Bad Seed Customs!!

I have CWM 3.0.0.8 on my Incredible.
I was running MIUI 1.3.5.
I flashed Calkulin's_FORMAT_ALL-CWM3.zip.
I flashed Nils' Business Sense - Desire-Z Based V5.0.
It didn't boot properly: kept cyiling between Droid, the SkyScraper, the blue "eye", the red "eye", so I have to wonder if a proper wipe was done.
(A couple of days ago, I made the same transition from MIUI to Nils' ROM, doing the usual manual wipes, and had no problem thereafter.)

I just did a bunch of testing and the CWM that appears to be most consistent with wiping data is 3.0.0.7
3.0.0.5 = Never completely wipes data
3.0.0.8 = Wiped data once in awhile
3.0.0.7 = Wiped data every time
Test process:
Added an app to /data/app/ that was not in my ROM /data/app/ folder and entered other than default settings in apps. When it was not there after a data wipe I call it success and if it was still there I called it failed.
Also when a full wipe did not force the fresh install setup to run since it did not reset the first run bit it was a fail.
The fact that data is not being wiped is what causes most problems for people trying to do a fresh install and either seeing stuff there that should not be there or more likely getting lots of FC's and other erratic behavior. In severe cases won't boot the new ROM.
It never failed to boot but most likely because I was booting my ROM over my ROM.
SIDE NOTE: If you try to install a ROM that is set up to run on CWM v3 and try to install on CWM v2 it will look like it ran and installed but don't expect good results with the new ROM since it more than likely did not run everything in the script.

NilsP said:
I just did a bunch of testing and the CWM that appears to be most consistent with wiping data is 3.0.0.7
3.0.0.5 = Never completely wipes data
3.0.0.8 = Wiped data once in awhile
3.0.0.7 = Wiped data every time
Test process:
Added an app to /data/app/ that was not in my ROM /data/app/ folder and entered other than default settings in apps. When it was not there after a data wipe I call it success and if it was still there I called it failed.
Also when a full wipe did not force the fresh install setup to run since it did not reset the first run bit it was a fail.
The fact that data is not being wiped is what causes most problems for people trying to do a fresh install and either seeing stuff there that should not be there or more likely getting lots of FC's and other erratic behavior. In severe cases won't boot the new ROM.
It never failed to boot but most likely because I was booting my ROM over my ROM.
SIDE NOTE: If you try to install a ROM that is set up to run on CWM v3 and try to install on CWM v2 it will look like it ran and installed but don't expect good results with the new ROM since it more than likely did not run everything in the script.
Click to expand...
Click to collapse
Thanks for the research NIls, I will add this info to the first post

I love you for this! <333333

nils, i just tested the cwm3 version with 3.0.0.7 and flashed it and then my rom and it gave a bunch of force closes and didnt appear to wipe properly. Any ideas?

Force Closes
I had the same issues as Incubus. Had to wipe the old way.

It appears that wiping data via the script is not consistent. Not sure why since wiping data via RM or directly in recovery works well on 3.0.0.7.
It does appear to do system fine but not cache or data for some reason
I will experiment with a couple of alternatives and see what I can come up with.

NilsP said:
It appears that wiping data via the script is not consistent. Not sure why since wiping data via RM or directly in recovery works well on 3.0.0.7.
It does appear to do system fine but not cache or data for some reason
I will experiment with a couple of alternatives and see what I can come up with.
Click to expand...
Click to collapse
How about Dalvik? Just trying to get Dalvik and cache to wipe before installing my builds.

Hmm, seemed to work for me. Using 3.0.0.8. I was on CM7, ran the script, then flashed Incredibly Re-Engineered Z right after. Haven't gotten any FC's yet...

ProTekk said:
How about Dalvik? Just trying to get Dalvik and cache to wipe before installing my builds.
Click to expand...
Click to collapse
This is what I use in my script which works to clear everything but data before installing.
Code:
run_program("/sbin/mount", "/dev/block/mtdblock3", "/system");
run_program("/sbin/mount", "/dev/block/mmcblk0p1", "/data");
run_program("/sbin/mount", "/dev/block/mmcblk0p2", "/cache");
ui_print("Removing Old System...");
delete_recursive("/system");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache/");
BrettApple said:
Hmm, seemed to work for me. Using 3.0.0.8. I was on CM7, ran the script, then flashed Incredibly Re-Engineered Z right after. Haven't gotten any FC's yet...
Click to expand...
Click to collapse
It seems to be hit and miss which is what we are trying to sort out.

NilsP said:
This is what I use in my script which works to clear everything but data before installing.
Code:
run_program("/sbin/mount", "/dev/block/mtdblock3", "/system");
run_program("/sbin/mount", "/dev/block/mmcblk0p1", "/data");
run_program("/sbin/mount", "/dev/block/mmcblk0p2", "/cache");
ui_print("Removing Old System...");
delete_recursive("/system");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache/");
Click to expand...
Click to collapse
Thanks for this

Just my experience that you probably should wipe your recovery nothing installs well over 3.0.0.5 I'm not using your script but I haven't had any problems since using 3.0.08

I just go directly into recovery, and manually wipe before installing a ROM. I have had the most sucess with doing it that way.

[Q] i897 dont boot

I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.

kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?

Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.

kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.

BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).

kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.

Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?

kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app

You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.

With TWRP + Backups Working Now - Which partitions make sense to backup regularly?

Until now, no my rooted Samsung Note 3 I have automatic TWRP backups running every night. This just mirrors my paranoia that I will manage to screw up something and recovery via TWRP restore is often faster/easier/more complete than trying to do anything else. I do this using the OpenRecoveryScript and have always used this backup command:
backup DSBCR DailyBackup
Which gets data, system, boot, cache, and recovery. I plan to do the same now that I know to put the OpenRecoveryScript into /data/cache/recovery instead of /cache/recovery on my Note 3.
So my question here is what partitions make sense to backup on the V40? And by "sense" I mean something likely to change or get broken (by errant apps or, more likely, my own doing) AND having the ability to restore using TWRP restore from backup.
There are a ton of partitions on this device - most of which I know little/nothing about. I do know that the system and vendor partitions have duplicates and so those are not needed, I guess. And it seems that the OpenRecoveryScript backup command has no way to handle anything except the following anyway:
S: system,
D: data,
C: cache,
R: recovery,
B: boot,
A: and-sec,
E: sd-ext (I don't need the external SD)
So there would seem to be no way to get modem and all the others I don't know much about anyhow.
When I tried to use the same command as above, I ended up with only boot and data - which is a great start! I think I saw an error that system was not mounted so maybe that explains its absence - perhaps I need to mount it first in my script (which I never have had to do on my Note 3)? Even though my V40 is rooted with Magisk, I am making changes to system so I do want to back that up (so long as I can use it during a restore).
Does it make sense to try and backup recovery since things seem really different recovery-wise on this device? Same question for cache and boot?
Thanks for your tolerance of my newbie questions.

Well from empirical experience, it seems that there is no way to backup anything save boot and data. I was able to mount /system_root but that had no impact on backing up system. And I was unable to mount cache or recovery explicitly so those are out as well.
PS - for anyone using the old 123 special partition for backups, they are no longer supported. I have never used them but decided to try and see what happened - only messages that they are no longer supported.
Perhaps there is some other way to accomplish this? Suggestions welcome. Thanks
Thanks.

That I'm aware of recovery should backup as part of the boot partition....I could be wrong tho

Ainz_Ooal_Gown said:
That I'm aware of recovery should backup as part of the boot partition....I could be wrong tho
Click to expand...
Click to collapse
I guess that does make sense. Thanks. I am still trying to get my mind around the whole new situation (compared to my old Note 3).

backing up a rooted phone

I want to do a backup of my android before restoring OOS on the phone (for a test). Was planing to use titanium backup but it seems like the app isn't very good anymore (the reviews are really bad now). Any other ideas? ADB didn't really create that a good backup and I lost WhatsApp and other stuff.
Current setup: lineage 17.1, twerp (latest version) and magisk 20.4.
Just realised I can use twrp for this ??

Eggstones said:
I want to do a backup of my android before restoring OOS on the phone (for a test). Was planing to use titanium backup but it seems like the app isn't very good anymore (the reviews are really bad now). Any other ideas? ADB didn't really create that a good backup and I lost WhatsApp and other stuff.
Current setup: lineage 17.1, twerp (latest version) and magisk 20.4.
Just realised I can use twrp for this ??
Click to expand...
Click to collapse
Two options:
1. Use TB to backup and restore app data and non-bundled/not split apks. Use SAI https://play.google.com/store/apps/details?id=com.aefyr.sai to backup/restore bundled/split apks.
2. Use Migrate https://forum.xda-developers.com/an...stom-rom-migration-tool-t3862763/post78060823
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Two options:
1. Use TB to backup and restore app data and non-bundled/not split apks. Use SAI https://play.google.com/store/apps/details?id=com.aefyr.sai to backup/restore bundled/split apks.
2. Use Migrate https://forum.xda-developers.com/an...stom-rom-migration-tool-t3862763/post78060823
Click to expand...
Click to collapse
I actually don't understand option one but two sounds just the ticket. Thank you.

Eggstones said:
I want to do a backup of my android before restoring OOS on the phone (for a test). Was planing to use titanium backup but it seems like the app isn't very good anymore (the reviews are really bad now). Any other ideas? ADB didn't really create that a good backup and I lost WhatsApp and other stuff.
Current setup: lineage 17.1, twerp (latest version) and magisk 20.4.
Just realised I can use twrp for this ??
Click to expand...
Click to collapse
If you have TWRP, then indeed, adb backup --twrp data should be your friend.
However, extracting TWRP backups on your computer is not that trivial. To do that you need twrpabx, specifically prudy's fixed version. On a Linux computer, it is quick and easy to compile. I haven't tried on Windows.
Else, TWRP backups can only be restored on the same phone (or maybe also on another phone of the same model)

yahya69 said:
If you have TWRP, then indeed, adb backup --twrp data should be your friend.
However, extracting TWRP backups on your computer is not that trivial. To do that you need twrpabx, specifically prudy's fixed version. On a Linux computer, it is quick and easy to compile. I haven't tried on Windows.
Else, TWRP backups can only be restored on the same phone (or maybe also on another phone of the same model)
Click to expand...
Click to collapse
That should be then fine. I just want to try a thing on OOS so no switching of phones intended.
ADB backup I don't think restored the apps data when I tried it which was the main reason for doing the backup

Eggstones said:
That should be then fine. I just want to try a thing on OOS so no switching of phones intended.
ADB backup I don't think restored the apps data when I tried it which was the main reason for doing the backup
Click to expand...
Click to collapse
When you do adb backup --trwp you can add which partitions you want to have backup up:
adb backup --trwp data system boot recovery (haven't checked the names, but data and system should be the most important ones)
Just be mindful that when you do an adb backup --twrp, the backup does not include Internal Files, so make sure to back them up separately or not to wipe them in the first place. I would recommend that after backing up your precious data, you go to "advanced wipe" and there select system, data, cache and dalvik cache. After that, happy flashing..

yahya69 said:
When you do adb backup --trwp you can add which partitions you want to have backup up:
adb backup --trwp data system boot recovery (haven't checked the names, but data and system should be the most important ones)
Just be mindful that when you do an adb backup --twrp, the backup does not include Internal Files, so make sure to back them up separately or not to wipe them in the first place. I would recommend that after backing up your precious data, you go to "advanced wipe" and there select system, data, cache and dalvik cache. After that, happy flashing..
Click to expand...
Click to collapse
I'm doing this with very basic understanding of what I'm doing/being recommended to do. Is adb backup --twrp a command or twice different things as in 'adb backup' to computer and twrp is done on the phone?
My plan is to copy the important data like audio files and photos to my laptop, then use use migrate to make a copy plus twrp backup. I should be fine after that I think.
I'm just hoping my root and magisk doesn't go when I reinstal OOS 9.0.6 as I want to try to edit my system to see if I can force vowife to work.

Eggstones said:
I'm doing this with very basic understanding of what I'm doing/being recommended to do. Is adb backup --twrp a command or twice different things as in 'adb backup' to computer and twrp is done on the phone?
Click to expand...
Click to collapse
That would be a command you have to run in a command line window on your computer. Again, after the --twrp parameter, you can pass the names of the partitions you want to have backed up, which would probably be data, system, recovery and boot.
First, of course, you have to install adb, if you haven't already. But if that's too complicated, it might be easier to make a full backup in TWRP and then copy it over to your computer. adb backup --twrp basically saves a step and you don't have to have sufficient space on your phone for a full backup
My plan is to copy the important data like audio files and photos to my laptop, then use use migrate to make a copy plus twrp backup. I should be fine after that I think.
Click to expand...
Click to collapse
That's always a good idea, even though wiping data in TWRP should not touch your internal files.
I'm just hoping my root and magisk doesn't go when I reinstal OOS 9.0.6 as I want to try to edit my system to see if I can force vowife to work.
Click to expand...
Click to collapse
I don't know, I never used it. I'm happy with LineageOS. I guess you can re-flash Magisk trough twrp and then in your running system, you can re-install the MagiskManager apk. But I haven't tried it.