yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
This note is to mainly serve as a way to give feedback, though should anyone recognize anything as familiar and would have anything to suggest that could help me clean up the mess I made, that would be great.

So, as I mentioned, after following OPs instructions, I got myself in trouble by flashing a back-to-stock ROM [QP1A.190711.148-BACK-TO-STOCK]. The procedure flashed all the following files:

abl
bluetooth
boot
cmnlib.mbn
cmnlib64.mbn
devcfg
dsp
hyp.mbn
keymaster
mdtp
mdtpsecapp
modem
nvdef
pmic
rpm.mbn
system
tz.mbn
vendor
xbl

to both(!) slots. They all flashed successfully except 'boot' which failed with:

fastboot: verbose: target reported max download size of 536870912 bytes
fastboot: error: Couldn't parse partition size '0x'

Flashing of the BTS ROM also triggered the red "your phone may be corrupt..." DM_VERITY check, which has been persisting since.

Trying to sideload OEM ROM (I tried two latest OTAs) now fails with:

E: failed to verify whole-file signature
E: Error 21

and the log refers to RSA key mismatch.

Trying to flash OEM ROM with 'fastboot' also fails with "Couldn't parse partition size '0x'" error.

So, that's that, and since most of what's involved is way over my head, I'd be so screwed were it not for still being able to flash A11 ROMs, and CAOS ROM is stable enough to serve as my daily-driver, but it does not pass Safety Net, and it has a quirk that when I hide Magisk, the SELinux is then set to 'Disabled' from the initial 'Permissive'.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hedgecore44:
I couldn't tell ya about Safety Net because I run vanilla
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Sorry for late response cuz I am busy last week

I found this solution on Reddit, please try it

When you finish flashing all partitions (except boot), then use this command to flash boot:

fastboot flash:raw boot_<a|b> boot.img

Good luck to you, bro!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Port r:
hi, what is this CaOs where can i find it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] foueddyf:
Read step 7 of the OP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
That did it! Thanks. Although even flashing OEM to both slots did not clear the tripped up DM Verity check. I'm still looking for a way to fix that. This could be it, though I'm still unsure how aplicable it may be. It seems to bypass the problem as opposed to fixing it.

At one time there was a moded boot.img by Invisiblek made explicitly for mata, but I'm still trying to locate the image itself before setting up to build it myself. Thanks again for your guidance.

[EDIT] I think I found it. I'll try it later.

[EDIT2]It did work! It's all good now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Port r:
I just tried it everything work, had red boot problem, flashed a redbootfix.img after a few bootloops installed ur boot.img and now it's running. but none of my old data, apps sms downloads back, it doesn't even ask for resting them is there a way to do this easily? if not i'lll have to manually donwnload all the apps
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
If you have backed up your phone (naturally your phone will do it automatically) to Google, the easiest method is install GApps and factory reset.

Another method is using the GSI that has already included GApps :))
[Essential Phone ROMs, Kernels, Recoveries, & Other] Port r:
after using for one night, android 11 gsm, i've found out that all the icon r square which makes the whole ui look old and ugly, auto brightness is missing which is the deal breaker for me, there's no way to restore call logs, sms and apps. open gapps do not flash from sideload on stock recovery . apart from these the os is smooth, very usuable daily. Oh, and I wasn't receiving calls. the phone was ringing but it wasn't showing anything on the screen at all so i wan't being able to answer, installing google dialer and contact seemed to fix the problem. i have tried 10 and 12 gsm it bootloops.

anyway because of the smoothness i have decided to keep on using 11gsm for some time.

also i gapps fails to install and apps and logs from previous install do not restore, there is no option to add backup account on backup settings
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Which 11 GSI did you used? in my #1 post, I have a link to the 11 GSI. Have you choose the right ARM64+GMS version? That version is already included Google Play store and Google service.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hedgecore44:
I tried to go away from GSI because mobile data does not always work, VoLTE rarely works, can't receive MMS videos, and MMS text messages come in severely compressed. Also can't record video or install any version of Gcam.

