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.

[Guide] CM6 Installation with a2sd and swap

I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
e) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.​Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w​ c) reboot into recovery.​
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.​
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone​
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt a2sd​
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) If you are not using a2sd and want to setup swap, please enter the below command in the terminal otherwise continue to step 9.
su
sh /sdcard/fr-patch140.txt sdext​
reboot the phone.
9) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt swap​
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
Free​If you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 9 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apk​
Also there are some apps which I don't prefer, as I don't use android native keyboard, Android browser, POP email, amazon MP3 etc. So I have created a script for my use which has been shared and it can be run from the terminal..
download remove-app-v1.0.txt and store it to root of your sd card. than enter below commands in terminal
su
sh /sdcard/remove-app-v1.0.txt​
currently this script will remove below mention apps based on user input.
Amazon MP3, Live Wallpaper picker, CM Wallpapers, POP Email, Android Native Browser, Android Native Onscreen Keyboard, Genie Widget...
Note: - Before removing browser and keyboard please make sure you have a replacement for them.
I do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat, Lbcoder for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
If you like my guide and want to Donate

Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on

supa2001 said:
Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on
Click to expand...
Click to collapse
Yes, swap can be there without A2sd..
Do you have Fr-Patch139.txt script or any other version...could you please reboot and so the step 8 again

I did it many times
Do I need to create some files like userinit ?
Thanks for replying.

supa2001 said:
I did it many times
Do I need to create some files like userinit ?
Thanks for replying.
Click to expand...
Click to collapse
Try below command:
sh /sdcard/fr-patch139.txt sdext​
reboot the phone
sh /sdcard/fr-patch139.txt swap​
If this doesn't work, could you please pass on the message you are getting from the script.

G1sanju said:
Try below command:
sh /sdcard/fr-patch139.txt sdext​
reboot the phone
sh /sdcard/fr-patch139.txt swap​
If this doesn't work, could you please pass on the message you are getting from the script.
Click to expand...
Click to collapse
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.

G1sanju said:
I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
d) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.​Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w​ c) reboot into recovery.​
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.​
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone​
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt a2sd​
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt swap​
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
Free​If you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 8 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apk​I do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
Click to expand...
Click to collapse
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...

supa2001 said:
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.
Click to expand...
Click to collapse
"danger detected" message is for SPL, It checks for the SPL first and you have danger spl installed.
By default CM6 does not mount ext partition as it does not support a2sd right now. sdext creates a mount point for ext partition. a2sd internally does that but as you are not using a2sd this was not done.

vermaekansh said:
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...
Click to expand...
Click to collapse
Thanks, If you use this guide then please provide your feedback and suggestion towards it.

Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.

supa2001 said:
Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.
Click to expand...
Click to collapse
In the terminal
sh /sdcard/fr-patch139.txt rev swap​
this will turn the swap off.

Watch out...newbie in the room
Okay, you are going to love this.... I'm sorry if this is too long but I hope you can help a newbie trying to learn this stuff!
I am REALLY new to all this, and did a Root and Rom Update as the Unlockr.com videos taught me, to get CM6. And then also added the gapps file because I read a thread that that was needed to get gmail and the market on my phone. Once rebooted, everything worked ok but slow. Then I noticed that my gmail wasn't syncing, and then it started to force close. So I did a wipe and loaded CM5 because I saw on a thread that that was faster for the G1. With all of this, after reading your thread and suggestion, I am wondering...
1. Is CM6 slow for you?
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
3. Should I stick with CM5 or try CM6 following these suggestions??
And big ones.... I wish there was a website somewhere with definitions to all the terms and apps used. Lol.. I Google all of them but don't always find anything that actually describes what they are.
Swap and app2sd were mentioned on the video instructions for loading a new ROM but do they automatically come in the ROM zip files? Because in the video they didn't load them separately. They partition the card "for" them, but don't show installing them. Obviously I assume App2sd is a program to store your apps on your sd card. Is this something that I SHOULD install? Is swap something I should install?
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
I know this is a lot of questions... I decided to ask them all here because they pertain to this thread because I'm wondering if I should do this...
Thanks for any and all answers!

