yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] ron917:
For context: we are discussing the flashing horizontal black lines.

I had the lines under that condition with 4.1.1, but not with 4.1.2. I tried to recreate the condition by moving to the far end of my house, where my WiFi signal is very weak and perusing the forums with the xda app. I always saw the lines when I was in that spot with 4.1.1, but I did not see them with 4.1.2.

I have no explanation for this, just offering a data point.
[Nexus 7 General] krelvinaz:
My update is being blocked by BrowserProviderProxy.apk .... I have "Browser" installed, but am unsure how to un-install it now. I moved it from the /system/apps area but that doesn't actually "uninstall" it.

apk for browser is/was Browser.apk

It doesn't show in the app list to uninstall it normally.

FIXED!

Ahhh... I am remembering now... I had to rename the BrowserProxyProvider files to make the browser work... Just undid that and it is installing now.
[Nexus 7 General] Logic_:
It is connected to wifi somehow, however I have never seen them when streaming hd video, mostly in the browser, but other apps as well.

Not seen em since 4.1.2 either, but they only happened very sporadically before too.
[Nexus 7 General] Pezo:
I restored Videos.apk and Wallte.apk but now I'm getting an error on /dev/block/platform/sdhci-tegra.3/by-name/LNX, which is the boot partition from what I could gather.

So possibly a stupid question, but I'm not yet familiar with the inner workings of the Nexus 7: do I have to relock the bootloader to apply this update, or any other updates for that matter?

edit: I just realized that I installed a custom kernel, I suppose I need to restore the stock kernel for the update as well?
[Nexus 7 General] Pezo:
I figured it out by myself, maybe my load of questions was a little premature.

For anyone that's not so lucky, you need to restore everything to stock before applying the OTA.

That is: stock recovery, kernel, bootloader doesn't need to be locked, I didn't need to unroot as well.

I defrosted all system apps, don't know if that would have been necessary though.
[Nexus 7 General] everyday_:
Hi guys,

I'm from Malaysia and I just update my Nexus 7 JB 4.1.1 (JRO03S) to the latest JB 4.1.2 (JZO54K). I've unlocked bootloader & rooted before. After OTA, still unlocked bootloader & rooted. Confirmed.

I followed the instructions by hololodilolo to update via OTA

(settings>apps>all>google service framework>clear data/force close)
[Nexus 7 General] coraxe:
No landscape?

I'm at 4.1.2 JZ054K and the landscape mode isn't working on the home screen. Autorotate is set in accessibility but only the apps rotate...ideas?
[Nexus 7 General] AraDreamer:
Stock rooted unlocked. No mods or anything except adding stickmount, current build JRO03D, haven't gotten an update yet, not even after multiple cache clears. My boyfriend's nexus updated first time through the cache clear, his device is about a week old, mine's from august. I went home for the weekend with just the tablet, I do not have CWM or a third party recovery, and I do not have a laptop with me to apply ADB update. Should I wait it out, and is my build the proper stock mage to receive the update? I've been checking about once a half-hour for the update, no luck yet (push notifications seem fine, I haven't gotten them much, though). -Ara
[Nexus 7 General] jersonf:
Had a few random screen offs today, even though sleep is set at 1 minute, no dimming then off, just screen off well within 1 minute.

Could be just me.

Sent from my Nexus 7

Motorola Atrix (CM10 + those libs)

Nexus 7 (Stock + root)
[Nexus 7 General] Groid:
Do you have a custom launcher like Nova? If so, you may have to enable home screen rotation in settings. For Nova launcher settings > look and feel > screen orientation > auto rotate.
[Nexus 7 General] Q.Entity:
That is not correct. I have CWM and did not need remove it. In fact, CWM will prompt you that that OTA may restore the recovery and it can skip it. CWM also warns about possible loss of root. However. SuperSU will handle that if CWM does not (it does).

Skickat från min Galaxy Nexus
[Nexus 7 General] jpeckinp:
This is getting annoying. I have tried every way that I can think of to get the update to progress and it still gives me error 7.

I reset the system back to stock including my kernel and still it fails.

I've tried with and with out CWM recovery. I'm about ready to say screw it 4.1.1 runs just fine.:eek:
[Nexus 7 General] veeman:
Have you tried going into Google Services Framework and clearing data. Then force stop. Then go into About tablet and system updates?
[Nexus 7 General] cushcalc:
Has the stock browser been removed in 4.1.2? I can't find it; only find Chrome.
[Nexus 7 General] arcisbre:
This is exactly why I didn't root my N7. Coz I knew I was gonna be pulling my hair out dealing with a lot of **** ups along the way.
[Nexus 7 General] twocube7:
This is exactly what I got. Installed with no problems still rooted.
[Nexus 7 General] jpeckinp:
No problem downloading. It just won't install.
[Nexus 7 General] garuhhh:
Mine is being uninstalled as well. I tried restoring it through Titanium, but was removed again without notice. Will it help if we remove Chrome?
[Nexus 7 General] Omar04:
No it won't help. And Chrome is now the default browser for any Android os from now on.
[Nexus 7 General] penguinolog:
Just download full ROM, extract it and flash system using fastboot :). And root again after it.
[Nexus 7 General] garuhhh:
I installed it again using Titanium. I'll monitor again and see whether it gets uninstalled once more.

