[REF] Nexus 4 Stock OTA URLs

Search This thread

oldblue910

Senior Member
Jan 1, 2011
4,248
3,156
Durham, NC
Below are a list of all known Nexus 4 OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file on my website, http://randomphantasmagoria.com, in case Google pulls it down in the future.

OTA updates - occam (Worldwide GSM/HSPA+)
Current firmware: Android 5.1.1, Build LMY48T

LMY48T from LMY48M - https://android.googleapis.com/pack...ac2c8b445.signed-occam-LMY48T-from-LMY48M.zip
----------------------------------------------------
LMY48M from LMY48I - https://android.googleapis.com/pack....signed-occam-LMY48M-from-LMY48I.b84572d4.zip
----------------------------------------------------
LMY48I from LMY47V - https://android.googleapis.com/pack....signed-occam-LMY48I-from-LMY47V.d49d67c5.zip
----------------------------------------------------
LMY47V from LMY47O - http://android.clients.google.com/p....signed-occam-LMY47V-from-LMY47O.050356b6.zip
----------------------------------------------------
LMY47O from LRX21T - http://android.clients.google.com/p....signed-occam-LMY47O-from-LRX21T.37c27ea7.zip
LMY47O from LRX22C - http://android.clients.google.com/p....signed-occam-LMY47O-from-LRX22C.e6789b4e.zip
----------------------------------------------------
LRX22C from KTU84P - http://android.clients.google.com/p....signed-occam-LRX22C-from-KTU84P.eef0995e.zip
LRX22C from LRX21T - http://android.clients.google.com/p....signed-occam-LRX22C-from-LRX21T.e93b20be.zip
----------------------------------------------------
LRX21T from KTU84P - http://android.clients.google.com/p....signed-occam-LRX21T-from-KTU84P.1c6f10c3.zip
----------------------------------------------------
KTU84P from KTU84L - http://android.clients.google.com/p....signed-occam-KTU84P-from-KTU84L.50b64331.zip
----------------------------------------------------
KTU84L from KOT49H - http://android.clients.google.com/p....signed-occam-KTU84L-from-KOT49H.61a9ce8d.zip
----------------------------------------------------
KOT49H from KRT16O - http://android.clients.google.com/p....signed-occam-KOT49H-from-KRT16O.250326d3.zip
KOT49H from KRT16S - http://android.clients.google.com/p....signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip
KOT49H from KOT49E - http://android.clients.google.com/p....signed-occam-KOT49H-from-KOT49E.0ec632f5.zip
----------------------------------------------------
KOT49E from KRT16S - http://android.clients.google.com/p....signed-occam-KOT49E-from-KRT16S.0896df95.zip
----------------------------------------------------
KRT16S from JWR66Y - http://android.clients.google.com/p....signed-occam-KRT16S-from-JWR66Y.d1b99704.zip
KRT16S from KRT16O - http://android.clients.google.com/p....signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
----------------------------------------------------
JWR66Y from JOP40C - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JOP40C.3b0cb3ad.zip
JWR66Y from JOP40G - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JOP40G.bc81f98c.zip
JWR66Y from JDQ39 - http://android.clients.google.com/p...2.signed-occam-JWR66Y-from-JDQ39.c4df9c73.zip
JWR66Y from JDQ39E - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JDQ39E.0327fb70.zip
JWR66Y from JWR66N* - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JWR66N.a33d7c5b.zip
JWR66Y from JWR66V - http://android.clients.google.com/p....signed-occam-JWR66Y-from-JWR66V.6136cbe0.zip
----------------------------------------------------
JWR66V from JOP40C - http://android.clients.google.com/p....signed-occam-JWR66V-from-JOP40C.f6938a0e.zip
JWR66V from JOP40G - http://android.clients.google.com/p....signed-occam-JWR66V-from-JOP40G.fad3efe5.zip
JWR66V from JDQ39 - http://android.clients.google.com/p...1.signed-occam-JWR66V-from-JDQ39.ebc8bad2.zip
JWR66V from JDQ39E - http://android.clients.google.com/p....signed-occam-JWR66V-from-JDQ39E.7e768b10.zip
JWR66V from JWR66N* - http://android.clients.google.com/p....signed-occam-JWR66V-from-JWR66N.fe92fc9f.zip
----------------------------------------------------
JDQ39 from JOP40C - http://android.clients.google.com/p...4.signed-occam-JDQ39-from-JOP40C.ebd2f14a.zip
JDQ39 from JOP40D - http://android.clients.google.com/p...4.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip
JDQ39 from JOP40G - http://android.clients.google.com/p...d.signed-occam-JDQ39-from-JOP40G.82917390.zip
JDQ39 from JDQ23* - http://android.clients.google.com/p...99.signed-occam-JDQ39-from-JDQ23.831bb496.zip
----------------------------------------------------
JOP40D from JVP15L* - http://android.clients.google.com/p....signed-occam-JOP40D-from-JVP15L.8c8adc7f.zip
JOP40D from JVP15Q - http://android.clients.google.com/p....signed-occam-JOP40D-from-JVP15Q.405bebc7.zip
JOP40D from JOP24G* - http://android.clients.google.com/p....signed-occam-JOP40D-from-JOP24G.ae1e42c5.zip
JOP40D from JOP40C - http://android.clients.google.com/p....signed-occam-JOP40D-from-JOP40C.625f5f7c.zip
----------------------------------------------------
JOP40C from JVP15Q - http://android.clients.google.com/p....signed-occam-JOP40C-from-JVP15Q.609c838b.zip

