Hmmm, very interesting! But nothing here yet (16:08 PST). I hope I won't be left in the dust because I've rooted mine... I guess we'll see.
Is this update automatically installed and activated, or is there something I need to do ??
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=43
ro.build.display.id=ThinkTablet_A310_03_21_43_US
ro.build.version.incremental=eng.build.20110713.185826
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Wed Jul 13 19:05:40 CST 2011
ro.build.date.utc=1310555140
ro.build.type=eng
ro.build.user=build
ro.build.host=build-desktop
ro.build.tags=test-keys
ro.product.model=ThinkPad Tablet
ro.product.brand=Lenovo
ro.product.name=Indigo
ro.product.device=1838-2AU
ro.product.board=ventana
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Lenovo
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRO03D
ro.build.display.id=JRO03D
ro.build.version.incremental=402395
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Jul 13 01:03:41 UTC 2012
ro.build.date.utc=1342141421
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpba30.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus 7
ro.product.brand=google
ro.product.name=nakasi
ro.product.device=grouper
ro.product.board=grouper
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra3Is this update automatically installed and activated, or is there something I need to do ??According to the eetimes article, you will be prompted to OK the upgrade.
This is all fine and good, but when can we expect to get the notification ??????If you're non-rooted, probably in the next 24-72 hours.
Thanks, been checking all last night and this morning and still nothing :(This is all fine and good, but when can we expect to get the notification ??????If you're non-rooted, probably in the next 24-72 hours.
Thanks birdastrompgman.@birdastrompgman - can't seem to be able to boot into recovery mode since update.
Nice to know this was possible :)
Also, the emoticons in the TAPATALK app for this forum work now as well.
Not sure that is JB 4.1.2, but who knows 8)
Looks like I had to re-install TWRP again.Thanks birdastrompgman.@birdastrompgman - can't seem to be able to boot into recovery mode since update.
Nice to know this was possible :)
Also, the emoticons in the TAPATALK app for this forum work now as well.
Not sure that is JB 4.1.2, but who knows 8)
I believe we need to renamed the \system\recovery-from-boot.p file.
Any ideas how to do that?
I still haven't gotten my update. How long will it take?
Very true, Tiny.You need to click on the menu icon and select INSTALL OpenRecoveryScript. It will then download TWRP and install it.
No, S. Prime. I couldn't find TWRP in the Goo Manager download lists. I ended up flashing CWM 6.0.1.0, and its boot to recovery option works for me. I'm copying my Nandroid 4.1.2 backup now to my USB flash drive and my laptop's hard drive.
This thread somehow reminds me of a bunch of kids at Christmas. Can't wait to rip open the packages and see whats inside.
I 'm stuck. Standard bootloader recovery fails because of the bug. quick boot fails despite my reloading it twice. I even downloaded TWRP, and it doesn't go into recovery mode, either.birdastrompgman I am in the say boat as you, can't get to stock recovery or custom recovery. I have tried Goo Manager, TWRP, ROM Manager, you name it. I guess we'll have to wait for a guru to figure this out. I have 4.1.2 installed and rooted, everything works fine, just no way to get to recovery for me.
Caveat emptor. You may not be able to recover backups until a fix for this bug comes out.
I am re-posting my original suggestion and advise any rooted user without advanced skills to wait until the issues are sorted out. This applies to the OTA as well as the download. If you choose to install the update, post your results and eventually we will achieve a solution. Remember the update has not achieved full distribution at this point.Advice that I will surely take.
Suggestion
At this point we have a very disjointed discussion of the advanced update for the rooted user, so brave ahead if you choose to do so, or exercise a bit of patience and wait for the update guide that we will post after the OTA drops and it can be evaluated or a flash install is developed at XDA, that is a less involved process.
S.Prime
No issuesCan you give us some more details? Are you rooted? Have you made any changes to your build.prop? What recovery are you using?
Seems to be much more responsive to me. Did anyone else notice that?
So, I got the OTA last night, and I'm noticing that two finger notification expand (which I've already gotten used to, and seems faster to me) seems to not be working very well anymore. Anyone else have that problem?
Here's hoping that it fixes the screen response issues...that was really the only bad issue I've had with mine so far.
Has anyone in the US received 4.1.2 OTA for the Nexus 7?
Has anyone in the US received 4.1.2 OTA for the Nexus 7?
Just received notification.
Those of you who are unrooted should have no problems.I am trying to download this but there seems to be an issue when trying to open or find the file after the download.
Rooted owners who have modified any of their system files such as build.prop, will probably get error messages, and will probably have to restore the OEM files to get successfully upgraded.
Those of you rooters who modified your build.prop file to enable auto-rotation, but didn't save a backup, can try replacing your file with this copy I made. Rename it build.prop, and place it in your /system directory. CBers and I and one of our moderators all had our initial upgrade installations fail because of our modified build.prop files.
You probably lost root. If you did a temp-unroot or have a valid root backup, you can restore that with OTA RK.I think you were right. I just went back in and edited the file and it let me.I then temp unrooted with OTA RK and forced the update. She is rebooting now. I will keep posted on results.
Hey , I just bought a nexus 7 today and am loving it so far, but for what ever reason it will not up date to 4.1.2, keeps saying its already up to date any thoughts, also I'm purely stock ATM
After fixing my Nexus 7 with a factory image flash I got the update notification and have just updated to 4.1.2...wahoo...
Jackson, There is a full firmware of 4.1.2 that you can flash If you want that build. It makes no sense to flash the JR003D firmware just to hassle with an update. Go straight to JZ054K.
Here are the instructions to go straight to JZ054K with a full ROM
[url]http://forum.xda-developers.com/showthread.php?t=1930018[/url] ([url]http://forum.xda-developers.com/showthread.php?t=1930018[/url])
I wish it fixed the bootloader. Three of us (all rooted) were unable to get into recovery after upgrading to 4.1.2. CBers, Jpcalhoun, and I all couldn't get into recovery with 4.1.2.
Are you able to enter recovery through the bootloader while plugged into USB?I couldn't.
Your build includes the binary update. This added updates drivers for the touch sensitivity, Wi-Fi radio, Bluetooth, GPS, orientation sensor, graphics GPU, CPU, and DRM. This binary update solved many bugs, however, build JRo03S is still android version 4.1.1. Build JZo05k is android version 4.1.2. The change in the version number signifies a change in the UI (user interface). This is apparent in the new feature of landscape rotation at the homescreen and app drawer. The new version update also includes all the bug fixes, including the bootloader.
I know that the update did in fact include a change to the notification expand. I believe that it was altered to use one finger instead of two somehow.