Question RE : SD1A.210817.037 - Google Pixel 6 Pro

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

Related

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:

Android OS is sucking up all my mobile data!

Got to work this morning to find out I had no mobile data left (attached image). I thought, how strange, yesterday I'd had about ~1GB usage out of my 4GB available, I of course immediately when and looked to see what had used it all and Android OS was at the top with 2.13GB (WTF?).
This also isn't the first time this has happened, I had the same last month. Can someone please explain what is going on because I know for damn sure I've not used all that, I only browsed a few web pages this morning.
Sent from my Pixel XL using Tapatalk
Stop automatic backup
thenessus said:
Stop automatic backup
Click to expand...
Click to collapse
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Sent from my Pixel XL using Tapatalk
pairedprototype said:
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Click to expand...
Click to collapse
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Use Data Saver in settings, works a treat
TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.
Just switch to the unlimited data plan..problem solved
TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
alluringreality said:
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.
Click to expand...
Click to collapse
You are indeed correct, I am due an update, however, I'm not rooted currently although, my bootloader is unlocked as I've been assisting with getting Magisk working on stock for Pixel devices.
And what kind of idiot developer/team thought downloading OS updates over mobile data without question was okay!? I've now got to go for 2 weeks without, I'm royally p*ssed about it. Guess I'd better flash the new update then while I have a (non-cellular) internet connection.
I remember when Google targeted power users with Nexus devices, I guess this is not entirely true for Pixel devices. Big boys like to do what they want, even if that means staying on a particular version of Android because we might be testing things... I'd rather not have OS updates forced down my throat, it's the same thing that bugs me with Windows 10.
lucky_strike33 said:
Just switch to the unlimited data plan..problem solved
Click to expand...
Click to collapse
If you're willing to pay the extra, sure thing!
You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data
lucky_strike33 said:
You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data
Click to expand...
Click to collapse
That's what I usually do! Just not had the time to do it recently.
this is caused by update downloading and failing over and over. I went into the dev options and turned off the auto update but it did not work. I had to update the phone manually and now its fine. I think after rooting the phone and going back to stock rom this happens.
IDK man, I was rooted and was pulling like 10gb+. Flashed stock via adb and I think it's still doing it. Project fi.
This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.
FrostyOrDie said:
This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.
Click to expand...
Click to collapse
When you returned to stock did you get to the latest version?
TonikJDK said:
When you returned to stock did you get to the latest version?
Click to expand...
Click to collapse
No. This all happened since returning to stock. Today I sideloaded the August update with adb and my phone says it's on the current version finally. It seems the support people at project fi are clueless for the most part. You have to do everything yourself but they will at least credit your account for the data used by Android os if you call them and tell them what's up. They want screen shots of the data usage. So save one before you go messing with stuff

Play Store FC trying to buy app

Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
mac796 said:
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
Click to expand...
Click to collapse
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
mlin said:
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
Click to expand...
Click to collapse
It's very strange happens on both my pixels so must be a bug on googles side maybe.
mac796 said:
It's very strange happens on both my pixels so must be a bug on googles side maybe.
Click to expand...
Click to collapse
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
mlin said:
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
Click to expand...
Click to collapse
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
mac796 said:
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
Click to expand...
Click to collapse
I flashed the factory image on release day and OTA'd to September security patch. No dice.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So it's still not working for you? Maybe I'll just wait till next update then.
mac796 said:
So it's still not working for you? Maybe I'll just wait till next update then.
Click to expand...
Click to collapse
Nope, still not working. I'll let you know if my efforts tomorrow are successful.
mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
mac796 said:
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
Click to expand...
Click to collapse
Lol, weird. So just reflash before each app purchase and you should be good!
mlin said:
Lol, weird. So just reflash before each app purchase and you should be good!
Click to expand...
Click to collapse
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
mac796 said:
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
Click to expand...
Click to collapse
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
mlin said:
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
Click to expand...
Click to collapse
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
mac796 said:
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
Click to expand...
Click to collapse
Did you wipe data as well?
mlin said:
Did you wipe data as well?
Click to expand...
Click to collapse
Yes I wiped everything except internal storage
mac796 said:
Yes I wiped everything except internal storage
Click to expand...
Click to collapse
I did wipe internal storage, though hard to say if that difference made it work. I'd be curious to hear if you do get it working eventually or if you find a different solution. Best of luck, hope you get it resolved eventually though I get the appeal of being unable to buy apps lol.

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/

Question issue with AA incremental update