* JVP15L, JOP24G, JDQ23, and JWR66N were prerelease or testing builds that never appeared on devices sold to the general public.


SPECIAL THANKS
deathpod
kevin@TeslaCoil
xdatastic
bongostl
thephantom
drmclove69
efrant
GreenSGS
VivaErBetis
TheManii
qorron
El Daddy
^ms
EthanFirst
dpjohnston
Displaxx
Tang034
 
Last edited:

Jamal Ahmed

Senior Member
Jun 23, 2012
942
979
Thanks :)
Glad to have you here:)
So basically were just need to provide the new build number and About Phone info right? :)
 

oldblue910

Senior Member
Jan 1, 2011
4,248
3,156
Durham, NC
That site doesn't have links to the OTA packages but yes, that would work for the factory images (though I guess it's not direct link to the zip file).

Plus, I mirror the files. Every time there's an OTA, Google removes the old factory images and replaces them with the new ones. My website doubles as an archive.

Sent from my Galaxy Nexus using Tapatalk 2
 

oldblue910

Senior Member
Jan 1, 2011
4,248
3,156
Durham, NC
Hi everyone. Since the N4 goes on sale tomorrow, I need someone to volunteer to grab some info for me from a brand new N4. This info will need to be obtained as soon as you power up the device, before you apply any OTA updates or anything else. Here's what I'll need from the device:

