yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
I kinda thought the whole locking yourself out bit was a dead giveaway. Lol

You are, it's fine. Read Read Read. Can't stress it enough.

Start with this. http://mata.readthedocs.io/en/latest/

Let me give you advice

1. Don't lock your bootloader or critical partitions, ever. Keep in mind I expect you want root, custom ROMs, kernels, etc. Just don't, if something screws up, you can get pulled out (unless you break bootloader somehow and end up in EDL mode, then your hosed). That is a real thing, but it's even sillier to lock your bootloader and critical, then your phone doesn't boot, and you can't do anything to get back.... that's just dumb paperweight.

2. We will probably never have permanent twrp, our twrp is janky, but works. Don't bug people.

3. GCAM works pretty well, and saves an otherwise mediocre camera experience.

4. Before you even get started,make sure you have good USB a--->c cables, and essentials windows driver (if that's you) installed. Make CERTAIN CERTAIN CERTAIN you have a solid, working adb/fastboot environment. I have typed it soooooo many times, the letters ad autocorrect to adb/fastboot.

5. Lastly, there's a link to a discord group in the LOS thread OP. It's the best help you can get when stuck, even though we spend most of the day talking to a bot and seeing what he says back....lol

Good luck
[Essential Phone ROMs, Kernels, Recoveries, & Other] jdgesmlls:
OK, so I am the last one to want to spread any false information... but if we are talking about giving up any and all desire to tinker with the device (complete stock) for purposes of warranty work say... Is there a real risk re-locking the bootloader (normal and critical) if and only if you have completely returned to stock? (i.e. fastboot flash w/ wipe the full dump packages?)

I believe your references in #1 are if someone doesn't make absolutely certain they are completely stock and attempt to re-lock the bootloader (normal and critical)?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
If that's the case, yes, it's fine. But I would certainly boot the phone and check it out fully prior to locking those partitions again. What I have seen is people locking everything before booting it up, and it doesn't boot , then your kinda screwed.

But if your plan is to tinker. Just leave everything unlocked, it's safer against error that way.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
3.14159265359 is a comin'... ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] runderekrun:
Android Pie.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jdgesmlls:
Fastboot/OTA images are available on Essential site. :good:
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
OP Updated with P Official BTS, Enjoy :)

Also: I have no idea whatsoever whats happening with firmware for LOS based roms stuck on 8.1. Dont know if anybody wants to flash the P firmware and tell me? lol
[Essential Phone ROMs, Kernels, Recoveries, & Other] Ascertion:
I am so impressed with Essentials software support. Really hope the PH-2 comes soon.

Thanks for uploading P Official! I'll be updating from here.

P.S. If you guys are having any issues on Windows, try these fastboot/adb sdk files straight from Google.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
the only problem i have seen with those (and i like their formatting better) is appends an extra _ when flashing partition that are a or b specific
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Aaaaaaand that's what I was waiting for. I'm not a developer in need of a sandbox, and I rather like my OS to be a stable release. Looks like it's time to make a backup of AOSiP and play with an Essential P.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Dude.. you're fast.. Thanks! Noticed that it's still based on Jul Security update. Guess there's another one coming soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NikoZBK:
It's actually the August patch, the string wasn't updated.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Thanks for the reply. By the way, are you rooted? Not sure if I can take the Magisk Patched root image created on a PH1 to be used on other PH1 units?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NikoZBK:
I am rooted, patched the stock boot image with magisk manager and flashed with fastboot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
[MENTION=4802051]Somcom3X[/MENTION] says p firmware will work on 8.1, at least carbon. So I upped a p novendor as well. Enjoy :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
That's excellent news. I didn't have the time to mess with it last night to see
[Essential Phone ROMs, Kernels, Recoveries, & Other] csrow:
Is it possible to just update the non-active partition and then switch the active partition to that partition so that one can keep a copy of the old version?

