yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
Yes. Here's what I did

- downloaded the Magisk APK directly to my phone from from https://github.com/topjohnwu/Magisk/releases

- installed the APK from local storage (renaming it to a .zip file and sideloading it seemed a less straightforward method)

- opened Magisk,

- APP was up to date: ver 22.0 - no further action needed

- Magisk showed Ramdisk N/A, and Install wants to Patch a file

- so, on my PC I extracted the Lineage image file and copied the "payload.bin" file to my Python directory

- opened Command.exe in the Python directory

- typed in: python -m pip install -r requirements.txt (which will check that Python is up to date)

- typed in: python payload_dumper.py payload.bin

- this unpacks "payload.bin" into the "output" folder, making "boot.img" for Lineage available.

- copied "boot.img" to the Download folder on my PH-1

- Clicked on Magisk/Install and then selected "boot.img"

- Magisk produced a patched boot image file, which I coped to my PC.

- Rebooted to the Boot Loader

- typed in: fastboot getvar current-slot (to check which slot was active... containing Lineage. In my case slot A)

- typed in: fastboot flash boot_a magisk_patched_xxxx.img (the xxxx bit are letters auto-generated by Magisk)

- Rebooted to Lineage

- Opened Magisk, selected the Settings icon, selected Magisk Hide.

- Opened SafetyNet Test app, and Passed the SafetyNet Test.
[Essential Phone ROMs, Kernels, Recoveries, & Other] life02:
Interesting, mine shows ramdisk: yes

I did try the patch method as well but appreciate you documenting it as I'm sure it will help others.

Maybe I need to reflash official FW and start over.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
Yeah, that's strange. I had to reflash Magisk after the update last night (it didn't stick), using the same method, and it worked again. You're trying with the Magisk-v22.0.apk?
[Essential Phone ROMs, Kernels, Recoveries, & Other] life02:
Yes using the latest v22.0 apk. I've also tried with the canary release. I tried a factory reset and got the same results. Reflashing back to stock Essential FW now (I was on lineage 17.1 prior to upgrading to 18.1).
[Essential Phone ROMs, Kernels, Recoveries, & Other] life02:
After relashing the official FW and flashing the patched boot.img, I was able to get Magisk working. I still have ramdisk: yes but the zip sideload method did not work.

Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Chirtan:
Unfortunately even after updating to the latest builds and trying this fix the network issues persist.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nullnull801:
LineageOS 18.1 was successfully installed.

However, it always freezes about 1 minute after opening Chrome.

I tried to initialize LineageOS 18.1 but it doesn't improve.

I tried reinstalling Chrome but it doesn't improve.

There was no problem with LineageOS 17.1.

Is there anyone in the same state?

Does anyone know how to improve it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
This issue with Chrome and many Chromium based browsers happened with other Android 11 ROMs for mata, also. It was a complete puzzle because only affected some PH-1 but not all, until this was found.

From that discovery, I found this. If you want to try this fix, the PQ1A.190105.112 is available here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nullnull801:
The problem was resolved using PQ1A.190105.112-NOVENDOR.zip. It's a very good fix. Thank you very much.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
It seems some mata users use last firmware from Essential, QQ1A.200105.032, because it's also free of the Chrome/Chromium issue. But I didn't try it because it breaks TWRP for this device.

Since you're using LOS recovery, maybe you'll like to try the attached firmware.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nullnull801:
I tried QQ1A.200105.032_Feb2020_firmware.

I didn't have any Chrome/Chromium issues with this firmware either.(y)
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
This just is not working out and I dont know why.

I flashed stock january 2020 so I could get twrp working. Flash twrp img and boot into recovery, no touch so I use a usb mouse. Flash Lineageos and gapps zips.

When system is booted up, theres no gapps.

Going back into recovery its in lineage recovery, you can only sideload there, but when I try to sideload, it says signature verification failed, so i hit yes, recovery flickers and adb no longer recognizes recovery. Ive tried also flashing twrp installer after lineage, but then it doesnt boot.

What am I doing wrong?
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
TWRP doesn't play well with LOS

