Database Info

Unable to install OTA updates since unlocking bootloader

Hello everyone!
Since I've unlocked and rooted my Pixel 2 it keeps failing the OTA update. I get the notification and the update is downloaded but when it's being installed, there is an undefined error. For all updates I had to sideload the OTA file via ADB. Honestly, I don't really know what could have caused this issue, as the first OTA update when I got the phone with all stock settings and roms it worked fine. Currently I can only instal the OTA.zip updates via ADB.
Things I did so far which could have caused the issue:
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Things I tried to resolve the issue:
Lock the bootloader again
Flash full stock rom with fastboot and official google script (failed "couldn't write bootloader.img" altough I had it unlocked)
Factory reset
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
Does anyone else have similar experiences?

ekalz said:
Things I did so far which could have caused the issue:[/B]
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Click to expand...
Click to collapse
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
ekalz said:
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
?
Click to expand...
Click to collapse
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.

SweetSofie said:
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.
Click to expand...
Click to collapse
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.

Can you root without patching or unlocking the bootloader so you don't fail the integrity check?

robocuff said:
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.
Click to expand...
Click to collapse
Thanks for the clarification! I would love to learn more about that stuff, I'm just not sure where to start learning.

I have the same problem with my pixel 2. I have tried full factory reset by flashing stock image. I have tried the recovery script some user posted in the p2 forum.
I contacted Google support about it and now i am waiting for 2nd line to contact me.
I will post here if/when i get a solution.

With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete

socal87 said:
With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete
Click to expand...
Click to collapse
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?

smorgar said:
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?
Click to expand...
Click to collapse
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread

socal87 said:
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread
Click to expand...
Click to collapse
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)

smorgar said:
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)
Click to expand...
Click to collapse
Did you try to sideload via ADB?

socal87 said:
Did you try to sideload via ADB?
Click to expand...
Click to collapse
No I am waiting to get it resolved by Google so that I can install OTA in the future.

smorgar said:
No I am waiting to get it resolved by Google so that I can install OTA in the future.
Click to expand...
Click to collapse
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.

socal87 said:
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.
Click to expand...
Click to collapse
I was trying to fix the problem permanently so that i dont have to sideload if i dont want to.
**** went to ****... I did factory reset as the Google support person told me. Tried installing OTA again but it did not work. So they left me waiting for second line support to contact me but its now been the whole weekend and no support.
After support told me to do reset the last time the phone began to freeze and crash apps randomly. So i tried to install full factory image via fastboot but that was the last time the phone booted up. Now its completely dead.
When i try to boot the phone nothing happens. If i hold power button for 20-30 sec i sometimes get a short vibration and a line of pixels flashing by on the screen then nothing more happens. Now im waiting for Google support for real. Pray for my dead pixel2
If anyone have some tips for me im willing to try. The phone does not seem to boot and the PC does not recognize it at all.

You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.

davidisflash said:
You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.
Click to expand...
Click to collapse
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
And so how did everything work out for you? Were they able to get you resolved, or are they just RMA'ing your phone?

No resolution. I sent it back to uk for replacement via seller.

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716

davidisflash said:
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716
Click to expand...
Click to collapse
I have done all the basic and advanced stuff. I had it dead for about a week to play around with. Used to work in a mobile repair shop so this isnt something new for me.

Relock Bootloader and return stock

For those of you that are rooted and would like to return back to stock with a relocked bootloader follow the steps.
This could also be useful for those of you stuck with a non bootable device. It will make your device eligible for warranty replacement again.
1. Flash stock boot.img (link) with the following command:
Code:
Fastboot Flash boot Stock_Boot.img
2.Re-lock bootloader with
Code:
Fastboot flashing lock
3. Enter recovery with Vol+ and USB plugged in. Then go down to wipe and Factory restore. Reboot and DONE
Hope this tip is useful to some.
See yah
Stock Boot.img Link
https://drive.google.com/open?id=1SqjkwVzNC3nAqDkNDMdEpqQH7viXDmb4

