yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] tanini:
Hello,

first of all thanks for the good job doing here.

I have a Problem. I was rooted and installed the bts june 8.1 no wipe a few days ago.

Now I can see the ota july update but my phone fails to install it.

Did I miss something? Are there any advices?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Did you root the June bts?
[Essential Phone ROMs, Kernels, Recoveries, & Other] tanini:
no, I rooted the may bts before.

Then a few days ago I installed the june bts without root.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Even using the CMD-here in your zips I get the same behavior. The commands only run after hitting enter, and then rebooting the bootlader (on phone). Once the phone reboots bootloader, and Windows detects the phone it'll run right through them.

Have had the same problem with ROM updates and flashing TWRP even.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
The latest ROM won't boot on my phone. I get some text that is so tiny I can't read it.

It boot loops a couple of times then the text.

I went back to the June ROM and no issues.

I did a complete wipe.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mrcooter:
I had the exact same issue, got a good quality USB 3.0 cable and the issue hasn't returned since. Tip that lead me this route, looking online I saw to make sure you see blue in the USB part of the cable. If you don't chances are, it's not 3.0.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Oh the cable is 3.0

Worked fine for Fastboot until last week. Now suddenly bugged. Maybe the cable went bad, got me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hussaination01:
I was on AICP rom . Flashed the latest P beta fastboo method . Did all wipes including the system. Now booted with no wifi nor Bluetooth. Tried the ota one same problem. Tried 8.1 and the same problem too. When I flashed a custom rom the wifi and Bluetooth work. Please help
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
There seems to be more then a few odd WiFi occurences lately.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Using AOSiP June 30th build and Nuetrino-Delphinus, and flashed the no system-boot-vendor file. No problems with mobile data or wifi.

[MENTION=5447216]aer0zer0[/MENTION] It isn't a huge deal, but the "no SYSTEM-BOOT-VENDOR" scripts are very difficult to type without using the tab autocomplete. Not that big of a deal for the majority of us, but it might help some new people out if they were a continuous filename with no spaces.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
No problem, I'll fix in next months build. Might use a acronym, less typing. Also, as a independent experiment today, in all of my free screwing off time, I used other fastboot/adb variable paths, it WILL randomly foul up flashing things.

So, if you have any ADB/FASTBOOT BINARIES OF ANY KIND, unless your not having any problems flashing, use the ones provided with the essential fastboot drivers, they just work. I won't be putting those in any more starting next month. I fully expect everyone to have essentials windows drivers and adb/fastboot from said drivers working as a pre-requisite. If you flashing more than 1 device, like me, remove the environment path, and keep your binaries separate (HTC_FASTBOOT is different entirely)

I have thoughts on other things too, lol :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
So just to clarify.

All of us installed the Essential drivers (as it's needed) which in turn installed adb and fastboot to my PC at 'Program Filesx86\Essential\ADB' so is that where I am to drop the BTS images? (Also noticed 'Program Filesx86\Essential\ADB' in my path environment variables)

Yet the Essential site recommends downloading the platform-tools from Google and adding that into the path variables. Talk about mixed signals here.

I've always just downloaded your zip, extracted and flashed straight from there for ease of access, and had little to no issues doing it that way. I hate windows lol.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Your good, keep doing what your doing. It works
[Essential Phone ROMs, Kernels, Recoveries, & Other] Zdog291:
I ran the flash all bat for July but I still cannot pass Safteynet on my phone, see attached
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
Your boot loader is unlocked and you are not running Magisk.

Is that a good guess?
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
After a clean install of Beta-1; I downloaded Beta-2 again and was able to install.

Not sure what was up.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Pretty sure it's like that for all non pixel dps
[Essential Phone ROMs, Kernels, Recoveries, & Other] Zdog291:
Yes, is it not possible to get back to safety net on stock with boot loader unlocked? I'm on the stock July Oreo build
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
To do that, you must have Magisk
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
I'm on the latest July O build, no magisk, bootloader unlocked, and passing safety net. ( And I'd know if I didn't pass safety net, my son plays Pokemon Go on my phone. )
[Essential Phone ROMs, Kernels, Recoveries, & Other] Daniel Br:
Thank you :)

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

but now it got latest beta 3. do you have beta 3 link?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NaterTots:
P Beta #2 (in the first post) is the newest P build. It's the same as the pixels #3.

Essential has a slightly different naming structure since they didn't get the very first developer preview of P.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
Working great too.