Do both partitions have to be updated in order to work?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Modify the batch file to do any side you want. Simple
[Essential Phone ROMs, Kernels, Recoveries, & Other] csrow:
That worked fine. I just updated the unused partition to Pie and left the Oreo on the other partition.

Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tech_head:
I wonder if you can leave TWRP in slot_b and flash, boot, etc into slot_a
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Sure. Hard part is switching slots in is to boot to it
[Essential Phone ROMs, Kernels, Recoveries, & Other] :
Why is there remnants of twrp files in the stock boot ramdisk. Thats what i want to understand and possibly utilize.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tvisforme:
IIRC this may cause issues given that /data is shared between the A and B ROMs. If you boot into P it would update Android data, which Oreo might conflict with.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tribulationwolf:
quick question. What is the difference between the ota image and the fastboot image?
[Essential Phone ROMs, Kernels, Recoveries, & Other] dayh8:
Could someone please give me the apk for the stock launcher for the .091 Pie release? I was using the pixel launcher via apkmirror, and after switching back to the stock launcher it seems to not update, even using the OTA to update (getting API outdated messages on boot) and i'm hoping getting the right version manually installed will get me back on track. Other ideas appreciated. Thank you all.
[Essential Phone ROMs, Kernels, Recoveries, & Other] arealcoolhand:
OTA is only the update files while the fastboot image has everything you would need to get back to stock.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jdgesmlls:
Here you go...
[Essential Phone ROMs, Kernels, Recoveries, & Other] Naruyasha:
I'm having trouble wiping all the user data, I used the flashallwipe bat file in the latest Pie update but apparently the command for wipe is not being recognized or something because the phone starts with the Pie update but also with everything I have installed... what could be wrong? in every oreo update the flashallwipe worked fine but now it doesn't :/

Thanks! and sorry if I'm being a nuisance
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
What's the cmd prompt say when doing it?
[Essential Phone ROMs, Kernels, Recoveries, & Other] dayh8:
Thanks so much!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Naruyasha:
it says this:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w

wiping userdata...

CreateProcess failed: The system cannot find the file specified. (2)

error: Cannot generate image for userdata

But that's when I try to wipe data on my own and if I run the flashallwipe file it never says wiping at any time of the process, it just flashes everything and the bootloader restarts and after that it boots up with everything I have installed. I want a fresh clean install of Pie :crying: maybe I'm dumb and that's not even the correct command :confused:
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
Works with AICP as well
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
That's odd, because mine gave a successful creation of a userdata filesystem when I just ran it about half an hour ago
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Nothing wrong with the command, might be your adb/fastboot (see OP)
[Essential Phone ROMs, Kernels, Recoveries, & Other] csrow:
I think you are right about the data settings changing once Pie comes on. Once I booted into Pie, I didn't go back to Oreo. But it was nice knowing that there was a working back up in case of a problem.

Instead, I installed TWRP in the Oreo partition and then made a full working back up of Pie in the other partition. This way, I don't have to fool with re-installing the boot image and then rooting when I restore from the back up.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Might clean the links in the OP up tonight, streamline it some. [MENTION=3053466]RandomPooka[/MENTION] [MENTION=8726540]IH8TouchWiz[/MENTION], [MENTION=4388555]Skripka[/MENTION] and others, anything else you think i should add?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Maybe a zip of JUST the ADB and Fastboot executables, since they're not included in the P release zips now? That way the utilities to do it are still here in the relevant thread, but not being redundantly packed into every new zip that gets posted. Sort of like the GCam thread having the core files and then all the 900 billion different cameras to choose from :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Naruyasha:
Thanks! it worked it was my damn laptop :eek: now I have a clean install and also rooted :victory:
[Essential Phone ROMs, Kernels, Recoveries, & Other] kaivorth:
Currently on 8.1 stock rom rooted with the elemental x kernel.

Can I just take the OTA update to 9.0 or am I going to have issues? Please advise :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Quantumrabbit:
I think I'm in trouble. My fastboot is acting up on me.

