Develop Bugs

Google abandons CDMA (for developer devices)

From techeye:
http://news.techeye.net/mobile/google-abandons-cdma?
CDMA is marked "archived, for reference only"
http://code.google.com/android/nexus/images.html
I guess that finally nails the Verizon Galaxy Nexus as a carrier-phone. Next time buy a truly free & open device (i.e. GSM)
Seriously though. This Galaxy Nexus launch and follow-up has to be the messiest thing I've ever since Google set its foot into. From launch, to providing international release-dates, to US promotion, to handling updates, to releasing buggy updates, to pulling them, to general PR.
It's all been a big ****ing mess.
Is this the sign of the start of the end of the Nexus program or what? Or is leaving closed CDMA networks and carriers behind actually a sign of a new, better start?
Discuss.

Welcome to last week.
Sent from my Galaxy Nexus

Edit: Rootzwiki seems to have something more to offer than the techeye article.
http://rootzwiki.com/_/articles/ann...dma-galaxy-nexus-will-continue-to-update-r374
Still not crystal clear, and definitely falls under my definition of messy PR.
The rootzwiki even has an update, because Google has messed up its correcting response and needs to correct itself, again.

Yeah this is old news. Plus the 4.0.4 update is out for the VZW. What's it like beating a dead horse lol?
Sent from my Gummy Nexus

http://forum.xda-developers.com/showthread.php?t=1479199
Sent from my Galaxy Nexus

Funny thing is how the 'abandoned' device is getting more frequent updates than e officially supported device. We still don't have 4.0.3 officially yet (the last relapse is officially the Nexus S one), and 4.0.4 is CDMA only.
Welcome to last week, BTW.

Omg. Not only does it keep being reposted but by people who don't even understand what's going on and say things like " next time buy a truly free and open device".
Sent from my 'closed' 4.0.4 CDMA Galaxy Nexus.

matt30 said:
http://forum.xda-developers.com/showthread.php?t=1479199
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Hm. Should have searched the forum better it seems. I didn't find it before posting. Anyway. The conclusion from that thread still seems to be incredibly messy.
Can anyone tell WTH it now does mean to be a "Nexus" device? Ever since the release of the Galaxy Nexus and its "evil" CDMA counter-pair, that definition seems to have been in a flux.

Haesslich said:
Welcome to last week, BTW.
Click to expand...
Click to collapse
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free

http://androinica.com/2012/02/cdma-...l-dev-support-updates-still-come-from-google/
Sent from my Gummy Nexus

josteink said:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
Click to expand...
Click to collapse
Don't talk about what you do not comprehend. That is the most ignorant thing I have heard in a long time.
I too can build 4.0.3 for CDMA. So go get educated.

adrynalyne said:
I too can build 4.0.3 for CDMA. So go get educated.
Click to expand...
Click to collapse
Good. Reading Google's various statements on the matters it seems like you cannot though, so excuse me for thinking otherwise.
So again. Yay for Google's handling of this

josteink said:
Good. Reading Google's various statements on the matters it seems like you cannot though, so excuse me for thinking otherwise.
So again. Yay for Google's handling of this
Click to expand...
Click to collapse
If my understanding is correct, you need to build 4.0.3 with the proprietary files (binaries) contained in a working cdma build of the device (what Google has called "apks"). Since those files are closed source, they cannot be included in AOSP.
Why those cdma files are closed source is a mystery. It could be for legal reasons or it could be because of the way cdma networks communicate with devices (requiring them to have a signature from the carrier embedded in them).
Sent via Galaxy Nexus

The proprietaries are all closed source. GSM included. Looks like Google couldn't obtain a license to distribute is the whole problem. Hence they also axed the factory images, because it was a form of redistribution of them as well.

adrynalyne said:
The proprietaries are all closed source. GSM included. Looks like Google couldn't obtain a license to distribute is the whole problem. Hence they also axed the factory images, because it was a form of redistribution of them as well.
Click to expand...
Click to collapse
And cmda (and I guess the proprietary software) is owned by a working group of several different telecom companies.
Sent via Galaxy Nexus

josteink said:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
Click to expand...
Click to collapse
how does what feel? unless you are just into foreign flags you will never use a cdma phone from verizon. looking at this logically you are either seeking attention or trolling. either way its sort of pathetic but i guess its winter over there and you havent much to do.