I ran flashall.bat from January stock firmware and once that booted I no longer have mobile data. I flash 4 different roms in TWRP and still no mobile data in any of them. I go back to GSI Corvus and RR and mobile data only works once I click on all options in the PHH Treble Settings (IMS Features). Any idea how to get mobile data working back in non-GSI configuration?? I feel I am stuck on GSI now. Lol .... I am on Verizon btw..

Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] G@Neo:
Hi,

Thanks too much for you clear steps, there was some update since this post.

Android 12 GSI is it supported now?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sambow23:
Android 12 works now that the official AOSP sources are out, I used this specific build
[Essential Phone ROMs, Kernels, Recoveries, & Other] Angrydr0id:
Amazing, any bugs?

And where did you get that ElementalX Kernel?

Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sambow23:
Seems to to work just as well as Android 11.

As for ElementalX, I just cloned his last version and merged some linux-stable updates to get it working on modern Android versions. https://drive.google.com/file/d/1xZeqGFpx8epU8r-BJPq7eWR-zceM5IW0/view
[Essential Phone ROMs, Kernels, Recoveries, & Other] LightningJimmy:
Noob question, but what images did you use to flash boot, system, and vendor? I assume the thing you linked is the GSI image which has to be flashed after?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sambow23:
Vendor from this post, custom boot made from me, then the rom
[Essential Phone ROMs, Kernels, Recoveries, & Other] G@Neo:
Is it possible to make a tuto? To install specific build
[Essential Phone ROMs, Kernels, Recoveries, & Other] sambow23:
It's the same method as the original post
[Essential Phone ROMs, Kernels, Recoveries, & Other] Heartbreakidhn:
Hello! Booted perfectly and runs quite nicely, but I didn't flash Gapps and have no Google playservices. Try rebooting to recovery mode to flash or sideload but it appears it doesn't have one :S
[Essential Phone ROMs, Kernels, Recoveries, & Other] G@Neo:
Can it be side loaded as an update on top off lineage-18.1-20211011?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Heartbreakidhn:
Anyone knows if there is a way to use the essential camera with gsi? I need to use the 360 Camera >.<
[Essential Phone ROMs, Kernels, Recoveries, & Other] LightningJimmy:
@sambow23 sorry for bothering u with another question, but did you happen to get safetynet to work? I can't even get basic integrity to pass
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
I've been running OctaviOS 2.9, an A11 AOSP based GSI ROM then rooted w/ Magisk, and after Magisk Hide it's all blue on SafetyNet check. This ROM has been nearly perfect in everyday use. It's been smooth as OEM and with even better battery life.

There's a bit of a (hopefully temporary) wrinkle as the GSI build of this ROM just lost it's maintainer (do to loss of hardware), but for now it's been great, and A12 is on the horizon already, so no worries. Essential has done a great job with Treble/Vndk I/F libraries.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Alitoki:
This is interesting! Would you mind sharing a thread of this ROM for the phone? I tried looking around and couldn't really find anything, thank you!
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
They (the OctaviOS team) aren't on XDA but, as per OP:

- information on GSI ROMs

- ...and from there OctaviOS
[Essential Phone ROMs, Kernels, Recoveries, & Other] Alitoki:
Thank you! Essential isn't one of the downloads on the website, but I went to that link you sent earlier and downloaded the arm64 image
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
I've had best results with the VNDK variant, and then follow OPs instructions.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Alitoki:
Ah got it, I'll try it out! I actually just flashed, but my display is shifted to the right, I've had this issue before after installing Magisk and I see that this version has magisk installed by default, have you had a similar issue before? Maybe it could be the version of TWRP I'm using hmm..
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
No such aberrations on my install, but GSI installs seem finicky about (I think) what was there on the device before. It took me a handful of times to get mine right. I ended up flashing the latest OEM image (A10) to both slots, and then I just followed OPs instructions, and even then... For example, going through the same steps flashing to slot_b as for slot_a results in no Wi-Fi when rooted but slot_a is fine. Like I said, finicky, but worth (;-) the effort.

