Database Info

Need help flashing OOS 5.1.8 zip (via twrp!?) bear with me.

New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !

leondestiny said:
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
Click to expand...
Click to collapse
You need to make sure you are booting the slot you flashed the rom on, A or B.

sting5566 said:
You need to make sure you are booting the slot you flashed the rom on, A or B.
Click to expand...
Click to collapse
how do i do this? i only flashed zip from the root of my SD , there was no option to select either A or B :C
i went into advanced or seomthing and saw SLot a and B i tapped a and reboot sytem now it is stuck on twrp logo.
f** this ab ****.

When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot

OnePlus 6 has two partitions like the Pixel 2. For seamless OTA updates. In TWRP go to the Reboot menu and you'll see your currently active slot. It's either A or B. Switch to the other one and reboot. That should do it if you did flash the ROM.

Bradl79 said:
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
Click to expand...
Click to collapse
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.

leondestiny said:
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
Click to expand...
Click to collapse
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.

mikex8593 said:
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
Click to expand...
Click to collapse
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up

leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.

mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l

leondestiny said:
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
Click to expand...
Click to collapse
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.

mikex8593 said:
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
Click to expand...
Click to collapse
thx mate, so for next time if i were to flash some oos through twrp, i only need to wipe data/cache etc.
then flash the oos zip ? i dont think i had the option to select which Slot to flash it to, so i guess i just have to reboot to the slot that it has it flashed on..?
and also flashing procedure must be like Rom then twrp then reboot twrp then flash magisk yes?

leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.

chrcol said:
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
Click to expand...
Click to collapse
Fastboot boot recovery. Img
Flash oos full ROM zip
Flash recovery. Zip
Reboot recovery
Flash oos full ROM zip AGAIN
flash twrp. Zip AGAIN
Reboot recovery
Flash magisk if you want root.
Make sure your using the correct twrp aswell. I recommend bluespark v86

chrcol said:
And people say its easy.
Click to expand...
Click to collapse
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.

leondestiny said:
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
Click to expand...
Click to collapse
If you're installing havoc os, make sure you're using latest bluespark TWRP first. Reboot recovery, flash oos, flash TWRP, reboot recovery, flash havoc gapps and magisk then reboot. The only difference in a/b partition is that there's a few extra steps in the flashing process. You don't have to flash to both slots to have havoc, but you also shouldn't be manually changing the slot in TWRP to try to boot a specific slot unless you know what you're doing.

How to Flash Recovery on Brand New J7 NXT (Android 8.1) ?

Hi I just got this hh yesterday and it's already android 8.1 oreo. How to flash costum recovery TWRP?

Flash this one first, but only the recovery, not the boot part. https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
After that, boot into TWRP, and select to use an image, flash this one choosing 'recovery' image https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Note that in order to install some things, supersu or magisk most importantly, but anything that goes on the /data partition, you must explicitly format the data partition, then flash what you want, then reboot. This will factory reset the phone with the exception of what you just flashed. Once you've rebooted, there aren't any TWRPs that can decrypt the data partition so you won't be able to flash anything else or back up /data. It will get you rooted and if you have magisk then you can get xposed from within the magisk manager app.
Good luck.

PantsDownJedi said:
Flash this one first, but only the recovery, not the boot part. https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
After that, boot into TWRP, and select to use an image, flash this one choosing 'recovery' image https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Note that in order to install some things, supersu or magisk most importantly, but anything that goes on the /data partition, you must explicitly format the data partition, then flash what you want, then reboot. This will factory reset the phone with the exception of what you just flashed. Once you've rebooted, there aren't any TWRPs that can decrypt the data partition so you won't be able to flash anything else or back up /data. It will get you rooted and if you have magisk then you can get xposed from within the magisk manager app.
Good luck.
Click to expand...
Click to collapse
So, it is just 1 time TWRP and it will factory reset my phone?

eBuzz_Recon said:
So, it is just 1 time TWRP and it will factory reset my phone?
Click to expand...
Click to collapse
Yes, pretty much.
You have to format the data partition from TWRP in order to have it in a state where TWRP can read or write to it as it isn't yet encrypted. Doing that is a factory reset. After you boot again, the ROM will encrypt the data partition, so unless someone builds a TWRP that can read the encrypted partition in this Oreo build, it will be like that.
Until there's a new build of TWRP, you need to do that format of data to install something from TWRP. You can try installing magisk and let it fail, it might patch the kernel, before failing, and then let you install the magisk manager separately but probably not. Perhaps if you go to that thread and explain, someone can clarify and there might be something you can remove from the magisk install script if it fails when data can't be mounted, so that the kernel will still be patched to accept root. As for xposed, you can install it from magisk manager and most other stuff can be done from the phone while its running.

