- 09-01-2010, 03:40 PM #2
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 secLoving this Oneplus one!!
- 09-02-2010, 03:17 AM #3
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.
- 09-02-2010, 10:28 AM #4
- 09-02-2010, 11:19 AM #5
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
- 09-03-2010, 05:18 PM #6
- 09-05-2010, 12:54 PM #7
- 09-06-2010, 02:22 PM #8
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
- 09-09-2010, 10:48 AM #9
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..
Last edited by anthonyzul; 09-09-2010 at 12:49 PM.OG Droid > Moto Droid 3.
- 09-09-2010, 02:19 PM #10
- 09-13-2010, 12:34 PM #11
- 09-13-2010, 02:55 PM #12
- 09-14-2010, 04:02 PM #13
- 10-04-2010, 02:14 PM #14
- 1 Posts
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:
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
- 10-11-2010, 06:43 PM #15