Hey there sorry for opening a new Thread but i found nowhere something about my problem... I have my G1 since it's released and i noticed that something is wrong with it. After updating to Cupcake (no root) i noticed that the Radio (Baseband) version is wrong. It should be 62.50S.20.17H_2.22.19.26I but it is 62.33.20.08U_1.22.12.29.
Here is what my phone says:
Model number
T-Mobile G1
-----------------------------
Firmware version
1.5
-----------------------------
Basband version
62.33.20.08U_1.22.12.29
-----------------------------
Kernel version
2.6.27-00393-g6607056
[email protected]#1
-----------------------------
Build number
CRC1
Please help me! I don't know what to do! Should I go to T-Mobile?
Woah, that's pretty weird. I assume you're unrooted? Otherwise you could just flash this
yeah it's unrooted. I tried to root it with the Goldcard method (So I don't have to change the SPL) to see if i get the right Radio after rooting it but it was still the same. Nothing changed. I had the wrong Radio on the official Build than I rooted it, installed the Radio, installed Dude's Cupcake and it was still the same. Now I'm back on the official Build and nothing changed. I thing about going to T-Mobile tomorrow...
mattmaso said:
yeah it's unrooted. I tried to root it with the Goldcard method (So I don't have to change the SPL) to see if i get the right Radio after rooting it but it was still the same. Nothing changed. I had the wrong Radio on the official Build than I rooted it, installed the Radio, installed Dude's Cupcake and it was still the same. Now I'm back on the official Build and nothing changed. I thing about going to T-Mobile tomorrow...
Click to expand...
Click to collapse
You flashed the radio after root but it was still the old one?! Sorry I can't help, I've never heard of that before :-S
AdrianK said:
You flashed the radio after root but it was still the old one?! Sorry I can't help, I've never heard of that before :-S
Click to expand...
Click to collapse
yeah exactly and now i flashed it back to the offical RC7, RC8, RC9 and than there came the autoupdate... now I'm back on CRC1. And no problem.... thanks for trying.. I go to T-Mobile tomorrow and give it to repair...
Related
I have been checking the massive froyo thread since it was on page 7 (now its > 120 pages) but still no love for AT&T/Rogers Nexus one.
My phone is unrooted and running stock rom with Firmware on 2.1-update1 and build EPE54B. Can people who have froyo on their at&t nexus one please post a step by step guide?
Should be the same method and file as that used for the T-mobile compatible phones.
id really like this answered too..i dont want to take a risk and brick my N1.. so far all the guides are ERE27..
The update zip as it stands is only for ERE27-FroYo... sorry.
unleashed12 said:
id really like this answered too..i dont want to take a risk and brick my N1.. so far all the guides are ERE27..
Click to expand...
Click to collapse
pjcforpres said:
The update zip as it stands is only for ERE27-FroYo... sorry.
Click to expand...
Click to collapse
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
I saw many at&t owners have froyo successfully flashed. They flashed to ERE27 first. Does that need rooting?
Thank you for this information.
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
Anyone tried this?
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
the update file is labeled signed-passion-FRF50-from-ERE27.1e519a24.zip
ATT/Rogers version is running build EPE54B. The update is from ERE27 to FRF50
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
I guess the 20 pages of 100% stock AT&T guys not being able to flash this are just morons then.
The update zip only lets you go from ERE27 to FroYo. Those with an "AT&T version" and FroYo had to flash ERE27 first... that also means unlocking the boot loader.
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
pjcforpres said:
I guess the 20 pages of 100% stock AT&T guys not being able to flash this are just morons then.
The update zip only lets you go from ERE27 to FroYo. Those with an "AT&T version" and FroYo had to flash ERE27 first... that also means unlocking the boot loader.
Click to expand...
Click to collapse
jasrups said:
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
Click to expand...
Click to collapse
That sucks.
Same problem with the european stock shipping ROM (EPF21B).
Can't wait to be able to get Froyo without unlocking.
my bootloader is unlocked..going to go ahead and try to flash pauls rooted version.
jasrups said:
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
Click to expand...
Click to collapse
What a bummer! Yeah I have waited this long to preserve my phone's virgini.. I mean warranty so I guess I'll wait longer.
At least its good to know that the build for at&t and rogers is the same!
I have the AT&T N1, and earlier today I flashed and formatted my phone back to new. I now have Froyo and it's working fine.
Kpow said:
I have the AT&T N1, and earlier today I flashed and formatted my phone back to new. I now have Froyo and it's working fine.
Click to expand...
Click to collapse
is your N1 rooted or stock?
MEGABYTEPR said:
is your N1 rooted or stock?
Click to expand...
Click to collapse
Clearly rooted and unlocked bootloader, otherwise he wouldn't have been flashing anything.
thread title misled me.
eric b
I have successfully flashed Froyo on my (AT&T) N1 with this:
http://android.modaco.com/content/g...com/309286/frf50-froyo-pre-rooted-update-zip/
I previously was on CM 5.0.6 with Amon RA Recovery v1.7.0.
I wiped and installed the update, it did flash a new radio. Rebooted and Froyo was waiting for me!
Hope this helps anyone that is not sure.
Hello, have a new nexus with 2.1 firmware. Like to update to froyo 2.2 A bit confused on where to begin. Think I have to unlock the bootloader. Appreciate pointing to the right link for instructions how to update the bootloader and flash with froyo 2.2.
AT&T
Firmware 2.1-update1
Build # EPE54B
Thanks!
Big_O said:
Hello, have a new nexus with 2.1 firmware. Like to update to froyo 2.2 A bit confused on where to begin. Think I have to unlock the bootloader. Appreciate pointing to the right link for instructions how to update the bootloader and flash with froyo 2.2.
AT&T
Firmware 2.1-update1
Build # EPE54B
Thanks!
Click to expand...
Click to collapse
Start by checking out the sticky at the top of this forums. It was ALL the info you need.
http://forum.xda-developers.com/showthread.php?t=686326
Big_O said:
Hello, have a new nexus with 2.1 firmware. Like to update to froyo 2.2 A bit confused on where to begin. Think I have to unlock the bootloader. Appreciate pointing to the right link for instructions how to update the bootloader and flash with froyo 2.2.
AT&T
Firmware 2.1-update1
Build # EPE54B
Thanks!
Click to expand...
Click to collapse
Or, just wait a week or two for the official release of Froyo.
Is that what we are talking about? One or two weeks?
Flashing the rom is not that big of a deal, was concerned about unlocking the bootloader for AT&T and what was required to do it. Didn't want to make a mistake and have a $500 paperweight
Still not sure where to go or what to download after reading the stickies about AT&T to unlock the bootloader before the flash.
when I got my phone 3 weeks ago, they said 1 or 2 weeks then also, lol....
I have the same type phone att/rogers. I did this then this (thx Jack)
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
then
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
using...
# Links for update.zip: [DOWNLOAD][MIRROR][MIRROR]
# How to update your rooted Nexus One: http://forum.xda-developers.com/showthread.php?t=686734
I followed both of those to the T and it all worked out, once or twice i had a problem or 2.... but I just renamed the recovery image and it worked..... and something else, over all... for a noob, I did pretty good, lol. Very glad I did, sooooo much faster, smoother and flash support
No rooting needed if you use the "originally" leaked FRF50 build .. just download to the phone and run the update.
You may use google to search for the file and the instructions
Good luck!
Edit: sorry, just realized you have an AT&T one. So, you may need to root. My one I got directly from Google and it does not need to be rooted.
Hey so I did something that I am really kicking myself for yesterday. As seen in my other thread, I was having issues with getting Google Voice from the Market. So guess what I did? I did a freaking OTA update on my nice new Hero that I just got yesterday. And guess what? Unrevoked won't work on it now.
So, I'd like to toss out my info and see if anyone has had luck downgrading with an old RUU. I tried one from the 2.1 root thread and it failed to flash.
Firmware: 2.1 update 1
Baseband: 2.42.01.04.27
Build: 2.27.651.6 CL169236 release-keys
software ver: 2.27.651.6
It seems to have a newer version of fastboot and hboot that won't let me flash from the SD card (forgive my noobish wording)
idumych said:
Hey so I did something that I am really kicking myself for yesterday. As seen in my other thread, I was having issues with getting Google Voice from the Market. So guess what I did? I did a freaking OTA update on my nice new Hero that I just got yesterday. And guess what? Unrevoked won't work on it now.
So, I'd like to toss out my info and see if anyone has had luck downgrading with an old RUU. I tried one from the 2.1 root thread and it failed to flash.
Firmware: 2.1 update 1
Baseband: 2.42.01.04.27
Build: 2.27.651.6 CL169236 release-keys
software ver: 2.27.651.6
It seems to have a newer version of fastboot and hboot that won't let me flash from the SD card (forgive my noobish wording)
Click to expand...
Click to collapse
I had just used the *.5 RUU to flash over a .6 not 5 days ago. Worked just fine. Was located in the 2.1 Root thread. Second post.
Yeah, sorry for the false alarm folks, I just tried it again with debugging turned off on the device and it flashed fine.
hey guys
last 4 days before my nexus one working good on froyo..but before 2 days it show me 4 color screen and stuck there ..
so thats why i flashed with PASSIMG FRF91...now my phone get restart and hang sometimes...and there is also low stand by time problem in FRF91..
so anybody can tell me how can i downgrade to FRF85b again...
waiting for reply..also give me link of which file i wana flash on my phone..
thank you in advance...
You should use the FRG33 passimg as per Wiki, then upgrade to FRG83D.
Also, wrong section.
my hboot is 35
norfo said:
You should use the FRG33 passimg as per Wiki, then upgrade to FRG83D.
Also, wrong section.
Click to expand...
Click to collapse
ok as u said i need to use FRG33 ( FRG33 is upgraded version than FRF91 ?)
Just grab the image from here: http://developer.htc.com/
Have you tried the last update (FRG83D)?
Although if you want the FRF85D, first flash the FRF50 update (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/update-nexusone-FRF50-signed.zip) and then upgrade to FRF83 with oficial recovery (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF83-From-FRF50.zip) and finally upgrade to 85D (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF85B-From-FRF83.zip)
http://android.modaco.com/content/g...es-zip-online-kitchen-optional-root-insecure/
my nexus one is korean n1 and its on hboot 0.35
gerar_f said:
Have you tried the last update (FRG83D)?
Although if you want the FRF85D, first flash the FRF50 update (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/update-nexusone-FRF50-signed.zip) and then upgrade to FRF83 with oficial recovery (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF83-From-FRF50.zip) and finally upgrade to 85D (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF85B-From-FRF83.zip)
http://android.modaco.com/content/g...es-zip-online-kitchen-optional-root-insecure/
Click to expand...
Click to collapse
hey dude my n1 is korean n1 with hboot of 0.35 ..so downgrade to FRF85d will not cause any problem or not?
i dont wana update my N1 becasue if i update than i cant be able to root or install cynogen mod rom to my phone (if i need).
My phone was working fine before i update to FRF91 (No restart problem or hang so thast why i wana downgrade back)..
can u tell me how to flash FRF50 update to nexus one
gerar_f said:
Have you tried the last update (FRG83D)?
Although if you want the FRF85D, first flash the FRF50 update (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/update-nexusone-FRF50-signed.zip) and then upgrade to FRF83 with oficial recovery (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF83-From-FRF50.zip) and finally upgrade to 85D (http://loadbalancing.modaco.com/download.php?url=paul/nexusone/Update-Passion-FRF85B-From-FRF83.zip)
http://android.modaco.com/content/g...es-zip-online-kitchen-optional-root-insecure/
Click to expand...
Click to collapse
hey dude i have download frf50 update..can u tell me how can i flash frf50 to my frf91 nexus rom...? can i flash by changing name to PASSIMG or can i change the name to Update.zip??
reply please soon
swapniladsure said:
hey dude my n1 is korean n1 with hboot of 0.35 ..so downgrade to FRF85d will not cause any problem or not?
i dont wana update my N1 becasue if i update than i cant be able to root or install cynogen mod rom to my phone (if i need).
My phone was working fine before i update to FRF91 (No restart problem or hang so thast why i wana downgrade back)..
Click to expand...
Click to collapse
Korean N1 was released with 2.2(FRF91) from the start, IIRC. So I don't know if downgrade is possible. (And, you can still root your device via rageagainstthecage exploit after upgrading it to 2.2.1(FGR83))
can i able to install custome rom after update to fgr83 as u say
LFact said:
Korean N1 was released with 2.2(FRF91) from the start, IIRC. So I don't know if downgrade is possible. (And, you can still root your device via rageagainstthecage exploit after upgrading it to 2.2.1(FGR83))
Click to expand...
Click to collapse
hey dude if i update to fgr83 and after update if my phone work well than it is ok ( not get restart) but if after update my phone again get restart while surfing or using any apps ..than it is possible to root and install custom cyanogen mod rom on my nexus one??
hi all.
my situation:
i got an european nexus one bought through vodafone.
the first step was when i received froyo ota: FRF91 build with v5.08 radio.
then i decided to leave vodafone and install stock android: now i got FRG83D build with v4.06 (downgraded!) radio.
now, since i realized that the newest radio is better than the old one, my question is:
does we already know that gingerbread ota gonna bring also a radio upgrade?
1) yes, waiting for it is recommended.
2) no, the only way is root it and manually update the radio to v5.12.
thanks.
I suspect it will.
Obviously no proof of that, but meh. Wait and see I guess, if it does, you're golden. If not, root (before applying the update, just to be safe, as I presume you're against unlocking the bootloader), flash radio, then update.
any other opinions?