I like the fluidity of stock browser over Chrome. :(
[Nexus 7 General] Omar04:
I love Chrome but from time to time I like stock. They should leave it there. Bad Google bad Google! :D
[Nexus 7 General] fangthorn:
How do you replace build.prop?

I have read this entire thread and see many mentions of the need to replace build.prop with the original version if you have changed it. (otherwise the update fails which is happening in my case see attached)

I tried overwriting it with ES File Explorer but the live file is write protected.

So I tried booting into CWM recovery, mounting /System, and then used ADB Push.

This seemed to work, but then a reboot produced a blank screen.

I had to go back into recovery and restore my Nandroid to get back onto my machine.

I'm probably missing something basic here but I could do with some step-by-step guidance.

Thanks
[Nexus 7 General] Crafty77:
Can I ask for a bit of help here?

I still don't have the OTA so am attempting to manually upload.

Tablet is stock, not even rooted. USB debug is switched on.

I started following the AndroidPolice route but the bootloader bugs prevent me from getting in to recovery mode.

If I attempt to get into recovery without being plugged in to my laptop via USB I can get it and select recovery, but it just hangs with "Google" on screen.

If I plug in to the laptop via USB I can't use vol up/down to select recovery mode in the first place, all I can do is reboot.

If I boot the tablet and plug in to my laptop I can see it in windows explorer, but if I try "adb devices" it doesn't show any devices as being attached.

I've tried the bodge where you clear the framework data/cache, that doesn't work either.

Thanks
[Nexus 7 General] wyvorn:
Has anyone seen this?

When I do in Settings > About > System updates, I see that the update to 4.1.2 is available but it says it is waiting to download and nothing happens, it just stays like that.

Does anyone know why this is happening and is it normal?
[Nexus 7 General] Omar04:
Android 4.2 coming end of October early November... After LG Nexus launch...
[Nexus 7 General] oldblue910:
Official source with link?
[Nexus 7 General] Nospin:
There is none. It's all conjecture right now.
[Nexus 7 General] oldblue910:
That was exactly my point. ;)
[Nexus 7 General] scott_doyland:
Id use file manager app to mount /system as writeable and then alter file perms to be writeable on build.prop. overwrite file and set perms back to original.
[Nexus 7 General] 3thman:
help plz guys i did the update by OTA and after it finished my market was the newest version. then I did a factory reset and the market went to the older version. what happened? this is really weird. I want the latest version of the market but i want it to be updated automatically
[Nexus 7 General] fangthorn:
Thanks for your reply.

Others might find the following details more helpful.

To force build.prop to be overwritten do the following in ES File Manager:-

Menu/Settings/Other Settings/Root Settings

And then tick all:

Root Explorer

Up to Root

Mount File System

Backup System App

Once you have done the above, navigate to the folder where you have stored the downloaded build.prop file, copy, then navigate to /system and paste. If you have set the above correctly it should overwrite and you should then be able to apply the OTA update to 412 successfully. (It worked for me!)
[Nexus 7 General] oldman_getting_older:
Maybe of some help

I'll post this here... maybe it will help some Market problems.

I could no longer successfully update or download app's from the Play Market after I updated to 4.1.2., even though all looked correct. After much effort, I discovered a solution that was repeatable (at least for me). Even though all looked good with respect to my Market account, there appears to be a link that can get dropped without any obvious indications (other than problems).

