yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] eqbirvin:
I was considering doing this actually! So you used the stock package?
[Essential Phone ROMs, Kernels, Recoveries, & Other] eqbirvin:
I did this and it fixed my issue. That's really weird. Thank you!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
Happy it helped.
[Essential Phone ROMs, Kernels, Recoveries, & Other] shoeprano27:
is the boot image available to dl for the latest build or will i have to retrieve it myself?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Deandre7452:
Pull it yourself if you want to
[Essential Phone ROMs, Kernels, Recoveries, & Other] Obamaloominaty:
Yeah, you'll have to pull the boot image yourself.

There's a guide on how to do that here: https://xdaforums.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976/page111
[Essential Phone ROMs, Kernels, Recoveries, & Other] shoeprano27:
thats the same guide i was gonna use. thank you sir
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Not sure if this is normal, or if anyone else is experiencing this (bug?). Play store shows my device as uncertified, yet it's able to pass safetynet via Magisk (version 16 stable release), and Android pay works with no issues. Netflix did not install from Google cloud restore, but I was able to manually download it from the play store without sideloading it and it works just as well. Anyone else noticed this? Is it even normal in Oreo. I know on nougat, any uncertified device meant no safetynet pass. Its not effecting device performance in any way here.

Also noticed the "preserve Force encrypting" box enabled on the main Magisk manager screen, under advanced settings section. If I uncheck that, would it really unencrypt? Not even sure if this device even can be unencrypted any other way. Used to be that a simple formatting wipe would remove device encryption, but on this device that doesn't seem to be the case.

Would be cool if anyone can chime in on these two topics
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
Non stock roms (including stock betas) always say uncertified as far as I know. When I had an s8 and was on the Oreo beta it said uncertified as well.

I think something is coded into the rom itself that tells play store that it's certified as far as I know
[Essential Phone ROMs, Kernels, Recoveries, & Other] DannyMeercat:
Got this rom going yesterday. So far it's great. I have only noticed one minor issue. Can't figure out if it would be rom or kernel specific, or if it is related to the bluetooth bug that was causing deep sleep issues. Bluetooth works, just no controls. Play/pause/skip/volume. I wear headphones at work and use bluetooth in my car. All the functionality has been lost. Just curious if anyone else is experiencing this, or if I'm just overlooking something.
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
My Bluetooth headphones work alright. Try the setting under configurations/interface/buttons for screen off volume just to see if that helps?

Also I believe there is a setting under connected devices/Bluetooth as well that pertains to this
[Essential Phone ROMs, Kernels, Recoveries, & Other] DannyMeercat:
Messing around in the configurations menu I did end up getting the volume buttons to work on my headphones. So far that's it. Just messing around, I did notice a new problem. I was trying to access app permissions in the settings and any time I try to mess with anything involving permissions i get a Package Installer force close. Hmmm.. lol
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
Change theme back to white. Then do your permission stuff
[Essential Phone ROMs, Kernels, Recoveries, & Other] DannyMeercat:
Thank you! So simple lol. What a strange thing.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Interesting, pretty much what I figured. Just never knew it's a normal occurrence.

Any idea about the encryption check box in magisk manager?

Would unchecking it really unencrypt data? I'm under the impression that there is no way to keep the device unencrypted. Thanks for the info
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
I'm not really sure about that, might be better to ask in the magisk thread. I'm not going to touch it though ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
The uncertified device...

Clear data on play store... Problem solved
[Essential Phone ROMs, Kernels, Recoveries, & Other] shoeprano27:
I'm not sure why I can't change my DPI, even adding the ro.sf.LCD blah blah line in build.prop. can anyone help?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Cool, didn't even occur to me for some reason. That used to be the first thing I'd consider, but knowing how Magisk would be the deciding factor for play store certification with root access enabled, at least on nougat and I think marshmallow, I just didn't even consider this option. Well I just tried it and sure enough play store says certified, so thank you [MENTION=3290808]rignfool[/MENTION] for the tip.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CtDMonet:
I'm curious about this too. I had RR on my old S5, and used the hotspot all the time. The Essential has it activated from Sprint from the box, however it limits it to 10GB/mo or roundly what a 10yr old can pull off Netflix/youtube in half a day if on a roundtrip and streaming his iPad off your hotspot (as I found out). Then Sprint asks you to upgrade.

