yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
flash this to the boot partition?

---------- Post added at 02:26 PM ---------- Previous post was at 02:24 PM ----------

Not sure, rebooting it twice more got it to boot up properly. I did my magisk installation by modifying the stock boot image while booted into the stock kernel using Magisk Manager, then going into fastboot to flash that patched image. Did the same thing for the past couple of months across all my devices without any issues. Have not had to use TWRP at all as I find it a pain to delete all my keys and fingerprints each time. Until someone figures out how I can get TWRP to co-exist with the stock kernel as my only backups are now TiBu and no longer make TWRP backups.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
finished adding the rest of my links? anything else you guys want in the OP. I was really hoping to just maintain the full BTS zips, and then add the scripting required to do everthing else, so i dont have half a million zips in afh
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
added novendor specific packages for you LOS types
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Did anything change in the novendor? At work otherwise I'd do an md5 comparison. 95MB is awful small for there to be changes...
[Essential Phone ROMs, Kernels, Recoveries, & Other] johncjenc:
Little assitance

I'm trying to sideload to RTS zip file, but I keep getting an invalid zip file format error in TWRP, fastboot flash throws an error "invalid sparse file at header magi"
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Unzip the file on your pc. Then run the batch file to flash
[Essential Phone ROMs, Kernels, Recoveries, & Other] johncjenc:
Ok...batch run reports same invalid sparse file at header magi. Edit, worked after wipe, thank you sir.
[Essential Phone ROMs, Kernels, Recoveries, & Other] cbalt:
If you flash the newest BTS full flash wipe, it doesn't wipe internal storage correct? I just wanted to make sure of what all I needed to back up before I did that later today.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
1. cant flash the BTS files in TWRP.....

2. Sparse header magic error is fine, and common, just let it go. The images are raw and not sparse formatted, which is why the error occurs
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
there a script to not wipe, choose the script that suits your needs
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
to be honest, probably not, its really just the system getting patched for may security update

just MD5'd

abl, boot, cmnlib, cmnlib64, modem, nvdef, system (obv), TZ, vendor all changed from .141 to .166
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
It DOES wipe userdata, which includes internal SD. Internal SD is a symlink to /data/storage or something of that sort. Back EVERYTHING up
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
i made a bunch of different scripts in the zip, one of them is flash-all-NOwipe
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Yeah, I saw that script in the zip. They were asking about the wipe version and if it wipes the internal sdcard too, or just apps and user app data.

Fastboot -w wipes sdcard too
[Essential Phone ROMs, Kernels, Recoveries, & Other] d0u8l3m:
So I just flashed the new update with LOS and I'm not seeing the may security patch? Is this included in the no vendor package?? Seems everything flashed fine, I didn't do anything different from the last two times I used the no vendor packages to update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aamadorj:
AFAIK, the security patch is included at the ROM, not the firmware files which are just updated versions of the drivers needed to make the device work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I think the LOS build dropped before the Essential update by a day or two. It might not be in there yet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Ask, and he shall receive. Buffet update today with the May patch. I need to fastboot the firmware from Essential, but I did take the update and it shows up as the May patch in "About Phone"
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
May patch was included only with the 5/08 LOS build today...there was a build on 5/07 that was still April,
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
that's an expected error message, but you should be good. The error is because we did a dump of the partition image
[Essential Phone ROMs, Kernels, Recoveries, & Other] johncjenc:
Coming off a lifetime of HTC devices, little growing pains here. Thanks everyone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
You guys want a BTS for P preview?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tech_Savvy:
forsure:)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
https://www.androidfilehost.com/?fid=818222786056029681

one P BTS, the .bat wipes, only flashes to A slot (to be safe).

you may need to fastboot set_active other if your on B slot after flashing. You may need to wipe data afterward in stock recovery prior to booting (my experience)

Good luck, and beware of dragons, obviously
[Essential Phone ROMs, Kernels, Recoveries, & Other] gianttama:
a very newbie question here,

i am on stock, rooted with magisk and got TWRP recovery (because i wanted the google camera), bootloader unlocked, currently unable to install OTA update.

can i go back to stock by simply download the "full dump" and run the bat? will i loss all of my data?

if my goal is to get the least rom and keep my data, could i download one of those "firmware packages" in OP and install those instead? many thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tire_007:
The steps i took to get May update was download .166 full dump> go to magisk> uninstall > Restore image> reboot connect the phone to pc > unzip the full dump> and run flash all no wipe.bat and it will update without deleting anything. If you want root again in the same full dump is the stock boot image just patch it with magisk like you did before. Sorry is there are any typos is really late here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] gianttama:
Great help, thanks a lot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] treIII:
This Thread seems to be alive and if I'm off topic and I shouldn't post here I will not again. My question is how do I flash a different radio other than the current radio that is with Android 8.1? I had a better signal with older nougat radios with T-Mobile so I'd like to flash an older radio if possible

