I just received a small update weighing in at 167MB and now it says version MP3
Is everyone else on this version already?
jananan said:
I just received a small update weighing in at 167MB and now it says version MP3
Is everyone else on this version already?
Click to expand...
Click to collapse
Yes
Just got the update just now as well.
But not able to update from OTA. Can someone drop a zip of the newest update so I can update, please and thank you!
Cammarratta said:
Just got the update just now as well.
But not able to update from OTA. Can someone drop a zip of the newest update so I can update, please and thank you!
Click to expand...
Click to collapse
You rooted? If so, thats why.
I am. That's an interesting find.
Cammarratta said:
I am. That's an interesting find.
Click to expand...
Click to collapse
You can't update rooted. Flash stock non rooted boot.img
bs3pro said:
You can't update rooted. Flash stock non rooted boot.img
Click to expand...
Click to collapse
Do you have a non rooted boot.img file?
Yes , in mp3...
Sent from my [device_name] using XDA-Developers Legacy app
Anyone having this issue, it's downloading & show updating then stops without updating and then shows that there is a new update
My phone is not rooted but fully unlocked (critical partition), is that the problem?
k2009 said:
Anyone having this issue, it's downloading & show updating then stops without updating and then shows that there is a new update
My phone is not rooted but fully unlocked (critical partition), is that the problem?
Click to expand...
Click to collapse
I just got mine so I haven't unlocked bootloader yet, the OTA went smoothly.
I tried looking for the OTA.zip but couldn't find it.
It didn't even warn me before the reboot to apply the update...
jananan said:
I just got mine so I haven't unlocked bootloader yet, the OTA went smoothly.
I tried looking for the OTA.zip but couldn't find it.
It didn't even warn me before the reboot to apply the update...
Click to expand...
Click to collapse
Now even it's not showing that there is an update.
k2009 said:
Now even it's not showing that there is an update.
Click to expand...
Click to collapse
It will reappear in a day or 2.
Again received update with same issue, downloading and then says updating, don't shutdown the phone & after around 1 minute it stops without restart or updating then again showing that there is an update.
Any help?
Flash MP1 using *#*#1027#*#*, reboot to recovery, wipe data. Boot, update to mp2, reboot to mp2, take the mp3 update.
Do you have to reinstall all apps?
bs3pro said:
Flash MP1 using *#*#1027#*#*, reboot to recovery, wipe data. Boot, update to mp2, reboot to mp2, take the mp3 update.
Click to expand...
Click to collapse
did you do this with unlocked bootloader?
I mean Im already on MP2 and as others say, I cant update to MP3 it says updating and then restarts
raz0r9199 said:
Do you have to reinstall all apps?
Click to expand...
Click to collapse
omer919 said:
did you do this with unlocked bootloader?
I mean Im already on MP2 and as others say, I cant update to MP3 it says updating and then restarts
Click to expand...
Click to collapse
Yes, and follow my directions. Doesn't get much easier.
bs3pro said:
Flash MP1 using *#*#1027#*#*, reboot to recovery, wipe data. Boot, update to mp2, reboot to mp2, take the mp3 update.
Click to expand...
Click to collapse
Anyway can I do it without wiping the data.
Thanks.
can't wait for the next MIUI 12.hope it brings better navigator gestures like OnePlus and pixels.
jananan said:
can't wait for the next MIUI 12.hope it brings better navigator gestures like OnePlus and pixels.
Click to expand...
Click to collapse
Its horrible. I ran the CN version. Couldnt get back to joyui11 quick enough.
Related
I captured the OTAPkg.zip, but I can't upload it...... Any suggestions where I should upload it for everyone??
xangel9626 said:
I captured the OTAPkg.zip, but I can't upload it...... Any suggestions where I should upload it for everyone??
Click to expand...
Click to collapse
Send a tip to the moderators at xda-developers.com or alert androidpolice.com, I can see them helping you.
xangel9626 said:
I captured the OTAPkg.zip, but I can't upload it...... Any suggestions where I should upload it for everyone??
Click to expand...
Click to collapse
Very, very nice! Thanks for capturing the OTA! I'd be glad to help you in the uploading process. Perhaps a good place to upload it would be DevHost or Google Drive? Feel free to let me know if you need help doing so. Once it's uploaded, I'll be sure to update the story I put out earlier on this update: http://www.xda-developers.com/andro...6-update-finally-rolls-out-to-att-htc-one-m7/
google drive or any file host really
willverduzco said:
Very, very nice! Thanks for capturing the OTA! I'd be glad to help you in the uploading process. Perhaps a good place to upload it would be DevHost or Google Drive? Feel free to let me know if you need help doing so. Once it's uploaded, I'll be sure to update the story I put out earlier on this update: http://www.xda-developers.com/andro...6-update-finally-rolls-out-to-att-htc-one-m7/
Click to expand...
Click to collapse
Wonders_Never_Cease said:
google drive or any file host really
Click to expand...
Click to collapse
Here you go guys Enjoy ...
http://www.androidfilehost.com/?fid=23501681358542441
MD5: 317bae285618b070279b3a58b2e308e5
Cool thanks sir
clsA said:
I'll post the link here at about 10:15 EST (around 10 min to go)
Click to expand...
Click to collapse
xangel9626 said:
I captured the OTAPkg.zip, but I can't upload it...... Any suggestions where I should upload it for everyone??
Click to expand...
Click to collapse
I got you covered .. thanks for the heads up
clsA said:
Here you go guys Enjoy ...
http://www.androidfilehost.com/?fid=23501681358542441
MD5: 317bae285618b070279b3a58b2e308e5
Click to expand...
Click to collapse
Many thanks, good sir. Article updated and credit given.
clsA said:
I got you covered .. thanks for the heads up
Click to expand...
Click to collapse
Thanks clsA. I tried to post a link and I wasn't even allowed to do that......
xangel9626 said:
Thanks clsA. I tried to post a link and I wasn't even allowed to do that......
Click to expand...
Click to collapse
it's ok ... Welcome to XDA
Flashable w/ stock recovery?
xandr115 said:
Flashable w/ stock recovery?
Click to expand...
Click to collapse
It's supposed to be. I got the update from my wife's phone which was able to update, but when I tried to apply it to my phone (which won't download the update) with recovery, I get a Check CID Failed and my phone reboots. All you can do is try and see if it works.
xangel9626 said:
It's supposed to be. I got the update from my wife's phone which was able to update, but when I tried to apply it to my phone (which won't download the update) with recovery, I get a Check CID Failed and my phone reboots. All you can do is try and see if it works.
Click to expand...
Click to collapse
So is this the Sense 6 update only? Will I lose any data, apps, or settings?
xpurtwitness said:
So is this the Sense 6 update only? Will I lose any data, apps, or settings?
Click to expand...
Click to collapse
Nope, it's just the Sense 6 update, everything on your phone is safe.
xpurtwitness said:
So is this the Sense 6 update only? Will I lose any data, apps, or settings?
Click to expand...
Click to collapse
OTApkg does not wipe the phone like a RUU... your sdcard and data are safe
If you do have to RUU back to stock be sure and backup everything as it will wipe the phone.
clsA said:
OTApkg does not wipe the phone like a RUU... your sdcard and data are safe
If you do have to RUU back to stock be sure and backup everything as it will wipe the phone.
Click to expand...
Click to collapse
Ok, I thought so. Unfortunately, I'm getting errors. The OTA just fails on its own, and flashing this zip in recovery does too. It says there is a data error in the file or that there is a problem with buil.prop.
I've tried the latest CWM touch, CWM standard, Recovery_Cingular_US_3.17.502.3.img, andrecovery_m7_att_stock_1.26.502.12.img. I've tried clearing cache and dalvik first, mounting system, and even toggling signature verifcation.
Was going to try temp un-rooting (via SuperSU) next. Hoping I don't have to flash the RUU and start from zero. Any other suggestions?
I'm s-off, htc-dev unlocked.
Added screenshots of install after new download of zip and temp un-rooted, install after mounting system, install after toggling verification. build.prop is definitely in system.
xpurtwitness said:
Ok, I thought so. Unfortunately, I'm getting errors. The OTA just fails on its own, and flashing this zip in recovery does too. It says there is a data error in the file or that there is a problem with buil.prop.
I've tried the latest CWM touch, CWM standard, Recovery_Cingular_US_3.17.502.3.img, andrecovery_m7_att_stock_1.26.502.12.img. I've tried clearing cache and dalvik first, mounting system, and even toggling signature verifcation.
Was going to try temp un-rooting (via SuperSU) next. Hoping I don't have to flash the RUU and start from zero. Any other suggestions?
I'm s-off, htc-dev unlocked.
Added screenshots of install after new download of zip and temp un-rooted, install after mounting system, install after toggling verification. build.prop is definitely in system.
Click to expand...
Click to collapse
you have to RUU back to stock to use OTA update you don't flash it like a rom
read my post here >> http://forum.xda-developers.com/showthread.php?t=2659374
clsA said:
you have to RUU back to stock to use OTA update you don't flash it like a rom
read my post here >> http://forum.xda-developers.com/showthread.php?t=2659374
Click to expand...
Click to collapse
Got it. So in what case would flashing the zip actually work without having to RUU and get the OTA?
xpurtwitness said:
Got it. So in what case would flashing the zip actually work without having to RUU and get the OTA?
Click to expand...
Click to collapse
on a totally stock phone and flashed from stock recovery
clsA said:
on a totally stock phone and flashed from stock recovery
Click to expand...
Click to collapse
This OTA Update Works with ATT-4.18.502.7-Stock-Rooted-ODEX ROM?
Thanks!
I just got the 5.1 OTA. It feels a little faster so far. Although, my 5ghz WiFi router doesn't work right anymore. It will only connect at 2.4 GHz.
fzurita said:
I just got the 5.1 OTA. It feels a little faster so far. Although, my 5ghz WiFi router doesn't work right anymore. It will only connect at 2.4 GHz.
Click to expand...
Click to collapse
I think it is a bug From Google, the same was with 4.4.3, WLAN bugs and more, i think in next update it will be fixed
the-cortana-project said:
I think it is a bug From Google, the same was with 4.4.3, WLAN bugs and more, i think in next update it will be fixed
Click to expand...
Click to collapse
This has to be a new bug. It used to work fine in 4.4.4 and 5.0.
fzurita said:
This has to be a new bug. It used to work fine in 4.4.4 and 5.0.
Click to expand...
Click to collapse
Is there any other issues?
theinspector said:
Is there any other issues?
Click to expand...
Click to collapse
Not that I have seen so far. The camera seems about the same as before. The Wi-Fi bug is kind of annoying though since it limits how fast I can transfer files around.
if only we could have a port for non GPe Z Ultra :victory:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
MrSewerPickle said:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
Click to expand...
Click to collapse
you tried to flash OTA with unlocked bootloader? ...if so ...lol :silly:
@scrubber @blueether @egzthunder1
Just received the 5.1 update as well...
Looks like several bugs have been addressed... Seems quicker/less laggy.
Nice that they fixed the charging info on the lock screen that always said the wrong thing when NOT charging...that always bugged the hell out of me for some reason.
Will check back tonight after a day of use.
---------- Post added at 09:27 AM ---------- Previous post was at 09:24 AM ----------
MrSewerPickle said:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
Click to expand...
Click to collapse
SÜPERUSER said:
you tried to flash OTA with unlocked bootloader? ...if so ...lol :silly:
Click to expand...
Click to collapse
Oops! ?
I know, shame on me. I should never attempt to install an update that shouldn't have anything whatsoever to do with my boot loader being locked or unlocked.
Actually, I should probably start paying Google to collect my personal data and ask them each time I install apps as well.
Care to explain exactly in detail why a OTA would failed on a unlocked boot loader? And why it would affect a factory boot loader at that? And why the 5.0 update didn't give a damn (as it should) about if the boot loader was locked or not?
MrSewerPickle said:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
Click to expand...
Click to collapse
Experienced the same issue here.
Didn't work on my GPE either. Had to reboot twice before getting the phone to work. Went into settings to manually look for an update and now it says my phone is up to date even though it is still 5.0.
fosselman said:
Didn't work on my GPE either. Had to reboot twice before getting the phone to work. Went into settings to manually look for an update and now it says my phone is up to date even though it is still 5.0.
Click to expand...
Click to collapse
Same here. Went to install the update and it failed. Rebooted and now system update is showing that my phone is up to date. Guess I'll have to sideload the ota once someone publishes the link.
Mugenmundo said:
Experienced the same issue here.
Click to expand...
Click to collapse
draiko913 said:
Same here. Went to install the update and it failed. Rebooted and now system update is showing that my phone is up to date. Guess I'll have to sideload the ota once someone publishes the link.
Click to expand...
Click to collapse
I just got another notification saying it downloaded it again and is ready to install. Gonna wait til I get off work to install it.
Is anyone able to grab the OTA link and post it?
If someone is running the 5.1 GPE on their ZU-gpe, can you share the build.prop from it please?
I received my update today too. So far so good.
You can do the :
- App Settings -> Clear Data (on Google Framework services)
- Dial *#*#2432546#*#*
- Settings - > About -> System Update
It may even prompt you to download again before you get to the System Update screen.
Saatvik Shukla said:
If someone is running the 5.1 GPE on their ZU-gpe, can you share the build.prop from it please?
Click to expand...
Click to collapse
Here you go
Hey guys nougat is available to download for axon 7.
A2017U only, of course...
(so far)
Just restored to stock form LeanageOS to give it a spin. Downloading now. Although I saw it on Reddit first ><
I remember lots of people in the other nougat threads that ripped on ZTE saying there's no way it would be ready.. a little late, but not too late. Good job ZTE.
Takenover83 said:
Just restored to stock form LeanageOS to give it a spin. Downloading now. Although I saw it on Reddit first ><
Click to expand...
Click to collapse
Just did the same. Flashed full b29, downloaded update and it failed.
Factory reset, now waiting for download again.
lafester said:
Just did the same. Flashed full b29, downloaded update and it failed.
Factory reset, now waiting for download again.
Click to expand...
Click to collapse
I had the same problem. On my 2nd go around as well. First time I restored B29 from TWRP. After the failed update. I reflashed B29 via the official recovery, and then re-downloaded the Nougate update again. Will update.
Edit: Success.
Takenover83 said:
I had the same problem. On my 2nd go around as well. First time I restored B29 from TWRP. After the failed update. I reflashed B29 via the official recovery, and then re-downloaded the Nougate update again. Will update.
Edit: Success.
Click to expand...
Click to collapse
Nice. almost there myself.
Takenover83 said:
I had the same problem. On my 2nd go around as well. First time I restored B29 from TWRP. After the failed update. I reflashed B29 via the official recovery, and then re-downloaded the Nougate update again. Will update.
Edit: Success.
Click to expand...
Click to collapse
Do you recommend to unlock bootloader before upgrading?
jorch_oc said:
Do you recommend to unlock bootloader before upgrading?
Click to expand...
Click to collapse
Don't know yet. A beta user said all they had to do was go into fastboot and unlock... Hopefully the release build is the same.
So... either wait and see, unlock now, or go for it and be the first to try.
Does nougat have the dreaded power management?
Just tested Daydream a bit. The power button is no longer a problem
But I can't find any options to adjust blur or flicker like in LeanageOS. Also, I still get quiet a bit of drifting to the right. Was hoping Official would help with that, as other fixes/solutions had minimal impact for me.
borijess said:
Does nougat have the dreaded power management?
Click to expand...
Click to collapse
It now has 3 options
Always remind to clean
Auto-clean without reminding
Do not clean
Fastboot doesn't appear to accept any commands unfortunately.
Is this still MiFavour 4.0 or maybe a new version?
4.2
lafester said:
Fastboot doesn't appear to accept any commands unfortunately.
Click to expand...
Click to collapse
Yep, was like grrr when I went to flash twrp.
Takenover83 said:
Yep, was like grrr when I went to flash twrp.
Click to expand...
Click to collapse
So what's the easiest method to install? Trying tennear's tool but I keep getting failed to open recovery.bin.
It came OTA
Could somebody pls pull the ota link?
I can confirm. I am downloading right now. I will try to pull the OTA when it has finished.
It's up and here https://developers.google.com/android/ota
gm007 said:
It's up and here https://developers.google.com/android/ota
Click to expand...
Click to collapse
Changelog?
Sent from my Pixel 3 using Tapatalk
nickporwal said:
Changelog?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-12-01.html
One of this days the 'Check for Update' button will work damn it! Hahahaha
Hahaha right, I have been flashing the OTA manually, its no biggie for me I am used to manually flashing the ota now
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
I got it through ota 1 hour ago.
gm007 said:
I got it through ota 1 hour ago.
Click to expand...
Click to collapse
You know Im mashing the button, lol. Only google phone that got all the updates pretty much same day was the Nexus 6P, I used to get the update notification even before any site would announce that it was out
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Do you have the Magisk uninstaller on your phone? Run it from the temp TWRP .img, and then it should boot OK. Go back to temp TWRP, and install Magisk again. The Edge Sense Plus module is broken again. Don not reinstall it until fixed.
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Flash all after removing the -w, rebooted and let it finish. Boot to TWRP and installed the latest canary. Did not install TWRP.
All good.
jd1639 said:
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ah figured it out, edge sense broken.
edit- thanks guys~
sulpher said:
Ah figured it out, edge sense broken.
Click to expand...
Click to collapse
There's no magic. I sideload the ota in the stock recovery. Booted into the system to make sure everything worked. Powered off the device and booted into the bootloader. Then booted twrp and flashed magisk. Then booted into the system. That's it.
Sent from my [device_name] using XDA-Developers Legacy app
No OTA here... It usually comes days later with unlocked Google pixel using TMobile. -.-
Installed the full version to update it, root just after and everything's fine!
There is only the edge sense that is'nt working as already told
TWRP keeps getting error 1 when flashing the OTA, bit odd
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
laill said:
TWRP keeps getting error 1 when flashing the OTA, bit odd
Click to expand...
Click to collapse
Archangel said:
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
Click to expand...
Click to collapse
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
What I do is download the full updated firmware, unzip that in your platform tools folder,,,make sure you also unzip the second zip inside there as well. If you have the Pixel edge module installed uninstall it and I also uninstalled Magisk in TWRP before I updated just in case there were any problems. Then find the flash-all.bat file in your platform tools folder, right click on it, open with notepad+ and find the -w at the bottom and delete it. After this, save the flash-all.bat notepad xml file and do not just close it. You can then flash the full firmware without it deleting your user data. After this you will have to fastboot boot TWRP and flash the TWRP zip over again. I rebooted then used TWRP to flash the Magisk 17.1 zip. I am up and running and did the same thing last month for the Nov update,,,hope this helps.
Rumsfield said:
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
Click to expand...
Click to collapse
Guys some help please.
I sideloaded the 037 Nov update OK.
Just tried Dec A1 global OTA and got the attached errors. Will I be safe to reboot? Or how do I sort this?
I'm in the UK on a Google Store unlock P6
Just rebooted. Install failure was immediate so despite the warnings guessed I'd be ok. Thankfully I was
Can't figure out where I went wrong. Can anyone tell me why I got those errors?
I got essentially the same errors on my laptop, but it went fine on my desktop. Try a different cable and a different computer or a USB port that is on the motherboard.
mitchst2 said:
Guys some help please.
I sideloaded the 037 Nov update OK.
Just tried Dec A1 global OTA and got the attached errors. Will I be safe to reboot? Or how do I sort this?
I'm in the UK on a Google Store unlock P6
Click to expand...
Click to collapse
sort of looks like you flashed a coreupt download... or the wrong firmware for your device
kevp75 said:
sort of looks like you flashed a coreupt download... or the wrong firmware for your device
Click to expand...
Click to collapse
Checked the download was good.
mitchst2 said:
Checked the download was good.
Click to expand...
Click to collapse
You verified the md5 checksum after you downloaded it? The only other thing would be you flashed the wrong one for your device ... but I guess if it works, no point in continuing on right?
Tool Belt said:
I got essentially the same errors on my laptop, but it went fine on my desktop. Try a different cable and a different computer or a USB port that is on the motherboard.
Click to expand...
Click to collapse
Might be the cable. Can't be sure if I used a different cable last time? It'll have to wait for another day now.
You try the google flash tool? If you're unlocked you could extract the factory image and fastboot update with the extracted Oriole zip
mitchst2 said:
Guys some help please.
I sideloaded the 037 Nov update OK.
Just tried Dec A1 global OTA and got the attached errors. Will I be safe to reboot? Or how do I sort this?
I'm in the UK on a Google Store unlock P6
Click to expand...
Click to collapse
You should be using the A4 OTA file since you're in the UK
arbrouwer said:
You should be using the A4 OTA file since you're in the UK
Click to expand...
Click to collapse
My understanding is that the A1 build is a Global build for Google Store bought unlocked phones which mine is.
Besides I tried A4 when A1 failed with the same result.
Pretty sure it's a cable issue.
mitchst2 said:
Guys some help please.
I sideloaded the 037 Nov update OK.
Just tried Dec A1 global OTA and got the attached errors. Will I be safe to reboot? Or how do I sort this?
I'm in the UK on a Google Store unlock P6
Click to expand...
Click to collapse
That happened to me the 1st time I sideloaded the mid-nov update, it read the img but failed installing it.
Turned out that simply switching from the front left USB 2.0 to the front right USB 2.0 of my PC solved it and I was able to sideload properly. No idea how or why that would make a difference though but I guess that's technologie for you
Hoped the OTA worked come today and save me the hassle. Still not got it though in the UK. How long can it take to come through?
mitchst2 said:
Hoped the OTA worked come today and save me the hassle. Still not got it though in the UK. How long can it take to come through?
Click to expand...
Click to collapse
Rumor has it that if you sideloaded the mid-november update (037) you won't get an OTA at all.
No idea if that applies to you but if it does you should consider using the flash tool to see whichever update it shows you as Default, then sideload that one. That way future updates should be OTA again (as long as you're not rooted).
Nimueh said:
Rumor has it that if you sideloaded the mid-november update (037) you won't get an OTA at all.
No idea if that applies to you but if it does you should consider using the flash tool to see whichever update it shows you as Default, then sideload that one. That way future updates should be OTA again (as long as you're not rooted).
Click to expand...
Click to collapse
Yes I sideloaded the November update. What is the flash tool. Sorry still new to this Pixel stuff.
mitchst2 said:
Yes I sideloaded the November update. What is the flash tool. Sorry still new to this Pixel stuff.
Click to expand...
Click to collapse
Android Flash Tool
mitchst2 said:
Yes I sideloaded the November update. What is the flash tool. Sorry still new to this Pixel stuff.
Click to expand...
Click to collapse
Yea V0latyle was faster lol - you need to use Chrome for that link though (or maybe Edge too), Firefox etc aren't supported.
Nimueh said:
Rumor has it that if you sideloaded the mid-november update (037) you won't get an OTA at all.
No idea if that applies to you but if it does you should consider using the flash tool to see whichever update it shows you as Default, then sideload that one. That way future updates should be OTA again (as long as you're not rooted).
Click to expand...
Click to collapse
Any threads relating to the no OTA rumours?
mitchst2 said:
Any threads relating to the no OTA rumours?
Click to expand...
Click to collapse
Check this sub forum, there are 1 or 2 that are about the December update and I'm pretty sure users in both mentioned it somewhere.
If you flash 037 update you won't get ota for December update.
But it's better to stay on November patch level.
I'm on December and have bad connection.
Can't use phone call longer then 10 sec ...