{"id":23499,"date":"2022-05-24T13:47:11","date_gmt":"2022-05-24T08:17:11","guid":{"rendered":"https:\/\/droidwin.com\/?p=23499"},"modified":"2022-05-24T13:47:11","modified_gmt":"2022-05-24T08:17:11","slug":"how-to-avoid-brick-while-flashing-custom-roms-a-b-partition","status":"publish","type":"post","link":"https:\/\/droidwin.com\/how-to-avoid-brick-while-flashing-custom-roms-a-b-partition\/","title":{"rendered":"How to Avoid Brick while Flashing Custom ROMs [A\/B Partition]"},"content":{"rendered":"

In this guide, we will show you the steps to avoid bricking your device while flashing custom ROMs in an A\/B Partition device. While the dual partition style has bought in quite a few under the hood goodies, it has also bought a few challenges for tech enthusiasts, especially when it comes to flashing custom binaries. Before flashing a custom ROM, it is always recommended to be on the latest stock firmware. While most users do verify it, but some only do so for the active slot [the slot to which they were currently booted].<\/p>\n

As a result, there could be a possibility of an older firmware in the inactive slot. This inconsistency between both the slots might not spell much trouble in the stock environment, but if you end up flashing a custom ROM, then a bricked device is usually on the cards. So to avoid this from happening, you will have to maintain the firmware consistencies across both the slots. And in this guide, we will show you how to do just that. Given here are the detailed steps to avoid bricking your device while flashing custom ROMs in A\/B Partition.<\/p>\n

\n

Table of Contents<\/p>\n