yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Someone should throw together a magisk module for this. I'm at work right now, so I can't do it. I'll certainly forget to by the time I get home.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Actually, I was also curious about whether editing this file by hand affects SafetyNet checks. Will this screw up certification or anything like that?
[Essential Phone ROMs, Kernels, Recoveries, & Other] raver445:
i m having so many issues rooting i m wanting to break my phone....
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
New build is up!!

New build (June 30th) is up and running fine on my PH-1, after I installed it using the AOSiP Updater app.

Before applying the updated I just removed all installed Substratum layers and before rebooting to switch A/B slot I installed root at the secondary slot with Magisk Manager app, to keep my phone rooted.
[Essential Phone ROMs, Kernels, Recoveries, & Other] raver445:
i just took the ota and rooted by following the instructions and my phone stayed at the boot logo...now i need to reflash stock which takes 15 minutes....
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
DEFINITELY disable all substratum layers! (don't need to uninstall them, though) Installing Magisk prior to rebooting is always a good idea as well. Sound advice for anyone who hasn't taken an OTA on this ROM yet.

---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------

Use fastboot to switch to the other boot partition, which is essentially rolling back the OTA you just took

Then, be sure you've disabled all themes, etc.
[Essential Phone ROMs, Kernels, Recoveries, & Other] raver445:
just got done going to stock rom...ill take a crack at it...this room is amazing though.....,

---------- Post added at 01:20 PM ---------- Previous post was at 01:19 PM ----------

do i switch to B partition or a partiton?
[Essential Phone ROMs, Kernels, Recoveries, & Other] UN5EEN:
Running build 6-17-18 with 4.4.135 neutrino kernel great so far however I'm finding any video I record is not viewable. Audio is available but the video file always shows a massive time on it as if it's my entire hard drive saved as a video file.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Weird. I was running the same build with nuetrino-delphinus release with no problem.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
Neutrino (delphinus) kernel was updated on June 18th to include a fix to the video recording bug. You can find the updated version at this post: https://xdaforums.com/showpost.php?p=76849941&postcount=279

EDIT: stock AOSiP kernel for the PH-1 also includes the fix for video recording, since previous build.
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
Safetynet is passing normally for me, and both CTS and basic integrity show up as true, so editing that file shouldn't mess with your safetynet at all.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Excellent. Thank you
[Essential Phone ROMs, Kernels, Recoveries, & Other] xlxfoxxlx:
newest build should have the video recording fix you posted on github as well
[Essential Phone ROMs, Kernels, Recoveries, & Other] xlxfoxxlx:
hows it been, as i never have the time lately i have decided that i am gonna give another maintainer a shot and see how it goes and if he does well i will be passing mata off to him but from what i can tell you guys will be plenty happy with this decision as he is going to be able to do alot more mata specific stuff giving me more time on the rom itself.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
It does, indeed. But just in case someone wants to use Neutrino kernel with this ROM, they should use the updated delphinus version.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I keep trying to modify the thermal-conf and can't get it to remount /vendor as RW

Likely due to magisk modules that modify files in /vendor. I'll have to either make this a module or do it in TWRP. If I cobble together a module, I'll post it here and submit the change to github for approval so we won't need the module in the first place. Eventually LOL
[Essential Phone ROMs, Kernels, Recoveries, & Other] Yayaboy13:
Pubg

I gonna go crazy because, the device turning dead because playing pubg.. With aosip june 30 With the upadated version of neutrino kernel.... Root.. And the device not even that hot..:eek::eek::eek:
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ryanvakil19:
Changing the thermal conf file worked for me ..now it doesn't often overheat even in 110+ degree heat
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
SafetyNet Check issue with newest ROM update

I just updated my PH-1 to the newest build using ASOiP Updater app, rebooted the device to make the updated partition active, check everything was working as it should and then switched to bootloader to flash a rooted kernel image (with Magisk), as usual.

After booting again, I discovered root is working fine but SafetyNet Check reported "ctsProfile false". I tried using a rooted kernel with Magisk 16.4 and also Magisk 16.6 but the issue was the same. Before this ROM update, SafetyNet Check was fine.

Is this an issue for other users after the update to newest AOSiP?

Beside this issue, new build is working great. Thanks, [MENTION=2903821]xlxfoxxlx[/MENTION], I really appreciate your hard work with this ROM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ryanvakil19:
I got the issue too..but it's weird because Google Pay, Snapchat, and other safetynet apps work. I guess if the apps work it doesn't matter that much :P
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Did you do it with a file editor, or by replacing the file in TWRP? I'm curious, only because I'm unable to remount the /vendor as RW while booted into the OS. That may be due to the DIY GCam Magisk module, though. I'm going to give a quick shot at disabling all Magisk modules and rebooting to see if I can do it.

Will report back on success/failure

--- Update ---

No luck at all with disabling the modules. What file editor are you using to edit the file?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
use solid explorer, that should r/w into /system/vendor
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Thanks. Total Commander isn't doing the trick

---------- Post added at 10:42 PM ---------- Previous post was at 09:57 PM ----------

Solid handled the problem without so much as a hiccup. Thank you for the heads up on that app.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ryanvakil19:
Ok so sorry for the late response..I'm in the UK right now..but the issue isn't with Magisk modules I have the same gcam module as you (actually makes the phone's camera really good) it's your file editor. If you use ES file explorer and turn root explorer on it should let you mount. I turned the shutdown parameters up from 47k and 46k to 67 and 66k respectively in case u wanted to know.
[Essential Phone ROMs, Kernels, Recoveries, & Other] asanford:
Not to beat the dead horse but I am also seeing the same thing. It passed fine on the previous version.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kakabobo:
updated to the latest build 20180709, all working good.

thanks for the update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 13stitches:
Just did a clean install of 20180709, with magisk 16.6. It's failing on the safetynet check on ctsProfile. Haven't tested if apps work correctly that I use yet.

Recently left LOS for this to combat a reboot issue I had with running maps and streaming music, (rebooted after a minute of use with both running). Seeing the past few posts I am wondering if it was overheating then.

Update - Installed a few different kernels seeing if it would change anything. Found that Elemental X doesn't work with AOSiP, SMF made no change to ctsProfile and then tried Neutrino with same results. I haven't been able to test if phone stops rebooting with any different kernel. I will be able to find out on my way home today. I might give the thermal config changes a try if I'm still rebooting.

Update 2 - Found that aosip, neutrino kernel and magisk 16.6 is working out for me. Sounds mods/music/maps all working with no reboots. Still failed on ctsProfile but it's working...
[Essential Phone ROMs, Kernels, Recoveries, & Other] asanford:
It looks like latest Magisk 16.6 removed the option to flash to secondary slot. Does anyone know of another way to seamlessly update via OTA and not lose root?
[Essential Phone ROMs, Kernels, Recoveries, & Other] dirtyreturn:
Hey, so there was a way to keep root with previous versions of magisk at least?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
Yes, it seems latest Magisk Manager lost the option to install Magisk at the secondary slot. As an alternative, I basically followed [MENTION=6474612]return.of.octobot[/MENTION] suggested procedure, as seen at the "Magisk Installation" section of the OP at this thread: https://xdaforums.com/essential-phone/development/kernel-lineageos-15-1-upstream-builds-t3754202

That is:

Installed the OTA using the AOSiP Updater

Before reboot, downloaded a copy of the kernel image on my PH-1

Patched the kernel image using the option of Magisk Manager

Moved the patched kernel image to a computer

Rebooted my PH-1 to make active the secondary slot with the OTA (ROM will boot without root)

Rebooted to bootloader and then flashed the patched kernel image with the fastboot command

Started device

Profit!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] DoR3M3:
I have a Xiaomi Mi A1 that I've been running AOSiP on, and from what I can see from the Ops instructions, it looks like you flash and root it like the Mi A1.

Can anyone tell me if the below command will work to root and flash the rom?

First like all Good Geeks, make a Backup in TWRP... ;)

