Develop Bugs

LCB43B - Huawei Watch update rolling out

Huawei Watch Receives Maintenance Release
Optimized the mic gain for improved "Ok Google" detection
Optimized the fitness tracking to improve step counting accuracy
Optimized the Bluetooth reconnect mechanism
Add a new app to display the battery level when charging
Add a new watch face that user can self-customize
Add fusion sensor of gravity/linear acceleration/rotation vector
Download link in post http://forum.xda-developers.com/showpost.php?p=64009566&postcount=14
you need to be full stock to flash it.

Nothing yet.
Sent from my Nexus 6P using Tapatalk

Can we still get a OTA update with a unlocked bootloader and a custom kernel?

stalls said:
Can we still get a OTA update with a unlocked bootloader and a custom kernel?
Click to expand...
Click to collapse
Nope. I flashed back to stock for it.

bmg1001 said:
Nope. I flashed back to stock for it.
Click to expand...
Click to collapse
dang ok

Changes according to this article are:
Optimized the mic gain for improved "Ok Google" detection
Optimized the fitness tracking to improve step counting accuracy
Optimized the Bluetooth reconnect mechanism
Add a new app to display the battery level when charging
Add a new watch face that user can self-customize
Add fusion sensor of gravity/linear acceleration/rotation vector
I have not received the OTA update yet. I thought the next update would bring speaker support which would have been awesome, but I of course appreciate other improvements as well.

..

MuF123 said:
so do I have to reflash:
-boot
-recovery
-system
and put oem lock back on?
And now - how can I now I am elligle to update? It won't update, however I don't know if it is because it was not rolled out for me yet OR if there is still problem with the watch that prevents it to be OTA updated.
Any ideas?
Click to expand...
Click to collapse
I think you'll need to wait until the OTA is available. I'm on stock and still don't have anything.

bmg1001 said:
Nope. I flashed back to stock for it.
Click to expand...
Click to collapse
how do i lock the bootloader again?

Hopefully I'll be able to use the always on mode without the watch locking up inside of 10 minutes.

earlymorninghours said:
Hopefully I'll be able to use the always on mode without the watch locking up inside of 10 minutes.
Click to expand...
Click to collapse
I'm hoping for that too. Mine isn't as bad if I use a stock face, but I like the ones I've picked out from the Play Store.
Sent from my LG-H810 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 10:24 AM ----------
Motawa88 said:
how do i lock the bootloader again?
Click to expand...
Click to collapse
After you are back to 100% stock use commands
fastboot devices
fastboot oem lock
fastboot reboot
Sent from my LG-H810 using Tapatalk

Motawa88 said:
how do i lock the bootloader again?
Click to expand...
Click to collapse
Unlocked bootloaders are fine with OTAs

Anyway someone can just upload the new update so we can all flash it?

The update seems available here : : https://drive.google.com/file/d/0B4CYHidtQWQGWG1Pbjd6QUYxQzg/view?usp=sharing
source :https://www.reddit.com/r/hwatch/comments/3u9g3e/huawei_watch_lcb43b_update_updatezip_for/
Code:
go to command windows and type : adb reboot bootloader.
choose "reboot-recovery" by clicking fast to go to the right menu, then long press to select it.
the choose apply sideload ADB by swipe down then swipe left/right
and then type : adb sideload update.zip
wait, reboot, wait again and enjoy

imfloflo said:
The update seems available here : : https://drive.google.com/file/d/0B4CYHidtQWQGWG1Pbjd6QUYxQzg/view?usp=sharing
source :https://www.reddit.com/r/hwatch/comments/3u9g3e/huawei_watch_lcb43b_update_updatezip_for/
Code:
go to command windows and type : adb reboot bootloader.
choose "reboot-recovery" by clicking fast to go to the right menu, then long press to select it.
the choose apply sideload ADB by swipe down then swipe left/right
and then type : adb sideload update.zip
wait, reboot, wait again and enjoy
Click to expand...
Click to collapse
getting a error after loading 19%
E: ERROR executing updater binary in zip '/sideload/package.zip'

