yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sagiballs:
2) Download this and unzip the files within to a directory (There is a .zip inside. Extract them all.);

3) Download the attachment and extract the files into the same directory

Yep. I dl'ed the file. I extracted it, and then went on to extract the zip file that was also inside it. This is all on my desktop (win 7, 32 bit). Can i leave this there? or do i need to copy it into the android SDK tools folder which houses fastboot and adb?

This is a very noob thing, but what i'm confused about is the "directory" part. Is it sufficient to make a folder in my documents, for example called "nexus", and put all the files in there? or does this all have to go in a specific place?
[Samsung Galaxy Nexus] efrant:
The files in the attachment and images all in one folder. Any folder.
[Samsung Galaxy Nexus] sagiballs:
Thanks for that. One last question (hopefully)

with steps:

5) Optional -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img

6) Reboot (not required if you did not do step 5): fastboot reboot-bootloader

7) Optional -- Flash the radio: fastboot flash radio radio-maguro-i9250xxla02.img

in your opinion, is it better to flash the bootloader and radio, or just to leave it? Since these are optional, clearly they aren't required to get 4.0.4 up and running. but would my phone work better with android 4.0.4 with these options?

Im on android 4.0.2 with the XXKK6 baseband radio (completely stock for australia)
[Samsung Galaxy Nexus] efrant:
Flash the bootloader-- you won't notice any difference. Check the stickied radio thread for a discussion on which radio is the best for you.
[Samsung Galaxy Nexus] Reeebo:
so far no signal problems! seems to actually be stronger than before since i flashed a new radio. but i'll keep you guys posted if something goes wrong
[Samsung Galaxy Nexus] Haroundb:
I made an illustration for those who are still confused, I hope it helps them out to follow the correct sequence of update!

Thanks...

Haroun
[Samsung Galaxy Nexus] zerdon:
First, thanks for the excellent instructions and continued support in this thread! You guys are great! I followed the full instructions in post #1 to the letter (including optional steps) and was able to easily update my white yakjuxw (4.0.2) to yakju (4.0.4) in about 15 minutes.

Now for the problems:

1) Unfortunately, I'm experiencing the signal loss issue. I'm on the ATT network, if that helps. Terrible signal loss. I believe I've missed some calls, possibly texts, but I'm not sure to the extent yet. Almost every time I check my phone, there is no signal after it sleeps. When I've gone to make a call, it takes several seconds for the network to reconnect. So this is annoying at best, possibly a complete mess at worst.

2) Battery life is terrible. This is the one I can't understand. My battery life is at least 1/2 or worse what it was with the original OTA 4.0.2 yakjuxw that was in the phone before.

So, any recommendations? I have read about the signal loss issue fixes, but as I understand it, that will reduce my battery life even further. So I prefer to just go back to where I was...

Unfortunately, I did NOT make a backup of the phone, and have no image to go back to, and at this point I have a nearly useless phone until some sort of update is done. The battery life alone makes it impossible to get through a day of even light use.

Do I just wait it out for Google to update, or start experimenting with other images?

Other than that, I really like 4.0.4! :)
[Samsung Galaxy Nexus] efrant:
Unfortunately, I can't really help you with the signal or battery issue, as I am not experienceing either. If you want, you could always revert to yakju 4.0.2 -- just follow the steps in post 1 again, but use the ICL53F image from Google's page here instead of the IMM76D image. Apparently those who are having signal issues don't have them once they go back to 4.0.2.
[Samsung Galaxy Nexus] stormaker:
@zerdon, or alternatively, you can try flash different radio first, if none of them fix the problem, then you should do like what efrant said, revert back to 4.0.2.
[Samsung Galaxy Nexus] zerdon:
Thank you efrant and stormaker. I'm going to give 4.0.4 one more day as-is so I can get a more precise measure of what is really happening, then follow your suggestions. I just reset my phone so I have nothing but the stock Android and apps, etc. so I can get a clear picture to compare to when I switch. Thanks again!
[Samsung Galaxy Nexus] zerdon:
Quick update: So the 4.0.4 was simply terrible for me, I didn't need to wait another day to test it more... within 4 hours, I could tell battery life was unusable, with major disconnection problems -- it said 49% signal connection loss I believe.

So I followed the directions in post #1 as suggested above, and went to the 4.0.2 ICL53F image from Google's page. With just an hour or two of use so far, the phone performs significantly better for me. No signal loss so far. Will update if something changes.