I suggest you back to stock and use LOS recovery to sideload it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
im trying but when i hit yes on "signature verification failed install anyway?" los recovery restarts and nothing happens.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Forgive me if I ask this....did you follow exactly step by step in the LOS installation instruction?
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
To the extent that I could. Fastboot required flash:raw to flash boot images, never experienced that before but it worked. LOS recovery doesnt let me flash anything with sideload, everything is considered unsigned and when I hit install anyway, LOS recovery just reboots. I can flash twrp to boot_b, and only boot_b, it just bootloops if I flash on boot_a. But after flashing LOS with twrp, it switches back to slot a, could that be why I cant get gapps? I dont know.

I had to switch back to the the January stock build for now, maybe Ill try again in a few weeks, but I need my phone. Its getting time for a new phone, nfc died (a few other people had this problem, and a fix was never found), the screen is no longer attached to the phone as the glue holding it on has failed. I was looking into a dual screen LG phone, but now Im not sure if thats a good idea as its another phone company thats gone under, LOL.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
To be honest, I've never got LOS installation success with TWRP, and I always back to stock before sideload LOS rom.

I can recommend StatiXOS rom which is stable at this moment, even it's not 100% perfect, but at least you can use as daily drive. Besides, it's update regularly and with latest Android security patch.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Oddity11:
I came from the android 11 development build. And I did not use twrp either. I sideloaded LOS recovery into both slots with the raw command, and that worked.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JudasD:
I had the exact same issue as you and i found the result that helped me. Hopefully the below info will assist you as well.

I installed Jan on bot slots A and B, then TWRP on both A and B. I verified that the phone booted into the OS and TWRP was working.

In TWRP on slot A, i installed LOS18.1 and the mindthegapps. Upon rebooting, LOS18.1 worked, but i had no gapps. When i rebooted into recovery (LOS as expected) i notcied i was in slot B. I have seen this before and i thought i was mistaken untill it happened again! I tried the exact same steps but starting in slot b this time and noticed that the reverse happend and now i was not in slot a! Very strange!

What appears to be happening is that while in TWRP, LOS18.1 is actually installing to your opposite slot and the gapps are installing into your current slot. So to recap: you are in slot A TWRP. you install LOS18.1 and this installs on slot B. then you install mindthegapps which installs on slot A. When you reboot, it changes you to slot B where you will boot to LOS18.1 but the gapps are in slot A. This has to be a bug with TWRP as i can reproduce this every single time with LOS18.1 and with LOS17.1.

So now that i am in slot B with LOS 18.1, i boot into LOS recovery and install the mindthegapps via sideload. I was also seeing the error that you had seen until i did a hash check on my download file and it did not match! a redownload of mindthegapps fixed the issue.

I hope this helps you,

JD
[Essential Phone ROMs, Kernels, Recoveries, & Other] thiagobaur:
I'm having this freezing problem too.

I was at stock QQ1A.200105.32.

When you suggest try another firmware. You say that I have to go back to stock and start all over again? I mean... Back to stock and than reflash Lineage?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Chirtan:
So I was having issues with my mobile network connecting and disconnecting rapidly, eventually the phone would end up crashing to. I've messed around with this for a few days and have found a way to fix it. Ill best describe it here.

Mobile Provider: Telus / Koodo Mobile, Canada

1. Open device settings and click Network and Internet

2. Click on your carriers connection

3. Click access point names

4. Choose IMS (This is what stopped the network from freaking out)

5. I then switched my preferred network type to GSM/WCDMA/LTE

Now I'm able to stay connected to the network and the phone wont crash. However it appears every time I restart the device I need to repeat this process. If anyone can provide me with info how to stop this from happening itd be greatly appreciated.

Or perhaps where I could submit more information so this could potentially be fixed.

Thanks in advance I know this probably sounds crazy haha.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nitix007:
yeah exactly I posted this on reddit too but forgot to post the solution here aswell
[Essential Phone ROMs, Kernels, Recoveries, & Other] nitix007:
try this

```

I had the same problem, but I solved it by setting the APN type to the minimum "default,supl" according to the settings specified by my carrier. I don't know if this is the solution for all mobile services, but I think it's worth a try (depending on your carrier's service, there may be other required fields such as "mms").

``` from @hogehoge61