I'm looking for unlocking the hotspot as well.

Other than that, I love the essential.
[Essential Phone ROMs, Kernels, Recoveries, & Other] codep0et:
Rom stability + firmware

I was wondering after reading alot and alot of the posts here if the stability of the rom as of now is fine for a daily use ?

Also the instructions of the OP says to flash the firmware OPM1.180104.092 even if you are on it, but I am on OPM1.180104.141 which is more recent, so I shouldn't flash it right ?

Thanks guys
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Hot spot's working great with T-Mobile data, not sure how it'll fare on sprint, should work in either case, just depends on yiur data plan and whatever sprint allows i suppose.

---------- Post added at 07:01 PM ---------- Previous post was at 06:49 PM ----------

More than fine. It's running perfect, I'd say almost 100%. A few small issues like system UI crashes in see custom configuration settings like theming crashes on me when I try to change the theme text color from blue to say other color, but the black and dark backgrounds week just fine. Never had any reboots or system hangs, nothing bizarre like that.

Try following my guide a few pages back, the only thing I forgot to mention there, is to wipe data and system partitions after you first flash TWRP boot. Or if you can, follow [MENTION=3462598]BakedTator[/MENTION]'s instructions page or two before mine, it has the whole outline to the t, mine just has all the in between specifics
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
I 100% agree with you. The issues you mentioned are really the only problems I have run into. This ROM is extremely stable and is my daily driver.
[Essential Phone ROMs, Kernels, Recoveries, & Other] fredgar75:
I sent you a PM
[Essential Phone ROMs, Kernels, Recoveries, & Other] codep0et:
Thanks alot, I had RR On my nexus 6P and it was great. Happy to see that on Essential its working good.

I read Both guides and no mention of flashing thr firmware so i just ignore that ?

Also my guess is that our camera notch we have is compatible with this rom ?

Thanks again for your answers
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Seriously, makes it hard to justify staying on stock. Unless "okay Google" voice access with screen off and a slightly better battery life are a priority over everything else.

This ROM actually fixed Bluetooth connectivity on Android 8.1 for me (huge plus), works without interruption now. Battery isn't too bad either, just that all the extra features enabled consume more power than if they were off. I was getting better battery life in RR before I set everything up, so I know this ROM can be just as good on battery as stock essential Android, but then again, you don't simply pick this ROM for battery efficiency as a priority.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
I have the multi touch bug from 8.1 and custom software was the only way to fix it. AOSIP and RR ROM have stopped me from selling this phone. RR in particular is one of my favourite ROMs and I've been flashing on a lot of phones for quite some time now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Same here, i was on the verge of selling this device after a few days and either get a 1+5T or Razer (which is a bit lacking in custom firmware atm)
[Essential Phone ROMs, Kernels, Recoveries, & Other] crixley:
I could never go back to stock. The crap immersive mode on stock makes it useless to me, let alone the scrolling. If I was stuck on stock I would have sold this phone.

With neutrino I get just as good as stock battery too.
[Essential Phone ROMs, Kernels, Recoveries, & Other] charlatan01:
Just curious if anyone else is having the same issue. I may give this another go if I can figure this out. Maybe just a bad flash?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
No issues here on trailforks. I flashed stock bts and updated to April security update then wiped. Flashed ROM, rebooted to bootloader then flashed stock gapps. Sounds like your install screwed up somehow.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ashwin Prabhunerurkar:
Build 4 with may security patch is ready

