Im just wondering if the official update will work better than the leaked version.
My problems are BSOD issues. Still getting them about once every 3 days.
chay03 said:
Im just wondering if the official update will work better than the leaked version.
My problems are BSOD issues. Still getting them about once every 3 days.
Click to expand...
Click to collapse
I'm reading more and more that the leaked updates are really the OTA Updates. They will start soon rolling out the 5.5.893 OTA and then progress through the others and you must be bone stock for the update to install. But the 5.8.894 will install on everyone's phone without regard to kernel/radio versions.
Geezer Squid said:
But the 5.8.894 will install on everyone's phone without regard to kernel/radio versions.
Click to expand...
Click to collapse
This is 180 degrees contrary to what we found trying to flash the leaked 5.8.894.
So maybe moto/vzw will alter the flash procedure to install this over everything else that was leaked?
RMD
In another forum, a user stated he had talked to a supervisor of Motorola's Technical help dept. and was told that the official update path is going via 5.5.886 --> 5.7.893 --> 5.8.894 --> ICS, and that the incremental updates released OTA through VZW will not have the pre-qual checks like the latest 5.8.894 does.
Take that with a grain of salt, though. If you read his posts, you'll understand.
Geezer Squid said:
I'm reading more and more that the leaked updates are really the OTA Updates. They will start soon rolling out the 5.5.893 OTA and then progress through the others and you must be bone stock for the update to install. But the 5.8.894 will install on everyone's phone without regard to kernel/radio versions.
Click to expand...
Click to collapse
Nobody has actually checked the MD5 sums yet (to my knowledge) so there is no way of knowing if the leaks are indeed the same. They are the same download size, but that does not mean that the OTA doesn't have edits not found in the leak.
The only way to know is to compare the MD5 sums.
Umm, I have checked the MD5 sums. The OTA that is already rolling out to people as of yesterday is the same 5.5.893 that we got from cheesecake back in the end of Sept or early October, whenever it was. According to another poster (see my reply 2 posts above) the upgrade path is 5.5.886 (stock) --> 5.5.893 --> 5.7.893 --> 5.8.894 --> ICS.
The hashes for both files are:
CRC32: 0EF1BF2A
MD5: 066E3C2393AEECB963FC950013E42A76
SHA-1: 304A2B479C80DB56DCA1A0D1E906511914D89100
I was not the first to check, another user here already posted that the MD5 sums matched, so I checked the old file versus the new one that just got pushed and all three match.
johnlgalt said:
Umm, I have checked the MD5 sums. The OTA that is already rolling out to people as of yesterday is the same 5.5.893 that we got from cheesecake back in the end of Sept or early October, whenever it was. According to another poster (see my reply 2 posts above) the upgrade path is 5.5.886 (stock) --> 5.5.893 --> 5.7.893 --> 5.8.894 --> ICS.
The hashes for both files are:
CRC32: 0EF1BF2A
MD5: 066E3C2393AEECB963FC950013E42A76
SHA-1: 304A2B479C80DB56DCA1A0D1E906511914D89100
I was not the first to check, another user here already posted that the MD5 sums matched, so I checked the old file versus the new one that just got pushed and all three match.
Click to expand...
Click to collapse
Okay cool, as I said, TO MY KNOWLEDGE, no one had checked the MD5 sums yet.
So thats cool that they are indeed the same thing. Concerning what the other poster is saying about the upgrade path, I'd take that with a huge grain of salt. Remember the source of the information, a moto rep. Who aren't really any better than VZW reps when it comes to actually knowing what's going on.
Plus it's already been said by a moto rep that the next update we'll be seeing is the ICS upgrade. See what I mean?
So has anyone actually been able to go from the 5.7.893 leak to 5.8.894? I can't get any info on this....
rduckwor said:
This is 180 degrees contrary to what we found trying to flash the leaked 5.8.894.
So maybe moto/vzw will alter the flash procedure to install this over everything else that was leaked?
RMD
Click to expand...
Click to collapse
I would say not that the 5.5.893 OTA is out, the leaked 5.8.894 can't be the final OTA. Since it only installs over stock 5.5.886 (kernel/radio/system) it will not install over the "new" stock of 5.5.893 since kernel and radio were updated. So who knows what that 5.8.894 leak really was, maybe it was an alternative to the 5.5.893?
Character Zero said:
I would say not that the 5.5.893 OTA is out, the leaked 5.8.894 can't be the final OTA. Since it only installs over stock 5.5.886 (kernel/radio/system) it will not install over the "new" stock of 5.5.893 since kernel and radio were updated. So who knows what that 5.8.894 leak really was, maybe it was an alternative to the 5.5.893?
Click to expand...
Click to collapse
Over at rootzwiki DroidTh3ory says the MD5 for the 5.5 is the same as 5.8.894. I'd link it but I'm in my phone. It's post number 481 in his Kin3tx thread.
Sent from my DROID BIONIC using Tapatalk
I think he might have meant that the 5.5.893 OTA had the same MD5 as the 5.5.893 leak because the 8.894 has a different radio (.03) than the OTA (.01).
I just updated my phone from the official update. I was running the leaked version of 5.5.893. So I unrooted yesterday with f4rever root and now to day I got the update. Everything when fine
Character Zero said:
I think he might have meant that the 5.5.893 OTA had the same MD5 as the 5.5.893 leak because the 8.894 has a different radio (.03) than the OTA (.01).
Click to expand...
Click to collapse
yeah, I think you are right. I've read over and over that the MD5 of the official OTA was the same as the leak 5.5.893. I actually hope that is the case.
It is.
Hashes for both files (I still have the one I downloaded as a leak at the end of October) and I compared it with the file that someone on here (user Terri, from her son's phone, IIRC) posted in one of these threads.
CRC32: 0EF1BF2A
MD5: 066E3C2393AEECB963FC950013E42A76
SHA-1: 304A2B479C80DB56DCA1A0D1E906511914D89100
Screenshot to prove it (Yes, I know someone out there can say "It could be doctored, the file could be the same one and I just renamed it, changed the date, blah blah blah" - well, these are the hashes from the original leaked file, easily verified from posts made around the net when the file was first found and posted from cheesecake, and anyone who *has* gotten the update but not yet applied it can manually DL their file and compare the hashes).
anyone know why dhackers released method doesn't restore ZUmocast with a stock 2.1 version ?
ZumoCast is actually in a different tree from the system tree. The R3L34S3D does not do the preinstall tree. Is that actually causing issues for people if ZumoCast is not there??
From the Updater script in the OTA update:
assert(apply_patch_check("/preinstall/app/com.motorola.zumocast", "27c7d3ba9de38230042dbc000b7cccb59c2aafaa", "73415ce67779b079ad83942f417992b02fbf31b8"));
Click to expand...
Click to collapse
Everything else prior to that is actually checking in /system not in /preinstall.
IIRC, when all is said and done, ZumoCast is not considered a system app (at least no on my TiBu). Yeah, just checked, and ZumoCast is not in read, so it is not indicated at a System app, per se.
Related
Hi! My Software-Version is 5.5.959, I heard about a version 5.6.890. What is the latest version that most people have and will I get OTA updates as my Droid 3 is rooted and I am using it in GSM-Mode in Germany?
Thanks
Additional info: Of course I changed some apk's names to bak in /system/app/ will this prevent me from getting updates, too?
To address both your questions -
1) You will be able to get updates on GSM mode - no problem. But only after they are published on Motorola servers - you will not be able to receive PUSH OTA from Verizon. Which is not end of the world since eventually you will get the update once it is released officially (forget about soak tests/etc).
2) Altering stuff in /system will 100% prevent you from getting update. You must restore content the way it was stock before trying to apply an update or it will fail to proceed due to checksum errors.
Thanks for your explanations
This is a Safestrap flashable ROM of an OTA leak that was pulled from the staging servers on 11/03.
[EDIT: 11/05] This ROM was kind of a test to see how well this would run w/o the kernal and BP. And to be honest, it's meh. The kernel + BP improvements in the actual OTA are probably what will make this better. I don't really recommend running this ROM for anything other than .. curiosity.
The Build ID is: 5.5.1_84_D3G-64
Download Here
The download link takes you to the "Android Downloads" section of my blog where you can grab the .zip file at the bottom in the "Other ROMs" section.
Instructions:
- Download the ROM
- Verify the MD5
- Place it on your SD card
- To run this you need to install Safestap which can also be downloaded from the same page on my blog. Please remove Koush's Bootstrap before installing Safestrap. 2 Bootstraps = Bad.
- Once Safestrap is installed, reboot and use the [ menu ] key during the splash screen to enter recovery.
- Make a backup, don't need the original system. We're going to use the /data partition in this backup in 4 steps.
- Turn on Safe System and wait for the swap process to finish
- Format /system
- Wipe data/cache
- Flash the MotoBlur ROM 5.7.894 .zip file
- Now do an advanced restore of "data" from the backup you made earlier. This should bring across all your apps from your primary ROM.
- Reboot and enjoy.
NOTE: The OTA leak also has a kernel and BP update which can't be included in a ROM like this.
I can release the actual OTA file if there's interest.
LEAK OTA WARNING: While using this ROM should be safe, flashing the actual OTA leak through stock recovery is a semi-dangerous decision as they may or may not release this update to the public for mass support. Do so at your own risk.
Kernel and BP update seems like a useful thing to have, can you post a link to the full OTA?
Why backup/restroe /dataļ¼that is no change.
thanks for all these goodies.
So if I understand this correctly.. a new update is coming?
DoubleYouPee said:
So if I understand this correctly.. a new update is coming?
Click to expand...
Click to collapse
yes but this may or may not be the final version of it. that is why it is recommended for now to install it this way so that you can preserve your original system to go back to if they dont release this version.
---------- Post added at 08:22 AM ---------- Previous post was at 08:16 AM ----------
Hashcode said:
This is a Safestrap flashable ROM of an OTA leak that was pulled from the staging servers on 11/03.
The Build ID is: 5.5.1_84_D3G-64
Download Here
The download link takes you to the "Android Downloads" section of my blog where you can grab the .zip file at the bottom in the "Other ROMs" section.
Click to expand...
Click to collapse
edit - grabbed wrong file
What does this OTA bring? Any ideas? What kernel changes are significant?
All I can say is I wonder how much Verizon techs know about the planned updates. Back at the end of September a day before the OTA rolled out I took in my phone, the tech was talking about an update that had just been released and another coming in November.
I pushed that there was no November update, and she must have it confused with the update that was about to roll out, she rolled her eyes at me and dropped it, but it turns out she may have been right.
Hash wouldn't be better with kernel intact in case of any incompatability?
-smc
Im running it right now and things seem fine. There are a few things I don't use so can't confirm everything works but, my download speeds have been normal finally if not excellent. Im about to test that theory here in a minute cause I get poor signal a work. Will report back later.
Sent from my DROID3 using XDA App
I'm guessing applying the OTA would also unroot and patch the exploit we use to gain root?
One of the biggest failings of this recovery method is we are still using the boot image's kernel, as opposed to the recovery's own kernel. Will this cause a problem for us to update the boot image? Isn't it all loaded into memory on startup by the bootloader anyway? Is the boot image touched at all after that?
I guess, worst case, we could apply the OTA, and then replace system with the 5.6.890 version using fastboot - assuming they don't change the signing keys to prevent downgrading...
slvrarrow said:
What does this OTA bring? Any ideas? What kernel changes are significant?
Click to expand...
Click to collapse
i used it for half a day and it seemed worse than current stock for radio and camera. i was dropping 3G a lot and the camera seemed even slower if that is possible.
went to Liberty and that is running perfect
Ok my signal went back to crap again. But it was crap before I installed so it might be the towers in my area.
Sent from my DROID3 using XDA App
Heh, sorry guys. I had forgotten to post the actual OTA for those that felt the need to apply it.
I believe this OTA is harder to root (current method does not work). So you'll need to have a "root keeper" method installed before applying it or risk having to do a lot of work to get root back (downgrade via fastboot, etc).
Once I get back to a computer I'll put the OTA .zip up (probably a few hours).
But you've been warned!
Can't you just SBF back to 890?
root keeper would be the best way but there's also zergRush it works works with the xt883 2.35 so i've read or me883 what ever its called
Or the loadpreinstalls.sh trick, not sure what's been patched.
Got 5.1.1 system update message but I'm on att? And when I check the list of stock android images, there is no 5.1.1 for att. Is it possible they are pushing ota's before they make the new image available to developers? Sounds odd to me.
I'm also rooted (but with stock recovery), so it sounds like I can't do the ota? I also have a Fi request out there. Or can I? I'm rooted but I haven't changed any system files. Can I do the ota rooted but with stock recovery and unmodified system files?
Should I unroot and try to get the ota?
-peter
If I'm not mistaken they normally do otas before images. You might be the first one to get this one. Get the url.
pcrussell50 said:
Got 5.1.1 system update message but I'm on att? And when I check the list of stock android images, there is no 5.1.1 for att. Is it possible they are pushing ota's before they make the new image available to developers? Sounds odd to me.
I'm also rooted (but with stock recovery), so it sounds like I can't do the ota? I also have a Fi request out there. Or can I? I'm rooted but I haven't changed any system files. Can I do the ota rooted but with stock recovery and unmodified system files?
Should I unroot and try to get the ota?
-peter
Click to expand...
Click to collapse
Buff McBigstuff said:
If I'm not mistaken they normally do otas before images. You might be the first one to get this one. Get the url.
Click to expand...
Click to collapse
AT&T is pushing LMY47Z via OTA. Factory image file has been available for some time on the Google website.
Buff McBigstuff said:
If I'm not mistaken they normally do otas before images. You might be the first one to get this one. Get the url.
Click to expand...
Click to collapse
hmmm, not sure how to get the url. the message was a system message, not an email with a link. the message says "Android 5.1.1 System Update Downloaded and Verfied..." i'm rooted with root permissions on ES file explorer, i can look for the ota but i'm not sure where they are kept after they are downloaded.
-peter
cam30era said:
AT&T is pushing LMY47Z via OTA. Factory image file has been available for some time on the Google website.
Click to expand...
Click to collapse
This was cut and pasted from the google website list of images about a minute and a half ago. can you tell me which one is 5.1.1 for att:
5.0 (LRX21O) Link af4520213c1a3e2b3dd811aef030b87b e028f5eab0952d0df60c63d6095b56c1c6f8e474
5.0.1 (LRX22C) Link a95f291164b5b438b5fc9e77c222d703 ff173fc66eca5a27b34ae28a9b69f9ad7f4d3b80
5.1.0 (LMY47D) Link 4d99d16bae3c5a638268731a5d27062e 6c44d4021142ffaa2197fb1308996a8846a79e26
5.1.0 (LMY47E) Link 7c50606b7d68ddd1b8a81d544ec59aff cf3131641c2bda2eba54bcc0108ce0325327f58e
5.1.0 (LMY47I) Link d6e750e58938de3b8516a4718c491d9c c8afc588e44ec087e8b98c1d6ed3ed565a9b9644
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
Click to expand...
Click to collapse
cuz if LMY47Z is for AT&T too, the "(For Sprint, USC ONLY)" bit was making me think otherwise.
-Peter
pcrussell50 said:
This was cut and pasted from the google website list of images about a minute and a half ago. can you tell me which one is 5.1.1 for att:
Code:
5.0 (LRX21O)Linkaf4520213c1a3e2b3dd811aef030b87be028f5eab0952d0df60c63d6095b56c1c6f8e474
5.0.1 (LRX22C)Linka95f291164b5b438b5fc9e77c222d703ff173fc66eca5a27b34ae28a9b69f9ad7f4d3b80
5.1.0 (LMY47D)Link4d99d16bae3c5a638268731a5d27062e6c44d4021142ffaa2197fb1308996a8846a79e26
5.1.0 (LMY47E)Link7c50606b7d68ddd1b8a81d544ec59affcf3131641c2bda2eba54bcc0108ce0325327f58e
5.1.0 (LMY47I)Linkd6e750e58938de3b8516a4718c491d9cc8afc588e44ec087e8b98c1d6ed3ed565a9b9644
5.1.0 (For T-Mobile ONLY) (LMY47M)Link0469ca2018c923498cc603baae4fd6485228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z)Linkc8fe950ad9e861120a1074825b92cfba33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E)Link9ea32a7ff1751afa2a16214ac23ef000b542b88a0ad478110f9f111dd32b62a1cb65b9d5
-Peter
Click to expand...
Click to collapse
There is only one LMY47Z. It says "For Sprint and USC only". Same build AT&T is pushing via OTA.
At&t rolled out the ota for at&t the zip is already available on xda for a few days now I sideloaded it two days ago. The factory image has not yet been posted on Google's site.
Edit: I wouldn't use the image that is posted on Google because even though it has the same build number the boot.img and radio are most likely different.
manup456 said:
At&t rolled out the ota for at&t the zip is already available on xda for a few days now I sideloaded it two days ago. The factory image has not yet been posted on Google's site.
Edit: I wouldn't use the image that is posted on Google because even though it has the same build number the boot.img and radio are most likely different.
Click to expand...
Click to collapse
I installed the OTA. Fastboot flashed back to 47D. Then after a few days flashed the 47Z factory image. They are identical. Same boot.img and same radio.
cam30era said:
I installed the OTA. Fastboot flashed back to 47D. Then after a few days flashed the 47Z factory image. They are identical. Same boot.img and same radio.
Click to expand...
Click to collapse
So you have this radio?
Edit: I ask because why would they put for sprint only on google's image download site. Kinda makes no sense to me at all, but you could be 100% correct I never flashed the image files off google's site.
manup456 said:
So you have this radio?
Edit: I ask because why would they put for sprint only on google's image download site. Kinda makes no sense to me at all, but you could be 100% correct I never flashed the image files off google's site.
Click to expand...
Click to collapse
Yes, same 101R radio. No idea why Google identifies things like they do.
i am rooted, but with stock recovery and have not edited any system files. can i go ahead and install this OTA, since it's already downloaded and verified according to the system updater?
-peter
pcrussell50 said:
i am rooted, but with stock recovery and have not edited any system files. can i go ahead and install this OTA, since it's already downloaded and verified according to the system updater?
-peter
Click to expand...
Click to collapse
you are rooted. just that in itself changes system files silly :silly:
cam30era said:
AT&T is pushing LMY47Z via OTA. Factory image file has been available for some time on the Google website.
Click to expand...
Click to collapse
simms22 said:
you are rooted. just that in itself changes system files silly :silly:
Click to expand...
Click to collapse
i had a feeling... thanks for confirming. i thought maybe just a root without any other changes might be like renaming the att splash so it doesn't happen on bootup.
-peter
AT&T 5.1.1 system update OTA, whats preventing the install?
manup456 said:
So you have this radio?
Edit: I ask because why would they put for sprint only on google's image download site. Kinda makes no sense to me at all, but you could be 100% correct I never flashed the image files off google's site.
Click to expand...
Click to collapse
pcrussell50 said:
Got 5.1.1 system update message but I'm on att? And when I check the list of stock android images, there is no 5.1.1 for att. Is it possible they are pushing ota's before they make the new image available to developers? Sounds odd to me.
I'm also rooted (but with stock recovery), so it sounds like I can't do the ota? I also have a Fi request out there. Or can I? I'm rooted but I haven't changed any system files. Can I do the ota rooted but with stock recovery and unmodified system files?
Should I unroot and try to get the ota?
-peter
Click to expand...
Click to collapse
I've had the 5.1.1 system update notice for a few days and finally clicked "install" - it counts down to reboot, then instead of rebooting it says "system up to date" with the current time stamp.
I am rooted, unencrypted, Franco kernel, stock 5.1 ROM.
I assume the root and/or un-encryption is somehow preventing the system updates? Is there any way to stop the system update notification?
Thanks.
I took a dive and did the update. My phone is now in a wonky state. Its still at 5.1. Every time I power on my phone, it does the applications countdown like its indexing all the apps.
(Unencrypted, ElementalX, 5.1)
garyHal said:
I took a dive and did the update. My phone is now in a wonky state. Its still at 5.1. Every time I power on my phone, it does the applications countdown like its indexing all the apps.
(Unencrypted, ElementalX, 5.1)
Click to expand...
Click to collapse
Do you mean you tried to install the OTA? If so, it won't install for you. You have to have be stock (encrypted kernel, no root, stock recovery). Your best option is to fastboot flash the factory image.
cam30era said:
Do you mean you tried to install the OTA? If so, it won't install for you. You have to have be stock (encrypted kernel, no root, stock recovery). Your best option is to fastboot flash the factory image.
Click to expand...
Click to collapse
Yeah, I tried to install the OTA. I heard it wasn't going to work. I just expected the "verification" step to fail before it tried to install. Apparently something fubar'd.
How do we get rid of the dang system update message?
Sent from my Nexus 6 using Tapatalk
ryan141 said:
How do we get rid of the dang system update message?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I did it by long pressing on the notification and selecting 'i' which took me to the Google Play services App notifications. Then I selected Block and the notification went away.
thrasher9 said:
I did it by long pressing on the notification and selecting 'i' which took me to the Google Play services App notifications. Then I selected Block and the notification went away.
Click to expand...
Click to collapse
Doesn't that kill all of the google play services notifications?
So the lollipop update failed on my phone, so I flashed back to stock. Now the update won't show up. Is this normal, did l get pushed to the end of the line for the update?
EYEramid said:
So the lollipop update failed on my phone, so I flashed back to stock. Now the update won't show up. Is this normal, did l get pushed to the end of the line for the update?
Click to expand...
Click to collapse
Same thing happened here.
colarosen said:
Same thing happened here.
Click to expand...
Click to collapse
Im gonna try reflashing back to stock again, in a couple of days. If you figure it out let me know
Will do.
Just to add some other info... current build is KXA21.12-L1.26.1, files obtained from the motorola support site, I wiped all data when I flashed. Now when checking for updates I am told the software is up to date.
colarosen said:
Will do.
Just to add some other info... current build is KXA21.12-L1.26.1, files obtained from the motorola support site, I wiped all data when I flashed. Now when checking for updates I am told the software is up to date.
Click to expand...
Click to collapse
That's exactly what I did too
ok. So if you obtained the file VZW_212.55.26.ghost_verizon.Verizon.en.US from the moto support site, it will lead you to build KXA21.12-L1.26.1 and will not lead you to any further updates. You must flash build KXA21.12-L1.26 obtained from VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml This file is posted in a number of threads; still - - - http://motofirmware.center/files/category/11-moto-x-1st-generation/
Side note-- I happened to have had this file from last year when I flashed it to get to 4.4.4 originally. In the time between then and now, I obtained the stock files directly from moto support- just to have on hand. When my initial attempts at taking 5.1 failed, I assumed the files from moto support were identical to the ones I had and went ahead and used them to flash to stock. Yet apparently the images from moto support will not lead you to further upgrades (at least at this time). Moral of the story, you must start from L1.26 and NOT L1.26.1. See http://forum.xda-developers.com/showpost.php?p=62839998&postcount=518
It will now go through all three ota's (the first one brings you to L1.26.3 -- this is where we started--- the build after the ota earlier this summer, then the final two to 5.1).
colarosen said:
ok. So if you obtained the file VZW_212.55.26.ghost_verizon.Verizon.en.US from the moto support site, it will lead you to build KXA21.12-L1.26.1 and will not lead you to any further updates. You must flash build KXA21.12-L1.26 obtained from VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml This file is posted in a number of threads; still - - - http://motofirmware.center/files/category/11-moto-x-1st-generation/
Side note-- I happened to have had this file from last year when I flashed it to get to 4.4.4 originally. In the time between then and now, I obtained the stock files directly from moto support- just to have on hand. When my initial attempts at taking 5.1 failed, I assumed the files from moto support were identical to the ones I had and went ahead and used them to flash to stock. Yet apparently the images from moto support will not lead you to further upgrades (at least at this time). Moral of the story, you must start from L1.26 and NOT L1.26.1. See http://forum.xda-developers.com/showpost.php?p=62839998&postcount=518
It will now go through all three ota's (the first one brings you to L1.26.3 -- this is where we started--- the build after the ota earlier this summer, then the final two to 5.1).
Click to expand...
Click to collapse
Cool, I'll try this tonight, thanks
Why am I not getting it? I checked for system updates and it says I am already up to date, but everyone is saying Oreo is out now.
I have crc5. So, somehow I have an even newer version. I would guess we need to go back to the last Verizon Android v7 to have the OTA work.
Good to know. Guess I need to find a firmware download for it and flash it manually with odin
GeorgeNav said:
Good to know. Guess I need to find a firmware download for it and flash it manually with odin
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-galaxy-s8/how-to/official-vzw-sm-g950u-g950usqu2crb9-t3765909
I could not find an OTA to go from CRA5 to the official CRB9. However, above is a link to the official firmware from verizon.
BBB
Icons Posted