yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
I can confirm, for some reason wifi just isn't what it was previous builds. Flashed multiple times, fresh clean install etc. No issues previously, but sometimes wifi will have a strong connection but just stops data transfer for a while or really slow speeds. Know it's not the wifi because the other devices I have are working as they have been. Figured it was something / some changes in this months release but I can live with it. Comes and goes. Updating apps in the play store is the only real noticable instance for me at least.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
see that i have never seen, my wifi cooks on playstore. im using 5ghz band tho
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Mines screwy on 2.4 and 5ghz connections, sometimes though I'm able to download a couple largish apps, but then it just drops to several KB/s..

For example, last time I used the BTS, my battery drained 22% from Google Play alone, just attempting to download PUBG Mobile, and it took over an hour or more, wasn't timing it.

Then if I start to switch between 2.4 and 5ghz while downloading my downloads go quick for about 60MB tops, then instantly KB/s.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Understand Google play has some download issues recently
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
Happens to me on both bands. Tried clearing data for play store and services framework etc, removing and adding google account back, but still the same. Since it's most noticable on the store, maybe that's the issue though and not with the actual system. Regular cellular data doesn't act this way though which I why I thought it was an issue with this release. Oh well, I can deal with it, just wanted to mention it for taking the issue is all.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I just blew my phone away and reflashed p beta 2, full wipe, using the BTS. WiFi is working perfectly and Google updated all my apps as fast as can be imagined.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
I had to do the same thing to get B2 to work properly.

Some settings or API changed and cases things to be wonky.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I blew mine away cause I was messing with gsi's was going to back to p beta anyways.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
Ahh. I'm not on P. May try it out when I have time to see if it's any different. Work and life has been crazy lately.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I hear ya. I do it late at night when I get some peace and quiet
[Essential Phone ROMs, Kernels, Recoveries, & Other] kittygotwet:
Am I doing something wrong?

I currently have .166 build. I grab the may 8.1 build and flash stock boot.img after twrp.

After downloading the update I get "installation problem." It'll ask me to try again and re-downloads the whole update...
[Essential Phone ROMs, Kernels, Recoveries, & Other] thelangosta:
Sounds kind of kinky lol
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
WiFi fix here:

https://www.reddit.com/r/essential/comments/90e05z/psa_proven_google_play_slow_download_speed_fix/

Can confirm it works, got PUBG downloaded in less then 10 minutes.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
hahahaaaaahahaaaahahahaahahahaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.....sorry, said it wasnt the firmware, lol
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Don't be sorry, you were totally right was just confusing as hell that only some people had issues while others didn't at all.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
It seems to me...given the fix...that the phone is treating Play downloads as WMM lowest priority downloads (if the router has WMM on its end)....so why is it doing that?

It could still be a goofball firmware thing-treating Play downloads as something de-prioritised to hell to save battery. WMM isn't new (over a decade old IIRC), and at this point all routers should have it probably by default by now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Yeah, but, I needed a good laugh. I know. Has anybody went to apkmirror and grabbed a beta play store?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
LOL...the last time I did that (both GP and aGPS come to think of it)...I broke my ROM install and had to clean flash :silly: :victory:

FWIW before the Essential OTA July update we were seeing that behavior on AICP ROM on late-June-patch builds. The behavior has since gone away with middling July patch AICP builds. We never figured out WTF was causing it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jamiejames:
Can't install drivers on Windows Vista 64. Any way around that? Lol yes Vista, don't judge.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kittygotwet:
What am I doing wrong?

grab the May .166 since the current build on my PH-1 is on that. adb twrp and went to install. Worked, i think and when I went to update the phone it couldn't update.

Fastboot flash boot stockboot.img and same thing, once it tries to update it fails.

Should I grab the June patch?
[Essential Phone ROMs, Kernels, Recoveries, & Other] m0bstr:
I am trying to flash the Android P beta 2, it installs and boots into the bootloader, it wont install, anyone have any ideas how to fix it?

My phone is stuck in a bootloop now
[Essential Phone ROMs, Kernels, Recoveries, & Other] Maxr1998:
Yup, mostly perfect. I sometimes get WiFi dis- and reconnects that last less than a second and are barely noticeable, but apart from that, everything works fine :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
You've got a kernel mismatch more than likely...

How? I'm not sure...

Or... A bad flash...

That's usually a bum cable... If the flash actually succeeded... I've had the best of luck with a USB 2.0 A-C...