Thanks again for your help!
[Samsung Galaxy Nexus] NCguy:
Wow. I haven't received 4.0.4 yet and now I'm not sure I want it. I will definitely do a nandroid before I attempt it. Just to confirm, Nandroid backs up all partitions including radio?
[Samsung Galaxy Nexus] efrant:
No, it backs up the boot and recovery images, as well as the files in /system and /data. All radios are available in the stickied radio thread.
[Samsung Galaxy Nexus] NCguy:
Does 4.0.4 ota update any of those partitions that nandroid doesn't back up?
[Samsung Galaxy Nexus] efrant:
I'm not sure where you are going with your questions. Yes, the update updates the radio and the bootloader, both of which are not backup up by a nandroid. But back-ups for those two images are readily available, so I'm not understanding the issue.
[Samsung Galaxy Nexus] NCguy:
Actually I'm on yakjuxw and I wasn't sure how available those files were in case I wanted to go back to what was shipped. I would obviously try the stock yakju first.
[Samsung Galaxy Nexus] efrant:
Yes, a nandroid will back up anything that is not currently available elsewhere.
[Samsung Galaxy Nexus] zerdon:
Quick update -- 4.0.2 (yakju) ICL53F image is working great since I flashed from the 4.0.4 update. Connection, battery, etc., working as good as my original 4.0.2 yakjuxw, if that matters, on ATT network.

Now that I'm on 4.0.2 yakju, I have not yet received an OTA notification for 4.0.4. For the heck of it, I checked for system updates, and it says that my phone is up to date.

Questions:

1) So, will I be getting the 4.0.4 OTA update at some point soon? (Not that I want it, due to my prior experience with installing it manually.)

2) Since I've followed the steps in post #1 (including optional steps) I'm wondering if I will get ANY OTA updates in the future, or did I disable OTA updates by flashing from yakjuxw to yakju?

Thanks again for your help.
[Samsung Galaxy Nexus] efrant:
You have not disabled anything. You will get the OTA update (and all future updates) as per normal. The thing is, no one knows when or how Google pushed the update out to devices, so it could take seconds after Google announces that it is rolling out, or it could take months.

The advantage of switching to yakju, is that it is the first build to receive updates, and, given that someone running yakju is likely to receive the update and post the link here WELL before it is rolled out to most devices, you can essentially update to the latest version not too long after the update is announced.
[Samsung Galaxy Nexus] zerdon:
Thanks again!
[Samsung Galaxy Nexus] ddragman:
Try fallowing and report if it will help. You may need to repeat it several times.

Go to Settings, select Apps, select All, find and select Google Services Framework and click Clear data.

Now go back to the Settings, scroll to the bottom and select About Phone, select System updates (Last checked for update will be 1/1/1970 or 1969. Nothing to worry about) and click Check now.

You may need to repeat these steps several times. Some users got update after first attempt. Others gave up after 50+ attemps without getting OTA.
[Samsung Galaxy Nexus] zerdon:
Thanks for the tip. I just tried this 5 times for the fun of it, system still reports it is up to date. I think for now I want to stick with 4.0.2 though, considering the problems I had with 4.0.4. :)
[Samsung Galaxy Nexus] UnusualSuspect:
I received my GNex from Newegg last Wednesday, a Docomo SC-04D with a 4.0.1 NTT build straight out of the box. The very first thing I did was flash it to yakju 4.0.4. When it was finished flashing I immediately did a factory reset before beginning customization.

So ... I have an uber-clean install of yakju 4.0.4 and I couldn't be happier with it. Great performance, great battery life, no signal problems and chock full of ice creamy goodness. :)
[Samsung Galaxy Nexus] NCguy:
Thanks for that report! Definitely eases my mind a bit.
[Samsung Galaxy Nexus] efrant:
It eases your mind with regards to what?
[Samsung Galaxy Nexus] zmsudu:
Disregard
[Samsung Galaxy Nexus] NCguy:
Upgrading to 4.0.4. Clearly that's why he made that post
[Samsung Galaxy Nexus] efrant:
I guess the three points I was trying to make are:

1) The flash procedure works. It has been confirmed by many individuals.

2) Some individuals have reported issues related to signal loss and battery when flashing 4.0.4. Some do not have these issues. We have not seen a common link between those who have them. Nor between those who do not have them. It seems like you will have to try it out yourself.

3) Given that we have unlockable bootloaders, we are able to create and restore a backup to return our device to how it was prior to flashing 4.0.4.

