Some background: I'm coming from an OP3 which did not have this Slot A/B thing and you could easily just flash firmware going forward. I'm currently confused as to how custom roms will update firmware and such going forward.
I noticed there's 'systemless' roms now (like NoLimits), I don't really understand what the advantages/disadvantages vs something like Havoc OS are.
If I go with a custom rom, will I need to flash to OOS to update firmware then reflash back to the custom rom in the future?
I apologize if these are really newb questions, trying to find specific details with some of these keywords makes it really hard to find relevant information (and I've tried).
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Link above is some info on A/B partitioning.
The benefit of systemless ROMs are that they are just Magisk Modules so installing and uninstalling is very easy. You don't need to boot into recovery or wipe anything.
Havoc is a full ROM and based on AOSP so wiping is needed, especially when security patches are different. Some people are decrypting their phones with the no verity zip but I won't say too much about that to keep things as simple as possible.
You don't need to flash any OOS firmware when on Havoc, and I think it's because custom ROMs have their own vendor image. More advanced users feel free to correct me if I'm wrong about this.
Flashing isn't really too different and I personally don't even think about A/B slots. You just need to remember to flash the TWRP zip file after a ROM flash to keep TWRP. And you also need to reboot back into recovery to install Google apps, rather than just after the ROM flash.
Custom kernels are now flashed last (after TWRP and Magisk).
This is how I've done it and have been issue-free.
Related
Hi there, can someone enlighten me how yo flash custom roms?my device already unlocked bootloader and i know how to flash cuz i play with xiaomi mi5, sams galaxy3 , sony x8.
For now i dont have a twrp. Im going twrp by fastboot before this.
Im really sure that i already go through all of the post. But seems from OB10 is really complicated.
1.ready fastboot twrp, bluspark twrp,roms, gapps and magisk( if necessary) and custom kernel
2.fastboot twrp by cmd or else
3.wipe what here? Or just factory reset and leave internal storage?
*Here i confused, do i need to wipe for both slot. Im still new to a/b partition. And do i need to do that for both slot to flash as steps 4-10 as below?
4.flash roms then bluspark twrp
5.reboot to recovery
6.flash gapps,magisk? Then twrp back?
7.reboot to twrp
8.flash custom kernel then twrp again?
9.reboot system
10. End right?
Please help me here. I cant find the real and proper steps. The only way i found is from OB7 to custom roms as they share same security patch.
Thanks for any help.
1. Flash any strock rom.zip partition A.
2. After that recovery.zip
3. Reboot back to recovery
4. Confirm you are in another slot B
5. Flash stock rom.zip. Which slot first is not important.
6. After that flash recovery.zip and then reboot.
After that you can install whatever you want.
That what I do if im switching roms and trying new stuff.
Working everytime.
Until OB7 and stable 9.0.2 I used fasboot roms, flashed via AIO tool, but new fastboot roms working different and I got laggy video and audio.
Okeh thats clear for both slot. But for OB10 to any customs rom is it needed to flash OB7?
What do you mean by stock rom?bete rom or stable rom?
slayerliar said:
Okeh thats clear for both slot. But for OB10 to any customs rom is it needed to flash OB7?
What do you mean by stock rom?bete rom or stable rom?
Click to expand...
Click to collapse
Stock any offical rom for OP6
9.0.2 or 9.0.3 or any OB3,4,5,6,7,8,9,10
If you want custom rom, look instructions, there is mentioned what is base rom. That you need flash.
If there is custom rom based OB7 then you need flash OB7(probably working lower builds also)
Thank brotha. I think they need to state which firmware do we need to start from. Otherwise it will be like me that confusing as they will patch up more and more security.
slayerliar said:
Thank brotha. I think they need to state which firmware do we need to start from. Otherwise it will be like me that confusing as they will patch up more and more security.
Click to expand...
Click to collapse
Pie ROM, pie firmware. (Except pre release betas)
Oreo ROM, Oreo firmware.
ROM - always flash latest firmware of the OS you want pie or Oreo (I always go for latest and don't have any issues . Tho I'm back to oos ,debloated now.)
Twrp - Always after ROMs, before roboot.
Gapps - after twrp and reboot, to make sure it installs to the right slot, that's why you install twrp and then reboot.. this will change your slot from A to B or from B to A. Manual switch is never necessary
Flashing gapps flashes to the slot you are in right now, so flashing before the first reboot (after twrp flash) Will get it to the wrong slot.
Magisk - if you want root. After all.
After all this you can, if you want, flash decrypt ..if you don't need your device to be encrypted,this Will give you more to think of tho.. let's just not go into this now.
i understand the process, but get confused at which file to specifically flash twice when they say
"latest firmware of the OS". So lets say the custom ROM i want to flash needs a PIE firmware 9.0.2 or higher,
what file am i supposed to flash?
9.0.2-PIE-OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9-FASTBOOT.zip
or
OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip
Hey OP6 users
i thought of something. that might have been obvious for some people but maybe not for everyone.
when doing a clean flash for a custom ROM it is often needed that we flash a required base. Either OOS stable or a OOS beta version.. which ever is needed by the custom ROM.
we don't need to flash the base again when we're just updating the custom ROM (unless the custom ROM needs a newer version of the base
knowing that, is it still needed to flash the base when changing to a custom ROM that needs the exact same base?
correct me if I'm wrong, but it would save some time for us to not have to flash the same required base for another custom ROM which needs the same one we previously flashed.
it would save: two OOS + TWRP flashes every time and two TWRP reboots, which would be pretty nice?
it would also be nice to save that time if we just wanted to re flash the current ROM I/you/we were using for any reason.
then a clean flash of a current custom ROM in use or changing to another ROM with the requirement of the same base would just be as simple/fast as
Format Data !!!!(optiona)!!!!
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash Custom ROM + TWRP.zip
Reboot TWRP
Flash GApps.zip + Magisk
Reboot System
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
How much time do you think you are wasting out of your life when you have to flash a base file (give me seconds and % of HP)? ROFL...?
If I am flashing a new ROM, usually I clean flash, test the ROM... IF I LIKE --> clean flash again, and set it up proper.
Feels good coming fresh out of the box, knowing everything is working optimized.
Anways, with xXx.NoLimits and how smooth OOS is, personally I don't really see any point on flashing custom ROMs anyways anymore.
castrum_doloris said:
In general you don't have to flash the base ROM again to change your custom ROM. Even if one base is 9.0.3 and the other is 9.0.4 it is normally not necessary. The base Rom is foremost used for it's vendor (and other partitions) which are not touched by Custom Roms.
But you have to pay attention to your security patch level before you switch between ROMs.
And of course (strongly recommended) to wipe cache, data and system before switching to another ROM (a complete format is only needed uf you are rolling back to an earlier security patch level)
At least this is my experience and (little) knowledge about how android etc works.
Allthough, If you run into problems, rebasing your phone is always a good option. Helped me out a few times.
Click to expand...
Click to collapse
Aight yeah it thougt so. Ofc I wipe data before flashing a new rom. But thanks for your input/confirmation feels good to have other opinions and experiences then there's also the fact you also have to wait until your rom supports the new base, so u don't flash a new base then switch to your custom Rom and stuff won't work correctly hehe
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
kewinhw said:
@castrum_doloris
or anyone else here on the forum
now that our oneplus 6 got an official update i want to ask something. is this okey/safe to do
currently having omnirom installed in both slots and to update base could this work? or will it give problems
1 have custom rom installed with 9.0.4 base
2 flash oxygenos (9.0.5) x2
3 flash custom rom x2
4 reboot twrp
5 flash gapps + magisk
6 reboot system
if i flash oxygenos over omnirom just to update the base and never reboot system to oxygenos will this still give me problems with data? or is it a safe way to update the base ? or is the only way to go to do factory reset?
Click to expand...
Click to collapse
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
castrum_doloris said:
Don't do it.
First, it is unneccessary (and useless) and second the security patch of 9.0.5 is too old compared to omni. Even if you don't boot into OOS System your whole storage won't get decrypted anymore (so you have to format your complete internal storage)
You have to get away a bit from this thought of the "Rom base". If you install a custom rom, you install a completely new system. The need of installing OOS "as a base" is mainly the vendor (and some other) partitions. And as long as these don't get updated/changed, your exact "base rom" is irrelevant.
9.0.5 doesn't have any significant changes. And these few changes are only relevant for the system itself (which would get deleted by installing a custom rom)
Click to expand...
Click to collapse
okey I'm using the disable dm-verity, forceencrypt script btw. but okey i see now hehe. thanks for your answer
It looks like the OP8T OOS recovery doesn't really exist. About the only things it will do is wipe data or reboot to fastboot or system. No sideload.
All of the android devices that I own I have rooted as well as installed new ROMS on them and they had at least a basic recovery. Why doesn't OP8T OOS have a recovery like most any basic android OS? I really don't understand especially since OP has been very user-oriented in dealing with it's fan base. It appears the LOS recovery has these basic features. I expect other ROMS built for OP8T have a working recovery. Is there something unusual about the OP8T?
zzjea said:
It looks like the OP8T OOS recovery doesn't really exist. About the only things it will do is wipe data or reboot to fastboot or system. No sideload.
All of the android devices that I own I have rooted as well as installed new ROMS on them and they had at least a basic recovery. Why doesn't OP8T OOS have a recovery like most any basic android OS? I really don't understand especially since OP has been very user-oriented in dealing with it's fan base. It appears the LOS recovery has these basic features. I expect other ROMS built for OP8T have a working recovery. Is there something unusual about the OP8T?
Click to expand...
Click to collapse
With the move to the A/B model, you now flash updates directly in the running system. So that functionality is no longer required in recovery. Which leaves just factory reset and fastboot as the two functions you can't do while the phone is still running.
Thanks. How do you install a new ROM then?
zzjea said:
Thanks. How do you install a new ROM then?
Click to expand...
Click to collapse
You use the custom ROM's recommended installation process.
You flash images, after unpacking them, with fastbootd.
So if you wanted to go back to OOS stock ROM from a custom ROM, you have to use the MSMtool? Did Android 10 or 11 or OOS change the partition structure for the OP8T? When and why did payload. bin become the container for the img files that used to be directly in the zip file? Is this all about the introduction of the seamless update and the a and b slots?
zzjea said:
So if you wanted to go back to OOS stock ROM from a custom ROM, you have to use the MSMtool? Did Android 10 or 11 or OOS change the partition structure for the OP8T? When and why did payload. bin become the container for the img files that used to be directly in the zip file? Is this all about the introduction of the seamless update and the a and b slots?
Click to expand...
Click to collapse
Have a read of this: https://source.android.com/devices/tech/ota/ab
Note that the OnePlus 8T uses this method - it even gets the updates from Google's servers.
noticed we've had some A12 roms for a little while now and for some reason now instead of flashing them, all of them seem to be sideloaded and using that roms custom recovery to sideload it instead of using something like twrp and normally flashing it. any reason this is the case with A12 roms? and is it possible to downgrade from an A12 rom back to OOS 11/10?
The reason for the sideloading is that there's no working version of TWRP for A12 that can decrypt the data partition, hence lineage created a custom recovery and I believe everyone else has copied it. As for the downgrading, you may be able to sideload a stock file, but I'd use the MSM tool to get back to OOS, although you should keep in mind you will need to unlock the bootloader once again.
I am still trying to fully wrap my head around Android moving to Slot partitions. I am reading as much as I can and feel I have a better understanding of it but have tried to flash lineageOS with microg but ended up with a bricked device maybe due to not doing the proper steps to switch to the active slot? My question is if I have TWRP installed and currently on OOS 11, can I just flash the zip file for lineage OS or so I need to do something additional? The TWRP script states you have to boot into Recovery to switch active slots and flash additional items. I know if I flash lineage I will end up with their Recovery as well which I obviously dont want. Can I flash the TWRP installer after flashing lineageOS zip or no? Please help confirm or deny what needs to be done given my current setup.
Thank you all in advance for any help/experiences you can share about this.