---------- Post added at 05:02 AM ---------- Previous post was at 04:06 AM ----------

Okay so I downloaded some stock firmware from Android nougat and I pulled out the modems from a couple different nougat stock firmware updates and I flashed the modem by itself from those updates and I was not able to hear anyone when I made a phone call. Does anyone know if I can Flash something else along with the modem and get this to work so I can use a different radio from Android nougat while I am on Android Oreo 8.1
[Essential Phone ROMs, Kernels, Recoveries, & Other] kakabobo:
btw how is BTS file extract by ?

any step or method to read upon ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Extract the zip, run bat file or sh. EZ
[Essential Phone ROMs, Kernels, Recoveries, & Other] TheBurgh:
Worked like a charm. Thanks for making it as effortless as possible.
[Essential Phone ROMs, Kernels, Recoveries, & Other] danial.aw:
I had the same issue where the receiver can't hear me... What fixed it for me is to disable volte
[Essential Phone ROMs, Kernels, Recoveries, & Other] thelangosta:
Same here though it was only one htc for me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
updated OP with a new BTS for P. I used the updated fastboot images (new ones from essential) so now there are no invalid sparse header magic errors, and its fresh and clean.

Enjoy
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Should we flash the updated images over the same ones which have the "invalid sparse header magic errors" ? or is it unecessary?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Doesn't matter, the ones in the old zip are dumps from phone, the new ones are essential issued images. Anything I posted in the OP, are essential issued images.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Shall stay put then. Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] gilbertsalessepillo:
How to go back to 8.1 from Android P, I unlock the bootloader, I do not know what command should I use to flash the image. Im using Mac, please help!Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Backup your apps and data.

Download the 8.1 .166 stock image

Run the return to stock shell script with Wipe. It will reverse to the original stock image

Boot it

Root it

Restore your data
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Make sure you also did unlock critical as well
[Essential Phone ROMs, Kernels, Recoveries, & Other] gilbertsalessepillo:
What command on terminal?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NaterTots:
I think it's "fastboot flashing unlock_critical"
[Essential Phone ROMs, Kernels, Recoveries, & Other] nijohnson:
Hiya,

Having some issues running the script.

I'm rooted with magisk, unlocked/critical unlocked. One thing that is odd is that I seem to be able to only get fastboot access on my pc when I add "-i 0x2e17" to my commands.

I am afraid I do not have the error codes, or output. I'll post those later.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Install the drivers from the OP. Essential has their own drivers for adb/fastboot
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Reboot to stock recovery, format data there is the quick answer.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ThaqAtaq313:
Could you share the process - having the same issue :mad::o
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
After all that flashes. Reboot to bootloader, then select reboot to recovery. In stock recovery, select wipe data.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Or just use the back to stock for may
[Essential Phone ROMs, Kernels, Recoveries, & Other] ThaqAtaq313:
THANK YOU!!

Through the PMs you were able to help me get back to Oreo 8.1.

I really apppreciate your help to the Essential community! :D
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Lol, was wondering whereyou ended up. What ended up working?
[Essential Phone ROMs, Kernels, Recoveries, & Other] ThaqAtaq313:
Seriously, I took my time and changed computers and cords..and followed your process instead of YouTube videos

1. cmd.exe

2. Fastboot -w

3. Flashed flash-all no wipe

4. Waited patiently

5. BOOM MAGIC

MUCH APPRECIATED BROTHA!!

:good:
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I got a feeling it's cord or port. The flash all wipe should work perfect for you. As far as cords go, use A to C, and I buy the choetechs from Amazon. you may also wanna look at usb 2 port instead of 3 ( my laptop is all 3.0, no problems though)

At any rate, since your back, play with the bats, see if you can get it going on your PC.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mdisbrow:
Can someone help me get back to stock? I've downloaded the fastboot files from essential. I get into fastboot and run fastboot -w and I get and error unable to determine partition. I can't get any further than that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Follow the rooting thread to unlock then flashing will with fine with return to stock
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Follow everything in the OP. sounds like cable, port, or driver issue.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mdisbrow:
I've reinstalled drivers, downloaded latest stock dump, swapped the cable out.

I run "adb devices" and see my device

"adb reboot bootload" it boots to bootloader

"fastboot devices" I see no device from here?

Here is a screen shot of adb https://imgur.com/gallery/bjcnFAD

