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.
Does anyone know how i can get froyo on my phone with the EPF21B build? Could i change to the ERE27 build WITHOUT rooting my phone? Or flash pauls version through the stock recovery image, without voiding my warranty? Thanks for any help
same problem.
my phone is EPE54B
HELP!!!
Gotta root until Google sort it out I'm afraid.
I have ERE36B with locked bootloader. Can I just update or do I need another update file?
You're on an awkward build... I very much doubt there will be an upgrade path for you.
You will most likely need to flash a mainstream PASSIMG.ZIP (AT&T EPE54B or Vodafone EPF21B) and update from that when Google release one.
Rusty! said:
You're on an awkward build... I very much doubt there will be an upgrade path for you.
You will most likely need to flash a mainstream PASSIMG.ZIP (AT&T EPE54B or Vodafone EPF21B) and update from that when Google release one.
Click to expand...
Click to collapse
Edit: Actually, maybe you should listen to him. After clarification it seems that there were un-original roms out in the wild that didn't need an unlocked bootloader. If you updated to that ROM yourself, even without unlocking then you may not see an upgrade at all.
Old post below for continuity's sake.
--------
Don't listen to him. It seems he is telling you that you will need to unlock to upgrade. If you aren't going to unlock yet, just wait, there will be an OTA update for you too, you just have to wait for Google to send it out.
Google will not force you to unlock your phone.
Is there a way to go back to ere27 so i can update now, without unocking?
Dont mind if i have to do a factory reset or something like that
Requiem87 said:
Is there a way to go back to ere27 so i can update now, without unocking?
Dont mind if i have to do a factory reset or something like that
Click to expand...
Click to collapse
EPF21B is the official euro shipping ROM.
You can't change it back to ERE27 without unlocking the phone, period.
If you don't want to unlock, you'll have to wait until Google issues the OTA for the official euro phones.
Clarkster said:
Don't listen to him. It seems he is telling you that you will need to unlock to upgrade. If you aren't going to unlock yet, just wait, there will be an OTA update for you too, you just have to wait for Google to send it out.
Google will not force you to unlock your phone.
Click to expand...
Click to collapse
Thanks for that completely incorrect post.
I am not telling you to unlock, both can be flashed in the same way you flashed ERE36B as they are official released images.
As ERE36B is a release that shouldn't be out in the field, I doubt an update will be made for it.
So, since I am not on Vodafone or AT&T, what should I update to? AT&T EPE54B or Vodafone EPF21B?
There has to be a way to restore the phone to factory state and factory ROM?
Rusty! said:
Thanks for that completely incorrect post.
I am not telling you to unlock, both can be flashed in the same way you flashed ERE36B as they are official released images.
As ERE36B is a release that shouldn't be out in the field, I doubt an update will be made for it.
Click to expand...
Click to collapse
Sorry about that, it seemed to me that you were telling him he would never get an update without unlocking. But he did mention that he was still locked and had that release. I don't know how he got that one, but if he is truly locked wouldn't it make sense that Google knows of the phones out there with that version?
I still don't think it would make sense for Google to not give those phones an update, and to force them to unlock to upgrade.
Am I missing something important here that's really messing up my understanding?
Requiem87 said:
So, since I am not on Vodafone or AT&T, what should I update to? AT&T EPE54B or Vodafone EPF21B?
There has to be a way to restore the phone to factory state and factory ROM?
Click to expand...
Click to collapse
Except that the factory ROM is different from one to another.
Tmobile factory ROM : ERD79 (which can then be updated to ERE27).
ATT factory ROM : not sure but the one before EPE54B
Europe factory ROM : EPF21B.
Clarkster said:
Am I missing something important here that's really messing up my understanding?
Click to expand...
Click to collapse
I think so.
There are certain ROMs that were leaked, these can be installed without unlocking the bootloader as they are release signed. No phone sent out by Google came with ERE36B, you had to install it yourself. There is also no way back to stock ERE27 without unlocking the bootloader.
My reckoning is that as this particluar ROM isn't meant to be in use by the public an upgrade path is unlikely, hence the advice to flash to a 'legitimate' release image (no unlock necessary) which will definitely be upgradable.
Rusty! said:
I think so.
There are certain ROMs that were leaked, these can be installed without unlocking the bootloader as they are release signed. No phone sent out by Google came with ERE36B, you had to install it yourself. There is also no way back to stock ERE27 without unlocking the bootloader.
My reckoning is that as this particluar ROM isn't meant to be in use by the public an upgrade path is unlikely, hence the advice to flash to a 'legitimate' release image (no unlock necessary) which will definitely be upgradable.
Click to expand...
Click to collapse
Thanks for explaining. I'll go edit my original post.
Thanks Rusty. What rom should i update to then? Is there another rom i can downgrade from, or is it generally impossible to go to an older rom with locked bootloader?
Can't go older unfortunately, else it would be a no-brainer.
As for which one, I doubt it matters, but I would expect EPE54B to be the next updated.
cant you just flash pauls prerooted version?
bobdude5 said:
cant you just flash pauls prerooted version?
Click to expand...
Click to collapse
Doesn't work, cancels installation when it doesn't find the right signature.
yeh, tried that, Wont work with locked bootloader. Tried all ERE27 images, renamed to either passimg.zip or update.zip, and same for all frf50.. Only one thing left to do i guess, and that is wait.
Having the Same Problem,
Hi, I have a Nexus One from Vodafone, and have unlocked it, however, I still can't get it to update to Froyo FRF50 so I can then further upgrade it, I am currently on build EPF21B which I think Vodafone have mucked around with, because I have just updated a Friends Nexus Manually with the same file not problems, mine keeps coming up with, first:
Froyo+E:Can't open /cache/recovery/command
Then fails on this:
E:failed to verify whole-file signature
Can any of you kind people out there confirm that there is something slightly odd about the stock Vodafone ROM,
Thanks for your time in this matter, I assure you that it is deeply appreciated
Kind Regards - Ashe
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.
Hi All,
Was just looking into the prospect of rooting and I came across a post that basically responded to a guy asking whether subsequent OTA/Official updates would revert the root. the response was:
this might well happen. To be sure that this won't happen, don't update, or wait for a rooted version of the update to be released
Click to expand...
Click to collapse
It's the bit in bold that's got me wondering. I have my Nexus running stock ROM but rooted (with locked bootloader). I have the problem with the WiFi which 2.2.1 claims to fix.....and I just wasting time thinking that this update might get released as a rooted version so I can just install and not worry about losing root?
Any help gratefully received.
Cheers
1. Already released as a rooted version (check the ROM section)
2. Really easy to root with rageagainsthtecage ...
Right I can ask you the question then......with the rageagainstthecage root method, is there anyway to install the update without flashing a new ROM...I'm ok with stock.
If you're rooted - install custom recovery and install pre-rooted ROM.
Or try to apply the stock update through stock recovery, if you have it.
Wiggz said:
Right I can ask you the question then......with the rageagainstthecage root method, is there anyway to install the update without flashing a new ROM...I'm ok with stock.
Click to expand...
Click to collapse
Just install the OTA - it will unroot you.
then root with "rage"
check out modaco, he's got frg83 completely stock with root. just flash using custom recovery. I didnt do a wipe so everything stayed the same just updated to 2.2.1 and yes it seems the wifi issue was fixed.
Just get the stock rooted from geo411m's rom!
http://forum.xda-developers.com/forumdisplay.php?f=559
The links here will also do it in 2 steps from custom recovery:
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=8419658&postcount=194
The geo411m link is a deodexed ROM and the one in the link above is not deodexed. Either way you get the fixes of the newer version.
Going forward, think of it this way with future updates:
If you apply the OTA, intending to lose root and then re-root, you always run the risk that all avenues of rooting (other than unlocking the bootloader) have been closed by the new ROM.
If you apply an update repacked for custom recovery, you don't have to worry whether the root exploit you used last time will still be valid.
nexusdue said:
Just install the OTA - it will unroot you.
then root with "rage"
Click to expand...
Click to collapse
Thanks for that - honestly not sure why I didn't think of it
Ahh found a flaw in my plan.....it seems that verification fails on my Vodafone Nexus One (UK). I'm guessing there isn't an upgrade path from Vodafone's Froyo update to this yet. Suppose I'll have to wait for Voda's 2.2.1
Hello,
I have some question regarding HBOOT:
What is HBOOT?
What is the difference between Bootloader and HBOOT?
Why should I upgrade or why I shouldn't?
If I upgraded it is it easy to downgrade?
Mine is HBOOT-0.33.0012 and there is a version HBOOT-0.35.0017
Because some ROMs requires the newer version and I saw some article warn not to update!!
Thank you and Regards.
http://forum.xda-developers.com/showthread.php?t=910865
http://forum.xda-developers.com/showthread.php?t=913179
1. Hboot is the boot loader.
2. See above.
3. Upgrading to the new Hboot supposedly gives you some small benefits such as better reliability in certain cases. It is also supposedly required by gingerbread. Most of the AOSP builds of gingerbread don't require the updated Hboot, but the initial builds required it. If you upgrade to the new hboot, I believe you loose the ability to flash images by the PASSIMG method (renaming a signed image to passimg.zip). The new Hboot was rolled out as an update along with the FRG83D OTA. I see no real reason to upgrade it or downgrade it. Messing with it could be dangerous.
4. http://forum.xda-developers.com/showthread.php?t=726258 I wouldn't say it is easy, but it is possible to downgrade. Not sure why you would want to. Downgrading an SLDC Nexus will brick it.
The warning to not update was due to some ROMs not working on .35 as the update script was checking for .33, however this was months ago and is no longer an issue.
Thank you guys for the reply, I already upgrade it to use a gingerbread rom, I think I'm going to stick with it for awhile. If I needed urgent to downgrade it I will try it but not now.
Don't worry, you'll never need to downgrade it.
Rusty! said:
Don't worry, you'll never need to downgrade it.
Click to expand...
Click to collapse
You made me happy now