yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] rknuovida:
so the steps will be

adb devices

fastboot -w

fastboot flash boot twrp-mata_11.img

<boot twrp> whats the command for this?

wipe system/data/cache

<flash rom> adb sideload file..zip <is this correct?>
[Essential Phone ROMs, Kernels, Recoveries, & Other] TJSteveMX:
first flash or sideload Oreo, can be OB2 but i suggest go to latest

then make sure USB debugging is enabled on developer options

after that, type:

adb reboot bootloader

this will take you to bootloader and since you just recently flashed Oreo im assuming your bootloader is unlocked

then you can type

fastboot -w

fastboot flash boot twrp-mata_11.img

then with your volume buttons go to boot to recovery

now once in recovery mode, type on your PC:

adb push <rom name>.zip /sd card/

wait like 3-5 minutes

then once it finish (you will noticed once line prompt start bling on your path) you can wipe if you want but we already wiped all.

now you can flash the rom located on your sd card folder on TWRP.

if you want root then follow the steps on OP about root
[Essential Phone ROMs, Kernels, Recoveries, & Other] rknuovida:
Thanks again for all the support.

quick one - I need to unlock boot loader before side loading the Oreo beta?

regards
[Essential Phone ROMs, Kernels, Recoveries, & Other] TJSteveMX:
I believe you don't need to since you sideload on stock recovery, the steps can be found on essential.com/developer/overview under beta builds

You need adb only to sideload on stock recovery.
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertzas:
I followed the directions for how to root, but when I get into twrp after booting up the first time and setting up, it asks for my password (to decrype) but doesn't accept it. I've tried several times and am sure I am using the right one. Is there something else I should be doing?
[Essential Phone ROMs, Kernels, Recoveries, & Other] TJSteveMX:
Flash boot.img and reboot, you need to disable fp unlocked or pin/password from settings
[Essential Phone ROMs, Kernels, Recoveries, & Other] DaveHTC200:
The latest boot.img looks really small! Ive pulled my own to root just in case
[Essential Phone ROMs, Kernels, Recoveries, & Other] blakeatl:
[MENTION=2903821]xlxfoxxlx[/MENTION] The new boot.img is only about 20mb. Is that the correct size as it's 1/3 the size of the 1/14 version.
[Essential Phone ROMs, Kernels, Recoveries, & Other] xlxfoxxlx:
For some reason when pulled from ROM its the 60+ but the ones I take from my out directory when building are 2# both are fine
[Essential Phone ROMs, Kernels, Recoveries, & Other] rknuovida:
screen takin Long time to turn back on

Well, have been able to install the room - root it with magisk and have the xposed framework .

Everything seemed ok , but having the following issue now:

- Once I leave the phone unattended, it goes into deep sleep. Meaning if I pick the phone the screen wont turn on, If I use the finger print, I hear the unlock sound but the screen is blank, pressing the power button on and off - no effect

- It takes about 10-15 seconds before the screen turn on.

- or else I have to reboot it by pressing the power button,

All the help will be really appreciated.

Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] mackentosh:
Are you using some type of immersive mode for the navigation bar?
[Essential Phone ROMs, Kernels, Recoveries, & Other] rknuovida:
yes using the full immersive mode from the quick settings.
[Essential Phone ROMs, Kernels, Recoveries, & Other] dandan2980:
Seems to only happen with full immersive mode enabled

---------- Post added at 06:59 AM ---------- Previous post was at 06:48 AM ----------

Very fast and stable Rom. I personally have set the CPU governor to Conservative, and the GPU is set to performance, I also have CPU boost option so all cores are set in the upper 1400's frequencies. Using Ex Kernel manager. Only setting that sticks after a reboot is the governor but I just manually return the rest to my likings. I was worried after I first installed the Rom cause it felt laggy in certain areas mainly the keyboard but after it settles in that goes away and I also believe I read in another thread that opening the camera app helps take care of the latency that people experience after install or a reboot.

Loving the Fling Navbar too, pretty sweet. Thanks to the Dev making this Rom available for us.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jrodbrown58:
I didn't unfortunately, I had to 1 day ship it off Amazon. Came in today and I fixed it.