Given the above three points (which are not opinion, they are fact), I personally do not understand some individuals' hesitation to try 4.0.4, unless of course those individuals are not comfortable with what the flashing process does at each step, and therefore may need to do a bit more reading to understand.
[Samsung Galaxy Nexus] NCguy:
Speaking for myself it has nothing to do with the capabilities of the tool. I'm confident now, from your gracious comments, that I could restore if need be. Unfortunately I don't have a spare phone and if I hosed it then it could possibly be a business interruption until I got it straightened out. Therefore, it gives me some relief to know that the chances are good that after going to 4.0.4. I won't have to worry about rolling back even though I know its probably not that big of a deal. I didn't mean to make it sound bigger than it is. Sorry if it came out that way.
[Samsung Galaxy Nexus] UnusualSuspect:
I made the post in question to share my positive user experience with the procedure outlined in this thread.

I don't do the "ROM du jour" thing. I use my phone for work, and so do not flash often at all. I do 24x7 support for a large IT services company, and my phone doubles as my pager (the corporate paging server sends me SMS) as well as Exchange calendar, contacts and email.

If I don't respond to a page-out because my current ROM is buggy ... well, the boss wouldn't be very happy. Before turning off my SGS II, I wanted to make sure that its replacement is good and stable - and it is.
[Samsung Galaxy Nexus] efrant:
No, no worries. I was just trying to understand. A lot of people are worried about messing up their phone. It is extremely difficult to mess up a GNex. Easy to lose your data, but extremely hard to make the device not work (given an unlockable bootloader -- the big advantage of Nexus device, and now, some HTC devices as well). The procedure I outlined in this thread can be used to flash any stock build -- 4.0.1 or 4.0.2 or 4.0.4. If 4.0.4 doesn't work for someone, they can just as easily flash 4.0.2. Once your drivers are set up on you PC, the whole process should not take more than a couple of minutes.

(That said, if you want to flash back your yakjuxw build, you have to create the backup yourself, as there is no image for that build floating around these forums.)
[Samsung Galaxy Nexus] zerdon:
Quick update for the record, for those that might have faced a similar problem with connection and/or battery life problems with 4.0.4 yakju:

Since I've flashed back to 4.0.2 yakju, my battery life has been excellent compared to 4.0.4 yakju. Also, no disconnection issue I can see. In fact, this 4.0.2 yakju seems to perform better than the original 4.0.2 yakjuxw I had on there in the first place!

And, for those that are worried about following the directions in post #1, I can confirm (along with many others) that the process works smoothly.

It's a mystery why some of us have had problems with 4.0.4, though, and others have had no problems. I wish someone could give a definitive reason why... perhaps it has to do with the carrier/network, hardware variations, who knows?

Anyway, I'm pretty happy with 4.0.2 so far. Thanks again for your help in this thread!
[Samsung Galaxy Nexus] efrant:
What's even more of a mystery is how you can have two people with the same hardware (and same original build) and same carrier, yet one has issues and one does not.
[Samsung Galaxy Nexus] sagiballs:
if anyone from Australia has any pearls of wisdom about driver configuration i'd love to hear them, because it's killing me at the moment!
[Samsung Galaxy Nexus] Theshawty:
Thank you for the guide, efrant!
[Samsung Galaxy Nexus] efrant:
Getting the drivers to install is the the part that is the most difficult to explain. But make sure you read the links in step 1 of my procedure.
[Samsung Galaxy Nexus] Theshawty:
What is your opinion on this utility? It's called knives and forks.

http://xdaforums.com/showthread.php?p=22047755#post22047755
[Samsung Galaxy Nexus] sagiballs:
that they are.

I've tried multiple ways of updating and none of them worked. So i tried the manual update to which my computer gave me the msg that windows had already selected the optimal driver and wouldnt let me select a new one. Under wugfresh's instructions over at galaxy nexus forums i've also deleted known offending previous drivers...

Hitting my head against a brick wall hoping at some point it will crack. the wall not my head that is. Thanks for your detailed instructions. i will keep trying!
[Samsung Galaxy Nexus] efrant:
I've never tried it.

As with any toolkit, I am against them for n00b-use. If someone doesn't do everything manually at least once, he/she will never learn. You need to try to install the drivers, see what is happening, troubleshoot, ask questions, troubleshoot some more, and figure it out. This is all part of the learning process. If people do not go through this process, they will not know what to do when something happens/changes later on.

