How to install TWRP and custom rom? - OnePlus 6T Questions & Answers

Please give me instruction!
What I have done to there:
1. Unlocked bootloader
2. Boot TWRP .img file
3. Install recovery ram disk from the same .img file
4. Reboot to TWRP
5. Install TWRP installer .zip file
6. Reboot to TWRP
7. Wipe system, data, dalvik partitions
8. Flash Havoc and TWRP installer
9. Reboot to TWRP
10. PARTITIONS ENCRYPTED/UNABLE TO FLASH GAPPS
I'm using TWRP UNOFFICIAL BY MAURONOFRIO.
What to do now?
I'm tired! Give me instruction!

You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.

Maybe this thread will help.

dj_ooms said:
You need to install the latest stable OOS to both slots before you install the majority of custom ROMs. There are multiple threads with instructions stating that. You also have to format your userdata partition when moving from OOS to a custom ROM and vice versa. You would need to backup your data beforehand. Worst case, the phone won't boot when moving to a custom ROM, but it will probably boot but have encrypted data.
Click to expand...
Click to collapse
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION

ALYSKY said:
I flashed it on both slots and still ****ing encryption exists. **** phone. Nothing works. only encrypt and encrypt. PLEASE GIVE ME RIGHT INSTRUCTION
Click to expand...
Click to collapse
Its the third post (link) in the thread I linked to....

Related

Root for 8.0 Oreo

Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
It was released a few days ago, just go with custom or wait for working solution
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
No-verity didn't work for me but remove encryption.zip did.
this didn't work for me, it resulted in a bootloop
ric69 said:
1 workaround for now :
flash rom via odin /
flash twrp via odin /
flash no_encrypt 6.0, full wipe, reboot to recovery /
flash MoroKernel 1.5 (magisk already included) /
reboot and have fun with no encryptation anymore
Click to expand...
Click to collapse
fre78 said:
this didn't work for me, it resulted in a bootloop
Click to expand...
Click to collapse
Sorry for you. check Mount system or data or enable MTP. Internal storage was probably still at 0
I rebooted more than 10times it's ok here
zainbfaisal said:
Hello,
I have tried to root multiple times but everytime I flash TWRP and format Data and then restart the data partition keeps getting encrypted again, I am using the official 8.0 Oreo UK version which recently got released, I have tried installing Magisk and Xposed both are installed successfully but with error that /data is not mounted and like I said if I format data to decrypt it and then restart it automatically encrypts it. I also tried flashing Samsung anti root and no opt zips but it also didn't help.
Click to expand...
Click to collapse
sir may i ask how come ur able to have twrp .
how dd u install twrp on android 8.0 UK firmware?
thanks for help
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
OREO stock keeps encrypting DATA partition
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
NewbieFTW said:
Yes, I can confirm that I can do whatever I want on TWRP.
I used a .zip found somewhere on a 8.0 thread. I feel like the no-verity zip doesn't work on some devices as it didn't on mine.
Let me grab the link for you : https://drive.google.com/file/d/1tCLamw9j07bhRgEd6qhymqUxExazy04c/view?usp=sharing
Here you go, try this. It should work now. Try doing the exact same steps as you did before but with this zip instead of no-verity.
Good luck mate
Click to expand...
Click to collapse
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
skydivider said:
Can anyone confirm that magisk should be installed in twrp before encryption disabler?
Click to expand...
Click to collapse
Magisk removes the encryption disabler .zip for some reason.
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
zainbfaisal said:
Sounds good dosen´t work.
When you flash Magisk it flashes its own boot or system img and remove encrypt flashes its own, if you flash the magisk itll flash the img but if you then flash encryption disabler it will overwrite the magisk img and magisk will uninstall or if you flash the encrypt and then magisk then you will have magisk but encryption will be enabled.
Click to expand...
Click to collapse
I'm sorry then, I don't know what to say. It worked for me.
I needed reinstal magisk after boot for root, but worked for me...
fre78 said:
Hi NewbieFTW,
I've followed the steps you've described. (in step 3, I also did format the DATA partition because it was encrypted)
The result is that I'm on stock OREO and I can boot in TWRP.
But whatever I try, after booting OREO the first time, my DATA partition is encrypted again.
So, I have a TWRP as recovery, but only in READ ONLY mode, because it cannot mount an encrypted DATA partition.
This way, I cannot backup or restore my DATA partition.
Can you confirm that your TWRP is not READ ONLY?
And what encryption disabler did you use? (I used no-verity-opt-encrypt-6.0.zip)
Click to expand...
Click to collapse
When this happend to me, i hit format data and typed yes, when i mount on TWRP i can see my storage again
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
miguelan.ruiz said:
I can root with patched boot image, but Samsung Healt and Samsung Pay don't works. Anyone?
Click to expand...
Click to collapse
Samsung Pay will, at the moment, probably never work again because it trips Knox.
For Samsung Health the fix is still the same: install a build.prop editor and change the value of RO.Config.Tima from 1 to 0.
not for me
NewbieFTW said:
What I did :
1. Install official room through Odin
2. Do not reboot!!!!
3. Install TWRP through Odin
4. Install Magisk
5. Install Encryption Disabler
It worked for me
Click to expand...
Click to collapse
doesn't work for me
Apparently there are 2 kind of users here.
One part did manage to install stock Oreo (BTU? other CSC?) , with root (magisk? superSu?) and a working TWRP (3.2.1?) which is not read-only on our beloved S7 Edge (SM-G935F)
The other part did not manage to setup this particular config.
It would be nice to have a detailed step-by-step guide from scratch by someone who managed to do it, so we can reproduce it.

