Hello,
I read about partition A/B, but I would like to have more insight some points are not really clear in my head.
My OP6T is rooted on partition B, everything works fine on this partition
On partition A, It automatically boot into recovery
How can I have a fresh install on both partition ?
Does I have to root both partition ?
You don't have to root both partitions, your second partition is probably blank, you can flash a rom to that partition or just let it be, its not a must have for a working device and generally when you root magisk inserts intself into both partitions.
Dark Nightmare said:
You don't have to root both partitions, your second partition is probably blank, you can flash a rom to that partition or just let it be, its not a must have for a working device and generally when you root magisk inserts intself into both partitions.
Click to expand...
Click to collapse
Ok, thank you for quick answer.
how do you flash a rom only on one partition ?
when you wipe in TWRP, does it wipe both or only one partition ?
I would like to have both partition at the same stage of update in case one get broken.
It is possible to make a copy of one partition to the other ?
Soujyu51 said:
Ok, thank you for quick answer.
how do you flash a rom only on one partition ?
when you wipe in TWRP, does it wipe both or only one partition ?
I would like to have both partition at the same stage of update in case one get broken.
It is possible to make a copy of one partition to the other ?
Click to expand...
Click to collapse
Well the whole point of two partitions is to have one in the previous state if an update breaks the current one...
You can flash one of the fastboot roms or full zips available in the general section, but you may have to modify the zip files to only flash to a single slot as the zips currently flash to both slots.
Dark Nightmare said:
Well the whole point of two partitions is to have one in the previous state if an update breaks the current one....
Click to expand...
Click to collapse
that's my point, I want to copy my partition B to my partition A, then modify one or the other, for a period they will be at the same state but this will rapidly change
Dark Nightmare said:
You can flash one of the fastboot roms or full zips available in the general section, but you may have to modify the zip files to only flash to a single slot as the zips currently flash to both slots.
Click to expand...
Click to collapse
is it possible to wipe everything and make a fresh install on both ?
Soujyu51 said:
is it possible to wipe everything and make a fresh install on both ?
Click to expand...
Click to collapse
use fastboot rom.
dieandromeda said:
use fastboot rom.
Click to expand...
Click to collapse
I will need a bit more information please xD
Soujyu51 said:
I will need a bit more information please xD
Click to expand...
Click to collapse
Only system / boot are concerned by the slot organization. Read general texts and tutorials about that and fastboot use. Everything needed is on the internet.
Striatum_bdr said:
Only system / boot are concerned by the slot organization. Read general texts and tutorials about that and fastboot use. Everything needed is on the internet.
Click to expand...
Click to collapse
Thank you very much that is a big help in my questionning
I followed this
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
and use this one flash-all.bat
it boot on both partition
Thank you
Thanks!
It solved my problems
Related
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
By default, you have to backup Boot, System and Data
Braakie said:
By default, you have to backup Boot, System and Data
Click to expand...
Click to collapse
and that will bring me back like i left off if i restore boot, system, and data?
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Krunk83 said:
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
Click to expand...
Click to collapse
Yes that would be true, you would have to disable any type of lockscreen security because it wont let you unlock your phone after restoring.
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Thats not even remotely a clean wipe and would cause nothing but issues.
I would highly recommend not doing that.
Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Noooooooo. When flashing a different ROM you need to clean flash (wipe system, data, cache, dalvik cache).
I have a pattern lock and fingerprints and restore my backup without any problems?
Braakie said:
I have a pattern lock and fingerprints and restore my backup without any problems?
Click to expand...
Click to collapse
Which partitions do you backup and restore?
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
TigerSoul925 said:
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
Click to expand...
Click to collapse
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
Heisenberg said:
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Click to expand...
Click to collapse
Oh so that's the reason! Well thanks, then I know what to do! I'll include the vendor partition then just for safety. I already have a complete backup of all partitions except recovery and cache too so I'll just keep that safe somewhere just in case.
Thanks for the replies!
Heisenberg said:
Which partitions do you backup and restore?
Click to expand...
Click to collapse
I backup/restore my boot, data and system partitions to data/media (SDCard)
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
survivor_evil said:
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
Click to expand...
Click to collapse
System.img is just that. An exact image copy of the system image in one chunk. So you would end up with IMG files. It's not necessary to choose the IMG options. Default options for boot, system and data is a complete backup.
I accidentally deleted the data partition. Everything else works fine including Recovery/Fastboot. Normally I'd be using the Mega Unbrick Guide to restore the partition, but not an option right now for the 5 (128GB). Assistance would be appreciated. Maybe flashing a userdata.img would work?
I'd recommend you to completely wipe and flash Stock OOS from here : https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
That should sort all your problems related to partitioning. Let me know how it goes.
anmolkakkar said:
I'd recommend you to completely wipe and flash Stock OOS from here : https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
That should sort all your problems related to partitioning. Let me know how it goes.
Click to expand...
Click to collapse
Already tried flashing the Full ROM earlier, but that doesn't fix the missing partition. Unless flashing with Stock Recovery would make a difference. Need a link to stock recovery to try that
Was looking into dumping partitions off a working OP5.
https://forum.xda-developers.com/showthread.php?t=2450045
Don't have a second OP5 (128GB) to dump partitions, but I did generate some .img files using this method. Optimally, flashing a proper userdata.img through fastboot should fix the partition, I believe.
aenews said:
I accidentally deleted the data partition. Everything else works fine including Recovery/Fastboot. Normally I'd be using the Mega Unbrick Guide to restore the partition, but not an option right now for the 5 (128GB). Assistance would be appreciated. Maybe flashing a userdata.img would work?
Click to expand...
Click to collapse
fastboot format userdata ?
Hastaloego said:
fastboot format userdata ?
Click to expand...
Click to collapse
The partition doesn't exist right now. It cannot be mounted or formatted. If someone could use the guide above and pull a userdata.img from a 128GB OP5, pretty sure that would restore the partition if I flash it in fastboot.
aenews said:
The partition doesn't exist right now. It cannot be mounted or formatted. If someone could use the guide above and pull a userdata.img from a 128GB OP5, pretty sure that would restore the partition if I flash it in fastboot.
Click to expand...
Click to collapse
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
You can also try restore the nandroid uploaded on my thread
Sent from Funk Tuned 3T
flame360 said:
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
Click to expand...
Click to collapse
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Funk Wizard said:
You can also try restore the nandroid uploaded on my thread
Sent from Funk Tuned 3T
Click to expand...
Click to collapse
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
aenews said:
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
Click to expand...
Click to collapse
Welcome buddy
Funk Wizard said:
Welcome buddy
Click to expand...
Click to collapse
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
electronicghandi said:
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
Click to expand...
Click to collapse
try flashing the stock zip from twrp.
electronicghandi said:
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
Click to expand...
Click to collapse
Restore the Nandroid
Sent from my OnePlus5 using XDA Labs
Worked for me to on a OnePlus 3
flame360 said:
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
Click to expand...
Click to collapse
That did it on my girlfriends OnePlus3 thank you very much!
aenews said:
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
Click to expand...
Click to collapse
Can you please share the userdata.img for 128gb and also fastboot image files for one plus 5t, my phone is dead please help
Dear All,
first of all i would like to say that i have had some samsung phone over the past years so i am not that new on how to install a custom ROM anyway lets get to the main issue....
i download the custom ROM
boot into download and install twrp with odin
open the phone and open twrp recovery and here is the problem i dont see the phone memory i see it 0
so i cant install any custom rom.... any help??
please advice
Thnx
Ibrahim
first of all give us a little details of the phone so we can help you like model and firmware currently on the phone.
Model SM-G935FD
Android Version 7.0
You need to FORMAT DATA, It's in wipe, put format data (IT WILL WIPE EVERYTHING), and woah, there will be the main memory.
ManXXXX said:
You need to FORMAT DATA, It's in wipe, put format data (IT WILL WIPE EVERYTHING), and woah, there will be the main memory.
Click to expand...
Click to collapse
Well thnx for the reply I will give this a try but I don't think it will work because when I install the twrp the data value becomes 0, quick question before I try this by wipe everything you mean the phone right not the sd card am I right?
ibrahimisadek said:
Well thnx for the reply I will give this a try but I don't think it will work because when I install the twrp the data value becomes 0, quick question before I try this by wipe everything you mean the phone right not the sd card am I right?
Click to expand...
Click to collapse
Yes ,internal memory. U don't see it becoz it's encrypted. After u format the data..the space become available again
gabytzubc said:
Yes ,internal memory. U don't see it becoz it's encrypted. After u format the data..the space become available again
Click to expand...
Click to collapse
Alright, so final question before I give it a try, the only thing that I click to format is the data right or should I choose something else with it?
ibrahimisadek said:
Alright, so final question before I give it a try, the only thing that I click to format is the data right or should I choose something else with it?
Click to expand...
Click to collapse
So.. u flashed twrp with Odin , reboot in twrp,after that format data,flash no verity encryption..then flash supersu or magisk
gabytzubc said:
So.. u flashed twrp with Odin , reboot in twrp,after that format data,flash no verity encryption..then flash supersu or magisk
Click to expand...
Click to collapse
What does this no verity encryption do?
thank you all this was very helpful
ibrahimisadek said:
What does this no verity encryption do?
Click to expand...
Click to collapse
Disable the encryption put in kernel by Samsung so u could boot twrp and other ROMs
So on the partitions our phone boots normally from partition A correct? When we flash new kernels/ROMs which partition gets flashed? And is there a way to switch between the two? Sorry for the questions I'm just trying to figure everything out before I jump into a new phone and rooting, unlocking and flashing.
majortaylor said:
So on the partitions our phone boots normally from partition A correct? When we flash new kernels/ROMs which partition gets flashed? And is there a way to switch between the two? Sorry for the questions I'm just trying to figure everything out before I jump into a new phone and rooting, unlocking and flashing.
Click to expand...
Click to collapse
When you do OTA updates partition is changed to other one..you can change partition in TWRP.. but remember it will have previous oxygenos version
So essentially were dual booting so to speak
majortaylor said:
So essentially were dual booting so to speak
Click to expand...
Click to collapse
Not really. There is only a single data partition, so if you try to have different OS on each slot then you will have problems because all of the data may not be compatible.
Sent from my crosshatch using XDA Labs
So when flash in twrp should I worry about with partition I'm flashing too? Or does it even matter?
majortaylor said:
So when flash in twrp should I worry about with partition I'm flashing too? Or does it even matter?
Click to expand...
Click to collapse
TWRP will flash/install to the "current" partition.
Do:
Code:
> adb shell
> getprop | grep slot
This will show what the current boot slot is "_a" or "_b".
In principle you could dual boot ... but there is only one data partition !!! So if might be that your data partition is not compatible with one of both.
I am using dual boot. Slot _a contains the original OTA 9.0.7; slot _b contains a debloated version with additions for pixel functionality. I use _b as daily driver, but if something goes wrong as a result of my patching on _b, I can quickly switch to _a and have a working phone.
The data partition is compatible in this case.
You can switch between _a or _b in TWRP.
So, if I have my stock ROM on slot A and want to flash Pixel Experience to Slot B, will data partition be compatible ?
Adiker said:
So, if I have my stock ROM on slot A and want to flash Pixel Experience to Slot B, will data partition be compatible ?
Click to expand...
Click to collapse
Nope.
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.