yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
But... Could you tell me one more time how to flash this?
[Essential Phone ROMs, Kernels, Recoveries, & Other] droidian5:
READ THIS: http://mata.readthedocs.io/en/latest/ LEARN FROM IT, DONT EVEN CONTINUE UNLESS YOU HAVE READ THIS. :p
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
+1

I'm surprised that so many people ask questions without going through that website properly first.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Successful flash on my palm pre:eek::silly:
[Essential Phone ROMs, Kernels, Recoveries, & Other] sinkoo1979:
Can't return to stock. ADB is working but when I click on flashall.bat "waiting for device". What did I do wrong?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
Are you in fastboot mode? What do you see with fastboot devices command?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sinkoo1979:
Not now

Let me check

---------- Post added at 09:59 AM ---------- Previous post was at 09:35 AM ----------

Still the same message "waiting for device"
[Essential Phone ROMs, Kernels, Recoveries, & Other] chris_stan:
Hello, when you hit fastboot devices, what do you get
[Essential Phone ROMs, Kernels, Recoveries, & Other] sinkoo1979:
the device number

now showing "the device is corrupt"

can't access TWRP only fastboot mode
[Essential Phone ROMs, Kernels, Recoveries, & Other] chris_stan:
where you opened your command window you have the file flashallwipe.bat
[Essential Phone ROMs, Kernels, Recoveries, & Other] sinkoo1979:
yes

but "fastboot flash nvdef_a nvdef waiting for device" when I double click
[Essential Phone ROMs, Kernels, Recoveries, & Other] chris_stan:
I read while browsing the thread quite regularly that some people had worries of cable, during the procedure, maybe it is your case, I am sorry for not being able to unlock you, people much more competent than me will inform you

I am sorry

Try another usb port or another computer if you have
[Essential Phone ROMs, Kernels, Recoveries, & Other] sinkoo1979:
thank you for your help
[Essential Phone ROMs, Kernels, Recoveries, & Other] sinkoo1979:
Reverted back to stock but still getting the message "device is corrupt". Any suggestions?

Thank you in Advance
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Red text at boot?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sinkoo1979:
Yes

found the answer in your thread.

Even in stock I'm getting that message. Is that normal?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Yes. Your bootloader is unlocked. There seems to be 2 messages.

The 'corrupt' message ask to press the power button. The other does not stop the booting.

The 'press power' can be fixed the other is persistent.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
hello, after so many tests all negative, now the phone does not turn on anymore, only black screen, can I throw it away?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Thebear j koss:
Please. Throw it away immediately and buy an iPhone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
It's not a room or stock thing. It's the verity triggered warning. Just read the link in the OP. It will tell you how to use it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Whelp, that's all she wrote....
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
anyway thanks to everyone, this experience with essential phone was the most horrible one I've ever tried with a phone so far.

thank you and sorry for all the questions asked.

Good life to everyone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
so what does it do? it just doesn't turn on now period? if you plug it in to your PC, does it show up as 9008 mode in device manager. For 200.00, essential will send you a replacement over RMA, completely unrooted and fully stock.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
the screen is always black, does not turn on even using any combination of keys, when I connect it to the PC in perfect management comes out:

qualcomm HS-USB QDLoader 9008 (com20)
[Essential Phone ROMs, Kernels, Recoveries, & Other] jamiejames:
My OG pixel did exactly that. It's done. Essential will replace it. Their customer service is second to none. They will probably overnight you one.

I've had a couple 360 cameras replaced. Very pleasant experience getting a replacement. Wish everyone was like that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I'm in Italy, I hope it will be possible to replace it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
I second this, their customer service is second to none. It's a perfect example of what I would expect from any manufacturer.

They're sending me a 2nd replacement now because the 1st one turned out to have a stuck pixel, which I noticed as soon as plugged it into the charger. For the 2nd replacement I asked if they don't mind sending me a Pure White version instead if the Halo Grey and they agreed! So it's literally on it's way to me now.

Hopefully this 3rd unit will be problem free. I think I'm just not having much luck with the Halo Grey versions lol.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Thebear j koss:
Just so everyone knows I was only kidding... Sorry you are having a bad experience with the essential. I love it, and it is the 1st device I have owned since my galaxy s3 that I keep stock/rooted. Sure there were growing pains and there is definitely room for improvement, but most most companies 1st device have been craptastic. This phone has been top notch (pun intended) from the day I got it and has been getting better with every update. The only hiccup is getting used to the a/b partitions, but for half the price of other premium devices there is very little to complain about. Plus the community of users here on xda is a small but great group who are always trying to help others with very little trolling and snarkiness. Also we are spared the ugliness of other more popular device development threads like the nexus and pixel, which always seem to have some sort of controversy or infighting among users and devs. And to top it all off, as stated above - essential has done a good job of customer service, keeping users happy, and having the quickest device updates of any company not named Google...

