yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] ptzink:
Well, I am unlocked and was rooted, but obviously not any more since I flashed the stock image. I flashed the fastboot img via stock recovery. Does this have something to do with the fact that I can't write to critical partitions? I saw a thread on Reddit about that. If that is the issue, is there anyway to unlock the critical partitions without wiping? If not, then I will just have to bite the bullet and go that route.

---------- Post added at 08:05 PM ---------- Previous post was at 07:39 PM ----------

I got it! I had to flash the October OTA via stock recovery (sideload). Then I went and patched the boot image via Magisk to regain root. Now I am back in business. Thank you!
[Essential Phone ROMs, Kernels, Recoveries, & Other] yankeefan:
Fixed it..I used factory recovery and pushed OTA again and it fixed bootloader. Must have been corruption from first update
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
You cannot flash fastboot images without unlocking critical. And unlocking it erases all your data. Should have unlocked both back to back before rooting. This is a one time operation.
[Essential Phone ROMs, Kernels, Recoveries, & Other] ptzink:
Well, I have been flashing with fastboot without unlocked critical pretty much every month for several months now. Seems to have been working fine. Today I did notice there are certain items that are not getting flashed because critical is not unlocked. How does the OTA update these items without critical unlock?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
Critical unlock is needed if you want to go back to stock or there is a bootloader update as in major Android version upgrade, i.e. going from 8.0 to 8.1 or 8.1 to 9.0. So it is recommended to unlock critical when unlocking normal bootloader so you don't have to wipe your data at a later time when unlocking it. OTA can work around this somehow.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 041987:
That's means if I want B slot go to 9.0 and A is current(don't want to touch it), flash particular build stock boot to B slot and go to bootloader->recovery->sideload OTA.zip and done?
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
Don't worry about the slot. OTA always gets installed into the opposite slot. You should not pick which one it is. If your A slot is active and you flash stock boot.img to it, OTA will update the B slot. What do you have against the A slot that you want B to have Pie in it?)
[Essential Phone ROMs, Kernels, Recoveries, & Other] 041987:
Could I flash 9.0(with mod of .bat) to b slot by fastboot? It seems no touch A slot and will have dual android(8.1 & 9.0):confused:
[Essential Phone ROMs, Kernels, Recoveries, & Other] sash11:
You could, but you will not be able to boot into 8.1. Bootloader versions are different between 8.1 and 9.0.

Here is another reason why dual booting is not going to work...

https://xdaforums.com/essential-pho...g-essential-ph-1-magisk-t3701976/post77631539
[Essential Phone ROMs, Kernels, Recoveries, & Other] 041987:
I haven't try 9.0, looks good and want to try. 8.1 SOH is not good, compare with 7.1.1.

And 9.0 don't have xposed, some modules are useful for me.

Also, I am lazy to flash the twrp, magisk and xpsed after flashing stock boot to OTA non-active slot.:p

Oh. looks bad:crying:

Maybe keep using 8.1

Many thanks:fingers-crossed::fingers-crossed:
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
PH1-oct-4.4.157-ex309-twrp-mgk.img

Here the same all-in-one but with kernel ElementalX 3.09.

https://www.androidfilehost.com/?fid=1322778262904019506
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Nice
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Thank you for this! :good:
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
Hi, how can I delete the red message start screen? my phone and with the bootloader unlocked and partition critical unlocked, with firmware last stock of October.

I attach screen
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
image not showing but i assume it's the screen that says to hit power to continue or similar? If so, flash this in twrp then flash your stock boot.img then reroot it w/ magisk..

https://www.dropbox.com/s/rnxqi5drlfi0xqs/boot.fix.red.img?dl=0

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I do not have the twrp installed, and necessary?
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
This probably isn't the place for this but if you are getting what I described you had twrp and rooted at some point no? If so you have to flash twrp, flash this img i linked, flash stock boot.img then modify that w/ magisk. BUt fix your pic (it's way too small) so we can see what you have going on, i'm speculating on what your problem is.

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
Here's the picture
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
Yeah so at some point you had TWRP installed to root correct? Or at least to flash something? All you need to do is what I said before.

Flash twrp and boot to twrp.

Flash the img I linked you to

Flash stock boot.img for your ROM

Root that boot.img if you want w/ magisk.

