yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
You already got response about the Sprint issues. But I'm interested in your fine Wifi in Q beta 3.

I noticed that Wifi won't connect when Wifi scanning is off. On my PH-1 I need to switch Wifi to automatically turn on (WiFi scanning turned on).

I'm curious if your WiFi will work when Wifi scanning is turned off and you want to connect to a WiFi host with medium or low signal.
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
I had to drop the Q beta because my home screen buttons did nothing

phone - messages - youtube- internet and camera on the bottom of all the screens was totally dead

Wifi and data worked fine, but I found no way to fix the tray icons being dead
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Same here. Could be solved with a reboot.

But after removing all modules in Magisk no dead buttons since 1 day....
[Essential Phone ROMs, Kernels, Recoveries, & Other] Quantumrabbit:
That definitely solved it. Thank you

---------- Post added at 08:59 AM ---------- Previous post was at 08:29 AM ----------

I seem to be able to connect either way, but I generally run with scanning on.
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
I never use any modules in magisk must have been something else

and even after a reboot the buttons were dead again after the screen was off and back on a couple times
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
I mentioned modules, but it has to do with software/apps that needs root.
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
gotcha .. I do use EX kernel manager
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
My versions:

EX kernel 4.00, EX manager 5.01

Magisk 19.2 canary, Magisk manager 7.1.2

EDIT

Last 3 days...

Every day once dead buttons. Needs a soft reboot.

EDIT2

1 day without issues; no dead buttons.

Q beta 3 - daily driver

EDIT3 [MENTION=2895182]clsA[/MENTION]

Again after a day normal use dead icon-buttons; not all but only the icons in the menu bar at the bottom of the screen. And around the same time (16:00)

EDIT4

Switching dark/light mode solves the dead icon issue.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
On my PH-1 with Q beta 3 Keep Notes was yesterday updated to version 5.19.191.07.40. Still white

Does anyone have Keep with a dark mode
[Essential Phone ROMs, Kernels, Recoveries, & Other] marcdw:
I have that version on an Oreo ROM on my Moto. In Keep's settings it has an Enable Dark Mode toggle.

Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
[Essential Phone ROMs, Kernels, Recoveries, & Other] Quantumrabbit:
I should probably not have messed with this... but I attempted to flash back to Android P since Android Q didn't work for MMS for me at all. I didn't really want to wipe data, so I tried not doing that. That didn't work. So I flashed everything back to Android Q, including the Ex kernel.

Now I have a much worse problem... I can't open settings or even the drop down menu any my notifications are gone. This has a pretty rough down side, I can't copy data off as I get no USB menu either...

I tried re-flashing, tried re-wiping dalvik.

Can't say I feel like Android Q is quite ready. :)

Anyone have any thoughts, or is my next move wiping data and going back to Android P?
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
Yes going back to P included wiping the phone for me too... I use cloud backup for pictures and settings so it was pretty painless

I did loose some PDF I had stored on the phone but it was simple enough to search my emails and download them again
[Essential Phone ROMs, Kernels, Recoveries, & Other] 63c:
June.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kpirnie:
Hey mate, that Elemental in the Boot Images -> June folder... is that rooted with TWRP, or just ElementalX?
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
I flashed the JuneTwrpRoot.img and ElementalX needs updated if that helps you
[Essential Phone ROMs, Kernels, Recoveries, & Other] JudasD:
i just tried that boot image and it is elemental, magisk and twrp.

JD
[Essential Phone ROMs, Kernels, Recoveries, & Other] 63c:
Q beta preview 4 BTS now available.
[Essential Phone ROMs, Kernels, Recoveries, & Other] clsA:
I didn't see these posted anywhere yet Sooo...

here's Magisk 19.3/TWRP/ElementalX 4.02 for the Beta 4 > https://www.androidfilehost.com/?fid=6006931924117889615

and here's the beta 4 Stock/magisk 19.3/TWRP > https://www.androidfilehost.com/?fid=6006931924117889616

flash with fastboot

adb reboot bootloader

fastboot getvar current-slot

fastboot flash boot_a

or fastboot flash boot_b