I can flash all the files, except for System. I've tried using the drivers from Essential, while yield this issue:

C:\Program Files (x86)\Essential\ADB>fastboot flash system_a system
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/5 (524284 KB)...
FAILED (remote: unknown command)
finished. total time: 0.281s

So after reading through the thread again, I tried updating to the new Google versions of adb and fastboot (r28). That does change the error, but it doesn't fix it:

C:\Program Files (x86)\Essential\ADB>fastboot flash system_a system
Sending 'system_a' (2097360 KB) FAILED (remote: Requested download size is more than max allowed)
Finished. Total time: 0.000s

So... now I'm like 90% of the way to Pie, but I don't dare leave the bootloader to try and boot since I haven't gotten system flashed. What now?
[Essential Phone ROMs, Kernels, Recoveries, & Other] msuki:
Hi,

someone could create backup file of system partition of android pie in TWRP and upload here?

Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Quantumrabbit:
I decided to try again with yet another cable I had laying around, just in case. This time, same laptop, r28 version of fastboot, I get this:

So I took my Windows Update that was pending, rebooted, googled around again, saw the notes for the new verbose command, thought I'd try flashing with verbose logging to see if fastboot would give me better errors, went back to the cable that worked the first time....and system_a flashed just fine during verbose. So I flashed system_b without verbose, and it went just fine.

I have no idea why fastboot is so farking picky, and I wish google would make it robust enough to support various cables and usb 1.0, 2.0, and 3.0 ports. This has been a royal pain.

At least I'm on pie. :cool:
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
Why would you want to do that? The BTS image already has it. There won't be any difference.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
There are quite a lot of bad cables out there. Better it does not accept the cable than a bad flash which will brick your device.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Quantumrabbit:
I don't know if you've noticed the pattern from googling around, but it seems like people often go buy a new $3 cable at walmart after their nice cables don't work. For instance my nice USB 3.0 cables really don't work for this. But my crappy old usb micro cable with a dongle to convert it to USB-C does. And my nice Anker USB 2.0 usb micro with the same dongle doesn't. It seems like only crappy cables work because fastboot doesn't accept fast enough writing or something.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mobileman88:
I am experiencing the opposite. All the crappy cables either don't work or transfer slowly
[Essential Phone ROMs, Kernels, Recoveries, & Other] persin:
Firmware fix

this is great
[Essential Phone ROMs, Kernels, Recoveries, & Other] droidstyle:
edit...nevermind!
[Essential Phone ROMs, Kernels, Recoveries, & Other] IH8TouchWiz:
These are the Essential Phone device forums, not the "Alcatel Go Flip 4044W TMobile" device forums. Go to correct forums for this and ask your question there.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Lol, really?
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Do you have the 1.6 Cupcake firmware for the Motorola Devour? Need this immediately.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Skripka:
But what about getting GNU HURD on my Samsung Galaxy SII Epic 4G Touch!! I need GNU HURD on my work phone NAO! Also working MS Outlook!
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Also need a version of Magisk that will work on these devices.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Hmm, only 3 posts ever. Guess I shouldn't flay him.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nummer:
CaN I gEt A KiTkAt CuStoM rOm fOr mY sAMsUnG FaScInAtE?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nicoconepala:
I just can't flash pie on my iphone SE :confused: I don't know what i'm doing wrong :silly:
[Essential Phone ROMs, Kernels, Recoveries, & Other] persin:
its for the kids. under the age of 10. i have a galaxy S8+ that i bought on Verizon and switched it, thanks to this site, to T-Mobile.

---------- Post added at 04:06 PM ---------- Previous post was at 04:04 PM ----------
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Do you have a essential phone or not?
[Essential Phone ROMs, Kernels, Recoveries, & Other] jdgesmlls:
I just wanted to report, my curiosity got the best of me... I went back to complete stock out-of-the-box.

1. Flashed BTS 8.1 July release, and added an extra 'fastboot -w' for good measure