sahakiap said:
how does what feel? unless you are just into foreign flags you will never use a cdma phone from verizon. looking at this logically you are either seeking attention or trolling. either way its sort of pathetic but i guess its winter over there and you havent much to do.
Click to expand...
Click to collapse
At first I was trying to get some news out. And discussion about Google's general handling of the Nexus-line this time around and how it hasn't exactly been "optimal".
But I guess that got lost in everyone picking up on the snide remark rather than the rest of the comment.

josteink said:
At first I was trying to get some news out. And discussion about Google's general handling of the Nexus-line this time around and how it hasn't exactly been "optimal".
But I guess that got lost in everyone picking up on the snide remark rather than the rest of the comment.
Click to expand...
Click to collapse
Thanks for posting josteink. I hadn't seen it before either. Not sure why everyone is getting their feathers ruffled when you clearly put a smiley face beside the comment. And besides, those that are posting saying it is old news keep bumping the thread...

josteink said:
Thanks. But even skimming the forums several times during the weekend this one never entered the FP of General while I was reading it.
How does it feel? At least we have source access which we can use to build a working phone image, running 4.0.3. Which is more than you can say about the 4.0.4 release.
So yeah, feels good, open and free
Click to expand...
Click to collapse
There is no source release of 4.0.4 yet but I have been on 4.0.3 since the day I got my phone.
How does it feel? It feels great to have 32GB of space on my phone and get an average 20Mbps downstream. (At times reaching 40Mbps+)

This isn't old news at all and it is a big deal. A lot of people got screwed here by both Google and Verizon. Not having official AOSP support for developer nexus phone is unacceptable. If there were code distribution issues, then Google should have worked that out way before the official launch. I'm still holding out hope that this will be resolved, but at this point i'd settle for just getting out of my contract and moving over to the GSM variant.
On a related note, I wish CDMA would just fade away into a bad memory.

Time to start a campaign

That being, a campaign of Twitter and G+ posts to try and get some form of response from Google about the next OTA for the Galaxy Nexus, or at least some transparency on where they are up to with the release.
I am thinking a hashtag like #NexusOTA

Let's pretend i'm a big person at Android team. I can realease ICS 4.0.5 for you tomorrow, but it'll have nearly same issues as 4.0.3. Do you really want it? I don't.
Next version of ICS will be out as soon as it's ready!

I think what scottatron is saying is why the heck do they take so long...be transparent about at what stage of development they're up to and give us an estimate of when is ready...I mean a the whole premise of a Google phone is the continuing update and support, they can be more open and up front about it
Sent from my Galaxy Nexus using Tapatalk

leonironchef said:
I think what scottatron is saying is why the heck do they take so long...be transparent about at what stage of development they're up to and give us an estimate of when is ready...I mean a the whole premise of a Google phone is the continuing update and support, they can be more open and up front about it
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Pretty much spot on.

I agree, there are enough issues to warrant releases. And some regions have yet to get an OTA release. Seems odd given ICS was intended to simplify development by making it platform independent.

Scottatron said:
That being, a campaign of Twitter and G+ posts to try and get some form of response from Google about the next OTA for the Galaxy Nexus, or at least some transparency on where they are up to with the release.
I am thinking a hashtag like #NexusOTA
Click to expand...
Click to collapse
Here's the thing... Either you really care that much about being up to date on 4.0.3/4.0.4 instead of 4.0.2, and you just flash a custom ROM; OR you don't care that much and you should be happy with 4.0.2 and it'll be OTAd as soon as it's ready.
Chill. No one is going to do this and no one will listen. You think that Googlers are going to see a bunch of tweets and be like "omg I guess we should start coding this next OTA release! We'll stop slacking!". Good lord, people...
They're not going to release the OTA until its ready. I'd take a 4.0.4 that's fully baked rather than a 4.0.3 that has some fixes and leaves bugs... and another OTA to 4.0.4 after that to fix the rest.

Didn't they run into more problems by giving ETA's and then missing them?

VaKo said:
Didn't they run into more problems by giving ETA's and then missing them?
Click to expand...
Click to collapse
Pretty much. Everyone wants ETA's... until they start giving ETA's that can't be met and/or the ETA's are considered too far in the future.
Pretty much Google will be scolded by whiney kids either way.