I would assume that you have a G1, and my answer is based on that assumption. If you have different phone let me know.
1. Is CM6 slow for you?
If I don't use a2sd and swap, answer is yes. I install lot of apps, with cutomMTD it works fine in starts but slows down after some time. With a2sd and swap it is worth a try.​
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
CM roms does not distribute google apps with the rom as its not legal. So if you want gapps then yes that file has to be flashed. CM6 can be run without gapps, but you won't get gmail, market etc..once you have gmail it should sync automatically.​
3. Should I stick with CM5 or try CM6 following these suggestions??
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....​
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
G1 was build with a low memory and the way internal memory has been partition todays rom can't fit into it. That's why dangerSPL, but there is a risk involved in installing dangerSPL. If you don't follow the instruction you can brick your phone. CustomMTD is a safe method. This increase the size of data partition so you can install more apps internally. link for that thread is in first post.​
a2sd is a way to store apps on sdcard, sdcard needs to be partitioned to support that..step 1 - e in my guide. That's a manual way of doing it. If you have AmanRA recovery then it will have a menu option for that. Most of the rom supports it automatically, so if you have sd card partition then rom will automatically do that.
CM6 does not support a2sd so it has to done in different way. CM5 supports it but in settings - application - a2sd has to be checked on to move your apps to sdcard.​
Swap is kind of extra memory to help running the applications. if you run multiple application together then you need swap on CM5 and CM6.​

G1sanju said:
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....​
Click to expand...
Click to collapse
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6

vermaekansh said:
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6
Click to expand...
Click to collapse
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App

G1sanju said:
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?

vermaekansh said:
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?
Click to expand...
Click to collapse
Roms are personal preferences, I also tried lot of roms before settling on CM... and for CM there are no eta it will be released when it's done...
Sent from my HTC Dream using XDA App

WOW!
THANK YOU!!! You are awesome for going through all of those!
Yes, it is a G1.
Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!

Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
CM6 is based on froyo, latest version of android...its good and yes speed is comparable. Also CM has added new stuff in it, like fully customizable power bar and other stuff...Full changelog is there in CM6 thread.​
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
For CM6 a2sd is through script, instruction is in first post. I have included customMTD also there. So if you follow the guide, you will be having customMTD, a2sd and swap...swap require an partition on your sdcard, if you don't have that partition then it will ask for swap file.​
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
you can wipe and start over again, first post should be good for you.​
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!
Oh I forgot about the fastboot, fastboot and adb are tool, which give an option to control, flash and do other thing on the phone from PC. The link for setup guide is in first post.​

Thanks again!!
Man! You are great! Thanks again for all your help! Now let's see if I can manage to follow your thread and not brick my phone! Lol
Until next time....

Dual booting 1.2 on main partition

I wanted to add this as a reply to the existing How-To guide in Android Development, but I don't have sufficient permissions to post in that forum.
The 3 guides currently in that forum are very detailed, and consequently very complex. If you haven't rooted a NC yet and/or have not set up dual booting yet, you should use those guides. However, having done both of those things several times, I think it would be helpful to have a brief overview of the steps to take to 1) Install 1.2 and 2) Set it up to dual boot.
I also wanted to have 1.2 on my main partition so that I could keep it up-to-date with new flashable roms as they come out, but leave my old 1.1 setup on the second partition, so that I could always go back to a ROM that I knew was functional for me. Setting it up this way took a few extra steps.
To get all the files you need, you'll have to go throug the Android Development forum. This post is only for the overall steps, and the order to take them in:
1)If you're already set up to dual boot, it's probably a good idea to remove that and go back to a single partition. (This will erase the ROM you're running on your second partition)
2)Create a nandroid backup of whatever ROM you're currently using and enjoying. (You can only backup the ROM on your primary partition)
3)Upgrade to 1.2
4)Root 1.2
5)Set up dual booting (flash the dual boot prep .zip)
**If you want to run 1.2 as your primary partition, here's where the tricky part comes.**
6)Now boot into CWM and create a nandroid backup of your rooted, dual-boot-prepped 1.2.
7)Boot into CWM and restore whatever custom ROM you want as your secondary partition. THIS WILL ERASE your 1.2 setup, so make sure you've got it's backed up
8)Flash the eclair-to-dual-boot.zip. This will copy whatever ROM you just restored onto your secondary partition.
9)Restore the backup you made of your rooted, dual-boot-prepped 1.2
Now you've got 1.2 set to boot up by default, and you can flash new kernels, new ROMs, etc... You've got a different ROM (in my case rooted 1.1) set to boot when holding power+n.
If you wanted 1.2 as your secondary (power+n) partition, at step 6 you'd flash eclair-to-dual-boot.zip, and then restore whatever ROM you like as your primary, and you'd be done.
Hope this helps someone. It would have helped me.
I don't really know what the forum etiquette is, but if I need to go through and add links to the files, threads, etc... and add credits, someone please let me know and I'll do that later.