Instructions

Hey there great people out there!
Can somebody provide me the correct instructions for installing any Oreo ROM? It's not that I am lazy to search, believe me I have tried But problems came like Internal storage is not showing up on twrp(encrypted).Thanks a lot!BTW I'm on marshmallow right now,so please provide on how to update from marshmallow ?
Tech x 125 said:
Hey there great people out there!
Can somebody provide me the correct instructions for installing any Oreo ROM? It's not that I am lazy to search, believe me I have tried But problems came like Internal storage is not showing up on twrp(encrypted).Thanks a lot!BTW I'm on marshmallow right now,so please provide on how to update from marshmallow ?
Click to expand...
Click to collapse
You said you are on marshnallow.. Detailed step below.
1. Update to the latest nougat firmware using ota. Because lateat firmware is needed for oreo roms. Else you will face tons of bugs and problems.
2. Download recovery from same thread of the oreo rom you are using. Oreo roms need vendor partition, so it needs recovery that supports it.
Download the rom and gapps also.
5. Copy the rom, recovery image and gapps into the memory card. Boot into fastboot mode. Connect to pc. You can boot to fastboot by using command "adb reboot fastboot" without quotes.
4. Unlock the bootloader by connecting to pc via fastboot.(steps to unlock is given in the xda guide section or k6 power.)
5. Boot into twrp recovery image using fastboot. Your phone will reboot to recovery.
6. Using recovery install the recovery image from it by going to "install option" then selecting file type as image and selecting recovery image file.
7. Reboot recovery.
8. Format data to remove encryption. After that you can access internal storage. Wipe data, cache, dalvic cache, system, data and internal storage.
9. Flash the rom file. Flash the gapps.
10. Reboot to system from twrp.
If you can understand any steps above you can google. If you cant understand google, then forget about doing it. Because you will eventually break your phone. Give it to someone who knows in that case.
Lol I will not brick my device.I can get back to marshmallow anytime!The only problem I was having before was the device wouldn't show anything(0mb) on internal storage on booting in the ROM.Is this normal.Maybe the ROM is encrypted.On nougat this is not happening on any ROM.Currently Iam on nougat(stock).It shows internal storage only after formatting data but reinstalling the ROM and booting again in recovery it shows 0mb on internal storage.
Tech x 125 said:
sk.vyshak said:
You said you are on marshnallow.. Detailed step below.
1. Update to the latest nougat firmware using ota. Because lateat firmware is needed for oreo roms. Else you will face tons of bugs and problems.
2. Download recovery from same thread of the oreo rom you are using. Oreo roms need vendor partition, so it needs recovery that supports it.
Download the rom and gapps also.
5. Copy the rom, recovery image and gapps into the memory card. Boot into fastboot mode. Connect to pc. You can boot to fastboot by using command "adb reboot fastboot" without quotes.
4. Unlock the bootloader by connecting to pc via fastboot.(steps to unlock is given in the xda guide section or k6 power.)
5. Boot into twrp recovery image using fastboot. Your phone will reboot to recovery.
6. Using recovery install the recovery image from it by going to "install option" then selecting file type as image and selecting recovery image file.
7. Reboot recovery.
8. Format data to remove encryption. After that you can access internal storage. Wipe data, cache, dalvic cache, system, data and internal storage.
9. Flash the rom file. Flash the gapps.
10. Reboot to system from twrp.
If you can understand any steps above you can google. If you cant understand google, then forget about doing it. Because you will eventually break your phone. Give it to someone who knows in that caseencryptedThanks Man!
Lol I will not brick my device.I can get back to marshmallow anytime!The only problem I was having before was the device wouldn't show anything(0mb) on internal storage on booting in the ROM.Is this normal.Maybe the ROM is encrypted.On nougat this is not happening on any ROM.Currently Iam on nougat(stock).It shows internal storage only after formatting data but reinstalling the ROM and booting again in recovery it shows 0mb on internal storage.
Click to expand...
Click to collapse
Reinstalling the rom means it is again getting encrypted. By default encryption is on in stock rom. So you have to format data to break encryption. Otherwise you cant access internal storage. You need latest firmware (nov security patch) for oreo roms.
Click to expand...
Click to collapse
thanks
sk.vyshak said:
You said you are on marshnallow.. Detailed step below.
1. Update to the latest nougat firmware using ota. Because lateat firmware is needed for oreo roms. Else you will face tons of bugs and problems.
2. Download recovery from same thread of the oreo rom you are using. Oreo roms need vendor partition, so it needs recovery that supports it.
Download the rom and gapps also.
5. Copy the rom, recovery image and gapps into the memory card. Boot into fastboot mode. Connect to pc. You can boot to fastboot by using command "adb reboot fastboot" without quotes.
4. Unlock the bootloader by connecting to pc via fastboot.(steps to unlock is given in the xda guide section or k6 power.)
5. Boot into twrp recovery image using fastboot. Your phone will reboot to recovery.
6. Using recovery install the recovery image from it by going to "install option" then selecting file type as image and selecting recovery image file.
7. Reboot recovery.
8. Format data to remove encryption. After that you can access internal storage. Wipe data, cache, dalvic cache, system, data and internal storage.
9. Flash the rom file. Flash the gapps.
10. Reboot to system from twrp.
If you can understand any steps above you can google. If you cant understand google, then forget about doing it. Because you will eventually break your phone. Give it to someone who knows in that case.
Click to expand...
Click to collapse
thanks

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.