---------- Post added at 02:22 PM ---------- Previous post was at 01:54 PM ----------

Here is where I get stuck https://imgur.com/gallery/bjcnFAD

It won't wipe the phone and when I run the flashall file it hangs at "waiting on device"
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Open your device manager when in bootloader, do you show a question mark there? Or do you see a device
[Essential Phone ROMs, Kernels, Recoveries, & Other] mdisbrow:
I see "Android Device" then in the drop down under it "essential phone"

I now have it recognized in fastboot but get this when running fastboot -w https://imgur.com/a/Ox8prHU

Not sure what to do.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Did you download the may BTS posted here? If so, open the cmd here.exe in the zip and try fastboot -w in there
[Essential Phone ROMs, Kernels, Recoveries, & Other] mdisbrow:
Yeah the most current from May. Here is where I'm at with it https://imgur.com/a/asGFgDT

Edit: I think I may have figured it out. I copied the cmd here.exe and fastboot to the stock file. I then ran the cmd here.exe from that file and it recognized it in fastboot. I then was able to run the flashall file and have it push through adb. It is booting now, hopefully it will be on oreo.

Edit 2: That's all I needed was to copy cmdhere.exe and fastboot from the minimal adb file and everything worked just fine. A whole lot of hassle for a really simple fix. Thank you for the help.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
So the whole point of all those files in that zip, is you don't need anything else. That's good though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mdisbrow:
Yeah I realized that the flashall file in there was suppose to be a one stop shop. I just continued getting "waiting for device" whenever I tried to run it. Your comment of cmdhere.exe made me look for it in the folder. When it wasn't in there I decided to try moving it from the adb folder to the stock folder along with fastboot to recognize the device. Had you not mentioned it I'd probably still be stuck and confused. I was just opening minimal adb from the shortcut or holding shift to run a command prompt prior.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
I was having that issue randomly until I got a good USB 3.0 cable. Should see blue inside the USB A connector. If you don't, it's not 3.0. Just something to check to maybe help next time around.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mdisbrow:
I tried 3 different cables total. 2 USB c-c and one USB a-c. The one that finally worked was the a-c. Id have stayed on Android p but the animations and gesture functionality was just flat out bad. I really hope Google makes some serious refinements to the interface by the time its out if beta. As it is right now the new navigation gestures release 2 days ago on xda work far better. If we are gonna use gestures than do it all the way or not at all. Having a back button when a swipe would do just as well or the standard height nav bar taking up screen space just doesn't make sense. It's like they missed everything that makes the iPhone gestures good.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
I have to agree with you I went to Android p for the sake of trying something new and I felt it was very underwhelming, especially the navigation and quick settings look. Wasn't overly impressed, so back to Oreo. ¯\_(ツ)_/¯
[Essential Phone ROMs, Kernels, Recoveries, & Other] ThaqAtaq313:
I hear you - any links to the cords on Amazon? :cyclops:
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
CHOETECH USB Type C Cable, USB C to USB A Fast Charging & Data Sync Cord (6-Pack, 1x1.6ft+4x3.3ft+1x6.6ft) for Samsung Galaxy S9 S8 S8 Plus Note 8, Nintendo Switch,Nokia 8,LG G5 https://www.amazon.com/dp/B01N4E9AN6/ref=cm_sw_r_cp_apa_i_e31aBbCM29Q3X
[Essential Phone ROMs, Kernels, Recoveries, & Other] ThaqAtaq313:
Thank you!:)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
DP#2 Is up

Enjoy :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] TheBurgh:
Everything worked perfectly. Thanks for making the process uneventful.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Does anyone know of a thread on XDA for the DPs? Or, should I start looking on reddit?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
You're in the thread mang, just check out the 1st post.

Both DP's are there.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I'm sorry. I wasn't very clear. I mean discussion of them and how they're coming along and not just location of the full system/vendor/radio/etc dumps.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Uneventful is the best answer tbh :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I'd make one [MENTION=3053466]RandomPooka[/MENTION] , everything is spread in a manic fashion
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
For this. I will always take uneventful
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I like easy
[Essential Phone ROMs, Kernels, Recoveries, & Other] Dashwood Foxe:
OPM1.180104.166 BTS doesn't work, Keep getting the error "invalid sparse file format at header magi" in fastboot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Lol, that's fine. It's not a sparse image, it's raw. It's why it throws that
[Essential Phone ROMs, Kernels, Recoveries, & Other] Dashwood Foxe:
Guess I was impatient, Had to sit a while longer. :p
[Essential Phone ROMs, Kernels, Recoveries, & Other] tvisforme:
Any thoughts on whether the radio firmware in the Android P DP2 ROM is suitable for use with Oreo/LOS 15.1?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
You could try it. Worst case is you use a BTS for Oreo if it doesn't work?
[Essential Phone ROMs, Kernels, Recoveries, & Other] tvisforme:
Would these lines (clipped from the no-wipe script for the most recent Oreo firmware) be a good start?