martonikaj said:
Here's the thing... Either you really care that much about being up to date on 4.0.3/4.0.4 instead of 4.0.2, and you just flash a custom ROM; OR you don't care that much and you should be happy with 4.0.2 and it'll be OTAd as soon as it's ready.
Chill. No one is going to do this and no one will listen. You think that Googlers are going to see a bunch of tweets and be like "omg I guess we should start coding this next OTA release! We'll stop slacking!". Good lord, people...
They're not going to release the OTA until its ready. I'd take a 4.0.4 that's fully baked rather than a 4.0.3 that has some fixes and leaves bugs... and another OTA to 4.0.4 after that to fix the rest.
Click to expand...
Click to collapse
best response ever...
As my friend here said "Good lord, people..." If you must have the latest flash the leaked 4.0.4 and be done with it.
And exactly what are you waiting for in the next release? what major issues do you have with 4.0.2?

Why are you on xda developers if you're not doing anything with your phone? There is plenty of forums that are just about stock nexus and that's where you should be .... I bought this phone for one reason only custom roms and always compatible roms. If I'd be you I'd buy HTC or other Samsung device and than whine for ota
Sent from my Galaxy Nexus using xda premium

Xda is a help line didn't you know?
Sent from my Galaxy Nexus using xda premium

MattSkeet said:
Why are you on xda developers if you're not doing anything with your phone? There is plenty of forums that are just about stock nexus and that's where you should be .... I bought this phone for one reason only custom roms and always compatible roms. If I'd be you I'd buy HTC or other Samsung device and than whine for ota
Click to expand...
Click to collapse
Some people (like myself) chose to buy a Nexus because it offers you the freedom to choose whether or not you want to root/hack/ROM your phone. I primarily bought the Nexus because I was tired of rooting/ROMing being the only option I had to get a near-AOSP experience with the features I wanted.
It's okay to not root, just don't complain about OTAs if you choose not to. Similar to my previous post -- if you care enough to be following 4.0.x releases, you should not complain about the quickness of your OTAs imho. Part of choosing to stay stock is dealing with the OTA release schedule. There are pros and cons to both sides. If you really want OTAs on your schedule, you just have to do the work and manually make it happen.

This is starting to remind me of the Nexus One and the froyo release. People are freaking out because they aren't getting nightly builds from Google.
Grow up.
Sent from my Galaxy Nexus using XDA Premium HD app

Another one star thread, pro.
Just help yourself and root your phone, then we don't have to read these pointless threads.
95% of people here respond as they do because the could care less about OTA's because we install custom ROMs.

now I feel bad for the op.
but to quote meryl streep, whatev.

martonikaj said:
Some people (like myself) chose to buy a Nexus because it offers you the freedom to choose whether or not you want to root/hack/ROM your phone. I primarily bought the Nexus because I was tired of rooting/ROMing being the only option I had to get a near-AOSP experience with the features I wanted.
Click to expand...
Click to collapse
That's pretty much why I got a Nexus One and stuck with the brand. While the ROM scene is pretty cool I really can't be bothered to spend my life messing around with my primary phone (got sick of that back in the WinMob days), I'd rather have something which just works and doesn't have a 6 month lag for updates due to OEMs and carriers dicking about with the software. But I like hanging about on XDA because it's the first place I'll hear about OTA's and the first place I'll hear about something which will make me re-think my "can't be bothered with custom ROM's" stance.

Boohoo it'll come when it comes. Just stay calm, relax, and enjoy the beauty of the phone.
Sent from my Galaxy Nexus using xda premium

why do u guys think google is just sitting on its ass and not developing. id rather have something finished than something half baked.
4.0 is a drastic new os, it takes time to develop these things.

What Google needs to do for the Nexus lineup is what they do with Google Chrome, they should have a Stable channel a Beta channel and a developer channel that you can pick from for your updates.

These threads are getting annoying. You bothered to make an account on XDA and you bought a Nexus device, ROOT IT.
Also, Google isn't obligated to give you anything but the latest Official version of Android via source, they don't have to give you an OTA and before you go on and say "the nexus program is all about being first" ITS NOT. Its about establishing a standard for manufacturers and developers to build upon not for some end user to ***** and complain about a small revision change that he doesn't have.
You have Android 4.0
No other phone has Android 4.0
SO SHUT UP AND BE HAPPY
Sent from my Galaxy Nexus using XDA