Is this the stock boot image for the regular non-carrier Razer Phone?

Kalveitt said:
Is this the stock boot image for the regular non-carrier Razer Phone?
Click to expand...
Click to collapse
This is for Non-Carrier.

Confirmed , you just made my day sir . i resurrect my device i flashed how you said with that command but i need to add -i 0x1532 , i got a message that is gonna flash it on b partition ,he said is done , after i restart it i got a message on phone (erasing) after i done the steps to factory reset it , i managed to get in the stock recovery, after 10 minutes i booted in the software all fine but not the wifi and flashlight ,
thank you once again for your hard work.
we keep in touch maybe i can do the wifi and flashlight
my device
Razer three uk

Anyone flash back to stock and have issues installing the latest update? Downloads but won't install?

So I relocked the bootloader before this file was released, by mistake my phone has twrp on both partitions, so when ever I boot it just says device corrupt and reboot I can however access qualcom diagnostics by pressing volume up + volume down at the same time, just wondering if phone can be restored through that interface

Btw as I'm finding out.. This doesn't reset to stock! It does relock your phone and you loose root, but any changes made to the system files while you were rooted sticks.. Ie hosts file changes. I'm back to "stock" and the adaway hosts file changes are still present.. I expect other changes are still there too and that's why I can't flash the update. guess I'm waiting for factory images for a full stock as well)

mikeandjaimie said:
Btw as I'm finding out.. This doesn't reset to stock! It does relock your phone and you loose root, but any changes made to the system files while you were rooted sticks.. Ie hosts file changes. I'm back to "stock" and the adaway hosts file changes are still present.. I expect other changes are still there too and that's why I can't flash the update. guess I'm waiting for factory images for a full stock as well)
Click to expand...
Click to collapse
Hopefully they get released at all at this point...sure looking less and less likely at this juncture with incremental push updates coming from Razer.

mikeandjaimie said:
Btw as I'm finding out.. This doesn't reset to stock! It does relock your phone and you loose root, but any changes made to the system files while you were rooted sticks.. Ie hosts file changes. I'm back to "stock" and the adaway hosts file changes are still present.. I expect other changes are still there too and that's why I can't flash the update. guess I'm waiting for factory images for a full stock as well)
Click to expand...
Click to collapse
Or if someone with a US/NA Razer Phone was nice enough to upload and post there TWRP backups before the the partitions were modified. We have a backup for the 3UK people, but one from US/NA Razer Phone, and one from the EU/Non Carrier Razer would help alot of people. I know people have them, just no one willing to share I guess Will probably be months if Razer ever actually posts the Factory Images.

There have been files for both uploaded and it was determined you couldn't use them for 3 phones already.. That's how alot of people got non working phones that just say corrupted now..
Gotta wait till factory images are released if you are on 3.

mikeandjaimie said:
Btw as I'm finding out.. This doesn't reset to stock! It does relock your phone and you loose root, but any changes made to the system files while you were rooted sticks.. Ie hosts file changes. I'm back to "stock" and the adaway hosts file changes are still present.. I expect other changes are still there too and that's why I can't flash the update. guess I'm waiting for factory images for a full stock as well)
Click to expand...
Click to collapse
I manage to find the location of the ota Update.zip and tried flashing it in the stock recovery but it also fails on stage 2.
As you pointed it out. The update is failing because it's still recognizing the system as modified.
I'll leave my link up to help those who are stuck on a boot loop with an unlocked bootloader this will at least make them eligible for warranty replacement so it's something... Follow the steps and then send it off to Razer for warranty replacement. It's a shame really to send out a phone that could easily be fixed with system images. Razer has really dropped the ball. Not having system images from day one really hurt the enthusiast development for this device. If your not able to send it out for warranty replacement then all you can really do is wait for Razer to release the images and I think they may not release them until they release Oreo.