Actual custom rom flashing instructions ??

This is my first Oneplus device and I just realized that in this device, in order to flash Custom Roms, you need to have a OOS installed beforehand plus not wiping /System partition.
So I was wondering which one is the best and quickest way to do a clean and fresh install from scratch, with the less amount of stuff from previous roms since wiping /System will end up on a bootloop.
Would it be something like this:
Starting from fresh and clean OOS latest version:
-Wipe /Data /Cache /Internal
-Flash Rom + kernel (optional) + TWRP
-Reboot recovery
-Flash Gapps + Magisk.
-Reboot System.
Is this the cleanest way to do it ?
I've seen @Koogly 's video but I dont know if theres a better way to do it.
Thank you all.
dirtyl0lharry said:
This is my first Oneplus device and I just realized that in this device, in order to flash Custom Roms, you need to have a OOS installed beforehand plus not wiping /System partition.
So I was wondering which one is the best and quickest way to do a clean and fresh install from scratch, with the less amount of stuff from previous roms since wiping /System will end up on a bootloop.
Would it be something like this:
Starting from fresh and clean OOS latest version:
-Wipe /Data /Cache /Internal
-Flash Rom + kernel (optional) + TWRP
-Reboot recovery
-Flash Gapps + Magisk.
-Reboot System.
Is this the cleanest way to do it ?
I've seen @Koogly 's video but I dont know if theres a better way to do it.
Thank you all.
Click to expand...
Click to collapse
First time from oos zip
Flash latest stock rom oos
Flash twrp zip
Wipe data and cache
Reboot to recovery
Flash latest stock rom oos zip
Flash twrp zip
Wipe data and cache
Flash custom rom zip
Flash twrp zip
Flash gapps zip
Flash magisk zip if you want root
Reboot to system
If you are already on custom
Flash lastest stock oos zip
Wipe data and cache
Flash custom rom zip
Flash twrp zip
Flash gapps zip
Flash magisk zip if you want root
Reboot to system
If going from custom to oos
Back up all your internal storage pictures videos music etc
Wipe data internal storage and cache
Flash latest stock oos zip
Flash twrp zip if you still want to customize
Reboot to recovery
Flash latest stock oos zip
Flash twrp zip if you still want to customize
Flash magisk zip if you want root
Reboot to system
If you want a custom kernel on any of these methods I would recommend booting the rim first and going through setup process the rebooting back to to twrp after and flashing the kernel
Also you will want a USB c otg port bc after the first flash your data will be encoded. You can select the otg storage via twrp to make the process easier.
If you don't have an otg cable you will need to sideload each zip via cmd prompt with fastboot tools and sideload in twrp
After all flashes are complete and you boot the rom the encrypted data will no longer be encrypted on custom rom flashing if going back to stock oos rom you lose all internal data
Most ROMs threads have instructions in main thread and those should be followed first. Some ROMs may require some bits and pieces from original oxygen rom prior to custom install
Asoip for example
Is flashing oos necessary if we unlock bootloader?
I see instructions for lineage os dont mention flashing of oos bit they have the first step as unlocking the bootloader
mustafabakrolwala said:
Is flashing oos necessary if we unlock bootloader?
I see instructions for lineage os dont mention flashing of oos bit they have the first step as unlocking the bootloader
Click to expand...
Click to collapse
You flash oos first so you have the correct vender and up to date files etc before flashing. Some ROMs require you to flash old oos versions bc their rom was based on that oos vender