Android 4.0.4 for SGN (LTE) - When?

Hello forum-goers and fellow SGN owners and enthusiasts,
Last time I read anything about a possible OTA for 4.0.4 for the Verizon LTE SGN, it was the week before St. Patty's Day weekend, and said that there might be an OTA that weekend. Well, it's past. I've been combing through the threads and I don't see a definite, or even a rumor, thread about this OTA update.
I know it's on Verizon to finally approve it. Samsung and Google have given it their approval, although we know Google is still improving it on a day-to-day basis. Has anyone heard anything new about a possible date/date-range/fiscal quarter upon which this future-well-received update might be sent out?
I appreciate any and all positive discussion, and I'm sure the mods will clean up any negative comments. I do apologize for creating another thread (if one exists), but like I said, I didn't see any recently. Thank you.
xXTERMIN8RXXx

xXTERMIN8RXXx said:
Hello forum-goers and fellow SGN owners and enthusiasts,
Last time I read anything about a possible OTA for 4.0.4 for the Verizon LTE SGN, it was the week before St. Patty's Day weekend, and said that there might be an OTA that weekend. Well, it's past. I've been combing through the threads and I don't see a definite, or even a rumor, thread about this OTA update.
I know it's on Verizon to finally approve it. Samsung and Google have given it their approval, although we know Google is still improving it on a day-to-day basis. Has anyone heard anything new about a possible date/date-range/fiscal quarter upon which this future-well-received update might be sent out?
I appreciate any and all positive discussion, and I'm sure the mods will clean up any negative comments. I do apologize for creating another thread (if one exists), but like I said, I didn't see any recently. Thank you.
xXTERMIN8RXXx
Click to expand...
Click to collapse
Google Android 4.0.5. Latest news indicates that it is being tested now and should be released to us sometime in April.

JayDaKissEP said:
Google Android 4.0.5. Latest news indicates that it is being tested now and should be released to us sometime in April.
Click to expand...
Click to collapse
You know, I heard bits and pieces of 4.0.5. being worked on... this is good news. Thanks!

xXTERMIN8RXXx said:
Hello forum-goers and fellow SGN owners and enthusiasts,
Last time I read anything about a possible OTA for 4.0.4 for the Verizon LTE SGN, it was the week before St. Patty's Day weekend, and said that there might be an OTA that weekend. Well, it's past. I've been combing through the threads and I don't see a definite, or even a rumor, thread about this OTA update.
I know it's on Verizon to finally approve it. Samsung and Google have given it their approval, although we know Google is still improving it on a day-to-day basis. Has anyone heard anything new about a possible date/date-range/fiscal quarter upon which this future-well-received update might be sent out?
I appreciate any and all positive discussion, and I'm sure the mods will clean up any negative comments. I do apologize for creating another thread (if one exists), but like I said, I didn't see any recently. Thank you.
xXTERMIN8RXXx
Click to expand...
Click to collapse
Get it here and install it yourself...

It's coming out tomorrow
Sent from my Galaxy Nexus

bwcorvus said:
It's coming out tomorrow
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Really? Source? Or are you just trolling?

weirddan455 said:
Really? Source? Or are you just trolling?
Click to expand...
Click to collapse
Trolling. Because people have been making these threads for about a month straight now...

weirddan455 said:
Really? Source? Or are you just trolling?
Click to expand...
Click to collapse
Source: My magic 8-ball told me.
Sent from my Galaxy Nexus

bwcorvus said:
Source: My magic 8-ball told me.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thank you!
I was starting to get a headache reading some of these threads/posts and you turned my frown upside-down, lol.

efrant said:
Get it here and install it yourself...
Click to expand...
Click to collapse
I appreciate the link, eFrant, but I don't want to root and unlock the bootloader. My problem, but I'm a busy guy. I'll think about it in the coming months, when I'll have more time to read up on it and tinker with it. In the meantime, my tablet serves as a dev-mod experiment test subject, but even then, I don't have the time to find a suitable ICS rom for that.

bwcorvus said:
It's coming out tomorrow
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I've seen this post be posted before. Safe to say, I'm not an idiot. Thank you for the trite bit of humor, though, chap.