1. The bootloader version. (Found only on the main bootloader screen, you'll have to reboot into the bootloader to see it)
2. Android version and build # (From settings)
3. Baseband version (From settings)
4. Firmware and device name. To get these two pieces of info, open /system/build.prop in a text editor and post the values of ro.product.name and ro.product.device.

Again, please do this as soon as you power on the device, before applying any OTA that may be available out of the box! Thanks much for your help!
 
Last edited:

Richieboy67

Senior Member
Dec 10, 2011
2,073
362
CT
www.talkdevelopment.net
If I get mine before you have the info I am happy to help. I will be ordering as soon as available and will be shipping next day if possible. I live on the east coast though so you may already have it by then..

Sent from my Nexus 7 using xda app-developers app
 

oldblue910

Senior Member
Jan 1, 2011
4,248
3,156
Durham, NC
Hi everyone. Since the N4 goes on sale tomorrow, I need someone to volunteer to grab some info for me from a brand new N4. This info will need to be obtained as soon as you power up the device, before you apply any OTA updates or anything else. Here's what I'll need from the device:

1. The bootloader version. (Found only on the main bootloader screen, you'll have to reboot into the bootloader to see it)
2. Android version and build # (From settings)
3. Baseband version (From settings)
4. Firmware and device name. To get these two pieces of info, open /system/build.prop in a text editor and post the values of ro.product.name and ro.product.device.

Again, please do this as soon as you power on the device, before applying any OTA that may be available out of the box! Thanks much for your help!

Just a reminder. If any of you guys in the UK can provide this information before applying any OTA updates, I'd really appreciate it. Also, if you get an OTA to JOP40C, if you could get the link for it, that'd be awesome too!
 

oldblue910

Senior Member
Jan 1, 2011
4,248
3,156
Durham, NC
Anyone? At this point, all I need to know is this: Did your phone come pre-loaded with JOP40C? Or did it come with JOP24G and then you had to OTA to JOP40C?
 
Last edited:

oldblue910

Senior Member
Jan 1, 2011
4,248
3,156
Durham, NC
The images are already posted here. You should easily be able to download them and see what the radio and bootloader version are, and extract the build.prop.

Yes, but I have reason to believe that the phone actually ships with JOP24G, not JOP40C. I want the information from JOP24G if the phone indeed ships with it. I have most of the information for JOP24G...the only thing I don't know is the bootloader version. Also, if the phone ships with JOP24G, I'm hoping someone will be able to provide the OTA link for JOP40C from JOP24G.
 

oldblue910

Senior Member
Jan 1, 2011
4,248
3,156
Durham, NC
OK, judging by YouTube unboxing videos, I can definitely verify that it does NOT ship with JOP40C out of the box. It ships with some earlier build. Nobody seems to scroll down so I can see the build number, but I can tell it's an older build by the baseband. It ships with 1700.24, but JOP40C uses 1700.33.

So, when somebody gets their N4, if you wouldn't mind, please (before installing any OTAs) do the following for me:

1. Reboot the phone into bootloader mode and tell me the bootloader version. It may be MAKOZ10L but I'm not sure so I'd like confirmation.
2. Android build number.
3. When you get the OTA notification to update to JOP40C, could you check logcat before applying the update and get the URL to the OTA file?

I would normally do this myself, except I won't be owning a Nexus 4 straight away since I'm on Verizon.

Thanks!
 

thatguyitsme

Senior Member
Mar 3, 2009
97
15
Bootlader version. makoz10f

Build # JVP15Q

Baseband M9615A-CEFWMAZM-2.0.1700.24

Phone already had OTA update ready to install by the time I logged in and got this info, but it won't reboot and install update. How can I get the URL it downloaded from?


Sent from my Nexus 4 using xda premium
 
Last edited:

oldblue910

Senior Member
Jan 1, 2011
4,248
3,156
Durham, NC
Bootlader version. makoz10f

Build # JVP15Q

Baseband M9615A-CEFWMAZM-2.0.1700.24

Phone already had OTA update ready to install by the time I logged in and got this info, but it won't reboot and install update. How can I get the URL it downloaded from?


Sent from my Nexus 4 using xda premium

THANK YOU!!

as far as the OTA, not sure what's up there, but if you want to work with me on getting the filename for the OTA, I'd really appreciate it. Are you familiar with ADB and the developer options (sorry if that's an insulting question, but I need to know what instructions to give you. ;)
 

oldblue910

Senior Member
Jan 1, 2011
4,248
3,156
Durham, NC
Basically, you'll need to turn on developer options on your phone by going into Settings | About Phone and tapping the build number a few times.

Once that's done, go to Settings | Developer Options and turn on USB debugging.

Once that's done, hook the phone up to your computer via USB, open a command prompt. Do the following command:

adb logcat >logcat.txt

After about 10 seconds, hit Control C to exit out. Open that file (logcat.txt) that you just created in a text editor and search it for ".zip" (without the quotes). You should find the name of a zip file in there. Give me the name of that file (or the full URL if it's in there).
 

Top Liked Posts