I'm on stock FRF85B, because I want to try the vanilla Google Experience of Froyo before switching to CyanogenMod 6 when it's out. I didn't upgrade to FRF91 when it was released, so I got the OTA. However, because I have a custom recovery, I can't install the OTA update.
The system update says that it contains security fixes. If it's really just that, I won't bother upgrading to FRF91 before switching to CM6 when it's out.
What exactly is the difference between FRF85B and FRF91?
There is no difference. As you said its just some minor under the hood security fixes.
Could it be that the security fixes in FRF91 prevent adb from finding "recovery" to stop rooting? It seems that the threads for rooting without unlocking require non-FRF91.
Related
I'm considering rooting and using the latest CM ROM, but there's been a lot of talk lately about the Dream getting an official 2.x OTA update. If I load the CM ROM and am rooted, will I have the ability to load the T-Mobile update if and when it comes out? (it seems like this would have been discussed before, but a quick search didn't turn up anything)
TeeJay3800 said:
I'm considering rooting and using the latest CM ROM, but there's been a lot of talk lately about the Dream getting an official 2.x OTA update. If I load the CM ROM and am rooted, will I have the ability to load the T-Mobile update if and when it comes out? (it seems like this would have been discussed before, but a quick search didn't turn up anything)
Click to expand...
Click to collapse
Yes but you'll lose root. When it comes out I would just wait for enomther to release the root version (~5 min.)
Hi,
anyone has a tip how I can downgrade from FRF91 (whic I got via OTA this mornig) back to FRF83?
I really regret upgrading.. overall feeling is worse, and GPS seems to stop fixing on satellites at all..
so - may be someone has a reliable method to go back to FRF83? or any tips how to get GPS back into functioning correctly?
thanks!
Ok, it seems that I've fixed most of the issues.
for those that also have the GPS issue (the most noticable) after the OTA update from FRF83 to FRF91 - here it is how I've fixed it:
I've downloaded the full FRF91 image : the link can be found is in this post: Official Froyo OTA
and manually installed it via recovery. Basicaly - FRF91 over FRF91 - but it did the trick and I'm happy now.
Did you try wiping the cache from recovery? Seems to have helped a few people with issues.
I want to update my nexus to FRF85b. However, i found that all the links are dead. Is there any other links to download the update? ( without rooting pls )
Really nid help in this. Cant find any links . Thks in advance.
I just got the update OTA this morning (even though I'm rooted!), unfortunately it could not be applied because either I have a custom recovery, or I'm rooted. (verification failed)
Havent seen an FRF83 to FRF91 update file, so you probably need to go from FRF83 -> FRF85B -> FRF91
http://www.redmondpie.com/download-android-2.2-froyo-frf91-nexus-one-stock-root/
I am also having this issue, the frf83 to frf85b file seems to be taken off google servers.
Yeah but how do you get to FRF83 -> FRF85B? Can't find anything have been looking for 15mins.
The link from google is down.
Oh wait, I think you can use the Universal FRF91 OTA Update?
britoso said:
I just got the update OTA this morning (even though I'm rooted!), unfortunately it could not be applied because either I have a custom recovery, or I'm rooted. (verification failed)
Havent seen an FRF83 to FRF91 update file, so you probably need to go from FRF83 -> FRF85B -> FRF91
Click to expand...
Click to collapse
That's what I had to do - I needed to find/download the stock FRF83, FRF85B, FRF91 roms that could be applied with a custom recovery.
i got the OTA msg but i do not want to update until a proper FRF91 mod comes out. i am currently running kang-o-rama 0.9 and am completely happy with it.... is there a way to get rid of this annoying update msg or can i just update and reinstall the custom rom?
I've got a Nexus 6 with Verizon Wireless. It is purely stock: I have never rooted or modified the phone in any way other than accepting the standard OTA updates pushed out by Google/Verizon.
I've been patiently waiting for the OTA update to upgrade my phone to Nougat, but I haven't seen any updates in over a month. My phone is currently running MOB31H (6.0.1) which, according to the Google Factory Images page is the security update from October 2016. However, according to the same page there have been two security updates in November (MMB31C and MOB31K), and there have been two versions of Nougat released since then (NBD90Z and NBD91P). My phone has not seen any of these updates, despite repeatedly checking for updates via the settings menu.
I've got a few questions along these lines:
1) I've seen rumors about trouble with Nougat, which suggests maybe Verizon/Google have been delaying a widespread roll-out. However, I have not seen anything posted recently about this (latest reports are from early October), and what I did see seemed focused on other phones (not the Nexus 6). Are there any known issues with Nougat running on the Nexus 6 that would make me want to delay upgrading manually?
2) Is it unusual for my Nexus 6 to still be running 6.0.1 with the October security update? Shouldn't it have at least received the November security updates? Have others experienced this issue?
3) If I download the OTA directly from Google and sideload the update, will this disable the automatic OTA updates in the future? I'd like to at least apply the November 6.0.1 security updates to keep my phone secure.
4) If I want to update my phone to Nougat manually, can I simply download the OTA for Nougat and follow the instructions Google includes for sideloading the OTA update? Or do I have to download the entire 7.0 factory image and install that image? I have experience installing the factory images (I have a Nexus 10 that I've had rooted for a while, so I've gotten good at installing the factory images whenever a new image is released) but it is still a bit of a pain and I would prefer the OTA updates for my phone if I can.
4a) If I can update via the OTA, can I pick the latest OTA (NBD91P), or do I have to go incrementally (install NBD90Z first then update to NBD91P)?
5) Only tangentially related question: I've noticed that Google has included the month and year on more recent factory images, but is there any way to determine the exact date that an image was released? For example: I see there are two November OTA updates for Nexus 6, how can I tell if MOB31K was released this morning vs. November 2? If it was released this morning that may explain why I haven't seen the update yet, but if it was released November 2 I would be surprised I haven't seen the update yet.
Thanks in advance for any help.
1. Verizon has no control over updates on this device. That said, no major issues with the stock ROM.
2. Not unusual at all. When I received my N6 earlier this year it stopped updating after the latest Android 5.0.1 update. I had to flash an Android 6.0.1 image manually.
3. No.
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
5. No way to tell outside of paying attention here, since someone will inevitably announce the release of the latest version. Of course, once you've installed the latest image, OTA updates should continue as usual if you don't modify the firmware like most of us do.
Thanks for the helpful reply! One quick follow-up:
Strephon Alkhalikoi said:
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
Click to expand...
Click to collapse
I will likely follow your advice regarding updating from the full factory image instead of the OTA. My main limitation is my two-factor authentication. Because I haven't rooted, it is a pain to transfer some of that from one device to another (in some cases it requires disabling two-factor authentication and re-enabling it on each site, and I have at least 12 website that are using two-factor authentication on my device). I need to make sure that I don't accidentally lose the authentication tokens.
If I get lazy, or just want to "risk" using the OTA: Can I use either OTA image (the one from October or November) to upgrade from 6.0.1 to 7.0? Or does the one from October apply a full update and the November is just an incremental update intended to by applied to an existing 7.0 build?
Both are full updates. I'm not sure as to how well your current data will transition over to Android 7.
I would look into finding a means of backing up your authenticator.