I also googled ur carrier, maybe try looking into it

Koodo Mobile - Canada APN settings - APN.how

Koodo Mobile Canada APN settings.

apn-canada.gishan.net
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
curious.

i couldn't wait, like i wanted to, and even though i've been reading about some issues, i backed everything up and decided to try to upgrade from 17.1 to 18.1, and install the beta of opengapps for android 11.

everything seemed to go well. i sideloaded the LOS18.1 zip image, rebooted to recovery, as instructed, then sideloaded the opengapps. this also seemed to go well.

where i am at now is the arc with sliding o's on the boot sequence. it's been doing this for about 10 or 15 minutes now.

normal as things set up? or is something amiss?
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
nevermind, i tried rebooting it and the same thing happened, so i factory reset and installed from scratch. all good now! just have to restore a bunch of stuff :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Chirtan:
So I went trough these steps, and same thing network goes crazy off and on until the phone crashes. Very odd problem. I hope some one else of Telus can provide some insite if they are experiencing this as well.

Does your phone maintain the settings upon reboot?

Thanks for the reply.
[Essential Phone ROMs, Kernels, Recoveries, & Other] R_THNDR:
I flashed 18.1 last night and everything works flawlessly except using VoLTE (T-Mobile, USA). Before the update I was still using the last build of LOS 16.0 with no issues.

When VoLTE is active, it sounds as though there is a mouse high on helium and meth on the other end of the phone. I tried this with the TMobile voicemail number and other phone numbers. It only manifests with VoLTE is enabled, whether wifi calling is used or not. Otherwise it's fine. With VoLTE disabled, I can make and receive calls with seemingly no issues. Installed per the instructions in first post using MindTheGapps.

Is this something I should wait and see if a fix comes in the next few builds?
[Essential Phone ROMs, Kernels, Recoveries, & Other] simanicu:
Upgrading from 17.1 to 18.1, following Lineage website flashing advice, alongside mingthegapps and Magisk package.

Been running 18.1 for 3 days now, and I can truly say that this feels like a rom that's well polished. Everything is working smooth, and quite surprised if I may say, it feels responsive like it was 3 years ago

Thank you!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
yeah i figured twrp was switching slots. its probably because thats what ota's do. twrp needs an option to switch back after flashing but thats not going to happen because its not being developed. my downloads are fine, but when i try to flash something with sideload in los recovery, it says its not signed which makes sense and it lets me hit "yes install anyway", but then it just reboots recovery. maybe if i could just turn off signature validation before hand in los recovery, it would just work, i dont know. but you cant do that in los recovery though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] DAE1964:
With los recovery you need to reboot to recovery after the ROM install. Then you should be able to install gapps and magisk.
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
Thanks for not reading anything I said. The problem is LOS recovery reboots when I accept unsigned sideloads.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Excelsis27:
If you mean a high pitched noise, kinda like coil whine, coming from the top speaker, I think that's an issue with the PH-1, as I've had that problem since I bought mine a couple years ago, on stock ROMs. Quick look around on google confirms that other people have had that same issue since the phone came out.

Not sure it would be possible to fix this, seems like a hardware issue...
[Essential Phone ROMs, Kernels, Recoveries, & Other] R_THNDR:
No, I don't think it is in the speaker hardware. I played around with changing APNs and toggling WIFI calling and VoLTE. It seems like it's something with VoLTE specifically. When VoLTE is on, all calls (in and out) sound as though the audio signal has been drastically sped up, and then the time stamp realigns so there is a squeaky pulse of audio that roughly aligns with the voice on the other end. When VoLTE is off, I can call and hear the other end just fine.

