yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] onema:
thank for your reply, I did not get a log cat , not familiar how I have to look into it, I'm back on 9 since I wasnt able to transfer my files.

I also tried to flash a few of the Q beta builds on my ph1 and got the same results, Titanium fc as soon as I open it, sometimes it opens but is suck on a screen. Another symptom is my android file transfers going incredibly slow one by one.

I switch back to android 9 and the 2 issues are gone and the phone runs smoothly. DO I have to update the bootloader for something for android 10? I've been flashing for a while but the terminology is still a bit foreign to me. Thanks for any help.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mruno:
I had to factory reset TB as it and other apps seemed to not be requesting permissions with 10's new system.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JudasD:
is anyone seeing LTE+ on sprint now with 148? I have never seen LTE+ before on this phone.

Thanks,

JD
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
Yes not sure if it's faster
[Essential Phone ROMs, Kernels, Recoveries, & Other] JudasD:
It is definitely not faster for me. I was thinking more along the lines of if this could be VoLTE or something like that.

JD
[Essential Phone ROMs, Kernels, Recoveries, & Other] Jz5678910:
This is exactly what it is. It's just VoLTE. Not faster in any way.
[Essential Phone ROMs, Kernels, Recoveries, & Other] JudasD:
Have you noticed any new features able to capitalize on this for sprint? it doesn't seem to actually crate a volte connection. All it does is have the regular wi-fi calling that it has always had.

Thanks,

JD
[Essential Phone ROMs, Kernels, Recoveries, & Other] Jz5678910:
I have AT&T myself so I really couldn't say. I get VoLTE support and that's it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] V0idst4r:
What bootloader/vendor do you guys use for pie based custom ROMs like AICP/RR? I remember why I quit using this device: Endless lower level firmware issues that makes hardware like the audio, earpiece, touchscreen, or the radio completely give out depending on certain kernels/bootloaders/ROMs. I can never get the perfect combination that actually allows this thing to be usable as a daily driver...
[Essential Phone ROMs, Kernels, Recoveries, & Other] dragynbane222:
Custom ROMs typically package their own vendor and bl in, so flashing a different one of either or both is not recommended and can actually cause issues
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
No... Custom ROMs do not bundle their own bootloader...

On this device they are system, vendor, and boot.img
[Essential Phone ROMs, Kernels, Recoveries, & Other] MrPhilo:
If I remove this line fastboot -w in the .bat file, will it work fine and not wipe my phone or cause any issue? But just technically update my phone. I don't keep up to date with Essential as it's my backup phone but will like to get it up to date now as I'm using it soon for a trip.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ktmom:
There's never a guarantee that a problem won't develop. As repeated over and once, removing the -w prevents the script from wiping the device. It works fine for me and others. Just make sure to use a good USB A to USB C cable.
[Essential Phone ROMs, Kernels, Recoveries, & Other] dragynbane222:
Ah, alright, I always thought the boot.img was part of the bl, thanks for setting me straight
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Boot.img contains the Kernel and Ramdisk, core components to load the device.
[Essential Phone ROMs, Kernels, Recoveries, & Other] dragynbane222:
So it's basically like the vmlinuz/initramfs in the /boot partition on most x86 Linux system
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Boot.img contains kernel and recovery...

We use SAR... sur
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Thanks for the correction.

Tbh no idea why I said ramdisk. Running on somewhat lack of sleep atm.

Sent from my mata using Thebear Blue XDA Labs
[Essential Phone ROMs, Kernels, Recoveries, & Other] aleph23:
Having just read Google's documentation on this, boot.img does indeed contain a ramdisk. The recovery partition is a ramdisk, plus the kernel. There are typically two bootloaders that initiate prior to boot.img, primary and secondary. Their partitions under /dev are usually 'pbl' and 'sbl'. Primary passes to secondary and secondary passes to boot.img <=- This would be the point (@ secondary bootloader) at which verity is confirmed. Starting with Android 10 recovery itself handles the initial boot process. Also in 10, fastboot is partly broken out of the bootloader and brought into the boot.img/recovery.

See

source.android.com/devices/bootloader/fastbootd#unified_fastboot_and_recovery
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Ok...

