Database Develop

Froyo for AT&T/Rogers (build EPE54B)

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.

Build EPF21B to Froyo

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

will I get stuck with FRF50 forever?

It looks like FRF85B is released, but I tried to run OTA using *#*#checkin#*#* and nothing happened.
When I tried to use manual update, I got assert-failed error.
Will I get stuck with FRF50? I am using stock "everything", no root, no unlocked bootloader.
Will unlocking bootloader fix such problem?

just wait for the official OTA. not everyone is on froyo
if you want to root, thats fine, but if its simply for froyo then you may wanna consider that your warranty was voided for impatience, not for unlocking greater benefits

[Q] how to return to stock recovery with locked bootloader?

im gona send my phone in as a replacement, but i want to make sure everything looks stock before it send it in, i found a couple of ways to return to stock but i keep getting signiture verified failed, and i assume its because i have an unlocked bootloader, can any 1 help?

You should be able to find the stock rom for unlocked users in the development section. Just flash that and you will be back on stock.
But you can't re-lock the bootloader. When you unlocked it you voided the warranty, and it stays that way.
If it is a physical hardware problem, you should be able to still get warranty though.

Sorry, I meant to say my bootloader is locked, I don't have a problem with the rom, but the recovery. I am on ra recovery atm and I want to go back to google's stock. Is there anyway to do that?

Im pretty sure this works for all phones but if you flash Official OTA it will put everything back to stock(except bootloader if it has been unlocked) but doing this you will also loose root as well
i would wait for some one to tell you another way to get back to stock recovery, im sure there is a way to do it in adb or something.. Flashing the official OTA should be like a last thing wanting to do

Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space

codearray said:
Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space
Click to expand...
Click to collapse
He cant do fastboot, he has locked Bootloader.

yeah, it saids verification failed and wouldnt let me flash anything onto it

oops my bad. I had an unlocked bootloader. My other phone is locked.
sent from outter space

vvaffles said:
yeah, it saids verification failed and wouldnt let me flash anything onto it
Click to expand...
Click to collapse
Yeah i had the same problem when i tried to revert mine to stock. My bootloader was lock and wouldnt let me reflash the stock rom with verification failed.
NOT SURE IF THIS IS THE CORRECT WAY, DO AT YOUR OWN RISK :
I renamed the image to PASSIMG.zip and booted into bootloader. The bootloader automatically searches for PASSIMG and when it found it went through an update/installing process which took about 5minutes. When it booted phone was unrooted again, and had the stock recovery.
Once that was done, i installed the FRF85 (i think) update.zip from bootloader recovery, then did the same with update.zip for FRF91.
Again not sure if this was the correct way as i have never seen posts directing to do it this way - have posted questions about it in the past week or two, but never got any responses...

I'm gonna bump this thread up again. I tried downloading the original PASSIMG file for the stock and when I try and flash it by putting it on the SD card I get that the main file is older and the install is aborted. I can't fastboot the files because my bootloader is not unlocked. I'm currently running a FRG83 based ROM, does this matter? I'd like to return my phone to stock recovery and stock ROM, but so far every attempt has been met in failure... I guess it's an irony of rooting a phone without unlocking a bootloader. If you have to send it in for repairs you have to unlock the bootloader to return to stock, or you can't return to stock and you're left with custom recovery and root... either way HTC knows you're rooted. I know my issue is a hardware issue, but it would be my luck they decide to void my whole warranty.

You can't just PASSIMG your way back from FRG83, if you have it - since there's no PASSIMG for FRG83 yet (at least I'm not aware of one, and looks like Google isn't either), and the system is designed not to flash older builds. Trying to use PASSIMG to return to older builds requires some heavy preparations (has to be rooted, then downgrading HBOOT and probably flashing initial system.img from an older build through adb in recovery, using flash_image). It's possible and not very hard to do, but most probably beyond "1-click-root"ers' skills. All the relevant info is in the Wiki, so if you want to attempt it - you can try.
Unrooting FRG83 (reflashing stock recovery from FRF91, removing su and Superuser.apk from root shell) might be easier.
Also, put attention that if the phone has SLCD screen - the official stock FRF91 won't work on it.

I actually was able to PASSIMG to FRG33 then OTA back to FRG83. which I thought was odd due to the fact that I was on a FRG83 based rom. Oh well, it's 100% back to stock now. So even though people say that a rooted/unlocked phone only voids your software warranty I don't have to worry about it. Yay for keeping a locked bootloader.

Help with network branded firmware

Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.

bobsie41 said:
Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.
Click to expand...
Click to collapse
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.

wnp_79 said:
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.
Click to expand...
Click to collapse
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
S-off together with super cid would give us the ability to use any RUU for this device which gives us an excellent safety net.

bobsie41 said:
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
Click to expand...
Click to collapse
It's ok. It's always best to be sure before attempting something!
You will not loose out on anything by not using an official update. All it will be is the stock firmware with T-Mobile's add touches. More often than improvements to the stock firmware, carries tend to restrict the features of a ROM and add bloatware (like game demos you can't uninstall) because they have made a deal with a game developer to make some money forcing them upon you.
Even without a nandroid backup you'll still be able to download and flash the stock firmware somewhere here. Basically anything you do to your phone you will be able to undo if you so choose. The only exception to this is that if you re-lock your bootloader, HTC will still be able to tell that it was at some point unlocked if you wanted a warranty return.

Yeah, as long as the stock bootloader is available, you just need to flash it after restoring the backup, and the updates should arrive.
The firmware might be flashable without the RUU or OTA, it was on the One X, but it was necessary to relock the bootloader.
I say go for it, mike1986 has the stock ROM in the dev section as well as his stock like improved ROM.