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?
Hi All,
Im on the Official ICS ROM INDIA...4.0.3 DDLP4
Yesterday, when i checked kies, there was an update waiting (No Update on OTA). The downloading of firmware was taking ages to download(3.2mbps connection) and after about 70 percent the downloading stopped and Kies said "Connection stopped"....
Any body who has downloaded the F/W can you please post the change log (If you find any).. I mainly wanna know, if the laggness of the lock screen and slowness to open contact's and capturing pics has been rectified.
Ramith123
Ah glad that i have company.sad at the same time!! Even i have the same problem after the 7mb OTA update. The andriod process closes often and hangs the phone.The phone was literally unusable. Hence i tried to install custom gingerbread rom on it. Now its almost completely bricked.How irresponsible is samsung to roll these things out without testing it thoroughly.
***PLEASE DON'T INSTALL THE 7MB ICS OTA UPDATE***
hopefully we can save some.
I also tried to update through OTA but it was failed and message popped up that do update through Kies. Now I got update through Kies and my firmware changed from DDLP4 to DDLPA. However I lost Root.
I also received the update notification. Downloaded the 7.8 mb update within a minute and asked for reboot. Everything worked fine and nothing special noticed. It just changed the build no. from IML74K.DDLPA to IML74K.DDLP8
dushy4 said:
I also received the update notification. Downloaded the 7.8 mb update within a minute and asked for reboot. Everything worked fine and nothing special noticed. It just changed the build no. from IML74K.DDLPA to IML74K.DDLP8
Click to expand...
Click to collapse
you mean LP8 to LPA? check your kernel version date. if it shows 12 June then fine, else your kernel has not been updated.
Hey guys basically its stability update. my phone feels much smoother now. i updated OTA via wifi, i also faced update not installed issue and i found out the problem, basically we all root our device that means we change SU binaries so when updating phone OTA it checks for those binaries and if these binaries are not official OTA update get aborted. i solved this problem like this,
1) I have downloaded STOCK LP8 firmware from samobile.com when it released
2) As my phone is rooted my SU binaries are changed so OTA update is aborted.
3) So FLASHED Stock rom LP8 from PC ODIN which kept my all DATA, APPS intact i just lost my root and some mods like 15toggles status bar and so..
4)then i started updating my phone using S/W update in settings, its 7.85MB file.
5)In few minutes my phone is updated to LPA
6)Now i again rooted my phone and my all data apps are intact and mob is much improved in stability.
Hope this will help you guys.
anjath said:
you mean LP8 to LPA? check your kernel version date. if it shows 12 June then fine, else your kernel has not been updated.
Click to expand...
Click to collapse
It still shows 12 may,,, But i read in some other thread that kernel was not updated in this update.
dushy4 said:
It still shows 12 may,,, But i read in some other thread that kernel was not updated in this update.
Click to expand...
Click to collapse
kernel is definitely updated in LPA. just flash LPA ROM file using Odin.
I also agree with what mullarameez has pointed out. rooting might be the reason for kernel being skipped. because if u flash LPA with odin you will lose root and hence get the new kernel.
Is there a way to update Kernel without flashing the whole 650 mb rom?
with all the issues in ICS, i think it would be safest if you would flash using the whole LPA ROM. I know its a pain to download but worth it in the end.
OMG! just a 7Mb update took 2hrs to download.. Hmmmm...
My main prob was with Lock screen, camera and contacts.. Noting has been resolved on this new Update!!!
what is the issue? is it lag?
This is confusing..
I have everything stock on my phone..All updates done OTA since i bought the phone..Not rooted..
Still the kernel says 12 May after the 7mb update..Why?? Although the deep sleep issue (sore point for me) seems to have been resolved after this update...
PS: The build info after *#1234# says 12 June, if that matters..
yes, almost all the users who updated OTA have the same issue. you may flash the new LPA using PC Odin from doc's post (anyways you're not rooted so no problem)
I just bought a new R1 HD Prime version. It's on 6.1, and the wireless update is showing that no updates are available. So I've tried manually downloading the OTA updates and applying them from local storage using the wireless update app, but I get an error message when attempting to do so (Signature verification failed). How am I supposed to update this phone? It's completely stock.
The only thing I've noticed is that the build time of what's on my phone is slightly different than what the 6.4 OTA says it's supposed to be updated from:
My build - BLU_R0010UU_V6.1_GENERIC 17-06-2016 14:53
OTA build - BLU_R0010UU_V6.1_GENERIC_6.0_20160617-1456
Notice the build time is different by 3 minutes. Is that maybe the source of the problem I'm having? I'm honestly at a loss here and I really want to get this phone updated.
Found out what the problem was with the manual OTA...I committed that cardinal sin of not opening up the zip file and realized I needed to extract update.zip I'm still not sure why the wireless update wasn't getting the OTA from 6.1 to 6.4, but once I was able to manually update to 6.4 I got the subsequent OTAs.
I have been on Android 12 (official OTA) for about 2 weeks now.
A couple of nights ago, I got an OTA message to welcome me to Android 12, and to download the 1.8Gb update.
I've not had any issues with A12, but I look through the Goggle forums, and see many who have, so I went ahead with the update.
I'm on UK EE.
Turns out, this update is a Verizon build.
The first full Android 12 OTA I had:
Baseband: g7250-00147-210811-B-7631450
Build number: SP1A.211105.003
After the "new" update this is now:
Baseband: g7250-00147-210830-B-7686829
Build number: SP1A.211105.002.A1
I went on Full OTA images to sideload my original (and correct) build back on but it refuses, saying that my current version is newer than the one I'm trying to download, and that a "downgrade" is not possible.
My question is, when the December OTA comes through, will my phone automatically get the correct build and get rid of this rogue Verizon build?
Or will I have to decline the update, and do a manual sideload of the new OTA (non-Verizon) build?
Thanks
hawkerpaul said:
I have been on Android 12 (official OTA) for about 2 weeks now.
A couple of nights ago, I got an OTA message to welcome me to Android 12, and to download the 1.8Gb update.
I've not had any issues with A12, but I look through the Goggle forums, and see many who have, so I went ahead with the update.
I'm on UK EE.
Turns out, this update is a Verizon build.
The first full Android 12 OTA I had:
Baseband: g7250-00147-210811-B-7631450
Build number: SP1A.211105.003
After the "new" update this is now:
Baseband: g7250-00147-210830-B-7686829
Build number: SP1A.211105.002.A1
I went on Full OTA images to sideload my original (and correct) build back on but it refuses, saying that my current version is newer than the one I'm trying to download, and that a "downgrade" is not possible.
My question is, when the December OTA comes through, will my phone automatically get the correct build and get rid of this rogue Verizon build?
Or will I have to decline the update, and do a manual sideload of the new OTA (non-Verizon) build?
Thanks
Click to expand...
Click to collapse
According to the Google Pixel Community Forum this is going to be fixed automatically by the Global December build.