yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] TheManii:
I've updated ITL35B/Yakju, IMM76B/Takju with likely timestamps.

Those two along with IMM76K/Yakju, IMM30D/Takju all need confirmations on their dates.

----------------------------------------------------------------------------------------------------------

I'll likely have to actually save them all onto the wiki eventually, but for the moment I need their timestamps confirmed after they are checked for updates (assuming they are the correct ones and give updates)

After those 4 all Yakju/Takju/Mysid/Mictacea will all either have correct timestamps or none at all.

There are still builds that have a build day but no timestamp as goog compiles everything for that build on the same day, but the timestamp records when it actually finishes compiling. Thusly even though Yakju/Takju/Mysid all recieved JDQ39, they all have slightly different timestamps.

(also as a side effect, the wiki will be able to sort them more accurately than just the day)

----------------------------------------------------------------------------------------------------------

I wonder how the patch notes are delivered to the device?

Is it a remote file it downloads with patch notes or are they directly pushed along with the update url?

----------------------------------------------------------------------------------------------------------

Edit: I wonder if it would be worth it to try and see if anyone with a no longer supported device would be willing to try also?

The ADP2/OG Droid/Xoom/Nexus 1/Nexus S are all still capable of recieving updates

(at least for roms newer then FRG83, roms older then that/the ADP1 no longer have their updates available on google's servers anymore).

The NS I have fingerprints and timestamps for roms that were not released to the wild.
[Samsung Galaxy Nexus] Cathair2906:
i just restored my galaxy nexus to yakjuzs JRO03C for getting the JOP40D, i will upload the link later on here
[Samsung Galaxy Nexus] efrant:
Done. Thanks.

Been really busy this weekend, so didn't get around to any more testing, but will post the results as soon as I do.

I'll also try to dig up my trusty Nexus One at some point and see what what I can do.
[Samsung Galaxy Nexus] TheManii:
Cool thanks, I'll give you infobits on the N1 after we get the GN done, as I'm sure more people (3+ people!) care about the GN right now.

--------------------------------------------------------------------------------------------------------------------------------------------

I would suggest splitting your OP into maguro, toro, toroplus segments, as mictacea is a toro rom but they're not compatable in the same way you cant ota yakju <-> takju.

It's not terribly important as noone is using it, but it's a bit confusing as-is?
[Samsung Galaxy Nexus] shakalaca:
Yakjuzs 4.2.1 (JOP40D)

http://android.clients.google.com/p...149357f78.update_yakjuzs_JRO03C_to_JOP40D.zip
[Samsung Galaxy Nexus] efrant:
Ok, so I went through them all.

Here are the results:

yakju

ITL35B updates to ITL41F http://android.clients.google.com/p...b74c962e.signed-yakju-ota-228551.2ef5b74c.zip <== we didn't have this link before.

ITL41D updates to ITL41F (we already had this one)

ITL41F updates to ICL53F (we already had this one)

ICL53F updates to IMM76I (we already had this one)

IMM76D updates to IMM76I (we already had this one)

IMM76I updates to JRO03C (we already had this one)

IMM76K updates to JRO03C http://android.clients.google.com/p....signed-yakju-JRO03C-from-IMM76K.3d319cfe.zip <== we didn't have this link before. The build date I used was 1334967744

takju

IMM30D doesn't update with the build date you mentioned

IMM76B doesn't update with the build date you mentioned

IMM76I updates to JRO03C (we already had this one)

JRN84D updates to JRO03C (we already had this one)
[Samsung Galaxy Nexus] TheManii:
I'm not sure about IMM30D/IMM76B, but everything else would likely suggest that there is no need to check them again in the future.

These is the other possible one for IMM30D:

1330709005

The only other one possible for IMM76B is:

1332707279

But that's the stamp for IMM76D/yakju, it's possible that IMM76B has no updates at all.

-----------------------------------------------------------------------------------------------------

If they dont update to anything recent, they likely never will.

At best they will give us full roms which is still nice, not that this batch gave us any recent ones.

ITL41F/yakju is our first full rom for maguro/toro.

It also concludes our list for maguro, as everything 4.1/4.2 had been previously checked by other posters.

For toro: Mictacea simply has no other candidates as the timestamps for the rest simply do not exist. (anywhere we can find them)

Mysid might need rechecking, the list looks like it could be potentially bigger.

For yakjuXX and toroplus/mysidspr: they're not actually nexus roms.
[Samsung Galaxy Nexus] oldblue910:
Thanks for these, Efrant. I'm mirroring both of the yakju OTAs on the website.
[Samsung Galaxy Nexus] mustafa.ali61:
Could someone tell me if there is the 4.2.2 update for nexus 4 in here. Is just that there are 207 pages and that is a lot.
[Samsung Galaxy Nexus] thephantom:
This is for galaxy nexus. Nexus 4 is http://xdaforums.com/showthread.php?p=33631631

[REF] Nexus 4 Stock OTA URLs
[Samsung Galaxy Nexus] shakalaca:
yakjuvs JRO03C from IMM76K

android.clients.google.com/packages/ota/samsung_proxima_yakjuvs/792fb0395674.update_yakjuvs_IMM76K_to_JRO03C.zip

---------- Post added at 08:58 PM ---------- Previous post was at 08:53 PM ----------

android.clients.google.com/packages/ota/samsung_proxima_yakjusc/ed269414c767.update_yakjusc_JRO03C_to_JDQ39.zip
[Samsung Galaxy Nexus] efrant:
Thank you. First post updated.
[Samsung Galaxy Nexus] osm0sis:
You added them backwards. ;)