On the other hand though, I am on the newest update and my phone starts acting sluggish and then the screen goes black and I have to reboot my phone in order to use it again. Anyone else having this issue? Or a possible fix? Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] jrodbrown58:
Update: it gets stuck on finishing the update and freezes my phone up and started the finishing the update again and does the same thing.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
Newest AOSiP build (2019-03-10) is working fine on my PH-1, after a dirty flash using TWRP.

Thanks, devs!!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] TheDude1998:
I've had a similar issue, where the system time doesn't update until the phone is unlocked
[Essential Phone ROMs, Kernels, Recoveries, & Other] jrodbrown58:
I just updated to the newest build and it's doing the same thing. It will freeze and screen will not come on, I either have to reboot the phone or wait and when it does eventually come back on where I can use the phone it resets the finishing system update and after a while freezes again and starts the process over. I'm at a loss on what to do. I do not want to lose my data and I've tried wiping cache and system several times and still same issue :/
[Essential Phone ROMs, Kernels, Recoveries, & Other] knift:
Maybe you can do a TWRP backup and wipe out all system, data and cache partitons. If it's ok after the wiping, then you may restore the backup data or reinstall one by one. If it still goes wrong, you should flash back to stock rom and ask for warranty.

In my Ph-1, it's no issue like yours.
[Essential Phone ROMs, Kernels, Recoveries, & Other] TheDude1998:
Updater working great for me, haven't even bothered to reinstall twrp for the last three builds not used to that xD

Hate the lineage snap app tho

But anyways, I'm having a bug where my Bluetooth headphones are always Max volume on connect, same thing when using the aux dongle, anyway I can fix this myself? Ver. 190305.002
[Essential Phone ROMs, Kernels, Recoveries, & Other] Wh1t3Rose:
See if your clock app is listed as being battery optimized and turn it off offif it is.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sk801:
I finally fixed my Bluetooth problems from last month.

For anyone having connectivity issues or any buggyness with Bluetooth, try changing your AVRCP to the latest version (as of right now I'm using 1.6) then perform a reboot. It's been working flawlessly for a couple days now.

The AVRCP can be changed in the developer options.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
Very loud speakerphone

I've been noticing my PH-1 speakerphone is very loud, even at the lowest volume. It seems audio and volume configuration is stored at vendor/etc/mixer_paths_tasha.xml, so I read this file and found this section has a way higher value than the initial volume setting (84):

<path name="speaker-mic-liquid">
<path name="dmic2" />
<ctl name="DEC7 Volume" value="111" />
</path>

Could this be related to the very loud speakerphone? I don't want to change the value blindly as I have no idea of the possible side effects.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
New build is up

I updated my PH-1 to the newest AOSiP build (2019-03-18) by dirty flash using TWRP, as usual, and it seems everything is working fine. Thanks again, devs!!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] varxx:
I used the updater to go to 20190318 from 20190310. All went fine, except that TWRP seemed to have been zapped somehow. When I rebooted to recovery it went to stock recovery.

Is there a simple way to keep TWRP after I use the updater to update AOSiP?

Very nice ROM, by the way. And I appreciate having an updater, assuming I can figure out how to keep TWRP.

Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bobbaloo:
Agreed. All good here too
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I believe the Magisk manager allows you to flash Magisk to the other slot before you reboot after an upgrade. If so, then you can do that.

I want to say there's also a Magisk module based twrp installer floating around that does just what the installer zip you flash in twrp does. You could run that installer through the newly updated and rooted OS after you boot into it.

I could be way wrong about the twrp installer, though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
I not sure if this could help, but it looks promising: Franco Kernel Manager and EX Kernel Manager are recently offering the option to flash ZIP format mods directly from the apps, when root is available. So, I guess it could be possible to flash TWRP zip to the kernel after an AOSiP OTA update. Check this article for more information: https://www.xda-developers.com/franco-kernel-manager-flash-zip-without-recovery/.

I haven't tried this idea, so it's just a wild guess.
[Essential Phone ROMs, Kernels, Recoveries, & Other] marcdw:
Maybe this is what you're referring to? In the OP of osm0sis' thread...

TWRP A/B Retention Module script

https://xdaforums.com/showthread.php?t=2239421

Haven't tried it as I don't use Magisk.