profit

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
if I do not want to root, I stop at point 3)
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
Correct. you can skip 4 and go right to 5.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I do not understand point 5) which means?
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
Sorry step 5 is just an american way of enjoying the results of your work. It's slang and isn't really a step.

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
OK thanks,

the boot.fix.red img file

and the boot.img of my rom, do I have to install them from the twrp?

slot A = android

or

slot B = TWRP

can you give me a simple guide to install the twrp?
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
A guide to install TWRP can be found here - https://xdaforums.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976

I would suggest to read this as well - https://mata.readthedocs.io/en/latest/

It has some nice info on how to manipulate the partitions.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
ok twrp installed

now how do I install the files;

boot.fix.red.img

boot.img

---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------

ok twrp installed

now how do I install the files;

boot.fix.red.img

boot.img
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Those files can be flashed with TWRP.

But I do not understand why you don't flash an 'all-in-one' image available in this thread

In the OP you may find the October BTS. Included in that zip is a patched magisk and twrp stock boot.img.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
where do I find the file I imagine?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
https://androidfilehost.com/?fid=1322778262904018340
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
thank you,

does the file launch it from twrp?
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
No, you need to flash it via Fastboot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
But this patch deletes the window as from the attached image
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
Ma questa patch cancella la finestra come dall'immagine allegata
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
In TWRP you may flash it as 'img'.

Then select the radio button 'boot'.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
so no fastboot as the user says [MENTION=3301438]geko95gek[/MENTION]
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Both methods will be ok.

You already have TWRP working so I think that's the easy way.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
You can flash it via TWRP too I'd you got it working.

Thanks.

Completely mind blanked that haha, I almost never flash image files via TWRP lol
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
so if l had not installed the twrp i can do it from fastboot, ok ? could you write me the command to write by fastboot ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
fastboot flash boot <filename>

You need to be sure your PH-1 has the latest October version.

In the first post (the OP) you'll find a link to so called Back-to-stock images in a zip-file. Extract the latest version on your PC. That's for plan B. When your PH-1 is messed up, you're able to go back to a working stock system.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
Ok thanks, then I have it via twrp, Simple. I'il let you know how it goes

---------- Post added at 06:28 PM ---------- Previous post was at 05:43 PM ----------

I installed the twrp as a guide but does not work the touch, as I do
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
You are not using the right version of TWRP if touch is not working.

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
and the correct one, can you tell me where to get it?

twrp-3.2.3-0-mata rename in twrp-mata
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
First tell me the version of twrp you have downloaded? 3.2.3 is what you need, here is my personal version.

https://www.dropbox.com/s/qabdko3i1vp6rag/twrp-3.2.3-0-mata.img?dl=0
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
twrp-3.2.3-0-mata rename in twrp-mata

how can I repeat the installation now?

---------- Post added at 07:17 PM ---------- Previous post was at 06:56 PM ----------

I redo the operation with your version and the same problem, after the twrp flash, restart in recovery mode, the twrp starts but the touch does not work
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
finally I was able to install and operate the touch on the twrp.

now I have to flash the file from the twrp:

oct_patched_twrp_magisk_stock.img

he asks me where

boot

immagine system

immagine vendor

what am I saying ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Because it's a boot image you need to select 'boot'
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I don't do damage, right? I'm just deleting the red alert screen, right? Sorry if I insist but I had a lot of problems with the phone, I would not have Others
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
Just did, the screen and remained and I installed Magisk. It doesn't seem to Work

It all works, but the red windows is left, useless work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
All have a red <!> after unlocking the bootloader. But the bootprocess doesn't stop.

When you still have to press start button when rebooting I don't know what's behind that.

As I said in post #1027 you could use the Back-to-stock method described in the OP. I've no ideas left.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
So if I want to return stock and delete all the work done (twrp, root magisk etc ..) I take all the files of the decompressed folder PPR1.181005.034_BACK_TO_STOCK I put them in the platform-tools folder, and then send the phone in fastboot mode and click on FLASHLLWIPE file, right?

or is it enough just to launch the FLASHALLWIPE file directly from within its folder, again from fastboot mode?
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
I would start with without wiping. With wipe you need to setup the PH-1 again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
back to stock wont get rid of the red ! screen. You still need to flash the boot fix red in order to get rid of it. What problem are you having?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
Dunque devo fare il flash da twrp del file boot.fix.red.img, per eliminare la schermata rossa
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
what?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
To remove the red alert screen, what do i do
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
You need working fastboot

1. Download this http://gg.gg/ai7m1 this is the boot.fix.red.img

