Related
Hello everyone,
I'm not sure if this has been answered yet or not but I recently received a GSM Galaxy Nexus that I ordered from Expansys-USA and it arrived with firmware ITL41D on it. I tried performing a System Update and it said my system was up-to-date.
I was wondering what the difference is between ITL41D and ITL41F. Google offers recovery images for both D and F, but doesn't specify a difference between the two. I am currently using the phone with an AT&T SIM if that makes any difference.
ITL41F has a fix for the volume bug and ITL41D doesn't.
The volume fix only applies to Europe though.
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
The volume fix only applies to Europe though.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not true, I have AT&T in the US, I was being affected by the volume bug almost every time I was in 2g. So was a friend of mine that has the phone. People here have explained that it is probably because AT&T's frequency is 850mhz and that is probably hitting a high enough range to be affected by the bug.
So I am not sure if it is rare, but it was happening to me at work, while driving in 2g areas, and at home when I was in 2g.
Also I couldn't get the OTA because of the Samsung keys, and having I think their build. I had to flash the stock build to get the update.
wolfedude88 said:
Not true, I have AT&T in the US, I was being affected by the volume bug almost every time I was in 2g. So was a friend of mine that has the phone. People here have explained that it is probably because AT&T's frequency is 850mhz and that is probably hitting a high enough range to be affected by the bug.
So I am not sure if it is rare, but it was happening to me at work, while driving in 2g areas, and at home when I was in 2g.
Also I couldn't get the OTA because of the Samsung keys, and having I think their build. I had to flash the stock build to get the update.
Click to expand...
Click to collapse
I stand corrected , I was under the impression at&t wasn't affected due to different bands than Europe
Sent from my Galaxy Nexus using xda premium
OP check your build.prop with astro or another file manager. It is located in /system.
look for the line ro.product.name=
Does it say yakju or yakjuxw?
If its yakjuxw you have a samsung build and not google.
See this thread for details. http://forum.xda-developers.com/showthread.php?t=1376856
Looks like I have yakjuxw
Will this be a problem for me with OTA time comes?
spectrumfox said:
Looks like I have yakjuxw
Will this be a problem for me with OTA time comes?
Click to expand...
Click to collapse
I'm sure you will get an update eventually but they wont be the one with the google keys.
Apparently, the yakjuxw builds are for a specific unknown region and carrier.
Being how I live in the US I just flashed the yakju build from here: http://code.google.com/android/nexus/images.html
Weird, i purchased my GNex from ExpansysUSA as well and it came with ITL41D and the fix wasnt out just yet. Last week i was notified of the OTA and allowed the update and it worked fine. If i check now it says my phone is up to date and version is ITL41F. Im on Tmobile USA though but i wouldnt think that should make a difference. I havent experienced the volume bug at all either but TMO doesnt use 850mhz.
Hmm i have the D version and my product name is yakjuux. I got the phone today and am with Bell. Searched the forum and no results came up with that product name.
Also on the ITL41D release and purchased from Negri in Nevada.
On the site where Google provides the prop files in order to build AOSP, http://code.google.com/android/nexus/drivers.html, they do split out the prop files for the two releases, ITL41D and ITL41F.
GSM and Graphics both have different md5sum values, but no idea what is difference between the two. If they release the prop drives similar to how they do for the nexus s 4g, they'll just be binary blobs making a diff on the files not very useful.
Appears a few blogs are quoting the ITL41F as being an update for the ITL41D devices, but not sure how accurate that is: http://www.givemedroid.com/tag/itl41f/
More information from JBQ: http://groups.google.com/group/android-building/msg/58cf11cfcbc46946
Seems they *could* be different software configurations and perhaps *could* be different hardware configurations but no definite answer ...
Would be interesting to find out what the real differences are between these devices!
nfoman said:
Hmm i have the D version and my product name is yakjuux. I got the phone today and am with Bell. Searched the forum and no results came up with that product name.
Click to expand...
Click to collapse
Pretty sure that it's just the code for the Canadian version of the phone. My Bell phone is the same product name. I haven't seen any updates on mine either but I haven't seen any volume bug happen on mine either.
I have a yakjuxw. This morning I was presented with an update from Samsung. I downloaded it and installed. It booted to the android with a red bang box over him but did nothing. I am rooted and have CWM installed. I pulled battery and booted phone again. Copied the /cache/yakjuxw_update_I9250xwkk5_ITL41D_to_I9250XWKK9_ITL41F.zip to my /sdcard rebooted to CWM and installed from SDCARD. Updated worked rebooted and I am now on 4.01 Build Number ITL41F.I9250XWKK9. I am using this with AT&T in the US. I have lost root and cwm recovery. Which I would guess is expected. Am on my chromebook right now and can't reroot. Will update once I have a computer.
knects said:
I have a yakjuxw. This morning I was presented with an update from Samsung. I downloaded it and installed. It booted to the android with a red bang box over him but did nothing. I am rooted and have CWM installed. I pulled battery and booted phone again. Copied the /cache/yakjuxw_update_I9250xwkk5_ITL41D_to_I9250XWKK9_ITL41F.zip to my /sdcard rebooted to CWM and installed from SDCARD. Updated worked rebooted and I am now on 4.01 Build Number ITL41F.I9250XWKK9. I am using this with AT&T in the US. I have lost root and cwm recovery. Which I would guess is expected. Am on my chromebook right now and can't reroot. Will update once I have a computer.
Click to expand...
Click to collapse
Same here! I noticed the system update around 2am EST. I'm not rooted and haven't unlocked the device yet. Only information I could gather was the update size of 1.4 MB.
Losing root and recovery is standard for official OTA updates. They usually fine a recursive directory permission setting line for /system/bin for all files at 755 removing the setuid/setgid bit on the su binary.
For flashing back the stock recovery, either it restores the linkage in /system to flash stock recovery on every boot or the OTA had a stock recovery included and loaded during the OTA update process.
Will know for sure after looking at whats included in the OTA .zip.
I accepeted the OTA update, loaded properly through stock recovery and rebooted to show ITL41F. I'm on TMO in the US.
Think you could post up the .zip file, yakjuxw_update_I9250xwkk5_ITL41D_to_I9250XWKK9_ITL41F.zip, from the /cache partition?
Might already be posted somewhere and I missed it. I'm curious to glance through it as the first official ICS OTA.
Do you have to be rooted to see what you are? Because mine says "ro.product.name=mysid
Edit: or is my build the same as yakju?
kbrian said:
Do you have to be rooted to see what you are? Because mine says "ro.product.name=mysid
Edit: or is my build the same as yakju?
Click to expand...
Click to collapse
Do not need root access to view the /system/build.prop file where the device information is kept.
As some custom ROMs do modify these values, it is possible they have been changed. If you've never unlocked the device, the values shouldn't have been modified.
I've never seen the value of "mysid" .. Would be very surprised to see tha value on a stock locked device ..
This issue actually inspired me to write a small application, Build Prop Editor, to view and modify the /system/build.prop file. In order to modify the file, root access is required, but to view the file root access is NOT required. I added a feature called "Device Information" to the main page of the application which grabs the relevant build.prop information and displays it all in one convenient location, which also supports sending the info via email/twitter/etc ...
Hope that helps clarify!
I looked it up and i think it's a Google verizon build or something like that
Edit: A thread i found on it
http://forum.xda-developers.com/showthread.php?t=1376856&page=27
Sorry was traveling. Here is the file from /cache.
Hello,
So I read some different topics on the forums and decided I would "convert" my Yakjuxw Galaxy Nexus to a Yakju one. So I did that, and kinda expected a OTA notice regarding 4.0.2 and got nothing. I've been running the device as a Yakju for 4 days now, and I'm beginning to think I did something wrong while converting it.
My question is though, did I do something wrong since I haven't recieved the OTA?
And what can I do to get the latest ICS version on my Galaxy Nexus while still being able to get OTA updates directly from Google?
Thanks for your time and Merry Christmas (For those of you who celebrate Christmas)
Why don't you just install the 4.0.2 ITL41F stock image from google.
Link : https://dl.google.com/dl/android/aosp/yakju-itl41f-factory-192e5c67.tgz
Hi,
You didn't do anything wrong if your phone still boots! What happens with these updates a lot of the time is they are rolled out in batches, say 5,000 phones at a time. Not all phones will receive the update at the exact same time, and some phones can even go weeks before receiving the update while some phones may already have it. If your phone still boots, you haven't done anything wrong Just a matter of waiting. Or you can install a custom ROM which most of those are already on 4.0.3. This way you can always be on the bleeding edge
Best bet is if you don't mind backing up all your stuff is to simply flash 4.0.2 directly from the link provided by nabiladeeb
Also if you really want to make sure everything is ok do *#*#checkin#*#* from the dialler and download the GN update checker from the market and that will tell you if you are on the stock google build
Stopped rolling out 4.0.2?
I switched my phone from Yakjuxw to Yakju yesterday. I know the 4.0.2 updated rolled out a few days ago. Does anyone know if it's too late to get the OTA update without manually doing it? Anyone get the OTA 4.0.2 after changing in the last couple of days? Want to avoid erasing everything again by unlocking the bootloader...
This has probably been answered before by one or two people, but I'd rather know from the whole lot of you brave souls who have switched from yakjuux to yakju.
I'm specifically wondering from those of you that have done the COMPLETE switchover to the yakju build... that includes ALL things that come with it, including it's radio.
I know we can flash the KL1 radio on top, but I'm not looking to do that. I want the entire thing to be from Google, and keep it as such. From what I understand, when you have the yakju build, and the KL1 radio, you will not get OTA updates automatically, thus having to flash manually. On the flip side, if its a complete yakju, including the radio that comes with it, you will get the OTA updates automatically.
So here's the questions:
1. Have any of you flashed the yakju build on your phones KEEPING THE RADIO that is a part of that build? If so, what are your experiences with reception/data specifically on the Bell Network? Any difference that you've noticed?
2. Am I wrong in my thinking? If you did flash yakju, then the KL1 radio, will you definitely receive OTA updates automatically? As in no real user intervention other than clicking "update"?
I want to be sure before I do this, because I cannot find a complete image of the yakjuux build that includes everything including the bootloader in case something goes wrong/or doesn't update the way a true Google experience should.
Please let me now.
Thanks
I am running stock 4.0.2 with everything from the official image. No problem with signal. What is your worry?
Sent from my Galaxy Nexus using XDA App
superlj said:
I am running stock 4.0.2 with everything from the official image. No problem with signal. What is your worry?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Just want to make sure the radio from the official build works properly with Bell.
Don't really want to create a Frankenstein build so too speak by adding different radios
Sent from my Galaxy Nexus using Tapatalk
I changed mine to yakju shortly after I got the phone, about two weeks ago.
I haven't noticed any difference with the radio, good or bad. Still no issues with reception or anything dropping out.
Can't tell you about the OTA updates though, haven't received anything yet to go past 4.0.2. If/when I do, I'll update my reply to help everyone else out.
torradan said:
I changed mine to yakju shortly after I got the phone, about two weeks ago.
I haven't noticed any difference with the radio, good or bad. Still no issues with reception or anything dropping out.
Can't tell you about the OTA updates though, haven't received anything yet to go past 4.0.2. If/when I do, I'll update my reply to help everyone else out.
Click to expand...
Click to collapse
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
greeced said:
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
Click to expand...
Click to collapse
bump. bump.
why are you so worried about receiving ota automatically? since you are on xda and know how to flash you will always have the latest build. Being in canada we usually are slow to get updates(Galaxy Nexus is still on 4.0.1 here) so whats the point in waiting for ota. if you are planning to flash an update now why not do it again when a new one comes out.
btw to answer your questions about the radio, the stock one,XXKK6, will work fine with bell although UGKL1 seems to work better for me on Fido. UGKL1 is probably the radio that your phone has now. it was on my stock fido GN.
I flashed the entire package, including the xxkk6 radio.. Works perfectly fine on Rogers, no comment for Bell but should be fine. Just try it, flash it back if you don't like it. Takes all of 2 minutes.
From what I understand (and I'm still new to this as well) you need to use the radio that comes with the official image otherwise you won't get OTA updates associated with that rom.
Newbie account so I can't post links yet but search "galaxy nexus upgrade to official roms yakju build" and its the leemn wordpress blog that says:
"After flashing to yakju build, you can still receive notification of the OTA updates.If you have flashed the radio, system, userdata and boot partitions, and you still have the stock recovery (or have flashed it) from the 4.0.2 image, you will be able to install the updates. However, if you flash a different radio, or different kernel , or a custom recovery, you will need to flash back the stock ones first before being able to install the update."
That's the whole thing.
When I was on the SGS, I tried a while slew of custom roms as well as the European beta builds.
I wasn't worried about doing that because there was always a way to go back to KG3, by spoofing the firmware to make KIES think it was on JL2. KIES would download KG3 officially back to the phone.
I always seemed to revert back to stock because none of the beta or custom roms seemed to work efficiently for me the way the stock one did.
I know, I'm strange.
So that experience brings me here. Without an official download of the yakjuux build available (bootloader image), there really is no going back if something just doesn't work as intended. (remember, we all use our phones differently).
That's why the fright. I just don't want to get to the point that this Canadian incarnation starts having an identity crisis.
Sent from my Galaxy Nexus using Tapatalk
I flashed it all.
Works great. No issues. I also wanted 100% stock and so far, i am very happy with it.
greeced said:
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
Click to expand...
Click to collapse
Sorry missed your question, but I'm using the KL1 radio.
I am with Fido and have complete 4.0.2 stock rom. I had some strange issues with signals but everything is fine after I changed to a new SIM.
Sent from my Galaxy Nexus using XDA App
greeced said:
That's the whole thing.
When I was on the SGS, I tried a while slew of custom roms as well as the European beta builds.
I wasn't worried about doing that because there was always a way to go back to KG3, by spoofing the firmware to make KIES think it was on JL2. KIES would download KG3 officially back to the phone.
I always seemed to revert back to stock because none of the beta or custom roms seemed to work efficiently for me the way the stock one did.
I know, I'm strange.
So that experience brings me here. Without an official download of the yakjuux build available (bootloader image), there really is no going back if something just doesn't work as intended. (remember, we all use our phones differently).
That's why the fright. I just don't want to get to the point that this Canadian incarnation starts having an identity crisis.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm not sure what the problem is. When you unlock your bootloader, you just do a nandroid backup, and it backups up your system, data, recovery and boot partitions. The radio is already available. So you can always go back to "stock" yakjuux in case yakju doesn't work (which it obviously does for Canadian users). I've even posted a nandroid backup of my yakjuux build before I flashed yakju. There is a thread in the general section. And to address your concern about "always reverting to stock", yakju IS the stock ROM, it is not a beta or a custom ROM.
The bootloader has nothing to do with yakju or yakjuux or whatever. It will not affect anything related to getting an OTA update or installing an OTA update. Keep your current bootloader if you are worried about not having a backup, and go ahead and flash all of the other images (after backing up your originals of course). That way, you can always return to your yakjuxx if you think there is a problem. Just because you didn't flash the bootloader that came with the latest yakju image does not at all mean you are not using yakju, and I would not call it a "frankenbuild" -- think of the bootloader as the BIOS in a computer. You computer is running Windows regardless if you are using an ASUS P5Q motherboard, or an ABIT IP5 motherboard -- both have different BIOS, but the OS is still Windows. Same with a GN -- you are running yakju regardless of whether you bootloader is 10, 14, 15, etc.
EDIT: To specifically address your question number 2 -- if you flash the system, data and boot images from yakju, you are running yakju, and you will receive the notification for an OTA update when it is available. However, you will not be able to have it install automatically if you don't have the radio image that came with the yakju build and a stock recovery (they are all the same). You can, however, flash those back as soon as you receive the OTA update notification and it will install automatically. Bootloader has no relevance whatsoever.
Great explanation. Thank you efrant. You've answered everything I've needed to know
Sent from my Galaxy Nexus using Tapatalk
Well finally took the plunge and went to yakju from yakjuux. Although my experience wasn't as seemless as everyone elses, so I thought I'd tell everyone just in case someone else runs in to the same problem.
For starters: I followed efrants excellent procedure from this exact post. However it also must be noted that I decided to use the 41F (4.0.1) firmware from Google's images instead of the 53F (4.0.2) image. I did this because I wanted to experience an update. lol
Now, at first I had to try several drivers in order for my Windows 7 laptop to even see the phone with the "fastboot devices" command. I finally found one that works. Coincidentally, one driver will work on one machine, but won't on the next, I have no idea why. After finally getting the right one, I proceeded:
I did all steps to the letter, but skipped steps 4,5 and 12, as the post says they were optional and I didn't really want to lose my bootloader and recovery in case I wanted to revert back to yakjuux.
After completing all steps but those, I did the final "fastboot reboot" and the phone restarted.
Here's where the ride began:
When it restarted, it seemed like everything was fine. It took a while to find Bell's settings, but it was ok. It then said an update to 4.0.2. was available.
Upon the reboot and install, the phone shut off, and rebooted twice, after the second time, I had an android on the ground with its chest open and a RED exclamationed triangle above it. My thoughts were "uh oh". I waited and waited, and nothing was happening. Pressing power and holding it down, wouldn't help.... After approx 5 mins I was about to do a battery pull, and it restarted itself, but remained on the 41F update.
Each restart would say it was upgrading, but never did.. always stayed on 41F.
So I went back and did everything in the procedure, not omitting anything this time (goodbye yakjuux bootloader!) and it went off without a hitch... This time my android figure was standing up, very much alive and getting a heart transplant.
So here I am.. Yakju configured and using the yakju KK6 radio. All seems well. Haven't decided if I'm going to put the KL1 radio on as yet, but thats for another day.
Thanks again efrant for all your help and patience with me.
@greeced Welcome to yakju. I doubt you will ever go back to yakjuux.
Sent from my Galaxy Nexus using Tapatalk
Well, I have been on yakju for a few days now and I can say no problems whatsoever.
At first I felt as if it was slightly Laggy, but that seemed to correct itself after a day or so. Not sure why, but the phone is just as quick as before now.
As for the radio, I wanted to stay completely stock, and that included the radio. So my phone is running the stock KK6 that came with the update, and I noticed my DBM levels are just as good as before if not better. So I don't feel the need to flash KL1.
Overall very happy that I'm now Pure Google.
One thing to note:
When I was on my SGS, I always factory reset after every flash, which always seemed to speed up the experience of the new ROM.
I think that should be the case for all firmware updates, including googles.
It's a painful process to redo everything, but well worth it in my opinion.
I mean think about it, installing a fresh copy of windows always performs better than doing an upgrade of windows, so that should be the same here.
We are dealing with computers after all.
At any rate. Just thought I'd update my experience in case anyone else who is on bell felt apprehensive like me.
Sent from my Galaxy Nexus using Tapatalk
greeced said:
Well, I have been on yakju for a few days now and I can say no problems whatsoever.
At first I felt as if it was slightly Laggy, but that seemed to correct itself after a day or so. Not sure why, but the phone is just as quick as before now.
Click to expand...
Click to collapse
I think the general consensus is that ICL53F is more laggy that ITL41F or ITL41D, so it is not a yakju vs yakjuux issue, it is a 4.0.1 vs 4.0.2 issue.
greeced said:
As for the radio, I wanted to stay completely stock, and that included the radio. So my phone is running the stock KK6 that came with the update, and I noticed my DBM levels are just as good as before if not better. So I don't feel the need to flash KL1.
Click to expand...
Click to collapse
Radio performance varies with a huge number of factors. If you are happy with how one radio works, use it. If you want to see if another one is better, try it. If you don't like it, flash back. It takes all of 30 secs to flash a radio.
greeced said:
[snip]
When I was on my SGS, I always factory reset after every flash, which always seemed to speed up the experience of the new ROM.
I think that should be the case for all firmware updates, including googles.
It's a painful process to redo everything, but well worth it in my opinion.
I mean think about it, installing a fresh copy of windows always performs better than doing an upgrade of windows, so that should be the same here.
Click to expand...
Click to collapse
If you believe this, then I suggest that you do not flash older builds and OTA update to a newer ones. This process adds more files to your ROM, and is not as clean as flashing the latest build from Google's factory image site.
When the next version of Android is released, the full version will likely be available on Google's factory image site shortly before OTA's for yakju start rolling out.* If you don't mind redoing your settings, apps, etc., it is better (and faster) to flash the full build, instead of updating your current build.
*My assumption based on release dates for previous versions.
Question efrant.
I relocked my bootloader purposely.
If I wanted to test other radios does the bootloader need to be unlocked?
If it does, no big deal, I just won't do it
Sent from my Galaxy Nexus using Tapatalk
Hi all,
I just received a new GNex from Vodafone Australia. Can someone please help me figure out which version I have so I can update it?
I am running 4.0.4 (rooted)
The Baseband is:
I9250TDVLE1
The build is:
IMM76K.I9250TDVLE1
I could not find an update on google anywhere...
I found reference to my build pertaining to Toro, Magro and Verizon.
I can't see how all of these could be simultaneously true...
I thought '**** it' I ll roll back to a yakju 'official' 4.0.4 IMM76I ROM from here and then flash the Update to 4.1.1 JRO03C
But When I booted into CWM and tried to flash the imm76i, it would not let me. Is there something I am doing wrong or do not understand about swapping roms...?
(I cleared the cache / factory reset)
Am I stuck with IMM76I until google makes an 4.1.1 update, or can I flash another google rom somehow and get the update that way?
Cheers
ac17 said:
Hi all,
I just received a new GNex from Vodafone Australia. Can someone please help me figure out which version I have so I can update it?
I am running 4.0.4 (rooted)
The Baseband is:
I9250TDVLE1
The build is:
IMM76K.I9250TDVLE1
I could not find an update on google anywhere...
I found reference to my build pertaining to Toro, Magro and Verizon.
I can't see how all of these could be simultaneously true...
I thought '**** it' I ll roll back to a yakju 'official' 4.0.4 IMM76I ROM from here and then flash the Update to 4.1.1 JRO03C
But When I booted into CWM and tried to flash the imm76i, it would not let me. Is there something I am doing wrong or do not understand about swapping roms...?
(I cleared the cache / factory reset)
Am I stuck with IMM76I until google makes an 4.1.1 update, or can I flash another google rom somehow and get the update that way?
Cheers
Click to expand...
Click to collapse
That's because the package you downloaded on Google's Developers website needs to be flashed using fastboot, not CWM. Follow this thread to flash back to yakju, and you should be good to go.
Did this work for you? as i have the same phone and im tempted to do this but not if its going to mess the phone up. Damn you vodafone for having to be different
Rayzor76 said:
Did this work for you? as i have the same phone and im tempted to do this but not if its going to mess the phone up. Damn you vodafone for having to be different
Click to expand...
Click to collapse
It would definitely work however if you even need to return your phone back to Vodafone, you may or may not run into some issues due to not being on their ROM. It's pretty hard to find random stock ROMs for places other than the main ones these days (or I just might be looking at the wrong places).
Rayzor76 said:
Did this work for you? as i have the same phone and im tempted to do this but not if its going to mess the phone up. Damn you vodafone for having to be different
Click to expand...
Click to collapse
I'm sorry, I can't remember what I did, but I fixed it that night, which now feels like months ago.
I installed Nexus Root Toolkit v1.5.2, on a pc and I know that that helped me speed up the process.
You can't ruin anything unless you flash a rom not designed for the phone, or format the bios partition and then reboot (with out installing a new bios), but even then I'm sure you can install stuff from a pc over usb using that program.
ac17 said:
I'm sorry, I can't remember what I did, but I fixed it that night, which now feels like months ago.
I installed Nexus Root Toolkit v1.5.2, on a pc and I know that that helped me speed up the process.
You can't ruin anything unless you flash a rom not designed for the phone, or format the bios partition and then reboot (with out installing a new bios), but even then I'm sure you can install stuff from a pc over usb using that program.
Click to expand...
Click to collapse
Thanks New to Android as I have been an avid iOS user and jailbreaker for a few years so just catching up on rooting and flashing ROMs n stuff. But good to know it can be done as i Have the exactly same phone from Vodafone Australia. Better to be safe than sorry and ruining a 2 day old phone.
Rayzor76 said:
Thanks New to Android as I have been an avid iOS user and jailbreaker for a few years so just catching up on rooting and flashing ROMs n stuff. But good to know it can be done as i Have the exactly same phone from Vodafone Australia. Better to be safe than sorry and ruining a 2 day old phone.
Click to expand...
Click to collapse
No worries mate, this is my 2nd android phone (first was a nexus s).
I learned a lot by rooting and playing with custom roms on that ph, but I have been really happy with stock jelly Bean on this (albeit rooted) device. Battery life is great, and it's a snappy phone with great features.
FYI I just read an interesting article Why Apple Won't Divorce Samsung today that explained how Samsung make all the chips for Apple products. You can't go wrong with Samsung mate.
Android users on this forum are generally friendly and Damn knowledgeable too.
Enjoy your new phone!
ac17 said:
Hi all,
I just received a new GNex from Vodafone Australia. Can someone please help me figure out which version I have so I can update it?
I am running 4.0.4 (rooted)
The Baseband is:
I9250TDVLE1
The build is:
IMM76K.I9250TDVLE1
I could not find an update on google anywhere...
I found reference to my build pertaining to Toro, Magro and Verizon.
I can't see how all of these could be simultaneously true...
I thought '**** it' I ll roll back to a yakju 'official' 4.0.4 IMM76I ROM from here and then flash the Update to 4.1.1 JRO03C
But When I booted into CWM and tried to flash the imm76i, it would not let me. Is there something I am doing wrong or do not understand about swapping roms...?
(I cleared the cache / factory reset)
Am I stuck with IMM76I until google makes an 4.1.1 update, or can I flash another google rom somehow and get the update that way?
Cheers
Click to expand...
Click to collapse
OK. The fact is that Vodafone and Telstra get all their updates later. This is because of the better 3g signals they have built in the phone. So due to this their updates come out a little while later. Also it depends where you are in the world (eg. UK, AU, USA) because the UK has already got the update as far as I know. So there is two options here to stay with Vodafone if something does go wrong so you have a backup. And referring to what Unlawful had said he is right you do need a stock Vodafone ROM or features and such can go wrong. BTW I am also with Vodafone but running a custom ROM.
Thank mate. I updated it manually, months ago.
The Gnex is an awesome phone (I upgraded from a NEXUS S), and with stock jelly Bean (rooted) with stock kernel it runs smoothly and is stable.
I miss rge Wolfson audio chip of the nexus s though bc audio recordings are terrible and crackling with the gnex.
Fast charge is something that I now need and otherwise I'm satisfied!
So I have a small question...
I have a Galaxy Nexus, had it since day 30 or so. Updated OTA many times and rooted every time, using the stock ROM so everything is perhaps more simple.
The lady friend has also got a GN. Her phone downloaded the OTA update and is now bugging her to install. She purchased her phone only a couple of months ago. We're on the same build number but my GN won't see the update to 4.2.
Is there a reason for this? Did Google pull the update once they have figured out the December bug and haven't yet fixed it?
I am a little worried as I used the Galaxy Nexus Toolkit to root my 4.1.2 phone but as the toolkit wasn't updated, I used the settings for 4.1.1. I am certain I did this to my partners phone too, but that is the only thing I can think of as to why I haven't got the update.
I'm not totally desperate for it, but just wondering why.
Thanks
anotherxdauser said:
So I have a small question...
I have a Galaxy Nexus, had it since day 30 or so. Updated OTA many times and rooted every time, using the stock ROM so everything is perhaps more simple.
The lady friend has also got a GN. Her phone downloaded the OTA update and is now bugging her to install. She purchased her phone only a couple of months ago. We're on the same build number but my GN won't see the update to 4.2.
Is there a reason for this? Did Google pull the update once they have figured out the December bug and haven't yet fixed it?
I am a little worried as I used the Galaxy Nexus Toolkit to root my 4.1.2 phone but as the toolkit wasn't updated, I used the settings for 4.1.1. I am certain I did this to my partners phone too, but that is the only thing I can think of as to why I haven't got the update.
I'm not totally desperate for it, but just wondering why.
Thanks
Click to expand...
Click to collapse
Nobody really knows (afaik) how Google decides which Nexus devices get OTA updates first. I'm pretty sure it has nothing to do with how 'old' your device is though. And having root won't affect the OTA update, don't worry. You do need stock recovery though.
Stock recovery?
I don't have anything like CWM installed. My phone is completely stock apart from rooted
Might try re-rooting using the Toolkit as my phone version (just in case) and then just wait I guess. Just a shame it won't see the update as I would have thought once they set the server to show there is a new version, all devices would see it... just like Windows Update for instance.
Man up and do it the right way..
Refer to the root sticky in the Q&A section by Jubakuba..
Beamed from my Grouper.