stalls said:
getting a error after loading 19%
E: ERROR executing updater binary in zip '/sideload/package.zip'
Click to expand...
Click to collapse
No error for me 100% a bit long but it all works.
Are you sure there is no problem with your usb ?
The new charging screen is nice, and the new custom watch face too.

imfloflo said:
No error for me 100% a bit long but it all works.
Are you sure there is no problem with your usb ?
The new charging screen is nice, and the new custom watch face too.
Click to expand...
Click to collapse
Do I have to be stock in any way? I have the boot loader unlocked, custom kernel, and twrp.

stalls said:
Do I have to be stock in any way? I have the boot loader unlocked, custom kernel, and twrp.
Click to expand...
Click to collapse
I believe you do have to be on stock, but the bootloader's state doesn't matter.

Do I need the watch to be connected to WiFi? How do I update the watch?

stalls said:
Do I have to be stock in any way? I have the boot loader unlocked, custom kernel, and twrp.
Click to expand...
Click to collapse
Yes you will need to roll back to stock. Bootloader can stay unlocked.
redeuxx said:
Do I need the watch to be connected to WiFi? How do I update the watch?
Click to expand...
Click to collapse
If you are waiting for the OTA, you will just have to wait until it gets pushed to your watch. You can checked by clicking the system update button in the about screen on the watch, but its rolling out in stages so there is no definitive time on when your watch will get it.

full Odin package *N920AUCS4CQA1* help you up to Nougat quickly

Can not wait for the official Nougat version! Here are the latest model which I can get for you.
Not much to say，here's link for QA1, every person can flash that with Odin and then OTA to Nougat by @norbarb 's way.
Simply speaking, upgrade is divided into two steps. First flash my QA1. Then usd adb update to QC5.
Flash QA1 by Odin:
https://mega.nz/#!EFAiXTKC!S0LvpCIedF_ubVgszflUaN3U_O2zwQoeH6ku68gqnDM
QA1-QC5 Adb files from @norbarb
https://docs.google.com/uc?id=0B4sOy1rlqVoYdnROaFU4LXQybjA&export=download

Warning
Whether Odin or Adb will formate data on your phone. Please backup and then do it.

smxwang said:
Can not wait for the official Nougat version! Here are the latest model which I can get for you.
Not much to say，here's link for QA1, every person can flash that with Odin and OTA to Nougat by @norbarb 's way.
Simply speaking, upgrade is divided into three steps. First flash my QA1. Then usd adb update to QB2. Finaly using adb update to QC5.
Flash QA1:
https://mega.nz/#!EFAiXTKC!S0LvpCIedF_ubVgszflUaN3U_O2zwQoeH6ku68gqnDM
QA1-QB2:
https://forum.xda-developers.com/att...-plus-t3563086
QB2- Nougat:
https://forum.xda-developers.com/att...rvers-t3574757
Click to expand...
Click to collapse
Thanks man...great job

Is this ready for "daily driving"?

Iam on PBH4 (agaust security patch)
can i flash QA1 directly?

TeldenW said:
Is this ready for "daily driving"?
Click to expand...
Click to collapse
Working great for me as DD. Battery life is better than 6.x, but I'd expect that it'd be a little better anyway after a full wipe & fresh install.

samsung lo said:
Iam on PBH4 (agaust security patch)
can i flash QA1 directly?
Click to expand...
Click to collapse
I was on the PK1 yesterday, then I ODIN'd to PL1 (using Norbarb's instuctions and wiped my device in the process).
I then realized that since the device was already wiped, I simply ADB directly to QC5 (as it was already 1.5GB in size and should already contain the previous updates).
Battery life is now horrible, although I'm still trying to get used to the new features by turning off / disabling what I don't need. The update is worth it. as the theme makes me "feel" as though I got a new device. The touchwiz additions replace quite a number of third party apps that I'd have downloaded separately otherwise.