I am on 11.2.4.4 (AA) and after reading about the success others were having I decided to take an incremental update, which shows up as 11.2.6.6 (unlocked/verizon). I followed the instructions found in many places, which consisted of restoring image in magisk, taking the incremental update, when finished I did not reboot, and then installed magisk to inactive slot. upon reboot my system still shows 11.2.4.4, and in the system update page it is still asking me to reboot, as if I needed to hit the system restart button in system update, which is very odd. also, I was running omega kernel, and after installing the update the kernel is back to stock, but for some reason the system has not updated and is still stuck on 11.2.4.4, and still has system reboot button on update setting screen. has anyone ran into this issue, and does anyone know how I should proceed? I am afraid if I hit reboot on the update setting screen that I will have some issue. I have also rebooted multiple times, yet the system has not updated. any help with this issue will be greatly appreciated!
When rooted you need the full update, not an incremental
You need to install 11.2.4.4 full update again in local update then the incremental will install
ryantf420 said:
You need to install 11.2.4.4 full update again in local update then the incremental will install
Click to expand...
Click to collapse
I've never heard of this method, where did you do this yourself and it worked? reinstalling a full update via local update actually forced your incremental update to take? also, how would this work when I would be installing things to different slots?
avid_droid said:
Yeah that don't work. Didn't reinstall but I wiped and tried again. Still failed. Even edited craznazn package to fix model number and still that didn't work. Back to BA and have no issues updating
Click to expand...
Click to collapse
so you are basically in the same boat as me? an incremental update is not taking? yeah thanks for reporting that, I was skeptical about that method, but I'm thinking I'll try it anyway. if not, guess I'll have to wait until AA releases a full update other than 11.2.4.4
thirtythr33 said:
so you are basically in the same boat as me? an incremental update is not taking? yeah thanks for reporting that, I was skeptical about that method, but I'm thinking I'll try it anyway. if not, guess I'll have to wait until AA releases a full update other than 11.2.4.4
Click to expand...
Click to collapse
Maybe you can download the full version of the 11 .2.4.4 from here and start over. The custom kernel combined with root may have messed it up. Happy modding!
Edit: only take full updates when rooted.
Nathan.7118391 said:
Maybe you can download the full version of the 11 .2.4.4 from here and start over. The custom kernel combined with root may have messed it up. Happy modding!
Edit: only take full updates when rooted.
Click to expand...
Click to collapse
I know the thing is up until this point I've always went for full os updates, never incremental, but after reading many posts about other members taking incremental updates successfully, (restore images in magisk - take update - don't reboot - then install magisk to inactive slot) I decided to try it myself, and I should have never bothered. I'll just wait until a new full update comes out for AA and never bother with incremental again. thing is I followed instructions to the T, yet it didn't work, so I don't know how others have been successful with this.
avid_droid said:
Yeah that don't work. Didn't reinstall but I wiped and tried again. Still failed. Even edited craznazn package to fix model number and still that didn't work. Back to BA and have no issues updating
Click to expand...
Click to collapse
Yeah it does work
Or I wouldn't have gave advice
ota 11.2.4.4 twice, and 11.2.7.7 will install....
ryantf420 said:
Yeah it does work
Or I wouldn't have gave advice
ota 11.2.4.4 twice, and 11.2.7.7 will install....
Click to expand...
Click to collapse
so since the incremental update I tried to apply is somehow "stuck" you are saying to local update 11.2.4.4 and then upon reboot 11.2.6.6 will be installed? and are you saying to ota 11.2.4.4 twice because of the slot I am on and would need to get back to that slot for the incremental update to apply? I am willing to try this but I've never heard of it, but hey if it works man then I am grateful
avid_droid said:
Don't get your panties in a bunch with that mad face haha. Just found it odd. I also wasn't rooted for the other gentlemen who said about root.was completely unrooted and fresh system update from BA to AA. Since there isn't a huge difference between 11.2.7.7 and 11.2.6.6 I'll just wait it out. Thanks guys
Click to expand...
Click to collapse
all good hdr is add to video but that's basically it. but method does work, did it on both my 9pro's
Hi, I just wanted to add that on the AA version(unlocked US version from OnePlus) the boot image have to match for the inc to install. Also I'm using props hide module and to manually select the OTA this has to be disabled (reverted). I ran into some issues at first but hopefully have it figured out.
So I decided to go to the EU version of the OS.
I did that on my 7 Pro and didn't have any issues.
So I'm on 11.2.6.6, running on Verizon with no issues.
Here is my theory on why people are failing OTA. I think maybe their A and B slots dont have matching content before they OTA. Try using the lineageOS script to duplicate the active to the inactive slots first. I'm curious if that does the trick.
dkcats3 said:
Here is my theory on why people are failing OTA. I think maybe their A and B slots dont have matching content before they OTA. Try using the lineageOS script to duplicate the active to the inactive slots first. I'm curious if that does the trick.
Click to expand...
Click to collapse
yes local update needs to be down twice...
ryantf420 said:
yes local update needs to be down twice...
Click to expand...
Click to collapse
Would I have to wipe everything if I'm already on 6.6?
ryantf420 said:
yes local update needs to be down twice...
Click to expand...
Click to collapse
I decided to take your advice bro but I'm getting update installation error. I've tried a few times now and the full 11.2.4.4 I have will not install. so I'm unable to even install the full ota, did this happen to you? thing is the 11.2.6.6 incremental ota that didn't install is no longer in system update, now 11.2.7.7 is, so I don't know what is exactly going on bc my system still reports 11.2.4.4. any help is appreciated

Categories

Resources