Jump to content

OTA Froyo from stock builds?


Recommended Posts

Guest jwhipple
Posted (edited)

My N1 had previously been rooted - the bootloader is unlocked.

Everything else has been put back to barebones stock, including the radio, the system, the boot, and the recovery.

At this point, shouldn't I be seeing the Froyo update available if I go to Settings / About / Updates ?

Or is the Froyo final OTA update only available at this point to those who were running the RC , or should I just give it time?

I've tried both via T-Mobile network and via home WiFi.

Thanks!

Edited by jwhipple
Guest joners
Posted
My N1 had previously been rooted - the bootloader is unlocked.

Everything else has been put back to barebones stock, including the radio, the system, the boot, and the recovery.

At this point, shouldn't I be seeing the Froyo update available if I go to Settings / About / Updates ?

Or is the Froyo final OTA update only available at this point to those who were running the RC , or should I just give it time?

I've tried both via T-Mobile network and via home WiFi.

Thanks!

Im still trying to find is someone can confirm that this is the final froyo build for the n1. From what i can tell this was only another internal build or test / rc build that was pushed to some phones, and it just looks like people have managed to 'find' the urls for downloading it.

Please someone correct me if im wrong!

Posted

IMO, considering FRF83 updates FRF50 only, this means it's an OTA update to the people who originally had the FRF50 build, and not the final general update that everyone should get.

It may or may not end up being the final version, it's just for the moment it's not yet the big OTA update everyone is praying for at night.

Guest jwhipple
Posted
IMO, considering FRF83 updates FRF50 only, this means it's an OTA update to the people who originally had the FRF50 build, and not the final general update that everyone should get.

It may or may not end up being the final version, it's just for the moment it's not yet the big OTA update everyone is praying for at night.

Ok this morning I went ahead and again put my phone back to 100% bone-stock shipping SYSTEM, BOOT, USERDATA, RADIO and RECOVERY (minus the unlocked bootloader of course). In the past (pre FROYO) I almost immediately got an update - but now I am just sitting here for over an hour and am getting nothing.

Trying to force the update via the ABOUT PHONE->System updates says I am up to date, which of course I know is not the case.

How long should I anticipate waiting? I'm sure the load on Google's systems is causing the delay with everyone updating, but I am merely curious how long I should figure on waiting before thinking something is wrong.

Thanks!

Guest echolock
Posted
Ok this morning I went ahead and again put my phone back to 100% bone-stock shipping SYSTEM, BOOT, USERDATA, RADIO and RECOVERY (minus the unlocked bootloader of course). In the past (pre FROYO) I almost immediately got an update - but now I am just sitting here for over an hour and am getting nothing.

Trying to force the update via the ABOUT PHONE->System updates says I am up to date, which of course I know is not the case.

How long should I anticipate waiting? I'm sure the load on Google's systems is causing the delay with everyone updating, but I am merely curious how long I should figure on waiting before thinking something is wrong.

Thanks!

No-one I personally know with Nexus Ones have had the Froyo OTA yet. I hear it's a very slow rollout (and those with the Vodafone build will have to wait even longer) and they certainly haven't gotten around to everyone having it yet. Myself I'm still locked and unrooted but I've been applying the "mini"/beta updates manually using the recovery mode.

On a personal note, does anyone know what the *#*#checkin#*#* actually does as it's never triggered an OTA for me :lol:

Guest jwhipple
Posted
No-one I personally know with Nexus Ones have had the Froyo OTA yet. I hear it's a very slow rollout (and those with the Vodafone build will have to wait even longer) and they certainly haven't gotten around to everyone having it yet. Myself I'm still locked and unrooted but I've been applying the "mini"/beta updates manually using the recovery mode.

On a personal note, does anyone know what the *#*#checkin#*#* actually does as it's never triggered an OTA for me :lol:

LOL I just tried that and the only thing it triggered was a checkin for updates of my installed apps - nothing for OTA :-) I guess I just learned something new!

Guest jwhipple
Posted

Ok now I'm a little concerned. Sure, I could do the updates manually, but I was really hoping to do OTA.

I've gone back to stock build on everything before and it never took more than an hour to update to at least the current OTA version (2.1 update 1) but now I am not even getting that.

Guest jwhipple
Posted
Ok now I'm a little concerned. Sure, I could do the updates manually, but I was really hoping to do OTA.

I've gone back to stock build on everything before and it never took more than an hour to update to at least the current OTA version (2.1 update 1) but now I am not even getting that.

I just did the manual update to ERE27 - I'm curious if that will "jump start" the process. At least it confirmed my thoughts that I was in an "OTA upgradable" state!

If I get any auto-updates I'll post!

Guest Wardski
Posted (edited)
I just did the manual update to ERE27 - I'm curious if that will "jump start" the process. At least it confirmed my thoughts that I was in an "OTA upgradable" state!

If I get any auto-updates I'll post!

I've just successfully done the revert back to stock unrooted ERD79 - after having an unlocked, rooted FRF91 - and then successfully updated to FRF91 using the original updates, and FRF91 OTA.

Thought I'd share my experience

