yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] ElfinJNoty:
For future(or even current?) BTS releases:

Is it possible to provide BTS flashable .zips now that we have fully working permenant TWRP?

Please and thanks in advance for your consideration ? as well as your existing contributions?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Made this before we had official twrp, hence the magisk patched boot. My intent is to just keep it stock, have you guys do your own patching. Probably no twrp flashable zip, since you can flash the ota in twrp and do the same thing.

They're really here to fix messes.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
For OTA updates only stock boot and system images are needed.

TWRP 3.2.3.0 is capable to flash both.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
you can also flash the OTA zip in twrp. 60 different ways to get here now
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tech_Savvy:
I've got a q for you....with September they updated hyp and rpm....let's say I skip sept and go from August to the October update won't it's available...will my hyp and rpm nvr get updated?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
We shall see.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
New is that TWRP for the PH-1 has an option to flash system.img.
[Essential Phone ROMs, Kernels, Recoveries, & Other] SpectraFun:
Whene i flash this rom, can i lock my bootloader after flashing? I will sell my phone and need 100% stock with locked bootloader. I have unlock both bootloader options.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Yes, just take sure you boot it up, play with it, and make certain everything works prior to locking bootloader and critical
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tech_Savvy:
can i downgrade from sept to aug using bts...do you know if anybodys done it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Yeah, just fine I would think.
[Essential Phone ROMs, Kernels, Recoveries, & Other] SpectraFun:
I have now test and relock working fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Excellent
[Essential Phone ROMs, Kernels, Recoveries, & Other] gm007:
Don't forget to disable oem unlock in dev option.
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
Maybe I missed something or I am doing something wrong but if I run the flashallwipe.bat file from PPR1.180905.036 AFH (P Official Fastboot Images September) I should have a completely stock phone with no twrp or magisk and it should be on both slots? If so it is not working for me. It only seems to flash to one slot (even tried flashing from both slots) and I still have twrp and magisk installed. What am I missing here?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
You could list the content of the .bat file to check the fastboot commands.

To make sure that fastboot is working correctly you could add the minimal adb/fastboot files to the same folder where you copied the stock images and batch files.

Link minimal adb/fastboot: https://androidfilehost.com/?fid=962187416754459552
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
It flashes and it wipes it is just not flashing what I expected it to. I thought it would install complete stock on both slots including recovery. Even after multiple factory resets and flashallwipes I only have one slot working and TWRP installed in the other slot. It is not a big deal I just wanted a clean stock version on both slots to start all over. Maybe I will try installing the OTA to both slots and see what happens.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
I've done the same, with the august version. But I didnot use the wipe batch.

Just overwrite. And both slots were synced.
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
OK.

So I am either doing something wrong or something is a little borked on my phone. I will play around some more.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
To be complete. . .

I've used the fastboot bts files mentioned in the OP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Doesn't sound like it's flashing.

You are critical unlocked?

You have essentials drivers?

Can you post a screenshot of what it's doing flashing?
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
Yeah, everything is unlocked and I flashed a dozen things so far but something is a little screwy with my latest OTA flash of stock. Bluetooth isn't working properly anymore and I randomly get a screen unlock sound that is driving me nuts. So I wanted to start fresh.

I pretty sure I am an idiot. Just so I am clear, I edit he flashall script to add what I want it to flash correct? Assuming just the images files and the rest can be left alone?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
No need to edit, it should just work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
The cmd window goes by pretty fast but I can see a note of no such file or directory go by so it is not flashing but the user wipe works. I just unzip and run the script right? This is what I see when I look at the script, I don't see .img and that's why I wondered about editing the script. The old nexus devices were such a piece of cake compared to this. Hell even samsung and all their versions are easier.

fastboot flash nvdef_a nvdef

fastboot flash nvdef_b nvdef

fastboot flash boot_a boot

fastboot flash boot_b boot

fastboot flash system_a system

fastboot flash system_b system

fastboot flash bluetooth_a bluetooth

fastboot flash bluetooth_b bluetooth
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
System shouldn't go by fast at all.

Sounds like you don't have adb/fastboot installed anywhere.

Did you extract everything? This is easy as can be. The files with no extensions are the images. That's way I set them up.

Download the essential drivers from the OP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jamiejames:
You might try downloading the factory image again from the essential website. Not the OTA the full factory image. Edit script to remove the format user data.
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
Fastboot is fine it is where I am placing the the files in an effort to keep things on this computer a little tidier. I have another PC with a little better setup that I will try after the kids activities.
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
Everything flashed fine on my home PC so there must be something wrong with my environment on the other one I was using earlier. I have flashed a few GSI's and OTA's but I could not get this script to work. Anyways got it working now as expected so thank you very much for the help and the files to begin with, it is a great setup.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 041987:
I am come from 7.1.1 NMJ51B and want to upgrade to latest oreo 8.1 july.