Guide MultiBoot 33b [EASY]

Hi everyone, my name is Mirko and I am an italian student and first of all sorry for my bad english, fiddle with ROMS and Kernels is an hobby for me and i really enjoy it.
I would make a tutorial for anyone who can not unencrypt OnePlus3 with any ROM. READ EVERYTHING BEFORE START.
I AM NOT RESPONSIBLE FOR WHAT COULD HAPPEN TO YOUR DEVICE. PAY ATTENTION.
DOWNLOAD
VIRUSTOTAL
Open and extract the zip file where you want.
Install USB drivers
Install ADB drivers by open adb-setup-1.3.exe, Y, Y ,Y and close.
Copy fastboot adb drivers 1.0.36 to C:\adb and overwrite.
Open CMD in the same file folder by pressing Shift+right click and type "adb", if it say nothing match reboot your pc.
Plug your phone to PC and allow adb access, then type "adb devices" and you should see your phone id.
We have to unlock bootloader, THIS ACTION PERFORM A FULL, FULL (EVEN INTERNAL MEMORY) OF YOUR PHONE, BACKUP EVERYTHING. Tick on OEM Unlock in developer option (nothing here will happen). Type "adb reboot fastboot" and your phone will reboot in fastboot mode. Use now "fastboot devices" for recognize your phone and "fastboot oem unlock" for unlock bootloader.
Do not restore backup cause we are gonna wipe again, back into fastboot mode (AFTER OEM UNLOCK FROM DEV OPTIONS) and flash twrp using fastboot flash recovery multiboot....img.
If phone reboot back again into fastboot and type fastboot format userdata. Reboot into recovery.
Now on recovery start MTP and copy OOS/HOS and supersu zips into your phone, flash the ROM, DO NOT REBOOT, flash supersu. Your device is now unencrypted.
Type adb shell chown -R media_rw:media_rw /data/media on CMD for avoid problems after flash.
You can now flash multiboot.zip and you have to inject boot sector every time you will install/update ROMS. OOS/HOS OTA ARE NOT COMPATIBLE WITH TWRP, YOU HAVE TO FLASH THE ENTIRE ZIP FILE FOR UPDATE IT.
You will see a slide menu on top right side of TWRP and from here you can install new roms on INTERNAL MEMORY. In advanced option select "no-kexec workhound" (important).For gapps go to ROM list, select the interested rom, then flash zip, >gapps.zip. NOT ALL ROMS ARE COMPATIBLE WITH MULTIROM.
Every OTA (i think) except (for sure) stock roms will update without problems.
Reboot your phone and it will boot on multiboot menu, here you select rom you want boot.
YOU ARE DONE.
I tested it on my phone and it works really fine, OOS can be installed as secondary rom BUT FLASH SUPERSU BEFORE REBOOT.
Installing secondary ROMS are slower than primary, cause it will create virtual disks.
If you have problems with pattern after reboot, back into twrp, advance, filemanager, /data/system and delete locksettings.db, locksettings.db-shm, locksettings.db-wal and reboot. Pattern will be deleted.
Installing Kernels wich are not compatible with MULTIROM will softbrick the phone, and you have to wipe.
Installing Kernels on virtual ROMS will softbrick the ROM.
I think my guide is done.
If you have problems
FOR ANY PROBLEMS AND DOUBTS WRITE HERE OR PM ME.