jaxf250 said:
Working great for me as DD. Battery life is better than 6.x, but I'd expect that it'd be a little better anyway after a full wipe & fresh install.
Click to expand...
Click to collapse
As you probably did, I'm using a non-rooted AT&T Galaxy Note 5 (N920A}. I'm familiar enough with ODIN to know that I'll probably mess it up the first try... And spend a lot of time figuring out my mistakes.
Did you have any difficulty with the update process?

TeldenW said:
As you probably did, I'm using a non-rooted AT&T Galaxy Note 5 (N920A}. I'm familiar enough with ODIN to know that I'll probably mess it up the first try... And spend a lot of time figuring out my mistakes.
Did you have any difficulty with the update process?
Click to expand...
Click to collapse
The only problem I encountered was the need to perform the large address aware fix to adb so it would sideload the S4CQB2-to-U4EQC5.zip file for me, otherwise it went fine. Just takes time. I went step by step after first backing all my stuff up. I was on an older MM release that had not been patched with any of the last 3 or 4 security patches, so I began with a complete wipe and ODIN of CPK1. Then sideloaded the rest, one at a time and switching USB debug on each time before the next update: CPK1-to-PL1, then PL1-to-CQA1, then CQA1-to-CQB2, then the final S4CQB2-to-U4EQC5. About 90 minutes maybe, a little less? I can't recall, but wasn't a big deal. It took Google longer to load my 180 apps back on at the end LOL. All the tips (like the large address fix) are in the other thread - just read it over before starting. I see we have a new update too to version QC6.... I may flash that or wait another week or two to see if more updates come out. Honestly it is running just great and I have no issues. Snappy. HTH

I will post in Nougat update thread new update to 4CQB2 to 4EQC6 firmware. Please let me know there if you want 4CQA1 to 4EQC6 update also.

jaxf250 said:
The only problem I encountered was the need to perform the large address aware fix to adb so it would sideload the S4CQB2-to-U4EQC5.zip file for me, otherwise it went fine. Just takes time. I went step by step after first backing all my stuff up. I was on an older MM release that had not been patched with any of the last 3 or 4 security patches, so I began with a complete wipe and ODIN of CPK1. Then sideloaded the rest, one at a time and switching USB debug on each time before the next update: CPK1-to-PL1, then PL1-to-CQA1, then CQA1-to-CQB2, then the final S4CQB2-to-U4EQC5. About 90 minutes maybe, a little less? I can't recall, but wasn't a big deal. It took Google longer to load my 180 apps back on at the end LOL. All the tips (like the large address fix) are in the other thread - just read it over before starting. I see we have a new update too to version QC6.... I may flash that or wait another week or two to see if more updates come out. Honestly it is running just great and I have no issues. Snappy. HTH
Click to expand...
Click to collapse
Dude, thanks man. I'm gonna do my research over the next couple days.
Good lookin' out.

norbarb said:
I will post in Nougat update thread new update to 4CQB2 to 4EQC6 firmware.
Click to expand...
Click to collapse
I just got QC5 sideloaded last night. I stayed up restoring my apps and data as close as I had it before on my PK1. This was a time-consuming process.
norbarb said:
Please let me know there if you want 4CQA1 to 4EQC6 update also.
Click to expand...
Click to collapse
You can't now just drop the QC6 on me like that so I have to go through that process all over again.
Hence I'll say "No, thank you" :highfive:

norbarb said:
I will post in Nougat update thread new update to 4CQB2 to 4EQC6 firmware. Please let me know there if you want 4CQA1 to 4EQC6 update also.
Click to expand...
Click to collapse
that's great. No matter what new model is better than elder one.

jaxf250 said:
The only problem I encountered was the need to perform the large address aware fix to adb so it would sideload the S4CQB2-to-U4EQC5.zip file for me, otherwise it went fine. Just takes time. I went step by step after first backing all my stuff up. I was on an older MM release that had not been patched with any of the last 3 or 4 security patches, so I began with a complete wipe and ODIN of CPK1. Then sideloaded the rest, one at a time and switching USB debug on each time before the next update: CPK1-to-PL1, then PL1-to-CQA1, then CQA1-to-CQB2, then the final S4CQB2-to-U4EQC5. About 90 minutes maybe, a little less? I can't recall, but wasn't a big deal. It took Google longer to load my 180 apps back on at the end LOL. All the tips (like the large address fix) are in the other thread - just read it over before starting. I see we have a new update too to version QC6.... I may flash that or wait another week or two to see if more updates come out. Honestly it is running just great and I have no issues. Snappy. HTH
Click to expand...
Click to collapse
Where did you find the QA1-to-QB2 file?