Except the fact that Cam was referring about boot instructions... Or.. initramfs I think... Which is a "traditional" ramdisk
[Essential Phone ROMs, Kernels, Recoveries, & Other] aleph23:
Hmm.... I guess I don't understand the difference. Boot.img has a kernel and what AOSP calls "recovery", right? And Recovery is, actually the INITial RamDisk, like a standard initrd, right? ...Or am I missing something?

:confused:
[Essential Phone ROMs, Kernels, Recoveries, & Other] onema:
Hello all is the latest Nov update going to be available for bts? I have a Sprint and the one on the essential site doesn't flash well for me
[Essential Phone ROMs, Kernels, Recoveries, & Other] eKeith:
Would also appreciate the November BTS. Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] handisnacks:
Seriously, where's November?
[Essential Phone ROMs, Kernels, Recoveries, & Other] ktmom:
https://www.essential.com/developer/current-builds
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I have gotten the dreaded red verity warning. But I cannot find the file with the fix. I believe I'm supposed to go to http://gg.gg/ai7m1. But that just returns a weird error message. Does someone have this file?

I got this Essential phone from eBay a couple of weeks ago, and I'm wondering if it has more problems than this. This red warning did not occur until today when I was flashing Android 10. I have been flashing stock pie and Q for the last couple of weeks. But for most of that time, fastboot seems to randomly fail when writing various partitions. I'm thinking it is possibly a problem with one of the slots, but I haven't really proved that. The cable that I am using is a good one, not the one that came with the phone. After some of those write failures today, the red warning started to appear.

I hope someone can give me that file to fix the red warning, but I don't think that's going to help me with these other issues.

I had successfully unlocked the bootloader right after I got this. But unfortunately, I did not do the critical unlock. Just a failure on my part to read well enough. But it sounds like that should not be an issue for me right now because I have never tried going backwards from a custom rom to the stock rom.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ktmom:
Look at the post here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks for looking for the file. I did see the link to the patch, but I wasn't sure what I would do with that. However, when reading it, it seemed to imply that we needed to do the same thing that is mentioned in post 1386 of this thread. That post mentions issuing command:

adb reboot "dm-verity enforcing"

I tried that, and it worked perfectly. However, I'm not sure if this just gets rid of the red warning, but does not fix the actual problem. Maybe the solution you put there about the universal disabler would actually fix it?

EDIT: I was replying while you were posting your new message. I will try to find that file later, but I do think that the command probably did the same thing that the missing boot.img did. Do you agree?
[Essential Phone ROMs, Kernels, Recoveries, & Other] ktmom:
[MENTION=4541967]sga999[/MENTION], if the verity warning is gone, no need for more
[Essential Phone ROMs, Kernels, Recoveries, & Other] krak3n77:
WTF

Dude legit, i thought that an actual bug on my screen!! I tried to smash it with my finger and I got really confused when there was nothing there! XD
[Essential Phone ROMs, Kernels, Recoveries, & Other] raoulbhatia:
I'd be interested as well - i.e. are people using https://sourceforge.net/projects/mata-bts/files/Pie/August/ ?

EDIT: I flashed the August NOVENDOR package and things Seen to work well. LTE/WLAN/Calls are working.

Thanks,