Had my hopes up for a new UI radio!
[Samsung Galaxy Nexus] efrant:
Doh!

Fixed.
[Samsung Galaxy Nexus] joshminear:
I've searched and hunted, and now have to post and ask

I've never found any reference to my specific problem:

I've got a stock, untouched/unrooted/un-unlocked US Verizon Samsung Galaxy Nexus. It has never updated OTA. It just never gets the notification, and I've tried the various 'tricks' to force the issue with no luck.

As of today, 7/9/13, I'm running the following:

Android Version

4.0.4

Baseband: I515.10 V.FC02 / I515.FC04

Kernal: 3.0.8-g034fec9

android-build@vpbs1 #1

SMP PREEMPT Tue Mar 13 15:46:20 PDT 2012

Build number

mysid-userdebug 4.04 IMM76D 299849 dev-keys

Based on my limited understanding, IMM76D doesn't show up as a mysid build, but a yakju build? In addition, it looks like IMM76D was crap and stopped mid-rollout and replaced.

I'm also concerned about the "SMP PREEMPT ...." under Kernal and the "userdebug ~ dev-keys" stuff under Build number.

In any event, I'm not particularly interested in rooting, etc. I bought the damn gnex because I like stock and wanted a nexus device. If I didn't like verizon's coverage I'd be long gone. So I'm interested in getting to the most current version of Stock Android for the Verizon Galaxy Nexus, but am now baffled and believing I somehow got my hands on the lone massively ****ed up handset in Verizon's storeroom.

As an aside, and I don't know if this is related or not, I've recently run into all kinds of issues regarding 'Google Play Services' which is somehow apparently not installed on my device, and will not install from the play store due to some conflict. From what I've found in research, this issue seems to crop up only with rooted/tinkered with phones. I haven't rooted/tinkered.

A factory reset has fixed none of these problems.

I'd be forever grateful for any assistance from anyone at this point. I've searched and hunted, not only here, but all over the net, with no luck. Next step is a full root and off I go...
[Samsung Galaxy Nexus] osm0sis:
SMP PREEMPT is normal, but dev-keys (or sometimes we've also seen test-keys) is not, you're stuck on a beta build basically and that's why it isn't updating. Not sure why they sent you a device with a dev build flashed but that appears to be the case.

Your best plan is to unlock the bootloader with fastboot, "fastboot oem unlock" (this will wipe all data so backup any pictures, etc. you want). And then fastboot flash the latest factory image from Google's Factory Image page. Once you're on a normal build Play Services, OTA and everything should work fine. Rooting shouldn't have any effect on that either, so don't be afraid to root and tinker if you like. :)