trsanning said:
Where did you find the QA1-to-QB2 file?
Click to expand...
Click to collapse
Here : http://forum.xda-developers.com/showthread.php?p=71184332
Originally from servers
Clicking from Edge of Galaxy

Help
Hello !
Please help, yesterday i try slideload with ADB from U2AOI6 to U2APB2 , i don't know how i did it, but now i have bootloop and messages " dm-verity verification failed "... " update from ADB is disabled " in downloading mode ... Is there any issue to do not loose my data. ..? If not, is the link of S4CQA1 provide here sufficient to make a full flash with odin ?

dakkidd said:
Hello !
Please help, yesterday i try slideload with ADB from U2AOI6 to U2APB2 , i don't know how i did it, but now i have bootloop and messages " dm-verity verification failed "... " update from ADB is disabled " in downloading mode ... Is there any issue to do not loose my data. ..? If not, is the link of S4CQA1 provide here sufficient to make a full flash with odin ?
Click to expand...
Click to collapse
ADB sideload always wipes after it completes
There is an app named Flashify which does not wipe after applying updates but that only works on rooted phones (and you cant root the AT&T Note 5)
Therefore no, there is (currently) no way to prevent sideload wipe

Thank you very much Dezborders!
Now it will be my first time to use Odin, pleaz can you give me the link of the more stable marshmallow for you on N920A... ?

dakkidd said:
it will be my first time to use Odin, pleaz can you give me the link of the more stable marshmallow for you on N920A... ?
Click to expand...
Click to collapse
Seriously dude!
See Page 1 Post 1 Link 1 of this thread.

dezborders said:
Seriously dude!
See Page 1 Post 1 Link 1 of this thread.
Click to expand...
Click to collapse
Lool... I have seen, but the idea was that the last update is not necessary the more stable... But ok, i'll do whith...
Thank you very much.
Sorry for my english, it's not my first speech :good:

Shield Oreo

It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.

Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google

Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo

kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/

JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere

Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.

dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!

Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!

dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language

Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.

dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.

dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?

Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.

eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!

bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/

I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/

Warning for Canadians waiting for Pie

I just got the ota notification this morning, updating it and bricked the damn thing.
Phone wasn't rooted, rebranded or anything, straight OTA messed it up. It boots straight to erecovery, and nothing can be done with it. Hisuite don't work either
Fastboot & rescue mode says
Android reboot issue
Bootloader 1
no
N/A
Reboot_enter_fastboot_common_function
I'm new to Huawei, so how df can I fix it?

In eRecovery, can you enable wifi, connect to wifi, download whole package?
That SHOULD be possible actually!
EML-L29 via Tapatalk

Kaherdin said:
In eRecovery, can you enable wifi, connect to wifi, download whole package?
That SHOULD be possible actually!
EML-L29 via Tapatalk
Click to expand...
Click to collapse
Does not work, says failed to gather package info

https://forum.xda-developers.com/huawei-p20-pro/how-to/upgrade-to-android-pie-throught-t3884054

oslo83 said:
https://forum.xda-developers.com/huawei-p20-pro/how-to/upgrade-to-android-pie-throught-t3884054
Click to expand...
Click to collapse
Not luck with that either, failed to gather package info

So use your huawei warranty.

oslo83 said:
So use your huawei warranty.
Click to expand...
Click to collapse
thats what I ended up doing, still trying though

The update just became available to me tonight on public mobile. Im going to try to take it tonight maybe. I know when i downloaded it from firmware finder before it actually became approved, it wasnt the size it said it should have been when it finished downloading. Im wondering if it is corrupt. It's C792 for Kirin 970. I also dont see it on androidhost.