1. Unlock bootloader - fastboot flash unlocking

2. Boot into TWRP image, not flashing TWRP to the phone

3. Click Wipe and Wipe partitions, reboot to booloader.

4. Boot back into TWRP and Wipe partitions on other slot, reboot back to bootloader

5. Boot back into TWRP, click the 'Install' and pick rom.zip and flash rom.zip

5. Reboot to booloader

6. Boot back into TWRP, again, then click Install and flash Magisk.zip

Reboot system...
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Step 2 - You can't boot into TWRP without flashing it to your boot partition. We don't have "fastboot boot IMAGE.NAME" available to us.

Steps 3 and 4 make it impossible to revert to a known working installation, which is partly the point of having A/B partitions.

You really love to reboot into bootloader between every step for some reason.

Step 6 - Because you have to flash TWRP to the phone's boot partition, you'll need to flash the boot.img for whatever ROM you're running to replace TWRP before you flash Magisk. This is because we don't actually HAVE a recovery partition or a permanent installation of TWRP available to us.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
New build is up!!!

I just updated my PH-1 to the new build with the AOSiP Updater app and it's working great. The SafetyNet ctsProfile check is fixed now and Magisk Manager reports green for ctsProfile and basicIntegrity.

As always, thanks a lot for this update, [MENTION=2903821]xlxfoxxlx[/MENTION].
[Essential Phone ROMs, Kernels, Recoveries, & Other] 13stitches:
Updated to latest build, passing safety net checks now. Thanks for the update!
[Essential Phone ROMs, Kernels, Recoveries, & Other] DoR3M3:
I didn't mean to be cross posting, this OP is talking about rooting one way, and on the AOSiP post, the OP mentions rooting another way, just booting into TWRP and flashing Magisk, which is what I do on a Mi A1 I own.

