Database Develop

Network Signal Guru - Google Pixel 4 XL Questions & Answers

Do any of the kernels properly support NSG's unreasonable requirements?
Haven't been able to get it working on any Pixel phone for months. What changed?
Edit: Dev says it's not supported yet.

Would love to get this working on a 4 XL.

I had it working on Pixel 2, 3 XL, and 3a XL. I am told the Pixel 4 is missing (or their methods can't see) the MPSS, modem peripheral sub system. I don't know how to enable this.
Also missing is diag mode and the older methods from the Pixel 2 don't work on the Pixel 4 because the modified Magisk doesn't patch the boot image correctly.
It would be nice to see if a userdebug/eng rom worked a little better.
Things I have tried: copy all diag libs from Pixel 3 XL; remove most selinux denials when opening NSG; spoofing as Pixel 3 XL and OnePlus 7 Pro.

Updated instructions for Android 11
Old instructions:
Here are instructions to get NSG working. You need to download the newest and re-apply the "userdebug" vendor.img every month. These instructions are given with the assumption you know that this app requires root, an unlocked bootloader, and that you know how to recover your device in case of flashing failures by using the factory images.
Warning: DO NOT use "Clear Forcings" - it will currently cause you to lose LTE bands at reboot and airplane mode toggles.
1. Download the appropriate Vendor image from https://developers.google.com/android/drivers
To avoid confusion, copy the build number from the Factory Image tab and ctrl+F on the Driver Binaries tab. Make sure your correct device variant is chosen.
2. Extract the vendor.img (with Windows you can use 7-Zip, just keep opening until you get to extract-google_devices-coral.sh\extract-google_devices-coral\vendor\google_devices\coral\proprietary\, then extract the vendor.img)
3. Make sure your fastboot tools (ADB) is up to date: https://developer.android.com/studio/releases/platform-tools
4. If already rooted with stable Magisk, open Magisk Manager, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF. (Canary builds may not work.)
If OFF, skip to #13.
If ON, then uncheck Preserve AVB 2.0/dm-verity then press Install>Direct Install, reboot. Skip to #13.
5. If you are already rooted with Canary builds, or are having bootloop issues, remove -w flag from factory image bat/sh then re-flash factory image
6. Boot into OS, install latest stable Magisk APK
7. Open Magisk Manager, make sure Advanced Settings>Preserve AVB 2.0/dm-verity is OFF
8. Patch stock boot.img
9. adb reboot-bootloader
10. fastboot flash boot <magisk_patched.img>
11. Reboot
12. Open Magisk Manager, make sure dm-verity option is still off
13. Reboot to fastboot (adb reboot-fastboot) - you should see "fastbootd" in red at the top
14. Flash the vendor.img you extracted (fastboot flash vendor location/of/vendor.img)
15. When it's finished, reboot, then Clear App Data of Network Signal Guru and launch it again
16. If you cannot boot or get a corrupted boot message, start over at #5
If you encounter "Driver Not Working or Not Found" error in the future like after a reboot, close and reopen the app a couple times as needed, or clear app data as a last resort.
If you encounter an issue where LTE Band 71 does not activate after a reboot or after toggling airplane mode, then you need to dial *#*#4636#*#* go to Phone Information then turn on Enable DSDS then reboot.
As of April 2020 patch or Android 11 DP3, you might be able to see your device in QPST with these commands:
Code:
adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
change usb config (file transfer, no file transfer)
wait
qpst

cstark27 said:
@LLStarks @troyhough
Make sure your fastboot tools (ADB) is up to date: https://developer.android.com/studio/releases/platform-tools
Download the appropriate Vendor image from https://developers.google.com/android/drivers
Please note that these are in reverse order than the Factory Image tab. To avoid confusion, copy the build number from the Factory Image tab and ctrl+F on the Driver Binaries tab.
Extract the vendor.img (with Windows you can use 7-Zip, just keep opening until you get to extract-google_devices-coral.sh\extract-google_devices-coral\vendor\google_devices\coral\proprietary\, then extract the vendor.img)
Reboot to fastboot (adb reboot-fastboot)
While in fastboot, reboot to fastbootd (fastboot reboot-fastboot) - it will look like it's booting normally, just wait then you should see "fastbootd" in red at the top
Flash the vendor.img you extracted (fastboot flash vendor vendor.img)
When it's finished, reboot, then Clear App Data of Network Signal Guru and launch it again
If you encounter "Driver Not Working or Not Found" error in the future like after a reboot, clear the app data again.
Click to expand...
Click to collapse
---------
ohhhhhhhhh is the screenshot on the Pixel 4?

troyhough said:
---------
ohhhhhhhhh is the screenshot on the Pixel 4?
Click to expand...
Click to collapse
Yep, 4 XL
It seems on each reboot you will need to clear the app data, just FYI. And on successive launches of NSG, you will see some missing fields for 5-10 secs but if you start moving some data it should populate.

cstark27 said:
Yep, 4 XL
It seems on each reboot you will need to clear the app data, just FYI. And on successive launches of NSG, you will see some missing fields for 5-10 secs but if you start moving some data it should populate.
Click to expand...
Click to collapse
Sweet! My phone isn't rooted so hopefully you can tell me what the P4 XL is actually capable of! Is it capable of this:
FDD-TDD DL CA utilizing a 10 MHz B25 carrier as PCC for DL /UL with 20 MHz B41 aggregated on the downlink

troyhough said:
Sweet! My phone isn't rooted so hopefully you can tell me what the P4 XL is actually capable of! Is it capable of this:
FDD-TDD DL CA utilizing a 10 MHz B25 carrier as PCC for DL /UL with 20 MHz B41 aggregated on the downlink
Click to expand...
Click to collapse
Sorry I don't have any active Sprint sims.
But per the FCC filing, it should be able to.
PCC [B25 (20mhz)] + SCC [B41 (20mhz) + B41 (20mhz) + B41 (20mhz)]. It supports ULCA on B41. And it supports 4x4 MIMO on bands 2,4,66,25,30,41. But while CA with B41, you only get 4x4 on B25 not any B41. To get 4x4 MIMO on B41, it has to be CA of only B41.
Let me know if my interpretation of your question is wrong.

cstark27 said:
Sorry I don't have any active Sprint sims.
But per the FCC filing, it should be able to.
PCC [B25 (20mhz)] + SCC [B41 (20mhz) + B41 (20mhz) + B41 (20mhz)]. It supports ULCA on B41. And it supports 4x4 MIMO on bands 2,4,66,25,30,41. But while CA with B41, you only get 4x4 on B25 not any B41. To get 4x4 MIMO on B41, it has to be CA of only B41.
Let me know if my interpretation of your question is wrong.
Click to expand...
Click to collapse
Im not into the technical verbiage, just would like to know if the 4 XL is capable of doing what the S9, S10, Note 10, etc can do on Sprint!
You can see below what the S9 is doing. You may have to read a little bit more of the thread to get all the info:
https://s4gru.com/forums/topic/6319...cussion-thread/?do=findComment&comment=549028

cstark27 said:
@LLStarks @troyhough
Make sure your fastboot tools (ADB) is up to date: https://developer.android.com/studio/releases/platform-tools
Download the appropriate Vendor image from https://developers.google.com/android/drivers
To avoid confusion, copy the build number from the Factory Image tab and ctrl+F on the Driver Binaries tab.
Extract the vendor.img (with Windows you can use 7-Zip, just keep opening until you get to extract-google_devices-coral.sh\extract-google_devices-coral\vendor\google_devices\coral\proprietary\, then extract the vendor.img)
Reboot to fastboot (adb reboot-fastboot)
While in fastboot, reboot to fastbootd (fastboot reboot-fastboot) - it will look like it's booting normally, just wait then you should see "fastbootd" in red at the top
Flash the vendor.img you extracted (fastboot flash vendor vendor.img)
When it's finished, reboot, then Clear App Data of Network Signal Guru and launch it again
If you encounter "Driver Not Working or Not Found" error in the future like after a reboot, close and reopen the app clear the app data again.
Click to expand...
Click to collapse
EDIT2: I got it working, but it seems to have an issue when DSDS is active, it jumps back and forth between the data from each SIM card.
Here is a screen recording of what I am talking about:
https://filebin.net/ddim8468plxx6otp/2020_01_07_22_10_35.mp4?t=82gimnzv

troyhough said:
Im not into the technical verbiage, just would like to know if the 4 XL is capable of doing what the S9, S10, Note 10, etc can do on Sprint!
You can see below what the S9 is doing. You may have to read a little bit more of the thread to get all the info:
https://s4gru.com/forums/topic/6319...cussion-thread/?do=findComment&comment=549028
Click to expand...
Click to collapse
Technically, it can support such combos. But again, I can't confirm that it does it out of the box since I don't have an active Sprint sim.
ryaniskira said:
EDIT2: I got it working, but it seems to have an issue when DSDS is active, it jumps back and forth between the data from each SIM card.
Here is a screen recording of what I am talking about:
https://filebin.net/ddim8468plxx6otp/2020_01_07_22_10_35.mp4?t=82gimnzv
Click to expand...
Click to collapse
You might reach out to the developers and see if they can help you out. I only use a single sim.

cstark27 said:
Technically, it can support such combos. But again, I can't confirm that it does it out of the box since I don't have an active Sprint sim.
You might reach out to the developers and see if they can help you out. I only use a single sim.
Click to expand...
Click to collapse
It was actually the devs who told me about this thread in an email. I did reply back to them with the issue though.

[/COLOR]
cstark27 said:
Make sure your fastboot tools (ADB) is up to date: https://developer.android.com/studio/releases/platform-tools
Download the appropriate Vendor image from https://developers.google.com/android/drivers
To avoid confusion, copy the build number from the Factory Image tab and ctrl+F on the Driver Binaries tab.
Extract the vendor.img (with Windows you can use 7-Zip, just keep opening until you get to extract-google_devices-coral.sh\extract-google_devices-coral\vendor\google_devices\coral\proprietary\, then extract the vendor.img)
Reboot to bootloader (adb reboot-bootloader)
While in bootloader, reboot to fastbootd (fastboot reboot-fastboot) - it will look like it's booting normally, just wait then you should see "fastbootd" in red at the top
Flash the vendor.img you extracted (fastboot flash vendor vendor.img)
When it's finished, reboot, then Clear App Data of Network Signal Guru and launch it again
If you encounter "Driver Not Working or Not Found" error in the future like after a reboot, close and reopen the app clear the app data again.
Click to expand...
Click to collapse
I followed your steps, I got "failed (remote: command not available on locked devices)" after I entered "fastboot flash vendor vendor.img"

bigJbig said:
[/COLOR]
I followed your steps, I got "failed (remote: command not available on locked devices)" after I entered "fastboot flash vendor vendor.img"
Click to expand...
Click to collapse
You need an unlocked bootloader. That step is assumed since this app requires root

cstark27 said:
Make sure your fastboot tools (ADB) is up to date: https://developer.android.com/studio/releases/platform-tools
Download the appropriate Vendor image from https://developers.google.com/android/drivers
To avoid confusion, copy the build number from the Factory Image tab and ctrl+F on the Driver Binaries tab.
Extract the vendor.img (with Windows you can use 7-Zip, just keep opening until you get to extract-google_devices-coral.sh\extract-google_devices-coral\vendor\google_devices\coral\proprietary\, then extract the vendor.img)
Reboot to bootloader (adb reboot-bootloader)
While in bootloader, reboot to fastbootd (fastboot reboot-fastboot) - it will look like it's booting normally, just wait then you should see "fastbootd" in red at the top
Flash the vendor.img you extracted (fastboot flash vendor vendor.img)
When it's finished, reboot, then Clear App Data of Network Signal Guru and launch it again
If you encounter "Driver Not Working or Not Found" error in the future like after a reboot, close and reopen the app clear the app data again.
Click to expand...
Click to collapse
cstark27 said:
You need an unlocked bootloader. That step is assumed since this app requires root
Click to expand...
Click to collapse
Thank you for your quick reply. I was on the customs kernel, then I went back to stock and all work!

Used SE Linux switcher to set Permissive and flashed clean vendor image. NSG still doesn't seem to work for me "coral"/4 XL. I have tried clearing app data of course.

loonix said:
Used SE Linux switcher to set Permissive and flashed clean vendor image. NSG still doesn't seem to work for me "coral"/4 XL. I have tried clearing app data of course.
Click to expand...
Click to collapse
You won't need permissive so don't worry about that. Also make sure you're flashing the vendor image that is downloaded from the specific Driver Binaries page. These are built as "userdebug" images, which has less functionality stripped out compared to "user" images that are in the completely factory image download. If you're sure you've done that, reboot, open NSG, menu button>exit, reopen and repeat as necessary. If it still doesn't work after like 5 attempts, then check a couple props. The first one we can check is 'getprop ro.vendor.build.type' (run with su).

Pretty sure I got the vendor image right. I am on January patch and the correct one for Google Fi is "Pixel 4 XL binaries for Android 10.0.0 (QQ1B.200105.004)". Unfortunately it still didn't work after trying the reopen 5/6 times workaround.
Code:
coral:/ # getprop ro.vendor.build.type
user
coral:/ #

loonix said:
Pretty sure I got the vendor image right. I am on January patch and the correct one for Google Fi is "Pixel 4 XL binaries for Android 10.0.0 (QQ1B.200105.004)". Unfortunately it still didn't work after trying the reopen 5/6 times workaround.
Code:
coral:/ # getprop ro.vendor.build.type
user
coral:/ #
Click to expand...
Click to collapse
Looks like it didn't flash correctly or you may have accidentally grabbed the wrong img file. Maybe download it again and rename it right away to "vendordebug" for example. The returned value should be "userdebug".

I am doing all of this in macOS. The idea is same , extract google_devices-coral-qq1b.200105.004-b60dcbca.tgz to get vendor.img but oddly enough the timestamp shows vendor.img to be Jan 1, 2008 , 2 AM and weighs 710.2 MB, and that looks odd.
In macOS, it is the sh scripts when executed extracts all files in all folders recursively.
Code:
/Users/x/Applications/coral/coral-qq1b.200105.004/vendor/google_devices/coral/proprietary
MacBook-Pro:proprietary $ ls -lrt
total 1409680
-rw-r----- 1 x staff 710222032 Jan 1 2008 vendor.img
-rw-r----- 1 x staff 768 Dec 18 00:23 device-vendor.mk
-rw-r----- 1 x staff 815 Dec 18 00:23 BoardConfigVendor.mk
MacBook-Pro:proprietary $

Related

WARNING #1: operations indicated on this post might potentially brick your device, make it unusable, to cause explosions, eruptions of nearest volcano and a lot of similar disasters.
For sure they will void your warranty in most countries and need all of your data permanently deleted, so make a copy of anything valuable before starting and don't do any operations if you are not a trained guy and sure about what you are going to do.
These are *not* operations for rookies. I will not be responsible in any case about eventual damages. XDA is your friend: if unsure, please ask! :fingers-crossed:
WARNING #2: operations elencated on this post are indicated and first hand tested as working only on Moto Z2 Force (Nash) XT1789-06 GSM/3G/LTE dual sim 6GB RAM 64GB storage unbranded international version on sale on German market with Nougat v.7.1.1 onboard.
They will probably work on most of unlockable bootloader & SIM unlocked versions, included US -04 versions too, but you'll test them yourself.
They are not intended for (US mainly...) CDMA versions (-01 & -03 if I don't go wrong...) since of a bit different hw/fw so avoid to apply them "as is" on those devices.
WARNING #3: there will probably be better methods to obtain same results and, for sure, there would be more in future. This is only a "recap" of what I've found working and applied first hand on my unbranded XT1789-06 Nash - with, IMHO, great results... - on November 2017.
I think this could be useful for many.
WARNING #4: I'm Italian, English is not my first Language, so... be patient!
1. INTRODUCTION
On this guide you will not find anything particularly new and/or not already present on this section of XDA.
So, why this guide? For some reasons...
First of all, to date every guide posted here is for a single operation (e.g. root, TWRP, etc...) and do not take in needed consideration interactions between single operations that, often, can be present, potentially dangerous and/or lead to unexpected behaviours.
More, for a single operation here there are often different posts with different guides/solutions and this could leads to errors and or doubts about what's better for our device...
Last but not the least, to date Nash developers here are mainly from US and so working on devices for the most part provided with branded fw and/or a bit different hw/fw respect to international unbranded versions sold on Europe, Asia, South America & Australia.
From my previous experience with my "old" Griffin (Moto Z) Motorola's fws are often interchangeable between devices with no (or only minimal...) issues at all, but, anyway, having a guide with operations first hand tested on same device is surely safer...
So, in this guide I'll link all best single guides posted here and I'll comment & link them to obtain a single complete "to do list" of works...
2. WHAT WE'LL GET
Following this guide we'll get a Moto Z2 Force with unlocked bootloader, latest available firmware (at present...) on board, a working TWRP recovery, complete root access, BusyBox support (needed for A LOT of interesting sw/tasks...) and Xposed support (I don't think I need to explain Xposed features & benefits here... ).
Taking in consideration how Moto's devices come with a "quite stock/vanilla" Android version on board, they are between the best devices to be rooted & Xposed provided to obtain a great customized system.
If you want to remain stock with your device eventually go with Samsungs (or similar...), but if you want a device that is a "blank canvas" for your customizations, Motorolas and this configuration would quite be the best you could want.
You are surely thinking about lack of Magisk and "SU hiding" solutions... obviously there are reasons for this.
Magisk: I have first hand seen how Magisk is a "very intrusive" software with its installation, it goes to modify *A LOT* of things on system partitions and this could leads to eventual issues/incompatibility.
More, it has its own rooting system (that in my humble opinion isn't better than SuperSU) that I preferred not to use (beneath I think it could be disabled... ) and that could conflict with SuperSU, if not now, maybe on successive Magisk updates (as it happened on my old Griffin... ).
Last but not the least, it seems to still have issues with particular partitioning present on our device (we'll see them later) and with TWRP flashing for same reasons...
Not to mention how, to date, it has really so few functions/modules we can't have using Xposed....
SUhide: there is a detailed guide on how to install succesfully SuperSU with its SUhide function on our device. On the same guide it's reported how that method is uncompatible with Xposed and leads to unsolvable bootloops if we setup both of them.
It is still not clear (to me...) if this is related to SUhide itself or to the different SU installation needed for SUhide to work but, anyway, I preferred Xposed obviously.
Not to mention that for Xposed have been developed some modules to succesfully hidden root (even if I don't know if they already works with Nougat... )
3. LET'S TAKE A LOOK TO OUR DEVICE
Knowledge is power. So, taking a look to our device particular features will help us to avoid errors and eventual issues...
Motorola developed our device with a new configuration/partitioning scheme seen before only on Google Pixels / Pixels XL, making our device probably the first "not Google" one to adopt it.
It is mainly marked by two news:
- there is no more a recovery partition :crying:
- there are two copies of boot and system partitions, called boot_a, boot_b, system_a & system_b and device is capable eventually to boot from every of them :cyclops:
Let's look them in details..
Recovery is obviously still present victory BUT it has no more its own partition, it is instead included in boot partition (where before there was only kernel and little more...) creating a potentially unwanted (by us tweakers, probably wanted by Google for the opposite reason! ) link between boot and recovery where safe rules would want them as unlinked as possible!
This leads to the need to flash a boot.img containing both kernel and recovery when we want to update only one of them (e.g. installing TWRP...) and this will have to be taken in account every time we would go to update kernel, TWRP but even when rooting (in fact, at first, developers were not able to gain root together with TWRP... issue then solved succesfully :highfive.
On Pixels their developers have found some methods to overcome this problem, but on our device, to date, we still don't have a complete solution to this issue. Anyway we are going in the right direction and it will be only matter of time in my opinion (especially since I'm "stressing" our developers to realize a similar solution...! ).
Double partitions for boot & system, often referred as "A/B partitioning" is a system introduced by Google to distribute OTAs in safer & seamless way, without interrupting user work during updates... (bah... ).
They are so totally unuseful as originally designed for US, since of going with TWRP/root, OTAs are no more a solution to upgrade and this partitioning scheme introduced some complications which have led to issues as with Magisk (as already seen...).
BUT as soon as we'll learn how to well manage them, new horizons will open (like updating fw on a partition still having the older one on the other for safety reasons and/or having two different fw versions and be able to choose what to boot from.. ). It's only matter of time...
Anyway in this guide we'll face them ever with safe in mind at the moment...
4. READY? LET'S GO WITH UNLOCKING BOOTLOADER!
If your device has unlockable bootloader (and if it is an international unbranded XT1789-06 it should have...!), you can easily unlock it with this good guide:
https://forum.xda-developers.com/z2-force/how-to/how-to-unlock-bootloader-t-mobile-t3654657
There is no more to say about this guide since it is well done, only some notes:
- guide title speaks of T-Mobile but obviously is suitable for international/unbranded too...
- please note that unlocking bootloader will wipe from your device all data & media storage (and they will be wiped again in successive steps, so *be sure* not having nothing valuable - e.g. your girl pics.. - before starting with procedures);
- install Motorola's latest drivers & fastboot provided on their site as hinted on guide. Don't skip this step to avoid potential issues in successive steps...
- if I don't wrong remember, step 8 of guide has to be repeated two times to confirm unlocking. Anyway look at your console messages and follow directions...
Reboot to system and make a fast configuration (we'll wipe them in minutes... ) to check all is ok and re-enabling usb debugging is preferred.
5. DOWNLOAD & UPDATE YOUR FW
I don't know with what firmware your device will come, BUT if it has anything *before* Nougat v.7.1.1 rel. NXPS26-122-68-1 we well go to update to this for following reasons:
- we need a (good) complete stock fw image to be flashed in case of problems;
- it is updated to September 2017 security patch;
- we have a TWRP with *this exact kernel* (they are linked in same image, remember?) for those (like me... ) which like a "so close to stock as possible" system...
This firmware can be downloaded from the following link: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (about 2,35 GB..)
PLEASE NOTE: If you have newer firmware don't use this BUT try to download a matching version with your actual one.
Zipped file has to be fully unzipped into the folder containing fastboot executable (downloaded from Motorola!) on your PC.
If you get any error unzipping, *DON'T FLASH* anything and download again (eventually from another browser/PC).
Fastboot sequence I used is the following:
Code:
fastboot devices
pause
fastboot flash modem NON-HLOS.bin
pause
fastboot flash fsg fsg.mbn
pause
fastboot erase modemst1
pause
fastboot erase modemst2
pause
fastboot flash bluetooth BTFM.bin
pause
fastboot flash dsp adspso.bin
pause
fastboot flash logo logo.bin
pause
fastboot flash boot boot.img
pause
fastboot flash system system.img_sparsechunk.0
pause
fastboot flash system system.img_sparsechunk.1
pause
fastboot flash system system.img_sparsechunk.2
pause
fastboot flash system system.img_sparsechunk.3
pause
fastboot flash system system.img_sparsechunk.4
pause
fastboot flash system system.img_sparsechunk.5
pause
fastboot flash system_b system_b.img_sparsechunk.0
pause
fastboot flash system_b system_b.img_sparsechunk.1
pause
fastboot flash system_b system_b.img_sparsechunk.2
pause
fastboot flash system_b system_b.img_sparsechunk.3
pause
fastboot flash oem oem.img
pause
fastboot erase carrier
pause
fastboot erase cache
pause
fastboot erase userdata
pause
fastboot erase ddr
pause
fastboot reboot
That is ready to be put into a batch file to avoid errors and having the possibility to check results of every single flashing since of pause commands presence (press a key to continue to next file). Batch file has to be placed and started from same folder of fastboot & unzipped files to avoid errors.
Please note:
- I've added a fastboot devices command as first to check if your device is properly connected;
- I've used stock sequence of flashing BUT removed gpt (partitions) and bootloader for safety reasons (no need to flash them usually... and let Motorola upgrading your bootloader rarely is a good choice... )
If all flashes will go fine your device /data would be wiped (yes, again!) and phone will reboot after last command.
If something go wrong stop the sequence by CTRL+C and do not reboot your phone until you have understood/cleared/fixed what has gone wrong.
If fine, again... reboot to system and make a fast configuration (we'll wipe them in minutes... ) to check all is ok and re-enabling usb debugging is preferred.
6. INSTALL TWRP
This is a quite simple step, but you have to take a decision before you start...
I'll provide two different boot+TWRP image files as attachment to chose from (both of them realized by @joemossjr )
First one is composed by stock NPXS26 kernel and TWRP v.2 (it's a 3.1.1-0 in TWRP versions), while the second is composed by a kernel recompiled (with little modifications) from sources by joemossjr and TWRP v.3 (still a 3.1.1-0 in TWRP versions) with some little improvements (you can go to his thread for details on TWRP https://forum.xda-developers.com/z2-force/development/twrp-3-1-1-0-moto-z2-force-nash-t3687421 and to this one for details on Pantheon kernel https://forum.xda-developers.com/z2-force/development/kernel-pantheon-kernel-t3702208 ).
If you are on NXPS software version (flashed before) and want to remain "full stock" go with TWRPNPXS.zip, otherwise (you preferring newest firmware or want all newest features) go with TWRPREV3.zip.
Both files *have to be* decompressed, *can't be directly flashed* and your choice of them has to be flashed in fastboot mode with the command:
Code:
fastboot flash boot TWRPxxxx.img
where xxxx is matching your choice.
If all have gone fine, you can now reboot to recovery and make some backups if you prefer (please note you will need to place them to an sd card or to a plugged USB key, since internal memory will be fully deleted again soon...
PLEASE NOTE: during this phase still *don't enable* TWRP to Mount system as R/W ("Swipe to allow modifications for /system" message...) since it could lead to a not booting system if DM verity check is still enabled (it shouldn't since what @ChainfireXDA reported on Twitter, but it is better to be safe...).
A reboot to system to check all is still ok is preferred. If TWRP asks to install his app files on exit, *be sure* to decline/skip (ever! There is an option in TWRP to disable this request too!).
PLEASE NOTE: this way we are flashing ONLY ONE of the boot partitions with TWRP (usually boot_a) while the other (boot_b) is unaffected. This is a wanted behaviour to stay on "safe side".
PLEASE NOTE: On the linked thread @joemossjr put a flashable zip file to update it from inside TWRP itself which flash both boot_a & boot_b. So if you'll want to update to newer versions (and remain on safe side...) unzip that file too (instead to flash it in TWRP), extract boot.img contained inside and flash it with the same command indicated before.
Please note all newer versions will use Pantheon Kernel.
WARNING: If you will in future reflash kernel/TWRP to update them, you would lose both root & disabled forced encryption!!!
So, after every boot.img flashing *you will need*, before booting system, to boot TWRP and flash again SuperSU before reboot to system.
If you fail to do this you'll face bootloops and/or your /data partition will be corrupted. So a /data backup (on external storage!) before a kernel/TWRP update would be mandatory.
7. ROOT & DECRYPT DEVICE
In this step we will go to finally root the device and decrypt its /data partition. This operation *will delete all data again* on you device (downloaded files & pics too!).
Decryption of /data is needed for many reasons:
- to date TWRP is unable to work with compressed /data (and, anyway, it's ever dangerous to work with encrypted data backups/restore... )
- some advanced software you'll go to use could have issues with encrypted data
- a decrypted device is slightly faster
- you definitely will want it unencrypted... listen to me!
Since our phone will come "force encrypted" (it can't be disabled on stock fw!), we need SuperSU help on this and so we'll need to follow *at perfection* the following provided sequence!
Not all SuperSU are equals (more... they are all different! :silly so, tested working fine version to be used is this: http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip?retrieve_file=1
If newer will be out, don't mind, you could ever upgrade it from inside a working system...
Steps are:
- boot to fastboot mode (from off, VOL DOWN + POWER)
- from fastboot mode select RECOVERY mode
- go to wipe menu and select /data FORMAT (not wipe or factory reset, FORMAT!)
- if you have placed downloaded SuperSU zip file on SDcard or USB key browse to it in TWRP Install menu (otherwise connect your phone to PC and trasfer it to internal memory and then browse for it), then Flash it.
- *do not* and I repeat it, *do NOT* clear cache/dalvik cache
- reboot to system
First boot could take a while and probably it reboots one (or two...) times, but at the end it will boot... :fingers-crossed:
You'll have to reconfigure again your system BUT this time, if all has gone fine, it's the good one, so you can do a better configuration if you want.
You will need a working Play Store for next steps, so add a data SIM and/or a wireless network and setup a Google account to enable it.
To check if all has gone fine you should have:
- a SuperSu icon into apps drawer
- on Settings - Security there should be an option to encrypt your system (DON'T chose it! :silly instead of the previous "encrypted" status..
It could be a good moment to download an useful Root check app. A good one is Root Check by JRummy Apps which is able to check Busybox & Xposed presence too (and more...).
8. BUSYBOX & XPOSED
If you have reached this point and all is fine, now it's very simple to complete.
Both Busybox & Xposed can in fact be installed from inside a working rooted system, so...
- download from Play Store BusyBox (free version) by Stephen (Stericson), open it, grant root permissions and press Install button without wait all the (unuseful) checks
- reboot
- enable in Settings - Security the "unknown sources"
- download from here https://forum.xda-developers.com/attachment.php?attachmentid=4319220&d=1509453299 latest Xposed installer/manager apk
- install it, open it and grant root
- select Xposed v.88.2 (or newer if available) for arm64 (if many options are showed be sure to select this, arm64!!!) and select Install (*NOT* via recovery... simply normal Install)
- when prompted for a reboot, accept it.
Please note first reboot could take a while and, again, it could self reboot one (or two times...). When at last it will reboot... gotcha!!! It's cigar time!!! :victory:
Well... it has been a LONG WORK to write this as simple & complete as possible. I hope to not have inserted any error and to have been enough clear on provided instructions.
If you'll find any errors please report to me for corrections.
Newer & better methods are welcome too.
If you liked this, PLEASE USE THANKS BUTTON!
EneTec
MANY THANKS TO:
@seniorstew
@joemossjr
@jhofseth
@Uzephi
for their useful linked guides and/or great development! :good:

Reserved #1.

Reserved #2.

Awesome guide! One of the most intricate guides that goes over every last detail that I've read on XDA in a long time. Thank you. ?

...

Great guide, thanks for the notes re: Xposed...I kept trying to install from TWRP (habit)

3's&7's said:
Great guide, thanks for the notes re: Xposed...I kept trying to install from TWRP (habit)
Click to expand...
Click to collapse
Our device still needs some cautions & tips...

Issue with Modem/Radio
After following your guide to the letter, my phone would not connect to a mobile network and would say "Error while searching for networks" when I tried to force it to find one. I ended up following this guide to try and get back to a working setup:
https://forum.xda-developers.com/z2...m-stock-november-hybrid-rom-t-mobile-t3712795
Unfortunately, nothing is working. Any help would be greatly appreciated.
Thanks!
-Josh-

I figured it out. Had to use the Flash ALL Package from that other post. The modem firmware is very specific.

might be this is the reason i loose 4G+ (4G instead) signal after flashing lmfao

just Wow!! What a great post!!

Damn! Why did follow this guide!? I knew I didn't need to flash anything but boot/boot_a and stay on stock FW with only TWRP from Pantheon kernel!
Now I have a Moto Z2 Force (Dual SIM, UK, retail) without wifi, mac 02:00:00:00:00:00:00:00 and it cannot switch it on!
Any one have full stock image, at least of the boot partition from Dual SIM, UK?
PS: No need to link to Factory Image Moto Z2 Force (NASH) RETAIL. both of them aren't fixing anything for me.

hashnon said:
Damn! Why did follow this guide!? I knew I didn't need to flash anything but boot/boot_a and stay on stock FW with only TWRP from Pantheon kernel!
Now I have a Moto Z2 Force (Dual SIM, UK, retail) without wifi, mac 02:00:00:00:00:00:00:00 and it cannot switch it on!
Any one have full stock image, at least of the boot partition from Dual SIM, UK?
PS: No need to link to Factory Image Moto Z2 Force (NASH) RETAIL. both of them aren't fixing anything for me.
Click to expand...
Click to collapse
Bitdefender blocked it for me for the longest time, then after reinstalling minimal ADB and Fastboot, Motorola Manager, and allowing access to Windows File Explore through Bitdefender, it worked for me; check your antivirus, hope that helps.

Blocked what? And anyway, I don't have any antivirus. There is brain and Linux for that!

hashnon said:
Blocked what? And anyway, I don't have any antivirus. There is brain and Linux for that!
Click to expand...
Click to collapse
Oh my bad, lol

Ok, fixed it my self, this: https://forum.xda-developers.com/ne...0000000000-t3257465/post65960082#post65960082 gave me general idea what to do and what to check.

hashnon said:
Ok, fixed it my self, this: https://forum.xda-developers.com/ne...0000000000-t3257465/post65960082#post65960082 gave my general idea what to do and what to check.
Click to expand...
Click to collapse
Good to hear that, I got so mad when I went in and tried rooting my Z2F without reading this guide first on the very first day that I got it. ??

Deester4x4jr said:
I figured it out. Had to use the Flash ALL Package from that other post. The modem firmware is very specific.
Click to expand...
Click to collapse
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?

ilovemeow said:
might be this is the reason i loose 4G+ (4G instead) signal after flashing lmfao
Click to expand...
Click to collapse
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?

hashnon said:
Ok, fixed it my self, this: https://forum.xda-developers.com/ne...0000000000-t3257465/post65960082#post65960082 gave me general idea what to do and what to check.
Click to expand...
Click to collapse
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?
How do you fix your wifi issue exactly?

LAST PERSONALLY Verified as working and "stable"*: GAPPS, 8/19 GAPPS
First and foremost, I'm simply compiling this for the OnePlus 6 and am making some small tweaks to include Opengapps and not only Go Apps in the builds.
The parent for this by phhusson can be found at [Resurrection Remix] [Unofficial] [2018-05-19] Phh-Treble
Next the most important information where to get the most current build of the ROM: Google Drive
For now I suggest the version ending in -go such as: 'rr_6_1_180616_system-arm64-ab-go.img.xz' as the '-gapp' is in development, I expect a number of builds over the next few days as I finally the build scripts and then the rate to tapper off to every two weeks or as there are changes that seem to warrant it, I'm not building nightly for no reason, as RR 6.1 is reasonable stable at this time.
Note: Attached (build.sh) is the build script currently being used, it is a work in progress. and will be updated in case you more regular builds. You will need 12GB of Ram Ubuntu 16.04+ (I'm using 18.04 now, but I started with 16.04) and at least 360GB (SSD recommended) to build, and upto 6 hours for the initial run and then 2 for ever additional run.
Many thanks to phhusson for allowing me to post this based off of his work.
Changes, when I have something to report. Not all build will:
The 7/7 build includes a number of patches recommended by DocRambone.
Overlay support to force Apps fullscreen, Under Display->Advanced
Some cleanups to the UI for the round corners
Better LED support
The 7/8 build is the same as 7/7, but includes July security patches, I built it in order to match the official release.
The 7/24 build is again to match the official release
The 8/19 build is again to match the official release, note regression in status bar height I'm looking into.
Second post: will have details on what is working and not
Third Post: will have full instructions on installation, backup restore based on my experiences
* Stable is relative, for me if I consider it usable from day to day it is stable.

As of 8/11/2018
In the GAPPS version
Working:
Fingerprint
Camera (Front and Back) + Flash (Also got the OnePlus Camera working*)
Speaker
Wifi (Some cut outs seen, this is not unique to this ROM and is dependent on the access port some are worse than others, no clue why)
Bluetooth
GPS
Brightness
Slider for Notifications as of 6/18 build
Mobile Data/Voice (tested dual SIMM is working)
Google Apps
Root (using magisk 16.3), told but have not personally tested that 16.4 without changes works as well
Ambient (works serious effect on battery see next post)
Full Screen Aspect Ratio Display->Advanced 7/07/2018 build+
More fully functional LED Improved for at least mounting USB sticks in 7/7 build
USB Host - Fixed for at least mounting USB sticks in 7/24 build
Bluetooth Phone audio is on the local headset. - Fixed in 7/24 build
Seems working NFC working 5.1.11 Vendor and Boot, not working with previous to 5.1.9 Vendor and Boot I have nothing to connect to to fully test
Not Working:
The Notch hides content (need to wait for P)
Unknown:
Camera Quality: I do little with the camera and am no photographer, so I can say nothing about quality, only it installed and took pictures
VaSU# said:
volte kinda works you can receive messages and calls and can send messages but cant call "out"
Click to expand...
Click to collapse
Please let me know if anything is missing, or needs to be added

Instructions to flash, backup ...
WARNING: With 5.1.8 I had no WIFI, so I suggest sticking to 5.1.6 to 5.1.7 FOR THE MOMENT
Instructions to flash, backup ...
Total time required about 90 minutes
Pre-Reqs:
First and foremost:
Start with at least 5.1.6 (or greater, as of writing 5.1.7 was the lastest), there are Treble fixes in 5.1.6 we need.
Second
verify you have a good USB cable (the Red one shipped with the phone is best)
Three
download the oneplus drivers and abd
- USB Drivers: OnePlus 6 USB Drivers for Windows
- ADB/Fastboot: ADB/Fastboot latest mini
Install both to your local system
Four
Download the latest TWRP (get both the img and zip files)
TWRP for OnePlus 6
Five
Download the files(Treble OP6 Files 5.1.6) from:
GUIDE] How to flash Treble roms on OnePlus 6
Extract and keep: vbmeta.img (if you are on 5.1.X where is the boot version you can keep the boot.img as well, if not discard).
Six
Download the lastest Oxygen OS ZIP and bootloader from:
[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates
As of writing this is:
5.1.6 full image: OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
5.1.6 boot: OnePlus6Oxygen_22_OTA_010_all_1806070151_boot.img
Seven
Download Device ID:
Device+ID APK
Eight
Download Magisk for Treble:
Magisk modified for treble
Since as of 6/2018 the default magisk does not support Treble we need a special version I suggest: Magisk-v16.3-factory-faizauthar12-20180406.zip as teh latest I could find with support.
Nine
Recommended download fastboot installable 5.1.6 (or latest build):
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Ten
Include Overlay/Ambient Display.
Download APK at: [Overlay] Enable Night Light, Auto-Brightness, Ambient Display & more on Treble ROM
Eleven
OnePlus Camera:
OnePlus Camera APK's
Finally
Download RR 6.0 for Treble compiled after 7/08/2018:
Either download the gapps or go version (gapps is still a work in progress when I wrote this)
ROMs Google Drive
Getting Ready:
WARNING: you will loss all data on your phone, backup anything you want or need, first.
Make sure you can get to fastboot (enable "Advanced Reboot" in developers options and make sure that you can enter on a reboot by pressing volume-down and power at the same time)
Make sure you are on 5.1.6+ (5.1.6 was the latest firmware upon writing this)
Remove Any security you have set (just to be safe)
Reboot to fastboot (bootloader)
run:
Code:
fastboot oem unlock
"You will be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection, allow your device to reboot"
Backup EFS
If you have not already I'd recommend backing up EFS (to do so you need to be rooted, or else use TWRP):
Preferred, if rooted simply open a terminal and run:
Code:
su
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
Copy these files someplace safe!
If not rooted reboot to fastboot (bootloader):
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
select only EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Backup the Phone
Recommended if you care: Backup your entire phone using TWRP as well:
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
Select Everything except EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Installing RR:
Finally we are ready to install RR (or any other Treble ROM), on the OnePlus 6. You will need a build from 6/7/2018 or later to have the required Vender-Hal to be present.
You will need to locate and install the AB version for the OnePlus 6.
Note: I'm using RR from 6/13 as the base for the guide: system-arm64-ab-gapps.img
SEE FIRST POST FOR CURRENT DOWNLOAD LOCATION I compiled this using phhusson's (Orginial Build Scripts)
instructions and a bit of setup on Linux. However most Treble base ROM's should work so long as they are from after 6/7/2018 in a similar manor.
* Remember this will wipe your device and you will loss all data *
First
boot in to fastboot (bootloader):
We need to go back to TRWRP and wipe internal storage and data to be safe, as the -w option to do so when flashing is not working for me.
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Swipe to Wipe
Click back until you are at the main menu
Click on Reboot
Click on Bootloader -> "Do not Install" for TWRP if asked.
Second
Flash the new ROM:
Flash vbmeta.img to remove validation
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
To be safe flash a default boot image (5.1.6 in this case)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Next reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->Thiscan not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot to fastboot
Now flash a the new ROM:
- fastboot flash system_a system-arm64-ab-gapps.img
- fastboot flash system_b system-arm64-ab-gapps.img
Three
reboot:
Code:
fastboot reboot
You will see the "andorid" boot screen (this is different that the Oxygen one) and being the first boot it could take a while. If you see no boot screen or it does not boot (give 10 minutes), then you likely need to repeat these steps again. If you boot into RR then continue.
You may get a Vender image mistake error ignore it it only appewars on boot.
Skip the Setup by clicking all four corners top left->top right->bottom right->bottom left (it my take more than one try), at this point you have no networking, that is what we want.
Suggestion make backup here as you have a working OS! -- Instructions to follow
Four
Move over required files: You now have RR installed and working:
Enable developer mode and then enable Advanced Reboot
Then copy over gapps-nano, Device+ ID.apk, magisk-manager apk and magisk installer zip to the phone
To get the magisk manager you need to extract it from the zip as I cloud not get the normal one to install. Extract the zip: Magisk-v16.3-factory-faizauthar12-20180406.zip copy common\magisk.apk to the phone
Five
Deal with: "Play Services not Certified by Google":
Install Device+ID (APK downloaed above) and Open
Once done open the second line shows the GSF ID for this device
Android Register GSF
Login using a gmail account (I suggest the one you use for the playstore)
Enter the GSF in the field, now we wait about 5 to 10 minutes for it to propigate
Reboot the phone as we want paly services to start fresh
First add a wIFI network.
Critical do not let any apps update until you have registered playstore, so if you see a notification saying downloading, select and click pause. Doing so with the updated 6/17 paystore resulted in a black screen where you would enter your password, no know work around other than reset if this happens.
click on playstore it should now start
Now login to your account and you should be go (it may take more than one attempt no idea why).
Now enable the update if previously paused
Update all Apps from the playstore before continuing, this may take a while give it 10 minutes
Optional: If you want remove Device+ID now (but I leave it as it is an easy way to get information).
You now have a working Playstore, if you have hung downloads then you may need to clear the cache for play services and the playstore I assume the unregistered might be the cause of them getting messed up.
Five
Install magisk:
Ensure you copied magisk zip and also the magisk manager apk to your phone, do not open, but click Done
Install the magisk manager, by locating the file in filemanager and selecting it.Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Install
Select the magisk zip from the filesystem and flash
clear cache
Reboot->System (If asked about installing TWRP swipe to install)
Allow the phone to fully boot
Suggested: Reboot the phone
Suggested: disable checks for updates as 5.7 does not work with this build.
Root is now setup.
Six
Installer th onPlus camera:
Many people want the one plus camera, copy the apk downloaed above to the phone.
Open and install via a file manager
Seven
resize Data (as it will be only 11GB), the partitioon will be larger, depending on your devide se we will use TWRP and resize2fs to grow it.
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Advanced->Terminal
Code:
resize2fs /dev/block/sda17
Reboot System
Eight
Recommended, make a backup of your hard work:
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select backup
Select Everything except EFS and Modem (as I'm unsure exactly which you need)
enter a meaningful name
swipe to backup
click "Reboot System" -> Swipe to reboot
Once back in RR copy the backup off the phone
Eight
Start using your OnePlus 6 with RR 6.0, rooted and with GAPPS
Nine
Upgrading:
Upgrading is simply replacing the system partitions and only these paritions (tested going from 6/13->6/16->6/17 builds)
Boot into fastboot (advanced reboot options)
Now flash the new system files:
- fastboot flash system_a new_system-arm64-ab-gapps.img
- fastboot flash system_b new_system-arm64-ab-gapps.img
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot System
Ten
Restoring a Backup from TWRP
*This is a work in progress I can not work out how to do so safely*
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Restore
Select the backup
Select Everything (other than EFS and Modem!)
Got to the main menu
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot Fastboot
Eleven
Night Light, Ambient Display, requires Root:
My suggestion is not to do this if you care abut battery as I've seen major drain (even with Ambient display disabled, testing this).
Copy the apk downloaded framework-res__auto_generated_rro.apk to /vendor/overlays
Code:
mount -o rw,remount -t ext4 /vendor
cp <location of file> /vendor/overlay
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
Reboot
Comments:
TWRP does not boot if flashed onto RR (the TWRP logo appears but it will not boot), this is currently only go to protect you from using the OnePlus Recovery and messing up RR. Flashing TWRP does not affect booting into RR.
TWRP DOES handle encryption without an issue, even a wrong first pin is not an issue
TWRP making a backup of Treble ROM, backup everything for now: Data, Boot, System, System Image, Vendor, Vendor Image.
If you have problems with hung downloads from the Playstore: Pending hung PlayStore
Wifi can be flaky (appearently this is a more general issue as even stock had some issues, I fixed them by only using either 2.4 or 5Mhz wireless, if I had both active I had constant disconnects.
Worst case, to recovery, back to Oxygen 5.1.6 if you end up in a boot loop stuck booting to rtecovery, etc:
- flash-all.bat
Reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->This can not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Copy the Oxygen full ROM back to the phone
Code:
adb push OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip /sdcard
In TWRP
Install
Select OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
Go back to the root and select Advanced Wipe
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Click on Reboot->Recovery (select Do not Install)
English
Wipe Cach and Data
Wipe Everything
Reboot
The phone will reboot same as the day it was made
If it does not then please refer to:
Mega Unbrick Guide for A Hard Bricked OnePlus 6
Note: Always boot fully at least once (I suggest twice and the first one is configuring android) before trying any steps above again.
Best of Luck, see a typo let me know
ERIC

thank you for this

[emoji102][emoji102][emoji102][emoji102][emoji102]
Sent from my ONEPLUS A6003 using Tapatalk

Thank you for putting so much hard work on this. Really much appreciated, will give it a try.

Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?

saintxseiya said:
Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?
Click to expand...
Click to collapse
No.

Great rom, I especially like the fact that I can choose to install without gapps (prefer fdroid). One thing that is missing is ambient display, hopefully it will be fixed sooner or later.

Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Abaddon said:
No.
Click to expand...
Click to collapse
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
same quality here

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
Never said anything about results, only that it could be installed and works, (takes pictures), personally I do little with the camera and am not photographer, but it can be installed (link above) and installed.
Updated the working to remove any confusion.

Maibol said:
same quality here
Click to expand...
Click to collapse
Could you post some comparison pics? Including portrait shots.
Would be awesome.

saintxseiya said:
Could you post some comparison pics? Including portrait shots.
Would be awesome.
Click to expand...
Click to collapse
sorry bro celebrating today with the family too much beer .....

So seeing this not even a month after the release of the op6 makes me happy and hopeful that we get a fully working RR-OS for the OP6 in the near future !

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
because Oneplus doesnt release blobs for camera

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
It will never be the same as OOS stock. Because aside from there is no device tree provided by OnePlus, they will never release the camera blobs due to licensing issues. Once we get a stable and proper gcam port. It'll be better than the stock OOS cam or close

is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore

unix2208 said:
is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore
Click to expand...
Click to collapse
TWRP not for now as treble is build as an image, but you should be able to flash using twrp just switch to img (though I have not tested that).
The GApps version is posted the 6/18 is working great, see second post.
As for Banking I'm unsure if any Treble based ROM passed the checks, as with or without root, as they appear as unsigned.
As for smartbar, I'll give it a try when I get a chance, as I do not use it personally.
ERIC

So safetynet won't pass?

I've been waited for Magisk v21 released by John Wu this morning, but I ran into some problems
What I've done
- download stock image file from Google official site
- follow the instruction given by John Wu at GitHub wiki
- run command
Code:
adb shell magisk --remove-modules
- when i flash the patched boot.img file, it stuck on the *G logo* with progress bar under it.
- After a certain period of time, it comes back to bootloader with a prompt saying: "no valid slot to boot".
What i've tried:
- redo all processes, no working
- switch active slot to both a & b, none working
- re-patch the stock boot.img file use different Magisk Manager version. The ones i tried: v8.0.0-Beta(offers Magisk v21), v8.0.0-Stable(offers Magisk v20.4), Canary version (offers Magisk Canary who claims to support android 11)
- change the command
HTML:
fastboot flash boot ***.img
to
HTML:
fastboot flash boot_a ***.img
&
HTML:
fastboot flash boot_b ***.img
then run
HTML:
fastboot reboot
. same result as said before
Basic info:
- Device: Pixel 3 (blueline), android 11 (build number RP1A.200720.009), latest android security update & Google play system update.
- Magisk: Magisk Manager v8.0.0 (released hours ago), Magisk v21 is suppose to be installed

Is patched boot.img filesize ~32 or ~64mb?

I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.

done

dmk16 said:
Is patched boot.img filesize ~32 or ~64mb?
Click to expand...
Click to collapse
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler

red stapler said:
I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.
Click to expand...
Click to collapse
Seems like we're in the same boat here lol, is this enough proof for a legit bug issue to John?

red stapler said:
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version.
Click to expand...
Click to collapse
DaddyTony said:
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler
Click to expand...
Click to collapse
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
[MagiskBoot] Pad boot images to original size with zeros
Click to expand...
Click to collapse

nogaff said:
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
Click to expand...
Click to collapse
Glad to hear, hope this indicates patch is successfully done?

Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11

So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).

I forgot to mention that I didn't install or use a custom recovery, such as TWRP. Using the stock recovery.

73sydney said:
Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11
Click to expand...
Click to collapse
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?

Didgeridoohan said:
So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).
Click to expand...
Click to collapse
I forgot to mention that i run this command before install magisk patched boot.img
Code:
adb pm shell magisk --remove-modules
I didn't have TWRP installed on my device, don't seem to have TWRP for Pixel 3 on android 11.

DaddyTony said:
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?
Click to expand...
Click to collapse
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it

73sydney said:
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it
Click to expand...
Click to collapse
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
Due to this reason, we no longer recommend installing Magisk through custom recoveries on modern devices.
Click to expand...
Click to collapse
BTW he also said the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
--------------------
edit:
Just find out Pixel 3 (blueline) has **NO** official support of TWRP v3.4+, but Pixel 3 XL (crosshatch) has it. How ironic.
and I wonder if TWRP v3.4+ support android 11?

DaddyTony said:
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
BTW he also says the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
Click to expand...
Click to collapse
Hmmm, disappointing
Ive literally tried the image patch method once, a lot of faffing about, I always use the TWRP method, easy peasy at least for older device
....we no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support.
Download the Magisk installer zip
Reboot to custom recovery
Flash the zip and reboot
Check whether Magisk Manager is installed. If it isn’t installed automatically, manually install the APK.
Click to expand...
Click to collapse
Guess ill be happy to remain a legacy device user

This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11

Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?

polyxn said:
Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?
Click to expand...
Click to collapse
Which version of Android?
Do you have TWRP installed?
If you do people have been posting that going to Advanced, then tapping Fix Bootloop may work
Otherwise find the boot image of the ROM you have installed, and flash that to the device
If youre on Android 11 on the Pixel, as i found out myself via bootloop, do NOT install TWRP, just fastboot to it to flash zips

M66B said:
This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11
Click to expand...
Click to collapse
I used this command (and tried to boot in slot a), the patched img still won't boot.
Did you managed to flash Magisk with patched boot file?

WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser app is not installed by default. Installing Firefox or Chrome from Google Play is recommended
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6/U7, please use the recovery tar for U6/U7.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img. boot.img, dtbo.img, recovery(U5), recovery(U6), recovery(U7)
- ADB and Fastboot
- Odin
- Kernel Source
- Google Apps(Flame)
WARNING: A BUG WHICH CAN POTENTIALLY LEAD TO BOOT LOOP ON U7 WAS FOUND. IF YOU ARE ON U7, PLEASE DO NOT FLASH THIS ROM UNTIL THIS IS FIXED.
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
Changelogs:
2021-10-19: Initial Release (AOSP 12.0.0_r2)
2021-10-21: Updated to AOSP 12.0.0_r3
2021-11-03: Updated to AOSP 12.0.0_r13 & added U7 support
2021-11-22: Fixed graphics issue, fixed battery issue (when battery level sometimes dropped by more than 2-3% on reboot), and fixed force crash when choosing Battery Manager in Settings
2021-11-25: Updated to AOSP 12.0.0_r15, changed battery mechanism to make it more accurate
2021-11-27: Kernel GPU driver update (R33P0 -> R34P0), LTE is now enabled by default
2021-12-10: Updated to AOSP 12.0.0_r16, removed the annoying search box widget on the home screen
2022-01-01: EGL graphics driver update to improve performance, minor bug fixes related to some apps.
SCREENSHOTS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

EDIT: the boot issue has been fixed, and you can now download the ROM.

This is great!
Do you working on this ROM for A21s, or you working on LineageOS 18 A11, paralel with this ROM?

grccorps said:
EDIT: the boot issue has been fixed, and you can now download the ROM.
Click to expand...
Click to collapse
instead of fastboot can we sideload super,boot etc?

Zdivan said:
This is great!
Do you working on this ROM for A21s, or you working on LineageOS 18 A11, paralel with this ROM?
Click to expand...
Click to collapse
Yes. I am also working on Lineage 18. Actually, the source code for this ROM is based on the source code for the Lineage 18. (of course, along with some modifications)

NuzzaimStark said:
instead of fastboot can we sideload super,boot etc?
Click to expand...
Click to collapse
I'm really sorry, but it is not possible to adb sideload images.

i got this when type and enter "fastboot flash boot boot.img"
C:\Users\nussa\Downloads\platform-tools>fastboot flash boot boot.img
< waiting for any device >
nothing showing in phone log

grccorps said:
I'm really sorry, but it is not possible to adb sideload images.
Click to expand...
Click to collapse
I am a bit sad because gaming time screen is flickering... Grrcorps pls check in your phone

grccorps said:
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
It has been only 2 weeks since Android 12 came out, so there may be some instability / bugs. I will try to work it out as time goes by. Also, when Lineage 19 is released, I will try to port it too. (Shouldn't be too hard though, as Lineage is quite similar to AOSP)
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
The network is set to 3G by default, so in order to use LTE, you should go to Settings->Network and Internet->Internet and change the default network setting from 3G to LTE.
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser and Music/Video Player apps are not installed by default. Installing Chrome and YouTube music from Google Pay is recommended
The search bar on the home launcher is useless until "Google" app or "Google Go" app is installed.
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img, boot.img, dtbo.img (Download all three)
- Recovery(for U5) / Recovery(for U6) / Recovery(for U7: coming soon)
- Google Apps
- ADB and Fastboot
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
SCREENSHOTS:
View attachment 5436707View attachment 5436709View attachment 5436711View attachment 5436713View attachment 5436731
Click to expand...
Click to collapse
only 1 sim card is work or 2 sim cards is working ?
( A217F ) , EGY

NuzzaimStark said:
I am a bit sad because gaming time screen is flickering... Grrcorps pls check in your phone
Click to expand...
Click to collapse
I'm really sorry, but could you please tell me which game it is?

ayman9321 said:
only 1 sim card is work or 2 sim cards is working ?
( A217F ) , EGY
Click to expand...
Click to collapse
As of now, this ROM is for single sim variant...

grccorps said:
As of now, this ROM is for single sim variant...
Click to expand...
Click to collapse
how can i fix it or can you help me to make 2 sim cards work ?
i install pit file for my country from the csc.tar from the android 11 firmware but not work after i install the stock android 11 firmware that is says your sim cards is changed restart to apply the changes .

grccorps said:
I'm really sorry, but could you please tell me which game it is?
Click to expand...
Click to collapse
Watch my gameplay I screen recorded it

NuzzaimStark said:
Watch my gameplay I screen recorded it
Click to expand...
Click to collapse
It said EXPERIMENTAL.
This ROM is not good enough for daily driver.
Wait for new version or install Lineage 18, or continue use this rom for testing.

Can anyone guide me how to root this rom?

Is this the s
grccorps said:
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
It has been only 2 weeks since Android 12 came out, so there may be some instability / bugs. I will try to work it out as time goes by. Also, when Lineage 19 is released, I will try to port it too. (Shouldn't be too hard though, as Lineage is quite similar to AOSP)
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
The network is set to 3G by default, so in order to use LTE, you should go to Settings->Network and Internet->Internet and change the default network setting from 3G to LTE.
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser and Music/Video Player apps are not installed by default. Installing Chrome and YouTube music from Google Pay is recommended
The search bar on the home launcher is useless until "Google" app or "Google Go" app is installed.
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img, boot.img, dtbo.img (Download all three)
- Recovery(for U5) / Recovery(for U6) / Recovery(for U7: coming soon)
- Google Apps
- ADB and Fastboot
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
SCREENSHOTS:
View attachment 5436707View attachment 5436709View attachment 5436711View attachment 5436713View attachment 5436731
Click to expand...
Click to collapse
Is this the stock Samsung Android 12 ROM?

NuzzaimStark said:
Can anyone guide me how to root this rom?
Click to expand...
Click to collapse
Patch the boot.img with magisk, same as how you root any other ROM
Maxis89 said:
Is this the s
Is this the stock Samsung Android 12 ROM?
Click to expand...
Click to collapse
No it is AOSP, it is written in the OP and also the screenshots are quite clearly AOSP

Do you need any logs or bug reports? If so, how to get them? Will the Lineage OS method work?
Add.: Gapps installation error: !Wrong android version detected. This package is for android 10.0 only. Your ROM is Android: 12. Blame, blind.

I tried rooting. There is no option ( root permission for usb debugging ) developer setting.
And I get these

NuzzaimStark said:
I tried rooting. There is no option ( root permission for usb debugging ) developer setting.
And I get these
Click to expand...
Click to collapse
Patch the boot.img with magisk app. Then reboot fastboot and flash the patched.img with fastboot.
This is, and will always be, the recommended way of installing magisk and getting root.

If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 3aXL
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!

Thank you so so much! I've successfully updated from October 2021 build to November 2021 build without any issues by following your guide. Bunch of thanks again.

I'm currently using Magisk Canary build?
May I Install Magisk Beta and also Magisk Stable build to the latest November 2021 build?

Rafiul Bari Chowdhury said:
Thank you so so much! I've successfully updated from October 2021 build to November 2021 build without any issues by following your guide. Bunch of thanks again.
Click to expand...
Click to collapse
Coming from the Pixel 3XL, which bricked out of the blue. I did every update on that phone, but never got to do 12 before the magical brick. I want to update this phone (5a, which I just realized is different than the 5?), but this seems to be missing quite a few steps. Shouldn't there be 4 different files added to your SDK folder and flashed, or has it completely changed, and I need to do more digging? Thanks.

Is there any way to do this after already updating? Or do I have to wait for the next update (I prefer flashing factory images).
I flashed the Nov factory image but forgot to disable the verified boot. Is there any way I can disable it so i can flash the magisk patched boot?

Rafiul Bari Chowdhury said:
I'm currently using Magisk Canary build?
May I Install Magisk Beta and also Magisk Stable build to the latest November 2021 build?
Click to expand...
Click to collapse
I honestly don't know. I've used Magisk 22.1, 23.0, Canary 23001 through 23011, all have worked for me.
The caveat is that Magisk 23010+ is Zygisk, which means that some legacy modules won't work anymore until they're updated - Universal SafetyNet Fix for example.
mcwups1 said:
Coming from the Pixel 3XL, which bricked out of the blue. I did every update on that phone, but never got to do 12 before the magical brick. I want to update this phone (5a, which I just realized is different than the 5?), but this seems to be missing quite a few steps. Shouldn't there be 4 different files added to your SDK folder and flashed, or has it completely changed, and I need to do more digging? Thanks.
Click to expand...
Click to collapse
You don't have to add any files to your SDK folder, you can always drag and drop them into the command line window. We are only working with two files here: vbmeta.img and boot.img.
EXV said:
Is there any way to do this after already updating? Or do I have to wait for the next update (I prefer flashing factory images).
Click to expand...
Click to collapse
You can do this as many times as you want. The critical point to remember is that if you allow Android to boot after not disabling verity/verification, you will have to wipe the next time you disable it.
EXV said:
I flashed the Nov factory image but forgot to disable the verified boot. Is there any way I can disable it so i can flash the magisk patched boot?
Click to expand...
Click to collapse
Yes...but you're going to have to wipe data. Extract vbmeta.img, and reflash it:
Code:
fastboot flash vbmeta --disable-verity --disable-verification <drag and drop vbmeta.img here>
Then, reboot your device. You will end up in Rescue Party, with the option to "Try again" or "Factory data reset". Choose the factory reset.
The best way to make sure you don't have to wipe your data is to always use --disable-verity --disable-verification when updating via the factory image.

Updated to November build with no problems, didn't like the new security patch - file managers targeting API 26 and below can no longer display/access other's apps data directories, hole is plugged, so went back to October build and had to wipe data to boot. So downgrading within same Android version also requires data wipe.
No more updates for me, sticking with October build...

I was on latest version of Android 11, rooted. I followed your third method using Android Flash Tool, and had both disable verity and verification checked. The Android flash tool says I may disconnect the phone. The phone is now stuck during boot, saying cannot load android system, data may be corrupt, may need to perform factory data reset and erase all user data, or try again. Trying again causes the boot loop. Any suggestions? Prefer not to perform factory data reset.

I got my phone back into bootloader and followed your second method via fastboot. I also arrived at the same error.

I tried the same thing on my wife's pixel 5a as well. Same errors.
I selected factory data reset and my phone boots up fine. Guess I had to reset my phone anyway, despite this guide. Hoping I don't have to reset my wife's phone. It's currently stuck at boot, but I can get into fastboot.

tintn00+xda said:
I was on latest version of Android 11, rooted. I followed your third method using Android Flash Tool, and had both disable verity and verification checked. The Android flash tool says I may disconnect the phone. The phone is now stuck during boot, saying cannot load android system, data may be corrupt, may need to perform factory data reset and erase all user data, or try again. Trying again causes the boot loop. Any suggestions? Prefer not to perform factory data reset.
Click to expand...
Click to collapse
This guide is for only Android 12. And you can't get your now at any cost.

That's a bummer. Guess there should be a disclaimer about going from Android 11 to 12. Good thing everything is backed up.

tintn00+xda said:
I tried the same thing on my wife's pixel 5a as well. Same errors.
I selected factory data reset and my phone boots up fine. Guess I had to reset my phone anyway, despite this guide. Hoping I don't have to reset my wife's phone. It's currently stuck at boot, but I can get into fastboot.
Click to expand...
Click to collapse
This guide was intended for updating, not for root.
If it wasn't clear in the guide, you will have to wipe data when you disable verity and verification, if they were not already disabled.
tintn00+xda said:
That's a bummer. Guess there should be a disclaimer about going from Android 11 to 12. Good thing everything is backed up.
Click to expand...
Click to collapse
It's at the very top of the post...
V0latyle said:
As many of you know by now, in order to run a patched boot image on Android 12 requires disabling Android Verified Boot.
Verified Boot on Android 12 devices, at least Pixels with the SD765G and Tensor, is tied to device encryption. Therefore, disabling Verified Boot requires a wipe, if it was not previously disabled.
Click to expand...
Click to collapse
This is why it's important to read the entire post, and ask questions if you don't understand something before you proceed.

Thanks a lot! This is my first device with verified boot / encryption linked - after crosshatch, and I have almost messed things up (just manually typed commands from memory), until I remembered this post.
Updated, everything is great.
December patch has brought bootanimation with different colours (Material You blahblah), made me freak out a little bit - I thought something went wrong.

I was always used to updating factory images (removing the -w) via ADB so none of my data would be wiped. But since the methods listed above don't include removing the -w from the zip, will any of those methods wipe my data while applying the update? I wanted to try the Android Flash Tool but got a bit paranoid since I didn't want my data wiped (I know there was a checkbox option to wipe the data, but I just want reassurance since with my luck, it'll probably brick my phone for no reason).

EXV said:
I was always used to updating factory images (removing the -w) via ADB so none of my data would be wiped. But since the methods listed above don't include removing the -w from the zip, will any of those methods wipe my data while applying the update? I wanted to try the Android Flash Tool but got a bit paranoid since I didn't want my data wiped (I know there was a checkbox option to wipe the data, but I just want reassurance since with my luck, it'll probably brick my phone for no reason).
Click to expand...
Click to collapse
Are you already rooted?
I personally don't use the flashall.bat method; I'm "old fashioned" and prefer to type the commands myself.
If you do use the script, just edit the "fastboot update" command to omit -w and include --disable options:
Code:
fastboot update image-barbet-buildnumber.zip --disable-verity --disable-verification
If you patch the boot image beforehand, you can add --skip-reboot, then once the update finishes, reboot to bootloader and flash the patched image.

Followed directions for recommended Android Flash Tool and everything worked flawlessly. If you've already rooted your phone once then you have somewhat of an idea of what you're doing. Just read everything twice and follow the directions. Thank you OP for such a clear path to update and root!

Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before.
I will be updating the OP to reflect this.

V0latyle said:
Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before. This needs testing, make sure you back up your data and photos before you try this!
I will be updating the OP to reflect this.
Click to expand...
Click to collapse
Just updated my wifes 5a-5G (non-root, verity/vbmeta enabled) to Dec update. Was able to root via flashing the patched boot.img with v23016 without a factory reset! Great news that John is still working on this tool and making all of our lives easier.

Someone want to test this?
Requirement: Pixel 4a, 5, 5a, 6, 6 Pro rooted with Magisk 23016
Reboot into bootloader and reflash vbmeta without flags.
Reboot to system.
Reboot to bootloader again, re-reflash vbmeta with disable flags.
Reboot to system. If you get the Rescue Party corruption message, just reboot to bootloader and reflash vbmeta without flags.
Report results here.