Welcome to the Android Central Forums Create Your Account or Ask a Question Answers in 5 minutes - no registration required!
Results 1 to 15 of 15
  1. Thread Author  Thread Author    #1  

    Default New Flash OTA: How do I stop it from coming?

    I am running BBv0.4 and manually installed flash 10.1. This OTA includes "security updates" so I consistently press "install later." Is there any fix?
  2. #2  
    thebizz's Avatar
    phone addict

    Posts
    3,579 Posts
    Global Posts
    3,731 Global Posts
    ROM
    mean

    Default

    Flash spr recovery the click install update. The good thing about spr is it wont flash an update.zip unless you click allow so let it do its thing and the install will be aborted. Or you can rename ocerts.so to ocerts.so.bak will get the full location for you in a sec
    Loving this Oneplus one!!
  3. #3  
    nox
    nox is offline
    nox's Avatar
    Retired Super Moderator

    Posts
    1,364 Posts
    Global Posts
    1,370 Global Posts

    Default

    The bad thing about the renaming is that it'll constantly try and reach the update server, draining your battery in a quickness.

    If you're rooted and have a custom recovery, then you should be perfectly fine.
    Both SPRecovery and ClockWorkMod Recovery do not allow an update.zip to be installed without your permission.
  4. #4  

    Default

    my wife's droid got the notification, i have her running bbv0.4, i knew clockwork would block it, so i chose to install it.. it was blocked, no more notification.
  5. #5  

    Default

    I accidentally let this install and now my phone is completely unrooted, which I could live with, however I cannot access my phone's settings and I have a constant error on my email client that I cannot get to go away because it just force closes when I try to open it.

    Looks like the only way to fix this will be a full recovery unless anyone has any other solutions here
  6. #6  

    Default

    So I let it install and clockwork will block it, is that correct?
  7. #7  
    Dirrk's Avatar

    Posts
    243 Posts
    Global Posts
    245 Global Posts

    Default

    Yes
    Google Plus+
    Current Devices: Samsung Galaxy Tab 10.1 - Samsung Charge
  8. #8  
    Ratchet's Avatar

    Posts
    265 Posts
    ROM
    Stock

    Default

    I tried the install block today and was successful. I'm running on rooted 2.2 OTA.

    Flashed SPrecovery via Rom Manager, clicked "install and restart" on the flash update, phone rebooted and stuck at the "M" screen. I let it marinate for 20-30 seconds, did a battery pull and everything is fine now. No more annoying update notification.

    Not sure if anyone else has gotten stuck at the first boot screen, but thought I'd share my experience just incase.
    Samsung Galaxy S3
  9. #9  

    Default

    I'm going ahead and doing this right now as well. I have Clockworkmod recovery, and have been getting rather annoyed by the constant OTA reminders. Hopefully this will work..

    *update*

    It worked!
    OG Droid > Moto Droid 3.
  10. #10  
    Ratchet's Avatar

    Posts
    265 Posts
    ROM
    Stock

    Default

    Quote Originally Posted by anthonyzul View Post
    I'm going ahead and doing this right now as well. I have Clockworkmod recovery, and have been getting rather annoyed by the constant OTA reminders. Hopefully this will work..

    *update*

    It worked!
    Yup. If the recovery loads properly, you'll read in the display where it says "Update.Zip" blocked.

    Simply nagivate the dpad to "reboot now" and the annoying notifications will cease.
    Samsung Galaxy S3
  11. #11  

    Default

    Well...

    It SEEMED to work.. But the notifications have come back! I can do the same thing again, but is there not a more permanent solution? I don't want to have to deal with and OTA notification every couple of weeks..
    OG Droid > Moto Droid 3.
  12. #12  
    Ratchet's Avatar

    Posts
    265 Posts
    ROM
    Stock

    Default

    Have you installed a different ROM or kernal by chance since you did the first "attempted update install?"
    Samsung Galaxy S3
  13. #13  

    Default

    Same thing happened to me. I am running the stock 2.2 ROM (the first one that didn't have flash) rooted. I got rid of the update message by booting into clockwork recovery and it went away. Today it came back. I am rebooting again into recovery to get rid of it (again).
  14. #14  

    Default

    Fix credit to GirLuvsDroid:

    1. In Root Explorer, go to /system/
    2. Tap Mount R/W at the top, then long-press on build.prop and scroll down to Open in Text Editor
    3. Once the file is open as a text file, scroll down until you see the line that says: "ro.build.fingerprint=verizon/voles/sholes/sholes:2.2/FRG01B/45394:user/release-keys" and change it to read as follows:
    ro.build.fingerprint=verizon/voles/sholes/sholes:2.2/FRG22D/50454:user/release-keys
    4. Tap the back key and say "Yes" when it asks you to save (it will automatically back up the original file for you)
    5. Tap Mount R/O at the top
    6. Reboot
  15. #15  

    Default

    Ratchet.. I hadn't flashed anything. I rooted with EasyRoot, but had not flashed anything.

    pwrmetal.. That is exactly what was happening to me! I did just flash CM6 though, and so far it hasn't appeared again.
    OG Droid > Moto Droid 3.

Posting Permissions