Is it possible to have a rooted version of stock Android on one slot and an unmodified version on the other?
I have s rooted version of Q installed on slot B. I tried using fastboot to flash system, boot and vendor to slot A but this didn't work.
Are there other images I need to flash to the A slot?
Is this even possible?
Are some of the images in the system image file shared between both slots?
ird0 said:
Is it possible to have a rooted version of stock Android on one slot and an unmodified version on the other?
I have s rooted version of Q installed on slot B. I tried using fastboot to flash system, boot and vendor to slot A but this didn't work.
Are there other images I need to flash to the A slot?
Is this even possible?
Are some of the images in the system image file shared between both slots?
Click to expand...
Click to collapse
The way I understand it, system is the only partition duplicated in a seamless update setup. Thus both A and B will have root.
Related
I unlocked the bootloader on my device previously. I hadn't rooted it yet, just haven't had the time. I'm ready to do so now, and i've read that you need to boot to this modified version of TWRP and use it to flash the TWRP image to the device, in doing so it flashes it to both the A/B partition of the device. I know you are always supposed to do good backups when you are doing these types of mods, BUT is it by functionality going to clear the device when it writes TWRP to both the A/B partition? When flashing TWRP to any other device that has never been the case. I just wondered if this works differently given the dual partition setup?
Afterwards I plan on using TWRP to flash magisk beta 14.3 to my pixel xl.
Thanks in advance.
Flashing TWRP will not wipe your dsevice.
Using the unofficial modified twrp is no longer necessary. Use twrp 3.1.1.1 img and 3.1.1.1 zip.
Hello guys,
I tried some stuff from the twrp thread and now I am curious how I can reflash the stock recovery?
Another question is the a/b slot system. I am currently on slot b with flashed stock image and root. If I use the OTA feature now, will the system set up on the slot a and after the next boot I am on slot a?
Best regards,
smoo62
I have a Pixel 2XL. It is rooted w/ Magisk and running RR Oreo ROM.
My Slot A does not work. I have tried to to install a ROM from TWRP and boot, but it goes into a boot loop. Slot B works fine. In TWRP, there is a re-partition or fix partitions button. Will that fix the problem? I've been rooting my phones for years, but I really only understand the basics. Is re-partitioning for Slot A/B, of for recovery/boot/vendor etc partitions?
Any other way to fix Slot A? Is there any problem other than OTA updates with not having 2 slots?
Any help would be greatly appreciated! I would really like it work.
TWRP won't fix this, and using the fix partitions option may do more harm than good. Flash a stock ROM (NOT an OTA image) using Fastboot and it should fix your A/B slot issue. From there you can go about setting up your device to use your chosen custom ROM.
My device forum doesn't have instructions how to do it, i've posted asking there but better to ask here also. I found this post for the Mi A2 that isn't my device mines the Mi A3 https://forum.xda-developers.com/mi-a2/how-to/guide-discussion-aio-gsi-thread-mi-a2-t3933356
The device is A/B arm64 has slots a and b i dunno how that effects flashing here, flashing custom roms will install into the inactive slot then you gotta change your active slot to be the the slot it installed into, then install rest of files there, does this apply with gsi .img files also?
When i tried using flashing the .img file i used orangefox recovery wiped all partitions flashed to system, just says no os installed i will probably try doing that again and flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip however who noes if that will help.
If someone can list the correct steps to flash using both fastboot method and twrp/orangefox recovery methods i would appreciate it. If it matters i was trying to flash android 10 gsi. I've seen many different methods listed depending on the device, so i guess that makes it harder to work out.
Thanks.
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
xVM said:
I've flashed it twice via TWRP with flashing DM-Verity & Forceencrypt Disabler and permissiver_v2.zip. Plus TWRP.
1st time it was into A slot. After 1st flashing I've restarted TWRP and booted into B slot. And then flashed slot B.
After rebooting and seeing Logo in 15 minutes - I've got Android.10
Click to expand...
Click to collapse
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Alister. said:
Thanks for the feedback, are you able to tell me the exact steps? like lets just say twrp is already installed and you factory reset, cleared all data.
Do you flash DM-Verity before you flash the rom? or after you flash the rom and what you just flash Forceencrypt Disabler and permissiver_v2.zip after installing the rom?
What i see with regular roms not gsi when you flash the rom if your on slot a it's actually installing it into slot b when you reboot that's where it is so you need to restart before flashing Magisk and other stuff. So i assume with the gsi maybe you need to reboot after installing as system image before flashing the other files?
Click to expand...
Click to collapse
Your better of using fastboot if flashing a gsi .img you dont need twrp really unless the rom is in a .zip format, or your wanting to add extras like magisk and such, or take a backup
Android 11
Did anyone tried Android 11 gsi??
Im using the ElementalX Kernel but its causing issues for my phone. I have it rooted with magisk too. how can i either go back to the stock kernel, or a different custom one?
Just download the factory image, unzip it, open the system.img and extract the stock boot.img
Then go into fastboot and flash the stock boot image to both slots and reboot.
This restores your stock kernel, and you're done if you just wanted to go back to stock. Now you can re-root it, and/or install another kernel.
You need to be stock before installing another kernel, so you have an untouched ramdisk.
id need to do it for the factory image i used for this one right? (in my case, the may 2020 image),
hey so, i wasnt sure what you meant by opening the system.img but i flashed the boot.img to both slots and rebooted to the slot i was originally using with bliss rom, and now it wont boot..