yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Perhaps I had a bunk download or something, but I couldn't flash the recent P beta, no errors on the command window, everything looked fine, but my device became real glitchy and wifi wouldn't turn on at all once it booted.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Not sure, your not the first person who told me this. It's been perfect for me so far. Are you flashing and wiping?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Yes, wiping is essential. One thing I did notice is: it doesn't wipe system_a, just flashes it, not sure if that makes a difference, but system_b gets wiped oddly enough.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
It wipes what it's going to boot. I bet your on B.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ad78:
If you are seeing the last word magi in the command and looks like its stuck, do not touch it. Wait and theres a lot more files to get going
[Essential Phone ROMs, Kernels, Recoveries, & Other] htcnerd1218:
Build.prop

Wondering if the people with the unlocked ph-1 would send me their build.prop so I can compare to Sprint verison. Trying to find a Sim unlock method.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Kochoa940:
Ok guys help me please I'd really appreciate it. I have the Sprint version and am on build number NMI81C and I unlocked bootloader and successfully rooted with Magisk. Well I go to adb sideload the zip for NMJ20D and it fails so I try it again with a different version I found and still failed. The screenshot is after trying and what it said. Now when I go to boot it up it just stays on boot logo and doesn't even go to the boot animation. I manually boot into bootloader and try to go to recovery and even after wiping data it doesn't boot. Now I can't even get back to that screen that you get to after the Android with the exclamation point. What do I do?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Kochoa940:
Here is screenshot
[Essential Phone ROMs, Kernels, Recoveries, & Other] jlin5647:
Hey, just read through this thread. Is there any difference between the sprint variant and the variant straight from essential? If I flash NMJ20D build onto my sprint variant, would I be able to get OTA directly from essential?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
Negative. No difference in the images. As I understand it, if the SIM in your phone is Sprint, you will not get the update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] elvex:
I think I might have bricked my phone lol. Can anyone help me out? I tried to flash the dump from the OP, and midway through the flash I got this:

writing 'system_b' 3/4...
FAILED (status read failed (Too many links))
finished. total time: 110.723s

Now I can't even try to flash anything with fastboot, it returns this:

c:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat

c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash abl_a abl
target didn't report max-download-size
sending 'abl_a' (1024 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s

c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash abl_b abl
target didn't report max-download-size
sending 'abl_b' (1024 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s

c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bluetooth_a bluetooth
^CTerminate batch job (Y/N)? ^Cy

Trying to flash TWRP returns something similar:

c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-mata_6.img
target didn't report max-download-size
sending 'boot' (32124 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s

fastboot devices returns this:

c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
???????????? fastboot

I never flashed over the stock recovery on this phone, so all it shows is "No Command". Does anyone know how to use that?
[Essential Phone ROMs, Kernels, Recoveries, & Other] prgopala:
Can anyone dump the oreo system images? Will make life easier to upgrade from nougat to oreo w/o relocking bootloader/wiping data etc.

---------- Post added at 07:55 PM ---------- Previous post was at 07:01 PM ----------

Thanks [MENTION=2385005]invisiblek[/MENTION] for the oreo dump.was looking for it
[Essential Phone ROMs, Kernels, Recoveries, & Other] ralphoberholzer:
Getting the following error

c:\Program Files (x86)\Minimal ADB and Fastboot\Stock>fastboot flash system_a system

target reported max download size of 536870912 bytes

Invalid sparse file format at header magi

Any help would be appreciated
[Essential Phone ROMs, Kernels, Recoveries, & Other] shooterlgk:
Let it sit..it'll keep going
[Essential Phone ROMs, Kernels, Recoveries, & Other] leapfrog2:
Stupid question...

But how do I revert back to 100% stock?

Do I flash the NMJ32F_back_to_stock.zip in twrp? Can anyone provide a step by step? I am familiar with fastboot/adb. Also, not sure if I have to flash this twice? For partition A and B? Many thanks.

EDIT: NVM
[Essential Phone ROMs, Kernels, Recoveries, & Other] artpena2323:
Yes. I'm wondering if the zip an be flashed instead of flash all bat. I'm using a mac. Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] Msean.o:
It almost seems like this is too much trouble. If you're smart you'll be patient and wait till development has progressed. In the meantime we now have Oreo.
[Essential Phone ROMs, Kernels, Recoveries, & Other] superior8888:
Its laggy af! Im going lineage until its better.

Skickat från min Essential PH-1 via Tapatalk
[Essential Phone ROMs, Kernels, Recoveries, & Other] xterminater07:
I can't unlock the bootloader, running the commands flashing unlock doesn't work at all in the oreo beta. How can I unlock the bootloader now to go back to stock nougat? I installed all drivers, including the official essential one as well.
[Essential Phone ROMs, Kernels, Recoveries, & Other] superior888:
It does. I did it yesterday. Have you enabled "OEM unlock" in developer tools?
[Essential Phone ROMs, Kernels, Recoveries, & Other] xterminater07:
Yes, i double checked everything. Rebooted both computer and phone too. It just would not recognize my device one bit.
[Essential Phone ROMs, Kernels, Recoveries, & Other] superior888:
Lastest adb tools and fastboot? I was in ubuntu and had to update my tools to get it recognized.
[Essential Phone ROMs, Kernels, Recoveries, & Other] xterminater07:
Yes i download the latest sdk platform tools
[Essential Phone ROMs, Kernels, Recoveries, & Other] superior888:
That is wierd. Windows? i don't know but check if you really are running the latest in cmd (fastboot version?) do you maybe have to run it as superuser? (admin?). Long time since a used windows in some technical way. I think Win2000 was the last.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Daemos:
I have the same issue (glitchy wifi and bluetooth) , I am trying with a manual fastboot -w now (I assumed the BTS did that)

edit: I reflashed the P beta (June) using the bts bat file but still same wifi and bluetooth errors, MD5 matches I'm redownloading the file just in case
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
That's how it works. Wiping the side it's going to boot is seamless updating
[Essential Phone ROMs, Kernels, Recoveries, & Other] Daemos:
Doesn't quite explain why wifi and bluetooth don't work....everything was wiped prior.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
So I'm a little lost here, the flash didnt work because I'm wiping and installing to system_b, when I need to be on system_a to install?

Edit

: tried using 'fastboot set_active other' and switched to slot A, then wiped with fastboot -w, but system_a still isn't being wiped, while system_b is getting wiped.. something fishy is going on, I made absolute certain I am on slot A. This is also a fresh download of the P Beta.

Edit 2

: No dice, went to slot A, wiped, and flashed a fresh P Beta, phone boots up glitchy, no WiFi, no Bluetooth. SO this has nothing to do with the slot I am booting, system_a definitely doesn't wipe regardless of which slot I'm on. I have no idea what is going on, I have no issues flashing the O june update on either slot, only this P Beta screws up my mata. [MENTION=5447216]aer0zer0[/MENTION]

Edit 3

: I tried giving a full wipe with TWRP, and formatting data and it flashed just fine afterwards, WiFi working and all that jazz.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Reiyer:
Could you explain in steps how you got the wifi to work?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
I went to fastboot and flashed TWRP, then wiped everything except internal data, then formatted data, then wiped using "fastboot -w" and reflashed P Beta. All was fine afterwards
[Essential Phone ROMs, Kernels, Recoveries, & Other] Daemos:
I got it to work by doing this:

Flash BTS Android P May DP2 (wifi works perfect)

Then I sideloaded June Android P OTA and it was fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] yankeefan:
Tether working for me in latest update
[Essential Phone ROMs, Kernels, Recoveries, & Other] fahrul:
Everything works like a charm on my device.

No bugs rightaway from the first boot up on P Beta 1.

I just doing the same procedure as on essential phone web told.

PS. : Sorry for my bad English.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Excellent. *.234 has a new baseband too....
[Essential Phone ROMs, Kernels, Recoveries, & Other] colinn24:
www
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ibanez33:
Does the latest p beta have notch settings?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nijohnson:
So I ran the Android P script. Didn't like it , and ran the latest O script, and now I'm stuck in a boot loop. Cannot get past the 2 circles screen. Device is not found by adb devices or fastboot devices (in bootloader) Any advice?

Follow up: I was able to get Android P back up and running
[Essential Phone ROMs, Kernels, Recoveries, & Other] indian84:
Nope
[Essential Phone ROMs, Kernels, Recoveries, & Other] tvisforme:
Thanks, ".234 novendor" works well with the current LOS 15.1 build (20180607).
[Essential Phone ROMs, Kernels, Recoveries, & Other] elquespera:
Hi everyone,

I'm trying to get back to stock Oreo from Android P beta. I flashed everything a few times and did a wipe but I cannot connect to the network. Instead of network name, it's written '230 030 - Vodafone.cz' and I cannot place any calls. I tried to fiddle with network type to no avail. The network stopped working after flashing Android P beta, but flashing Oreo didn't solve the problem. I'd be glad if anyone has any suggestions.
[Essential Phone ROMs, Kernels, Recoveries, & Other] elquespera:
So after successfully flashing back to stock images multiple times my fastboot and recovery still look weird. Recovery has no commands and fastboot has strange serial number and bootloader version. The phone is fully functional except it cannot register on any network, saying either no networks found or failed to search for networks. Does anyone has any idea what's going on?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NaterTots:
Well, that's what stock recovery looks like so that's normal.

But your serial number is definitely weird. I don't know what would have done that. Have you flashed any other zips in the past, before you did the BTS?

Hopefully someone else can chime in.
[Essential Phone ROMs, Kernels, Recoveries, & Other] three92:
I have used the command fastboot flashing unlock_critical The machine is not attached. When you plug in your computer then qualcomm hs-usb qdloader 9008. Do you have a solution?
[Essential Phone ROMs, Kernels, Recoveries, & Other] elquespera:
Doesn't stock recovery have options to sideload, etc.? Mine stays on no command screen no matter what I press. I didn't flash anything except from essential website and this thread...
[Essential Phone ROMs, Kernels, Recoveries, & Other] NaterTots:
To get the sideload option in stock recovery press the power button and then the up volume button.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
So what happened?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Did you unlock critical?
[Essential Phone ROMs, Kernels, Recoveries, & Other] 92sik:
I have the same problem. I flashed TWRP, but something went wrong . At first I lost stock recovery, then lost stock 8.1 may firmware with unlocked bootloader. the phone rebooted every time in non-working Fastboot. Adb console didn't see the serial number, and flashall.bat didn't help. Then phone powered off and stucked on Qualcomm 9008 and red led. There are two ways to solution this awful problem: change mainboard from other working phone or find stock firmware for flashing by the QFIL - QPOST, but no way, because there is no such firmware, it really disappointed me. Sorry for my poor English.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I think that's just EDL mode. You realize that recovery is built in boot.img?? So you flashed a boot.img (think like pixel2). It's based on LOS nougat source. THERE IS NO PERMANENT TWRP.

It sounds like your in edl mode. What happens if you force restart the the phone (hold vol up, down, power) until u get the logo. Just get back to the bootloader, you will be fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] three92:
Me too.