PantsDownJedi said:
Yes, pretty much.
You have to format the data partition from TWRP in order to have it in a state where TWRP can read or write to it as it isn't yet encrypted. Doing that is a factory reset. After you boot again, the ROM will encrypt the data partition, so unless someone builds a TWRP that can read the encrypted partition in this Oreo build, it will be like that.
Until there's a new build of TWRP, you need to do that format of data to install something from TWRP. You can try installing magisk and let it fail, it might patch the kernel, before failing, and then let you install the magisk manager separately but probably not. Perhaps if you go to that thread and explain, someone can clarify and there might be something you can remove from the magisk install script if it fails when data can't be mounted, so that the kernel will still be patched to accept root. As for xposed, you can install it from magisk manager and most other stuff can be done from the phone while its running.
Click to expand...
Click to collapse
I don't understand the part of kernel patching. Why would I need to patch the kernel? Is there any chance for fail when I try flashing magisk?
Sorry for my noobinity.

eBuzz_Recon said:
I don't understand the part of kernel patching. Why would I need to patch the kernel? Is there any chance for fail when I try flashing magisk?
Sorry for my noobinity.
Click to expand...
Click to collapse
The magisk and supersu scripts do that automatically. As for why, I don't remember, but there's information on it here most likely
https://forum.xda-developers.com/an.../test-disable-defex-security-samsung-t3851487
It has to do with the implementation of security features that Samsung includes. Remember that rooting is in itself an exploit. Those features see something with elevated permissions and are programmed to believe that it isn't meant to be there.
As for failure, you can always reflash the whole ROM with Odin if it doesn't go well, and if that doesn't work, then yes you have a real problem at that point. The link I just put above is perhaps a place to ask which could have better information.

[GUIDE] The correct way to flash custom ROMs

Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices. For bypassing Decryption Issues, adb sideload the .zip files.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
[This is known as a dirty flash]
To update the custom ROM or fix a error (Bootloop after successful first boot, No Service, etc.)
I am assuming you used my guide to flash the custom ROM
These are basically the same steps but without wiping or formatting data
Turn off Lockscreen Security
Reboot to Recovery
Flash the ROM (has to be the same ROM, updated is recommended, older versions may cause issues) and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
LINKS:
Official GApps Website - GApps Github
Official TWRP Website - TWRP Github
Magisk Forum - Magisk Thread - Magisk Github
Official SuperSU Website - SuperSU Forum - SuperSU Thread - SuperSU Github
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy!

