• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root rooted 2.2 now vzw is pushing update: what to do?

schwim

schwim

Well-Known Member
Hi there everyone,

Using the tutorial thread here, I rooted my phone. Tonight I got notice on the phone that 2.3 was ready for install, which would begin on the next restart. I can't see any way to stop it.

Someone said before that the update probably wouldn't succeed because of the root, but I don't want to test the theory if possible. Is there any way to politely decline the upgrde before my next restart?
 
I am looking to install the update on my rooted incredible and would like to know how I can do that. The update froze when I tried to install it last night (11/14/11).
I have the unrevoked root with titanium backup to 'freeze' the bloatware. Is there a place I can manually install the new update?
Thanks in advance.
Schwim... didn't want to post a new thread when both our answers could be in a single response. :)
 
sbstn, After the update freeze, were you able to restart your phone and use it normally? Is the update nag gone?

"finding the rooted ota over at xda, and installing" seems well above my paygrade.
 
If a rooted user that has the update downloaded to /cache can post the new build version of the OTA (6 digit number at the end), and also if you post the contents of your build.prop (located at /system), then we can edit your current build.prop to the new build number. It will then think it already has the update and it won't nag you anymore. I just don't know the new number.

Like sdrawkcab said, you should be fine if you install a 2.3.4 rom but it looks like many users on 2.2 based roms are getting the nag.
 