Ok so i took the update through software update app built into the phone and everything went fine. Seems like the phone may even be a tad snappier. Still no expandable notifications though.

Question RE : SD1A.210817.037

My device is running .036 and about a week ago the system update said there was a download. I am assuming is .037 because that is the only thing it could be...
I try to download it and it fails and it says to try again and it fails, repeat ad nauseum...
Is this ( .037 ) supposed to download ?
Ah snap, is my phone's update software broken ?
I assume this android bug will only go away with a factory reset...
Hmm...
Because fixes are cumulative, should I just wait a little bit and download December's update. I am assuming there will be a software update in December besides the security stuff.
Vote now.
Factory Reset -or- wait

You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip

miravision said:
You can always sideload updates using adb on a computer if the OTA is failing for you
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037-1543ec70.zip
Verizon
Code:
https://dl.google.com/dl/android/aosp/raven-ota-sd1a.210817.037.a1-9436a359.zip
Click to expand...
Click to collapse
Ug, ya I know, too many questions... lets try again...
Question: Is the .037 supposed to download ?

Yes

I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.

miravision said:
Yes
Click to expand...
Click to collapse
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?

NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Cool ! I like that idea. Will the newer update push in front of the glitched update ?

old_fart said:
Because mine is failing to download, I must have a software glitch. Crap. Crap. Crap. Glitches do not magically go away...
Question 2 : Doing the sideload of the OTA after pulling it down . . . will it wipe me completely. Is there a batch switch to install-all that will NOT wipe the data area and allow me to retain my setup ?
Click to expand...
Click to collapse
The OTA will not wipe, no flags needed. Only the full image will wipe, unless you use the flag.
I doubt your update system is broke, I suspect you just got a bad download. Next download will be fine I think. So sideload or wait for December.

NippleSauce said:
I would just wait. The December update was rumored to drop on the first. But even if it doesn't, it shouldn't take much longer regardless.
Click to expand...
Click to collapse
Monthly updates usually occur on the 1st Monday of each month, which would be the 6th for December. Just curious, where did you hear this rumor that they were deviating from this process?

old_fart said:
My device is running .036 and about a week ago the system update said there was a download. I am assuming is
Click to expand...
Click to collapse
To be clear, are you rooted, or at least running a custom kernel? If yes to either one, you shouldn't attempt to take any automatic downloads. At worst they just won't update, such as you found out, or at worst it could break something, although still not catastrophic except maybe losing some data.
So, if you are rooted or at least using a custom kernel, you should turn off automatic updates in the Developer Options. And if you're not rooted and not using a custom kernel, then go with what everyone else said. Now if December's OTA failed to update your phone correctly and you're not rooted or using a custom kernel, then I would consider first just flashing the full factory image (whatever the most up to date at the time will be) while removing the -w (wipe) command from the flashall.bat.
Also, to complicate this reply even further, whether you're rooted or not, have you /or disabled verity and verification? If so, when you use the flashall.bat, you're going to want to put the disable verity and verification commands in place of the -w wipe command - otherwise you would *have* to wipe any time you go from either enabled to disabled, or from disabled to enabled.
Sorry for any confusion my reply may cause.

Do I need to root my phone before manually updating using the OTA file?

speedyx2000 said:
Do I need to root my phone before manually updating using the OTA file?
Click to expand...
Click to collapse
No

Lughnasadh said:
No
Click to expand...
Click to collapse
Thank you for your quick answer!

I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers

virtyx said:
I'm starting to think 037 was pulled from the updator
I have several friends with h p6pros and only the ones who got their device early in the release received 037
I'm still on 036, however the updator no longer shows an update is available, edit: looks like Google only released 037 for select carriers
Click to expand...
Click to collapse
It was America only apparently. Everyone else will get it in December as normal

From Orange France is 036, from Google store is 037

Fingerprint improvement patch was U.S. and Japan only, if you really want it sideload it, it works perfectly fine