Essential PH-1, /e/ 0.5-n ROM, microG (NoGapps), XDA Legacy
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bobbaloo:
TWRP installer can be found in essential development chat on telegram. I Flash it immediately after rom in the same session all the time. It does what's needed
[Essential Phone ROMs, Kernels, Recoveries, & Other] varxx:
That works when you're flashing a ROM from Recovery or otherwise. But my question was about how to retain TWRP when you use the AOSiP updater to move to a newer ROM release.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bobbaloo:
I "export" it to a folder and flash it in TWRP. I'm leery of doing it Ota for fear of losing it
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Exactly. I was trying to help come up with a point and click (touch?) way to regain TWRP without needing to fastboot, sideload, or use TWRP for the OTA
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bobbaloo:
My method described above

---------- Post added at 12:32 AM ---------- Previous post was at 12:30 AM ----------

Not my method by far, lol. The one I use
[Essential Phone ROMs, Kernels, Recoveries, & Other] foueddyf:
If you need to go to TWRP after updating via the updater, might as well flash everything in TWRP instead of using the updater, or am I missing something?

The updater is really for people that use stock AOSiP (no rooting, no modified kernel, etc...), and not needing to flash anything, hence not needing TWRP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bobbaloo:
I've seen updates in the OTA that weren't released here or on the telegram channel. Download and flash in TWRP
[Essential Phone ROMs, Kernels, Recoveries, & Other] varxx:
Yeah, you're right. I was just intrigued that a custom ROM had an updater, but I used it before realizing what should have been obvious, that I'd lose my custom recovery. This isn't a huge deal, as you say.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
The possibility to flash ZIP format mods (including custom kernels and maybe TWRP) using Franco Kernel Manager or EX Kernel Manager new feature, when root is available, could be an excellent complement to the OTA Updater. I just haven't been brave enough to try it, as I mentioned before.
[Essential Phone ROMs, Kernels, Recoveries, & Other] foueddyf:
Yeah.

I personally flash everything via TWRP because I like to make a backup before flashing anything.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Bobbaloo:
Yep. And flash root.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
If you flash my zip after magisk... You TWRP loop... So you'd have to uninstall magisk from the manager to stock kranel... Then flash that installer... Then reflash magisk

Osmosis's zip works before reboot but after applying update... And before you flash magisk to the other slot thru the manager
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertelam83:
Can anyone confirm the latest AOSiP release for MATA has "OK GOOGLE" fixed?
[Essential Phone ROMs, Kernels, Recoveries, & Other] boybill:
I just tried it on the March 18 build. It worked
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertelam83:
Nice. Thanks for the response.
[Essential Phone ROMs, Kernels, Recoveries, & Other] knift:
This is the most stable custom ROM I ever flashed. Great job!
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertelam83:
I clean flashed the 3/18 AOSiP mata official build however OK GOOGLE wasn't working. Dirty flashed today's (3/25) update and Google play services repeatedly crashed.

When using the ROM installer what's the process to install it without losing twrp/root?

Thanks in advance
[Essential Phone ROMs, Kernels, Recoveries, & Other] knift:
Which launcher r u using? I use NOVA, after checkinging the "OK, google" setting in the "gesture and input" , this feature works great.

It's look like you flash the ROM without flashing Gapps, and it will cause many errors and crash.

If you want to keep twrp and root, flash the rom in twrp rather than rom updater.
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertelam83:
Ah ok I didn't check that in Nova. But with AICP OK GOOGLE works without issues. With AOSiP I couldn't switch it on in the Google app. I flashed PICO gapps. That may have been the issue
[Essential Phone ROMs, Kernels, Recoveries, & Other] knift:
I flash nano Gapps, and no issue.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Zahidow:
i installed beautiful rom but gapps not loaded
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Install rom in twrp. Flash twrp j installer zip in same session.

Reboot to RECOVERY.

Install gapps and Magisk (if desired).