Lots of issues from the B1 build are fixed. :D
[Essential Phone ROMs, Kernels, Recoveries, & Other] Daniel Br:
You mean this update: https://www.xda-developers.com/essential-phone-android-p-beta-3-july-security/ right?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NaterTots:
Yes
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
There have been 4 P released. 1 & 2 were DPs, then beta 1 and now beta 2. XDA has the nomenclature wrong.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
I was still noticing that during a BTS adventure, only system a, or b would be erased (depending on my current slot), I was also facing wifi issues when downloading from Google Play after flashing the latest July O build, so for what it's worth I decided to try wiping system a, and b, and have had no issues at all since. Before using the BTS flash all I simply used:

'fastboot erase system --slot a'

and

'fastboot erase system --slot b'

After my phone booted up, I had literally no wifi troubles, not sure if this is just a placebo or not, but worth a shot if anyone else is having similar issues.

:highfive:
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
it does only wipe the system that it is going to boot on, mine wipes A everytime, but i only work off of A. i thought about writing those into the script, but everyone complains that scorched earth is too much. lol
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
Only because you put a wipe in the beginning and at the end... And only the first time we use your scripts...
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Whatchu talkin bout Willis?
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
essential phone

The smartphone does not turn on red
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
you broke verity?

like the red google this device cannot be trusted or something?
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
essential phone Has ceased to be included at connection on usb only the diode blinks red
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Hard reset maybe? Doesn't sound good.
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
how to bring it back to life?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
[youtube]3YxaaGgTQYM[/youtube]

No idea, are you using Linux or windows to flash? When it's plugged into the computer, is it still a essential device or does it pop up as a Qualcomm device in the hardware information?
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
The laptop finds it as Qualcomm HS usb qdloader 9008
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
That's bad. I understand only essential can fix it in this mode
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
we dont have firehose images unfortunatly.
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
Well and how to fix it
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
no idea, i think only essential can fix it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ink718:
The July firmware package does not have a "flash-all" file, please point to the correct file to flash the zip...
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
how to do it, tell in detail
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
which program to reanimate the essential phone
[Essential Phone ROMs, Kernels, Recoveries, & Other] ink718:
Are you trying to go back to stock?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Use the batch file from the July package. It will flash the firmware files just fine
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
discard the link to the firmware, and through which program to flash

---------- Post added at 06:43 AM ---------- Previous post was at 05:45 AM ----------

I launch flash-all and there writes * waiting for any device *

---------- Post added at 06:44 AM ---------- Previous post was at 06:43 AM ----------

I launch flash-all and there writes * waiting for any device *
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
I launch flash-all and there writes * waiting for any device *
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Do you have more than 1 copy of fastboot? Is your phone in bootloader mode?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
May want to read back maybe a dozen or so posts. Their phone is bricked AF, and only reads as a Qualcomm device when plugged into the PC. Can't get to bootloader mode, I don't think, so they can't use the BTS files.
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
on the off chance you are on linux with a working phone, the kludge for this is to prepend SUDO in front of every line in the batch file.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
fastboot dont work in edl mode
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
"******did you mean to fastboot format this ext4 partition"
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
I don't get that, it just starts erasing system a (or b) for me.

However I don't think the Wi-Fi issues have anything to do with the BTS zips here, Wi-Fi is bugged out for quite a few people, on P Beta 2 and the July O build. Something on Google or Essential's end I'd wager.
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
help how to resurrect the phone
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
You have asked this repeatedly, and were given a small bit of information, along with several of us just not knowing. You're going to have to try to find an answer elsewhere, because we just don't know how, or don't have the tools to help you.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Contacting Essential...and likely warranty replacement is your best bet.

If you could fastboot/ADB into the phone this might be recoverable. If you cannot fastboot/ADB-you're hosed.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
can you explain, in detail, what you did to your phone? how did you get to this point.
[Essential Phone ROMs, Kernels, Recoveries, & Other] romeowen:
Need Help: A problem with unlocking Critical partition

Hi tech-experts,

I have encountered an issue after running the command [fastboot flashing unlock_critical] in Bootloader.

Problem:

After running the command & wiping user data, my phone auto-reboots twice then stops at the message below:

//

Android Recovery

Essential/mata/mata

8.1.0/ OPM1.180104.141/272

user/release-keys

Use volume up/down and power.

Can’t load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

-----------------------------------------------------

Try again

Factory data reset

-----------------------------------------------------

Supported API: 3

//

-	If I select [Try again], the phone auto-reboots twice ---> then stops on the same message above.

-	If I select [Factory data reset], the phone wipes & formats data ---> then auto-reboots twice ---> and then stops on the same message above.