Using toolkits or any kind of 1-click solution is fine for those that understand what they do, but if you don't understand, then you shouldn't use it. As an example, if a toolkit has an option called "Root your device" and you click it, you are rooted. But do you know how it did that? If you know that what that option does is mount the system partition to r/w, copy su and Superuser.apk to the correct spots, change the permissions on those files to the right ones, and then unmounting the system partition, then I think you are ok to use the toolkit. If you didn't understand what I just said or how to do it, then you shouldn't be using a toolkit.

---------- Post added at 09:05 AM ---------- Previous post was at 09:03 AM ----------

Uninstall ALL previous drivers and use the ones I linked to in step 1. Do not use the Samsung drivers.
[Samsung Galaxy Nexus] ijortegar:
Question

Hi,

I have a yakjujp version of Galaxy Nexus and i want yakju in order tu receive updates via OTA.

You do this. Is your phone working OK?

I have the 4.0.2 version and i want the 4.0.4, but i need some confirmation of someone who did it sucsessfully.

Sorry for my bad english.
[Samsung Galaxy Nexus] sagiballs:
WOW. ultimate thanks for your patience.

I got my drivers working using your ulti/every driver in the link, doing this method:

http://xdaforums.com/showpost.php?p=22336085&postcount=486

And now i am on 4.0.4 sweet :)

So thankful. hope it goes alright...
[Samsung Galaxy Nexus] efrant:
Follow the instructions in post 1. I would not have created a step-by-step with instructions that do not work...
[Samsung Galaxy Nexus] ijortegar:
Thx

Well thank you. I will.

I will post the results later :)
[Samsung Galaxy Nexus] sagiballs:
this was a good update so far:

Pros:

battery seems slightly better (subjective)

no longer have in call volume issues (Thank God)

vibration is still on the lower end but better

auto-rotation is still not as fast as i'd like it, but it is better

camera subjectively looks a little nicer

addit: updating the drivers was a major plus - now my phone doesn't connect by MTP anymore, so I can actually copy and paste things over properly

Cons:

? subtle changes to the UI which i don't like as much... but is not a bother to live with

I'm not sure if my signal has been affected - i think not... but all the calls and msgs i've received have actually occurred while i've had the screen on... what are the chances?
[Samsung Galaxy Nexus] umadbra:
Hello,

I did the procedure in the second post and i got the OTA update to the 4.0.2, but i still cant get the update to the 4.0.4 using this:

http://xdaforums.com/showthread.php?t=1578569

Wnat should i do?

Can i use the procedure in first post without any problem?

Tks
[Samsung Galaxy Nexus] efrant:
Use the method in the first post.
[Samsung Galaxy Nexus] Theshawty:
Can I ask you a question beside this one?

What can cause these signal-drops many seem to have with 4.0.4? It cannot be the radio as I use the one that came with 4.0.4 together with CM9 and I'm not facing this issue there. What in the official IMM76D build can cause this?
[Samsung Galaxy Nexus] efrant:
I can't really answer that for you. There has been no consistency in findings and/or reports. It's not the radio, it's not the IMM76D build, it's not the bootloader, it's not the wireless carrier, it's not the hardware -- it seems to be some combination of all of these.

As I have said in other posts, I have no issues whatsoever with signal drops. These are my details:

Device model: GT-i9250M

Device purchased from: Virgin Mobile Canada

Battery used: Samsung OEM 2000mah

Date of purchase: 08 December 2011

Original device build: yakjuux ITL41D

Wireless carrier used: Rogers Wireless

Radio: I9250XXLA2

Bootloader: PRIMELA03

Recovery: CWM 5.5.0.2

Kernel: stock IMM76D (no mods)

ROM used: yakju IMM76D

Update method: flashed yakju IMM76D-from-ICL53F update package in CWM as per these instructions.

Root: Yes

Bootloader unlocked: Yes

Based on the above, I have had no issues.
[Samsung Galaxy Nexus] NCguy:
Agreed it seems hard to pin down and google may have stopped the 4.0.4 until they can get a better handle on it. Last I heard is that it happened after sleep and some devices may go into a deeper sleep depending on their app mix.
[Samsung Galaxy Nexus] Benmc06:
Hi there

Does anyone know if followingthe Noob Version on the second post on the first page, involves unlocking the bootload or root the NEXUS in order to install Yakju?

This is just because i want minimal interferance in my NEXUS in order to move from Yakjudv to Yakju.

