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

[Verizon] should I accept JB update

Okay CWM Recovery installed fine and I was able to backup from ROM Manager via the menu.

Please verify next two steps which I believe should hopefully be the last two steps.

1) install Rootkeeper in case JB update is still forced on my and it succeeds which causes me to lose my root

2) install ES File Explorer to trick the update servers by modifying ro.build.fingerprint
 
Using Root Explorer:

  • Goto /system

Not seeing this directory even when I press the UP button. All I see at top of screen is /sdcard/ and the list of subdirectories (Alarms, Android, bugreports, clockworkmod, DCIM, etc) at the bottom of the screen.
 
Not seeing this directory even when I press the UP button. All I see at top of screen is /sdcard/ and the list of subdirectories (Alarms, Android, bugreports, clockworkmod, DCIM, etc) at the bottom of the screen.

Like I said, if you use ES explorer instead of root explorer, there'll be differences. I think you have to choose some options pertaining to root and maybe showing /system in that app's settings. Idk exactly what options you need to invoke because I don't use it.
 
Using Root Explorer:

  • Goto /system
  • Mount as r/w
  • Long press on build.prop, then choose open in text editor
  • Find the line that includes "ro.build.fingerprint" and change it to read:
ro.build.fingerprint=google/mysid/toro:4.1.1/JRO03O/424424:user/release-keys

(note that the JRO03O is letter "O", zero, 3, letter "O")

  • Once the line is edited, press settings and then save and exit.
  • Reboot phone and done
This will essentially trick the update servers into thinking you already have the update so the nag will disappear.

It worked! Will this mod have any adverse effect in the future?
 
JB is great, fast smooth, responsive. My gripes are (big ones in bold):

1. battery life is a bit worse on average, will have to wait and see how it equalizes out...
2. google now is kinda silly, its cool, but still needs a year or two of development, and better hardware to run off of.
3. Samba filesharing isn't compatible with JB (doh!) - good thing I got Wifi File explorer pro older version for free, plus my usb drivers work too. So no biggie, only need it every now and then.
4. charging while on USB seems slower
5. voice dialing wont recognize some of my key contacts now, at least one with a non-standard name.
6. I dont like the new lockscreen animation
7. I liked the smooth auto-brightness from 4.0.4 better (Lux app is somewhat a solution)
8. swype has been wigging out a big, like jumping to the beginning of a post when I try to delete a word by holding backspace.

however, I love that the web browser and system UI are generally so much more responsive and fast. The radios seem a bit better and faster at grabbing a signal.

accept the update and test it out for a month. then you can go back to stock 4.0.4 or flash a custom rom.
 
JB is great, fast smooth, responsive. My gripes are (big ones in bold):

1. battery life is a bit worse on average, will have to wait and see how it equalizes out...
2. google now is kinda silly, its cool, but still needs a year or two of development, and better hardware to run off of.
3. Samba filesharing isn't compatible with JB (doh!) - good thing I got Wifi File explorer pro older version for free, plus my usb drivers work too. So no biggie, only need it every now and then.
4. charging while on USB seems slower
5. voice dialing wont recognize some of my key contacts now, at least one with a non-standard name.
6. I dont like the new lockscreen animation
7. I liked the smooth auto-brightness from 4.0.4 better (Lux app is somewhat a solution)
8. swype has been wigging out a big, like jumping to the beginning of a post when I try to delete a word by holding backspace.

however, I love that the web browser and system UI are generally so much more responsive and fast. The radios seem a bit better and faster at grabbing a signal.

accept the update and test it out for a month. then you can go back to stock 4.0.4 or flash a custom rom.

Thanks for the recommendation. I'll wait until I see a pressing need for it. Can't risk killing my phone if the OTA update fails and results in non-responsiveness.
 
It worked! Will this mod have any adverse effect in the future?

No. When/if the next update comes along, you will be asked to update to it. You can then use the same method to avoid the update nag if desired. Only the next time, you would use the info (numbers/letters of the update ID) for that particular update which we won't know until it's released and reported by users.
 
Back
Top Bottom