Enjoy
[Essential Phone ROMs, Kernels, Recoveries, & Other] h.420:
if i use the flashall script, will it also install TWRP or are there extra steps I need to take to flash TWRP?
[Essential Phone ROMs, Kernels, Recoveries, & Other] HopelesRomantc91:
When trying to download an OTA it says "waiting for wifi" when I'm on a WiFi hotspot from another device. Why does it do that? Anyone know how to get around it, or better yet, fix it?

Edit: tried this on latest Pie build and Q preview 4, same results.
[Essential Phone ROMs, Kernels, Recoveries, & Other] plee3:
Better URL for July OTA

The July OTA update on the Essential web site seems to be incorrect. I tried the following URL

https://storage.cloud.google.com/essential-static/PH1-OTA-PQ1A.190105.090.zip

which is similar to the June OTA update URL but with the July OTA filename and it seems to download.

I have not had a chance to update my phone yet with this file, so use it at your own risk.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lynnux:
Thanks for catching this. It worked for me. I'm probably an idiot for trying it, but someone had to be the first ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Dwigtt:
Hi everyone. I recently bought a used essential phone advertised as faulty. I initially thought it was dead so I plugged in the charger, the red led began flashing. The screen then turned on and a message saying the "device/software is corrupt and I should press the power button to continue" appeared. I pressed the power button and an image of a dead battery appeared and the phone switched off. I haven't gotten it to switch on since.

When I plugged it into my pc, my pc recognized it as "Qualcomm hs-usb qloader 9008" and I haven't had much luck since. Any help you can offer would be greatly appreciated
[Essential Phone ROMs, Kernels, Recoveries, & Other] jamiejames:
I had a OG pixel do exzatly that. Sorry but it's garbage. Hardware failure.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 63c:
hardware failure is not quite what it is but yes, its not functional

Device is Toast
[Essential Phone ROMs, Kernels, Recoveries, & Other] 63c:
I'll have the August BTS up soon enough... need to move all this **** off of androidfilehost.... its terrible
[Essential Phone ROMs, Kernels, Recoveries, & Other] 63c:
thread revamped and simplifed, august bts and novendor available in the pie bts and novendor folder
[Essential Phone ROMs, Kernels, Recoveries, & Other] HueyT:
Do you think this is fixable using your instructions on post #1?

https://www.ebay.com/itm/Essential-...-Black-Moon-BOOT-ISSUE-SOFTWARE-/143347925097

Sounds like just need stock boot.img reflashed?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Aimless Rambler:
I clicked on the link in your post, I bought one of those phones a few days ago and it was delivered yesterday (15 August). On reading availability there are a few left as of today. As I suspected, it was just the standard unlocked bootloader warning, just like ya get on every Google phone you unlock bootloader on, from Nexus 5X to Pixel (that I know of). I let mine charge a bit (low battery) then booted up, pressed the appropriate button when prompted, booted into startup, signed into Google and it seems to be working fine. Definitely worth the 53 bucks I paid for it. I'm currently downloading firmware to have on hand in case of emergency. If the remaining devices listed are of a similar state, there's no issues. If I had the extra cash and no wife to complain about it, I'd buy a couple more.
[Essential Phone ROMs, Kernels, Recoveries, & Other] HueyT:
Took a chance. Hope it works out :silly::highfive::cyclops:
[Essential Phone ROMs, Kernels, Recoveries, & Other] Aimless Rambler:
I'm thoroughly pleased with the one I got thus far. Hopefully, the one you bought will be just as good.

To keep on topic ... you'd asked;

"Do you think this is fixable using your instructions on post #1?

https://www.ebay.com/itm/Essential-P...-/143347925097

Sounds like just need stock boot.img reflashed? "

If the warning on boot is annoying to you I believe all you have to do is re-lock the bootloader in fastboot. Not certain but I bet the command is fastboot flashing lock. Granted you will likely loose any data you have on phone once you relock bootloader. If you go that route, before locking I suggest doing a bit more research, of course. Afterall, I just got my Essential, not sure about any quirky business it could throw your way.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Wickidmasshole:
The O beta 2 just dropped
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
I have slot_A (beta1) rooted with Magisk, not sure if I can take the OTA without messing things up . Theoretically it should update to slot_B
[Essential Phone ROMs, Kernels, Recoveries, & Other] Maxr1998:
You should disable Magisk first, by reverting to the stock boot image. Else the update won't apply.

