I have a Mi A3 it has the A/B partition system. As far as I understood (please correct me if I am wrong really new to the whole messing with mobiles stuff) both the partitions have different builds in them and the one which is active is the newer one
I was thinking if what I think is correct then is there a way to have like the stock rom on one and a custom one on the other??
Ofc updating the stock rom would remove the custom rom but is there any way to have this 2 os setup??
Related
Though everyone seems bz with antirolback or pie "Dual Boot Patcher" has officially supported whyred. Thanks to "chenxiaolong" (its completely his work)
here's official site https://dbp.noobdev.io/
downloads:
https://dbp.noobdev.io/downloads/
we have lots to talk about and there will be many success story to discuss . lets start.
those who dosen't know or new to this it actually uses other storage partitions to flash roms and there are many unique features like app data sharing on multiple roms , in app flashing roms etc.
welcome to the party .
process to flash
1. patch the rom.zip file with app or from windows for multi slot partition . e.g. rom-multi-slot-1.zip (not sure secondary works or not)
2. try add rom from in app (if its aroma you have to flash from twrp)
3. switch rom from menu
4. reboot
everything for better understanding is here https://forum.xda-developers.com/showthread.php?t=2447534
Last I knew even oreo wasn't supported on dbp.
Sent from my Redmi Note 5 Pro using Tapatalk
no Boot UI for whyred/Xiaomi Redmi Note 5? how to switch the rom without UI?
Boot UI
Supported: no
Click to expand...
Click to collapse
Hey i will unlock my device in the next days and actually have global stable rom with arp4. My idea was to unlock, boot twrp through adb, save stock rom and stock recovery, flash twrp, flash root, install dual boot patcher and test/install roms as second rom and leave stock rom as primary. My hope is that this way there is no risk of bricking my device. am i right? thank you
@ecrum you got dual boot patcher successful installed on whyred? Didn't test it till now but i am not sure if there could be problems because of ARP and a risk of bricking the device? Thank you
i know that i doesn't support Oreo
alfredxyz said:
@ecrum you got dual boot patcher successful installed on whyred? Didn't test it till now but i am not sure if there could be problems because of ARP and a risk of bricking the device? Thank you
Click to expand...
Click to collapse
still no update from dev's side. but no risking bricking either. for now it only see all the partitions and it can set the kernel for primary rom for pie. in case of oreo a non gsi rom perhaps Ressurection Remix could work. in case of dual pather the rom updater script must support DBP ...
things have to go long way for now. but its not bricking anything. test if you like but nonetheless you have taken a proper nand backup
Any news?
still not working?????
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
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.
Hi XDA please I have three worries that I need help. Please if someone can give answers chronologically, I will appreciate
1. My Device's architecture is 32 and A-only partition. But when I flash ARM, a-only custom roms through the right process, I end up in bootlooop. This happened when I flashed HavocOS-gsi-arm-a only-v4.5. instead a64 was successfully flashed (OctaviOS gsi). Why is this so?
2. I backed-up my ROM using OrangeFox Recovery inorder to flash a custom one. I went back to restore it. When it was restoring system partition, it failed with an error message talking about password. When I tapped on password, it took me to another section and said I can't add addons. That is it and I was unable to restore the backup. Why is this so?
3. My phone supports OTG. it was present in my phone. When I bricked my phone, I used a lower version to unbrick it (because I could not find the exact stock rom version currently installed on my phone). Now there's no OTG option anymore. I even later switched to a custom rom (OctaviOS) yet still no OTG option. Is it that the custom rom inherited the disease from the stock rom? Help
My Device
Tecno Spark 4 KC8, Android 10
A-only
Ramdisk: Yes
Architecture: armeabi v7 (32)
I'd like to have the stock rom and a custom rom on it.
Probably not because there is no a/b partitions. But if you can create it then I think the bootloader won't boot to it and there is no recovery which allows to choose between a/b slots