i want to downgrade from android P to 8.1. but I have problems with boot loop in flashboot mode. i try to unlock critical but it stucked on Qualcomm 9008 not red led.

i live in thailand. i can't go to essential support to fix it. I just hope it has a solution.

to MR. aer0zer0

i try to (hold vol up, down, power) but it only show Qualcomm 9008.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I have no idea then, you can't get to bootloader at all?
[Essential Phone ROMs, Kernels, Recoveries, & Other] elquespera:
Yeah, thanks, forgot about that. Recovery works as it should.

Otherwise, the situation has not been solved. Serial number still looks weird, I did relock and unlock both both system and critical. Essential support wouldn't send me a replacement since I'm outside US. Pretty screwed at this point...
[Essential Phone ROMs, Kernels, Recoveries, & Other] felonius:
Hi, I'm now on aosip and i want to go back stock.

Can anybody help me with the exact steps to flash back to stock?

Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Importspeed:
Hi all, i bought a used Essential for my wife. The person flashed .166 back and kept the bootloader unlocked. I tried following steps using I think aer0zer0's youtube vid to get my wife's phone onto the newest Oreo update as the OTA doesn't work. I'm not sure what i'm doing wrong but when I run the batch script (tried both wipe and no wipe) the script runs super fast and doesn't update. What am I missing here? I've since locked the bootloader back because I thought I was successful the first time through be clearly I'm not since I still cannot update OTA for the newest update for Oreo.