So two different ways of rooting are being presented, that is why I posted in two different sections, someone always has a different way of doing things...

The Mi A1 has A/B partions, and when you boot into TWRP it just picks the slots automatically. For the Mi A1, boot into TWRP, wipe phone and flash the rom, then rebboot to fastboot, and back to TWRP, and now it's switched automatically to the other slot to flash Magisk on.

To be honest, all the booting back and forth is the way everyone teaches everyone on the Mi A1, and I can see reasons for it, because with certain things, if you don't then you end up getting a boot loop, not that it's always that way. So it seems to just be habit that everything teaches, to ensure everyone isn't making mistakes, that have lesser experience, in certain situations, where if you don't boot back and forth, you'll end up with problems.

SO, now after all this said and done, does this work on the Essential, as according to the OP of AOSiP?

Flash twrp, then wipe system/data/cache on slot A, next switch to slot B and wipe system/data/cache on it. Then switch back to slot A and flash the rom on it. Now I personally reboot back to Fastboot, then back to twrp, and the slot should be on B, and now I flash magisk.zip

So does that work for flashing the rom and magisk for root on the phone?

Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] antmunny:
oh....I was about to ask this question. LOL

<---new owner of a $250 Essential Phone
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I'd suggest just following the directions in the OP of the "Rooting your Essential" thread that you posted in already, instead of making this as needlessly complicated as you can by trying to relate it to some other phone you owned. That's worked for all of us with no major issues (except when someone didn't fully follow the directions)

Literally nobody wants to read through your own plan of attack, compare it to the way its been laid out numerous times already, and then point out the differences between your method and the established working method, when you could just do what it says in that thread and have already been rooted for the last 2 days.
[Essential Phone ROMs, Kernels, Recoveries, & Other] beard805:
Lol, he's been on a bender about the A1 and is trippin' over the development for Essential Phone :) But you are correct, don't over complicate it!
[Essential Phone ROMs, Kernels, Recoveries, & Other] DoR3M3:
No bending and trippin going on, just trying to learn as much as possible before I get the phone, or if I'm even going to get the phone...

[MENTION=3053466]RandomPooka[/MENTION], you've been around here long enough to know that in certain parts of this forum there is a lot of conflicting information going around, and maybe since the Essential side is so small here, it's a lot better. So I was only checking just to make sure, better safe then sorry.