2. boot to bootloader, enter this command, fastboot getvar all this will tell you what slot is active

3. put the boot.fix.red.img in the directory where your fastboot resides

4. run this command fastboot flash boot_a boot.fix.red.img or fastboot flash boot_b boot.fix.red.img depending on what your active slot is

5. reboot the phone, it will bootloop (this is fine) let it bootloop until you get a orange screen telling you your bootloader is unlocked.

6. Force the phone back into bootloader, and flash whatever boot.img you need to boot your stock system.

https://mata.readthedocs.io/en/latest/

Read that ^^^^^^^^^^^^^^^
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
Ok the Stitches 1. 2. 3. 4. 5.

You can better explain the point 6.

Thank you
[Essential Phone ROMs, Kernels, Recoveries, & Other] gorm:
You need the boot.img from whatever Rom/Firmware u have installed.

Boot back into bootloader ( power button volume down ) flash appropriate boot.img . Reboot device
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
hi, I need to return stock, which is the most appropriate guide?

Now I'm with TWRP + magisk + ROM STOCK (patch the october)+ unlock Bootloader + unlock partition critical

I ran the first post guide, but it does not work

fastboot devices = ok

fastboot getvar current-slot = ok A

fastboot -w = ok

then start the flashallwipe

ok boot_a

ok boot_b

system_ a failed

and so for everything

now my phone goes only in fastboot mode, if someone can give me a hand, I will be grateful
[Essential Phone ROMs, Kernels, Recoveries, & Other] LoveScarGuitar:
I've had to try mine a few times to get it to work. Not sure if there's a less complicated method, but I just kept rebooting, unplugging, replugging, doing all of the commands again, and seeing if it works until it finally goes through.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I'm always going on, but nothing even changing usb, I do not know what to do anymore.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LoveScarGuitar:
Have you tried flashing it to the other partition instead?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
no always on slot A

also done on slot B, same problem

nothing I did a thousand tests is wrong, just fastboot mode

never had so many problems with a phone
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
I've seen many questions and answers of [MENTION=943156]nibera[/MENTION] and I think he has some problems with the language.

I've suggested to go back to stock of October to make sure both slots are synchronized.

After that rooting and flashing the red-fix-boot,img and the all-in-one boot image should solve the problem.

But I'm still unsure if his PH-1 has unlocked the bootloader and critical partition as well.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
unfortunately I use google translator,

unlock bootloader

unlock critical partition

I do not know what to do.

fastboot flashing unlock_critical

failed : (remote device already: unlocked !)
[Essential Phone ROMs, Kernels, Recoveries, & Other] chris_stan:
Hello M. [MENTION=5447216]aer0zer0[/MENTION]

When opening the script I see that you do not specify boot.img

The files have no extension but are the right size (stockboot.img)

when you are under windows

for example, indicate

fastboot flash boot boot.img

it's a question, not a criticism

the other files in the zip are for the root procedure, if I understand correctly

thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
Exactly, the reason I didn't throw .img at the end is it's easier to sort when I make the following months BTS. Anything with .img is used after running the BTS.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
We helped him get through fixing the red verity. He is now on a BTS mission. We need to figure out what adb/fastboot he has. [MENTION=943156]nibera[/MENTION] what OS are you using on your PC, what version of adb/fastboot do you have.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
thank you

adb/fastboot = platform-tools_r28.0.1-windows

PC Windows 10 64 bit

Door Usb 3.0

Cable usb - type c 3.0

after many attempts I managed to restart the phone, but even during the flash of the firmware patch October some files to Failed data, I could not see which, however now turns on and start the system, the only news and that e the red window returned.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
You need a PC with working ADB/Fastboot environment.

A working USB connection and a different usb-cable, because the original ph1-cable does not work.

The PH-1 needs to be unlocked twice with Fastboot:

fastboot flashing unlock

fastboot flashing unlock_critical

and on the PH-1 USB debugging must be active.

When that's all ok the commands:

ADB devices

ADB reboot bootloader

are working. You must see on the ph-6 the screen of the so called fastboot mode.

When all stuff I wrote above is done well. You must check with the PC if the Fastboot mode is really working.

The command Fastboot devices may not fail.

When it fails you need to update the usb drivers on the PC.

Now you are ready to follow one or more of the suggestions of the posters that tried to help.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
the adb commands do not go