Using Adao file manager, it looks like my /cache is empty(or I don't have the proper permissions to view the files maybe). Do I need a different file manager to be able to see the files there?
 
schwim said:
Using Adao file manager, it looks like my /cache is empty(or I don't have the proper permissions to view the files maybe). Do I need a different file manager to be able to see the files there?
Click to expand...

Yeah, you need Root Explorer or another file manager with superuser access, not sure what others, if any exist.
 
Schwim,

I pulled the battery out and my phone seems to work the same after the freeze. I have not received the notice again but I know it didn't install. It froze when it was trying to reboot for the initial install part. No repeat nag notice yet.

sdrawkcab25,
Thanks for the info! I will work on installing this manually. I'll be back if/when I have problems or break something. Haha.
 
Little more info for anyone wanting to help with the build.prop edit:

Back on Froyo, these were the instructions I posted:
-Open Root Explorer and make sure you're mounted as Read/Write
-Navigate to /system and long press on build.prop, then select the "Open in text editor" option
-Find the line that contains "FRF91/XXXXXX:user..." and replace that 6 digit number with 264707
-Then hit Menu > Save and exit
-Reboot

Now, we need to try a similar edit only this time the "FRF91" will be something different so you need to look for the /XXXXXX:user portion in the build.prop. I spotted one XDA user that claimed the new version is 210690. Ideally, it'd be nice if somebody could use Root Explorer to look in their /cache folder and verify that build number is correct. If so, the next move would be to edit the old build number to the new one, then reboot and see if this method still works. A backup beforehand would be a wise choice just to be on the safe side. These instructs are mainly geared toward people who are getting the nag while already on a custom rom which seems to be happening based on some posts this morning.
 
in cache, I find:

6f37e6f6b9ab.OTA_Incredible_C_Gingerbread_S_VERIZON_WWE-4.06.605.3-3.26.605.1_release_210690.zip

Is that what we're looking for?

Here's my build.prop:

# For Eclair project build property customization

# For FOTA bug report
# ro.error.receiver.system.apps=com.android.updater

# begin build properties
# autogenerated by buildinfo.sh
ro.com.google.clientidbase=android-verizon
ro.com.google.clientidbase=android-verizon
ro.build.id=FRF91
ro.build.display.id=FRF91
ro.build.version.incremental=264707
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=四 9月 30 22:01:49 CST 2010
ro.build.date.utc=1285855309
ro.build.type=user
ro.build.user=root
ro.build.host=HPA003
ro.build.tags=release-keys
ro.product.model=ADR6300
ro.product.brand=verizon_wwe
ro.product.name=inc
ro.product.device=inc
ro.product.board=inc
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=inc
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=3.26.605.1 CL264707 release-keys
ro.build.description=3.26.605.1 CL264707 release-keys
ro.build.changelist=264707
ro.product.ua=
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
ro.build.project=152016
ro.product.version=3.26.605.1
keyguard.no_require_sim=1
# end build properties
#
# system.prop for device
#

rild.libpath=/system/lib/libhtc_ril.so
ro.ril.def.preferred.network = 4
ro.telephony.default_network = 4
wifi.interface = eth0
wifi.supplicant_scan_interval=45
ro.com.android.dataroaming = true
ro.com.google.locationfeatures = 1
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 240
# ro.sf.lcd_density = 160
#0 - mdp composition, 1 - gpu composition
ro.sf.hw=1
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072

# For SD storage insert notification sound
persist.service.mount.playsnd = 0

# For the agps default value
ro.ril.def.agps.mode = 2

# For auto backlight default value
settings.display.autobacklight=1

# default value of brightness
settings.display.brightness=143

# For emmc phone storage
ro.phone_storage = 1

# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=24m

# For Verizon data retry
ro.cdma.data_retry_config = max_retries=infinite,0,0,60000,120000,480000,900000

# This file describes the media capabilities and profiles
# using system properties.
#
# Note: The property key and value has some length
# limit as defined by PROPERTY_KEY_MAX and
# PROPERTY_VALUE_MAX, respectively
#
# WARNING: We may not use system properties for specifying
# media capabilities and profiles in the future
#
ro.media.enc.file.format = 3gp,mp4
ro.media.enc.vid.codec = m4v,h263,h264
ro.media.enc.vid.h263.width = 176,1280
ro.media.enc.vid.h263.height = 144,720
ro.media.enc.vid.h263.bps = 64000,6000000
ro.media.enc.vid.h263.fps = 1,30
ro.media.enc.vid.m4v.width = 176,1280
ro.media.enc.vid.m4v.height = 144,720
ro.media.enc.vid.m4v.bps = 64000,8000000
ro.media.enc.vid.m4v.fps = 1,30
ro.media.enc.vid.h264.width = 176,800
ro.media.enc.vid.h264.height = 144,480
ro.media.enc.vid.h264.bps = 64000,6000000
ro.media.enc.vid.h264.fps = 1,30

#
# Increase SKIA decode memory capability for progressive jpg file
#
ro.media.dec.jpeg.memcap = 20000000

# Release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.version = Bluetooth 2.1 + EDR
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.50.032
#0x10000010010100101000011 represent bt profile list
ro.bt.profiles = 4270403

# Properties of BTLA stack
service.brcm.bt.activation = 0
service.brcm.bt.srv_active = 0
service.brcm.bt.hcid_active = 0
service.brcm.bt.btld = 0
service.brcm.bt.btld_pid = 0
service.brcm.bt.avrcp_pass_thru = 0
service.brcm.bt.avrcp_toggle = 1
#service.brcm.bt.btport_redir_on = 1

#Welly_Fang_01/05/2010
ro.cdma.home.operator.numeric = 310012
ro.cdma.home.operator.alpha = Verizon

# Disable HTC checkin service.
ro.config.htc.nocheckin=1

# Set Horizontal VVM = true and ro.HorizontalBUA = true for Incredible#C Verizon build
# Then Verizon VVM/BuA program can check this property to known if there is a Native VVM/BuA in ROM
ro.HorizontalVVM = true
ro.HorizontalBUA = true

#Recognize different PRL and PCB ID to load different acoustic ACDB for Incredible_C
ro.ril.enable.prl.recognition = 1

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_alert=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=OPTIONAL
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.com.google.clientidbase=android-verizon
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.2_r5
ro.com.google.clientidbase=ms-android-htc
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=1
htc.audio.hac.enable=1
ro.media.enc.hprof.file.format=mp4
ro.media.enc.hprof.codec.vid=m4v
ro.media.enc.hprof.codec.aud=amrnb
ro.media.enc.hprof.vid.width=720
ro.media.enc.hprof.vid.height=480
ro.media.enc.hprof.vid.fps=24
ro.media.enc.hprof.vid.bps=2000000
ro.media.enc.hprof.aud.bps=12200
ro.media.enc.hprof.aud.hz=8000
ro.media.enc.hprof.aud.ch=1
ro.media.enc.hprof.duration=60
ro.media.enc.lprof.file.format=3gp
ro.media.enc.lprof.codec.vid=m4v
ro.media.enc.lprof.codec.aud=amrnb
ro.media.enc.lprof.vid.width=176
ro.media.enc.lprof.vid.height=144
ro.media.enc.lprof.vid.fps=15
ro.media.enc.lprof.vid.bps=256000
ro.media.enc.lprof.aud.bps=12200
ro.media.enc.lprof.aud.hz=8000
ro.media.enc.lprof.aud.ch=1
ro.media.enc.lprof.duration=30
ro.media.enc.file.format=3gp,mp4
ro.media.enc.vid.codec=m4v,h263,h264
ro.media.enc.aud.codec=amrnb
ro.media.enc.vid.h263.width=176,1280
ro.media.enc.vid.h263.height=144,720
ro.media.enc.vid.h263.bps=64000,6000000
ro.media.enc.vid.h263.fps=1,30
ro.media.enc.vid.m4v.width=176,1280
ro.media.enc.vid.m4v.height=144,720
ro.media.enc.vid.m4v.bps=64000,8000000
ro.media.enc.vid.m4v.fps=1,30
ro.media.enc.vid.h264.width=176,800
ro.media.enc.vid.h264.height=144,480
ro.media.enc.vid.h264.bps=64000,6000000
ro.media.enc.vid.h264.fps=1,30
ro.media.enc.aud.amrnb.bps=5525,12200
ro.media.enc.aud.amrnb.hz=8000,8000
ro.media.enc.aud.amrnb.ch=1,1
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.media.cam.preview.fps=0
ro.media.dec.jpeg.memcap=20000000
ro.media.enc.jpeg.quality=95,85,70
ro.setupwizard.enterprise_mode=1
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

So it looks like the line you describe has changed somewhat and the string "264707" shows up in the file 5 times. Do all require changing?
 
We may need to get a build.prop from somebody who has the new, stock 2.3.4 now. At first I was thinking we could get by with editing just the 6 digit number but I don't think that'll work this time since we jumped OS versions. Anybody who got the update able to help us out?

This is the line that would get the edit:
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
 
Ok guys, I checked my own build.prop from the "Stock Plus" rom and I may be able to infer the rest. If anyone wants to try (backup first), edit to this:

ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.3.4/GRJ22/210690:user/release-keys

I think that might do the trick. If you still see the nag in the notification bar when you reboot, swipe down the bar and either try clearing it or press on it, then use the "back" button and see if that gets rid of it. I remember that happening on 2.2 but then it went away for good after that.
 
I am rooted 2.2. I received the update notice this morning and ignored it. I was going to change the build prop to remove the notice. However, when I looked back at my phone the update notice is gone. I check settings and it says my phone is up to date. It looks like they may have pulled this update at least on my phone.
 
Similar situation - Rooted 2.2 S-off. Wondering if I should take the OTA to 2.3.4. Can anyone explain the best way to upgrade and retain root/s-off?

Thanks!
 
euph_22 said:
What he said ^

Do not, do not, do not unroot to get the update. Install it as a rom, it will be faster, easier, and you get to keep root the whole time.
Click to expand...

Ok. But the ROM listed looks like it is a slightly different version (4.06 instead of 4.08). Should I wait for a few days to see if a new version gets posted? If I go through the process listed for the above rom, it sounds like I will lose all of my settings. Is that correct?

Thanks!

K
 
Since I've never installed a rom, are his instructions the only thing I need to know?

  1. Make a Nandroid Backup of your current rom
  2. Reboot into ClockworkMod
  3. Choose "wipe data/factory reset"
  4. Go into "mounts and storage" menu and choose "format /boot" and confirm
  5. Choose "format /system" and confirm
  6. Go back to main menu and choose "install zip from sdcard"
  7. Browse your sdcard for the rom zip and flash!
Click to expand...


I'll need to look up nandroid, but the rest seems fairly straight-forward.
 
Thank you Iowa! This worked for me. I only want to kill the Nag for now and this is working.
:)

iowabowtech said:
Ok guys, I checked my own build.prop from the "Stock Plus" rom and I may be able to infer the rest. If anyone wants to try (backup first), edit to this:

ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.3.4/GRJ22/210690:user/release-keys

I think that might do the trick. If you still see the nag in the notification bar when you reboot, swipe down the bar and either try clearing it or press on it, then use the "back" button and see if that gets rid of it. I remember that happening on 2.2 but then it went away for good after that.
Click to expand...
 
schwim said:
Since I've never installed a rom, are his instructions the only thing I need to know?




I'll need to look up nandroid, but the rest seems fairly straight-forward.
Click to expand...

can leave out steps four and five, a nandroid is made from within clockwork. so technically the first step is get the rom onto your sd card (somewhere you can remember/easy to find) then boot into clockwork.

Theoretically, you don't NEED to wipe data (but is the most error free way of installing the ROM), really only need to wipe cache, go to advanced, wipe dalvik cache; definitely recommend to wipe data though. You will also want to download titanium backup from the market first (paid version makes things 100 times easier). This will allow you to backup all of your apps for easy reinstall if you do have to wipe data.

PS: first boot up will take a while (10-20 minutes)

http://androidforums.com/incredible-all-things-root/233251-how-titanium-backup-tips.html
 
Philbo said:
Thank you Iowa! This worked for me. I only want to kill the Nag for now and this is working.
:)
Click to expand...

Cool. I heard from another user that it was working for him also. They seem to be updating certain phones with a patch and then they may move toward a mass OTA to be Gingerbread final? If so, we may have to update the prop again, we'll see how it goes. Glad to hear it's working though.
 
Question:

If I re-flash to the stock ROM linked above, will I still have the "disappearing apps" problem, where the SD card is mounted incorrectly?
 
You must log in or register to reply here.
Back
Top Bottom