Or... You're flashing Magisk before booting up the first time...
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
U sound like me, except i keep trying to flash pretty much any system image and try to get it to boot. I have only got pixel 2 P preview to boot, fixed the cam but no mobile data.. we should share notes.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Hi!

I just tried to put my essential phone back to stock, but after i have finished i get the message "Your device has loaded a different operating System". I have wiped the phone first with "fastboot -w". After that i clicked on "Flash-all-WIPE.bat". Restarted phone when finished. Loaded into Fastboot Mode with Volume Down and Power Button. "Fastboot Flashing lock".

Phone is starting normal after the message, but something i must have done wrong. I was on 8.1 July and downloaded also 8.1 July stock from the first page. However before and after it said Security Patch Level June 5. Is that normal or might i have rooted 1 week ago accidently to an older rom? (I didnt, i just checked the download history folder)

Any suggestions? Thanks!!! (:
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
it sounds to me like flashall failed, and it booted to your other slot. Did you watch the bat file at all while it was going?
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Hey aer0zer0! Got it fixed 30 min ago, just wanted to delete my post and saw youve answered already. Well i have unlocked the bootloader again and did the same procedure, but this time with flash-nowipe. I had a closer look at the batch working and saw in a step "fastboot flashing unlock_critical" failed because its locked. or sth liked that, but it continued. However it looks like its on stock now, no warning message after locking the bootloader again. is it a problem that i never unlocked critical?

And i somehow managed to be on june version before, despite ive got the phone just a week ago and 100% installed july root rom. Because now i got the slow play store download bug many are talking about. However i hope my phone is now like i got it.

Cheers!
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
The .267 should be July OTA. that's strange.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
High chances that i have messed up somewhere, but i have downloaded 100% July versions (for root and for stock) I just hope that i dont have unnecessary files now sitting somewhere in the storage, because i need every last space.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
send me a screen shot of your kernel info and system version
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Just to clarify: I am on July now, but my rooted phone and the first "back to stock" attempt somehow was June Security Build. Sorry for my bad english if u thought i am still on June. If you were asking about kernel because of another reason please forget this post. However i have sent you the screenshot :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
nope, thought you were still on june. your all good though, happy flashing :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
hey guess what!!!!! P beta 3 BTS is up. I decrypted the OTA file, and created a BTS based on that, i also used the fastboot images and created another. 2 to choose from.

Have fun :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
I got havoc os, bootleggers, and arrow gsi to install and boot up. Everything seems to work except play services. Swamped witj device not certified errors.. u know how to work around it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
you can hide root with magisk from play store, wipe app data from playstore and try that? Not sure what else to do with that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Cool, i only flashed a stock kernel the last test and it wasnt rooted and still same crap. I think i need to use a root explorer and edit the build. Prop. Fyi, every single treble rom or pixel2, or pixel2 xl system image flashes with few probs, as long as u fastboot -w, flash it to both slots, then flash one of our kernel after
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
No verity breakdown?
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Nope.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 12paq:
Yup, saw that today. Thanks for being on it so quickly.

I have never had a problem doing a full -w wipe BTS version upgrade. It's always very clean, and far less bugs. Much better than OTAs and side loads.

I'm thinking of doing a ADB pull back up guide for those who don't know how to backup folders and files before they do a full wipe BTS.

There are many ways to backup /sdcard/ data like photos and Titanium backups, but an <adb pull> of certain /sdcard/ files like photos, Titanium Backup folders and other data is just SO easy. A backup ADB pull of multiple folders is just fast, more people need to know.

I am tired of the complaints of lack of nandroid backups.

Haha ? Just. Learn. ADB pull/pull.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Exactly, clean is clean. I hate dirty flashing.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tech_Savvy:
What command do you use to use adb backup of sdcard and data and apps? Didnt know it was possible to back it up with adb?
[Essential Phone ROMs, Kernels, Recoveries, & Other] galakanokis:
You can just use adb pull file path to grab what ever file or folder you want. I use to use it to pull the build.prop file to my PC, edit it and push it back when I wanted to make tweaks but stay unrooted.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
i am really sorry that i have to ask again, but when exactly is "fastboot flashing unlock_critical" necessary? I Remember that the batch window shortly said that xxx files could not be "written" because its locked. I have never had it unlocked btw. . Im just asking because i experience high idle battery drain since im back to stock. It has most kindly another reason, i just want to make its not the lock_critical thing resulting in a not working 100% correctly android system causing this drain.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Unlock critical allows you to flash the critical partitions in the BTS
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
:o I am sorry but i dont know what that means, is it necessary to do that?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Did you get back to stock? Then yes, lol.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Ive always been to stock (no Lineage OS or sth like that), just unrooted again now. So should i do it again with unlocked critical? Thanks for your answers :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Did you have critical unlocked or not? I'm confused. You could try the P betas, the one yesterday is great. Battery is tremendous.
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
I am sorry for being unclear, i also feel a little ashamed to spam here with my noob questions. I never had critical unlocked ever, never touched it. and despite getting the message writing "mdtpsecapp_a", "mdtpsecapp_b" (and maybe more) could not be written, the flash went through and the device is working. Everything seems working well except battery idle drain. As i said it has probably another reason, just want to make sure its not the case because these files could not be written.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
It's entirely possible you have a firmware mismatch
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Thanks, ill do it again with unlocked critical!
[Essential Phone ROMs, Kernels, Recoveries, & Other] colinn24:
180610.066 and 180610.030 didnt support China Telecom3G(cdma)，i cant get apn settings in the cellular interface，the older version run well
[Essential Phone ROMs, Kernels, Recoveries, & Other] 12paq:
You can do all kinds of backing up of Android via ADB. For just the file you want to save from a -w full wipe just backup those folders only.

For example if you want to back up your pictures or titanium backup to your PC simply:

adb pull /sdcard/TitainiumBackup/ c:\whatever-folder-on-your-PC\ Then reinstall your apps and data with Titanium. Never system app data. I let the app store reinstall most apps. I only reinstall apps with data for a few apps.

For photos:

adb pull /sdcard/Pictures/ c:\whatever-folder-on-your-PC\

To move them back to your phone just:

adb push \c:\whatever-folder-on-your-PC\ /sdcard/

You can also adb push and pull multiple files at the same time by listing them in the string in the command line.

It's much faster than using windows.

This is off topic, so I am done here. Hope this helps and good luck.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rambleon84:
Any idea what i am doing wrong? Flashing the flashallwipe.bat and everything works fine except for the wipe. Everything booted and 9.0 is up and running fine but not sure why fastboot -w doesnt want to work. Really wanted to start with a clean slate. Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Try a different adb/fastboot like the one that comes with essential drivers
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
What does it show in your device manager in Windows? Boot into bootloader and plug/unplug your device to see which it is. If it shows as "mata", that's your issue. Manually update driver to bootloader or adb driver. For some reason I have to do this almost every time. Doesn't seem to stick.
[Essential Phone ROMs, Kernels, Recoveries, & Other] xterminater07:
For android device, it does show essential instead of android or adb. I tried to do the manual driver adb in windows 10 but it wont let me, i select the device list and chose next but it said your device has latest driver
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
Don't choose the auto function, pull from list of other installed drivers manually. (It's a different option from where you were starting. Just right click the "Mata" or whatever and update driver.)
[Essential Phone ROMs, Kernels, Recoveries, & Other] xterminater07:
That's what I did, manually add a driver until I get to the place it said Essential, I click on the name inside the box and hit Next and it just said I have the latest driver. Any other way to manually install the google adb driver?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
Go to "Device Manager" in Windows