Threads:

[REF] efrant's "Android for Galaxy Nexus" 101 & FAQs

[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JDQ39)
[Samsung Galaxy Nexus] TheManii:
He should make a nandroid first and post it, as it's a dev rom and they're generally not super common for any device. (well in general, I dont own a GN so I dont know how many dev roms have leaked for it)

It might be worthwile to someone.

Dev roms supposedly are IMEI whitelisted for updates, and if one got lost/stolen/sent forward in time 12 minutes they get removed from the whitelist.

Goog generally builds a lot more roms then it releases, for most of ICS they compile each build for all devices. They simply dont release the majority of them
[Samsung Galaxy Nexus] joshminear:
Many Thanks!

Should have posted long ago! Thanks for the quick response and the quick solution. I'll give it a go!

---------- Post added at 02:13 PM ---------- Previous post was at 01:57 PM ----------

I'm not at all opposed to this, if it would be of value to the community. However, someone will have to walk me through it (baby steps, people) step by step, or point me to a resource that will help me accomplish it.
[Samsung Galaxy Nexus] TheManii:
I cant be more specific then this as I dont actually have a GN, but the steps are pretty standard:

(assumes you have fastboot already set up on your pc)

Reboot device into fastboot mode

use "fastboot oem unlock"

download a custom recovery (doesnt really matter which)

"fastboot boot <path to custom recovery you downloaded>"

follow onscreen directions to make nandroid

Steps 1 and 2 are required to reflash any rom, so you'll be doing those regardless of if you make a nandroid
[Samsung Galaxy Nexus] joshminear:
All Alone

One of the problems I've run into in the past (rooting a Droid X and an original Galaxy S) is that I am apparently the only person on the planet using a mac mini and android devices (no pcs in the house). If only I'd known....or were independently wealthy... :D

I don't like things to be easy.
[Samsung Galaxy Nexus] TheManii:
You'll need the osx version of fastboot, assuming you're running osx on it.

You can grab the osx android sdk and it'll download the right versions, assuming you dont simply manually dig up the osx fastboot manually.
[Samsung Galaxy Nexus] tweentop:
hello me ali from turkey Hi everyone I am from Turkey ali hi A820 reopened display incorrect results do not establish a rom flash tool version is not here, please help needed rom multılangue
[Samsung Galaxy Nexus] osm0sis:
How to flash is in the second post, you use custom recovery to do so, no other tool is required. There are some toolkits which will also help you flash zips but we don't support them in this thread since we prefer to teach the right way. :)
[Samsung Galaxy Nexus] Zepius:
efrant,

please update the thread to show the latest version is 4.3

https://developers.google.com/android/nexus/images
[Samsung Galaxy Nexus] DJxSpeedy:
i need an takju OTA url please :D
[Samsung Galaxy Nexus] Misledz:
http://www.mediafire.com/?9haa8boct999v93

SuperSU for 4.3 ONLY.

-Flash this in CWM/TWRP

-Reboot

-Enjoy

Tested and works. Will post screens.
[Samsung Galaxy Nexus] osm0sis:
Why, did SuperSU stop working?
[Samsung Galaxy Nexus] Misledz:
Yeah 4.3 changed alot of things, for one their storage is no longer storage/0/

it's now emulated/legacy/0

If you don't change the Titanium folder location from storage/0 to legacy/0 your TiBu's will fail, and you will get constantly spammed with "No storage space available"

As per cheating the system without a Insecure Boot Image, I copied the TiBU folder on a USB, OTG'd it and pasted it and it worked :)
[Samsung Galaxy Nexus] osm0sis:
It was already storage/emulated/0 in 4.2. :confused:

P.S. Is it just me or is the MD04 bootloader slow as ****?
[Samsung Galaxy Nexus] Misledz:
It's not just you it has a 5 second black screen before it falls to the bootloader. Aside from that the current was /emulated/0

But now it's /legacy/0 for 4.3

Success my plan worked
[Samsung Galaxy Nexus] osm0sis:
Seems to still be /storage/legacy -> /storage/emulated/0, /sdcard -> /storage/emulated/0, /storage/sdcard0 -> /storage/emulated/0 just like in 4.2. And those symlink endpoints change depending on the user in multiuser setups.

And a 2-3 second black screen sounds like a slow as **** bootloader to me. :p It was instantaneous with LC03.
[Samsung Galaxy Nexus] Misledz:
I'll let you reach that part. For some reason 4.3 is acting like a little girl atm being picky about location. I know it's the exact same thing and it loads the exact same folders but the system rejects opening anything that isn't opened from the legacy path
[Samsung Galaxy Nexus] efrant:
I updated the title of this thread. Once the OTA update is available, I'll update here.

Be careful with that version of SuperSU. It is not yet stable (on the N4 at least). There is an issue where for some reason (and we haven't figured it out yet), you lose root, and the daemonsu process starts eating up ~70%+ of your CPU time. Battery dies pretty quick.
[Samsung Galaxy Nexus] Misledz:
That explains it ._. I was checking the CPU process and it was INSANELY high. But all for the love of root.
[Samsung Galaxy Nexus] osm0sis:
Okay here's what I think you were trying to explain:

https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L

Chainfire explains it better but the symlinks didn't change, the way root works with apps trying to access them does. :)
[Samsung Galaxy Nexus] alexeiw123:
So will this be the correct spot to spot a .zip for updating a yakju maguro to 4.3? I guess it could be a matter of days before we see the OTA yeah?

Could flash factory image, but seeing as life is busy I'd rather not have to re-setup my phone settings let alone the data.
[Samsung Galaxy Nexus] osm0sis:
You can just flash bootloader.img, system.img and boot.img and call it a day. No data or app loss that way.

That's how we "dirty flash" stock. ;)
[Samsung Galaxy Nexus] artkrz:
There's a OTA Yakju link in this thread.
[Samsung Galaxy Nexus] aryan79:
YEAH!!!! :)
[Samsung Galaxy Nexus] artkrz:
Do I have to un-root to get this update installed ? I'm getting:

Warning: No file_contexts assert failed: file_getoprop("system/build.prop"

E: Error executing updater binary in zip /sdcard..

Error flashing zip '/sdcard/....'
[Samsung Galaxy Nexus] osm0sis:
Whatever the failed assert says, that's something you changed and need to revert for it to pass. Or you could just flash system.img from the Factory Image and call it a day. ;)
[Samsung Galaxy Nexus] artkrz:
Yep. Want to get rid of root anyway so probably best to flash to stock.
[Samsung Galaxy Nexus] osm0sis:
You tried to flash an OTA over non-stock? Come on.. :p
[Samsung Galaxy Nexus] jellymelly:
To receive the OTA immediately, go to android settings > apps > Google Play Services then hold your phone above your head, making sure you have full wifi signal strength and turn your body on the spot 20 times, pressing the clear data button once with each circle, repeatedly chanting louder and louder each time the following: "god of holo, nexus warrior, may Lord Duarte OTA my soul... god of holo, nexus warrior, may Lord Duarte OTA my soul...god of holo, nexus warrior, may Lord Duarte OTA my soul..." ﻿
[Samsung Galaxy Nexus] -Jesco-:
i can ensure that this work :Humor:
[Samsung Galaxy Nexus] Cupellom:
Very usefull guide, thx!
[Samsung Galaxy Nexus] fpbasilio:
i have the same error. Is there a way to check what exactly needs to revert? I'm not sure what I changed in the past that's causing the error. I defiantly did not remove any system apps.

---------- Post added 26th July 2013 at 12:44 AM ---------- Previous post was 25th July 2013 at 11:44 PM ----------

Nvm, just realized im on takju that's why. Will wait for takju ota links :)
[Samsung Galaxy Nexus] markitosd:
No OTA for Takju yet? I want to upgrade to 4.3 and I'm having 4.2.2 right now. Thanks!
[Samsung Galaxy Nexus] switch85:
Yakju JWR66V from JDQ39 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815.zip
[Samsung Galaxy Nexus] oldblue910:
Thank you! I'm mirroring it on randomphantasmagoria.com right now.
[Samsung Galaxy Nexus] KnighthooD:
I Uupated succesfully my gnex to android 4.3
[Samsung Galaxy Nexus] aanto:
I've been trying to update but adb won't recognize my device when it's off or in recovery mode. It does recognize it when it's on :/

What should I do?

Thanks.
[Samsung Galaxy Nexus] jcsww:
Install the correct device drivers mentioned in the how to in the first post.

Edit: That must be in another thread. I will find it.

Edit 2: This first post. http://xdaforums.com/showthread.php?t=1626895
[Samsung Galaxy Nexus] panlinux:
It will only recognize the device after you selected the adb sideload option in recovery and it's waiting for the file. Then you can run adb sideload on your computer.
[Samsung Galaxy Nexus] aanto:
Oops, sorry. I think it's updating now.

Thank you!

Edit: I'm getting "installation aborted" after the verification.
[Samsung Galaxy Nexus] Soldier 2.0:
This should get stickied! :good:

Sent from my GT-I9505G using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] oldblue910:
Actually no. Is a very bad idea. Doing that completely breaks push notifications for every app that uses them. If you do this, you will not receive push notifications from any app until you clear the data for each app that uses push notifications and set each one up from scratch. This trick can also cause problems with paid apps purchased through the Play Store.
[Samsung Galaxy Nexus] osm0sis:
It can also cause those weird Play Store -## download errors, and GApps crashes until you remove and readd your Google Account.. So yup, bad news. You should only do that if you take a nandroid first, and then only so you can logcat the OTA URL. Then you'd restore your nandroid so that everything still works, and use the OTA URL to manually flash the OTA in a custom recovery.
[Samsung Galaxy Nexus] Soldier 2.0:
People from the future will read these threads and laugh their asses off.

Sent from my GT-I9505G using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] jeremysherriff:
All, please participate in this survey to assist with identifying how Google prioritizes their OTA roll-out schedule.

http://forums.androidcentral.com/an...googles-nexus-updates-study-ota-rollouts.html

Apologies in advance for the spam, I've posted this in a couple of different Nexus device threads.
[Samsung Galaxy Nexus] _acp:
Hi there,

those of you that tried the new 4.3 OTA, have you rooted the phone and how? Is Voodoo OTA rootkeeper going to work?

Thanx
[Samsung Galaxy Nexus] ogre_x:
Yes. Flashed the SuperSU zip. No.
[Samsung Galaxy Nexus] davebyone:
can i flash OTA 4.3 yakju on takju?
[Samsung Galaxy Nexus] el_charlie:
Pointless. It won't work.

If your bootloader is unlocked, follow Efrant's guide to flash the 4.3 factory image without userdata to upgrade. You wont't lose settings or apps.

Cheers!
[Samsung Galaxy Nexus] davebyone:
thank you. i'll try to do this.
[Samsung Galaxy Nexus] el_charlie:
You're welcome!

Just make sure to real ALL the guide before atempting anything on your phone and ask there if you have any questions.

Cheers!
[Samsung Galaxy Nexus] burnedx420:
got takju OTA:

http://android.clients.google.com/p...9.signed-takju-JWR66V-from-JDQ39.cda87c8b.zip

hf
[Samsung Galaxy Nexus] oldblue910:
Thank you! I'm mirroring the file on randomphantasmagoria.com right now.
[Samsung Galaxy Nexus] Shibang:
Thanks for takju. Just installed it on my rooted 4.2.2 and everything seems to be working great.
[Samsung Galaxy Nexus] Penphoe:
http://android.clients.google.com/p...9.signed-takju-JWR66V-from-JDQ39.cda87c8b.zip