After that, you can reroot/reinstall Magisk according to the rooting guide in the guides subforum.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
shall attempt that and see how it goes.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
i disabled Magisk by reverting to the stock Beta1 boot.img, the update still does not let me apply. Keeps saying "installation problem". Will do a full flash of B2 stock from this thread into slotB and boot to slotB if it works.
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
Finally someone figured out the advantage of A/B slots.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Took me a while to get it into my head. Simply love it now. I have a slot with root and one without coexisting. When I need root, just reboot to the other slot and voila. Only problem I have is I need to use a pc with fastboot to switch slots. If only I can do it before rebooting
[Essential Phone ROMs, Kernels, Recoveries, & Other] Rep7ile:
So I locked my bootloader after flashing OB2 and firmware to my phone. And re-enabled ADB debugging/ unlock bootloader options again. My question is have I potentially enabled myself to unrecover a bricked device if one of my future OTA updates fails?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Until the bootloader is unlocked, enabling bootloader unlock doesn't mean you are unlocked yet
[Essential Phone ROMs, Kernels, Recoveries, & Other] Rep7ile:
I realize this as I currently have it locked, I followed the directions given on essentials webside. But after locking the bootloader I'm starting to wonder if it was a good choice and why essential recommend I lock it after flashing.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Locking it after flashing (if you don't root or flash any mods) will allow you to take OTAs and pass safetynet out of the box. However, if you want to root, keeping it unlocked allows you to flash and even recover from bad flashing easily.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Rep7ile:
Okay great, that's the impression I was under. Just wanted to make sure I guess. Im happy with the OB2 so far and really have no need to root this device as of yet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Make sure you are 100% stock before locking again. You will have a high chance of bricking if it isn't so
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Once unlocked... Do not understand any circumstances EVER relock your bootloader...

Between recovering data issues... And maybe not being able to unlock it again... Or having some stupid verity issue... You're better off unlocked...
[Essential Phone ROMs, Kernels, Recoveries, & Other] joemossjr:
I've relocked my bootloader 6 times not for safety net purposes. But if you run the flash all and run fastboot -w afterwards and make sure it boots then I reboot and relock usually
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
I'm glad it worked for you...

However... Most people don't read... And definitely do not read enough to understand why things break... Regardless of how well documented the problem may be...

If someone were to lock their bootloader with root... TWRP... A custom kernel... A custom ROM... Anything that doesn't bear the OEM signature... Nasty verity will keep you out of your phone... Leaving you with a nice paper weight... Since there is no fix... And JTAG doesn't work AFAIK
[Essential Phone ROMs, Kernels, Recoveries, & Other] joemossjr:
I'm not saying that stuff is impossible lol ( bricked 2 devices like that) just saying what I did lol
[Essential Phone ROMs, Kernels, Recoveries, & Other] siulmagic:
I just **** my pants, when i restore my device and still said it was corrupt, but a few bootloops seems to have fix it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Rep7ile:
I soft bricked my device after accidentally erasing all data on my device using TWRP on N. After that f*ck up I got the Back to stock Oreo B1 and firmware downloaded. Ran fastboot -w and ran the bat files. Everything went well. I didn't have any issues after updating OTA to the OB2. I want to unlock my bootloader again but haven't since going back to stock. I did re enable ADB debugging tho. Just in case lol
[Essential Phone ROMs, Kernels, Recoveries, & Other] Serial Kazama:
Hello Freinds,

Fastboot -w does not work for me. It says there are no userdata?

"mke2fs failed: -1

error: Cannot generate image for userdata"

Install.bat doesnt work neither
[Essential Phone ROMs, Kernels, Recoveries, & Other] HueyT:
I have Pixel 2 XL, V30, Moto G6, LG G6 all with unlocked bootloader so I'm well aware of the error message of unlocked bootloader (generally yellow). The red one is a corrupted bootloader which generally can be fixed by reflashing stock boot.img. This message on the Ebay photo seems to be the red one which is the latter problem and not the benign yellow bootloader unlock warning one.
[Essential Phone ROMs, Kernels, Recoveries, & Other] DAE1964:
You can find information at this link.