Right click and select "Uninstall Device" WHILE in bootloader mode. Don't check the box to uninstall driver though.

Different drivers for different states is all. You can also be sure it's the right one by unplugging and plugging in device, seeing which one disappears etc. If you are in bootloader and see "mata", that's the MTP driver which is the issue.

After uninstalling unplug and plug in the Device again. Locate which is your device and right click, select update driver.

Select "Browse my computer for driver software".

Then select "let me pick from a list of available drivers on my computer".

Find and select the right one for bootloader. For me it was called "android bootloader interface".

You can follow this process until you find the right one if you aren't sure. Each time you update the driver, try typing in cmd "fastboot devices". Once your device shows up, should be good to go.
[Essential Phone ROMs, Kernels, Recoveries, & Other] xterminater07:
Will definitely try this when I'm home.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ZooBaAr:
You can get all the stock images AND drivers for this phone from Essential site now.

Read This

first and the link you need is there, takes you to their dev page with destructions too.

Oreo also if you are so inclined.

Read. Read some more, this phone is easy.

Zo0

Thanks invisiblek for getting these out there first.
[Essential Phone ROMs, Kernels, Recoveries, & Other] artpena2323:
Anyway to restore to stock thru a MAC? Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Do you have fastboot working in shell?
[Essential Phone ROMs, Kernels, Recoveries, & Other] artpena2323:
Yes
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
What happens if you take the commands from the .bat file (open it in whatever text editor) and flash them 1x1
[Essential Phone ROMs, Kernels, Recoveries, & Other] artpena2323:
Let me try that. Thank you
[Essential Phone ROMs, Kernels, Recoveries, & Other] artpena2323:
That worked. Thanks again!!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] bryanus:
I'm on a Mac and was not able to get my PH-1 flashed back to stock running the shell script. No matter how many times i tried, I got a kernel panic towards the end of the last few commands. I also tried running them one by one and had the same problems. It always crashed when 'writing system_b 1/4...'.

