FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!
electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Updating now!!!
dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.
The fact that it was not released to beta first makes me think it may just be an official release of the beta
crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!
epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Wonder if Essential pushed it since Pixel is now offering pre release of Android P?
My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice
GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.
Can anyone tell me if stable has multitouch issues that were on beta?
Rooted 7.1.1 took the update just fine, lost root and twrp
Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.
Related
Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.
Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.
beelow319 said:
Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.
Click to expand...
Click to collapse
Can you offer up the steps to do that? I know how to do a factory reset, but that will wipe the data. Thanks.
Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do
newtoncd said:
Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.
Click to expand...
Click to collapse
Are you, or have you been rooted in the past?
rmjones2006 said:
Are you, or have you been rooted in the past?
Click to expand...
Click to collapse
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.
beelow319 said:
Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do
Click to expand...
Click to collapse
May I just say, thank you very much.
That worked ... I am now running v4.4.4 .... and you are right, that was very easy.
Too bad I had already wiped my phone twice ... ugh ... again, thank you!
newtoncd said:
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.
Click to expand...
Click to collapse
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.
distortedloop said:
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.
Click to expand...
Click to collapse
I had replaced the radios with stock before trying to update to v4.4.4 .... when that didn't work, I thought the reset to factory specs would take care of that; no joy.
In the end, I love the HouseofMoto program .... that was really easy.
My phone just got updated. Not sure what changed. I couldn't find any info online.
View attachment 3998431
Probably the security patch.
Taken from my 920
It brings us up to 10i where T-Mobile is currently at.
Ant way to block updates on a non rooted phone?
Could we possibly finally get a stock KDZ from this?
I froze that
jetracer said:
Ant way to block updates on a non rooted phone?
Click to expand...
Click to collapse
I installed FOTAKill.apk and have not been prompted about any update.
No root needed, just install like any other apk. I've been using it since I had my Epic 4G.....LoL...... I hate the pushy notices.
Edit: It failed this time.....I just got the update prompt
monke30butt said:
I installed FOTAKill.apk and have not been prompted about any update.
No root needed, just install like any other apk. I've been using it since I had my Epic 4G.....LoL...... I hate the pushy notices.
Click to expand...
Click to collapse
Can you link the apk. Can only seem to find old ones
haris163 said:
My phone just got updated. Not sure what changed. I couldn't find any info online.
View attachment 3998431
Click to expand...
Click to collapse
I got the notification for that but I haven't updated yet.
Did you willingly install the update or did it happen automatically? Can anyone confirm?
I need to know if I should be freaking out or not. I haven't rooted yet but now I think I'm running out of time and need to get it over with.
I have "Automatic system updates" turned off in Developer options. Am I safe?
ubergeek77 said:
I got the notification for that but I haven't updated yet.
Did you willingly install the update or did it happen automatically? Can anyone confirm?
I need to know if I should be freaking out or not. I haven't rooted yet but now I think I'm running out of time and need to get it over with.
I have "Automatic system updates" turned off in Developer options. Am I safe?
Click to expand...
Click to collapse
I willingly let it install.
AT&T Forced this update on my phone
And am currently bootlooping into TWRP. ****. Anyone have any ideas?
---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------
haris163 said:
I willingly let it install.
Click to expand...
Click to collapse
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
mmarsie said:
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
Click to expand...
Click to collapse
Sorry I don't know about that. My phone is pure stock.
mmarsie said:
And am currently bootlooping into TWRP. ****. Anyone have any ideas?
---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------
I'm currently on the NotSoStock modded rom with ATT variant, everytime the update goes to install it gets to the point where the phone goes to reboot and then boots into TWRP. Any ideas on what I should do?
Click to expand...
Click to collapse
You should stop trying to install it
I've run into this before on other devices. Basically, the phone assumes you have the stock recovery installed, and attempts to run a command very specific to that recovery. Since you have TWRP, such a command is not compatible, and therefore nothing happens. If you were to look at the terminal output in TWRP, you should see something indicating that flashing the update failed.
But as a general rule of thumb, you should stay away from OTA updates when rooted. They are generally not compatible with or safe for rooted devices and custom ROMs. Even if the update were successful, it would unroot your device and patch the update that allowed you to obtain root, and you'd be stuck without root indefinitely.
So in your case, you need to freeze/uninstall "System Update" app (or whatever it's called) and wait for the maintainer of your ROM to include the changes in the next ROM update.
If you're still bootlooping, in TWRP's file manager, try looking for the update and deleting it. I think it may be in the /cache folder, but please do some research before you go deleting stuff at random. You may also try connecting it to adb, restarting in root mode, and running "adb uninstall com.lge.lgdmsclient," or "adb hide com.lge.lgdmsclient." Basically, you need to find a method of preventing the update from initiating automatically upon boot.
ubergeek77 said:
You should stop trying to install it
I've run into this before on other devices. Basically, the phone assumes you have the stock recovery installed, and attempts to run a command very specific to that recovery. Since you have TWRP, such a command is not compatible, and therefore nothing happens. If you were to look at the terminal output in TWRP, you should see something indicating that flashing the update failed.
But as a general rule of thumb, you should stay away from OTA updates when rooted. They are generally not compatible with or safe for rooted devices and custom ROMs. Even if the update were successful, it would unroot your device and patch the update that allowed you to obtain root, and you'd be stuck without root indefinitely.
So in your case, you need to freeze/uninstall "System Update" app (or whatever it's called) and wait for the maintainer of your ROM to include the changes in the next ROM update.
If you're still bootlooping, in TWRP's file manager, try looking for the update and deleting it. I think it may be in the /cache folder, but please do some research before you go deleting stuff at random. You may also try connecting it to adb, restarting in root mode, and running "adb uninstall com.lge.lgdmsclient," or "adb hide com.lge.lgdmsclient." Basically, you need to find a method of preventing the update from initiating automatically upon boot.
Click to expand...
Click to collapse
I initally declined the update when the notification came up, it is currently being forced down my throat lol. thank you for the info, I really hope i can get around this incredibly annoying issue.
mmarsie said:
I initally declined the update when the notification came up, it is currently being forced down my throat lol. thank you for the info, I really hope i can get around this incredibly annoying issue.
Click to expand...
Click to collapse
Did you have Developer Options enabled, and did you have "Automatic software updates" set to OFF in developer options?
I'm not rooted yet. I'm seriously scared right now that I'm going to auto update on next reboot. I'm doing everything I can to backup all my stuff and somehow safely do DirtySanta without being at risk of updating.
ubergeek77 said:
Did you have Developer Options enabled, and did you have "Automatic software updates" set to OFF in developer options?
I'm seriously scared right now that I'm going to auto update on next reboot. I'm doing everything I can to backup all my stuff and somehow safely do DirtySanta without being at risk of updating.
Click to expand...
Click to collapse
yes and yes to both your questions. this was a 100% forced update even though dev options and auto update was set to off
mmarsie said:
yes and yes to both your questions. this was a 100% forced update even though dev options and auto update was set to off
Click to expand...
Click to collapse
This is terrible.
ubergeek77 said:
This is terrible.
Click to expand...
Click to collapse
yeah I'm lived right now, currently with out a cellphone untill i test some of the above options another user posted. Here's hoping
Does anyone know whether a phone with this update can still use the dirtysanta exploit to root, or is that also broken by the security update?
InoHello everyone.
It has been a long time since my last post....
I bought my HTC U11 128GB/6GB last August and I find it awesome. Since the announcement of the Oreo update being rolled out, I became impatient to try it. I checked and checked for updates... but nothing. Right now it's running Android 7.1.1, SW version 1.27.400.21, with the October 2017 security patch.
How can I find if there are other updates that I didn't receive? How can I find my model number? How can I force the updates?
Info: My phone is already unlocked (it's the first thing that I did after receiving it).
Edit: with Simple CID Getter I found out that my CID is HTC__060. Is it the DUGL/India model? If yes then I guess that the Oreo update didn't arrive yet?
Thank you in advance to anyone that can help me.
Samribi said:
InoHello everyone.
It has been a long time since my last post....
I bought my HTC U11 128GB/6GB last August and I find it awesome. Since the announcement of the Oreo update being rolled out, I became impatient to try it. I checked and checked for updates... but nothing. Right now it's running Android 7.1.1, SW version 1.27.400.21, with the October 2017 security patch.
How can I find if there are other updates that I didn't receive? How can I find my model number? How can I force the updates?
Info: My phone is already unlocked (it's the first thing that I did after receiving it).
Edit: with Simple CID Getter I found out that my CID is HTC__060. Is it the DUGL/India model? If yes then I guess that the Oreo update didn't arrive yet?
Thank you in advance to anyone that can help me.
Click to expand...
Click to collapse
There is unofficial update: https://forum.xda-developers.com/u1...u-firmware-t3612048/post74674442#post74674442 and https://forum.xda-developers.com/u1...u-firmware-t3612048/post75213806#post75213806 You can manually install OTA.
4squer said:
There is unofficial update: https://forum.xda-developers.com/u1...u-firmware-t3612048/post74674442#post74674442 and https://forum.xda-developers.com/u1...u-firmware-t3612048/post75213806#post75213806 You can manually install OTA.
Click to expand...
Click to collapse
Thank you very much. I will look at it.
Samribi said:
Thank you very much. I will look at it.
Click to expand...
Click to collapse
Please tell if it worked
dany xe said:
Please tell if it worked
Click to expand...
Click to collapse
I just did a backup. Downloading the first files to upgrade from 1.27.400.21 to 2.31.400.6 now. Do I have to flash all the files? OTA, recovery, boot and firmware? Or only the OTA zip is enough?
Edit:
I tried to install the OTA Zip with TWRP and it gives me an error message. I think I will wait until the official OTA arrives (hoping it doesn't take too long).
The wwe version has only just been updated so you'll probably get the update in a month or so once the carrier is happy with the release. My advice is to wait. Do not root and s-off for it.
Samribi said:
I just did a backup. Downloading the first files to upgrade from 1.27.400.21 to 2.31.400.6 now. Do I have to flash all the files? OTA, recovery, boot and firmware? Or only the OTA zip is enough?
Edit:
I tried to install the OTA Zip with TWRP and it gives me an error message. I think I will wait until the official OTA arrives (hoping it doesn't take too long).
Click to expand...
Click to collapse
It's OTA zip, you dont have to s-off or root, here you have guide how to install OTA: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
4squer said:
It's OTA zip, you dont have to s-off or root, here you have guide how to install OTA: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
Click to expand...
Click to collapse
I'm looking to the post, and (being S-OFF already) it says that I have to flash a Combined Full Wipe firmware and then the OTA. Does it mean that I will lose all my data?
You can try to connect through the VPN that allows to select server located in India.
Had exactly same problem as OP.
Solution with VPN worked for me. And phone updated to Software version 2.42.400.3
EugeniusD80 said:
You can try to connect through the VPN that allows to select server located in India.
Had exactly same problem as OP.
Solution with VPN worked for me. And phone updated to Software version 2.42.400.3
Click to expand...
Click to collapse
What kind of VPN did you use? What software?
Samribi said:
What kind of VPN did you use? What software?
Click to expand...
Click to collapse
I used NordVPN. They have servers in India.
Update download was a bit slow though.
Thank you very much. It is downloading now. Slow but at least I will have it. Thank you again.
EugeniusD80 said:
I used NordVPN. They have servers in India.
Update download was a bit slow though.
Click to expand...
Click to collapse
Downloaded the first time with VPN, tried to install it, but it didn't work (I had TWRP, and after reboot I got the message that the update was corrupted). I flashed the recovery from the Google Spreadsheet: https://docs.google.com/spreadsheet...EYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=2137120377
using:
Code:
adb reboot download
and then:
Code:
fastboot flash recovery recovery_1.27.400.21.img
I checked for updates and it asked me to download it again, no VPN needed. Downloaded it and tried to install it (much faster). Phone restarted, update started, and after a few seconds I saw a black screen with a red triangle.. it looks the same as when it's in recovery mode.... Had to restart the phone again.
I'm trying again to download it and I'll check better if I can see the error.
Edit: It goes fast from 1% to 24%, then it stops at 24% for about 19 seconds and then black screen with red triangle...
Any idea what the problem could be?
Samribi said:
I checked for updates and it asked me to download it again, no VPN needed. Downloaded it and tried to install it (much faster). Phone restarted, update started, and after a few seconds I saw a black screen with a red triangle.. it looks the same as when it's in recovery mode.... Had to restart the phone again.
I'm trying again to download it and I'll check better if I can see the error.
Edit: It goes fast from 1% to 24%, then it stops at 24% for about 19 seconds and then black screen with red triangle...
Any idea what the problem could be?
Click to expand...
Click to collapse
Sorry, don't think I can be of any help here. Have almost no experience with this sort of things.
In my case I did not do any tweaking with the original OS.
First tried to explore any possible option to get it "official" way.
My only guess would be to try to roll back to the original state and to have no trace of tweaking.
EugeniusD80 said:
Sorry, don't think I can be of any help here. Have almost no experience with this sort of things.
In my case I did not do any tweaking with the original OS.
First tried to explore any possible option to get it "official" way.
My only guess would be to try to roll back to the original state and to have no trace of tweaking.
Click to expand...
Click to collapse
Yes, I will try to do a factory reset this weekend. If it's not working, I will try to follow the instructions on the other post to flash a RUU.
Edit: I did a factory reset, tried to update to Oreo, it still stopped at 24%. I flashed the latest RUU I could find on the spreadsheet, and then after 2 updates I'm finally on Oreo!!!
HTC u11 Oreo update received via WiFi 4 days ago
Just got the notification!
Android 9.0 - Beta 3
PPR1.180610.066
Don't notice anything new so far. It looks like the font may be slightly different, and the kernel has been updated. Still no notch settings, and the lag that happens still exists.
Sorry to be thick but do a have too sidload or flash or is it OTA?
I have no updates...
Sent from my PH-1 using Tapatalk
oracleoftruth said:
Sorry to be thick but do a have too sidload or flash or is it OTA?
I have no updates...
Click to expand...
Click to collapse
I fastboot flashed but you can OTA by downloading the zip from essentials sideloading like you mention
Did the GPU version changed？
OTA rolling out
t2jbird said:
OTA rolling out
Click to expand...
Click to collapse
It rolled out when I posted it, I got the notification about half hour before then. Probably a staggered rollout though
crixley said:
It rolled out when I posted it, I got the notification about half hour before then. Probably a staggered rollout though
Click to expand...
Click to collapse
This was the actual ota, pushed directly to the phone.
Package was released when you posted. I thought you just flashed it through fastboot.
crixley said:
Just got the notification!
Android 9.0 - Beta 3
PPR1.180610.066
Click to expand...
Click to collapse
I upgraded from Beta 2 using fastboot rom, but didnt erase data. Everthing is working except home button. Anyone else facing this issue?
I updated ota and my home button is working fine.
hariprs said:
I upgraded from Beta 2 using fastboot rom, but didnt erase data. Everthing is working except home button. Anyone else facing this issue?
Click to expand...
Click to collapse
Sent from my PH-1 using Tapatalk
Beta 4 update killed my WIFI
The Beta 4 update killed my WIFI reception on my Essential phone. YMMV
hello together.
I`m on the beta 3 with unlocked bootloader.
When I try to install the update ota on the phone I get a installation error.
What could be the problem? Do I have to lock the bootloader to be able to install updates ota?
I know that I can sideload the ota update via fastboot but would like to be able to get ota updates directly on the phone.
t2jbird said:
This was the actual ota, pushed directly to the phone.
Package was released when you posted. I thought you just flashed it through fastboot.
Click to expand...
Click to collapse
Yes, as was mine. I always flash them through fastboot, I'm rooted and even when I wasn't I had issues with the latest radio not applying, OTA failing even though I unrooted etc. That's why in the post I said I just received the notification.
hariprs said:
I upgraded from Beta 2 using fastboot rom, but didnt erase data. Everthing is working except home button. Anyone else facing this issue?
Click to expand...
Click to collapse
I did the same, no issues with my home button. Did you get any failed errors? I usually flash each .img myself
New PH-1 owner here, well new to me but mint from someone else lol. Woke up with the OTA update flag. Unlocked bootloader and unlocked critical. Quick download and restart and it's good to go... No chance to play with anything or poke around yet though
mikeearwood said:
The Beta 4 update killed my WIFI reception on my Essential phone. YMMV
Click to expand...
Click to collapse
Same here. I flashed the latest stable Oreo 8.1 then flashed P beta. It fixed the problem.
What's the best way to flash the fastboot files without wipe? Can I edit out the wipe command in the bat file?
srscott said:
What's the best way to flash the fastboot files without wipe? Can I edit out the wipe command in the bat file?
Click to expand...
Click to collapse
If you're looking to update the build, you can just flash the OTA from the Essential site in TWRP.
Thanks!
crixley said:
I did the same, no issues with my home button. Did you get any failed errors? I usually flash each .img myself
Click to expand...
Click to collapse
Data reset solved the problem.
I also flash the .img myself, didnt get any error while flashing.
Anyway thanks your reply
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