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
So I just bought the XT1068 and I know that the L update is still not released in India so how can I flash it instead of waiting for the OTA? Any step-by-step guides would be helpful because I am quite the noob. My phone is brand new, just removed out of the box so please tell me how to flash the update.
Ajit99 said:
So I just bought the XT1068 and I know that the L update is still not released in India so how can I flash it instead of waiting for the OTA? Any step-by-step guides would be helpful because I am quite the noob. My phone is brand new, just removed out of the box so please tell me how to flash the update.
Click to expand...
Click to collapse
Check this out:
http://droiddefy.com/how-to-update-...69-to-official-android-5-0-lollipop-manually/
That is the best tutorial i could find! Cheers!
Edit:
There could be some bugs for dual sim models. the xt1069. Make sure to read the comments and especially the tutorial
Ajit99 said:
So I just bought the XT1068 and I know that the L update is still not released in India so how can I flash it instead of waiting for the OTA? Any step-by-step guides would be helpful because I am quite the noob. My phone is brand new, just removed out of the box so please tell me how to flash the update.
Click to expand...
Click to collapse
Mate, I'd hold on a bit if I were you . You have to unlock your bootloader to flash these ROMs. Unlocking means losing your warranty (special case in India :crying. And there's also tiny bugs in those ROMs.
aditya.upadhyaya said:
Mate, I'd hold on a bit if I were you . You have to unlock your bootloader to flash these ROMs. Unlocking means losing your warranty (special case in India :crying. And there's also tiny bugs in those ROMs.
Click to expand...
Click to collapse
It all depends - while I will leave the research up to you, I was able to update without unlocking the bootloader on an xt1064. The trouble is that all the pieces have to fall into place correctly, meaning that you have to have the right update file for your build (and YOUR device - xt1068). My update process was haphazardly documented here. Basically, I started out with a carrier locked (Consumer Cellular) version of the phone, running their specific build. I unlocked the phone's sim lock via online vendor, flashed over the latest factory firmware I could find at the time (21.11.23.titan_retuaws). from there, I installed the specific update to go from 21.11.23 to 22.21.25 (where I am now). but that's the kicker - you need the OTA files that correspond to your exact build(s) and there may be more than one to get you all the way up to current.
Anyway, I did all of this using official, signed OTA files and firmware and more importantly, with a locked bootloader.
joeparker54 said:
It all depends - while I will leave the research up to you, I was able to update without unlocking the bootloader on an xt1064. The trouble is that all the pieces have to fall into place correctly, meaning that you have to have the right update file for your build (and YOUR device - xt1068). My update process was haphazardly documented here. Basically, I started out with a carrier locked (Consumer Cellular) version of the phone, running their specific build. I unlocked the phone's sim lock via online vendor, flashed over the latest factory firmware I could find at the time (21.11.23.titan_retuaws). from there, I installed the specific update to go from 21.11.23 to 22.21.25 (where I am now). but that's the kicker - you need the OTA files that correspond to your exact build(s) and there may be more than one to get you all the way up to current.
Anyway, I did all of this using official, signed OTA files and firmware and more importantly, with a locked bootloader.
Click to expand...
Click to collapse
NIIIICEEE!!!!!! But the problem here is, we don't have Lollipop OTAs for XT1068/69 to do that.:crying:
I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance
pokedroid said:
I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance
Click to expand...
Click to collapse
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.
You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?
ac3theone said:
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.
Click to expand...
Click to collapse
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
rootSU said:
You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?
Click to expand...
Click to collapse
I just installed it as an update.zip using adb. No unlock required.
pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
FYI, AT&T have no control over the update process. The update comes directly from Google, for all carriers. As long as you didn't install M or I, you're fine. There is nothing that AT&T could do to prevent anyone getting the update. Except maybe sending a memo out to a staff saying "you'll receive an update from Google. Please, please, please don't accept it"
pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.
ac3theone said:
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.
Click to expand...
Click to collapse
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung
rootSU said:
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung
Click to expand...
Click to collapse
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?
ac3theone said:
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?
Click to expand...
Click to collapse
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0
rootSU said:
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0
Click to expand...
Click to collapse
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*
pokedroid said:
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*
Click to expand...
Click to collapse
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,
rootSU said:
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,
Click to expand...
Click to collapse
Oh, I was thinking the boot loader status would show "relocked" when in fastboot
It's security updates up to May 1st. I can't install it though it fails and I am stock with unlocked bootloader.
Comet1966 said:
It's security updates up to May 1st. I can't install it though it fails and I am stuck with an unlocked bootloader.
Click to expand...
Click to collapse
I'm in the same boat. I just followed this thread and did everything right when restoring my stock ROM for Sprint. The only thing I didn't do was lock the bootloader. I cannot do OTA updates, fails every time. Someone mentioned a few pages in that thread, that right now it's a 50/50 chance due to an unknown variable. Give the forum time we will get it
Link to thread: https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
I'll try tonight after the Gym and see if I can get it to update for me
JordanFromIT said:
I'm in the same boat. I just followed this thread and did everything right when restoring my stock ROM for Sprint. The only thing I didn't do was lock the bootloader. I cannot do OTA updates, fails every time. Someone mentioned a few pages in that thread, that right now it's a 50/50 chance due to an unknown variable. Give the forum time we will get it
Link to thread: https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Click to expand...
Click to collapse
For me, that variable is twrp. If I flashall to stock I can take the ota, then resinstall twrp and root after. Worked today too.
I was going to install LineageOS and just gave up on it lol. So I flash-all'd back to stock and the OTA worked this time.
So is there a method for clean flashing or i just flash over a rom using fastboot? I tried flashing a retail rom on my tmobile variant, it work but some things were broken.
Comet1966 said:
I was going to install LineageOS and just gave up on it lol. So I flash-all'd back to stock and the OTA worked this time.
Click to expand...
Click to collapse
which flashall did you use? I'm trying to do this too and it fails no matter what. did you also re-lock the boot loader for the ota to work?
I've tried unlocked and locked and it still doesn't take the OTA for me.
byt3b0mb said:
which flashall did you use? I'm trying to do this too and it fails no matter what. did you also re-lock the boot loader for the ota to work?
I've tried unlocked and locked and it still doesn't take the OTA for me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
I used the sprint oreo flash-all from that link, 2nd post. I just ran it and then updated without issue.
Comet1966 said:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
I used the sprint oreo flash-all from that link, 2nd post. I just ran it and then updated without issue.
Click to expand...
Click to collapse
oh. I am on T-Mobile. seems that im on december security patch although im on 27.1. something is wrong with my phone...
You'd think Motorola would have released an updated flash-all. Maybe they have?
Josh McGrath said:
You'd think Motorola would have released an updated flash-all. Maybe they have?
Click to expand...
Click to collapse
I doubt it. The Feb release of the Dec update got released two months later. (Apr 7th)
This phone is really weird. I got the update to work the very first time I flashall but twrp bootlooped and it won't install after the second flashall, tried multiple times.
This phone is really software wonky
the zip files from Tmobiie are NASH_TMO_C_OCX27.109-51.... Does anyone know the difference between this and the OCX27.109-48-6?
kendallgreen said:
the zip files from Tmobiie are NASH_TMO_C_OCX27.109-51.... Does anyone know the difference between this and the OCX27.109-48-6?
Click to expand...
Click to collapse
When the update first came out, the December path I think, it was simply generic Android security updates, nothing specific to our phone or fixes, at least for the TMobile version