Sent from my PH-1 using Thebear Blue XDA Labs
[Essential Phone ROMs, Kernels, Recoveries, & Other] thelangosta:
+1
[Essential Phone ROMs, Kernels, Recoveries, & Other] boybill:
Top notch ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
But you have still a point. [MENTION=943156]nibera[/MENTION] has problems with the language. But was able was to ask the same questions in several threads. The phone is misused not the user.
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
I bet they laid off all their CS staff in the last round.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Yeah how can you not like this phone, I keep it stock (rooted) with EX kernel and get longer SoT than my OP5.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sonic0504:
Will locking my bootloader wipe any data?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Yup
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
No need to lock.

Just use Magisk and hide the rooted and locked state.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Works great with Netflix !
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
Works great with almost every root checking app, except some games, i.e. Fortnite. Although I've read that custom channel for Magisk has a fix even for that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tvisforme:
I'm still having issues with Magisk, my PH-1 (with LOS 15.1) is failing CTS. I've also noticed that the device is no longer "certified" on the Play Store, although that is probably a Google issue. (Our Asus phone with LOS 14.1 is also uncertified whereas both devices were certified earlier this year.)
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
I can't answer why is doesn't work. I'm using Magisk 17.3 with the Oct. stock release. I don't have any issues.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Magisk with stock works great.

You may extract a Back-to-stock zip on a PC and flash it. There is a all-in-one boot image included with root and TWRP.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
I am on stock with Magisk and it passes. For play store, just delete the data and it will be certified
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Let's try some basic troubleshooting... Since you decided to leave that part out...

Did you disable all modules and reboot? (Do not do this if running a "pixel" ROM... The overlays will cause a bootloop)

Does it pass?

If that doesn't work... Uninstall and reinstall Magisk...

Does it pass?

Scorched Earth time... Format the whole damn thing and go Back to Stock... Then reflash LoS...

Add back modules one at a time... And reboot in between...

When it stops passing... You have your offender... Stop using that one and let the dev know
[Essential Phone ROMs, Kernels, Recoveries, & Other] jrodbrown58:
I tried updating to the newest baseband while using the 9/11 release of AOSIP ROM I then had the no touch issues as mentioned in several forums both with twrp and through the ROM that I've also noticed that people had many different fixes before some saying they worked and others saying they didn't. What is the best way to get the newest baseband to work without problems? I'm currently on the most recent oreo baseband version using the 9/11 release of the aosip ROM. Also don't wanna lose my data since I don't have a way to back it up :/
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
5:00 November 1 and no security monthly. Essential is slipping.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Tis a sad day, I even reminded them
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Wasn't the October update released on the 5th?
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
Whole your attempt to use logic to diffuse humor is not appreciated the October patch was released on the 1st:

https://xdaforums.com/essential-phone/how-to/august-security-patch-t3849262
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Remember Remember...

The 5th of November!

(HA! I got to use it)
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
I honestly didn't remember. I just know it says my security patch level is October 5th
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ulver:
I've noticed these security updates usually get released the 1st Monday of the month rather than the actual 1st of the month.
[Essential Phone ROMs, Kernels, Recoveries, & Other] panaderodc:
For clarification, run the flashall bat file, then flash the patched image? Or change the name of the patched image to "boot" in the folder, then run flashall? Set up my phone in may, and ready to try pie.

I know you are giving back to stock, so assumption is I must then flash twrp, magisk, patched boot img. I am just not clear if this installs twrp, or not. I am guessing I will have to flash twrp and magisk after the flashall, but if it is all in the bat file, then even better.

Thanks for your work.

David

edit - downloading now, will check the bat files...

again edit. got it loaded. thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] panaderodc:
OK, I did get pie loaded, seemed fine at first, then a no sim message. Reset the network, rebooted, fine for five minutes, then off again. I have the openus variant, though I am using Ting cdma, which is the sprint network. I think I will flash back to oreo, to see if I just need to read more, or if i need immediate help to get it working again. Most links talk about this problem with sprint variants.

Thanks for any advice.

David
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Before downgrade you may try the settings of "Preferred Network Type". One by one and reboot after every change. Start with network type Global.
[Essential Phone ROMs, Kernels, Recoveries, & Other] josh4trunks:
Hi I was wondering if I could get little help. My wife's cousin bricked his Essential phone, while trying to do an OTA update, and I am trying to get it working for him again.

It does not boot into system or recovery, just fastboot.