xXTERMIN8RXXx said:
I appreciate the link, eFrant, but I don't want to root and unlock the bootloader. My problem, but I'm a busy guy. I'll think about it in the coming months, when I'll have more time to read up on it and tinker with it. In the meantime, my tablet serves as a dev-mod experiment test subject, but even then, I don't have the time to find a suitable ICS rom for that.
Click to expand...
Click to collapse
Well, you don't have to unlock your bootloader, and you don't really even have to root. All you need is to just get temporary root access to place the update in the right directory. Takes all of 2 mins. But I don't have time to guide you through it right now.
Sent from my Galaxy Nexus using Tapatalk

xXTERMIN8RXXx said:
I appreciate the link, eFrant, but I don't want to root and unlock the bootloader. My problem, but I'm a busy guy. I'll think about it in the coming months, when I'll have more time to read up on it and tinker with it. In the meantime, my tablet serves as a dev-mod experiment test subject, but even then, I don't have the time to find a suitable ICS rom for that.
Click to expand...
Click to collapse
Okay... then just wait for the OTA.

it'll be release when theres 10 new threads a day on xda asking when the Verizon nexus us going to get 4.0.4. Calling google names and saying their devs are lazy and useless will speed it up too

bwcorvus said:
It's coming out tomorrow
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Funny thing is that the 4.0.4 source came out today (this posts Tomorrow)
Sent from my Galaxy Nexus using xda premium

neotekz said:
it'll be release when theres 10 new threads a day on xda asking when the Verizon nexus us going to get 4.0.4. Calling google names and saying their devs are lazy and useless will speed it up too
Click to expand...
Click to collapse
I didn't do any of that, except for posting another thread about 4.0.4. I'm sorry, people don't label their threads very well around here. And tags are a bit of a nightmare when I searched... please, can you ever forgive me?
xXTERMIN8RXXx

efrant said:
Well, you don't have to unlock your bootloader, and you don't really even have to root. All you need is to just get temporary root access to place the update in the right directory. Takes all of 2 mins. But I don't have time to guide you through it right now.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Well, if it's that easy, I'll look into it. Thanks, good sir.
xXTERMIN8RXXx

xXTERMIN8RXXx said:
Well, if it's that easy, I'll look into it. Thanks, good sir.
xXTERMIN8RXXx
Click to expand...
Click to collapse
Do this:
Note: This assumes that you have the drivers for your device installed on your computer.
Step-by-step:
1) Download the attached file to your computer and unzip it in the same directory as your adb.exe file;
2) Open a command prompt in the same directory;
3) Copy the file to your device: adb push mempodroid /data/local/tmp/mempodroid
4) Copy the update to your /sdcard: adb push 659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip /data/media/659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip
5) Open a shell: adb shell
6) Change permission on mempodroid to allow it to run: chmod 777 /data/local/tmp/mempodroid
7) Run the exploit: ./data/local/tmp/mempodroid 0xd7f4 0xad4b sh
Note: Once you do step 7, your prompt should change from $ to #. If not, it did not work.
8) Copy the update to /cache: cat /data/media/659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip > /cache/659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip
9) Reboot into recovery and apply the update.

Here is the CDMA IMM76D 4.0.4 for VZW SGN (Toro) for those of you who can't wait.

WiredPirate said:
Here is the CDMA IMM76D 4.0.4 for VZW SGN (Toro) for those of you who can't wait.
Click to expand...
Click to collapse
Yeah, but that is not an OTA update and, moreover, it is not a stock build...

[Q] Galaxy Nexus ToolKit Has Nexus 7 JB build listed under VZW Toro?