-	My phone cannot be power-off. Now the phone is always "Power-On" and staying on the same message above.

Attempt:

-	try to run the command [adb devices] ---> {List of devices attached: <blank>}

-	try to boot into bootloader by running the command [adb reboot bootloader] ---> {error: no devices/emulators found}

-	try to run the command [fastboot devices] ---> <nothing happen>

-	try to wipe/erase UserData by running the command [fastboot -w] ---> {waiting for any device}

-	try to flash TWRP Image by running the command [fastboot flash boot twrp11.img] ---> {waiting for any device}

-	try to run the command [adb shell twrp sideload] ---> {error: no devices/emulators found}

Reasons:

My original goal was:

1.	unlock Critical partition

2.	back-to-stock (full dumps) to current build OPM1.180104.141 (Oreo 8.1 April)

3.	online-update my phone from <Essential.com> to newest build OPM1.180104.267 (Oreo 8.1 July)

4.	root my phone

Since I am not sure that I have unlocked Critical partition previously, I did the command [fastboot flashing unlock_critical]. Unfortunately, it screwed up my phone. I have already unlocked the bootloader + rooted my phone.

I use the USB-C to USB 3.0 cable to connect this phone to my PC (Windows 7 Pro 64-bit) --> No issue with this cable on previous update + rooting.

Current phone status:

Essential PH-1

Android Oreo 8.1

Build OPM1.180104.141

Carrier: Canada - TELUS

Bootloader-unlocked + Rooted successful on April, 2018

Using ANKER Powerline USB-C to USB 3.0 cable

Does anyone of you know how to fix this problem?

This is my 1st post on the Xda-Developers Forum :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
is it a red screen with text at bootup?
[Essential Phone ROMs, Kernels, Recoveries, & Other] romeowen:
Hi, this is what it appears on my phone: (Please also see the attached screenshots)

//

Android Recovery

Essential/mata/mata

8.1.0/ OPM1.180104.141/272

user/release-keys

Use volume up/down and power.

Can’t load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

---------------------------------------------------------------------------------------------------------

Try again

Factory data reset

---------------------------------------------------------------------------------------------------------

Supported API: 3 (@bottom, text in white color)

//

- I can only use [Volume Up/Down] button + [Power] button to select {Try again} or {Factory data reset}

- If I select {Try again}, the phone auto-reboots twice (Screenshot 2 & 3) ---> then stops on the same message above (Screenshot 1-1 & 1-2)

- If I select {Factory data reset}, the phone wipes & formats data ---> then auto-reboots twice (Screenshot 2 & 3) ---> and then stops on the same message above (Screenshot 1-1 & 1-2).

- My phone cannot be power-off. Now the phone is always “Power-On” and staying on the same message above (Screenshot 1-1 & 1-2).

Here is the links / URL for Screenshots:

Screenshot 1-1:

https://www.4shared.com/s/fN8Sdi4n2ee

Screenshot 1-2:

https://www.4shared.com/s/fZ9WjbDFefi

Screenshot 2:

https://www.4shared.com/s/fNoYjuDpjfi

Screenshot 3:

https://www.4shared.com/s/frMxNOYgEfi

Thanks, best regard :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
send me a PM
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
Interestingly enough I got that message also when trying to go to B2.

I wiped the phone multiple times.

Tried installing multiple times, even downloading multiple times.

I changed cables, etc.

Nothing.

I went back to B1 and everything was fine.

I charged the phone completely and redid the process with the same cables and it worked.

I was up all night last week struggling with that message.

I have no idea what went wrong or right in my last attempt.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
did that happen when using the BTS, or sideloading?
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
Flashing BTS.

Checked the script and even executed line by line.

Same result.

My Mac had been rebooted multiple times.

I used two different cables (not stock).

I changed USB-C ports.

I have no idea what I did to get past it. I took a break and let my phone fully charge.

It was at 70-80%.

The only real difference I can point to was a phone at 100% when I flashed.

I never got an error.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
now that is odd
[Essential Phone ROMs, Kernels, Recoveries, & Other] romeowen:
What "B1" and "B2" are you refer to? :confused:

Can you be more specific on your solution?

(with command/script)

I am a newbie.

Anything from you will be very grateful.

My phone is charging now after 1 day of idling..... :crying:

Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
p beta 1 and p beta 2

so, can you tell me how you got here?
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
Have your tried going back to a previous version?

I went back to P-Beta1 just to see if it was my phone or something else.

I used the scripts that format the data and wipe the phone.

The P-Beta1 installed and my phone was fine. So I knew the phone wasn't borked.

I set up the phone as Beta1.