I followed the step-by-step for putting twrp on mine. All seems to go well but it just keeps booting back into bootloader. If I turn it off and hold the vol+ while plugging in the USB I just get the Razer logo and nothing. When I finally gave up I flashed the stock boot in the OP. I'm up and running now but no BT and the latest update just fails. Relocked the BL and no system changes were made since TWRP never seems to have installed, if though I got a successful when complete. I hate to send this back, anyone know if they can reflash it remotely? I'll pay the fee, just need the phone working on WiFi again.

Does this method also work if am rooted, running a stock 8.1 rom and kernal?

Solved Flash Razer Phone To Stock and gain OTA capable!!
This is for the Razer Phone!!!! Fixed Warranty and OTA Update!! As if freshly purchased!!!!
I figured out that unless you use the Razer provided images from their support site your phone will not function properly as any other procedure will be extremely time consuming on a command prompt!!! Imagine individually flashing all components in their respective orders and flashing to both partitions is a requirement so use the provide images and the flashall.sh command included in the downloaded file.
The instructions for gaining the ability to flash the update via windows cmd.
follow the original instructions from the razer support site and the do this for the connection or what it's actually called (Environment variables) you will need to navigate on your pc to the system properties window the click on environment variables, two panes in the window at the lower pane look for the PATH line which is the pathe for the variable to point cmd to file system where your stock razer update is located. If you followed all steps : usb drivers, androis sdk 28.xx or higher extracted to C:/adb folder, navigated to system window then update driver connect phone in bootloader mode then open update driver browse computer let me pick from a list of drivers on my computer and install the android bootloader interface continue even though it says not recomended it works.
now open your razer downloaded factory file and double click flashall.sh and wait till finished then stop the reboot and boot to booloader and open windows cmd and type fastboot devices then type fastboot flashing lock and lock it up, Done sorry for the unorganized text but I'm sure nobody cares as long as it works right? !#fi enjoy!!!

Solved!!!!!!!!!!!!!
---------- Post added at 06:41 AM ---------- Previous post was at 06:20 AM ----------
Mike02z said:
I followed the step-by-step for putting twrp on mine. All seems to go well but it just keeps booting back into bootloader. If I turn it off and hold the vol+ while plugging in the USB I just get the Razer logo and nothing. When I finally gave up I flashed the stock boot in the OP. I'm up and running now but no BT and the latest update just fails. Relocked the BL and no system changes were made since TWRP never seems to have installed, if though I got a successful when complete. I hate to send this back, anyone know if they can reflash it remotely? I'll pay the fee, just need the phone working on WiFi again.
Click to expand...
Click to collapse
I solved this and if you need detailed instructions or help anyone can ask and I will help and yes it does return it to brand new fresh ota and warranty is returned, everything works as it should no bugs wifi works and data on sim.
As for twrp you should flash it to one slot not both as you may know system is on both slots you could have two slots with twrp and no system lol I did that before!
Your phone can be stock but not ota with twrp fyi.

mikedeboefis said:
Solved!!!!!!!!!!!!!
---------- Post added at 06:41 AM ---------- Previous post was at 06:20 AM ----------
I solved this and if you need detailed instructions or help anyone can ask and I will help and yes it does return it to brand new fresh ota and warranty is returned, everything works as it should no bugs wifi works and data on sim.
As for twrp you should flash it to one slot not both as you may know system is on both slots you could have two slots with twrp and no system lol I did that before!
Your phone can be stock but not ota with twrp fyi.
Click to expand...
Click to collapse
Thanks, but I returned my Razer within the first 30 days. Just not for me.

