first I think you guys are the best you have shown that the Android platform is all they said it would be, before they screwed it down. I have a UK G1 with cupcake 1.5. last night an update OTA change my buid to build CRC1. has any one tryed to root one yet. Or has the downgrade method been patched
phirejack said:
first I think you guys are the best you have shown that the Android platform is all they said it would be, before they screwed it down. I have a UK G1 with cupcake 1.5. last night an update OTA change my buid to build CRC1. has any one tryed to root one yet. Or has the downgrade method been patched
Click to expand...
Click to collapse
Haven't seen any one trying to root yet. You can be a gracious guinea pig and try it?
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...
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.
so before the official 2.1 ruu was released to sprint i ran the ruu that had leaked a few days before the official release came. Is that leak exactly the same as the official release.
yes.....yes it is.. I think the ruu of the leak had test keys in it with root i need someone to confirm this tho. But yeah i read that they have the same MD5.
Powers16 said:
yes.....yes it is.. I think the ruu of the leak had test keys in it with root i need someone to confirm this tho. But yeah i read that they have the same MD5.
Click to expand...
Click to collapse
it doesn't matter they could be different give me a sec and I'll try to get you that and what i would like you to do if you have your msl is run the stock 2.1 rom and reset to factory settings and then do update your prl and everything else so then flash fresh 2.0d
Here is a copy of the radio from the actual ruu
thatguythatdid said:
it doesn't matter they could be different give me a sec and I'll try to get you that and what i would like you to do if you have your msl is run the stock 2.1 rom and reset to factory settings and then do update your prl and everything else so then flash fresh 2.0d
Here is a copy of the radio from the actual ruu
Click to expand...
Click to collapse
sorry, but is this directed at me? you want me to run the stock ruu? and then flash fresh 2.0d? my phone is not rooted, i'm just curious if mine is unrootable (as of now) like the official 2.1 ruu
eagles16 said:
sorry, but is this directed at me? you want me to run the stock ruu? and then flash fresh 2.0d? my phone is not rooted, i'm just curious if mine is unrootable (as of now) like the official 2.1 ruu
Click to expand...
Click to collapse
As of now, it is not rootable, however, devs are working on getting it rooted.
so before the official 2.1 ruu was released to sprint i ran the ruu that had leaked a few days before the official release came. Is that leak exactly the same as the official release.
Click to expand...
Click to collapse
No it is not exactly the same, there were some minor, but good fixes
-------------------------------------
Sent from my HERO200
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.