I then used the Beta2 scripts and things worked.

I don't remember doing anything different, had wiped the phone and used the same scripts.
[Essential Phone ROMs, Kernels, Recoveries, & Other] vanzyzz10:
flew the bootloader on the smartphone, how to solve the issue help
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Just in response to your other past posts: you have a bricked device. No fix for a brick unless someone knows otherwise.
[Essential Phone ROMs, Kernels, Recoveries, & Other] pdrayton:
Been at this ALL day. Can't flash an image - I always get:

FAILED (remote: Flash Write Failure)

I've got bootloader and critical unlocked. And I've done a complete wipe with TWRP, and many, many other things. I've run the flash batch files manually line by line, and they fail randomly, even after I restart in bootloader. I have tried it on a windows 7 laptop and windows 10 desktop with brandnew usb 3.1 cable.

I'm trying to flash "PPR1.180510.022_BACK_TO_STOCK", but maybe I need a different rom? I don't know what my system was on before, but I took all the updates up til 7/12, so I'm thinking it was 8.1. .

I need this phone for work on monday.

HELP! PLease!

EDIT: Just tried the instructions from here and when wiping in TWRP there is an error "Could not mount /data and unable to find crypto footer" I've been having the "device is corrupt" red error too, but thought that was something I could fix later, when I can boot to a ROM.

EDIT 2: Got rid of the crypto error by formatting data in TWRP. Flashing a stock rom from AOSiP now. Fingers crossed, but whiskey bottle at the ready for a screw this, life is too short melt down....

EDIT 3: WOOOOOOT! Got AOSiP 8.1 from here on it through TWRP. Should I count myself lucky and skip root? Hmmm, that's how I got in this mess in the first place

For anyone in the "Failed to write to partition" error boat, try TWRP format data, then wipe everything, then flash the AOSip rom from TWRP. If you can't boot into a rom, you can mount the phone as a drive in TWRP and copy the ROM over.

I'm probably wrong about this, but it seemed the keys to my problem are not formatting the data partition, and using the wrong ROM. Say that fast 10 times "Wrong ROM".

EDIT 4: Geez. Celebrated too soon. Rebooted, and it's back at the bootloader screen and giving me this error when trying to flash TWRP FAILED "(remote: Error flashing partition.)" WTF? Can't flash twrp, can't do anything. What is going on?
[Essential Phone ROMs, Kernels, Recoveries, & Other] romeowen:
Hi,

Originally I want to BTS OPM1.180104.141 (Oreo 8.1), but I'm not sure I had unlocked Critical partition before or not. Hence, I did run the command [fastboot flashing unlock_critical] in Bootloader. After that my phone kept auto-reboot few times and displayed this error message.

Now my major dilemma is that I'm currently unable to boot into Bootloader. :(

As a result, I cannot flash any BTS or Twrp...

How did you able to boot into Bootloader from this problem?

My phone current status:

Android Oreo 8.1

build OPM1.180104.141

- already rooted

- already unlocked Bootloader

- use USB-C to USB 3.0 cable

Thanks

---------- Post added at 02:20 AM ---------- Previous post was at 02:06 AM ----------

No, I cannot go back or flash BTS to any version, because currently I cannot boot into Bootloader.

I tried the scripts that format the data and wipe the phone by running the command [fastboot -w]. It showed {waiting for any device}.

Any clue how to fix? :(

Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
have you installed the windows drivers for the phone?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
wgat do you mean it wont boot to bootloader?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
your phones broke mate, no idea how you got there.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
This is gonna sound silly...

Go find a USB 2.0 cable... And try that... Preferably and A to C...
[Essential Phone ROMs, Kernels, Recoveries, & Other] kakabobo:
is this to use the Google latest adb pack or the essential adb pack that come with the driver package?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
use essentials adb/fastboot pack from their driver. if you install the windows driver, it sets a environment variable to use it by default.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ink718:
Anyone notice a better data connection after flashing the July fw?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
both p beta 2 and july 8.1 have been great so far. everybody get their flashing issues fixed?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
July O and P Beta 2 have been awesome builds, but still having major WiFi issues unfortunately with both. Other then that I've had great connection with mobile data and some more then decent battery life.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
my wifi has been great, i just dont get it
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Well I'm not sure if this has anything to do with it or not, but the last Telus variant build was in June, and apparently Telus has reached end of life with the Essential phone. I wonder if there's something needed and those Telus variant builds that aren't in the open market builds. Telus didn't give me much info on it pretty much told me they want me to buy a new device.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
i mean maybe, but theyre all supposed to be the same.