I can only assume it's something with LOS 18.1 as I didn't have this issue on LOS 16.0. There are a few bug reports for other devices on TMobile. I'm not sure if I should as this as one or not. It's been ages since I've done much in the way of flashing custom roms.
[Essential Phone ROMs, Kernels, Recoveries, & Other] DAE1964:
I did read your posts. I had that happen once because I didn't reboot between installing the ROM And Gapps. The problem is when installing a ROM with TWRP or Los recovery it installs to the opposite slot so you must reboot to recovery and then install Gapps.
[Essential Phone ROMs, Kernels, Recoveries, & Other] The Jack of Clubs:
Ive done that. LOS recovery still reboots when accepting unsigned zips.
[Essential Phone ROMs, Kernels, Recoveries, & Other] DAE1964:
Just for fun. I reinstalled stock then followed the procedure to install lineage OS 18.1 to a t and I'm up and running again. Maybe the issue is with the mind the g apps version.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mervinb:
I have updated from official 17.1 to 18.1. A clean install was needed.

The chrome freeze means I can only use the LOS browser for now. This freeze also occurs with Vivaldi browser.

Magisk installed without issue via LOS recovery update (I renamed the .apk to .zip).

If the browser freezes can be addressed, it looks like this will be a solid ROM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
this is so minor, that i almost don't mention it. but it's also a tidbit of information that may be useful to know.

somehow, the sound panel got to the left side of the phone, when i use the volume up/down buttons. i'm already used to it so , on a scale of 1 to 10, it's a zero...but still...i am curious what i did.
[Essential Phone ROMs, Kernels, Recoveries, & Other] thiagobaur:
Netflix doesn't work?

Only notice now!
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
It seems there's now a setting for this, "Show panel on left" under Buttons, in Settings.

Chrome is working fine for me, no crashes. Some Google apps had this crashing problem a few weeks ago, fixed by an update to Android System Webview and Chrome. Not sure if some are still experiencing this because they didn't update, or if they're experiencing a different issue.

Gmail, Chrome and other Android apps are crashing — how to fix it now

Gmail and Chrome apps keep crashing? No worries, we've got the fix

www.tomsguide.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] moichman:
yep. it was right there. i had previously looked under sound.

thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] mervinb:
Apart from its relatively poor battery performance, my PH-1 with Lineageos 18.1 is exceeding all expectations!

While my Pixel 4A is awaiting service for dodgy volume and power buttons, it's serving me well. But there are a series of gotchas to getting a frustration-free experience:

1. Installation:

Using linux adb, I was failing all the time at fastboot flash boot. The solution is that the newest linux adb has a different option for flashing boot:

# fastboot flash:raw boot_a lineage-18.1-20210412-recovery-mata.img (your image version may vary)

2. Chrome (and Vivaldi browser) freeze - 100% consistent on both my PH-1, one coming from Lineageos 17.1, the other from stock ROM:

Using the QQ1A.200105.032 fastboot zip, extract the modem image (modem.img)

# fastboot flash modem_a modem.img

# fastboot flash modem_b modem.img

3. Installing and updating Magisk:

I couldn't install using the latest standard method (extract boot.img / patch / flash), presumably because I had not found the new "flashboot flash:raw" syntax at that time. My guess is that it would work. However the rename magisk.apk to .zip / recovery / apply update method did work.

To keep Magisk through an OTA update:

- Uninstall Magisk

- Download and install OTA update, but do not reboot

- Install Magisk (from the app), using the 3rd option (Install to Inactive Slot after OTA); Magisk reboot

Hope this reduces frustration and significant search / trial and error time for some of you.