While I followed this method (http://forum.xda-developers.com/showthread.php?t=614850) there are quite a few confusing things.

First of all, when you download the original 22607-ERD79-update-nexusone-stock-images.zip file and try to unzip it in windows, you get the error message that the conpressed file is invalid. Ignore this, and download 7-zip and unzip the files using this instead. Even Winzip will say invalid, so just use 7-zip (it works with windows 7 also)

Secondly, this tutorial doesnt say you need to flash the original baseband radio file, where is in fact my experience says if you want to return to stock, then get the ERE27 OTA, you will need to flash back the old radio image as well in order for the OTAs to work properly. So flashboot flash radio ....img as well that comes in the original ERD79 images file noted above.

So, after following the Xda developers method as mentioned above to revert back to ERD79, I then waited.. I did the checkin about 10 times, and still no update to ERE27.

After a few days, I ended up getting frustrated and downloading the original update package - ERD79 to ERE27 update, renaming the file to update.zip, then using the stock recovery to flash it. It worked fine.

Then I waited for another OTA.... nothing happened, even after 2 days, and multiple checkins.

So I got frustrated again, and decided to go about finding the original Froyo update (this file is "signed-passion-ota-42745.dc39ca1f.zip"). This file updates you from your current OS version what ever that may be (eg, you can even do it from ERD79 or ERE27!) Now after looking around, of course this file is no longer available direct from google (how convenient) and most other forum links are dead, so plug that exact name into google search, and you'll find a mediafire link (I used this one http://www.mediafire.com/?j5zejudgngm) - download this 85mb file, rename to update.zip, put it on your SD card, and use the stock recovery to flash it.

After flashing this, I ended up with FRF85B on my N1.

Amazingly, straight after the first boot, I got an on screen message notifying me of the FRF91 OTA, downloaded and installed it (thus i can conclude that OTA's are now working).

So, for those frustrated waiting @ ERD79 after a full restore, and nothing is happening, i think Google aren't OTA updating the earlier firmwares anymore. I would suggest that from FRF50 onwards will get the OTA's, but anything prior to that, no. So my recommendation is just to download the "signed-passion-ota-42745.dc39ca1f.zip" after a full restore back to ERD79 - which will give you the fast lane up to FRF85B, and then ready to receive all new OTA's.

Now if only someone could workout how to root, and still receive OTA's, so I can use setCPU and keep my N1 @ 1Ghz... lol

Hope this helps.

Edited by Wardski
Guest jwhipple
Posted
I've just successfully done the revert back to stock unrooted ERD79 - after having an unlocked, rooted FRF91 - and then successfully updated to FRF91 using the original updates, and FRF91 OTA.

Thought I'd share my experience

While I followed this method (http://forum.xda-developers.com/showthread.php?t=614850) there are quite a few confusing things.

First of all, when you download the original 22607-ERD79-update-nexusone-stock-images.zip file and try to unzip it in windows, you get the error message that the conpressed file is invalid. Ignore this, and download 7-zip and unzip the files using this instead. Even Winzip will say invalid, so just use 7-zip (it works with windows 7 also)

Secondly, this tutorial doesnt say you need to flash the original baseband radio file, where is in fact my experience says if you want to return to stock, then get the ERE27 OTA, you will need to flash back the old radio image as well in order for the OTAs to work properly. So flashboot flash radio ....img as well that comes in the original ERD79 images file noted above.

So, after following the Xda developers method as mentioned above to revert back to ERD79, I then waited.. I did the checkin about 10 times, and still no update to ERE27.

After a few days, I ended up getting frustrated and downloading the original update package - ERD79 to ERE27 update, renaming the file to update.zip, then using the stock recovery to flash it. It worked fine.

Then I waited for another OTA.... nothing happened, even after 2 days, and multiple checkins.

So I got frustrated again, and decided to go about finding the original Froyo update (this file is "signed-passion-ota-42745.dc39ca1f.zip"). This file updates you from your current OS version what ever that may be (eg, you can even do it from ERD79 or ERE27!) Now after looking around, of course this file is no longer available direct from google (how convenient) and most other forum links are dead, so plug that exact name into google search, and you'll find a mediafire link (I used this one http://www.mediafire.com/?j5zejudgngm) - download this 85mb file, rename to update.zip, put it on your SD card, and use the stock recovery to flash it.

After flashing this, I ended up with FRF85B on my N1.

Amazingly, straight after the first boot, I got an on screen message notifying me of the FRF91 OTA, downloaded and installed it (thus i can conclude that OTA's are now working).

So, for those frustrated waiting @ ERD79 after a full restore, and nothing is happening, i think Google aren't OTA updating the earlier firmwares anymore. I would suggest that from FRF50 onwards will get the OTA's, but anything prior to that, no. So my recommendation is just to download the "signed-passion-ota-42745.dc39ca1f.zip" after a full restore back to ERD79 - which will give you the fast lane up to FRF85B, and then ready to receive all new OTA's.

Now if only someone could workout how to root, and still receive OTA's, so I can use setCPU and keep my N1 @ 1Ghz... lol

Hope this helps.

I got a bit fed up with the waiting and re-rooted and flashed MCR21 FRF91 .... I'm glad I did too because based on what you are saying, I would never have received the updates!

With Froyo being so "Young", I just wanted the ability to OTA update if any new updates come out...

Oh well - I'm enjoying it now, just a shame that they make it such a hassle to get.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.