2. Booted up and did minimal setup, everything was working.

3. Factory reset, booted up, and went back into bootloader.

4. Locked critical, went through erase and booted up. I did minimal setup again but I don't think this was needed.

5. Factory reset, booted up, and went back into bootloader.

6. Locked bootloader, went through erase and booted up.

I'm back running P-R1, rooted and all works as expected.
[Essential Phone ROMs, Kernels, Recoveries, & Other] persin:
i have my S8+, but my kids use this stupid phone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] droidian5:
Essentially the same........
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
Your kids use an Essential phone, then?
[Essential Phone ROMs, Kernels, Recoveries, & Other] msuki:
I trying use this as GSI image of Android P. https://xdaforums.com/project-trebl...ment/rom-android-p-developer-preview-t3816659

The system file of this BTS is strange. After open has several partition folder. But i only need files inside of system folder. I extracted files inside of system folder, but i lost all link files of inside system folder. I tried anyway and the boot stop in bootanimation, probably because i lost all link files of inside of system folder.

So if possible provide backup file of system partition of android pie in TWRP I will be grateful.
[Essential Phone ROMs, Kernels, Recoveries, & Other] panossd:
Try this one.. https://xdaforums.com/showthread.php?t=2317790

I think u know that you have to run the commands on the path you have those drivers installed..
[Essential Phone ROMs, Kernels, Recoveries, & Other] easyrider77:
So if I'm reading this correctly, before you do the flash all batch file, you need to fastboot unlock the critical partition first?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Yep
[Essential Phone ROMs, Kernels, Recoveries, & Other] einfeyn496:
Long time lurker, first time poster...

My upgrade from O to P has been a mess.

Previously, I had updated from N to O and had been applying the OTAs using the same method (adb sideload from stock recovery, then flashing patched boot for root)

This time for unknown reasons (complacency I guess), I applied the sideload to both slots (switching the slot at the bootloader) before booting into the phone and verifying things were working.

Upon the first reboot, aside from an issue that I had previously encountered in other updates (non functional WiFi), and general unease with the new UX, things seemed to be working, so I patched the boot image and rebooted to root the device.

Upon reboot, I was rooted, but I still had no WiFi (in the past this had cleared up after a reboot or two) and the new UX seemed utterly unusable:

* swipe down to get the notification tray never showed any notifications

* there is only one swipe down level: bringing up some toggleable icons (WiFi, cellular data, bluetooth, etc), while in O and previous, there had been two swipe down levels, the second bringing more system settings into view

* no notifications on lock screen (or anywhere for that matter, other than the notification light)

* new gesture based home button non-functional, can't change between open applications, can't get to the home screen easily without multiple back button presses

* I am told that "developer options are not enabled for this user", and tapping the build number any number of times never brings any message of any kind

* I tried using several of the "magic codes" for accessing certain system information, and after entering them in the phone keypad, the digits disappear, but not popup ever appears with info

These were all enough to get me to decide that trying to go back to O was in my best interest (again, complicated because I had sideloaded the OTA to both slots...)

So I downloaded the July BTS zip and flashed it onto one of the partitions (no wipe option) and rebooted.

This resulted in the "Can't load Android system" message, whereupon I tried a few reboots, all with the same result.

I was still able to boot into the handicapped P partition, so I tried to reflash this partition with the P BTS zip, hoping it would resolve the missing WiFi and seemingly broken UX issues, but this was not the case.

Long story short, my upgrade to P is handicapped by WiFi and UX issues, while downgrade to O is seemingly not possible.

I would prefer to not go the nuclear option of just "reset and wipe and try again", so if there are any other things to try before then, I'd appreciate any insights.
[Essential Phone ROMs, Kernels, Recoveries, & Other] rignfool:
I have this feeling a couple of your apps didn't like the upgrade to P...

You can... If you like a challenge... Use the TWRP file manager and attempt to remove data from the apps causing force closes... But there is no guarantee it will work...