Raoul
[Essential Phone ROMs, Kernels, Recoveries, & Other] rocketrazr1999:
WOW!!!! Now I understand what my problems are due to!!!! I have problems with EVERYTHING on my Essential!!! From the A/B being a mess, ( continually stops booting and defaults to the bootloader after Magisk module flashing, etc) to apps not working right (Titanium Backup only backs up data), and BusyBox not installing (Viper won't work without it), and a plethora of other examples of hardware and software issues, notably the terrible audio crackle and touchscreen responsiveness. Oh, anyone know why the screen is cut off on the right side? This phone is so rough around the edges (and insides) that it's nearly impossible to like. Such a contrast to my beloved N5, which I finally sold both of (Almost 7 year old phones that can still handle ported Android updates and run BETTER than this Essential!!!

Mike
[Essential Phone ROMs, Kernels, Recoveries, & Other] raoulbhatia:
Hi Mike - I am not sure what this has to do with my question about the bootloader/vendor images people use.

However, I am using my Essential PH1 with Lineage for a loooong time and experienced only a few issues that I was able to overcome with the help of the community. I haven't had any real issue since it got official Lineage support [1] - i even dirty flashed from an unofficial build (thanks [MENTION=2385005]invisiblek[/MENTION]!) to the official build w/o real issue. (I only had to use lineage-migration-signed.zip, i believe).

If you share more details, perhaps to a relevant thread, people might be able to help you, i.e. https://xdaforums.com/essential-phone/development/lineageos-16-0-appears-to-live-t3939150.

If not, then at least you have a phone that has strong support from the vendor w/ fast updates, etc.

Good luck with making your phone work!

Raoul

[1] https://wiki.lineageos.org/devices/mata
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Here in this the thread there's latest Jan 2020 NOVENDOR:

https://xdaforums.com/essential-phone/development/firmware-collection-novendor-images-t4030965

Easily update to the latest ESSENTIAL files if you're in a Custom ROM.

Edited link because file was re-uploaded.

Enjoy :D
[Essential Phone ROMs, Kernels, Recoveries, & Other] raoulbhatia:
Are the Q firmware files compatible with Lineage 16?
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Yeah you should be fine.

Do a TWRP backup beforehand if you're not sure.

;)
[Essential Phone ROMs, Kernels, Recoveries, & Other] the_Pan:
Thank you for the update!:good:

Is there a changelog somewhere? Just searched on essentials site, but I can't find one. :confused:
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
They stopped doing changelogs on their site a while ago.

I think you only see it if you're receiving OTA.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Hmm...

Can you right click the flashallnowipe.bat and click edit, then screenshot the contents?

Coz it sure doesn't look like ur using my zip.
[Essential Phone ROMs, Kernels, Recoveries, & Other] the_Pan:
The file is looking good to me, the only difference seems that some files, like "abl" or "bluetooth" are now .img files, while in older builds they've got no extension.

It seems this is something with Q, because the files are looking the same in the first Q realease, I just checked.

EDIT: Wait, I just looked into the .bat file, over there you changed the filenames, but not in the .sh file. I'll change them and try again.

EDITx2: With edited scriptfile, it also works on linux! ;)
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
The Linux script had errors in it which have now been fixed, this is because I natively use Windows and didin't test the SH script before uploading. All sorted now though.

Glad you got it flashed fine. ?

Sent from my mata using Thebear Blue XDA Labs
[Essential Phone ROMs, Kernels, Recoveries, & Other] Talnoy:
Hey can someone maybe give me a hand on how to actually use these 'back to stock' packages?

I've got an essential with a TWRP.img file flashed to slot A on my essential but slot B is the booting slot. No matter what I try, TWRP simply refuses to install anything to the B slot and nothing boots from it except the stock recovery, but now I can't load a rom or go back stock since it's been wiped.

How do I either get TWRP on to slot b, or use these back to stock packs? I've tried using the 'cmd-here.exe' files and running the 'flashallwipe.bat' command but it just sits at 'waiting for device'

Update: Seems I've figured out how to use the stock restoration zip files via fastbook but now my phone just doesn't do anything - I can still get into fastboot but I can't boot on either slot for recover - I just get a dead android with "no command" sitting there. Trying to boot to system does the same thing.

Help?

Is there something I'm missing? I'm so confused at this phone. *Everything* I've read has said the TWRP zip file was supposed to install TWRP on BOTH the A and B slots but mine just never worked.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
If you want to use TWRP in future, use Jan stock rom, if not, use Feb stock rom

- Make sure you install Essential driver to your PC

- Use fastboot package from Essential

- Unzip the stock rom

- Put phone in boot loader mode

- Run "flashall.bat" in unzip folder

- Let the scrip does installation itself and after phone reboot, you should be back to stock.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrrocketdog:
also ; [MENTION=4133432]Talnoy[/MENTION] make sure you flash the twrp-installer-mata-3.2.3-0.zip ; after you flash twrp and after you set active your initial slot ; from twrp. which will patch both slots. (after flash , hit reboot and on that screen select your initial slot).
[Essential Phone ROMs, Kernels, Recoveries, & Other] Talnoy:
Awesome! So to get this straight I'm going to do the following:

