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?
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.
I am not a newbie to rooting or flashing roms, but I have a question for anyone who knows; can the hole in software that existed on 1.5 be exorted on the official 2.1 update from sprint? I would like to know before I try to root, that way I do not accidentally brick my phone from not knowing what I'm doing. I really only want to flash a 2.2 rom, since I know that Sprint will not be providing an official update, which, disappoints me, to say the least. I know that they might lose customers to Verizon, or even Tmo, thanks to their lax attitude when it comes to providing updates. Thanks in advance.
You should run the 2.27.651.5 RUU which has the root exploit that you can use. It is found here. Scroll to the second post and download/install first. Then proceed with the first post.
Yeah, post above mine is the most recommended method for rooting. I have read that the only difference between .5 and .6 is the root exploit was patched by sprint or htc. I think they purposely let a RUU with root be released for a day or two so the smart people can get a hold of the code, but call it an error. hahaha!
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.