Reboot to system.
[Essential Phone ROMs, Kernels, Recoveries, & Other] agmyers76259:
Can you confirm PRL and service updates are working for SPRINT users? Back in January it appears service was not functional. Please advise and TIA. :D
[Essential Phone ROMs, Kernels, Recoveries, & Other] Zahidow:
Thank you. I did finally :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Those do not work. If you want to update prl and profile, you need to use stock
[Essential Phone ROMs, Kernels, Recoveries, & Other] tqwzUX6fn39GZMEzSnDF:
I've just moved from March Stock. Everything seems to be fine so far, thank you very much team AOSiP, except Gcam doesn't start / crashes at startup. In GCam thread typically answer is to delete cache / data of gcam, but this didn't solve my problem. Anyone has working gcam?

If so, do you have any gapps installed (I don't)?
[Essential Phone ROMs, Kernels, Recoveries, & Other] knift:
I installed nano gapps and gcam, both worked well. No problem.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tqwzUX6fn39GZMEzSnDF:
OK, thanks. I've searched for some more information and think (most) gcam require some gapps installed :(

Edit: Works if microG Services Core is installed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] robertelam83:
Yup that did it. Thanks bud. ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Netflix working for anyone else?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
I just checked and it's working fine on my PH-1 with latest AOSiP build and Magisk.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Odd. It force closes for me instantly on a fresh, clean install of the 3/25 build with 3/25 mini gapps.

Magisk canary build

A Java librealm error, but I haven't grabbed logs yet (my daughter is hogging my pc and getting an adb log is easier there
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
By the way, I have SELinux enforcing.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I'll try toggling from permissive. But, I'm not hopeful. What gapps are you using?

Switching to enforcing took care of it. Now to see if it affects anything else.
[Essential Phone ROMs, Kernels, Recoveries, & Other] marcdw:
Yeah. Google App needs to be a system app for OK Google to work. Nano would be the smallest GApps package if one ever needs that function.

ZTE Axon 7 A2017U, /e/ 0.5-n ROM, microG (NoGapps), Multiboot, XDA Legacy
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Do you manually set it to enforcing on reboots, or is there any easy way to automatically set it to enforcing on boot?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
I switch SELinux to enforcing manually with a terminal app, on every reboot (just because I reboot my device rarely). But I know there's an app developed to change SELinux mode automatically on boot: https://xdaforums.com/android/apps-games/app-selinux-switch-t3656502.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I realized after asking that I can just use the "run shell" action in Tasker at boot to run "setenforce 1" as root...

Derp.

Added bonus of not having to install any apps or Magisk modules, since I already have Tasker installed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] killer86th:
Hello guys, I just came back to the rom yesterday and it has been awesome so far.

Can someone help me by pointing out how to enable Pie navigation (the pill one)?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Owls nest, gestures, aosp gestures, home button
[Essential Phone ROMs, Kernels, Recoveries, & Other] BastardRacoon:
Does instant tethering work with supported chromebooks on this rom?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Hmmmm.

Got this fun log snippet after updating the Magisk Manager and Magisk to the most recent versions earlier today. Rebooted around 3;15 PM and I can't boot back into the system.

I was running the Canary build prior to this, and updated via direct install to .. I don't even know. I'm going to uninstall the manager app after reflashing the ROM and then try installing Magisk 18.1 and Manager 7.0.0 and taking the updates it gives me. That's assuming that reflashing without Magisk fixes the problem in the first place.

