hi there:
i have 2 general questions about radio updates...
1) is a radio update - 2.15.x, for example - a software update or a firmware update? like, did i flash my radio so that all my roms are affected? or, is only the rom i applied it to affected?
2) does a radio update - 2.15.x, for example - affect all radios in my phone? like bluetooth? or just my cellular radio?
i'm asking because i can no longer get my dinc to connect to my bluetooth, no matter which rom i'm on. i'm trying to pin it down, and the timing seems about right to when i flashed 2.15. even my stock 2.1 rom won't connect anymore. i guess it could be something else, but the radio seems a likely culprit.
thanks!
1. It is neither...it is a radio update
2. It affects only the baseband, or cellular radio...bluetooth has something to do with the bluez plugin, which is updated in the android versions
Sent from my ADR6300 using XDA App
1. Technically, it's a firmware update, so yes, all of your ROMs are affected. ROM flashing has nothing to do with the radio.
2. The radio update affects baseband version, which has an effect on cell network connection/quality. Bluetooth, Wifi, etc, are all handled by the kernel, which is part of Android, not the radio. Think of the radio as a completely separate OS running outside of Android.
thx for the replies, guys. it's what i expected, although i was hoping i was wrong. dang, what's messin' with my bluetooth? dang...
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
Hey guys I have a question about baseband compatibility
My GNex is completely stock 4.1.1 and is rooted.
I was on bigxies ROM running uglc1 and I seemed to have better reception with it.
Thing is, ever since I went back to stock, I've tried flashing the same radio over xxlf1 and I can't get any service. I am experiencing the same issues once again such as random signal loss and no service. I ran GetRil and everything is good there.
So is it that you just cant run a different baseband on a factory installed rom or am I doing something wrong?
Any ideas are greatly appreciated.
...Sorry for wasting anyones time http://forum.xda-developers.com/showpost.php?p=23305473&postcount=195
modiand said:
Hey guys I have a question about baseband compatibility
My GNex is completely stock 4.1.1 and is rooted.
I was on bigxies ROM running uglc1 and I seemed to have better reception with it.
Thing is, ever since I went back to stock, I've tried flashing the same radio over xxlf1 and I can't get any service. I am experiencing the same issues once again such as random signal loss and no service. I ran GetRil and everything is good there.
So is it that you just cant run a different baseband on a factory installed rom or am I doing something wrong?
Any ideas are greatly appreciated.
...Sorry for wasting anyones time http://forum.xda-developers.com/showpost.php?p=23305473&postcount=195
Click to expand...
Click to collapse
Not all radio versions are compatible with every version of Android. This sounds like you have a GSM version of the GNex as I myself have a the CDMA/LTE version but in some cases when new version of Android come out or leak or what have you it's best to keep current the radio versions with the OS.... If that helps or makes sense at all. I do know that on the CDMA/LTE JellyBean updates I'm still using the radio versions from 4.0.4 with it and it's perfectly fine. Have you always had the loss in signal or is this only of recent with testing different radios?
PaullieVicious said:
Not all radio versions are compatible with every version of Android. This sounds like you have a GSM version of the GNex as I myself have a the CDMA/LTE version but in some cases when new version of Android come out or leak or what have you it's best to keep current the radio versions with the OS.... If that helps or makes sense at all. I do know that on the CDMA/LTE JellyBean updates I'm still using the radio versions from 4.0.4 with it and it's perfectly fine. Have you always had the loss in signal or is this only of recent with testing different radios?
Click to expand...
Click to collapse
I got it to work. Apparently some thunderstorms knocked out at&t service last night and I was flashing radios during it so when I got done, I couldn't pull any service down. While I'm still without signal, I know its not a radio issue now. Thanks for the response
Sent from my Galaxy Nexus using xda premium
Hi,
I recently installed JB and rooted my GN using this tutorial (youtube.com/watch?v=1y3Lm6feyGI) and a few other infos picked here and there (including xda). It worked perfectly. BUT here is the thing: I had a GN GSM (I'm in Europe) maguro/yakjuxw running 4.04. My goal was to install JB 4.1.1 JRO03C which I did (and it runs like a charm so far). Now, when checking in Google Maps the version, I find 'takju'.
My question is: is that 'normal'? I mean installing JB had to change the version or is it something wrong I did like picking the wrong file or option in the GN Toolkit? And when I'm at it, is a rooted GN able to use OTA (and should the GN running a specific version for that)?
Thank you guys
Eric
When you flashed to Jelly Bean, you used the images directly from Google, which made your phone "takju". That just means from this point forward you'll get updates quickly directly from Google.
Root doesn't block your ability to get an OTA. Taking the OTA will make your root go away unless you use an app like "OTA Rootkeeper". Things that will stop you from taking an OTA are a custom recovery, different radios, modified/deleted system files.
If you have custom recovery, you can keep it and flash the OTA manually and keep that custom recovery. You just can't accept and auto-install an OTA.
Changing variant does not effect you in any bad way. It gives you benefit of being ota from Google
So the answer is yes, don't worry about it
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Hi, I'm not sure if theres thread on this but my signal is lost. two weeks ago i wake up one morning to find my service isnt working,the sim does work on my two old phones so it's not a sim issue. I then found my baseband is unknown. So I searched and found some fixes which are too flash the radio with a new radio through either clockwork mode or nexus toolkit. I've tried 5 different radios all being diffrent updates of the galaxy nexus radio. I was runnung 4.2.1(which i hated) but now I got android revolution HD 2.1.2 and ak kernel and downgraded to 4.0.2(yes the phone is unlocked and rooted). I was wondering can anyone tell me whats wrong before I factory lock it and unroot and send it in for warranty repair. Btw phone was with Rogers/Fido carrier.
Since you've done all that, we don't know what's wrong with it. 4.0.2? You're missing out on security fixes (been talked about a lot lately), new features, optimizations, not sure why you're running it. That aside, and I'm not saying it will do anything for you, you could try GetRil from the Play Store, to see what RIL you have installed, and if it recognizes any baseband at all. Your radio (or radios, we don't even know which variant you have) may be dead, who knows? What's the latest baseband you flashed? What's the latest bootloader you flashed?
a manta wrote this.
beekay201 said:
Since you've done all that, we don't know what's wrong with it. 4.0.2? You're missing out on security fixes (been talked about a lot lately), new features, optimizations, not sure why you're running it. That aside, and I'm not saying it will do anything for you, you could try GetRil from the Play Store, to see what RIL you have installed, and if it recognizes any baseband at all. Your radio (or radios, we don't even know which variant you have) may be dead, who knows? What's the latest baseband you flashed? What's the latest bootloader you flashed?
a manta wrote this.
Click to expand...
Click to collapse
I wanted 4.1.2 but for some reason I got 4.0.2 so I have no idea, but I'm going to stick with ice cream sandwhich since 4.2.1 update had tons and I mean TONS of bugs that wanted me to kill my nexus.
Build Number: Android revolution HD 2.1.2 GSM
aNDROID vERSION: 4.0.2
kERNEL vERSION: 3.0.8-GAAA2611 ANDROID [email protected] #1
IMEI: UNKNOWN
IMEI SV: UNKNOWN
I have flashed versions:
UGKL1
UGKK1
UGKM1
(All are for I9250M GSM not LTE or CDMA since my phone is GSM)
I have Clockwork Mod version: 6.0.3.1
Bootloader PRIMELA03
Baseband: I9250MUGKL1 (According o bootloader, still unknown in About phone)
... and install the app GetRil. Not sure, but I think you should revert to ICS boot loader.
a manta wrote this.
beekay201 said:
... and install the app GetRil. Not sure, but I think you should revert to ICS boot loader.
a manta wrote this.
Click to expand...
Click to collapse
Hello, yeah I got the app, but it says that they dont match and they show basband unknown compared to ugkl1. How do I get the ICS Bootloader?
See the sticky by efrant (android 101; useful links)
a maguro wrote this.
http://forum.xda-developers.com/showthread.php?t=1587498 Is this the link? I have no idea and which one do I get.