The safe course of action is to wipe all user accessable data...

You can try wiping data (not format) in TWRP and save your internal storage but it's always a crap shoot
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
I flashed and rooted to P with essentially no issues.

When I look at system information it says I only have July security updates.

How bad did I really screw this up?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
they sent a tweet, they screwed up the string to say august. your fine.
[Essential Phone ROMs, Kernels, Recoveries, & Other] persin:
Correct.
[Essential Phone ROMs, Kernels, Recoveries, & Other] RandomPooka:
That whole thing about the flip phone was very confusing and irrelevant, then. Why did you ask about it here, and what's your actual question concerning the Essential PH1?
[Essential Phone ROMs, Kernels, Recoveries, & Other] tvisforme:
My apologies if I've missed a post, but a few days ago someone was inquiring about using the Pie "novendor" flash on Oreo. There were a few responses about other ROMs, has anyone tried this with LOS 15.1 yet? Thanks in advance.
[Essential Phone ROMs, Kernels, Recoveries, & Other] schweigster:
Any idea what could be causing this? Everything flashes okay up until this point. I unlocked critical.

C:\XXX>fastboot flash system_a system

target reported max download size of 536870912 bytes

erasing 'system_a'...

OKAY [ 19.664s]

sending sparse 'system_a' 1/3 (514232 KB)...

OKAY [ 4.070s]

writing 'system_a' 1/3...

FAILED (remote: Chunk data size exceeds partition size)

finished. total time: 26.908s
[Essential Phone ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Try a previous BTS and see what happens, maybe a bad flash or your cord?
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
what version adb/fastboot?
[Essential Phone ROMs, Kernels, Recoveries, & Other] schweigster:
I used the BTS Android Pie from the OP. Unzipped it and tried the FlashAll from within there. I don't see the ADB/Fastboot program in there, but the FlashAll is obviously executing it from somewhere. Do you know where I can find that?

Edit:

Thanks! I copied the newest minimal ADB/Fastboot into the folder and I though that worked. It goes through the entire flashing process, but getting the following errors now:

C:\XXX>fastboot flash system_a system

target reported max download size of 536870912 bytes

erasing 'system_a'...

OKAY [ 31.142s]

sending sparse 'system_a' 1/3 (4194303 KB)...

FAILED ()

finished. total time: 31.454s

C:\XXX>fastboot flash system_b system

target reported max download size of 536870912 bytes

sending sparse 'system_b' 1/3 (4194303 KB)...

FAILED ()

finished. total time: 0.328s

C:\XXX>fastboot flash bluetooth_a bluetooth

target reported max download size of 536870912 bytes

sending 'bluetooth_a' (412 KB)...

OKAY [ 0.095s]

writing 'bluetooth_a'...

OKAY [ 0.014s]

finished. total time: 0.109s
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Open a command prompt, type in fastboot --version

That's space, minus, minus

Send the output
[Essential Phone ROMs, Kernels, Recoveries, & Other] schweigster:
C:\XXX>fastboot --version

fastboot version 28.0.0-4797878

The system flash is the only command that fails on both A and B.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 12paq:
It was a bit tough reading your whole post, but it looks like you're moving between Android versions without wiping. If you're changing between versions of Android on any device, and not using the official OTA because you're rooted, ALWAYS back up media and data then do a full wipe. Or if you have problems after using an official OTA Android version upgrade, back up your data (this should be done before any upgrade) and go back and do a full wipe BTS. For these BTS versions it's a necessity to wipe between Android versions. If you want to have zero problems on any BTS update, always do a full wipe. Do a -w in Fastboot or easier yet choose the "wipe" BTA versions in the OP.

Clean installs are always the best. Backing up your photos and data with a bit of knowhow via ADB it is easy. Besides, the command line is fun. Then use Titanium carefully for some user apps and Google restore most of your apps. ADB push your media back to your phone and bam, you're done.

It's off topic, so send me a pm if you need advice with different backups.