In fastboot responses are inconsistent. I often get "FAILED (remote: unknown command)" but sometimes will get a response. It seems like putting lateral pressure on the USB port (like you're trying to snap it off) may affect this.

I have 3 different USB A > USB C cables available. A stock samsung one, an hefty USB3 Anker one, and another off-brand braided one. They all display the inconsistent behavior.

I have the latest fastboot installed on my arch linux PC (Android Debug Bridge version 1.0.40 / Version 9.0.0_r3), but also have the "platform-tools-latest-linux" available.

When I try "fastboot flashing unlock / unlock_critical" I inconsistently get the following

FAILED (remote: Flashing Unlock is not allowed)

Also "fastboot flashing get_unlock_ability" inconsistently gives

(bootloader) get_unlock_ability: 0

I believe he never unlocked, or relocked his OEM setting in his ROM before it got bricked.

fastboot set_active other

FAILED (remote: Slot Change is not allowed in Lock State)

Do I have any chance of flashing a working ROM? Or is his phone now a paperweight? Thanks!

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

I think with OEM locked, my best/only option is to get a working stock recovery installed in the current slot b. Then in the recovery flash the stock OTA.

But for some reason I inconsistently get the following, which just hangs.

target didn't report max-download-size
sending 'boot_b' (20777 KB)...

Maybe I need to try with a different USB A > USB C cable, or with a Windows computer?

I actually got more of response once... but it seems really bad

target reported max download size of 536870912 bytes
sending 'boot_b' (20777 KB)...
OKAY [ 0.762s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
[Essential Phone ROMs, Kernels, Recoveries, & Other] techfreak243:
you need to have both the bootloader and bootloader_critical unlocked. just make sure when it reboots after the erasing part to hold down the volume down button to go back into fastboot mode and unlock the other one. they both wipe your data so backup anything you need to before you run those commands, the commands will be fastboot flashing unlock bootloader and fastboot flashing bootloader_critical
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
Nailed it!
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
thats hosed now. only chance you have is if you can boot into recovery somehow. can you get into recovery?f
[Essential Phone ROMs, Kernels, Recoveries, & Other] Somcom3X:
aer0 best dev.

I love all the work you do!
[Essential Phone ROMs, Kernels, Recoveries, & Other] indian84:
Stree. Is that you?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
November BTS up in OP, Novendor Next
[Essential Phone ROMs, Kernels, Recoveries, & Other] josh4trunks:
Nope, recovery and system both just show the powered by android screen.

Would Essential pay for a replacement, my wife's cousin made it seem like he only ever used official/preview builds?

I guess this phone is only good for parts otherwise?
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Well, its safe to say you wont get anywhere with the phone in a completely locked state and not allowing you to unlock it because to flash anything at all you NEED an unlocked bootloader!

Do you know what your cousin did exactly when trying to do the OTA? What was the state of the phone before he tried to OTA (what firmware, rooted or not, OEM Unlocking enabled)? Did he follow the official instructions on the Essential site on how to take OTA properly?

To me it seems like the only option is to open a support case with Essential and tell them that you tried to OTA the phone but you're unable to unlock the bootloader and tell them exactly what commands you tried and the output you're getting. If they determine that the brick isn't his fault they'll likely replace the unit, don't quote me on this though.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
A new ph-1 has no preview version out of the box.

With an locked bootloader OTA is only possible with an on line connection.

When you don't know exactly the cause of this. Just send it for repair with no explanation other than the ph-1 won't boot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kerry2020hinsen@gmail.com:
Forgive me if this isn't the right place to be asking this but I'm looking for a noforce encrypt Angler NRD90U img. I can't find it anywhere
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
November boot image with EX kernel 3.09.

Patched with TWRP 3.2.3.0 and Magisk 17.3 for root.

https://www.androidfilehost.com/?fid=11410932744536996455

Same with Magisk 17.4 (nightly)

https://www.androidfilehost.com/?fid=11410932744536996460

Note: Magisk 17.4 has a different su database.

A database corrupt message may appear. I solved it by flashing the above image first (Magisk 17.3).

Reboot and flashed this version with Magisk 17.4 (nightly)
[Essential Phone ROMs, Kernels, Recoveries, & Other] kerry2020hinsen@gmail.com:
Thanks I'll try these...I'm thinking its BLOD
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
https://androidfilehost.com/?fid=24724405900804317
[Essential Phone ROMs, Kernels, Recoveries, & Other] kerry2020hinsen@gmail.com:
It worked thanks...I got it out of the bootloop but the supersu put it right back lol
[Essential Phone ROMs, Kernels, Recoveries, & Other] TacoLoco:
I' on October Update with TWRP & Magisk.. Now Android shows November update? How is the recommended procedure for upgrade?
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
I use ex kernel manager and flash stock recovery and take the OTA as normal

My problem is windows 10 never sees the phone in the bootloader mode and I can't flash the new patched boot.img
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
The cause is mostly:

- not working adb drivers;

- USB cable.

The ph-1 cable is only for charging. Use a different usb-cable.

Generic Google ADB drivers works on many PC's.

When Windows device manager shows an error '!' there's a connection, but not working. Manually (re)activating the existing driver is needed by starting the Windows management tools.
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
Well I can do adb reboot bootloader So I assume the driver/cable is ok

but in fastboot it just sits on waiting for device

I have tried the following drivers in fastboot

Android Bootloader Interface

Essential phone fastboot

Essential phone ADB

Android platform Sooner Single ADB Interface

Android Composite ADB Interface
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
This driver could work when it's from Google.

Sometimes I need to reinstall the driver (when connected), otherwise Fastboot won't work.

When Fastboot works device manager shows ' Android Phone ' and under Portable devices ' PH-1 ' is no longer listed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
If you're running the Essential driver it will show up as "Essential Phone Fastboot Interface" I think.

It's very strange his ADB commands work but not Fastboot.

Some people have gotten Fastboot to detect the phone by using "fastboot devices -i 0x2e17", without the quotes.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
ADB uses the driver for portable devices. Fastboot needs a different driver to work with the bootloader mode.

There are 'composite drivers' for both modes, but not for every Android.
[Essential Phone ROMs, Kernels, Recoveries, & Other] TacoLoco:
Thank you.. But where can i find Stock recovery?
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
You can find all the latest builds here:

https://www.essential.com/developer/current-builds

They contain the Boot.img within the zip which includes kernel, ramdisk and recovery.
[Essential Phone ROMs, Kernels, Recoveries, & Other] TacoLoco:
Thank you! Now I installed october boot.img (Stock) and tried to update to november (from Android) but it shows an Error Updating (installation problem), still in Android.. Any advice on how to get to november update safely?

Can I flash the whole november ROM with EX Kernel Manager?

Edit:

Installed OTA ZIP via ADB Sideload (Stock Recovery).. Worked..
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
scratching my head, now what ?

PS D:\Essential ADB and FASTBOOT> adb reboot bootloader

PS D:\Essential ADB and FASTBOOT> fastboot devices -i 0x2e17

PM1LHMC7716***** fastboot

PS D:\Essential ADB and FASTBOOT> fastboot getvar current-slot

< waiting for device >
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Are you rooted?

If you don't mind loosing your data and rebuilding it you can just flash the whole Nov stock via the flash-all.bat included within the zip. This is the best way to get up to date, however you will loose your data during the factory reset and will have to go through flashing TWRP again to both slots.

Alternatively you can flash the full Nov update zip it via TWRP, or sideload it in Stock recovery.

I think this is where you need to try different USB ports/USB-C cables.

Can you do fastboot set_active other or fastboot set_active a?

This site helped me loads when I was going through similar issues - https://mata.readthedocs.io/en/latest/
[Essential Phone ROMs, Kernels, Recoveries, & Other] TacoLoco:
Thank you for this! But after Flashing TWRP does want a encryption password, did I do anything wrong?

Edit: I'm dumb, I simply had to input my Lockscreen PIN..
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
disable lockscreen to disable encryption before flashing TWRP
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Do you have any password or any kind of security enabled?
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
No anything fastboot except fastboot devices -i 0x2e17 results in

< waiting for device >

I have tried several different usb ports and cables

lucky for me I don't really need root for anything but the EX kernel would be nice
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
It sounds to me like it might help to uninstall your drivers completely and install them again from Essential's site.

Pretty sure it's the Fastboot driver issue or Fastboot itself.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
What does

fastboot --version

say, that's minus minus version
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
Genius !!!

That was it .. I was using fastboot from c:\fastboot and not the one in the current directory

PS D:\Essential ADB and FASTBOOT> adb reboot bootloader

PS D:\Essential ADB and FASTBOOT> fastboot --version

c:\fastboot\fastboot.exe: unknown option -- version

PS D:\Essential ADB and FASTBOOT> fastboot --version

fastboot version 3db08f2c6889-android

Installed as c:\fastboot\fastboot.exe

PS D:\Essential ADB and FASTBOOT> fastboot flash boot_b "D:\Essential ADB and FASTBOOT\4.4.161-ex309-twrp-mgk173.img"

target reported max download size of 536870912 bytes

sending 'boot_b' (65536 KB)...

OKAY [ 1.934s]

writing 'boot_b'...

OKAY [ 0.561s]

finished. total time: 2.498s

PS D:\Essential ADB and FASTBOOT> fastboot getvar current-slot

current-slot: _b

finished. total time: 0.002s

PS D:\Essential ADB and FASTBOOT> fastboot reboot

rebooting...

finished. total time: 0.001s

PS D:\Essential ADB and FASTBOOT>

copied fastboot from Essential ADB and FASTBOOT directory and boom it works !!

Thanks for that