As for root? Hmm... I started with [IGNORE]this image, which is "bgN-vndklite", i.e. no root. Then, I downloaded the latest (v.23.0) Magisk app from the Play Store and went from there. Good luck.

[EDIT: it's this image]
[Essential Phone ROMs, Kernels, Recoveries, & Other] Alitoki:
Oh I see, so trial and error then! I'll see, I kinda messed up my recovery partition from trying to isntall lineage a while back, so my slot b has lineage recovery while my a has twrp haha, so I think I'm going to start all over again, I'll try that 2.5 image you sent, thank you!
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Sorry, sorry, sorry! I copied the wrong link. It's supposed be 2.9, NOT 2.5.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Alitoki:
Ah okay makes sense! I'll reflash! I fixed the display error I was having, just had to reinstall TWRP, thanks for this one!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Alitoki:
So I downloaded the image and flashed it, but it looks like the OS never boots, it just loads infinitly at the boot animation, but it's not a bootloop since it doesn't restart, may I ask what boot.img you have by chance?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
That did not happen to me, but it does take time (few minutes) to boot for the first time.

I used the boot.img from OP's AOSP.zip, but I think you could use any Essential's as well. BTW, remember to *always* erase userdata... no dirty flashing! [to save on the configuration pains I use SwiftBackup]. I'd re-flash the ROM again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] G@Neo:
Hi

Thanks for the Info I got it installed on second phone and it's running smouth, but the major issue is that I get muted call even if I change the dialer still persist.

did you got the same issue?

Any clue ?

Thanks in advance
[Essential Phone ROMs, Kernels, Recoveries, & Other] sambow23:
I do not have a SIM in the phone, so i have not tested it
[Essential Phone ROMs, Kernels, Recoveries, & Other] G@Neo:
Ok,

Could you please test, I revert back to lineagesOS18 and the problem was solved.

I think it's an issue with vendor img, because when I flash AOSP with the same vendor image I got the same problem.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mcdull:
How did you install magisk? Whenever I sideload it, I loss wifi.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
After having this new door for our phones opened by OP, I tried a handful of GSI ROMs, and have encountered the either/or problem with Magisk root and Wi-Fi myself. As per google, a problem's been encountered by many, and has no definitive resolution, and because I must have root on my phones, I was discarding all the ROMs that exhibited such behavior until I found one that did not. Well, now I'm coming around to understand that my blaming any such ROM was premature because the ROM that runs for me (nearly) flawlessly on slot A, has the same Wi-Fi problem when installed on slot B [shrug]. BTW, that ROM is OctaviOS.

Because of the many tries to get it working right, it seems to me that these things (Treble ROMs) are pretty picky about what's left behind on the device from previous installs (and what that could be is way beyond my understanding of the structures involved). I'm just speculating here, but where I started to succeed more consistently was by starting fresh every time by establishing a baseline (flashing the latest OEM ROM) before installing any new ROM, and then by following OP's instructions.
[Essential Phone ROMs, Kernels, Recoveries, & Other] zukizo:
ummm link not working? can you send me new link plz? and is it ok if i want to try this method to install any gsi room from cusrom? iam on havoc rn, thanks for the reply
[Essential Phone ROMs, Kernels, Recoveries, & Other] ali.sbi:
hi pro's. never used a GSI roms on my ph-1. i need to know can A12 GSI roms be install as daily driver?how?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Not yet. But A11 ROMs like Covus and Octavi certaily can be.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Hii bros,

I have come back and give you a new build for AOSP 12. Please check it now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
I updated in #1.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Hii bro, have you tested my new AOSP_12 build??
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
For now I'm holding off while tracking how the GSI builds mature. But I'll be getting a test PH-1 soon to play with, so I won't have to mess with my daily driver.

If I may ask, have you build a custom GSI yourself?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Mah009:
My problem is after unlocking bootloader, I wrote fastboot flash system.img and I got this error message me ANDROID-PRODUCT-OUT not set, I tried everything but nothing works out. I need some guidance.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
I dont clearly understand your mentioned “custom GSI”.

I only build the baseline AOSP in the step 1 by myself.

The custom roms such as Lineage GSI, DotOS GSI, etc. I use the provided prebuilt GSI.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Which AOSP file did you use? AOSP_11 or AOSP _12.

Could you please give me the step number you are stucking?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
hi, tried AOSP _12. After following all of your fastboot steps (successfully), rebooting the system failed and gave the RED Warning - system appears to be corrupted. I recovered from that easily (adb shell, then: reboot "dm-verity enforcing")

so, have you tested this build yet? it should never generate a RED Warning.

and, what is the purpose of "fastboot flash system_b system_other.img"?

this instruction gets executed on the inactive slot, which strikes me as very strange, and definitely needs a release note to explain what it is and what it does.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Yes, that's what I meant by "custom", the "official" GSI builds like DotOS, Corvus, etc..

The baseline AOSP you've build, do you start with the pure Google AOSP code, and how close is that to PHH's AOSP builds (which is what I've build as part of setting up my build environment)?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Mah009:
AOSP 11 i mean I couldn't get it installed, the above error message was what I got from the fastboot
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Sorry, this build hasn’t been tested yet, because I dont have the phone at the moment.

I tried to build this aosp 12 with the same method as aosp 11.

The fastboot step you mean is the Step 5, right?

You can try the boot.img in AOSP_12 and system.img and vendor.img in AOSP_11.

The system_other.img, according to the Google document, contains the odex/vdex optimized files.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
The AOSP I built is synced from the Google git. It’s the very pure AOSP bruh 😂. Maybe I will release the step-by-step guidance to build the AOSP baseline in 2 or 3 weeks…
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Not a bad idea. The more information is out there the more people get involved. "Sharing is caring" ;-)
[Essential Phone ROMs, Kernels, Recoveries, & Other] sluttyduck:
Hey, I followed the 1st post and just did the google gsi 11 install. How do I get gapps installed though? I've tried sideloading mindthegapps and it fails to install. "failed to find meta-info/com/android/metadata".

edit:

is the 2nd link in step 7 to a gsi w/out gapps right?

does GMS mean the image has gapps then?

so if I download the ARM64+GMS from google i'll have the plain google asop image with google apps right?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sluttyduck:
the answers to my questions are yes, for anyone wondering. I opted to download the dotOs with GAPPS.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chaseadam:
When you say you "recovered," does that mean you were able to boot the AOSP 12 image after enabling dm-verity?

How did you get to the point of being able to use adb? Did you have to reflash AOSP 11?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
After "recovery", I did not attempt a reboot. I deleted the build. I'll wait until after nguyenquangduc tests/validtes it.

So, to get to adb:

- connect a USB cable

- when the phone starts to reboot after getting the "red warning", launch the bootloader (power/vol down)

then,

- fastboot flash boot_a or _b (the current lineage recovery image)

- - get the Lineage Rcovery image at: https://download.lineageos.org/mata

- reboot to Recovery

- select Advanced

- select Enable ADB (you'll see "Enabled ADB" at the bottom of the PH-1's screen

now from your PC

- type and enter: adb shell

- you'll see the prompt: mata:/ #

- type and enter: reboot "dm-verity enforcing"

- when the phone starts to reboot, launch the bootloader (power/vol down). this avoids trying to reboot AOSPA12.

- from the bootloader you can overwrite AOSPA12 with a known/tested rom (or change the active slot, etc.)

Lineage Recovery is straightforward to use, and is actively maintained for the PH-1 (updates are made as often as weekly).

It also keeps the kernel fully up to date, It is now 4.4.295. And it is in fact a PH-1 boot image, which works with some A11 roms (I haven't kept a list)..
[Essential Phone ROMs, Kernels, Recoveries, & Other] chaseadam:
for anyone interested in using 'enforcing' SELinux, here is how I modified the cmdline from 'permissive' to 'enforcing':

Seems that selinux status is set by the boot.img (which I presume you are getting from nguyenquangduc2000's AOSP 11 download). That has the cmdline set to `permissive`. You can modify the cmdline with `abootimg` by extracting bootimg.cfg and then updating boot.img with the modification.

➜ AOSP11 abootimg -x boot.img
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
➜ AOSP11 ls
boot.img bootimg.cfg initrd.img system.img vendor.img zImage
➜ AOSP11 cat bootimg.cfg
...
cmdline = quiet ... androidboot.selinux=permissive firmware_class.path=/vendor/firmware_mnt/image buildvariant=userdebug veritykeyid=id:7e4333f9bba00adfe0ede979e28ed1920492b40f
➜ AOSP11 vi bootimg.cfg
➜ AOSP11 abootimg -u boot.img -f bootimg.cfg
➜ AOSP11 adb reboot bootloader
➜ AOSP11 sudo fastboot flash boot_a boot.img
Sending 'boot_a' (25057 KB) OKAY [ 0.839s]
Writing 'boot_a' OKAY [ 0.765s]
Finished. Total time: 1.628s
➜ AOSP11 sudo fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.050s
[Essential Phone ROMs, Kernels, Recoveries, & Other] sansp00:
I messed around with the tutorial and managed to boot the Android 12 version of PixelExperience GSI using the lineage recovery and WiFi does not work :( Was not able to boot the Google Android 12 GSI. Reverted back to Google GSI Android 11 which looks pretty flawless up to now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
I have updated a new version of AOSP_12_Jan_7.zip on #3 post. Could you guys help me try installing it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sansp00:
Sorry to report that I have the same issues with the latest AOSP_12_Jan_7 build than the previous one.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Hmm. so sad to hear this. Any guys who have a computer could try building the rom?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sansp00:
That's actually what I started looking into ... I haven't built a rom since Gingerbread, so bear with me :) Do you have a specific git and/or tutorial ? Currently, I am checking out the AOSP (GSI and normal), phhusson stuff. I was also gonna checkout the mata source code just in case. Thank god for WSL cause I don't have a Linux box lying around anymore that have the required specs.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sansp00:
After a lot of fiddling with WSL2, I managed to get a build of the current AOSP master branch and ended up with the same issues. I will experiment a bit using the info provided here from the Essential team. I have also looked at this but I have a lot of catching up on that front.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Dear bro,

As some ones reported that using the android-12-enabled kernel together with AOSP can be a successful solution.

Therefore, I have built a new image with android-12 kernel and system AOSP 11.

The link to the new build I have updated on #3 post. Could you please help me try it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sansp00:
This boots properly, but like in all Android 12 based GSI's, wifi is broken ... Android 12 kernel is probably missing the wifi modules/driver. We seems to be making progress :) I spent some time looking the source code to get a full AOSP build going in Android 12, but it is quite tedious and I don't have a ton of free time on my hands currently.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
For the confirmation, the wifi works normally on AOSP 11 but is broken in Android 12 GSI? Is it your situation?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
With the A12 ROMs that I tried, this seems to be the case. Using OEM boot.img results in SELinux enforcing, but WiFi that will not turn on. When that boot.img is patched w/ Magisk, SELinux becomes permissive, but WiFi is then working OK.

Also, every A12 GSI I tried requires the .088 vendor.img in order to boot. This is all in addition to the fact that A12 AOSP and GSI ROMs based on it are a work in progress and far from ready to be "daily drivers"
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
According to your report, maybe the wifi module violates some SELinux rules in Android 12. It is a good idea to get the logging of SELinux so that I can analyze and fix it.

The AOSP rom is built upon .088 vendor so that using the lower version of vendor may result in errors, bro!
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
I have updated wifi driver to the latest version with CAF. Here is the new built, please give it a try bros!

AOSP_Jan_27.zip
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
[deleted] will post later
[Essential Phone ROMs, Kernels, Recoveries, & Other] sansp00:
Here is a dump of dmesg with the latest version ... No apparent changes from the previous one. Hope it helps