I downloaded the Galaxy Nexus ToolKit the other day and I noticed that under CDMA/LTE Verizon model, after the latest ICS build that I know of for The VZW GN (IMM76k) there is a 4.1 Build JRN84D listed...I looked that build up and it's JB for the Nexus 7 apparently? This confuses me, because I'm pretty sure that the Nexus 7 has drastically different hardware in contrast to the Galaxy Nexus and this Toolkit is apparently SPECIFIC to the Galaxy Nexus (I mean...it's in the name). So why is there a JB build listed in this toolkit for the Nexus 7 UNDER the MYSID-TORO section?
I've one more question as well; before you can even being using the ToolKit it asks you to choose which Model and Build you have. My phone is currently on the Vicious JB 4.1 v5 build and that's not something I'm able to choose. Does that mean I need to go back to stock before I can use this toolkit?
Thanks!

Bump, because it is been a day or so. Or maybe more? I lose track of time sometimes
Sent from my Galaxy Nexus using xda app-developers app

dont use a toolkit.
there is no official JB for the verizon GN.

I'm really not trying to sound like an ass, but you answered two questions that I did not ask. I never asked if I should use a tool kit or not, nor did I ever imply that I thought there was an official verizon wireless jelly bean released yet , and I certainly didn't ask if one existed.
I apologize if there was a misunderstanding, I did not mean to make any misleading remarks or comments.
Sent from my Galaxy Nexus using xda app-developers app

Don't use toolkit
Its pretty simple answer that though don't answer your question but answer to your problems that you might get later.

Soundfx4 said:
I'm really not trying to sound like an ass, but you answered two questions that I did not ask. I never asked if I should use a tool kit or not, nor did I ever imply that I thought there was an official verizon wireless jelly bean released yet , and I certainly didn't ask if one existed.
I apologize if there was a misunderstanding, I did not mean to make any misleading remarks or comments.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm not trying to sound like an ass, but to answer your last question in post #1, no you do not. However, it is obvious that the toolkit is showing you wrong info, so would you trust it? I wouldn't. So, as the others have said, don't use a toolkit. Flash things manually.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
I'm not trying to sound like an ass, but to answer your last question in post #1, no you do not. However, it is obvious that the toolkit is showing you wrong info, so would you trust it? I wouldn't. So, as the others have said, don't use a toolkit. Flash things manually.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I need to apologize; I honestly was not trying to being hostile, I was just pointing out the fact that my questions were not answered, and in fact, information that I didn't request was given instead. I didn't intend to inspire anyone to feel that they need to retaliate, but I will admit, it is very frustrating when I start a thread asking, for example, "why are some apples red, and some green?" And instead of someone answering my question, they advise me not to eat apples. Surely you can see why this would be frustrating? I really don't want to be an ass to anyone because I'm anything but an ass, but at the same time, I feel need to point out the irrelevancy of the response. And I try to do it without being a rude about it. Hence the, "i'm not trying to sound like an ass" part, which was obviously taken offensively, because you used it deliberately with the intent of snapping back at me when I never snapped at anyone in the first place.
So I do apologize, and this is not sarcasm, nor me being a smart ass, I really am apologizing for upsetting anyone. There's just no reason for it, and I certainly do not intend to upset anyone.

Soundfx4 said:
I need to apologize; I honestly was not trying to being hostile, I was just pointing out the fact that my questions were not answered, and in fact, information that I didn't request was given instead. I didn't intend to inspire anyone to feel that they need to retaliate, but I will admit, it is very frustrating when I start a thread asking, for example, "why are some apples red, and some green?" And instead of someone answering my question, they advise me not to eat apples. Surely you can see why this would be frustrating? I really don't want to be an ass to anyone because I'm anything but an ass, but at the same time, I feel need to point out the irrelevancy of the response. And I try to do it without being a rude about it. Hence the, "i'm not trying to sound like an ass" part, which was obviously taken offensively, because you used it deliberately with the intent of snapping back at me when I never snapped at anyone in the first place.
So I do apologize, and this is not sarcasm, nor me being a smart ass, I really am apologizing for upsetting anyone. There's just no reason for it, and I certainly do not intend to upset anyone.
Click to expand...
Click to collapse
To follow along with your apple analogy: if you are asking why some apples are red and why some are green so you can figure out which ones are better to to eat, and someone tells you those apples are rotten, don't eat them, does it matter why some are red and some are green? It becomes purely an academic exercise. Unless you weren't asking the question to find out which one was better to eat, but just purely out of curiosity in the first place.
So, if that is the case, here are the answers to your questions:
Soundfx4 said:
I downloaded the Galaxy Nexus ToolKit the other day and I noticed that under CDMA/LTE Verizon model, after the latest ICS build that I know of for The VZW GN (IMM76k) there is a 4.1 Build JRN84D listed...I looked that build up and it's JB for the Nexus 7 apparently?
Click to expand...
Click to collapse
There is a JRN84D build for maguro (GSM GNex), although there is no JRN84D build for toro.
Soundfx4 said:
This confuses me, because I'm pretty sure that the Nexus 7 has drastically different hardware in contrast to the Galaxy Nexus and this Toolkit is apparently SPECIFIC to the Galaxy Nexus (I mean...it's in the name).
Click to expand...
Click to collapse
Yes, the Nexus 7 has different hardware than a GNex. You are confused because you did not understand that JRN84D can be for different devices... although a maguro JRN84D build is different than a nakasi JRN84D build, but they are still JRN84D builds.
Soundfx4 said:
So why is there a JB build listed in this toolkit for the Nexus 7 UNDER the MYSID-TORO section?
Click to expand...
Click to collapse
It is not a build for the Nexus 7, as mentioned above.
It is listed under mysid-toro because it is a MISTAKE/ERROR. <== This is why you should not use toolkits. Toolkits that are made to cover multiple builds and devices are more prone to having mistakes and incompatibilities. And, as with anything that uses scripts made by someone else, you do not know what it is doing so if something messes up, good luck trying to figure it out (given that you do not have the knowledge to flash things yourself without scripts).
Soundfx4 said:
I've one more question as well; before you can even being using the ToolKit it asks you to choose which Model and Build you have. My phone is currently on the Vicious JB 4.1 v5 build and that's not something I'm able to choose. Does that mean I need to go back to stock before I can use this toolkit?
Click to expand...
Click to collapse
You are asking this question because you do not know what the toolkit is doing. <== Another reason not to use them. I would hazzard a guess that it is asking which version of android your ROM is based on. So if Vicious JB 4.1v5 is based on JRN84D, then that is probably what the toolkit is looking for (so that it can boot the right kernel or something), but that is just a guess.
Flashing images, etc. is not difficult at all. But, if you don't want to take a few minutes to learn, you will likely have additional issues in the future using toolkits.
http://forum.xda-developers.com/showthread.php?t=1469909