Thanks
[Samsung Galaxy Nexus] catfish:
Had some alot of issues unpacking the .TAR file but finally figured it out and used 7zip and unpacked the original ROM from google and now up and runing free from NTT Docomo! Thank you!
[Samsung Galaxy Nexus] martin.capeletto:
thanks for the info!
[Samsung Galaxy Nexus] efrant:
I will update my post and get the first post updated as well. WinZip and WinRAR do not work properly on .tar files. 7zip is far superior (and open source!).

---------- Post added at 09:02 AM ---------- Previous post was at 08:59 AM ----------

Rooting is not involved in any of the methods. It is something different.

The second post does not require YOU to unlock your bootloader, but odin will essentially unlock it and re-lock it for you.

If you are using the method in post #2 and are expecting to get the OTA update to 4.0.4 immediately, you will likely be disappointed -- you may get it immediately, or you may get it months later.

Use the method in post #1.
[Samsung Galaxy Nexus] Theshawty:
A small question. If I install the official 4.0.2 system and boot, will I be able to get OTA's when and if they arrive?

Or will I also need the bootloader and radio accompanying the 4.0.2 factory package? I'm thinking of ditching custom ROMs for now.
[Samsung Galaxy Nexus] efrant:
There are two issues here, and they are separate, so don't confuse them. The two issue are:

1) Receiving the OTA update notification;

2) Having the OTA update install automatically.

Everyone (including those with custom ROMs) with this line in their build.prop file will eventually get the OTA update notification for the next update:

ro.build.fingerprint=google/yakju/maguro:4.0.4/IMM76D/299849:user/release-keys

However, in order for that update to install AUTOMATICALLY OTA, you need to have the following flashed to your device:

IMM76D system image

IMM76D boot image

XXLA2 radio image

IMM76D recovery image

You could also installed it MANUALLY if you have CWM installed (instead of the stock recovery), but all the rest above also need to be installed.

You could even have it install if you only have the IMM76D system image flashed and nothing else, but this requires editing of the build.prop, so you need to understand what you are doing.

The update will not install on a non-stock image, nor on a "stock" deodexed image, not on a "stock" AOSP image.

EDIT: I realized that I wrote this for those on IMM76D, but the same idea applies for ICL53F.
[Samsung Galaxy Nexus] Theshawty:
Ok, thanks for your well-written guide!

Another question. I'm looking to install the stock 4.0.2 factory image again (but keeping the bootloader unlocked, which shouldn't affect anything?) but there is something that stops me: The radio and bootloader.

I don't know why, but I'm always a little bit afraid of flashing these. Need I be afraid?

How do I "start" the flash-all.sh on a Windows box? There is no exe file in the downloadable zip containing the ICL53F factory image from Google.
[Samsung Galaxy Nexus] efrant:
No, having an unlocked bootloader doesn't affect anything related to the OTA updates.

As for your radio and bootloader question, I already replied to you in the radio thread:

http://xdaforums.com/showpost.php?p=25088951&postcount=486

As did josteink:

http://xdaforums.com/showpost.php?p=25080597&postcount=482

Extract the zip using 7zip and flash each image individually like I have indicated in the first post of this thread.
[Samsung Galaxy Nexus] Katana-Bob:
Hi, great guide! But.... I installed the latest GSM rom from the official google site, using the fastboot method called "How to Change Galaxy Nexus Firmware from YAKJUXW to YAKJU" on theunlockr (I can't post a link, I don't have enough posts.

1. I don't have a dictionary, so when I type it only suggests contact names

2. Does using the image "yakju-imm76d-factory-c6e807a1" negatively affect reception and wifi signal in my country (Norway?). Can all countries use it without bad reception? I already installed it, but I keep getting reception down to -100 dB, sometimes even below that. And wifi is always no more than two bars.

3. Battery life SEEMS worse, but I can't really confirm yet.

4. I didn't back up my image. I only know it was YAKJUXW. Is there a way to go back to out of the box rom? Do I need to hunt down a specific rom that applies to my country, or are all the YAKJUXW roms the same?

I was extremely disappointed when I saw I had YAKJUXW, so I hope you can help. Thanks in advance!

RADIO: I9259XXKK6

Build number: IMM76D
[Samsung Galaxy Nexus] efrant:
I can't really comment on the method you used, but I can tell you that the method in post #1 works just fine.

1) Not sure why you are experiencing this.

2) Try flashing a different radio. I notice that you are on XXKK6, which is an older radio. Maybe try one of the newer ones, which you can find in the stickied radio thread.

3) Battery life is better for me on IMM76D vs ICL53F.

4) All yakjuxw images are the same.