I need someone to test it since i am on android p

PM me if you are not a noob and can flash my build without trouble
[Essential Phone ROMs, Kernels, Recoveries, & Other] Archangel:
Finally got around to flashing this and everything works perfect so far. Used [MENTION=3462598]BakedTator[/MENTION] guide to flashing and it worked perfect!

Just one question,,,is the lockscreen weather supposed to be all white? I have tried all different kinda of weather icon packs and they are all white?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Not sure about the weather, but on mine, I noticed fingerprint settings are missing in security settings. And settings menu looks messy. Not sure if that's normal or something you're experiencing. I dirty flashed this over build 3, so maybe that had something to do with it. Other than these two quirks, the build works without issue, battery standby definitely improved
[Essential Phone ROMs, Kernels, Recoveries, & Other] Archangel:
Yeah brother, you def have something weird going on there. Here is my settings menu and I have the fingerprint menu. Sometimes I wish I didnt LOL,,,,many times I flash to TWRP and forgot to disable the fingerprint and pin and have to reboot back in order to flash things. As for the weather,,,If someone else has it in anything else other than white please let me know.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
I'm prob going to wipe and flash this from scratch.

What's interesting is, that if i switch active slot back to slot B, which still has build 3 installed, everything runs perfectly fine.

I've tried following the update instructions from op, and it kept bootlooping, so I restored build 3 nandroid and flashed updated new test build on slot A along with neutrino kernel and boot patch created with Magisk manager and neutrino image file. It updated and booted without issue, but I'm guessing either the overlap flashing or possibly the test build being incompatible as an update caused the fingerprint settings to disappear and mixed up settings
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ashwin Prabhunerurkar:
Build 4 Released

Daredevils Only try the included gapps in the rom only

do not flash additional gapps and see if the play services work
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
I'll give it a shot, just finished clean flashing the 5/8 tester build. Works without issues, only thing that's not changed is the security patch says April 5, 2018.

Oh and clean flashing it without gapps boots up with no Google apps or services preinstalled, so I had to wipe and reflash with gapps zip.

Is this upload the same build as the 5/8 tester build by chance?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ashwin Prabhunerurkar:
i guess the RR had not implemented the may patch when i built it
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
Does anyone else have the issue if awake screen off being so high? I don't really have apps installed. Wifi, sync, data and Bluetooth are all off.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Not sure, I'm flashing it now. I'll let you know if mine runs similar after I used it for a day or so.

I just finished testing the 5/08 tester build, was very stable, not much different from build 3, but security patch was dated April 5th.

Just flashed build 4 public release without gapps zip, and it still shows April 5th security patch, not sure what's up with that, but no big deal. Gapps aren't present, so I'm going to reflash with gapps package and magisk.

By chance, have you figured out how to update (dirty flash) this ROM without breaking stuff?

I've managed to dirty flash and boot into the updated build (from build 3 to build 4 tester), but settings menu broke and looked messy as hell. It was still very much usable as a daily driver, but that settings mess drove me off the wall, so I just wiped everything and clean flashed.

The original instructions for updating in op, never worked for me, resulted in bootloop and/or broke one or more of the partitions.

I didn't reflash gapps, just neutrino+magisk because neither stuck after updating.

I originally clean flashed build 3 to slot A based on [MENTION=3462598]BakedTator[/MENTION]'s instructions found on page 24.

for the update, I flashed twrp to slot A and created a nandroid of that slot (which contained the ROM)