- reboot to fastboot mode

(As of now, my active booting slot is slot a.)

- Flash the TWRP.img file to slot b

- flag slot b as the active slot

- boot to recovery in slot b

- install the TWRP.zip file

- switch to slot A

- reboot to system

- reboot to bootloader and then ensure slot a is active and boot to recovery

- once in recovery, I'll then be able to flash a custom rom - do a wipe and flash away
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrrocketdog:
well just -boot to recovery.

then select install and flash the twrp.zip file. go back to twrp's home screen. hit reboot and select slot A.

if thats what you were saying then , yup.

then yup , wipe and flash away [emoji111]

---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------

here is link to twrp-installer.zip if you dont have.

?https://www.dropbox.com/s/gw8bkyzvfc6z5hz/twrp-installer-mata-3.2.3-0.zip?dl=0
[Essential Phone ROMs, Kernels, Recoveries, & Other] natetokes:
Are you THAT talnoy? If so, whatchu doin in my waters?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Talnoy:
Woah woah woah - what CHU doin in MY waters!?
[Essential Phone ROMs, Kernels, Recoveries, & Other] natetokes:
Hahaha, your name is pretty unique so I saw it and was like nooooo waaayyy. This is crazy. I got one of these phones for free like 2 weeks ago, finally got it all set up a few days ago. TWRP/evox 4.4/magisk. It's a good phone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Talnoy:
Amazing! Hit me up on telegram friend!
[Essential Phone ROMs, Kernels, Recoveries, & Other] natetokes:
Ok give me a bit I have to install it and go outside to get a signal to set it up. I'm not sure how precious time is but if that phone can wait until after work tomorrow I can send you my fastboot folder and the rom zip I used etc. I have to be at work in 6hrs.

If not, look up "daze one TWRP" on YouTube. I got january stock (found it by using a cached copy of essentials site) replaced the boot with this guy's pre rooted image, set up the phone after flashing in fastboot, flashed the TWRP and root IMG to the current slot in fastboot, used TWRP installer in the booted TWRP, rebooted to recovery, formated data, flashed Evo x in twrp. Rebooted to system.
[Essential Phone ROMs, Kernels, Recoveries, & Other] capmaan:
Having lots of trouble here. After executing flashallwipe.bat/sh i get error messages "no such file or directory"

Has anyone an idea what I am doing wrong? I have the unziped folder in the same folder as my Platform tools (ADB & Fastboot) and execute them from there via "sh directory/to/file"

What am I doing wrong?
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
First, check if you already install Essential driver

Second, I've never seen "flashallwipe.bat", I used "flashall.bat" file, please double check if that file is existed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] SirDigitalKnight:
Essentials ADB/FASTBOOT

Essentials ADB/FASTBOOT (HIGHLY HIGHLY RECOMMEND THIS VERSION)

ADB/FASTBOOT

The link in the OP thread doesn't work. Where can I download it? Thank you.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chanh2018:
Use this...

https://developer.android.com/studio/releases/platform-tools.html
[Essential Phone ROMs, Kernels, Recoveries, & Other] SirRedwind:
Does anyone know if there's a way to make the PH-1 work better on T-Mobile networks in the US?
[Essential Phone ROMs, Kernels, Recoveries, & Other] luis saucedo:
Hello, currently my PH1 is in stock QQ1A.200105.032 in slot "B", can I install firmware QQ1A.200105.088?
[Essential Phone ROMs, Kernels, Recoveries, & Other] thk_ms:
Hello,

what's the funktion of the NOVENDOR-files? is it an update-file for 18.1-LineageOS?

Thanks, thk_ms
[Essential Phone ROMs, Kernels, Recoveries, & Other] razbary:
I'm having issues with my PH-1 in fastboot. I can get it to show up when i exec devices but any other commands (flash, -w, etc) don't work. They just almost act like they're waiting for something
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Do you have the Fastboot environment set up correctly?