--------- beginning of crash
11-18 19:35:45.419 817 846 F libc : Invalid address 0xe687f918 passed to free: value not allocated
11-18 19:35:45.419 817 846 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 846 (magisk.bin), pid 817 (magisk.bin)
11-18 19:35:45.477 849 849 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-18 19:35:45.477 849 849 F DEBUG : Build fingerprint: 'essential/mata/mata:9/PQ1A.190105.014/451:user/release-keys'
11-18 19:35:45.477 849 849 F DEBUG : Revision: '1.8'
11-18 19:35:45.477 849 849 F DEBUG : ABI: 'arm'
11-18 19:35:45.477 849 849 F DEBUG : pid: 817, tid: 846, name: magisk.bin >>> magiskd <<<
11-18 19:35:45.477 849 849 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
11-18 19:35:45.478 849 849 F DEBUG : Abort message: 'Invalid address 0xe687f918 passed to free: value not allocated'
11-18 19:35:45.478 849 849 F DEBUG : r0 00000000 r1 0000034e r2 00000006 r3 00000008
11-18 19:35:45.478 849 849 F DEBUG : r4 00000331 r5 0000034e r6 e687f8ac r7 0000010c
11-18 19:35:45.478 849 849 F DEBUG : r8 e6c13288 r9 00000332 r10 e6a1a9c8 r11 00001000
11-18 19:35:45.478 849 849 F DEBUG : ip 00000000 sp e687f898 lr e6d2d039 pc e6d24ed6
11-18 19:35:45.489 849 849 F DEBUG :
11-18 19:35:45.489 849 849 F DEBUG : backtrace:
11-18 19:35:45.489 849 849 F DEBUG : #00 pc 0001ced6 /system/lib/libc.so (abort+58)
11-18 19:35:45.489 849 849 F DEBUG : #01 pc 0007df69 /system/lib/libc.so (ifree+880)
11-18 19:35:45.489 849 849 F DEBUG : #02 pc 0007e087 /system/lib/libc.so (je_free+70)
11-18 19:35:45.489 849 849 F DEBUG : #03 pc 00008955 /system/lib/libsqlite.so (sqlite3_free+60)
11-18 19:35:45.489 849 849 F DEBUG : #04 pc 00008d05 /sbin/magisk.bin
11-18 19:35:45.489 849 849 F DEBUG : #05 pc 00008f11 /sbin/magisk.bin
11-18 19:35:45.489 849 849 F DEBUG : #06 pc 0000923d /sbin/magisk.bin
11-18 19:35:45.489 849 849 F DEBUG : #07 pc 00064389 /system/lib/libc.so (__pthread_start(void*)+22)
11-18 19:35:45.489 849 849 F DEBUG : #08 pc 0001e099 /system/lib/libc.so (__start_thread+24)

---------- Post added at 06:59 PM ---------- Previous post was at 06:38 PM ----------

Removing Magisk and the Manager app didn't help at all. Guess it's time to dig deeper in the logs
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
After a boat load of attempts to recover, I ended up having to wipe user data and set up the device as new.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tqwzUX6fn39GZMEzSnDF:
Magisk 19 from auto-update?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Yeah. And I'm currently running that same Magisk version.

I have no idea what actually happened to break everything, but i don't think it was Magisk related, so much as Magisk manager was affected by it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MadsMann:
I had updated to version 19 also, I went to install the 3/25 update of AOSiP and got the red corruption warning. Ended up having back to stock and just installed the 18.1 stable version and all's well. Going to flash 19 again and see if I can duplicate it
[Essential Phone ROMs, Kernels, Recoveries, & Other] tqwzUX6fn39GZMEzSnDF:
I'm on Manager 7.1.1 and Magisk 18.1. Both are shown as up to date. If update information for 19.0 will come, I guess I'll not apply to it until you / someone found out what causes the problems.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
Magisk version 19.0 is already available at the beta channel. If your device is at the stable channel, the current version is 18.1.

My PH-1 with latest AOSiP build is using Magisk 19.0 since it became available at the beta channel and everything seems to be working fine. I only saw a reboot yesterday, but I think it was related to a rogue app.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I'm pretty sure that v19 isn't the problem anyway. That's just the first crash log I saw while trying to get a log via adb while attempting to boot.

It may have been related to upgrading the manager while it was repackaged as a random apk name.

Or, it may have been completely unrelated.

I ended up randomly losing my signal while working in Goodyear's HQ, so I looked for an open wifi network.

There was one, but it required guest sign in information that I didn't have. Turned wifi off and toggled airplane mode to try and reconnect to my carrier. Phone crashed and rebooted, but it wouldn't finish booting.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Ext4 or F2FS?

I ask because your encryption might have died...
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Ext4
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Could you get into TWRP?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Definitely. I was able to use adb during the boot cycle as well. Fastboot worked fine. TWRP worked fine. I just couldn't boot into the OS
[Essential Phone ROMs, Kernels, Recoveries, & Other] Admiral2145:
The new 4-1 build has the latest April security patch?
[Essential Phone ROMs, Kernels, Recoveries, & Other] killer86th:
Thank a lot man, I keep going back and forth Navigation settings, no wonder I couldn't find it :p

It's still March security patch, doesn't bother me though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] TheDude1998:
Anyone get viper4androud working?