I then flashed build 4 tester to the same slot A (not sure if I should've wiped data and/or dalvik prior to flashing this)

booted into system, made sure it was updated, gapps were still present and fully functional, magisk was missing and so was the neutrino kernel.

booted back to bootloader into slot A, flashed twrp, booted to twrp and flashed neutrino and magisk.

I initially made the mistake of flashing these onto slot B, which resulted in a bootloop,

This is where the nandroid backup helped restore slot A and allowed me to reflash neutrino + gapps onto slot B (this is to get it working the way it was set up from a clean flash).

This brought me back to the point before I botched the dirty flash.

So now instead of reflashing neutrino + magisk to slot B (which causes bootloop), I flashed them to slot A (same as the ROM location), this resulted in a smooth reboot and update, except that my settings menu was bizarre looking. I think it may have something to do with forgetting to clear data/dalvik cache before dirty flashing the ROM, or I'm completely off and the whole process was flashed incorrectly.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Archangel:
I hear ya brother, dont use the instructions in the OP they are flawed and caused my phone to bootloop too. I used BakedTators guide and it boot up fine. Been running for a week or so now and everything seems fine other than the weather on the lockscreen being all white no matter what icons pack I flash,,,which is minor at best. Great rom though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ali.sbi:
I'm running RR 7.1.2. first of all I should flash oreo frimware and then follow the instructions to flashing this rom ,am i correct?and sholud this process to flashing RR 8.1 will wipe all my storage?i mean that command wipe -w or something that erease all stuffs is necessary?tnx
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Didn't know there was RR Nougat for essential. Anyway you'll want to perform a full wipe with the fastboot -w command. You'll also need the TWRP recovery boot file, neutrino kernel boot file (if you want better performance than stock RR kernel), latest Oreo RR build, and gapps package of your choice (must be ARM64 specific) from open gapps. Then just follow instructions from [MENTION=3462598]BakedTator[/MENTION] on page 24, or if you need extra details, try my instructions on page 27. Just be sure to wipe data and dalvik cache in TWRP before you flash the ROM.

If you feel adventurous, you can try to install as an update, but I imagine it wouldn't simply update major updates like Nougat to Oreo, first of all, gapps packages are ROM version specific, so at the very best, your Google apps well keep crashing or breaking. In worst case it simply won't boot to system and may just either bootloop, hang on boot screen or keep returning to bootloader menu.

You can definitely update custom ROMs but it'll likely have to be of the same or similar structure like weekly or monthly updates based on the same versions of Android (ie RR 8.1 build 3 to build 4 is possible to update via dirty flash).
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
You will boot loop... Completely different keys...
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Well I ran bbs on my PH-1 with build 4. I'm assuming it's keeping screen awake while off when certain priorities like network connection is experiencing poor signal or no signal, maybe also Bluetooth keeps it awake while music is streaming, which in itself relies on constant data or wifi usage. Otherwise not sure. I did notice that this ROM does get more power hungry as more features get turned on. So that can possibly contribute to quicker battery discharge
[Essential Phone ROMs, Kernels, Recoveries, & Other] Joylesstuna:
OK I'll keep that in mind I don't use bluetooth. This phone does have reception issues so its possible that is it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ali.sbi:
Thank u for detailed instruction.so i have to flash oreo frimware on OP before starting yor guide?(if yes the frimware is only about 70MB is this ok?)only some thing is not clear and i saw some where what is this dump boot.img ?is it included on yor instruction?or do i need to doing extra step?is it that neutrino kernel twice flashing step that you talk about?tnx
[Essential Phone ROMs, Kernels, Recoveries, & Other] Yayaboy13:
For me build 4 make my device charging slowly.. I clean installed this by bakedtutor tutorial..with 092 firmware, I really like this rom can anybody have fix for the charging issue?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
You don't need the official essential firmware image unless you're flashing it back to stock out of box firmware.

Download the RR 6.0.0 build 4 firmware (that's the Android 8.1 RR custom ROM) from op, grab the neutrino kernel from the neutrino thread (it's somewhere under custom kernels/ROMs section) in the essential XDA thread. Then grab Google apps from open gapps (make sure to select amd64 for 8.1 Android, and select your package of choice (don't recommend aroma package, unless you know what you're doing, it may break stuff if you don't). And if you desire having root enabled, grab the latest magisk superuser zip file (not the manager), manager will be installed once you flash the magisk zip. And lastly grab the TWRP image recovery from op.

Then just follow the instructions and be sure to clear dalvik cache and data first thing after the first TWRP flash (from inside TWRP), do this before flashing ROM and everything else, if you don't, device won't boot into system.

---------- Post added at 06:30 PM ---------- Previous post was at 06:06 PM ----------

Check out this thread:

https://xdaforums.com/essential-phone/help/oreo-8-1-deep-sleep-issue-t3750645

Looks like it may be a kernel issue. Basically as you've noted, kernel doesn't or rarely goes into deep sleep, which results in higher than normal battery drain while device is not being used. Looks like elemental x kernel (latest version) may fix the problem. I'm going to clean flash with elemental x later tonight.

Someone also noted that rebooting helps bring back the deep sleep mode, but it's only a temp fix and doesn't always stick throughout a full discharge cycle. A few folks in the thread above, reported elemental x kernel fixing the issue, at least for 48 hours. Haven't seen any updates on that thread regarding how the fix is holding up, but it's worth a shot in any case. I'm sure it can't get any worse than in the current state of almost no deep sleep with stock or neutrino kernels
[Essential Phone ROMs, Kernels, Recoveries, & Other] weiyangbo:
I have the exactly same issue in build 0508.Did you figure it out？
[Essential Phone ROMs, Kernels, Recoveries, & Other] weiyangbo:
After formatting my sdcrad，I realized I should flash OPM1.180104.092 first.....

Lost all my photos and music,so sad...
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Not sure why you're having such difficulties, but that original file isn't necessary, unless your goal is to flash back to stock Essential Android firmware. This is a custom ROM, it doesn't share much with official Essential firmware. Flashing it before flashing RR ROM may cause bootloops or a softbrick.

Do yourself a favor and format both slots, preferably using "fastboot -w" command while in bootloader mode then switch slots (fastboot set_active other) and run the "fastboot -w" command again. This should leave your device completely formatted. I'm not sure if wiping on just one slot is enough, I personally always performed it on both slots before clean flashing this ROM and never had any issues other than the deep sleep issue. Just scroll back to page 24 and follow [MENTION=3462598]BakedTator[/MENTION]'s post to the t. Make sure to wipe dalvik and data in TWRP before you flash the ROM (I missed that step a few times and it resulted in a bootloop every single time), and be sure not to skip anything. If you don't want GAPPS or custom kernel or root access, you can leave those bits out, just be sure to reboot into system after flashing ROM+gapps+kernel, let it set up at least to the home screen and then you can reboot at anytime (it'll finish restoring your apps if you're restoring from a cloud backup). You'll only need to go back into recovery if you want root, if not then you're good to go.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
Why do you suggest flashing that OPM1.180104.092 file (it's currently up to version .166)?

I've wiped my device with fastboot -w plenty of times and never installed that official firmware file before installing RR and other than device rarely ever going into deep sleep mode, it still is very much a daily driver.

I'm only asking this because I've watched a video on installing LOS ROM and the guy installed this same firmware file before installing the ROM. Does it retain certain parts necessary to run a custom ROM smoother than without it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Syndrome666:
care to explain how you got it to work?

Is it the same process as installing neutrino kernel as per [MENTION=3462598]BakedTator[/MENTION]'s instructions on page 24 of this thread?

I've only tried dirty flashing this kernel in place of neutrino, but that didn't go so well, wound up bootlooping, so I reinstalled neutrino (dirty flash) and it worked.

I'm asking because, I flashed it as the zip file and didn't extract any files as I wasn't sure if I should take apart the elemental x kernel zip file.

I'm planning on clean flashing this when I get the chance, but not sure how it'll turn out. So since you say you got it working with RR, any input would be extremely appreciated.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Airwolf79:
Always flash back to the stock kernel (boot.img) before flashing another kernel. That's why you boot looped.