Here's how I fixed it - I recommend you do it in this order. You will need to stop the Market from logging into your current account. To do this, you need to:

On your computer, set up another account to use for the market (you can skip the credit card stuff and this can be a temp acct).

On your computer, go to the broken account and change the Password (so the market and your device/emails/etc) can't log in.

Go to the Nexus7, Settings>Apps>All> |Google Play and Google Services Framework

Clear Cache and Data - Do NOT force quit (that causes the framework to reboot and pull in bad data from it's linked apps). Just back out after clearing cache/data).

Reboot your Nexus7. You may need to supply the new acct info during boot-up.

On the Nexus7, go to the Market - you should not be able to log in and will be prompted for an account. Select the new acct you set up. This can be a temp acct as you will be able to use the old one after things are fixed.

Because this is a new acct, you will loose tags to the apps you've downloaded - this will be for the new acct but, if you come back after the problem is fixed and you re-select the old acct, if desired, your apps will be there.

Hope that helps - it fixed my Nexus market issues...:victory:
[Nexus 7 General] wilfridofivanhoe:
build.prop it is/was

Thanks for that advice. I'd tried unsuccessfully flashing with CWM and stopping Google Services Framework to force an update. This downloaded the update and looked as though it was going to work, but then decided not to. I've changed my build.prop back to the original and then CWM worked fine.

The new landscape mode on the home screen looks a lot like the app Rotate. But.. a few minutes later, I've found a couple of apps that use landscape but only with the top of the N7 to the left ie anticlockwise 90degrees. I'll keep Rotate after all as I often like to use the cable on the left.
[Nexus 7 General] garuhhh:
Oh so sorry, didn't realize I posted in a Nexus 7 thread. I'm on galaxy nexus.
[Nexus 7 General] lfeuln:
Please let that be true. Still waiting on the update (grr) but the touch issues really do affect my otherwise love of the device.
[Nexus 7 General] Omar04:
I can't believe how's posible that yet too many user haven't received 4.1.2, because I purchased my Nexus 7 13/Oct/2012 at 5 am in Walmart then just power it up set wifi and 4.1.1 already there installed then reboot and there was 4.1.2 waiting to be installed. :confused:
[Nexus 7 General] bcatcool:
Hi guys,

I am in the UK and had mine come through on Friday 12th. No problems updating over rooted stock 4.1.1

Cheers

Bcat
[Nexus 7 General] legom:
I had problems updating from 4.1.1 due to using Titanium Backup's "integrate into rom" feature, but I ended up getting things working.
[Nexus 7 General] doraville:
Let me apologize in advance for this question. I know that the answer is here but I have spent a couple of hours searching and cannot find the answer.

My Nexus 7 is stock 4.1.1 that is rooted, has CWM installed, and has the build.prop file edited to provide the tablet UI. I understand that I need to restore my build.prop file to stock before I can install the 4.2.1 update. I thought that I had a backup of my original build.prop file but apparently I do not.

Is there a place that I can download a stock build.prop file, or if not what are the stock settings in the build.prop file that were changed?

Thanks!
[Nexus 7 General] frank35:
There's a download link at the bottom of this post:

http://xdaforums.com/showpost.php?p=29012253&postcount=2
[Nexus 7 General] doraville:
Thank you!
[Nexus 7 General] h4uw1n3:
**Edited

Get it done by replace the build.prop file...

I copy and paste the text didn't work... but i work when i replace the file.... :D now i have the 4.1.2 on my nexus...

Need help here...

My Nexus 7 rooted and installed cwm...

Update via OTA failed and i read this thread...

I did modified the file... just adding one line to force the launcher landscape mode.... and i restored it... but i can't update yet...

It's still displaying the error like before...

Ota and the 4.1.2 file i downloaded from here also...

Both doesn't work....
[Nexus 7 General] donaldjl:
4.1.1, stock ROM, unlocked, rooted, Voodoo rootkeeper, with ASOP browser (renamed browser.provider.proxy.apk and browser.provider.proxy.odex for it to work). Got the OTA, let it load, had droid on his back with the red exclamation. The update didn't install properly, still stuck on 4.1.1.

There were some disabled apps that I re-enabled. I also read in this thread that the ASOP browser and renamed browser provider files would result in a failed update. True? I've tried closing the ASOP browser and renaming the files through ES File Explorer, but the files keep the altered name.

How would I rename the files to original (I simply added a "1" after .apk and odex), or should the update to be forced without having to restore the original file name? Do I need to uninstall the ASOP browser before those files can be changed back?

I really don't want to start reflashing OEM ROMs, so any advice would be appreciated.

Thanks!
[Nexus 7 General] oldblue910:
EVERYTHING on your system partition must be exactly as it was stock, every filename, every byte, otherwise the OTA will fail every time. No exceptions. The end.

So, you have one of two choices:

1. The easy choice (assuming your bootloader is unlocked) is to download the 4.1.2 factory images from Google and only flash the system.img and boot.img files. This will be exactly like applying the OTA. You will not lose any data.

2. Restore your system partition to exactly 100% stock state which is more time consuming and may not even be possible depending on what modifications you've made.

Furthermore you cannot flash OTAs automatically (by tapping "reboot and install" when you get the OTA notification) with a custom recovery. Unless you're using stock recovery, you will have to pull the OTA file out of /cache, move it to your internal storage and flash it manually in your custom recovery.
[Nexus 7 General] mexigga:
Mine was rooted, bootloader unlocked, stock rom and accepted the ota update without issues.
[Nexus 7 General] donaldjl:
I thought I was running the "stock ROM", but apparently changing two file name extensions is enough to not allow the OTA? That's where I'm confused. (Sorry for the noob-ness with Android. I've worked with Windows and Linux and Motorola phones, what could be so hard about Android, right? LOL!) Those were the only changes I made to any files in the system. I was under the impression that uninstalling/deleting the ASOP browser .apk and changing the BrowserProviderProxy file extensions back would put the system back to its "OEM-ness".

Just so I can get a handle on things, the simplest method would be to pull the system and boot files from a copy of 4.1.2, plug the Nexus into the computer, and replace/overwrite those files on the Nexus, and restart the Nexus? I used the Wugfresh Rootkit to unlock and root the device but I'm not sure if that's something I should do simply via the computer (drag/drop) or through the Rootkit.

For number 2, that's where I thought getting rid of the non-stock browser and restoring the BrowserProviderProxy extensions would make things right. Ugh.

Thanks much for your patience, oldblue. I have no idea why I'm having trouble getting my head around this. I think my brain keeps trying to think "Windows" when it's obviously not, LOL! :silly:
[Nexus 7 General] phonic:
First, Android IS Linux. While it's a highly customized "distro" of it, the underlying foundation is still Linux.

Second, as the other poster said, you need to be 100% stock in order for the OTA to work. One of the first things the upgrade script does is validate the MD5 checksum of a crap ton of files on your device. If even a single one has changed, or has been removed/renamed/etc., the install script will abort. Even so much as an extra space at the bottom of the file will cause the script to abort. Assuming it does pass the verification steps, it then begins to *patch* those files. This is important, because instead of replacing them altogether, like many/most upgrade systems do, this one simply modifies the files to bring them up to date. This only works if they know -exactly- what the contents of the file are, since changes would break the patch, which is why they do the verification step first. And if the file was renamed/removed, there is nothing to patch so the install would fail.

If you know what you are doing, you can examine the updater-script and make some changes to get the zip installer to work with your system, but that isn't advisable unless you really know what you're doing. Outside of that, you can either revert back to stock or use the fastboot flash method.
[Nexus 7 General] oldblue910:
What you need to do is search for fastboot.exe on your machine and find that. If you used a toolkit then fastboot.exe has to be on your system somewhere. Once you've found the folder where it resides, download the 4.1.2/JZO54K images "nakasi" for Nexus 7 from http://developers.google.com/android/nexus/images. Extract the following files:

bootloader.img

system.img (located inside a tar file in the zip)

boot.img (located inside a tar file in the zip)

recovery.img (only required if you want stock recovery, otherwise you can use CWM or any other custom recovery you want)

Put those three .img files in the same folder with fastboot.exe and then do the following:

Reboot your Nexus 7 into bootloader mode by turning it off, then, while holding volume down, power it on. It'll boot into the bootloader screen.

Plug your Nexus 7 into your PC.

At a command prompt, change to whatever folder contains fastboot.exe and your .img files.

Type the following commands:

fastboot flash bootloader bootloader.img (this will bring you up to the new 3.41 bootloader that was included in the 4.1.2 OTA)

fastboot reboot-bootloader

fastboot erase system

fastboot flash system system.img

fastboot erase boot

fastboot flash boot boot.img

--- ONLY IF YOU WANT STOCK RECOVERY ---

fastboot erase recovery

fastboot flash recovery recovery.img

----------------------------------------------------------------------

fastboot erase cache

fastboot reboot

You'll be running 4.1.2 as if you'd applied the OTA and you're all done. Also, in the end, it's better to know how to do this stuff manually than to use a toolkit. That way when you get stuck like this, you'll be able to ninja your way out of it in a flash. ;)
[Nexus 7 General] donaldjl:
Phonic, yeah, it is a linux distro at heart, it just seemed pretty foreign with the different file extensions.

Oldblue, I'll try that tonight when I get home. I'm guessing I want the stock recovery. The OS was left alone except for installing the ASOP browser, and I can always re-install if I have to. I won't have to unlock and re-root afterwards, will I?

And yeah, I'm guilty of taking what seemed the easy route last time. I was anxious to dive in and root right off the bat before I got a handle on the Android system. This will help a lot. :highfive:

Thanks guys, you rock! :good:
[Nexus 7 General] dferrey:
I'm rooted and have CWM and did the above without a problem.

Thanks oldblue910 :)
[Nexus 7 General] oldblue910:
I'd recommend staying with stock recovery for however long you run the stock ROM, though many on this forum would probably take me to task on that. As you'll see below, if you ever DO need a custom recovery for anything, you can just boot one up, do what you need to do, and when you're done you'll still have stock recovery. The one thing stock recovery allows you to do that no custom recovery does is auto-flashing OTAs, which is useful if you run the stock ROM. Now, if you ever decide to run a custom ROM, you'll have to use a custom recovery as you can't flash anything other than a signed, sanctioned OTA from Google with stock recovery. So yes, for now, I would recommend including the steps for stock recovery in my previous post.

As for your other question, yes, you will lose root afterward, as well as any changes you made to the system partition (you won't have the AOSP browser anymore, etc.) That said, restoring root is easy. Once you've completed the steps for going to 4.1.2, follow these steps:

1. Download the Android SU binary and APK from the source.

2. Copy the ZIP you download to your N7's internal storage.

3. Download ClockworkMod recovery for the Nexus 7 and put it in the same folder with fastboot.exe.

4. Reboot into your bootloader (hold volume down while powering on).

5. From a command prompt, go to the folder that contains fastboot.exe and your CWM recovery image that you just downloaded.

6. Type the following commands:

fastboot boot recovery recovery-clockwork-6.0.1.0-grouper.img

7. Once ClockworkMod recovery loads, you'll see a menu of choices. Navigate using your volume up/down keys and select with the power button. Choose to install a zip file from your internal storage. You'll be presented with the directory structure of your N7's internal storage. Find the Superuser ZIP file you downloaded, select it, and flash it.

8. Once it's done flashing, choose to reboot your system (in the recovery menu).

Once Android boots up, you'll have root.
[Nexus 7 General] donaldjl:
All ready to go, with all the files stuffed into a separate directory directly off my C:\ so it's easy to get to. While extracting, I found that the bootloader found in the compressed file is named bootloader-grouper-3.4.1.img. I'd like to double check that the command should be:

fastboot flash bootloader bootloader-grouper-3.41.img

fastboot reboot-bootloader

fastboot erase system

fastboot flash system system.img

fastboot erase boot

fastboot flash boot boot.img

You know how running a command line in Windows doesn't like spaces or dots. This is still okay, or rename the bootloader img file so there's no conflicts with naming parameters? I'm guessing the commands are as written above, but I'm new to the manual method and would rather not hose something and have to patch it back together.
[Nexus 7 General] oldblue910:
I forgot they named the bootloader with that long name. Yeah, you have the command right. Also, make sure you flash stock recovery. So after system, throw in:

fastboot erase recovery

fastboot flash recovery recovery.img
[Nexus 7 General] donaldjl:
Update worked like a charm. Your directions were spot on and much clearer than others I've seen online. Hell, I wouldn't have used the toolkit the first time if it were so clear before.

I'm stuck on rooting. With the clockwork .img file in the same directory as fastboot, I enter:

fastboot boot recovery recovery-clockwork-6.0.1.0-grouper.img

And get:

cannot load 'recovery'

Weird. Don't know why recovery has single quote marks. I'll have to look at it again tomorrow when I have more time.