Finally got it to flash successfully through bootcamp/windows 10.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 3's&7's:
PS C:\Android> fastboot flashing unlock_critical

...

PS C:\Android> fastboot flashing unlock_critical

...

My results:

fastboot flashing unlock_critical

...

FAILED (command write failed (No error))

finished. total time: 0.019s

This method appears to have not worked for me...anyone else experiencing this? I noticed some Pixel 2 users complaining about the same through some light research.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Hung0702:
I'm having issues booting. I restarted my device after updating some apps and now it's stuck at the boot animation. I'm on NMJ32F. Could I flash the back-to-stock image without losing my data? I've already copied my internal storage, but it's time-consuming and tedious to redo all my the settings changes for apps and stuff.

EDIT: I flashed the full NMJ32F factory image and nothing was wiped! I just need to flash magisk and xposed again and I should be fine. Looks like everything was preserved. Hooray!
[Essential Phone ROMs, Kernels, Recoveries, & Other] kleinbiker:
It looks like the same process for restoring to stock is listed at the Essential site - https://www.essential.com/developer/current-builds.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Quantumrabbit:
So, if one did flash all on the sprint version to get all the Sep and Oct and Nov updates... And the phone is identifying within about phone as the 23F instead of the NIMIC... Would that have a negative impact on the reception on the sprint network?

I probably should have tried the phone before on the network, but I was trying to switch it off the sprint variant, hoping flashing all would take care of that. It didn't.

I know the radio and wifi seem to be the only difference, so can I just flash those back over and retain the rest of the updates? Or do I have to go back to all the sprint versions?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
If you are downloading just the update patches which are usually less than 100mb, not sure if it would work just to go back as I'm not sure what parts it's patching. But if you download the full build, should be a rather large file, extract all and run the flash all bat, it will take you back fully. I would also recommend backing up user data and running "fastboot -w" to wipe everything and start fresh which would also prevent any bootloops.
[Essential Phone ROMs, Kernels, Recoveries, & Other] kirschdog1:
Deleted
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Get the adb fastboot from Google or essential. It's your version
[Essential Phone ROMs, Kernels, Recoveries, & Other] xNotta:
The bold underlined text is slightly confusing me.

I know from previous experience that the bootloader unlock is necessary for root/modifying stuff.

I am assuming that you mean you do not recommend re-locking bootloader and critical.

However, it sounds like you are saying that you do

NOT

recommend unlocking bootloader and critical.

I read it like this:

Am I correct with assuming that it is not recommended to re-lock bootloader and critical? Leave them both unlocked.

First day with my PH-1. I am probably over reading everything right now. Sorry for being an idiot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jdgesmlls:
The recommendation as I read it (and this is universal with any Android device) is that re-locking a bootloader (normal or critical) should only be attempted/done when a device has been returned completely to stock . The Full Dump packages provided in this thread will return the device to complete stock configuration (using the Wipe option). They flash both A/B partitions with images provided by Essential. Yes, anything not backed up elsewhere will be lost. Re-locking the bootloader (normal and critical) will also each wipe the device. The same as when an unlock (normal and critical) is done.

There is separate debate as to *why* you would re-lock the bootloader. Again, similar to other Android devices, you would only re-lock the bootloader if A) You want to run complete stock and rely only on updates provided by the manufacturer or B) The device needs to be returned for any type of warranty service.

On Essential's own site, it references unlocking and re-locking the bootloader depending on which release the user wants to run. It doesn't mention anything about unlocking/re-locking critical. The need to unlock critical comes when anything other than stock images (custom ROMs. kernels etc.) are to be used on the device.

I've only had the device for two weeks as well and this page is a very good reference: http://mata.readthedocs.io/en/latest/