Latest Takju update!!!
[Samsung Galaxy Nexus] jerem.b:
Thanks, I'll try the takju update asap.
[Samsung Galaxy Nexus] Reeebo:
Just got the takju OTA update!
[Samsung Galaxy Nexus] davebyone:
error while try to flash it on takju. using CWM 5.5.0.2
[Samsung Galaxy Nexus] Hotshot205:
Any method to flash this update without losing root?
[Samsung Galaxy Nexus] ogre_x:
No. You need to re-root after update.
[Samsung Galaxy Nexus] Hotshot205:
Well guess I'll wait until I can update without having to re-root the device.
[Samsung Galaxy Nexus] jerem.b:
And it worked...Thanks a lot!
[Samsung Galaxy Nexus] el_charlie:
Is your bootloader unlocked? If so, I don't see a reason why not to reroot again. It's just flashing a .zip through CWM/TWRP.
[Samsung Galaxy Nexus] osm0sis:
You will be waiting a long time since that'll never happen for stock. Chainfire has been pretty clear that you need to flash the zip to reroot the first time after you update via the OTA. No root keeper can save you this because the root method is completely different starting with JB4.3.
[Samsung Galaxy Nexus] Hotshot205:
What I'm really saying or asking is it an method to flash this update and keep my data than re-root and keep my data without wiping my data, pictures, music etc etc.
[Samsung Galaxy Nexus] osm0sis:
What? OTAs don't wipe data, and neither does the root zip.

Only way is if you haven't unlocked your bootloader and you don't have a custom recovery yet. If your bootloader is locked and you're somehow rooted (via one of the old exploits or something) then get the BootUnlocker app by segv11 and unlock it. Couldn't be simpler and zero data lost since all it does is flip the bit that tells the bootloader it's un/locked.
[Samsung Galaxy Nexus] Natakranta:
See my post here, bear in mind I have unlocked boot loader.
[Samsung Galaxy Nexus] Hotshot205:
Oh my mistake lol all I have to do is flash the OTA and the supersu zip in rom Manger or recovery? And I'll be fine? No data loss or loss of root?
[Samsung Galaxy Nexus] Natakranta:
Easiest way is to flash OTA zip through custom recovery like CWM. This will not wipe your user data and apps. Though you will lose root and you will have to flash new SuperSu through CWM.

I tried it but I received an error. That's why I downloaded full 4.3 ROM and extracted necessary .img files from it. Than I flashed them manualy in fastboot mode. I'd advise readinh efrant's tutorial. It is really good and detailed.
[Samsung Galaxy Nexus] Hotshot205:
Which tutorial? The one on the first page?
[Samsung Galaxy Nexus] Natakranta:
Yes, for flashing OTA update see the one here on first page.

If you get an error message, try flashing 4.3 ROM like described here link
[Samsung Galaxy Nexus] matthyx:
takju on android police

The link for takju is available on android police, google for the page named:

How To: Flash Your Galaxy Nexus Takju Or Yakju To Android 4.3 (JWR66V) And Root It Right Now

I cannot post the link here as:

"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
[Samsung Galaxy Nexus] theillustratedlife:
From my logcat:

http://android.clients.google.com/p...9.signed-takju-JWR66V-from-JDQ39.cda87c8b.zip
[Samsung Galaxy Nexus] fromage2323:
Easiest way to update was to copy the patch via USB to the Download folder, where Android automatically recognized it and prompted me for patch. Ive never seen that before, is this new or am i just slow?
[Samsung Galaxy Nexus] osm0sis:
Anyone else using Stock Browser find Most Visited started showing only an empty white page starting with JB4.3 or shortly after? Clearing app data doesn't help. I usually have it as my opening homepage and it's been driving me crazy not being able to use it anymore. My next day off I'm probably going to have to TiBU and start from scratch if I don't figure out another fix. :(