G.Nexus - Just purchased - Advice

Hey Guys,
*Insert flame here*
I am a apple fan boy all the way, however I am also a geek, and I LOVE gadgets. I just recently purchased a second hand galaxy nexus for myself to play with.
Ive been watching android closely and Jelly bean looks great, Im keen to get some time to learn and have some fun with it all.
So this brings me to a whole new world I have no idea about. I am hoping some nice helpful people on this forum can give me some clear answers without slamming me lol.
1) I want to install Jelly Bean, im looking around on samsungs page, only ICS. Im finding custom roms that are 4.1 however there seems to be so many different distrobutions of it, (canyogen etc) whats the differences?
Reason I bought nexus was that I wanted pure google experience, not a version of Android skinned or changed by samsung or htc etc.
2) Im very well educated in the iOS jailbreaking scene etc however, unlocking the bootloader, I am assuming this is reversable.
Does it have any adverse effects that I would notice etc?
Im hoping you guys can point me in the right direction in getting the device on jelly bean, and as I said, straight up android.
Looking to sink my teeth into Android, I think its a great OS and I always love to learn and experience new technologies.
Thanks in advance.

http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1626895
They said it much better than I ever could.

Your phone should receive an update notification as mine did when I bought it. First updated to 4.0.4 and then to 4.1.1 (Jelly Bean). You don't need to root the phone if you only want the pure Google experience. Nor flashing kernels or ROM's. Just stay on stock for a while and see what you can do. Then you can go to the threads posted by 3rdstring that will help you a lot to introduce you to the development world
The update notification is within the phone. You can go to About Phone in settings to know about it

STAY AWAY FROM TOOLKITS while ive used one and it went fine some people get issues with them just do a few simple commands