Wow, there's a lot of misinformation in this post.
No "virtual disks" are created. Mount points are changed to point to the secondary ROM.
You don't have to use a multi ROM capable kernel, you should read up on the no kexec workaround before you write up a post like this
Also, you can flash kernels to secondary ROMs. I'm not sure what gives you the impression that you can.
You don't have to flash the multi ROM zip Everytime you write to the system partition. Mutirom is on the "SD card" on the data partition
Aside from the incorrect parts, the rest of the tutorial is poorly written and very difficult to follow
Why don't you leave the tutorials to the people who actually know how things work on the back end.
Sent from my Pixel XL using Tapatalk

slothdabski said:
Wow, there's a lot of misinformation in this post.
No "virtual disks" are created. Mount points are changed to point to the secondary ROM.
You don't have to use a multi ROM capable kernel, you should read up on the no kexec workaround before you write up a post like this
Also, you can flash kernels to secondary ROMs. I'm not sure what gives you the impression that you can.
You don't have to flash the multi ROM zip Everytime you write to the system partition. Mutirom is on the "SD card" on the data partition
Aside from the incorrect parts, the rest of the tutorial is poorly written and very difficult to follow
Why don't you leave the tutorials to the people who actually know how things work on the back end.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
First of all thank you for reply, i totally missed to enable no-kexec workhound function...
I want to clarify that it is my first guide I do, I started in make some because I want to help people like me who have had difficulties in carrying out certain passages. I accept ANY advice and I will try to improve with time. I admit I made a mistake forgetting the previously mentioned feature. I can tell you, however, that the multi-boot every time you install a new ROM is removed. Going blind I specified / system because it is the main partition is rewritten during a flash. But I have a doubt. The Kernel for secondary ROM, should not be predisposed to function properly?

mirko8054 said:
First of all thank you for reply, i totally missed to enable no-kexec workhound function...
I want to clarify that it is my first guide I do, I started in make some because I want to help people like me who have had difficulties in carrying out certain passages. I accept ANY advice and I will try to improve with time. I admit I made a mistake forgetting the previously mentioned feature. I can tell you, however, that the multi-boot every time you install a new ROM is removed. Going blind I specified / system because it is the main partition is rewritten during a flash. But I have a doubt. The Kernel for secondary ROM, should not be predisposed to function properly?
Click to expand...
Click to collapse
I assure you, you do not have to reflash the mutirom zip Everytime. I have flashed dozens of times on my phone and have not had to flash mutirom again. The only exception is if you wipe internal storage, BC it wipes your "sdcard"
Mutirom patches the kernel when you flash to to secondary, hence almost any kernel will work
Sent from my Pixel XL using Tapatalk

slothdabski said:
I assure you, you do not have to reflash the mutirom zip Everytime. I have flashed dozens of times on my phone and have not had to flash mutirom again. The only exception is if you wipe internal storage, BC it wipes your "sdcard"
Mutirom patches the kernel when you flash to to secondary, hence almost any kernel will work
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
When my CM13 (Internal rom) installs OTA, after reboot multiboot menu won't appear, and i can't select secondary roms for boot them, i solve by re-flash multiboot.zip...

What you have to do in that case is go into the mutirom menu from twrp , then hit " inject boot sector"
That patches the new kernel from the OTA. You dont need to reflash the entire mutirom zip
Sent from my Pixel XL using Tapatalk

slothdabski said:
What you have to do in that case is go into the mutirom menu from twrp , then hit " inject boot sector"
That patches the new kernel from the OTA. You dont need to reflash the entire mutirom zip
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Ok thank you, i will update the guide.

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).