I bought a non-rooted Nexus One off of Craigslist and I updated to frg83d and the radio wont update!
It stayed the same old 5.12.00.08 radio version before and after the update! I dont want to update to gingerbread and have the radio not update again
I know the radio can improve the battery life and reception so what can I do to get the radio updated to the current version?
Also, does anyone know WHY the radio isnt updating? Its the easiest way to brick your N1 and I dont want to have to keep risking bricking my phone everytime a new OS comes out having to manually update the radio if I can avoid it.
Thank you anyone who can please help me pls pls
What radio are you trying to get to?
5.12 is the newest one.
pwig said:
What radio are you trying to get to?
5.12 is the newest one.
Click to expand...
Click to collapse
Are you sure? Isnt the most current radio there 4.06.00.12.7?
here is a picture from an Xda thread showing 4.06.00.12.7 after updating to frg83d: i51.tinypic.com/14jrrpi.jpg
If 4.06.00.12.7 is the most current radio then my Nexus baseband radio isnt updating and I would need some help
n1needhelp said:
Are you sure? Isnt the most current radio there 4.06.00.12.7?
here is a picture from an Xda thread showing 4.06.00.12.7 after updating to frg83d: i51.tinypic.com/14jrrpi.jpg
If 4.06.00.12.7 is the most current radio then my Nexus baseband radio isnt updating and I would need some help
Click to expand...
Click to collapse
You really need to learn numbers...
OK the 5.12.08 radios are from the Korean version of the N1. The 4.06 version is the stock radio from the N1s here in the U.S. Soooo what you saw in that picture was someone who got the update of FRG83D with the stock N1 radio from the US. I have the 4.06 radio. It only helps SOME people with better battery life. Your mileage may vary in other words. You HAVE the most updated version. FYI: " believe only half of what you see and none of what you hear"
Sent from my Nexus One using XDA App
Babydoll25 said:
OK the 5.12 and 5.08 radios are from the Korean version of the N1. The 4.06 version is the stock radio from the N1s here in the U.S.
Click to expand...
Click to collapse
So since I am in the united states I SHOULD have the 4.06.00.12.7 is what you are saying? Because I dont atm I have the Korean radio 5.12.00.08 unfortunately and when I update its not updating to the correct U.S. version
Babydoll25 said:
Soooo what you saw in that picture was someone who got the update of FRG83D with the stock N1 radio. You HAVE the most updated version.
Click to expand...
Click to collapse
Yeah I also found an androidspin article here: androidspin.com/2010/09/24/googles-nexus-one-updated-to-android-2-2-1/
The article says I should have the 4.06.00.12.7 (the US version) but for some reason its the Korean version so how could I fix this?
thanks for the responses so far you guys I just gotta get this fixed to the right U.S. radio version.
n1needhelp said:
So since I am in the united states I SHOULD have the 4.06.00.12.7 is what you are saying? Because I dont atm I have the Korean radio 5.12.00.08 unfortunately and when I update its not updating to the correct U.S. version
Yeah I also found an androidspin article here: androidspin.com/2010/09/24/googles-nexus-one-updated-to-android-2-2-1/
The article says I should have the 4.06.00.12.7 (the US version) but for some reason its the Korean version so how could I fix this?
thanks for the responses so far you guys I just gotta get this fixed to the right U.S. radio version.
Click to expand...
Click to collapse
For god's sake, stop trying to find something wrong with your Nexus.
The korean radio is fine and IS the newest and DOES run better. Keep it and be happy, there is NO point in going back to 4.06.
gravufo said:
For god's sake, stop trying to find something wrong with your Nexus.
The korean radio is fine and IS the newest and DOES run better. Keep it and be happy, there is NO point in going back to 4.06.
Click to expand...
Click to collapse
exactly, well said
Keep in mind that when you flash a ROM it typically does not include a radio. You have to flash the radio separately, preferably using fastboot.
Did you seriously think the 4.xx radio was newer then the 5.xx radio?
LOLOLOLOL
Related
T-Mobile supposedly sent out an over the air update to correct a problem with missed calls.
Does anyone know how that works? Is there some way to get the correction if I am on CyanogenMod? Is it a radio update? If so what is the new radio version and how can I get it?
I ask because I keep on getting in trouble for not knowing that my wife tried to call me.
MonkeyK said:
T-Mobile supposedly sent out an over the air update to correct a problem with missed calls.
Does anyone know how that works? Is there some way to get the correction if I am on CyanogenMod? Is it a radio update? If so what is the new radio version and how can I get it?
I ask because I keep on getting in trouble for not knowing that my wife tried to call me.
Click to expand...
Click to collapse
mine took an OTA update and it did change my radio
So you got an OTA update and it did update your radio. Are you using a stock ROM?
MonkeyK said:
So you got an OTA update and it did update your radio. Are you using a stock ROM?
Click to expand...
Click to collapse
yes 1.6 stock rom not even rooted
Where can I find the latest radio update? I tried clicking the links in the th3fallen's thread on rooting the Nexus One, but they just take me directly to www.modaco.com. Help is appreciated, thanks!
Part Four said:
Where can I find the latest radio update? I tried clicking the links in the th3fallen's thread on rooting the Nexus One, but they just take me directly to www.modaco.com. Help is appreciated, thanks!
Click to expand...
Click to collapse
use the search feature, thats what its there for
hint... search football and ere36b
Part Four said:
Where can I find the latest radio update? I tried clicking the links in the th3fallen's thread on rooting the Nexus One, but they just take me directly to www.modaco.com. Help is appreciated, thanks!
Click to expand...
Click to collapse
I'd stick with the OTA update and its radio update. There aren't any benefits with the unreleased radio update.
uansari1 said:
I'd stick with the OTA update and its radio update. There aren't any benefits with the unreleased radio update.
Click to expand...
Click to collapse
What are the supposed benefits, im still on the OTA ERE27, i keep hearing lots of reports of reception problems with ERE36
liam.lah said:
What are the supposed benefits, im still on the OTA ERE27, i keep hearing lots of reports of reception problems with ERE36
Click to expand...
Click to collapse
That's my point... there's a reason ERE36B hasn't been released OTA yet. Skip it.
I had ERE36B and I had issues. Wifi kept giving me a connection error if I left wifi range and returned. My 3G wasn't as stable. I went back to ERE27 and had no more issues.
My personal experience is that the reception problems are present in ERE27 and ERE36B. But, I just pull the *#*#4636#*#* menu and set it for 3G only. I have 3G everywhere I go, so it works for me. And, I do get faster data with ERE36B.
I got no connection problems at all ...
Have 4.03.00.21_2 (I think it´s not the newest radio though..)
Edit: jst updated to latest one, found at modaco site..
Another Thread?
Well, the newest radio is EPE54B or something like that..
but it's the same as ERE36B
Apparently the AT&T N1's come with the latest leaked radio...EPE54B.
so does that mean that my tmobile nexus one will be getting a radio update soon?
Master_sk3 said:
so does that mean that my tmobile nexus one will be getting a radio update soon?
Click to expand...
Click to collapse
Well that's hard to say, but eventually we should for the tmob frequencies.
I have a factory unlocked n1 that ive only owned for about 3 months.
I noticed its still on FRG83 (not the latest FRF91).
Will I have to do anything special to get the 2.3 update? (Im in the UK if that makes a difference).
FRG83D is the latest, not FRF91.
mcrosmar said:
FRG83D is the latest, not FRF91.
Click to expand...
Click to collapse
Ok, well im still running FRG83 (not FRG83D)...
maxppp said:
Ok, well im still running FRG83 (not FRG83D)...
Click to expand...
Click to collapse
hopefully this will solve your problem
http://forum.xda-developers.com/showthread.php?t=844464
maxppp said:
Ok, well im still running FRG83 (not FRG83D)...
Click to expand...
Click to collapse
to get the latest available update for your phone, dial
Code:
*#*#2432546#*#*
flybyme said:
to get the latest available update for your phone, dial
Code:
*#*#2432546#*#*
Click to expand...
Click to collapse
Thanks, it came up with 'check in succeeded', but nothing else (this was 5 mins ago).
I take it that it doesnt matter that the nexus one wasnt ever offered on my network (o2 uk), and the phone actually polls google servers?
It doesn't matter at all, just have to wait patiently, or force it (as above).
Rusty! said:
It doesn't matter at all, just have to wait patiently, or force it (as above).
Click to expand...
Click to collapse
But 83D came out two and a half weeks ago, isnt that abit too long to wait?
maxppp said:
But 83D came out two and a half weeks ago, isnt that abit too long to wait?
Click to expand...
Click to collapse
Can't you just update using the link provided above?
Im in the uk, running FRG83D and expecting the 2.3 update today. (also on o2)
Could it be my simcard? It works with 3g but its quite old still...
Also do I need to register my IMEI or anything?
Rest of the phone says this.
Code:
android version
2.2.1
baseband version
32.50.00.32u_5.12.00.08
kernel version
2.6.32.9-ge9111ea
[email protected] #1
build number
FRG83
Poolmunch said:
expecting the 2.3 update today. (also on o2)
Click to expand...
Click to collapse
Good luck with that
maxppp said:
Could it be my simcard? It works with 3g but its quite old still...
Also do I need to register my IMEI or anything?
Rest of the phone says this.
Code:
android version
2.2.1
baseband version
32.50.00.32u_5.12.00.08
kernel version
2.6.32.9-ge9111ea
[email protected] #1
build number
FRG83
Click to expand...
Click to collapse
You've got a weird kernel there? And the Korean baseband... my guess is your phone has had the KT FRF91 passimg flashed at some point, which would explain your lack of update.
That is very weird!
Are there any instructions on how to flash the kernel and baseband back to UK defaults?
Also what is the KT FRF91 passimg about, is it anything dodgy / something I should be concerned about?
Edit: I sent my phone to HTC last week and it's come back with a different IMEI...i guess that explains the korean part.
It's not really dodgy, or anything to worry about, it was an easy way for European N1 owners to update to Froyo without unlocking the bootloader back in the day. It does mean you'll lag behind with updates though.
I don't think you'll be able to get back to the proper Google firmware without rooting/unlocking your bootloader due to the 0.35 HBOOT (you can check if you have this or not by turning the phone off, holding in the tackball and powering on, the second line will say either HBOOT-0.33.0012 or HBOOT-0.35.0017).
Ive got the Hboot 0.35.0017 on FRG83D, i got the FRG83 -> FRG83D OTA update when everyone else did. I dont think this is his problem
It's not a problem as such, but it will prevent downgrading to get onto the Google version.
Ok its says HBOOT 35.0017.
If i root the bootloader, can I then flash my way back to 'Default' kernels / radios?
Yes, easily, you might not even have to wipe it in fact.
You use fastboot to flash the system.img and boot.img from the FRG33 image on shipped-roms.
Ok thats great, thanks for all your help.
Just to re-cap, install android sdk / fastbook on my pc, then flash boot.img then system.img from FRG33?
Exactly, although I lied, you will have to wipe.
I forgot that unlocking automatically wipes the phone.
Hi!
I am looking for radio 1.77.15p sbf almost 6 hours..
I am despret..
Aster I flashed to radio 01.77.07P I have no data over mobile..
And 01.87.00R really killing my battery..
Someone can Help me please?
What carrier are you with? If there has been no leak of your carrier's sbf, then there will be no radio.
Did you flash the entire sbf, or just the 01.87.00r radio?
I am at At&t..
I flashed only the radio sbf after I'v tried the 1.77.07 radio and I'v got no data..
shai347 said:
I am at At&t..
I flashed only the radio sbf after I'v tried the 1.77.07 radio and I'v got no data..
Click to expand...
Click to collapse
You have an AT&T version? What carrier is it running on? ATT or another?
Have you checked your APN settings?
Yes I am on AT&T careier..
What I neen to check on APN settings? Evrything looks good over there..
There is a stock at&t radio sbf included in this post.
http://forum.xda-developers.com/showthread.php?p=13248063
[MOD] Enable HUSPA on ATT
Sent from my MB860 using XDA Premium App
shai347 said:
Yes I am on AT&T careier..
What I neen to check on APN settings? Evrything looks good over there..
Click to expand...
Click to collapse
shai347, have you found the 01.77.15P already?
I'm on the same boat as you.
@everyone:
The stock rollback radio included on the file above is actually older than the one we had before the HSUPA update (01.77.07P) and that's why we are looking for 01.77.15P instead.
Any news?
P.S. I would like to avoid rolling back the entire ROM just for the radio.
Thanks!
Rayan
I'm in the same boat. If someone could find N_01.77.15P radio that would be an epic win. It's the radio that shipped with AT&T 4.1.83 update.
SC. said:
I'm in the same boat. If someone could find N_01.77.15P radio that would be an epic win. It's the radio that shipped with AT&T 4.1.83 update.
Click to expand...
Click to collapse
Here it is.
h t t p: / /w w w . filesonic.com/file/991439424/AT&T_OLYFR_U4_1.8.3_Radinly.rar
goscrewsir said:
There is a stock at&t radio sbf included in this post.
http://forum.xda-developers.com/showthread.php?p=13248063
[MOD] Enable HUSPA on ATT
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
This is not the stock radio for the Atrix. This is the HSUPA mod that was released prior to update 4.1.83, and caused many users to experience overheating with their phones.
Please next time check when you post something as stock for a phone that it is actually stock for that model.
here whipon have it
[MOD] Retail Brazil Radio (by request) AT&T Atrix only
I received the OTA for ICS today, and it updated without any problems like some are having. However, since receiving the update, I get NO SERVICE most places. I'll occasionally show 1 bar of service and at that point SMS will come flooding through and send out. I have a 9020A and i'm wondering if they didn't change the radio to the T-Mobile version. Is anyone else having similar issues? I plan on possibly flashing a different radio to the phone when i get home (i'm currently at work)
I'm kinda going nuts. I only recently went to this from an I9000. I haven't even rooted it or flashed any roms. It was entirely stock. I'm admittedly a novice with this phone. Any help would be appreciated. Thanks!
Model: 9020A
Android - 4.0.3
Carrier - Immix Wireless
Baseband - NO DGSXXKI1
Build - IML74K
Kernel - 3.0.8-gb55e9ac [email protected] #1
And why didn't you grab a link before you ran the update? My guess says is you got a failed update and need to reapply.
I'm a noob to all this BUT at the very least I can tell you that you need to flash a different radio since "Baseband - NO DGSXXKI1" indicates a radio that is not going to work.
Is this a troll
Did we just get trolled? Dude that's so cruel.
Grab the radio here http://forum.xda-developers.com/showthread.php?t=1116884 and flash it with fastboot. That should get you the proper radio and get your phone back in working order...
omistake said:
I received the OTA for ICS today, and it updated without any problems like some are having. However, since receiving the update, I get NO SERVICE most places. I'll occasionally show 1 bar of service and at that point SMS will come flooding through and send out. I have a 9020A and i'm wondering if they didn't change the radio to the T-Mobile version. Is anyone else having similar issues? I plan on possibly flashing a different radio to the phone when i get home (i'm currently at work)
I'm kinda going nuts. I only recently went to this from an I9000. I haven't even rooted it or flashed any roms. It was entirely stock. I'm admittedly a novice with this phone. Any help would be appreciated. Thanks!
Model: 9020A
Android - 4.0.3
Carrier - Immix Wireless
Baseband - NO DGSXXKI1
Build - IML74K
Kernel - 3.0.8-gb55e9ac [email protected] #1
Click to expand...
Click to collapse
I used that guide as a referemce:
http://forum.xda-developers.com/showthread.php?t=1396937
You will have to re-flash a radio, if you paid attention, you probably saw a line about flashing a new radio during the process.
Flashing a radio is a quick and painless process if you have the SDK with fastboot installed. (Newer version on Mac doesn't include fasttboot, you have to get it on top of it)
Here's the link to the Radios:
http://forum.xda-developers.com/showthread.php?t=1116884
I suggest you look for your carrier, you might found people recommending different radio for different speed/reception. Get one radio, flash it, test speed and signal and find the one that works best.
You should be all set with those links.
Thanks everyone, I'll try this out in a bit and get back to you. I never read anything about flashing a radio. Again, I got the ota directly from Google... At least wifi is working.
Sent from my Nexus S using XDA App
wait..
isnt a 9020a for att?
tmobile is 9020t.
simms22 said:
wait..
isnt a 9020a for att?
tmobile is 9020t.
Click to expand...
Click to collapse
i9020a is for AT&T, how does he get the update?? Does any other 9020a get it???????
JakeOcn said:
i9020a is for AT&T, how does he get the update?? Does any other 9020a get it???????
Click to expand...
Click to collapse
Was wondering about that myself... Came about 3pm Eastern time...
Sent from my Nexus S using XDA App
omistake said:
Was wondering about that myself... Came about 3pm Eastern time...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Nice.. I'll be waiting for it, by the way you should try radio you were using before OTA that should work properly
JakeOcn said:
i9020a is for AT&T, how does he get the update?? Does any other 9020a get it???????
Click to expand...
Click to collapse
could be an 9020a update. would explain why the 2g signal got worse, since he doesnt have 3g on it( )
Ghostyle said:
I'm a noob to all this BUT at the very least I can tell you that you need to flash a different radio since "Baseband - NO DGSXXKI1" indicates a radio that is not going to work.
Click to expand...
Click to collapse
This indicates he's got the wrong ROM. Probably used ROM manager to restore back to stock, leaving him with the i9020t image.
Sent from my Nexus S
use this Radio - it worked for me as i have the same model as you.
http://forum.xda-developers.com/attachment.php?attachmentid=620140&stc=1&d=1307623157
download and copy it to your sd card and flash it in recovery
No OTA update received on my i9020a...
Me neither...I keep trying though
Sent from my Nexus S using XDA App
There is another thread around here somewhere. I've been doing so much searching today i cant remember where i saw but, apparently rogers pushed the ota ICS update for a short period of time and then pulled it. I guess i know why now. shouldnt be much longer if the just have to package the proper radio. cross your fingers
g2theno said:
There is another thread around here somewhere. I've been doing so much searching today i cant remember where i saw but, apparently rogers pushed the ota ICS update for a short period of time and then pulled it. I guess i know why now. shouldnt be much longer if the just have to package the proper radio. cross your fingers
Click to expand...
Click to collapse
Rogers nor any other provider have a say when the ota comes out. It's 100% up to google
Sent from my Nexus S
Matridom said:
Rogers nor any other provider have a say when the ota comes out. It's 100% up to google
Sent from my Nexus S
Click to expand...
Click to collapse
what he said , that said im on Rogers(not that it matters) and nothing yet.
with the blessing of the provider.... R did have the update and quickly pulled it. It's happened before in R land.