---------- Post added at 01:21 PM ---------- Previous post was at 01:05 PM ----------

now I tried with phone switched on regularly. here is the result:

adb devices = ok to recognize the phone

adb reboot bootloader = has rebooted the phone in fastboot mode on a regular basis

so it seems that the adb and fastboot commands work !!!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
You still need to check the command 'fastboot devices' to make sure the drivers on the PC works correctly.

Because in bootloader mode Windows uses another driver.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
in fact I wanted to create the boot.img file from adb

this is the result:
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
You must use fastboot !
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
can you write me the command from fastboot to create the boot.img file?

and anyway I have problems with the drivers on adb.

can you attach a screen of your pc in device management to see which drivers see your essential in both adb and fastboot?

because all my problems are there.
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
You don't need to create anything.

You need to flash with fastboot the file boot.fix.red.img. You got it from TT_vert.

And directly after that the stock boot.img that's in the Back-to-stock zip you downloaded already.

(fastboot flash boot <filename>)
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I now or on installed the firmware PH1-Images-PPR1.181005.034 no firmware PPR1.181005.034_BACK_TO_STOCK

so and the same?
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
He does need stock boot.img which I believe he doesn't have so he wants to extract it form his existing ROM. I'm trying to find the info on how to do that but if you know what ROM you are using get the img here.

Extracting from existing ROM:

If your custom ROM awas on slot A:

adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boota.img

If your custom ROM was on B:

Code:

adb shell dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/bootb.img

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
Just pull the boot.img from your existing rom via adb commands if you aren't entirely sure which of those in that google drive link is yours.

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
in adb I tried

with phone on I have this situation:

adb devices = ok

adb reboot fastboot = ok

now in fastboot if I write;

adb shell dd if = / dev / block / bootdevice / by-name / boot_a of = / sdcard / boot.img

it does not work !!!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
That is not done in fastboot. If you cannot boot, boot to twrp recovery image and use usb adb.

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I do not have the twrp, I have the stock recovery
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
You will have to flash twrp or boot your device into it's OS to use ADB.

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I do not want to install the twrp because I want to return stock, so there is no other way to create the current boot.img file?
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
boot your phone to the OS now and use adb to extract image. If you know what rom you are going to go to you already have it downloaded, pull boot.img out of it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
it does not work
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
but if I take the boot.img file that I find in the firmware package I installed PH1-Images-PPR1.181005.034

it's the same ?
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
What do you get if you type adb shell?

what about typing ls after adb shell?

do you know if your os is on slot A or B?

To check:

adb shell getprop ro.boot.slot_suffix

Dave

---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------

You are going back to stock right? if so you'll need the boot.img from the firmware (ROM) you are installing.

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
I'm in A
[Essential Phone ROMs, Kernels, Recoveries, & Other] TT_Vert:
ok well probably this is probably because you are not rooted. YOu may not have permissions to that area. I'd start a new thread instead of us cluttering this up any further.

Dave
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
no root

no twrp

they are stock

unlock bootloader

unlock critical_partition

firmware PH1-Images-PPR1.181005.034 official site

this is my position
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
So what is it that you're trying to achieve?

You have the right firmware, you're not rooted and you don't have a custom recovery.

I would suggest you post in this thread - https://xdaforums.com/essential-phone/help/help-thread-question-noob-friendly-t3659718

Remember to describe your system fully, and also what you want to do with your phone.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Nickdroid86:
If I have reverted completely back to stock, I still shouldn't relock my bootloader?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nibera:
OK thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] NLBeev:
Quoting [MENTION=5447216]aer0zer0[/MENTION].

I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
[Essential Phone ROMs, Kernels, Recoveries, & Other] aer0zer0:
If your going to sell the phone, or just want to, sure I guess. But just be aware that you want to make sure EVERYTHING is working, booting, everything before issuing those commands. Once you lock the bootloader, your SOL if the phone doesn't boot in any way.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Yep, honestly there's absolutely no reason to relock your bootloader once it's unlocked.

You're doing more harm than good.
[Essential Phone ROMs, Kernels, Recoveries, & Other] avd:
You erase everything anytime you issue a lock or unlock commNd
[Essential Phone ROMs, Kernels, Recoveries, & Other] Thebear j koss:
8 pages... 8 freaking pages. Fml. Only development being done here is the developing headache I am getting from reading the past 8 pages....

Sent from my PH-1 using Thebear Blue XDA Labs