[Disabler-ONLY]
`This is basically the same guide just if you want to flash Zackptg5's "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers" or any other disabler which requires different steps.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Flash the Disabler, Magisk and then GApps
Reboot to System
Profit
Dirty Flash? You can't. Usually when using a Disabler you have to clean install your custom ROM.
To update use the method in the first post but for step number 5 Flash the Disabler, Magisk and then GApps

This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!

dpryor88 said:
This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!
Click to expand...
Click to collapse
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.

This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.

_Masked_ said:
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.
Click to expand...
Click to collapse
Why are you angry? Haha.
And you linked this from the op6t forums so I'm commenting on that phone. And that's how it's done on that phone. And it does matter which twrp you use for THAT phone because one doesn't decrypt correctly.
Copy and paste? No... And nano is always best if you read xda basically anywhere. Not that I said you HAVE to use nano anyway.. it was just in my steps. And that works for me with any/every ROM. So don't be so opposed to other suggestions. Your method is really weird and involves way too much use of a computer/fastboot. Kind of defeats the purpose of using twrp, don't you think?

Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:

raiderep said:
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:
Click to expand...
Click to collapse
Sorry for the late reply, but yes this is for bypassing TWRP Decryption issues.

_Masked_ said:
Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data (Wipe)
Flash ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Go to Advanced, ADB Sideload then sideload GApps, the Recovery Installer and Magisk
Reboot to System
Profit
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy
Click to expand...
Click to collapse
this step means need do with pc not by twrp

ayed78 said:
this step means need do with pc not by twrp
Click to expand...
Click to collapse
This is to bypass Decryption issues.

Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
I mean I could make a tool for flashing a custom ROM but I'm sure that there's a tool for that already.

bump. (ignore)

_Masked_ said:
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
Click to expand...
Click to collapse
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?

Krullendhaar said:
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?
Click to expand...
Click to collapse
Just follow the steps, in order.

Hi.
What if I want to flash a custom kernel on a clean Rom flash? When should I do it? Together with Magisk and Gapps?

What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.

Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.
Click to expand...
Click to collapse
Same here, I do not understand why I should flash a recovery img when twrp does seem to stay installed after flashing everything. Maybe the custom rom I use does include twrp ?

Custom rom means bugs, possible privacy leak and overall less polished. Developer that are working on them are fantastic but they are most of the time nowhere near as what offer the stock one.
What you need is to check adb, doesn't need root but you can still remove apps (even system one) and do more tweaks.
If needed, check how to patch boot image with magisk, it works on all phone and get you root.
With that, you're free to debloat your device.

Hey just one little question: is it ok to dirty flash with encrypted data folder ?

Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Click to expand...
Click to collapse
Me neither, is it safe to assume that the step can be left out if TWRP is already there and I use it to flash the ROM?
Santi3598 said:
Thank you for this guide.
Click to expand...
Click to collapse
+1

Reverting back to stable from open beta without pc

Hello, I am a noob and i would like to know how to revert back to stock oos stable from open beta without pc. I have installed twrp but i want to install stock recovery too. Thanks.

yorllin said:
Hello, I am a noob and i would like to know how to revert back to stock oos stable from open beta without pc. I have installed twrp but i want to install stock recovery too. Thanks.
Click to expand...
Click to collapse
If you have TWRP, flash the OOS Stable Zip + TWRP, reboot the recovery, and there flash only OOS.
You will have OOS Stable in both slots, and the second flash will replace the recovery with the one from OnePlus
You may have to Format Data at the middle of the operation (When you reboot the recovery before the second flash). If that's the case, you won't be able to do the second flash, because the OOS zip will be erased !

Totone56 said:
If you have TWRP, flash the OOS Stable Zip + TWRP, reboot the recovery, and there flash only OOS.
You will have OOS Stable in both slots, and the second flash will replace the recovery with the one from OnePlus
You may have to Format Data at the middle of the operation (When you reboot the recovery before the second flash). If that's the case, you won't be able to do the second flash, because the OOS zip will be erased !
Click to expand...
Click to collapse
then in case I have to format the data, I would need a PC necessarily?

yorllin said:
then in case I have to format the data, I would need a PC necessarily?
Click to expand...
Click to collapse
Not necessarily. If you just flash OOS Stable, and Format the Data after, you will have a perfectly working device, with OOS Stable and OnePlus stock recovery. The storage will just be totally empty (So no Zips left to flash anything else like TWRP or Magisk), but the phone will work, just like when you first bought it ! If you don't want to flash anything more than OOS, then yes just flash the ROM, Format Data, and reboot
A PC would be useful if you want to flash OOS a second time to fill the second slot. But even then, you could do without one :
- Flash OOS
- Format the Data
- Reboot, setup the phone, install apps, ect
- Download the OOS Stable zip that has been erased when you formatted from Chrome on your phone
- Do a "Local upgrade" from the Updater in the settings, and flash 9.0.5 again
- Now you have a totally stock OOS Stable phone, with 9.0.5 on A and B System slots, clean as a baby !
I did this exact procedure myself this moning after being stupid and messing with the encryption, and not having an USB cable near me to use a PC

Totone56 said:
Not necessarily. If you just flash OOS Stable, and Format the Data after, you will have a perfectly working device, with OOS Stable and OnePlus stock recovery. The storage will just be totally empty (So no Zips left to flash anything else like TWRP or Magisk), but the phone will work, just like when you first bought it ! If you don't want to flash anything more than OOS, then yes just flash the ROM, Format Data, and reboot
A PC would be useful if you want to flash OOS a second time to fill the second slot. But even then, you could do without one :
- Flash OOS
- Format the Data
- Reboot, setup the phone, install apps, ect
- Download the OOS Stable zip that has been erased when you formatted from Chrome on your phone
- Do a "Local upgrade" from the Updater in the settings, and flash 9.0.5 again
- Now you have a totally stock OOS Stable phone, with 9.0.5 on A and B System slots, clean as a baby !
I did this exact procedure myself this moning after being stupid and messing with the encryption, and not having an USB cable near me to use a PC
Click to expand...
Click to collapse
Bro if I only want install the stock recovery just have to flash the open beta oss?

yorllin said:
Bro if I only want install the stock recovery just have to flash the open beta oss?
Click to expand...
Click to collapse
Yes ! If you don't flash TWRP, it will replace it !

Totone56 said:
Yes ! If you don't flash TWRP, it will replace it !
Click to expand...
Click to collapse
Thanks I just want to be sure that not gonna brick my phone ?

Totone56 said:
Yes ! If you don't flash TWRP, it will replace it !
Click to expand...
Click to collapse
Bro last question, the local update metod works too?

Just install the rollback zip through the local update and reboot.
Nothing else is required
It'll wipe out your data though.

Update OOS 9.5.7 to 9.5.8 - Magisk Root

Hi fellas,
I'm running OOS 9.5.7 GM21AA and rooted using Magisk.
I got a notification for the 9.5.8 system update. I would like to upgrade the OS but would still like to keep root (and don't wanna restore my phone). However, I have still backed up to Google Drive, and also using the OnePlus Switch app and copied the back up to my PC.
My question is, what's the best way to go about updating the system without having it touch my data?
I know the system update will unroot the phone automatically, which I'm guessing is going to delete all my data (because my device is rooted). So is there a way I can UNROOT separately so I don't lose my files and data, --> and then after that do the system update?
Can I download 9.5.8 from the web manually and install via TWRP for example, thus not messing with root and not losing data?
Thanks for your help in advance!

Follow this https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414

whatthekj said:
Follow this https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
Click to expand...
Click to collapse
Thanks for the quick reply.
Just to make sure, following those steps I shouldn't lose my data, correct?

omar0aziz said:
Thanks for the quick reply.
Just to make sure, following those steps I shouldn't lose my data, correct?
Click to expand...
Click to collapse
Correct. I didn't lose data when I did it awhile ago but I would still make a Google back up just in case of any errors

whatthekj said:
Correct. I didn't lose data when I did it awhile ago but I would still make a Google back up just in case of any errors
Click to expand...
Click to collapse
Awesome, thanks again! :good:

See here, as the exact question has already been asked and answered: https://forum.xda-developers.com/oneplus-7-pro/help/how-properly-update-t3942735
I know you did already got an answer, but there is additional info on the other thread.
In particular, I would reiterate would I posted about data retention when updating:
Yes, it should retain your data. I just updated to 9.5.8 a few days ago, and it kept my data intact (by the process of updating in settings, don't reboot, in Magisk Manager install TWRP installer in inactive slot, etc.).
But what I always say when attempting a "dirty flash" (flashing the ROM, but retaining data) is: hope for the best, prepare for the worst. Backup anything that is important to you before any big update, just in case. What should happen, and what actually happens, are not always the same thing!

@omar0aziz, no, losing root does NOT mean you lose your data. (This is not to be confused with locking or unblocking the bootloader, which will inevitably lose your data.) If you lose root, simply flash Magisk again.
The best way to update? I recommend taking full manual control of the update process. Use TWRP to update your ROM (that includes stock OOS) when you want to, and when you need to fix stuff.
- Flash ROM
If you are on slot A and flash a ROM, it goes to slot B.
- Flash TWRP installer zip
Keeps TWRP on both slots, patches boot.img
- Reboot to TWRP, not system
- Flash ROM again
This installs the ROM to the other slot, so now both slots are updated
- Flash TWRP installer zip again
Keeps TWRP on both slots, patches boot.img
- Flash Magisk
Patches the TWRP-patched ROM, allowing it to boot.
- Wipe dalvik
You can wipe data and dalvik instead for a clean flash
- Now reboot to system
(Keep in mind that in most custom ROMs, you will need to do an initial setup of the ROM, then reboot to recovery and flash Magisk again to get root.)
Consider flashing BOTH slots (A and B) whenever you update OOS, for two reasons. First, you don't have to keep track of which slot has which version of OOS should you flash a custom ROM or kernel with a specific version of OOS required as a base. The second reason is more compelling: the way the data partition changes encryption every update has nearly obviated the reason for A/B slots, in that if newly updated B changes data encryption upon boot and then something happens, you cannot revert to A because A can't read the new data encryption. So the solution is to update both A and B at the same time so both slots use the same encryption and can both access the data partition.
Or like me, run the device decrypted (i. e. without forced encryption).
Good luck!