It's that download the stock rom in #1 and run bat? (will deleted "flash data" command for just upgrade system)

Any other things I need to do?

Also, TWRP are not allow. How can I backup the phone? (system,data etc)
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
You can use ADB to backup the phone.

Info about ADB:

https://developer.android.com/studio/command-line/adb

If you are familiar with PC and .bat files, you may use ADBsync of [MENTION=4544860]osm0sis[/MENTION].

With the help of app WiFi ADB of MetaCtrl it is possible with a wireless connection on the same network.

https://www.androidfilehost.com/?w=files&flid=282113
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
October BTS up, i even included a patched magisk and twrp stock boot.img

Enjoy :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Any issues found with using the BTS, then installing persistent TWRP to both slots via the instructions we used for the september BTS?

I'm using EX Kernel, so I'll probably wait to see if Flar2 throws a new build up soon before doing it. But, the basic gist was:

Fastboot flash the BTS

Flash the TWRP image

Reboot to TWRP

Flash bone stock image, then EX, then the TWRP-installer to get it onto both slots, and lastly magisk.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
I ended up sideloading the OTA, then flashing the patched image [MENTION=5447216]aer0zer0[/MENTION] just posted (thanks!), then the twrp installer zip to the inactive slot (not sure if this was necessary). Flashing the twrp image got me to the 'no touch' zone, not sure why, I believe both slots were on the Sep build.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
October novendor is up
[Essential Phone ROMs, Kernels, Recoveries, & Other] stompysan:
So how exactly does the patched boot img work? Do we literally just flash it and done? Does it need to be in both A and B?
[Essential Phone ROMs, Kernels, Recoveries, & Other] gorm:
Yes Flash it and done.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 041987:
If I come from 8.1 (A & B are twrp and A is current) and want to go 9.0, I need to flash stock boot to b slot and OTA in a slot. It's that right?
[Essential Phone ROMs, Kernels, Recoveries, & Other] yankeefan:
I go to install from bootloader and it just does not get beyond first step. I started flash with phone unplugged and then plug phone and it starts but does not get past first step. Not sure why

I did also download official from essential with no luck. Phone boots up fine. Even done factory reset from factory recovery and also from inside is with no success. Any thoughts…?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
Flash stock boot.img for your particular build number into an active slot, then boot into stock recovery and sideload full OTA which you can get from official Essential website.

---------- Post added at 04:19 PM ---------- Previous post was at 04:18 PM ----------

What are you trying to do to your phone? Which build are you on?
[Essential Phone ROMs, Kernels, Recoveries, & Other] yankeefan:
I am on current Oct build

---------- Post added at 04:23 PM ---------- Previous post was at 04:23 PM ----------

Trying to install twrp

It like it will not write anything to phone. Had twrp before update. Device is showing up in device manager as adb Android on computer. I thought restoring to stock would clear something up but I cannot even do that now
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
Follow the instructions in the OP to install twrp permanently.

https://xdaforums.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
It's a stock boot image and already patched with TWRP and Magisk for root. Flash it on the active slot after updating to the October version.

Both A and B?

Personal choice; not needed.

I've flashed the official OTA zip again after rooting the first.

The October version is on both slots. Only the active slot is rooted.

When booting the opposite there's no root; completely stock.
[Essential Phone ROMs, Kernels, Recoveries, & Other] GEOVANNI MTZ:
Someone can support me, updated to android foot and began to fail from nowhere the screen went black and there is no way of image, you can only hear it react when I step on the screen, there is some way to remove the dark to the screen to see it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
If you step on the screen long enough you might hear a glass cracking sound. So be careful)

Seriously, you need to be more specific what you did to your phone before it started to go screen black. What version did you have prior to update and what version did you update to and how?
[Essential Phone ROMs, Kernels, Recoveries, & Other] GEOVANNI MTZ:
I had 8.1 was updated to 9, twice began to encourage the team and the third black screen and no image, only sounds when you swipe the finger across the screen, did not suffer any blow.

Sorry for my bad English, I use translator.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ptzink:
Okay, so I skipped the September update and just flashed the October update and have no touch. Can anyone point me in the right direction?
[Essential Phone ROMs, Kernels, Recoveries, & Other] TJSteveMX:
guys, about the message: Invalid sparse file format at header magi

how long you guys waited to see the script to continue running?

i waited for about 20 minutes now and it still stuck, including a pop-up message about fastboot.exe has stopped working.