3rdstring said:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1626895
They said it much better than I ever could.
Click to expand...
Click to collapse
Thank you, that was a MASSIVE amount of information to take it but it very clear and makes a whole bunch of sense.
tnx- deadalus93 and Alex1123.
Now this leads me to my next set of questions.
Deadalus93 - Im in Australia, from what I understand the carrier dictate when the OTA updates arrive, from what I can tell, they have not pushed JB out to the devices yet? (Mind you I don't actually have the device yet, it will arrive in about 5 hours via courier)
So your telling me there is a pure google jelly bean ROM out there that I can use?
Also, what are the advantages of a custom rom, such a cyanogenmod?
From what I see there is a whole range of custom roms, what are the popular ones, and why?
Alex1123 - I dont even know what a toolkit is, but thanks ill keep it in mind
I know I am asking a lot of questions, so thanks again, Im catching up quickly.

xe4 said:
Thank you, that was a MASSIVE amount of information to take it but it very clear and makes a whole bunch of sense.
tnx- deadalus93 and Alex1123.
Now this leads me to my next set of questions.
Deadalus93 - Im in Australia, from what I understand the carrier dictate when the OTA updates arrive, from what I can tell, they have not pushed JB out to the devices yet? (Mind you I don't actually have the device yet, it will arrive in about 5 hours via courier)
So your telling me there is a pure google jelly bean ROM out there that I can use?
Also, what are the advantages of a custom rom, such a cyanogenmod?
From what I see there is a whole range of custom roms, what are the popular ones, and why?
Alex1123 - I dont even know what a toolkit is, but thanks ill keep it in mind
I know I am asking a lot of questions, so thanks again, Im catching up quickly.
Click to expand...
Click to collapse
If the device is carrier unlocked GSM version you should get an update notification regardless of your carrier's policy.
Sent from my Galaxy Nexus

lqaddict said:
If the device is carrier unlocked GSM version you should get an update notification regardless of your carrier's policy.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This is not true.
xe4 said:
[snip]
Im in Australia, from what I understand the carrier dictate when the OTA updates arrive, from what I can tell, they have not pushed JB out to the devices yet? (Mind you I don't actually have the device yet, it will arrive in about 5 hours via courier)
So your telling me there is a pure google jelly bean ROM out there that I can use?
Click to expand...
Click to collapse
You need to find out what build you are running. (Read the links that were provided to you.) If you are running yakju or takju, you will automatically get updated to JB. If you are running a yakjuXX build, then you will not get an update for the time being. You can flash a yakju or takju stock build though. And yes, it will be perfectly fine. (Again, read the links provided.)
xe4 said:
Also, what are the advantages of a custom rom, such a cyanogenmod?
From what I see there is a whole range of custom roms, what are the popular ones, and why?
Click to expand...
Click to collapse
Before you ask those questions, stick with running stock for a while and see how that works for you. Then you can ask those questions.

All of what efrant said. You should definitely look for build you are running and follow the guides if you wan to change,
PS.: Also new to this phone

just to answer one of your questions ..
"Also, what are the advantages of a custom rom, such a cyanogenmod?
From what I see there is a whole range of custom roms, what are the popular ones, and why?"
Click to expand...
Click to collapse
Customs roms are builds people have packed for themselves , putting in features/apps/etc and taking out what the don't like.
Some customs roms allow for customization for various parts of the whole experience , from custom toggles in the notification bar , for customization of colors and change of navigationg buttons.
They also have performance tweaks , making them faster in some cases then stock.
But as everyone else says , stay for stock till you are bored of it and try one of them on. Be warned though , flashing a rom is saying goodbye to your warranty and some roms have big/small bugs in them.

Qbking77 on YouTube will tell you anything you want
---------- Post added at 07:28 AM ---------- Previous post was at 07:27 AM ----------
0utkast said:
just to answer one of your questions ..
Customs roms are builds people have packed for themselves , putting in features/apps/etc and taking out what the don't like.
Some customs roms allow for customization for various parts of the whole experience , from custom toggles in the notification bar , for customization of colors and change of navigationg buttons.
They also have performance tweaks , making them faster in some cases then stock.
But as everyone else says , stay for stock till you are bored of it and try one of them on. Be warned though , flashing a rom is saying goodbye to your warranty and some roms have big/small bugs in them.
Click to expand...
Click to collapse
you can unroot and reflash stock and get warrantee back.

Congrats on your Nexus. It's a sweet device. My biggest love for it is because of Google Wallet. Such a dream to use.

while I can see others point in staying stock until you get settled in, I kinda disagree. unlocking the bootloader wipes the device so it makes some sense to go ahead and do it.
the main reason people use custom roms is for the customization it allows: both visually and performance-wise.
CyanogenMod and aokp are the most popular options, but there are many worthwhile roms here.
sent from outer space or something...

If you don't have either Yakju or Takju on your Nexus then first thing I would do is flash either one from https://developers.google.com/android/nexus/images . That will get you on the official Google Supported build which is a must if you want Jellybean