On Mata it can be really temperamental and picky.
[Essential Phone ROMs, Kernels, Recoveries, & Other] necross_o:
is it possible to revive if the bootloader is locked (and unlock is not allowed)? (got bricked by one of their OTA updates)
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
Is your issue resolved? I face the same problem, need help.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Zraxonix:
Use a USB dock hub of any kind. I used USB-C hub meaning USB-C goes into the computer and connect it with original USB-C cable; other cables should work and normal USB-A hub should work as well.

Keep in mind that adb won't work over this so you will need to keep switching cables.

Bump @razbary
[Essential Phone ROMs, Kernels, Recoveries, & Other] baltek222:
I have same problem here. Have anyone found the solution already? I am on LineageOS trying back to stock.

" fastboot -w

Erasing 'userdata' FAILED (remote: 'unknown command')

fastboot: error: Command failed"
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
As mentioned earlier, Use any time of USB dongle or dock. It worked for me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] baltek222:
I don't know how, but it worked for me too. Thank you so much.

While I am trying to open flash.bat (rom downloaded from https://essential-images.netlify.app/) in the platform tools directory I am getting such errors:

Spoiler content hidden.

The only thing I achieved is clearing existing rom (Lineage OS). Phone boots to clear Lineage OS. Stock rom wasn't flashed.

EDIT.

I edited and copied commands from flashall file (instead of running it) and typed it manually in PowerShell. After that it worked. Thank you anyway for suggesting using USB dongle.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Hmmm. .

Way back when... This used to happen when the file allocation table gets screwed...

The old fix was to load the device as a USB drive... Let your PC format it... Then let Android reformat it...

But we're talking years ago... Different device...

But... TWRP should let you mount USB Mass Storage... So...
[Essential Phone ROMs, Kernels, Recoveries, & Other] Serial Kazama:
I could solved the problem.

I followed this [YOUTUBE]https://www.youtube.com/watch?v=RrMLqSXcxjI[/YOUTUBE] but on my maschine there was no mke2fs.exe so i load the platform-tools-latest-windows 27.0.0.1 new.

After that fastboot -w works like a charm and after that i have to start the flash-all.bat normal,

not with admin rights!

.

The guy in the video makes a right klick and select run as admin.

Sounds good, dosnt work for me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kjhoerr:
Flashed the oreo beta 2 full dump from OP coming from LineageOS 14.1 (to move to LineageOS 15.1). Everything worked fine, only now I get the red error "your device is corrupt. It can't be trusted and may not work properly" at boot, in addition to the yellow warning.

Re-locked critical partitions and relocked the bootloader (including in settings), neither made the error go away. As far as I can tell, SafetyNet no longer works either. I figure I messed something up along the way. Any clues as to what's up?

$ fastboot oem device-info
...
(bootloader) Verity mode: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Device modem EFS unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
[Essential Phone ROMs, Kernels, Recoveries, & Other] DaveHTC200:
http://mata.readthedocs.io/en/latest/

Read this, there is a way to clear the red error.

Hopefully you can unlock your bootloader again though, its never recommended to lock that, just in case
[Essential Phone ROMs, Kernels, Recoveries, & Other] spotmark:
For those of you who weren't aware, the factory zips from Essential can also be flashed with TWRP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kjhoerr:
Thanks so much! It worked great.

And yeah, no issue re-unlocking my bootloader. I assumed it was fine since I was on stock at that point, but thanks for the heads up.
[Essential Phone ROMs, Kernels, Recoveries, & Other] chk27:
Sorry for the potentially dumb question:

Can the dumps be used to "update" the phone without loosing root nor user data?

Last time I patched my rooted nexus phone, I simply flashed (in a certain order which I can't remember right now) the bootloader, the boot image, the radio and the system partition.. ant there it was updated to newer os, with all of my data.

I'm waiting for the phone to arrive next week, I hope.

It would be nice if essential released full updates (with partitions in them) as google did for the nexuses, for now thanks a lot for the dumps.

Thank you.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Yes you can do that. I used it to update to ob1 followed by ob2
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
The back to stock will wipe TWRP and magisk.

After running bts you need to put back TWRP then flash magisk