Database Users

Going from Apex to CM7

So I have a Droid 2 which I rooted and have run Apex RC3 on since last fall. It recently has slowed down a bit and I have wanted to try switching to CyanogenMod7, but the whole concept of downgrading and then rerooting and then finally flashing the ROM seemed quite complicated.
Is that in fact what I have to do? I'm on 2.3.3, not 2.3.4 (I know there's a problem with downgrading from that), but is it not possible to simply flash CM7 from my current situation? It seems kind of redundant to unroot my phone just to reroot it again.
Finally, I am using Titanium Backup to store some data and I have a few questions. First of all, which one of the many contacts options is the one that actually stores my contact data? I would prefer not to backup and then restore all five or six of them. In addition, if I am forced to flash back to stock and unroot, will anything happen to my backups (obviously I can't use Titanium Backup while unrooted, I mean once I finally reroot and get CM7).
Thanks in advance for any help!

Find the version of CM7 for Ginger Bread (2.3.3)
Get the zip, and GApps if necessary
Place it on the root directory so it will be easy to locate
Go into your contacts and export them to your SD Card
Boot into Recovery
Wipe Data, Wipe Cache, go to Advanced then Wipe Dalvik Cache
Go to Mounts and Storage, Format System, then Mount System
Install zip from sd card, choose zip from sd card, select and let it run (repeat for Gapps if necessary)
Reboot

Actually it is possible to install cm7 over 2.3.3 you just have to use the unofficial cm7 on rootzwiki
Sent from my Droid Incredible using xda premium

So pretty much, I can just flash any of these ROMs the same way I did Apex (in recovery, wipe the data and cache and then install .zip for ROM and gapps) so long as I'm running the right OS/have the right kernel? I noticed on rootzwiki that there is actually a version of CM9 up, could I do that the same way too?
Just some info in case it's needed:
System Version: 4.5.153.A955-continuous.Verizon.en.US
Android Version: 2.3.3
Baseband Version: BP_C_01.09.13P
Kernel Version: 2.6.32.9-gca08d89
[email protected] #1
Tue Jul 19 22:10:06 IST 2011

Yes, you can flash CM7/9, MIUI, Gummy, etc as you did before. Just make sure if you flash any actual 4.0 roms such as CM9/MIUI V4 you format and then re-mount system. There are slight differences in GB and ICS that apparently necessitate this because anyone who has skipped this step has ended up having to SBF back to GB and start over.

Perfect, thanks. One last question for now though (I'll flash later today): will the data I'm saving on Titanium Backup transfer over to an ICS rom? I'm saving my messaging data and some data for games, and I'm not sure whether they are applicable on the new OS.

As far as I know yes, that will work with TB, but you also might want to download an SMS backup app from the Play Store quickly just in case.

Just wanted to say thanks to MissionImprobable and Albinoman for their help--I'm successfully running CM9 on my Droid 2!

[Q] Sanity check: install new bootloader, new PA, full wipe

Hey
I got a bad case of the lag (sometimes i have to wait 30s for the launcher to show the icons after unlocking the screen <.<'). Tried the Forever Gone approach, but i'ts still laggy and i guess it's because i'm still on the old code base (with Paranoid Android 2.14). So i've decided to do a full update - new bootloader, last PA (2.2), and a new kernel (i'm still with the stock one). Also i think to do a full wipe as i'm going along with it. I'm using TWRP.
So i did my research, but it'll be nice if somebody does a quick sanity check on my todo list
0. Backup (i don't like the idea of full apk+settings backup, so i'll try to cherrypick the things i want to backup - like game saves, etc)
1. Full wipe - nuke /data, /system, /boot
2. Flash new bootloader (JZO54K_bootloader.zip)
3. Flash new Paranoid Android 2.2
4. Redownload all apps from Appstore
5. Restore backup
The kernel part is missing, because i'm still undecided with what should i go. I don't want overclocks, but i want it to be able to undervolt (apply Jay's buttery goodness maybe). If someone can recommend me something i'd be grateful.
So... that's about it

This is what I did when I updated but instead with CNA.
0. Backup
1. Full wipe
2. Flash new rom ( I flashed CNA 3.7.0 before they removed it for bug fixes)
3. Reboot and make sure rom is functional
4. Reboot into recovery and flash new bootloader
5. Reboot again to test, reboot to recovery to test, and lastly fastboot
6. Restore backup from Titanium

You forgot an important steps.. flash GAPPS after you flash PA. Otherwise your google apps won't work.
Do this:
1. Backup
2. Wipe Data/Cache/ Delvik Cache
3. Flash PA 2.3
4. Flash GAPPS
5. reboot
Then you set up your nexus 7 however you want, with the help of titanium etc :good:

Ah, yes - i count this as a thing that goes hand to hand with the PA flashing so that's why it's not there.
So - tomorrow when i have some free time i'll wipe the lagging monster
Thanks!

[Q] After Flashing a rom??

hello I have a question that may seem dum but through trial and error many times I realized asking the questions before actually doing stuff when it comes to android mods is best anyways I just flashed a rom code name Sammy to get a touch wiz experience and before I did that I did a nandroid backup through twrp recovery and I really want to go back to what I had before the rom or even try a different one like smooth rom but I wasn't sure if I could just restore from my back up or if I need to flash something differently all together to start over thanks for your help

johnfred1987 said:
hello I have a question that may seem dum but through trial and error many times I realized asking the questions before actually doing stuff when it comes to android mods is best anyways I just flashed a rom code name Sammy to get a touch wiz experience and before I did that I did a nandroid backup through twrp recovery and I really want to go back to what I had before the rom or even try a different one like smooth rom but I wasn't sure if I could just restore from my back up or if I need to flash something differently all together to start over thanks for your help
Click to expand...
Click to collapse
Hi, johnfred1987...
No, there's nothing you have flash before you start over.
Prior to a Nandroid restore in TWRP, I prefer to wipe Dalvik Cache, Cache, Data and System - although be careful with wiping System; ensure you have either a flashable ROM .zip or a Nandroid backup on Internal Storage first.
If you wipe System without either one of these to fall back on, your Nexus 7 will have no bootable OS; just TWRP and the Bootloader. Although not an insurmountable situation, its a pain in the backside to recover from.
You only really need to wipe System if you're flashing a new ROM... although if you're upgrading a given ROM from, say, version v1.0 to v1.1, you can generally (unless otherwise specified by the developer), 'dirty flash' it over the top (although I still like to clear Dalvik and Cache).
Generally, though, all you need to do is 'Swipe to Factory Reset'... But whatever you do, don't touch the FORMAT DATA button, as this will wipe your Internal Storage, including any Nandroids, ROM .zip flashables, Titanium backups and whatever else you have stored on the Nexus.
Good luck.
Rgrds,
Ged.

GedBlake said:
Hi, johnfred1987...
No, there's nothing you have flash before you start over.
Prior to a Nandroid restore in TWRP, I prefer to wipe Dalvik Cache, Cache, Data and System - although be careful with wiping System; ensure you have either a flashable ROM .zip or a Nandroid backup on Internal Storage first.
If you wipe System without either one of these to fall back on, your Nexus 7 will have no bootable OS; just TWRP and the Bootloader. Although not an insurmountable situation, its a pain in the backside to recover from.
You only really need to wipe System if you're flashing a new ROM... although if you're upgrading a given ROM from, say, version v1.0 to v1.1, you can generally (unless otherwise specified by the developer), 'dirty flash' it over the top (although I still like to clear Dalvik and Cache).
Generally, though, all you need to do is 'Swipe to Factory Reset'... But whatever you do, don't touch the FORMAT DATA button, as this will wipe your Internal Storage, including any Nandroids, ROM .zip flashables, Titanium backups and whatever else you have stored on the Nexus.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks worked like a charm smooth rom now lots better

johnfred1987 said:
Thanks worked like a charm smooth rom now lots better
Click to expand...
Click to collapse
You are most welcome... glad you found something you like.
Rgrds,
Ged.

[KERNEL][RECOVERY][LOS15.1] F2FS upstreamed Kernel + TWRP for Lineage 15.1

WARNING: I am not responsible if you brick your device or lose any data. I personally heavely tested these releases myself and have not encountered any problems.
These are built on official sources and nothing more should be broken but remember to always make backups before installing any mods, kernels etc.!
You should read everything I wrote in this thread before taking any steps unless you know exactly what are doing.
About:
Okay, so I was tired of almost not usable Magisk on official builds because of outdated Moto F2FS implementation, so I built new LOS15.1 kernel and Treble-compatible TWRP with newer version of it for myself and I want to share this with you.
You may ask why I did it and what does it change, so here's the list of features:
This combo may be solution for smooth transition from 15.1 --> 16 without losing data (Without this you will need to reformat your /data partition before flashing when the day of 16 comes - confirmed by Mike). I cannot say 100% that it give you this ability but I'm pretty sure it will!
This Kernel and TWRP applies to LineageOS 15.1, all LOS15.1-based ROMs (like RRemix) and all Treble GSI's.
F2FS loopback fix module is not needed anymore, you can directly install modules from Magisk Manager app.
Magisk modules are persistent now. They will never disappear, even when cache is cleared.
Magisk hide settings are persistent now. They will not reset after reboot.
You can now use systemless hosts properly (No ads and SafetyNet is still passing!).
Filesystem R/W speeds may and should be slightly better (I haven't tested this myself so feel free to do before-after benchmark comparisions).
Don't need to start from zero. You can restore your /data backup after formatting device and it will work just fine.
TWRP is updated to version 3.2.3-0 so it may fix OTA's on "enter pin to boot" encrypted devices.
In TWRP there's written "Lineage" next to it's version to avoid confusion, especially for newbs (Lineage because everyone's talking about LOS TWRP and it's also built on Lineage source)
"Format Data" button in "Wipe" screen is temporarily removed until I/we find fix to make it work. This feature is still broken and causing bootloops (Like on TWRP from LOS Wiki). You still need to use official one for decryption.
That's all I think. I will edit this thread If missed something.
Instructions:
* This instruction applies to new and existing LOS-based ROMs users *
* This tutorial I wrote for someone may be useful if you need help with bootloader mode(fastboot) *
Important: If you don't care about porting your /data to newer F2FS (not talking about Internal data) and willing to start from "zero" then you just should typical LOS installation steps + changing kernel (Steps 1 - 8 and 14 eventually if you're going to restore some pictures or something)
1. Do /data partition and/or Internal Storage backups if you didn't already. Pull them to your computer or SD card.
2. Flash TWRP 3.2.3-0 Lineage build (lineagetwrp.img) from the download section using method you want (fastboot one is recommended).
3. Flash latest official build of LOS15.1 (If you have it already then you can skip this step).
4. Flash bootimage (f2fs_boot.img): Install > Install Image > f2fs_boot.img and check "Boot"
5. Download latest official TWRP from HERE
6. Boot to bootloader mode (fastboot) and use this command "fastboot boot [OFFICIAL_TWRP_IMAGE.img]" to boot into official TWRP without flashing it.
7. When in official TWRP: Wipe > Format Data > type "yes". If it fails then reboot to bootloader mode (Main menu > Reboot > Bootloader) and boot it once again as in point 3 (It happens very often).
8. If formatting went fine then go to: Reboot > Recovery to boot to recovery flashed before. After it boots just make sure that it says "3.2.3-0 Lineage" on top bar like in attachment screnshot
9. Wipe > Advanced Wipe > check "Data" > Repair or Change File System > Change File System > F2FS (This step is not really necessary but it confirms that everything is set up if no errors was throwed here).
10. Reboot to recovery and put your TWRP /data backup on your Internal Storage via PC - Skip if on SD card.
11. Restore your TWRP backup.
12. Don't exit yet if you haven't restored from SD card. There's a little bug(?) where your data from Internal Storage will stay in /data/media directory but MTP will switch to /data/media/0/ after first boot so you will be not able to see that data via PC. Make sure you've deleted these files before rebooting to system. You can do this after first start too but these files will extend encypting time at least twice.
13. Finally you can reboot. In case you were using any lockscreen when doing a backup you should check THIS
14. You can put back your internal storage data right when ROM successfully booted.
Download:
DOWNLOAD - 12.01.2019
Troubleshooting:
If you encounter any problems in any of these steps you will probably need to start from step 6.
Still not able to do this or messed something up very badly so u can't enter TWRP? Try entering bootloader mode and type "fastboot erase userdata", then proceed to step 6.
Remember: After doing an OTA you will need to flash "f2fs_boot.img" once again before booting into system. Else you will end in constant reboots until you do this. Kernel will be updated when some changes will be pushed into it (not often)
Any support for this will be probably instantly dropped after first stable enough release of LineageOS 16.
Have Fun!​
All thanks goes to @mikeioannina for commiting to kuntao sources which I used here.
Kernel source
Recovery source​

Thx, I was looking for this.
---------- Post added at 10:11 AM ---------- Previous post was at 09:20 AM ----------
I reread the whole article again and better to wait for lineage os 16 and fixes. I am fine with ext4 now. No need to mess with twrp and bootloops

Well, the most complicated flashing orgy so far...

Why making another kernel for putting just 1 commit that fixes f2fs? Recovery was needed because for treble we are still using 3.2.2-0, but kernel is useless, @mikeioannina could merge that commit in official lineage kernel.

mahmutpekkara said:
Thx, I was looking for this.
---------- Post added at 10:11 AM ---------- Previous post was at 09:20 AM ----------
I reread the whole article again and better to wait for lineage os 16 and fixes. I am fine with ext4 now. No need to mess with twrp and bootloops
Click to expand...
Click to collapse
There's almost no changes in that kernel compared to stock. The same for TWRP. The real difference between this procedure and re-installing LOS15.1 is installing the kernel file. Resetting lockscreen settings (because your pins will not work) was always the case when restorong nandroid backup.
If you're on ext4 then just stay on it. Not worth doing it in your case

RayDeemer said:
Well, the most complicated flashing orgy so far...
Click to expand...
Click to collapse
It's not that complicated even if it looks like that. It's very detailed, step by step comparing to typical flashing instructions. I did this because I know that a lot of users from this forum have problems even with simple things. Like I said before: the only difference between this and reinstalling ROM with restoring /data partition is flashing boot.img. Not my fault that this treble TWRP formatting feature is broken and nandroid backups are breaking login when PIN is set.

matteo0026 said:
Why making another kernel for putting just 1 commit that fixes f2fs? Recovery was needed because for treble we are still using 3.2.2-0, but kernel is useless, @mikeioannina could merge that commit in official lineage kernel.
Click to expand...
Click to collapse
This will not gonna happen and that's why I compiled it myself. He reverted this change before it came live and I just readded it (https://github.com/LineageOS/androi...it/48c639c3581eb04693ae0771d8e85ce1151550b4).
You will probably find his post around page 50 of LOS thread about that.
He said that he will be not push this change to build since it will break LOS14 -> LOS15.1 transition when doing an OTA (user data will be corrupted if I remember correctly).
If you wondered why this tutorial is long and "complicated" like people said before then as you can see it turns out that data transition could be done with simply doing nandroid backup and then restoring it. These step are 90% of this tutorial due to bugs which are in lineage TWRP and "bugs" because that TWRP is backing up ROM with lockscreen settings which are breaking every time when restoring from backup. Also removing backup data step is necessary because these files will slow down encryption and will be not placed in /sdcard so people will forget about it probably and wonder what is eating so much space.
EDIT: I forgot to add that Mike refused my opinion about this but at the end you will still need to format your data anyway when going from 15.1 to 16. This kernel with TWRP may be solution for smooth transition to 16.

Kielbek said:
This will not gonna happen and that's why I compiled it myself. He reverted this change before it came live and I just readded it (https://github.com/LineageOS/androi...it/48c639c3581eb04693ae0771d8e85ce1151550b4).
You will probably find his post around page 50 of LOS thread about that.
He said that he will be not push this change to build since it will break LOS14 -> LOS15.1 transition when doing an OTA (user data will be corrupted if I remember correctly).
If you wondered why this tutorial is long and "complicated" like people said before then as you can see it turns out that data transition could be done with simply doing nandroid backup and then restoring it. These step are 90% of this tutorial due to bugs which are in lineage TWRP and "bugs" because that TWRP is backing up ROM with lockscreen settings which are breaking every time when restoring from backup. Also removing backup data step is necessary because these files will slow down encryption and will be not placed in /sdcard so people will forget about it probably and wonder what is eating so much space.
Click to expand...
Click to collapse
Ok, I understand. I think that some things in lineage wiki for p2 must be more clear. Starting from the guide for going from stock ROM to lineage 15.1...

matteo0026 said:
Ok, I understand. I think that some things in lineage wiki for p2 must be more clear. Starting from the guide for going from stock ROM to lineage 15.1...
Click to expand...
Click to collapse
Yeah, wiki instructions are a big mess. You actually need to perform most of steps I've written and described here if coming from another ROM (Steps 1 - 8) and you can do this few different ways
Maybe I will shorten this tutorial by fixing some aspects of TWRP and then request it to be included in the wiki so it will be easier for everyone.

Kielbek said:
Yeah, wiki instructions are a big mess. You actually need to perform most of steps I've written and described here if coming from another ROM (Steps 1 - 8) and you can do this few different ways
Maybe I will shorten this tutorial by fixing some aspects of TWRP and then request it to be included in the wiki so it will be easier for everyone.
Click to expand...
Click to collapse
Yes, for example for going from stock to los15.1 the right steps are:
- unlock bootloader and install official twrp 3.2.3-0
- (in case, do a backup)
- wipe system, data, cache and dalvik
- format data in ext4 (with official kernel, with yours I think it's not needed)
- install treble twrp
- wipe system, data, cache and dalvik another time
- install los15.1 (+ in case your kernel) + gapps and eventually addonsu or magisk
- reboot system

matteo0026 said:
Yes, for example for going from stock to los15.1 the right steps are:
- unlock bootloader and install official twrp 3.2.3-0
- (in case, do a backup)
- wipe system, data, cache and dalvik
- format data in ext4 (with official kernel, with yours I think it's not needed)
- install treble twrp
- wipe system, data, cache and dalvik another time
- install los15.1 (+ in case your kernel) + gapps and eventually addonsu or magisk
- reboot system
Click to expand...
Click to collapse
Yep, the only difference is that I suggest to use "fastboot boot recovery.img" with official twrp instead of flashing it directly to /recovery partition to prevent meaningless excessive data writing here. NAND will last for longer.

Kielbek said:
Yep, the only difference is that I suggest to use "fastboot boot recovery.img" with official twrp instead of flashing it directly to /recovery partition to prevent meaningless excessive data writing here. NAND will last for longer.
Click to expand...
Click to collapse
You are right, but I think NAND is not a problem, we are going to flash recovery maybe 10-20 times in all the device's life, no more

I am now on los15.1 with ext4 data partition which is encrypted. So can I direclty update recovery to this one or I need to do something else ?

Mrinmay Medhi said:
I am now on los15.1 with ext4 data partition which is encrypted. So can I direclty update recovery to this one or I need to do something else ?
Click to expand...
Click to collapse
Yes, of course you can directly update it. If you're on EXT4 it will work for you just fine like version from LOS wiki and maybe even better. Assuming to changelog this version fixes OTAs on encrypted devices. Only F2FS users need to reformat their data.

Hopefully when lineage os 16 released, treble twrp can format data properly, and decrypt/format/use right f2fs system...

mahmutpekkara said:
Hopefully when lineage os 16 released, treble twrp can format data properly, and decrypt/format/use right f2fs system...
Click to expand...
Click to collapse
There's no doubt that it will use newer F2FS version. Not sure about TWRP tho. Maybe I will look into it.

Kielbek said:
There's no doubt that it will use newer F2FS version. Not sure about TWRP tho. Maybe I will look into it.
Click to expand...
Click to collapse
Please do, we need one dedicated TWRP. Also thx again.:angel:

@Kielbek hi does it fix 1689mhz stuck speed bug?

Cuvillier said:
@Kielbek hi does it fix 1689mhz stuck speed bug?
Click to expand...
Click to collapse
What do you mean by this? I don't have such problems.

@Kielbek
How can we disable force encrypt from the kernel?

Need a little help understanding A/B partitions

I have a few questions I'm new to the a/b partitions thing I've read the page on a/b partitions. But I'm still in the mud.
1 I'm on Verizon bootloader unlocked twrp 3.2.3-23 and magisk installed I have 9.0.11 installed twrp and magisk in slot a/b
now is it necessary to backup stock rom? If I install lets say crDroid in slot A install twrp installer I know twrp goes into both slots reboot back to recovery making sure I'm still in A install gapps and magisk reboot back to recovery making sure again I'm still in A slot then reboot to crDriod that should work yes?
2 Now If I wanted to go back to my stock rom witch is in B slot can I not reboot back to twrp and switch to slot B and go to stock?
Thanks guys this A/B partition is still clear as mudd

Making a back up is always recommend, but it's up to the user to decide if the want to or not. The down side is loosing all your data, so there is that.
The short answer to your 2nd question is no you can not dual boot ROMs on this device. I posed the same question in a different thread and you can read the explanation from Dark Nightmare here.
https://forum.xda-developers.com/showpost.php?p=78375631&postcount=988
Sent from my ONEPLUS A6013 using Tapatalk

foamerman said:
I have a few questions I'm new to the a/b partitions thing I've read the page on a/b partitions. But I'm still in the mud.
1 I'm on Verizon bootloader unlocked twrp 3.2.3-23 and magisk installed I have 9.0.11 installed twrp and magisk in slot a/b
now is it necessary to backup stock rom? If I install lets say crDroid in slot A install twrp installer I know twrp goes into both slots reboot back to recovery making sure I'm still in A install gapps and magisk reboot back to recovery making sure again I'm still in A slot then reboot to crDriod that should work yes?
Click to expand...
Click to collapse
I'm new to A/B as well but have been flashing quite a bit. Maybe someone can correct me if I'm wrong. From what I've observed, ROMs are designed to flash to the slot you're not using and, on reboot, switch slots. TWRP zip installer is designed to install to both slots. Magisk and Gapps, however, install to the current slot. This means you should flash the ROM (which flashes to the non-active system and boot partitions and possibly others), flash the TWRP installer (which installs to both boot partitions, including the one that was just flashed). Then reboot back into recovery (which will be the other slot that the ROM was installed to), and then install all the other zips needed (i.e., Gapps, Magisk, etc...).
Switching A/B partitions in the TWRP reboot menu also triggers the partition switch after reboot, if needed. It doesn't seem to immediately switch before a reboot however, even though it gives that impression.
foamerman said:
2 Now If I wanted to go back to my stock rom witch is in B slot can I not reboot back to twrp and switch to slot B and go to stock?
Click to expand...
Click to collapse
The data partition, which contains user apps and system and user app data, is not slotted. Moving back and forth between slots that share a common ROM type and are close in version might not pose a problem. But A/B slotting wasn't designed for switching Roms back and forth. It was designed to try to ensure that there is always a valid bootable ROM without regard to use data (i.e., potentially, after a factory-reset). Don't expect to boot up an AOSP modded ROM using the data and apps from an OygenOS ROM. Do a backup of all partitions to be safe (with the exception of system and vendor since system_image and vendor_image give a bit-for-bit copy, instead of file-for-file copy). Copy the TWRP directory to a computer afterward, if possible. Make sure to wipe data if flashing a ROM of a different type, not just a different version (after flashing everything but before initial system boot).

phillymade said:
Making a back up is always recommend, but it's up to the user to decide if the want to or not. The down side is loosing all your data, so there is that.
The short answer to your 2nd question is no you can not dual boot ROMs on this device. I posed the same question in a different thread and you can read the explanation from Dark Nightmare here.
https://forum.xda-developers.com/showpost.php?p=78375631&postcount=988
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Nsane457 said:
I'm new to A/B as well but have been flashing quite a bit. Maybe someone can correct me if I'm wrong. From what I've observed, ROMs are designed to flash to the slot you're not using and, on reboot, switch slots. TWRP zip installer is designed to install to both slots. Magisk and Gapps, however, install to the current slot. This means you should flash the ROM (which flashes to the non-active system and boot partitions and possibly others), flash the TWRP installer (which installs to both boot partitions, including the one that was just flashed). Then reboot back into recovery (which will be the other slot that the ROM was installed to), and then install all the other zips needed (i.e., Gapps, Magisk, etc...).
Switching A/B partitions in the TWRP reboot menu also triggers the partition switch after reboot, if needed. It doesn't seem to immediately switch before a reboot however, even though it gives that impression.
The data partition, which contains user apps and system and user app data, is not slotted. Moving back and forth between slots that share a common ROM type and are close in version might not pose a problem. But A/B slotting wasn't designed for switching Roms back and forth. It was designed to try to ensure that there is always a valid bootable ROM without regard to use data (i.e., potentially, after a factory-reset). Don't expect to boot up an AOSP modded ROM using the data and apps from an OygenOS ROM. Do a backup of all partitions to be safe (with the exception of system and vendor since system_image and vendor_image give a bit-for-bit copy, instead of file-for-file copy). Copy the TWRP directory to a computer afterward, if possible. Make sure to wipe data if flashing a ROM of a different type, not just a different version (after flashing everything but before initial system boot).
Click to expand...
Click to collapse
OK I understand what you both are saying my understanding is that data is still there in both slots yes? so If I want to go back to my 9.0.11 stock rom I should be able to just reboot to twrp and select slot B and go back to to stock yes? guys I'm sorry this is my first A/B partition phone I'm just trying to figure it out

foamerman said:
OK I understand what you both are saying my understanding is that data is still there in both slots yes?
Click to expand...
Click to collapse
As long as it isn't wiped, yes.
foamerman said:
so If I want to go back to my 9.0.11 stock rom I should be able to just reboot to twrp and select slot B and go back to to stock yes? guys I'm sorry this is my first A/B partition phone I'm just trying to figure it out
Click to expand...
Click to collapse
No. Except for the possible exception that both slots contain different versions of the same ROM, the data will work with one ROM but not the other.
When flashing a ROM in TWRP, just mke sure to make a nandroid backup first and follow the installation directions. If you have to switch back, you will need to flash the nandroid backup.
It is a pain and there are pitfalls. This phone is relatively new and this is the cost of flashing a custom ROM/bootloader.

No. Except for the possible exception that both slots contain different versions of the same ROM, the data will work with one ROM but not the other.
When flashing a ROM in TWRP, just mke sure to make a nandroid backup first and follow the installation directions. If you have to switch back, you will need to flash the nandroid backup.
It is a pain and there are pitfalls. This phone is relatively new and this is the cost of flashing a custom ROM/bootloader.[/QUOTE]
OK one more I think lol If I have 9.0.11 on my internal storage can I not go into slot A and wipe it and install it back on there and be OK?

foamerman said:
OK one more I think lol If I have 9.0.11 on my internal storage can I not go into slot A and wipe it and install it back on there and be OK?
Click to expand...
Click to collapse
Internal storage is an encrypted folder in the data partition that is wiped separately from data. As long as you don't wipe internal storage for any reason it should be ok, in theory. But it's not in practice.
Most of the problem with this phone is maintaining encryption back and forth between ROMs. Honestly, if you can't afford to lose data, don't try to flash ROM's yet. I have had very little luck flashing back and forth and, after reflashing data, being able to avoid a bootloop. TWRP has only supported encryption on this phone for a month or so and IMHO it's not ready for prime time. I have relied on Titanium Backup and moved it's backup folder back and forth between my phone and computer.

Nsane457 said:
Internal storage is an encrypted folder in the data partition that is wiped separately from data. As long as you don't wipe internal storage for any reason it should be ok, in theory. But it's not in practice.
Most of the problem with this phone is maintaining encryption back and forth between ROMs. Honestly, if you can't afford to lose data, don't try to flash ROM's yet. I have had very little luck flashing back and forth and, after reflashing data, being able to avoid a bootloop. TWRP has only supported encryption on this phone for a month or so and IMHO it's not ready for prime time. I have relied on Titanium Backup and moved it's backup folder back and forth between my phone and computer.
Click to expand...
Click to collapse
Well the mud is starting to clear up a little. Yea I've been a little leery about trying to install roms yet. I have read all the post in the Recovery thread mauronofrio is getting a 6t soon so maybe he can figure it out. But again Thank you.