Please let me know what you need to know or if you can point me in the right direction that would be great.

Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Make sure you have unlocked and unlocked critical on your device. I have done this on multiple devices and the BTS here works just fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Importspeed:
At what point to I unlock critical? After wiping the phone?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Unlocking critical wipes data. So, I'd suggest doing it before you set your phone up
[Essential Phone ROMs, Kernels, Recoveries, & Other] Importspeed:
So pretty much steps would be to:

1. Get into bootloader

2. Unlock critical

3. Run batch no wipe

Anything else?

Thanks again
[Essential Phone ROMs, Kernels, Recoveries, & Other] pantherking:
Likely due to fastboot being out of date, not running the script as sudo/admin or could be due to using a usb-c to usb-c cable (such as the one from essential) which can cause issues. Open up a terminal/powershell window in your fastboot directory and try running "fastboot devices" or one of the lines from the script itself, the results should point you in the right direction for further troubleshooting
[Essential Phone ROMs, Kernels, Recoveries, & Other] Importspeed:
I'm using a usb a to c cable from Google. When i run fastboot devices, fastboot sees my device.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
no need to wipe first, the unlocking actions will always perform a wipe
[Essential Phone ROMs, Kernels, Recoveries, & Other] Importspeed:
so i now have unlocked bootloader and unlock critical (i tried unlocking through fastboot and it told it it's unlocked). I've tried using Google's USB a to c and an Amazon usb a to c to run as administrator the flash-all batch but still no dice. What am I doing wrong?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Can you get a screenshot of what it's doing?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Importspeed:
Sorry on mobile and i can't seem to find where i can edit post but i also want to mention I've tried flashing .166 and .234 and i can't seem to get them to work. My goal is to just have the phone back to stock so my wife can do OTA updates

---------- Post added at 12:55 AM ---------- Previous post was at 12:36 AM ----------

Pmd you to reduce clutter on this thread.
[Essential Phone ROMs, Kernels, Recoveries, & Other] felonius:
Hi OP,

May i suggest a step by step list form on what to do to flash BTS whether on custom roms or rooted.

Of cos it's your choice.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
I think it is actually quite detailed already short of doing a video.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Not at all... with regards to the wipe, step 2 would have already done the wipe. I assume you have already done a basic unlock, if not, you need to do an "unlock" before going to step 2 of "unlock critical" . Hope this helps.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Importspeed:
Hi there, what do you mean basic unlock? Like unlock bootloader?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
that's right
[Essential Phone ROMs, Kernels, Recoveries, & Other] dirtyreturn:
Hi essential phone owners, say, when on a custom ROM, do we fastboot flash the bootloader and radio to keep them updated also??
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
Yes, you should flash everything in the ROM.

Normally everything is packaged.
[Essential Phone ROMs, Kernels, Recoveries, & Other] dirtyreturn:
Like, to be more specific, with the nexus 6p when updating, say, a custom ROM that is based on a new android version or a monthly security update I would have to download the factory image from the Google dev page and extract it. Then with fastboot - flash bootloader /path/to/file. Same with the radio - fastboot flash radio .... I've went to the essential phone website and grabbed the latest ROM also the backtostock with and without the vendor. This phone does not require that to be done, then?
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
When upgrading/downgrading I use the back to stock ROMs listed in the thread.

Those typically have all file required in a particular release.

I flash everything. I do not wipe.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
For most custom roms, they will inform you whixh firmware version they are based on. You will need to flash them after unlock critical. Roms need the right version of vendor and radio to work well

---------- Post added at 07:34 AM ---------- Previous post was at 07:33 AM ----------

It's the same. Flash the corresponding stock first and you are all good
[Essential Phone ROMs, Kernels, Recoveries, & Other] demolatorul:
For what purpose we need the unlock critical thing, I'm on stock rom, bootloader unlocked, rooted with magisk and xposed installed and I'm not having any problems
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
So that way you can flash the rest of the firmware images in the zips. Bootloader unlock only allows a few things to flash.
[Essential Phone ROMs, Kernels, Recoveries, & Other] demolatorul:
So now in my case, can i make a backup with twrp, and after that unlock critical and flash twrp backup so I can restore the phone?
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
I would have thought that you had to unlock critical to install TWRP?

It is the boot image.

I don't remember because I did it so long ago.

If you don't have to unlock critical to install TWRP, then that should work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] demolatorul:
I only unlocked the bootloader not critical, after unlocking the bootloader i flashed twrp and installed EX kernel, magisk and xposed. I'm on stock rom and at that time i didn't know that when I'm unlocking the bootloader i need to unlock critical to. All I'm asking is that i can make a twrp backup of what I have now, because when I'll unlock critical it will wipe the phone and after that to flash the twrp backup and be back where I was?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Sounds legit. Should work. I'm just not entirely sure how well twrp backups work with our twrp (it's a little off, never tried tbh) I'd backup data to PC as well, just in case. Let me know how twrp backup works though, been curious to know.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
It should work although I have never done it yet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
OP Updated with July O OTA BTS & NOVENDOR and P Beta 2 BTS

Enjoy:)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
This is from a Reddit thread, those who have an awful time using the flashalls for windows, please read this: might she'd some insight into the problems your facing.

I posted this in another narrow focus thread but I thought it might be helpful to a wider audience......

Essential has laid a trap for us phone enthusiasts!!! If you have ever flashed any other phone, you likely have your own copy of ADB / fastboot already installed. In my case, it was "Minimal ADB". When I got my Essential PH1, I also downloaded and installed the Essential "Windows drivers". What I did not realize until yesterday was that the Essential Windows Drivers also includes a version of ADB / fastboot that is not the same as Minimal ADB (in my case). I don't know what the differences are but it would appear to have something to do with PC / phone protocol. Since Minimal ADB was installed first, it also appeared in my environment variables first and as a result Minimal ADB was what ran when I executed any fastboot command. For the most part, everything seemed OK. "fastboot devices" for example returned a valid ID string. But.... any attempt to flash via fastboot would fail. The process would start and execute the first command in FLASHALL.BAT but then would stall and wait for a response from the phone that never came.

The solution was simple.... Just uninstall Minimal ADB (or any other version of ADB) and problem solved. As soon as I did that, fastboot functions (including flashing by double clicking FLASHALL.BAT worked perfectly.

Note that I had to figure this out myself.... when I attempted to flash back to Oreo from Android P and the commands on the Essential web site failed I contacted support for a little help and was refused. Maybe Essential doesn't realize that many of their customers ARE phone enthusiasts who (like me) already have a copy of ADB installed prior to purchasing the PH1.

The End.....
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ascertion:
I'm so impressed with how fast you upload these. I use these to flash updates on my rooted device.

Thanks for uploading!