(It would be really useful if the most current tips are kept on the original post #1)
[Essential Phone ROMs, Kernels, Recoveries, & Other] thiagobaur:
Hello man. Thank you for the tips!

Can you please give us more details about the freezing chrome issue?

I also came from stock QQ1A.200105.032 but I'm having the problem. I'm not sure how to flash firmware without losing the current rom. Also not sure of what file I should flash.

Thank you
[Essential Phone ROMs, Kernels, Recoveries, & Other] mervinb:
What I posted is fairly comprehensive if you've used linux to install lineageos in the first place:

Using the QQ1A.200105.032 fastboot zip, extract the modem image (modem.img)

# fastboot flash modem_a modem.img

# fastboot flash modem_b modem.img

Sorry, can't help if you're on Mac or Win. The commands will be similar. You may want to read some articles on using fastboot, so that you have a better understanding what the two lines of fastboot commands are trying to achieve.
[Essential Phone ROMs, Kernels, Recoveries, & Other] thiagobaur:
Thank you!

I'm on windows but the commands are very similar.

I'm try that and see what happens.

What still strange for me is that I was at QQ1A.200105.032. So I assumed that it wouldn't be necessary.

Let's see.

Thank you again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mervinb:
If the next OTA update brings back the chrome issue, then we can surmise that the lineageos zip includes a modem blob that causes the issue. If not, then I too wonder why..
[Essential Phone ROMs, Kernels, Recoveries, & Other] mawdogbe:
From what I can tell, Chrome freezing has nothing to do with any particular ROM. I've never had the issue with any ROM I've tried on Mata. The key is to flash the stock January firmware and then flash the February vendor file before doing anything with ROMS. This also lets you use touch in TWRP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 谷歌原生:
I installed the latest version, but Google Maps is still unable to locate
[Essential Phone ROMs, Kernels, Recoveries, & Other] 谷歌原生:
I installed the latest version, but Google Maps still can’t locate GPS
[Essential Phone ROMs, Kernels, Recoveries, & Other] jbloggs2008:
Has anyone been able to successfully pass SafetyNet? I can't even pass basicIntegrity
[Essential Phone ROMs, Kernels, Recoveries, & Other] npjohnson:
that means whatever zip you're installing is corrupted.
[Essential Phone ROMs, Kernels, Recoveries, & Other] good4y0u:
Do we know if the browser issues is fixed ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] thiagobaur:
Yeah. It can be fixed. I had the problem and now I don't.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Pairman:
Having flashed the modem images of January QQ1A.200105.007 and then Feburary QQ1A.200105.032.

However chrome still constantly freezes. Good news is that this time it at least shows a "chrome isn't responding" dialogue, and bad news is that the issue occurs more severely.
[Essential Phone ROMs, Kernels, Recoveries, & Other] exillity:
Same problem here.

Update: seems like the problem with the magisk itself.

Latest canary build should fix the issue: Latest Debug (Canary)
[Essential Phone ROMs, Kernels, Recoveries, & Other] F_S:
I just wanted to say how exceptional this ROM is. I left it a few weeks to upgrade from 17.1 but it went flawlessly.

I forgot that the USB-C cable that came with the phone doesn't play nice with ADB, but once that was swapped out, the upgrade zip file sideloaded and updated perfectly and MindTheGapps too. All without losing any data or settings. I'm using Edge browser for work and Firefox for personal and had no issues with either. Audio via the USB dongle works fine too, as does SMS via Volte. Perfect.

The LineageOS team are absolute legends. Thank you.
[Essential Phone ROMs, Kernels, Recoveries, & Other] npjohnson:
I just can't replicate these...

Are you flashing something with the ROM, or firmware afterwards or something?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mervinb:
I have 2 units of PH-1, and I experienced the browser freeze on both of them. Both were updated to the latest version of stock Essential Android before moving to Lineageos. One was flashed with Lineageos 17.1, and the other remained on stock. Then both were installed with 18.1.

To remove the freeze, I used the QQ1A.200105.032 fastboot zip, from which I extracted the modem image (modem.img)

(linux)

# fastboot flash modem_a modem.img

# fastboot flash modem_b modem.img

This corrected the browser freeze on BOTH phones (latest stock -> 17.1 -> 18.1 and latest stock -> 18.1). I have to suspect it's the modem binary on the latest stock that somehow causes the issue.

The browser issue have not returned after Lineageos OTA updates on 0412 and 0419.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jbloggs2008:
(Sigh) didn't work for me. Brave keeps freezing after a minute. On 0419 with Magisk installed. Anyone else have any luck?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Pairman:
Flashing modem didn't work for mine either and I don't know why.
[Essential Phone ROMs, Kernels, Recoveries, & Other] SirDigitalKnight:
Post in thread 'New StatiXOS OFFICIAL 4.2 build for Essential PH-1' https://xdaforums.com/t/new-statixos-official-4-2-build-for-essential-ph-1.4242099/post-84595559

This might fix it as it seems to fix the Chrome issue on other Roms
[Essential Phone ROMs, Kernels, Recoveries, & Other] Chirtan:
Anyone else's gps unable to "go to/find my location"?