https://mata.readthedocs.io/en/latest/
[Essential Phone ROMs, Kernels, Recoveries, & Other] HueyT:
"Removing the Red Verity Warning

The red verity message that appears on modified systems and requires you to hit the power button to boot can be cleared by fastboot flashing this boot.img: http://gg.gg/ai7m1

That image will reboot over and over again (you’ll never get anywhere) but when it does, it’ll clear out that annoying red error. After flashing it, boot normally once. You will still get the red error but it will be cleared it the next reboot.

Here’s a link to the patch that is included to perform this: http://gg.gg/ai7kb "

This is exactly what I need -- thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] Aimless Rambler:
Wouldn't just fastboot flashing stock firmware be more efficient?
[Essential Phone ROMs, Kernels, Recoveries, & Other] droidian5:
It is my understanding that the red "verity" is not fixed by flashing stock. Did yours come with the red or yellow warning?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Aimless Rambler:
First the yellow, then the red. Yellow warning indicates the bootloader is unlocked then next screen has the red corrupt warning message that prompts you to press power button to continue booting up.

---------- Post added at 09:30 PM ---------- Previous post was at 08:56 PM ----------

While dinking around with the phone after reading various posts concerning the Red Verity Warning message I came across a band-aid, with no multiple reboots required. Took me 2 minutes, all cleared of warning message. Granted, it's not a fix, it's more of a cat burying a turd but warning is gone. Also, I'm completely stock with system wide ADB meshed into PC. Read below!

Red Verity Warning Removal - adb reboot "dm-verity enforcing" (--remember to include the quotation marks--).

With thanks to the Oneplus forum (link below). Different device I know, but it works.

1. https://forums.oneplus.com/threads/get-rid-of-dm-verity-warning-at-boot.513115/

2. Info on dm-verity

a.) https://www.kynetics.com/docs/2018/introduction-to-dm-verity-on-android/

b.) https://source.android.com/security/verifiedboot/
[Essential Phone ROMs, Kernels, Recoveries, & Other] HueyT:
Just an update: Ebayer advertised red verity boot warning, but sent me a black-screened, unresponsive, hard bricked ph1 with the feared "qdloader 9008” on PC connection. Trying to swap or refund now :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] jowandrys:
Looks like we finally got the android 10, but the web site is not allowing me to download the OTA who has another link besides the official website??
[Essential Phone ROMs, Kernels, Recoveries, & Other] Neytiri_AVA:
cyclic reboot essential phone

Hello, I have the essential phone with a cyclic reboot, I can boot in fastboot mode.

I can’t boot in recovery mode, Android, I don’t know what Android is installed here.

I buy this phone with a problem, please help me, you are my last chance
[Essential Phone ROMs, Kernels, Recoveries, & Other] ktmom:
Edit: I answered in the Q/A help thread where you also posted. That's a good thread for this problem.
[Essential Phone ROMs, Kernels, Recoveries, & Other] someone0:
I tried to download fastboot version and got the same problem. But I was able to bypass the problem. First, instead of just clicking on the link. Just copy the URL instead. Second, paste the URL on the URL bar instead and hit enter. If that doesn't work, keep reading. Third, try the URL w/o the filename (basically just hostname+directory). This will cause it to give some error message. Forth, after you get that error message, past the same URL w/ the filename back again and retry. I follow these 4 step and able to download the fastboot zip file for QP1A.190711.107
[Essential Phone ROMs, Kernels, Recoveries, & Other] ElfinJNoty:
I have my essential Bricked

No power on, no led, no vibration, no sound, no fastboot or recovery, no adb, nothing.

I was able to get a red led blink a bit when holding volume up and plugging into PC. PC made a little noise, but nothing showed in device manager(windows10). Battery still had juice then. Haven't been able to reproduce since.

The last thing I did was try to fastboot flash the fix for no touch in recovery(flashing the two partitions to correct the firmware mismatch). Then device turned off and been in the condition stated above since.

I have tried everything I could find searching the web for potentially getting the device to do anything towards being recognized by a PC. To no avail.

Is it a goner?(hard brick) or is there some way to force it into being able to take a flash of something?

