No KitKat Update? SOLVED

Search This thread
By:
Advanced…
M

Mon431

Senior Member
Feb 25, 2014
72
8
I think I figured out why people aren't receiving the update on the Verizon Samsung Galaxy S3.

If you all remember, the previous update (which allowed roaming in Canada) had a build number of JSS15J.I535VRUCNC1. That is the exact same build number for the update that brings us to Android 4.4.2. I am assuming that since the previous update has the same build number, when we check for updates, Verizon thinks we are on the latest update. This is just a guess that I thought I should have some light shed on.
 
landshark68

landshark68

Senior Member
Jan 13, 2011
1,265
710
Illinois
Mon431 said:
I think I figured out why people aren't receiving the update on the Verizon Samsung Galaxy S3.

If you all remember, the previous update (which allowed roaming in Canada) had a build number of JSS15J.I535VRUCNC1. That is the exact same build number for the update that brings us to Android 4.4.2. I am assuming that since the previous update has the same build number, when we check for updates, Verizon thinks we are on the latest update. This is just a guess that I thought I should have some light shed on.
Click to expand...
Click to collapse

The build number has nothing to do with it. This would not be the first time Verizon has had the wrong build number in one of these PDF documents. People aren't receiving the update because it's not rolling out yet. You can read in the software update instructions PDF linked below that users can manually update starting today if they do it over WiFi. So the normal OTA automatic roll out likely has not begun yet.

http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy_s3_instructions-6-19-14.pdf
 
M

Mon431

Senior Member
Feb 25, 2014
72
8
landshark68 said:
The build number has nothing to do with it. This would not be the first time Verizon has had the wrong build number in one of these PDF documents. People aren't receiving the update because it's not rolling out yet. You can read in the software update instructions PDF linked below that users can manually update starting today if they do it over WiFi. So the normal OTA automatic roll out likely has not begun yet.

http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy_s3_instructions-6-19-14.pdf
Click to expand...
Click to collapse

Oh okay, thanks. It was just a thought
 
SlimSnoopOS

SlimSnoopOS

Senior Member
Jan 29, 2011
8,052
3,348
Mon431 said:
I think I figured out why people aren't receiving the update on the Verizon Samsung Galaxy S3.

If you all remember, the previous update (which allowed roaming in Canada) had a build number of JSS15J.I535VRUCNC1. That is the exact same build number for the update that brings us to Android 4.4.2. I am assuming that since the previous update has the same build number, when we check for updates, Verizon thinks we are on the latest update. This is just a guess that I thought I should have some light shed on.
Click to expand...
Click to collapse

No. Bold emphasis is mine. Verizon simply hasn't pushed the update out. It has been 24 hours since the PDF was uploaded. Verizon has a tendency to leave typos in their PDFs. They have done so at least twice since the S3 was released. Verizon is not that ignorant to leave the build number as VRUCNC1.

To be even more technical, let's take it to AOSP names. Our "updated" PDF still reads "JSS15R" for the AOSP name, which is JellyBean 4.3. KitKat 4.4.2 is named "KOT49H" in AOSP. Logic states, this is a typo. Here's the Factory Images for Nexus devices, to use as a reference for AOSP names per OS.

Edit: Ninja'd by a country mile haha
 
  • Like
Reactions: landshark68
M

mpridmore816@gmail.com

Member
Mar 23, 2011
13
2
Update to 4.4.2 successful for me

I, too, was fooled by the NC1 update. What I forgot to do, which Tech Support (live chat) reminded me, was to check for an additional software update after the NC1 update. Sure enough, the 4.4.2 update was waiting to be downloaded and installed. The 4.4.2 baseband version/build number are I535OYUDNE1.

Oh--and it's rootable using Towelroot! Worked like a charm for me.
 
  • Like
Reactions: Mon431 and ShapesBlue
M

Mon431

Senior Member
Feb 25, 2014
72
8
mpridmore816@gmail.com said:
I, too, was fooled by the NC1 update. What I forgot to do, which Tech Support (live chat) reminded me, was to check for an additional software update after the NC1 update. Sure enough, the 4.4.2 update was waiting to be downloaded and installed. The 4.4.2 baseband version/build number are I535OYUDNE1.

Oh--and it's rootable using Towelroot! Worked like a charm for me.
Click to expand...
Click to collapse

Did it trip the counter?
 
M

mpridmore816@gmail.com

Member
Mar 23, 2011
13
2

Attachments

  • Screenshot_2014-06-20-21-20-11.png
    Screenshot_2014-06-20-21-20-11.png
    207.9 KB · Views: 193
You must log in or register to reply here.

Similar threads

Scott
  • Locked
[ROM][6/7/14] - CleanROM 8.2 -★| Clean! | Smooth! | Stable! | No Gimmicks! |★-
Replies
15K
Views
2M
Scott
Scott
open1your1eyes0
[GUIDE] No-Wipe Jelly Bean Factory Images ***Final Update: 6/1/13***
Replies
1K
Views
483K
M
madmatt5510
hedwig34
[Rom][d2vzw][d2lte][Official][Kitkat - 4.4.4] - Gummy - Nightly's
Replies
2K
Views
233K
madefree
madefree
Restola
[OFFICIAL]CM10.1.3 Release for D2VZW GSIII (OP updated 9/24/13)
Replies
3K
Views
540K
Ibuprophen
Ibuprophen
open1your1eyes0
  • Poll
[GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 5/29***
Replies
975
Views
509K
P
porkchopp420

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 2
    M
    mpridmore816@gmail.com
    Update to 4.4.2 successful for me

    I, too, was fooled by the NC1 update. What I forgot to do, which Tech Support (live chat) reminded me, was to check for an additional software update after the NC1 update. Sure enough, the 4.4.2 update was waiting to be downloaded and installed. The 4.4.2 baseband version/build number are I535OYUDNE1.

    Oh--and it's rootable using Towelroot! Worked like a charm for me.
    View
    1
    SlimSnoopOS
    SlimSnoopOS
    Mon431 said:
    I think I figured out why people aren't receiving the update on the Verizon Samsung Galaxy S3.

    If you all remember, the previous update (which allowed roaming in Canada) had a build number of JSS15J.I535VRUCNC1. That is the exact same build number for the update that brings us to Android 4.4.2. I am assuming that since the previous update has the same build number, when we check for updates, Verizon thinks we are on the latest update. This is just a guess that I thought I should have some light shed on.
    Click to expand...
    Click to collapse

    No. Bold emphasis is mine. Verizon simply hasn't pushed the update out. It has been 24 hours since the PDF was uploaded. Verizon has a tendency to leave typos in their PDFs. They have done so at least twice since the S3 was released. Verizon is not that ignorant to leave the build number as VRUCNC1.

    To be even more technical, let's take it to AOSP names. Our "updated" PDF still reads "JSS15R" for the AOSP name, which is JellyBean 4.3. KitKat 4.4.2 is named "KOT49H" in AOSP. Logic states, this is a typo. Here's the Factory Images for Nexus devices, to use as a reference for AOSP names per OS.

    Edit: Ninja'd by a country mile haha
    View
    1
    landshark68
    landshark68
    SlimSnoopOS said:
    Edit: Ninja'd by a country mile haha
    Click to expand...
    Click to collapse

    ;)
    View

New posts