Who's ready for some official pie?
ME!!!
Downloading now! :good:
(System update notification received about 20 mins ago)
Update still hasn't shown up for me. Keep hitting that check button...
That was fast. Downloading it now.
Yeah, well, here we go. Remove PIN...undo overlays in Sub...download and pray!!!
techlogik said:
Yeah, well, here we go. Remove PIN...undo overlays in Sub...download and pray!!!
Click to expand...
Click to collapse
Or just navigate to root/data/ ota package/update.zip, then copy to internal.. then undo security, then flash adb sideload..
Edit. Dont do this, the package isnt signed and fails
I have the update but it keeps failing to install.
jacksummers said:
Or just navigate to root/data/ ota package/update.zip, then copy to internal.. then undo security, then flash adb sideload
Click to expand...
Click to collapse
Good idea, because it keeps failing on the install...will give this method a go...thanks. Plus they don't have the download zip on Essential support...so kind of have to try this if I want Pie..haha
Thanks
jgates86 said:
I have the update but it keeps failing to install.
Click to expand...
Click to collapse
It wont go twrp, have to use fastboot or adb sideload
My wife's phone got it before mine, still waiting :/
jacksummers said:
It wont go twrp, have to use fastboot or adb sideload
Click to expand...
Click to collapse
I'm straight stock DP5, no unlocked bootloader or anything so not sure why it won't update.
jgates86 said:
I'm straight stock DP5, no unlocked bootloader or anything so not sure why it won't update.
Click to expand...
Click to collapse
Oh then just take it ota
Fails the sideload as well.
Installing Update....
Step 1/2
Error applying update 20 (ErrorCode kDownload StateInitializetionError)
Error in /sideload/package.zip
Installation aborted
On my command prompt:
adb sideload update.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
Going to try a flashall.bat with the stock image file again, reboot and try to OTA it..see what happens.
jacksummers said:
Oh then just take it ota
Click to expand...
Click to collapse
That's where it;s failing, just downloads, starts step 1 of 2 and just says installation problem with no other info.
Just got it installing myself, been running the Beta Preview for months...we'll see what the Pie is like...hopefully it's not a Cleveland Steamer Pie...
OH well, the full file just showed up for download on the Dev Essential support site...will just update that way!!
Just installed and it looks good.
I think I would need some time to get familiar with the new navigation bar though.
OTA download is a little slow so you'll need to grab a beer and be patient.
There are a couple of changes that make it more iOS-like -- the smart text selection with the window and also the carousel that displays the recent apps when you swipe up. I wish the navigation bar were fully transparent, but I guess you can always revert back to a mod for that. I'm most interested to see if there is indeed an improvement in battery performance and whether signal improves with my T-Mobile service. Enjoy!
Update: the gestures implemented by Google seem a little half-baked in comparison to OnePlus'. The latter's is a more preferable interpretation to me.
Does the open market OTA work on Sprint version, or are we stuck waiting?
Related
OK, so why does 3.1 update fail on a rooted device ?
The only thing I did when rooting my device was to replace
the "su" program. If I revert that change, will the OTA update
work ?
Anybody has the original "su" and it's mode settings (ls -l) ?
Thanks,
rudi
PS: Actually, I guess we need the "su" from 3.0.1 ...
But to get "su" on there in the first place, you likely had to flash your boot.img.
The update checks your system and boot.img to verify that it's stock before proceeding, as applying patches to modded files will likely have craptastic results.
What method are you using to update? What specific error message are you getting on the failure?
Yeah, so if reverse the boot.img and "su" package, the original
update should work ?
I don't remember the error message, I got the OTA update, and
it basically failed. Has not shown up again ...
Thanks,
rudi
FYI, I was able to root my xoom without loosing any data following these steps:
http://www.mydroidworld.com/forums/...ow-manually-update-your-xoom-3-1-3-0-1-a.html
luudee said:
I don't remember the error message, I got the OTA update, and
it basically failed. Has not shown up again ...
Click to expand...
Click to collapse
Weird...I'm rooted...got the OTA update, hit Install now, it went through the countdown process to reboot and install update, but then nothing happend. No reboot, no error message. I manually shutdown and turned on the device and got nothing.
Is that what happened to you?
--Q
Yeah, that's what happened to me as well. It looks like it will install the update,
but than shows some message for a second and than shows the android with
the Explanation mark (Warning sign).
If you check, you will see that you are still using 3.0.1 ... (At least that was my case).
Follow the post i referenced above, it is easy, safes all your data and gives
you 3.1 and root.
Cheers,
rudi
Thanks...that was my original plan, but then I got the OTA notification and figured I'd do that instead. Guess not! LOL
--Q
Here's the files from the update... not much we can do with them though...
http://www.androidfilehost.com/?fid=23501681358545806
Edit: I was on 800-20k with a custom recovery (autorec) installed. Taking the update will put you in a "recovery" bootloop. I was able to get out of the bootloop by nulling out the fota partition.
I reflashed the 800-20c TOT file using LGFlashtool and then went and did a software update. It downloads both 20k and 20u updates and applies them both. Afterwards I rooted using autoprime's ioroot25r1 tool (adb sideload method).
Because there is a new kernel to support knock-code, do NOT flash a recovery using autorec or anything that will affect the kernel until a developer gets their hands on it and inserts the older bootloader.
-Daryel
Just got this notification. Anybody know if there's anything important or significant with this?
Sent from my LG-D800 using Tapatalk 4
RS7JR said:
Just got this notification. Anybody know if there's anything important or significant with this?
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
The only difference I see is knock-code.
Good news is that ioroot25 still works on it.
-Daryel
so, do you lose root after this update? i'm rooted with no custom recovery
xbxjunkie said:
so, do you lose root after this update? i'm rooted with no custom recovery
Click to expand...
Click to collapse
ota should error out, mine did, i tried twice.
spdwiz18 said:
ota should error out, mine did, i tried twice.
Click to expand...
Click to collapse
hmm, then i'm not gonna do it. anyone know where it's downloaded to and what to freeze to prevent the DL again
i'm coming from a tmobile G2 and the update app is different
Nvm.....found and froze it.....problem solved
spdwiz18 said:
ota should error out, mine did, i tried twice.
Click to expand...
Click to collapse
After it errors out, do the notifications stop? I've "postponed" mine atm and have no interest in actually updating. I'm not wanting to be pestered daily by the update request. (I'm stock recovery rooted too)
Edit: It detected that I'm rooted and has stopped notifications.
daryelv said:
The only difference I see is knock-code.
Good news is that ioroot25 still works on it.
-Daryel
Click to expand...
Click to collapse
Here's AT&T's update page that has some info: http://www.att.com/esupport/article.jsp?sid=KB423381&cv=820#fbid=9EhTGDbrWCI
Software update includes:
Knock Code" security feature
Calendar/ Exchange Active Sync (EAS) enhancements
I've also noticed that Album Art for music playing in Google Music now takes up the entire lock screen; the previous release only displayed in a little box at the top.
spdwiz18 said:
ota should error out, mine did, i tried twice.
Click to expand...
Click to collapse
I was able to take the update and did not lose root. however I do not have a recovery installed.
D800 model
skullymullins said:
I was able to take the update and did not lose root. however I do not have a recovery installed.
D800 model
Click to expand...
Click to collapse
I was able to root last week with IOroot, d/l the update yesterday, and keep root.
newb here. mine just automatically updated to 20u. I saw the update when I recieved my g2 yesterday but didn't think it was going to update by its self. can I still follow the pinned newbie guide and use ioroot25 and AutoRec?
edit: re-read the first post, so can't use autorec till its updated? do you think it will take long? I wanted to put cm on
Gabe3 said:
newb here. mine just automatically updated to 20u. I saw the update when I recieved my g2 yesterday but didn't think it was going to update by its self. can I still follow the pinned newbie guide and use ioroot25 and AutoRec?
edit: re-read the first post, so can't use autorec till its updated? do you think it will take long? I wanted to put cm on
Click to expand...
Click to collapse
Autorec will work, but you'll lose the "knock code" which I doubt you would care about if you're going with CM. Autorec will be updated sometime after LG releases the source code for the kernel. The latest they still have posted is the code for D800-20c.
-Daryel
daryelv said:
Autorec will work, but you'll lose the "knock code" which I doubt you would care about if you're going with CM. Autorec will be updated sometime after LG releases the source code for the kernel. The latest they still have posted is the code for D800-20c.
-Daryel
Click to expand...
Click to collapse
thats great, thanks. and ioroot still works as well? i'll have to do some googling what the knock code is.
I'm bone stock, unrooted and just got the latest update. Only difference i see is Knock Code (which is very cool BTW), other than that it's still the same old awesome G2. Glad to see they are still paying attention to it now that they are focusing on the G3. Wonder if we'll get the new G3 UI on the (stock) G2
ItsDon said:
I'm bone stock, unrooted and just got the latest update. Only difference i see is Knock Code (which is very cool BTW), other than that it's still the same old awesome G2. Glad to see they are still paying attention to it now that they are focusing on the G3. Wonder if we'll get the new G3 UI on the (stock) G2
Click to expand...
Click to collapse
This! :thumbup:
Scribe'd on my awesome OG2
daryelv said:
Autorec will work, but you'll lose the "knock code" which I doubt you would care about if you're going with CM. Autorec will be updated sometime after LG releases the source code for the kernel. The latest they still have posted is the code for D800-20c.
-Daryel
Click to expand...
Click to collapse
"IF and WHEN" LG decides to update it seeing as they never released source for 10q or 20k(and now 20u but it just started going public so who knows)
daryelv said:
Edit: I was on 800-20k with a custom recovery (autorec) installed. Taking the update will put you in a "recovery" bootloop. I was able to get out of the bootloop by nulling out the fota partition.
-Daryel
Click to expand...
Click to collapse
How can I do that? Nulling out the fota partition
I have the same problem
Thanks
Sent from my KFTHWI using Tapatalk
Sj12345 said:
How can I do that? Nulling out the fota partition
I have the same problem
Thanks
Click to expand...
Click to collapse
Like this...
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
-Daryel
I tried ioroot25r1 on the 20u update but when it says press any key to continue the window just closes.
Gabe3 said:
I tried ioroot25r1 on the 20u update but when it says press any key to continue the window just closes.
Click to expand...
Click to collapse
have you tried the manual method:
1)open cmd window inside ioroot25 folder
2)place phone in airplane mode and enable usb debugging then plug into pc
3)type adb devices in cmd to make sure device is visible
4)after you see your device type adb reboot recovery
5)when the phone reboots into stock recovery using volume keys scroll to adb sideload update option and use power button to confirm
6)in cmd window type adb sideload kk_root.zip
7)you should see dat root on phone screen
8)enjoy root
Click to expand...
Click to collapse
Sent from my Potato powered G2 D800
Just got this OTA. Totally unexpected!
I was Rooted with TWRP Installed. So couldn't get to install it But I have captured the OTA.
Here's the link: https://drive.google.com/open?id=0B7swCULtrdl5SW5GQkZISmdFNDQ
I'll try to Install this later this evening.
I still hope they will release VoLTE update unexpectedly!
Nice. I might stay for a while with stock until LineageOS with N blobs comes out.
installing via adb fastboot.. will notify once done
edit: done
Wow! I'm slightly impressed... A new security update on the X Style.
Now if they would just roll-out Nougat to Pure. :/
Is there a Volte support?
Sent from my XT1572 using Tapatalk
krishnas.goutham said:
Is there a Volte support?
Click to expand...
Click to collapse
The release notes clearly state it is only August 2017 security update... So I am going to say no.
Sagar_1401 said:
installing via adb fastboot.. will notify once done
edit: done
Click to expand...
Click to collapse
I'm not getting the OTA
Could you please let me know the steps to install this via adb
I'm on NPH25.200-15 with unlocked bootloader
#noob
It's just a security update. Just wait for it roll out to your device.
krishnas.goutham said:
I'm not getting the OTA
Could you please let me know the steps to install this via adb
I'm on NPH25.200-15 with unlocked bootloader
#noob
Click to expand...
Click to collapse
download the ota files on ur pc and then store it some directory that u want
then turn off your phone and put it into bootloader mode and select recovery mode..
now here comes important step.. u need to be in stock recovery and it will be totally blank.. with a triangle Android
now keep pressing vol up and power button simultaneously..(luckily ull enter the recovery mode or it gets rebooted if done many times)
if u successful entered the recovery mode ull find 5 options or 6
1) reboot
2)applt update from sd card
3)...
.
.
.
select the option which says something sideload ( i don't remember it) and connect yours phone to pc via usb cable
u need to install adb interface for sideloading download from here..
https://forum.xda-developers.com/showthread.php?t=2588979
after installing this.. open cmd prompt and then locate it where u stored the ota file.
and then use the following code to install the ota
adb sideload finename.zip
it will stay at 66% for 3-4 mins.. donot close the cmd window and do not disconnect the phone from pc or u may endup in softbrick
file name just copy paste and then use.zip at the end..
this are the steps to install it manually via adb sideloading
Hello! Where can I find the 7.0 stock rom that fits with that OTA? Would it run in a US Version of the XT1572? (I can see that you're running the IN version)
Thanks!
severus.snape said:
Hello! Where can I find the 7.0 stock rom that fits with that OTA? Would it run in a US Version of the XT1572? (I can see that you're running the IN version)
Thanks!
Click to expand...
Click to collapse
You can't... there is no "US version" of the XT1572. In the US we have the Pure which is XT1575 and it hasn't gotten Nougat yet.
acejavelin said:
You can't... there is no "US version" of the XT1572. In the US we have the Pure which is XT1575 and it hasn't gotten Nougat yet.
Click to expand...
Click to collapse
Thanks dude! Let's keep waiting then...
Complete shocker from Motorola this one. Had zero expectancy about future support after the nougat update.
25.201.3
I was waiting for the update after seeing your post & just finished installing OTA update on my Moto X Style... Thanks...
Does this mean we are getting Oreo at some point ?
D.Spirit said:
Does this mean we are getting Oreo at some point ?
Click to expand...
Click to collapse
Absolutely not!
D.Spirit said:
Does this mean we are getting Oreo at some point ?
Click to expand...
Click to collapse
From Moto?!?!?! Hahahahahahaha... Dang it, coffee hurts when it shoots out your nose.
Will we get it custom ROMs? Absolutely... Stock? I would probably win lotto before that occurs.
D.Spirit said:
Does this mean we are getting Oreo at some point ?
Click to expand...
Click to collapse
are you serious?
D.Spirit said:
Does this mean we are getting Nougat at some point ? -XT1575 owners
Click to expand...
Click to collapse
Fixed.
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.
Pixel 7 Pro Sideload OTA for January 2023 FAILED now phone Google image start and stops.
I followed exact instructions and OTA sideload failed. rebooted and now screen just flashes Google every 15 seconds or so. Not sure what to do!
Help!
Sorry I'm at work and don't have much time to help and maybe someone else will chime in. It's stuck in a bootloop. Try using the Pixel Flasher Tool to sideload the OTA or the image
Just flash.
Android Flash Tool
flash.android.com
jaseman said:
Pixel 7 Pro Sideload OTA for January 2023 FAILED now phone Google image start and stops.
I followed exact instructions and OTA sideload failed. rebooted and now screen just flashes Google every 15 seconds or so. Not sure what to do!
Help!
Click to expand...
Click to collapse
More information is needed like are you rooted did you download the correct OTA file what instructions did you follow where did you download the file from
I was able to "fix" my issue and redo the OTA successfully!
I had to use the button combo of Power-volume down to get to a place where I could choose the proper setting and get back to the screen where I could again choose sideload from ADB. This time it completed successfully. Not sure why it failed the first time.
WHEW!!!!!!!
I downloaded from the Google site for OTA files and I chose the proper file.
All is good now and everything appears to be OK.
Thanks to all who quickly responded to my concerns!!!!!!
Just use the web browser to update it if you're using an unlocked phone.
UltimateGamer83 said:
Just use the web browser to update it if you're using an unlocked phone.
Click to expand...
Click to collapse
Even though I was ultimately able to sideload the update using ADB (and all is good on day 2) I am curious as to how this can be accomplished using a web browser? Do you have detailed instructions for such a procedure? I do have an unlocked phone...always!
jaseman said:
Even though I was ultimately able to sideload the update using ADB (and all is good on day 2) I am curious as to how this can be accomplished using a web browser? Do you have detailed instructions for such a procedure? I do have an unlocked phone...always!
Click to expand...
Click to collapse
The Android Flash Tool is used through your web browser https://flash.android.com/welcome?continue=/devices?continue=%2Fcustom
If I am not mistaken this method will "wipe" your device?
That is not a desirable thing unless your phone is hosed.
jaseman said:
If I am not mistaken this method will "wipe" your device?
That is not a desirable thing unless your phone is hosed.
Click to expand...
Click to collapse
You just change the settings to uncheck the options for wipe, force flash partitions, and lock bootloader. I actually used Android Flash Tool to upgrade my phone the other day and it went fine. I just wanted to see how it worked. Going back to PixelFlasher since I want to keep root but yeah, pretty cool tool.