mikedeboefis said:
This is for the Razer Phone!!!! Fixed Warranty and OTA Update!! As if freshly purchased!!!!
I figured out that unless you use the Razer provided images from their support site your phone will not function properly as any other procedure will be extremely time consuming on a command prompt!!! Imagine individually flashing all components in their respective orders and flashing to both partitions is a requirement so use the provide images and the flashall.sh command included in the downloaded file.
The instructions for gaining the ability to flash the update via windows cmd.
follow the original instructions from the razer support site and the do this for the connection or what it's actually called (Environment variables) you will need to navigate on your pc to the system properties window the click on environment variables, two panes in the window at the lower pane look for the PATH line which is the pathe for the variable to point cmd to file system where your stock razer update is located. If you followed all steps : usb drivers, androis sdk 28.xx or higher extracted to C:/adb folder, navigated to system window then update driver connect phone in bootloader mode then open update driver browse computer let me pick from a list of drivers on my computer and install the android bootloader interface continue even though it says not recomended it works.
now open your razer downloaded factory file and double click flashall.sh and wait till finished then stop the reboot and boot to booloader and open windows cmd and type fastboot devices then type fastboot flashing lock and lock it up, Done sorry for the unorganized text but I'm sure nobody cares as long as it works right? !#fi enjoy!!!
Click to expand...
Click to collapse
Yeah.. I need help on this one. I tried it and fastboot doesn't allow me to flash_all script.
How do you even double click flashall.sh?

I know this is kind of old but I'm currently having the same problem as a person above. I've tried using the flash_all command but it will only stay at "waiting for device" and doing flash_all.sh doesn't work.

[GUIDE] How to Flash the Pixel Experience ROM on Nokia 7 Plus & Nokia 7