Sorry, my issue was old fastboot.exe, used the drivers from essential page and now all good
[Essential Phone ROMs, Kernels, Recoveries, & Other] IC_Blood:
Even when doing the fastboot flashing unlock_critical, I get a lot of FAILED (remote: Flashing is not allowed for Critical Partitions).

Am I supposed to select Yes when the prompt to unlock appears or just run the script when the prompt is at the screen? If I need to select Yes, will it erase my phone?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
You will have to select yes and it will wipe all internal data so make sure to backup first.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Hung0702:
I'm having a similar problem to the "Invalid sparse file format at header magi" issue, but it's not stuck. It proceeds all the way through, then closes. But, when I check my build, it still says NMJ32F and not NMJ51B.

EDIT: If you're on stock and want to update from 32F to 51B, don't just flash the package. Flash the back-to-stock 51B. If you're rooted with an unlocked bootloader, just flash TWRP after you fastboot flash 51B BTS, then reboot to recovery and flash Magisk. Turn the phone totally off, then it should boot up all fine and rooted. Flash xposed from within the app when you're done. If you're using xposed, keep an eye out for when the Google Phone app updates, because it will break you /system and you'll need to re-flash the 51B BTS. I recommend turning off auto-updates for it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Quantumrabbit:
So, now that Sprint has released the NMJ32F... I have two questions:

1) What's the difference between Sprint's version, and the raw version of the same version?

2) Since I remained bootloader unlocked, I can't take the OTA. I know I can flash this way, but depending on how number 1's shape up, is there a good reason I should lock and take the OTA instead of manually flashing? If not, should I go and update all the way to the NMJ51B?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Hung0702:
There's no difference, to both questions.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kirschdog1:
Thanks for all you do for this community. Do you by chance have a flashable magisk for the new 51 firmware update by chance? Or even better a su that won't break wifi? I can't find a working su any on any of these threads for the essential. SU SR5 2.82 borked wifi.Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] Hung0702:
[MENTION=1946444]socali[/MENTION] posted it in this thread.
[Essential Phone ROMs, Kernels, Recoveries, & Other] supervandy:
Does the first boot after flashing via the flash-all bat take quite a while? Mine's been sitting for a good 10 min now on the loading screen.

Edit: going on 20 mins... I need some suggestions. I ran the fastboot flashing unlock_critical command in fastboot with successs, then ran the flash-all bat from NMJ51B with no booting, just sitting on the spinning dots loading screen. Same with the NMJ32F.

Edit 2: I was able to flash the NMI81C image from the Essential website... My phone is the unlocked model but I have service through Sprint, that must have something to do with it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Hung0702:
Did you flash back-to-stock or package? If you came from NMI81C, you need to flash NMJ32F first (I think). I know this applies to sideloading official OTA zips, but don't know if it applies here. I'm pretty sure it applies to the packages at least.

EDIT: Oh yeah, you might have to power off the phone right after flashing. I just flashed the NMJ51B BTS without wiping over NMJ32F (no data loss). It booted no problem. You can just power off from the bootloader after you flash, then it should work fine after you boot up.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jesus359:
I have no idea what I did that my device is now on a boot loop and it doesnt let me restore anything now. All it shows is this: http://imgur.com/ce7sRna and I dont know how to restore it back.
[Essential Phone ROMs, Kernels, Recoveries, & Other] joemossjr:
Means your encrypted I'm not familiar with the device yet but I am getting one. But that means your encrypted and that your most likely not gonna be able to recover unless your backup was saved on your PC. I'm also not familiar with the bugs of this twrp but if you can flash a stock firmware file and format internal should fix the issue
[Essential Phone ROMs, Kernels, Recoveries, & Other] ZooBaAr:
Just read this

Then go here

Get the drivers, install them and flash all bat from UNzipped Build NMJ32F dL AND BOBS YER UNCLE oops

Google this > minimal_adb_fastboot_v1.4.2_setup.exe ( sry forget where i found it ) its the best.

profit

Zo0
[Essential Phone ROMs, Kernels, Recoveries, & Other] sasquatch23:
I did the same thing. Just confused on your instructions. Do I do this in fastboot mode or recovery(I have TWRP)? sorry for being such a noob but the more details, the better.

*Edit* When I tried this in fastboot mode I get a "waiting for device" message. However, when I do the "fastboot devices" command it does see my device.
[Essential Phone ROMs, Kernels, Recoveries, & Other] carleeno88:
So I think I completely bricked my phone, but I'm hoping one of you might have some insight.

I've been running (and greatly enjoying) lineage on my ph-1. This morning I noticed my firmware wasn't the latest despite running the 12-08 build so I came here to flash just the firmware.

I did unlock_critical and ran the script, and most of the files flashed over, but several of them failed with "Remote: Error flashing partition."

I tried those same files that failed again manually by copy/pasting the lines from the script to term, still failing.