Anyhow I also don't own the phone, just ordered it, also doing my research on the phone before actually getting it, as to all the pain involved with modding it before I jump at it. I'm also very much into microG and Xposed, so another area of needing to know the support here.

Sorry if you got bent out of shape, you seemed a little jumpy...

Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I'm very familiar with the diverse group we have here at XDA. I was mostly just confused as to why you don't just follow the instructions that have been so kindly given to us. I'm all for learning everything I can about a new device when I get one. I read my butt off, and download all the tools needed to recover from a brick before I attempt to do anything, just in case I overlook a step.

But, this device is exceedingly well documented here in our corner. There are big weird quirks to it, and the instructions take them into account. It's also not the A1, so there's bound to be things that don't work exactly the same. Coming from Motorola devices, to an LG device, to a Nexus device, to a U11 to this, with probably some in between that I've forgotten about, I absolutely expect to start relearning almost from scratch with every new device. Things that are required with any device may be counter intuitive based on what you know with past devices.
[Essential Phone ROMs, Kernels, Recoveries, & Other] DoR3M3:
[MENTION=3053466]RandomPooka[/MENTION], well since you understand the lay of XDA, let's just say, I ran into one to many times, where someone was saying and posting something and followed it, just to have problems.

So now I walk with a little paranoia around here, LOL, with no disrespect to anyone, especially the OP, it's just that I don't want to jump without asking first.

Hope that is all clear now, thanks...
[Essential Phone ROMs, Kernels, Recoveries, & Other] beard805:
RandomPooka, the person who suggested looking at this thread:

https://xdaforums.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976

So there's 2 options, you can use root on the stock rom provided by Essential or you can root a custom rom, but there's a LOT more involved in rooting the custom roms.

I just completed my first root of a custom rom on this phone, I just got mine today as well.

You already have the gist of the process, it's just a bit more granular with the custom roms.

Just always remember you typically always have to involve a boot img and twrp everytime you have to restart and install something (in my experience).

Typically most of the custom roms have the boot img baked into the install zip, so that's why you want to use the instructions to install twrp via fastboot, then just install your rom, and reboot the system. Then follow and finish the setup wizard, don't ever put a password or fingerprint, until you're finalized with root.

After you've setup your base rom, you're going to want to re-enable debugging in dev settings and "trust" your phone with your computer, run the adb command to get yourself back into bootloader.

Then you're going to run this command to find out if ur on a or b partition:

fastboot getvar current-slot

After you find out a or b, you will use this comand to swap to the opposite partition:

fastboot set_active other

Now flash your twrp again in fastboot, reboot into recovery and verify you have the full file system from your previously installed rom /sdcard and now run this command:

If your rom was on A partition: adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boota.img

If your rom was on B partition: adb shell dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/bootb.img

Reboot fastboot, reinstall twrp

Now install img you just made, boota or bootb and NOW flash Magisk

Voila.

It's just a matter of finding your boot img, installing it, and then installing twrp.

Hopefully this response was more what you were looking for?

I've never used the A1, so I won't know how it compares to it, but this is definitely the worst process I've ran into for rooting and modding an Android phone, but I've been pampered with Nexus and Pixel devices up until now lol.

Hope it helps?
[Essential Phone ROMs, Kernels, Recoveries, & Other] DoR3M3:
[MENTION=9284359]beard805[/MENTION] thanks I'm learning the process, it's always different on different phones, have to learn some of the ropes over... ;)
[Essential Phone ROMs, Kernels, Recoveries, & Other] beard805:
Yeah it's definitely not too bad, just a couple more steps. The most irritating thing about the Essential phone is the non-persistent TWRP lol. Having phones that didn't have that problem previously has spoiled me. What phone are you currently using? While you wait for your Essential to arrive.
[Essential Phone ROMs, Kernels, Recoveries, & Other] DoR3M3:
Sorry been going off topic here...
[Essential Phone ROMs, Kernels, Recoveries, & Other] TheRealKingSen:
Fixed issue
[Essential Phone ROMs, Kernels, Recoveries, & Other] Saundersmtt:
I've been having an issue with the Essential Camera app on the 7-18 build. When opening it just redirects to a web browser and the essential sale page. Any thoughts on how to fix this? The phone says that it's a Pixel XL in the settings, but it's correct in all of the build.prop and default.prop files.
[Essential Phone ROMs, Kernels, Recoveries, & Other] joenun:
i received my phone today and flashed aosip but under settings/security i have no option to use fingerprint scanner.. is this a know issue?

thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Nope. That's definitely an anomaly.
[Essential Phone ROMs, Kernels, Recoveries, & Other] samy1111:
Call over WiFI

Is there actually in this ROM the option Telephoning over WiFi

If so, where do I put it on :confused:
[Essential Phone ROMs, Kernels, Recoveries, & Other] ranasrule:
Is latest Xposed beta working fine for you guys on the latest build of the rom? I'm having a few issues.

---------- Post added at 05:48 PM ---------- Previous post was at 05:44 PM ----------

Also is there an option to enable long press back button to kill app feature in this rom ?

And one last question....has anyone tried ElementalX kernel with this rom?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
I can't answer because I don't use xposed.

I think so. In Settings -> OwlsNest, go to Navigation and choose Smartbar as navigation mode. Then go to Smartbar settings, start edit mode and finally assign the force close action to back button long press.

I tried a while ago and it didn't work. The only third-party kernel I have successfully used with AOSiP at my PH-1 is the Neutrino kernel.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jdgesmlls:
Mobile network - > Cellular networks - > Advanced - > WiFi Calling
[Essential Phone ROMs, Kernels, Recoveries, & Other] DoR3M3:
Are you also trying microG, I'd like to know how the support is for that in Essential roms...

Be sure to post a Bug Report/Issue on GitHub over Xposed;

https://github.com/rovo89/Xposed
[Essential Phone ROMs, Kernels, Recoveries, & Other] samy1111:
For me this option does not exist
[Essential Phone ROMs, Kernels, Recoveries, & Other] jdgesmlls:
Does your carrier support WiFi Calling on unlocked devices?

Try long press on 'Mobile data' in quick settings, them click on the 3 dot menu on the upper right side, and choose 'Mobile Networks'. Click on 'Advanced' and 'WiFi Calling'.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jdgesmlls:
On day 5 with the PH-1, this ROM runs excellent. I updated stock right to the latest before unlocking the bootloader and installing AOSiP. My baseband shows 2.0.c4-M2.0.3. Is this the latest for those more familiar?

My WiFi connectivity isn't as good with this device in my home and was wondering if any firmware/baseband versions perform better etc.

*UPDATE* - Something isn't right with my WiFi throughput. I tried to download some larger files (~600 MB) to my device and I am getting normalized speed for 30 seconds and then a *significant* drop off. I tried the same download on my OP3T (running AOSiP) and it completes with consistent speed throughout. I realize it is not a like for like comparison.

I seen in the LineageOS thread of flashing a specific firmware to ensure it is on both A/B partitions:

Does anyone know if FW mismatch on A/B partitions affects WiFi performance?
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
It does not...

By design there can be different FW versions on different slots...
[Essential Phone ROMs, Kernels, Recoveries, & Other] ranasrule:
Anyone tried ElementalX kernel with AOSiP as its based on ASOP ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I would recommend that you don't
[Essential Phone ROMs, Kernels, Recoveries, & Other] thirtythr33:
just wanted to let the devs know just how much I appreciate the hard work they put into this rom. I have used this one in the past on my 6p, and it usually is a tos up between this and DU. either way I switched over to the essential (which was a choice I should have made earlier) and I am glad to see this rom is available. the features, the performance, and the kernel are all solid. thanks again devs!
[Essential Phone ROMs, Kernels, Recoveries, & Other] schweigster:
Anyone know how to resolve this? I see it happened to a few people with no solution posted. I tried reflashing and same issue. Thanks.