Hey guys i know the Pixel Experience rom has been released for a long time, more information about this Pixel Experience rom https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-pixel-experience-t3796011
but unfortunately we could not boot on nokia devices after we flashed this rom
Congratulations that bootloop problem has been solved right now, we are not tired to flash roms
DOWNLOAD TWRP https://drive.google.com/open?id=1-e7zNrXp_mi468h-Zu1X5gbwQtgE17I6
follow these steps
1: unlock your bootloader
thank for @hikari_calyx
2: erase data/factory reset
3: connect your computer with adb and flash any roms based on project preble ( AOSP or RR )(why this step ? my friend told me that this twrp has a bug which can't boot recovery on official firmware)
Code:
fastboot flash system system.img
4: flash this TWRP supported project treble with
Code:
fastboot flash boot_a TWRP.img
Code:
fastboot flash boot_b TWRP.img
5: boot into the twrp
6: extract rom image from PE zip and download Magisk-v16.6.zip, after that move them to Internal Storage
7: format data and flash the Pixel Experience image, choose "System image" Notice: Don't do a reboot before flash Magisk.zip
8: flash the magisk.zip
9: wipe all data and reboot. Done !
Notice: you may see Your Device Is Uncertified when you intend to login Google on this device
Just Do This
Download and install Device ID.apk
copy your Google Service Framework ID
fill your GSF ID on this web and Clink on REGISTER
reboot some times you will be able to use google apps
btw all project treble roms do not include Adaptive brightness and Ambient display
fix them at here https://forum.xda-developers.com/project-treble/trebleenabled-device-development/overlay-enable-night-light-adaptive-t3741965
I'm on this rom for three days and every things go fine unless fingerprint control bug (that means you can control your phone easily with fingerprint)
thanks for viewing, sorry for my english is poor but I've been improving it, I wrote this GUIDE without translate tool
thanks for every member which develop the project treble rom and TWRP and something else

some amazing screenshots

The image does not load

12345wxj said:
The image does not load
Click to expand...
Click to collapse
什么？哪一个镜像不加载？

1452686579 said:
什么？哪一个镜像不加载？
Click to expand...
Click to collapse
我這邊圖片一個都加載不出來

I have a Little problem at step one ._.
No way to unlock BL?

Why is the TWRP upload locked behind a google drive link that you need to request access for?

pitt93 said:
I have a Little problem at step one ._.
No way to unlock BL?
Click to expand...
Click to collapse
there is a way. but you need to pay.

donjamal said:
there is a way. but you need to pay.
Click to expand...
Click to collapse
Do they accept ETH/BTC?

shubham412302 said:
Do they accept ETH/BTC?
Click to expand...
Click to collapse
i have no idea. i don't think so, you need to ask them. it's 5 dollars, they for sure accept paypal

Has anyone flashed this yet? This thread was the straw that broke the camel's back for me and I unlocked my bootloader today.
Now just waiting to hear if anyone other than the op has been successful with this guide.

Doktaphex said:
Why is the TWRP upload locked behind a google drive link that you need to request access for?
Click to expand...
Click to collapse
I don't know why. ? Maybe it is shared right now

Doktaphex said:
Has anyone flashed this yet? This thread was the straw that broke the camel's back for me and I unlocked my bootloader today.
Now just waiting to hear if anyone other than the op has been successful with this guide.
Click to expand...
Click to collapse
Trust me dude ,it works fine I and my Chinese friends tested this guide on Nokia 7 plus and Nokia 7
And there is anotber guide to flash pixel experience rom, but that mode is complex and sometimes does not work

1452686579 said:
Trust me dude ,it works fine I and my Chinese friends tested this guide on Nokia 7 plus and Nokia 7
And there is anotber guide to flash pixel experience rom, but that mode is complex and sometimes does not work
Click to expand...
Click to collapse
It might take me a couple of days as I am quite busy at the moment.

Thank you for your development for the Nokia 7 plus. Really appreciated.

Well, I installed the system image, but now my SIM is not recognized.
I will go through setup and see if the SIM works afterwards?
EDIT: No IMEI on SIM slot 1, there is an IMEI on slot 2 but this slot also does not work.
And of course, I did not do a backup of my working system. (You'd think I would have learned by now, but NO )

Doktaphex said:
Well, I installed the system image, but now my SIM is not recognized.
I will go through setup and see if the SIM works afterwards?
EDIT: No IMEI on SIM slot 1, there is an IMEI on slot 2 but this slot also does not work.
And of course, I did not do a backup of my working system. (You'd think I would have learned by now, but NO )
Click to expand...
Click to collapse
LOL always do backup man, i learned the hard way Please update if you got sim 1 to work!

sublimeace said:
LOL always do backup man, i learned the hard way Please update if you got sim 1 to work!
Click to expand...
Click to collapse
I got my entire system back up and running using the July patched boot image flashed into boot a and b and then sideloaded rollback zip etc, etc....
In general I have found that when I get my self into these situations, if I actually have a back up it ends up failing anyway.
It's always more fun walking the tightrope.
Anyway, both SIM slots are fine on stock ROM rooted with magisk, xposed etc.
I won't be flashing any treble images until I hear more success stories in that respect, I feel that our twrp still has some kinks that need to be ironed out.

9: wipe all data and reboot. Done ! you mean factory reset?

donjamal said:
there is a way. but you need to pay.
Click to expand...
Click to collapse
so, no way

September Update is out!!

https://www.essential.com/developer/current-builds
Also, just received it on my phone this very moment.

Downloading now! Came to post this exact thing.

UPDATE
Screen shot for those interested

changelog?

mookiexl said:
changelog?
Click to expand...
Click to collapse
Check the screenshot one post right before your!

Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works

ziddey said:
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
Click to expand...
Click to collapse
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?

If I try to unroot by restoring images it says "Stock backup does not exist!"

sruel3216 said:
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
Click to expand...
Click to collapse
I believe you'd fail the OTA if you have an altered boot, but you can try.
oracleoftruth said:
If I try to unroot by restoring images it says "Stock backup does not exist!"
Click to expand...
Click to collapse
I dumped the old boot before rebooting just in case: https://drive.google.com/file/d/11MjB4kTOHuxbUyHe_kIwZ1d0wqp6-Nmf/view?usp=sharing
You can flash it to your boot slot while rooted, take the OTA, and then install magisk to the other slot before rebooting.
Drop a shell.
Determine current boot slot: getprop |grep boot.slot
Flash the boot: dd if=/path/to/boot_b.img of=/dev/block/by-name/boot_b (change to boot_a if that's your slot)
Of course, don't reboot since you'll lose root. Instead, you should now be able to take the OTA, and then use magisk to patch the other slot before rebooting.
Magisk should now have a backup for next time, so you can uninstall/ota/install in the future.

Nice...4 days in, and patched with the security update already.

ziddey said:
I believe you'd fail the OTA if you have an altered boot, but you can try.
Click to expand...
Click to collapse
Was curious cuz I was able to update the OTA on my pixel when rooted with custom kernel.

For some reason after I ran the magisk uninstaller and made sure to flash the stock boot image I still ran into problems updating via OTA and after sideloading the OTA for the Sept Update with success I found that TWRP would seem to freeze whenever it got to the main screen for some reason. I was able to use adb commands to reboot to bootloader and flash the stock kernel for the update and was able to boot normally. Just wondering if anybody else is having issues with TWRP freezing after installing the security update and yes I did remove fingerprint and lock screen security before booting into TWRP so I know its not something from that causing it to freeze.

Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........

Just installed patch. Scrolling feels so much better, especially when scrolling slow.

gorm said:
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Click to expand...
Click to collapse
That's exactly what happened to me.. a user on /r/essential said they had the same issue; frustrating!
I'm going to be going back to 8.1 via fastboot, and then flashing 9.0 august, THEN fastbooting september, and if that doesn't work, I'm going to fastboot 9.0 august and then try OTA to
get my screen back.
Really weird stuff.
EDIT: Here's a supposed fix for those with the touchscreen issue - https://www.reddit.com/r/essential/comments/9d0lg3/for_anyone_having_trouble_with_touchscreen_not/
I don't know if we're allowed to link to reddit or not, but I'm doing that fix now.
Thanks!

my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back

jon_ybanez said:
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
Click to expand...
Click to collapse
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!

beard805 said:
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
Click to expand...
Click to collapse
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance

jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Sadly, I don't know much about the SIM side of the issue
Hope someone with more knowledge can chime in!

jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Are you rooted? Here are the unlocked modemst files: https://drive.google.com/file/d/1LQC-2QOC-PWX7vza-82tpwFrnUjaGZVq/view?usp=sharing
You can try to dd them:
Code:
dd if=/path/to/modemst1.img of=/dev/block/by-name/modemst1
dd if=/path/to/modemst2.img of=/dev/block/by-name/modemst2
Would be a good idea to backup your current images
from https://forum.xda-developers.com/essential-phone/how-to/discussion-brainstorm-sim-unlock-t3724135

Anyway to return to stock? or Install TWRP/ Rom

I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP

Passportpowell said:
I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP
Click to expand...
Click to collapse
do you have usb debugging enabled, are your sdk tools up to date?

Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.

Passportpowell said:
Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.
Click to expand...
Click to collapse
then you need to update your htc drivers.

here you go.

Aldo101t said:
do you have usb debugging enabled, are your sdk tools up to date?
Click to expand...
Click to collapse
Aldo101t said:
here you go.
Click to expand...
Click to collapse
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
I've done a format data on twrp and it won't ask for a password anymore but I still can't sideload anything. Going to try to copy the rom to the storage and see what happens there
I've only could see a twrp folder on my phone when I connect it to my pc while still in twrp so I copied a rom there and went into install zip, data, media, twrp. My file was there.
Installing rom now I'll update if it worked.

Passportpowell said:
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
View attachment 5087597
View attachment 5087599
Click to expand...
Click to collapse
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.

here is magisk

if you are on pie that viper rom is based on oreo. just so you know.

Aldo101t said:
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.
Click to expand...
Click to collapse
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Aldo101t said:
if you are on pie that viper rom is based on oreo. just so you know.
Click to expand...
Click to collapse
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you

Passportpowell said:
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you
Click to expand...
Click to collapse
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34

Aldo101t said:
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34
Click to expand...
Click to collapse
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?

Passportpowell said:
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?
Click to expand...
Click to collapse
3.37.617.1 is for the us-unlocked

Hello to everyone...I just got from my older brother his HTC U11 4gb 64gb phone. And it has locked bootloader and does not have root. So please what should I have to do so I can install custom rom. Stock rom is old full of bloatrware. There is so many information that I am confused.
Thx so much !