Here's where I screwed up, I thought "let's restart the bootloader and see if it takes the files next time" so I did so. Instead of restarting, phone turned off.

And stayed off.

I can't turn it on, whether plugging it in, or trying any (random) combination of button presses/holds.

I'm guessing I screwed up the bootloader? Is there any way to fix it? Or is it a ceramic/titanium paperweight now?

Btw I'm using a mac for fastboot, and got it from android platform tools from homebrew-cask, if you think that had something to do with the write failures.

Oh yea, my first post on xda! I've been that guy who quietly sits in the back, doesn't say anything, but has been around longer than you realized, haha.
[Essential Phone ROMs, Kernels, Recoveries, & Other] itsita:
Oh no... that sucks.

I guess you've already tried everything, but maybe try and see whether the computer recognizes the phone in any way - even if the screen would not turn on. that might be a start.

I've went through the same process as you today - it all seems very risky.

After the firmware flashing wasn't going smoothly for me as well (got couple of errors as well), i've wiped everything and started fresh.

In hindsight it's always better to be patient for some safer methods of flashing, but on the other hand that's why we are all here in XDA :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] carleeno88:
Hmm, so I've got something, when I hold power and vol down to try to turn it on, then check mac's sys info and QUSB_BULK shows up as connected. But I try fastboot devices and nothing shows up.

Fortunately amazon will replace it still. But I wonder why I had the write failures in the first place? Could it be something to do with the version of fastboot I was using with mac? Unfortunately I didn't get a chance to try with windows before bricking it. I definitely don't want to brick my replacement as well, so now I'm wary of even installing lineage again as I wonder if I would have the same issue if I try to go back to stock afterwards?
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Ummm...

I know on other phones you need a JTAG at that point...

If what I read is true... JTAG doesn't work...
[Essential Phone ROMs, Kernels, Recoveries, & Other] carleeno88:
Yep, that's what I was thinking. Well the replacement should arrive Wednesday, I'll probably just load the 2nd oreo beta (that should be out by then) and see how much I miss lineage.

Still curious to know what caused the write failures, for myself or anybody else who might have the same problem.

And to anybody reading this having write failures while flashing firmware, DO NOT restart the phone until you've gotten all the files to write!

Things I could have tried before restarting the phone: different computer, different OS, different version of fastboot, different firmware version, or even try flashing the entire stock image. But I decided to be lazy and try the easiest thing first >.<
[Essential Phone ROMs, Kernels, Recoveries, & Other] artiemon:
I've had issues with fastboot on OS X. No write failures, but kernel panics on the Mac. I now only use Windows for fastboot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
Try flashing stock boot.img for September update in fastboot.

---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------

How exactly did you update from 8.1 to 9? Did you receive an OTA and install it from withing the OS or did you flash it from fastboot? Is your bootloader unlocked?
[Essential Phone ROMs, Kernels, Recoveries, & Other] ptzink:
UPDATE: flashing Sept boot.img did not work.

Okay. So flash Sept stock boot.img to slots a & b and reboot to check touch? If it works, can I flash the October boot.img again?
[Essential Phone ROMs, Kernels, Recoveries, & Other] GEOVANNI MTZ:
update via OTA, bootloader locked.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
My bad, dude. You need to flash boot.img for the version you are using. So if you updated to October, use October's boot.img. You can get it from fastboot image on the Essential site.

Flash it and see if you regain touch in the system.

---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------

Try sideloading the full OTA image from stock recovery. Download OTA from Essential website for the build you are running. I assume it is the latest Pie from October? Here is a youtube video how to sideload an OTA:

[YOUTUBE]https://www.youtube.com/watch?v=I0K1_FrbpDY&t=[/YOUTUBE]
[Essential Phone ROMs, Kernels, Recoveries, & Other] ptzink:
Thanks for the help. I tried downgrading back to August build without wiping userdata, but it told me userdata partition was corrupt and I would need to wipe userdata (which I would rather not do unless necessary). So then, I flashed the entire October fastboot img from Essential's web site (though I removed the "fromat userdata" line). It boots but still no touch. This seems not good. Any other ideas. I will have to revisit in a few hours when the kids are in bed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] GEOVANNI MTZ:
what happens that noi I see nothing of the screen is completely in black, I will have to do it to the luck, I hope and it works.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
Of course not. You have to see what you are doing on the screen. Did you try to long press the power button to force the phone to reboot? If that does not work, try long pressing all three buttons at the same time volumes Up/Down and Power.

---------- Post added at 11:56 PM ---------- Previous post was at 11:39 PM ----------

You can try sideloading OTA from stock recovery. That will preserve your data. Very strange that you do not have touch in the system. Did you root your phone or install twrp?