TWRP and Decrypt?

Hi.
I am new to the Nexus 6p.
I want to install Magisk and backup my ROM via TWRP.
I am running stock Oreo 8.1.0 with a password and fingerprint.
I have just unlocked and installed TWRP 3.3.3-1. When I first loaded TWRP it asked me to decrypt data, but I just cancelled it as I thought it wasn't needed. I take it this is wrong?
I have now tried to go back into twrp but I get the Android on its back saying 'no data'. So the twrp flash never stuck.
I am under some confusion whether I need to format userdata or not. The guides I am following are old and don't mention Oreo only Developer preview N. I would prefer not to but if it needs doing it needs doing.
Would removing my fingerprint before flashing twrp help?
Thanks.
Warren_Orange said:
Hi.
I am new to the Nexus 6p.
I want to install Magisk and backup my ROM via TWRP.
I am running stock Oreo 8.1.0 with a password and fingerprint.
I have just unlocked and installed TWRP 3.3.3-1. When I first loaded TWRP it asked me to decrypt data, but I just cancelled it as I thought it wasn't needed. I take it this is wrong?
I have now tried to go back into twrp but I get the Android on its back saying 'no data'. So the twrp flash never stuck.
I am under some confusion whether I need to format userdata or not. The guides I am following are old and don't mention Oreo only Developer preview N. I would prefer not to but if it needs doing it needs doing.
Would removing my fingerprint before flashing twrp help?
Thanks.
Click to expand...
Click to collapse
You need to boot back into twrp and format data the reboot back to recovery again and advanced wipe system data cache dalvik/art and internal storage if necessary, then flash a custom ROM .

Categories

Resources