Expecting the worst at this point, but figured I'd ask. Any advice is appreciated. Thanks in advance
[Essential Phone ROMs, Kernels, Recoveries, & Other] gdmsndmxr:
I was able to finally get Essential to take my phone and they were able to unbrick and it now works. Worth a shot. I did have to pay shipping but that's not bad.
[Essential Phone ROMs, Kernels, Recoveries, & Other] someone0:
Holding the vol-down & power will not get you anywhere? I have seen where the phone appear brick, but that is because the phone is already on but stuck. holding vol-down & power will force it to reboot and into fastboot mode. Just a thought.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ElfinJNoty:
Thought I was pretty clear, "no fastboot", but thanks for the thoight:svetius:
[Essential Phone ROMs, Kernels, Recoveries, & Other] ktmom:
Ok, this is just spitting in the wind, but I read somewhere online where an individual had what appeared to be a bricked device. He dismantled and pulled the battery for a bit and the PH-1 was revived. That said, I commented this to someone in the essential Q/A help thread recently. That person was unable to get to recovery or system, but could get to fastboot but could not fastboot images. They also pulled the battery and reported that their device works now.

YMMV
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
How nice...

If you did not read my post before it was moderated for actually providing good information please reply and I'll rephrase without offending...

And mod .. please go cuddle in the corner with your blankey... Nothing I said was that evil...
[Essential Phone ROMs, Kernels, Recoveries, & Other] amoot329:
Just a quick heads up for the OP. The flashall.bat has a typo, I was going to modify it so as not to wipe the device (hate restoring everything again). This is the line that has the error:

"fastboot flash vendor_a vendor

fastboto flash vendor_b vendor"
[Essential Phone ROMs, Kernels, Recoveries, & Other] handisnacks:
OMG THANK YOU FOR THIS. I couldn't figure out why the **** my phone wouldn't boot, hahaha.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tanner1294:
Tried out Lineage 17 but it's pretty barren at the moment. I just want to go back to stock Pie but everything is pretty broken. I can get into fastboot and the system just fine, but using any of the back to stock Pie options doesn't seem to work. The batch file flashes everything fine, no errors, bootloader and critical partitions are unlocked, and it's able to boot into Android 9. But it boots up, shows a massive QR code and a gray screen with a weird orange loading circle. I can "skip" whatever the QR code is but bluetooth keeps crashing and the WiFi can't turn on at all.

Edit: I've tried using Essential's own Fastboot zip package and same thing. Just boots into a QR Code. I found another thread saying that the QR Code is part of some factory mode and to hold the power button until it reboots while the code is showing and it will go back to normal. That doesn't do anything at all. Code still pops up, no setup wizard, bluetooth keeps crashing and WiFi will not turn on. I've tried using an older BTS package, July to be specific. Same issues. I've tried using the patched TWRP-SEP boot image, same results. I'm going to try and fastboot it to official Q and see what happens. If that doesn't work I'll use the July BTS and then flash the OTA through ADB.

Edit2: Used the latest Q fastboot package from Essential here: https://www.essential.com/developer/current-builds and it's booted correctly, wifi and bluetooth are working. Now restoring the phone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ktmom:
We're you on the Q release before lineage? Maybe it's a bootloader incompatibility.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tanner1294:
I wasn't.. sort of. I used the Q novendor package so that I could try Lineage Q. I was on the last Pie update before that as I actually hadn't gotten the prompt to update to 10 yet.

Edit: I was able to get back to Pie fyi. I used the Q fastboot package from Essential again, this time it booted correctly. Rebooted and used the Pie fastboot package and it finally loaded correctly and didn't give me some weird factory mode.
[Essential Phone ROMs, Kernels, Recoveries, & Other] onema:
My titanuim back up doesn't work (FCs) after updating to android 10, is this a known issue?
[Essential Phone ROMs, Kernels, Recoveries, & Other] ktmom:
Are you trying to restore anything other than user apps? Or is it crashing on launch? Getting a logcat would probably be informative
[Essential Phone ROMs, Kernels, Recoveries, & Other] srgrusso:
Solved by upgrading Android Tools. The issue was a known bug https://bugs.archlinux.org/task/63370.
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
Is this an Arch thing or for all Linux?
[Essential Phone ROMs, Kernels, Recoveries, & Other] srgrusso:
I'm not sure. I only tested this in Arch.