fastboot flash bluetooth_a bluetooth

fastboot flash bluetooth_b bluetooth

fastboot flash modem_a modem

fastboot flash modem_b modem

fastboot reboot bootloader

Also, if it doesn't work, flashing the most recent Oreo "firmware package without vendor" (OPM1.180104.166) should restore the radio and bluetooth without having to wipe, correct?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I'd think the firmware without vendor package should work. The one labeled for custom ROM users?
[Essential Phone ROMs, Kernels, Recoveries, & Other] ztxgeol:
Few problems I've noticed when using ur work:

1. removing file extensions fails my laptop every time(using MacOS), this is serious since I've only been through system failure 1 or 2 times for these year

2. seems like u didn't give the right premission for scripts to be excuted, I've to "chmod +x" them every time before using, but official package's .sh is ok

3. the zip seems crrupted when unzipping on MacOS, but windows is doing ok, so maybe it's a MacOS problem

Anyways, thanks for ur great work
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
sounds like first world mac problems.....
[Essential Phone ROMs, Kernels, Recoveries, & Other] SethKraKray:
I flashed with this a while ago and even though the phone works completely fine and successfully flashed it still says my device is corrupted and my serial changed so I can't get OTA's. Any ideas for fixes?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
What is corrupt?
[Essential Phone ROMs, Kernels, Recoveries, & Other] SethKraKray:
Every time I restart my phone it says "Your device is corrupt. It can't be trusted and may not work properly Visit (the link) Press Power Key To Continue" I press the power key and I go into Oreo 8.1 completely fine as if nothing happened. I actually don't know what is corrupt about it besides the serial number being different after trying to flash several times.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
Nothing is corrupt.

It says "you device can't be checked for corruption."

I presume the splash screen is orange and not red?

If you unlock the boot loader you get the message.

There is nothing you can do about it.

If you want to have root, you live with the message.

You cannot lock the boot loader unless you are completely stock, stock unmodified boot image, no root.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
If it's red u broke verity
[Essential Phone ROMs, Kernels, Recoveries, & Other] SethKraKray:
I didn't want to have root. It wasn't for rooting. It was from going back to Oreo from the Android P Beta.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Could you be more specific about the serial? Your IMEI and MEID haven't changed, have they?

If you did a complete Back-to-stock with one of the full firmware versions here, which one did you use? How do you know you are unable to receive OTA updates if you restored the most recent 8.1 version?

Why not just relock the bootloader?
[Essential Phone ROMs, Kernels, Recoveries, & Other] SethKraKray:
The bootloader was already locked because I relocked it. The corruption was red. And I did complete back to stock with the latest oreo firmware from here. I've already done some things to "fix" the issue. And the IMEI and MEID did not change, just the serial number for the phone in software. I know I am not able to receive ota's because essential only sends them out to phones with valid serials, according to a support employee through email.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Did you flash the fix-red-boot.img ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
You "know" it, in that someone you know told you that (regardless of how in the know they might be), and not because you received an OTA notification and made a failed attempt to install it. That does not count as "knowing" it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Zaisesl:
I have the red screen. I have to flash the boot.red.fix.img, in only have to let it boot once roght? and then flash stock boot.img?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
let it bootloop until it turns orange, then flash the stock boot
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Also, P Beta is uploading now
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
OP Updated with P beta #1, i would have had it up last night, but i decided to fall asleep instead...
[Essential Phone ROMs, Kernels, Recoveries, & Other] indian84:
Well, sleep is Essential.

;)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
lol, my kid has a double ear infection, the eardrum in his right ear ruptured yesterday afternoon, and the left ear last night..... It was miserable, but then we all just fell asleep
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Rough, sorry to hear that and hope your kids okay.
[Essential Phone ROMs, Kernels, Recoveries, & Other] indian84:
Hope the little one gets well soon...
[Essential Phone ROMs, Kernels, Recoveries, & Other] thelangosta:
That sucks. Mine have ruptured a couple times
[Essential Phone ROMs, Kernels, Recoveries, & Other] eriknors:
New update?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
im building it now, upping in a little bit
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
OP updated, .234 BTS and .234 novendor updated
[Essential Phone ROMs, Kernels, Recoveries, & Other] eriknors:
Anyone know if this update includes the multi touch issue ???
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
It should