Android 4.2.2 OTA Update

bhatbhai · Feb 13, 2013

So I'm getting problems likely related to flashing the AOSP browser sometime after the 4.2.1 update. Status 7 error (BrowserProviderProxy.apk/odex). Before flashing, I had renamed the two files to add a ".bak" at the end.

I attempted to delete the Browser.apk file and rename the two BrowserProviderProxy files to the originals before flashing the update via TWRP, but I'm still getting the same error. Ideas?

sl4y3r88 · Feb 13, 2013

pfmiller said:
I don't think anyone outside of Mountain View knows the answer to that. I would guess since the deleting the Services Framework trick really does seem to work, it may be based on some random device ID assigned to each device when the device first logs in with a Google account but that's just my theory.

Thanks for your reply. I cleared the Framework data and cache of that service but have still not got 4.2.2. I'm from India so probally will hit in a day or 2.

styckx · Feb 13, 2013

Not bad after almost a day live on it. I actually decided when someone posted a link to the update to go ahead and throw it on.. I just ended up flashing the stock 4.2 image and rolling up to 4.2.2. I wanted a fresh bed of rice to lay my user experience on. My intention when I bought this was to run pure stock as I didn't really feel like tweaking out a $500 device and to just use it as Google intended. Unfortunately 4.2.1 was such a pile of poo I only stayed on stock for a minute to copy Rasbean and Trinity to it. I hope they give the Nexus 10 a factory image of 4.2.2 since we never got one for 4.2.1

irishrally · Feb 13, 2013

^^ haha I knew you would cave ....

styckx · Feb 13, 2013

This is new.. Now to find out where to deauthorize authorized computers because it doesn't look like Google got that far yet.. Would be nice as the owner of the tablet to block debug access from certain computers. Or better yet password protect it.. What's the point of RSA keys if a single key press authorizes it without a middle man security measure? I hate one way features.

Hereisphilly · Feb 13, 2013

styckx said:
This is new.. Now to find out where to deauthorize authorized computers because it doesn't look like Google got that far yet.. Would be nice as the owner of the tablet to block debug access from certain computers. Or better yet password protect it.. What's the point of RSA keys if a single key press authorizes it without a middle man security measure? I hate one way features.

I think the main application is when used with a secure lockscreen (face unlock, gesture, pin) so if a thief has your phone, he cant use adb to dump all your personal data, thus bypassing the lockscreen.
Great for use with a totally stock phone, but not the best when custom recoveries are used, as that prompt can be bypassed

More info here http://www.androidpolice.com/2013/02/12/new-android-4-2-2-feature-usb-debug-whitelist-prevents-adb-savvy-thieves-from-stealing-your-data-in-some-situations/

styckx · Feb 13, 2013

Hereisphilly said:
I think the main application is when used with a secure lockscreen (face unlock, gesture, pin) so if a thief has your phone, he cant use adb to dump all your personal data, thus bypassing the lockscreen.
Great for use with a totally stock phone, but not the best when custom recoveries are used, as that prompt can be bypassed

More info here http://www.androidpolice.com/2013/02/12/new-android-4-2-2-feature-usb-debug-whitelist-prevents-adb-savvy-thieves-from-stealing-your-data-in-some-situations/

Yeah... I see that end of it but.. I don't know.. It's a step in the right direction and glad to see Google getting more into security but relying on the lock screen as the end all be all security for critical access to internal information is strange in my opinion as I'd say more people use swipe to unlock than pins, etc.. Android needs a legit SU layer added for stuff like this..

I guess all in due time..

onemandivision · Feb 13, 2013

the battery usage on standby went down quite a bit since i have 4.2.2

(the first 20% of battery loss is from gaming with wifi and full brightness)

styckx · Feb 13, 2013

Google services is still the bane of my existence.. What an awful service.. On battery 22hrs and Google services has kept it awake for one hour of that.. ONE HOUR for 22.53KB sent and 44.00KB received..

Time to disable location services again.

chiccitstix · Feb 13, 2013

Updated just now. Went very smooth. I deleted Browser.apk from /system/app and changed the apk and odex back to their original names (basically I just took away .bak).

Restoring my system folder to that default was all I needed. I formatted dalvik/cache and then installed via CWM. Upon exit it asked me to fix the recovery and restore root, and I was done.

Anyone know if this fixes WiFi drops due to same-named AP's?

tvBilly · Feb 13, 2013

Problem with "debuggerd"

Just finished the update, and ran into a few problems, and had one question.

The question: Could you please take an MD5 of your file /system/bin/debuggerd for me. My debuggerd's MD5 is aacdcea17619cdae3263a1b9a6c8ee3c. Oh, and I only need this for a stock ROM N10, and could you indicate what version of the ROM this is from (JOP40C, JOP40D, or JDQ39).

My N10 was Unlocked, Rooted, TWRP 2.4.1.0, otherwise stock JOP40D. The update failed the first time due to my system/app/BrowserProviderProxy.apk mods causing the install script's patchcheck to fail. Fixed that on the N10. Ran the update again, and this time it failed on the script's patchcheck for /system/bin/debuggerd. Noticed there was a debuggerd.bak sitting there, though I have no idea what caused it to be there. So I renamed the active one, and renamed the .bak to become the active one. Didn't help; same updater failure. So I went back to my TWRP backups as far as last November, and extracted every backup of debuggerd that I had (and indeed saw when the .bak version started showing up, though I still don't know what caused it). Turns out the MD5 on every version of debuggerd I have is exactly the same.

So I commented out the patchcheck line for debuggerd in the JDQ39 installer script (but not the actual debuggerd apply_patch command in the script). And low and behold, the updater worked, and my N10 running JDQ39 is also working just fine now.

I have no idea why the JDQ39 updater doesn't like my debuggerd file, whether it's something weird about my debuggerd, or something weird about the script, or something weird about TWRP, but I'd love to know what the MD5 of your /system/bin/debuggerd file is to see if it's different from mine.

Thanks!

edit: And, hey, I didn't name it debuggerd.

espionage724 · Feb 13, 2013

tvBilly said:
Just finished the update, and ran into a few problems, and had one question.

The question: Could you please take an MD5 of your file /system/bin/debuggerd for me. My debuggerd's MD5 is aacdcea17619cdae3263a1b9a6c8ee3c.

a44f77131653be959d70997306a7e665

jonstrong · Feb 13, 2013

MD5 for the file on my VzW GNex - 1e1285480aae05834a4a18ffce551275

other properties:
Size 21.31 KB (21,824 bytes)
Modified: 2008-08-01 08:00:00 AM

tvBilly · Feb 13, 2013

espionage724 said:
a44f77131653be959d70997306a7e665

Is this on a Nexus 10, and is that for JOP40C JOP40D, or JDQ39?

I should have made that part of the original question (sorry, I'll edit it).

jonstrong said:
MD5 for the file on my VzW GNex - 1e1285480aae05834a4a18ffce551275

other properties:
Size 21.31 KB (21,824 bytes)
Modified: 2008-08-01 08:00:00 AM

How strange. On my VZW GN the file has the same date and time, but is 21.24K and the MD5 is different. But I'm not running a stock ROM on my VZW GN, I'm running "shiny", which could explain the difference.

jonstrong · Feb 13, 2013

tvBilly said:
Is this on a Nexus 10, and is that for JOP40C or JOP40D?

I should have made that part of the original question (sorry, I'll edit it).

How strange. On my VZW GN the file has the same date and time, but is 21.24K and the MD5 is different. But I'm not running a stock ROM on my VZW GN, I'm running "shiny", which could explain the difference.

Hmmm...I'm running JBSourcery (latest build). Just odd that the files vary like this.

talktoanil · Feb 13, 2013

No update for India yet ;(

jonstrong · Feb 13, 2013

talktoanil said:
No update for India yet ;(

I'm in in the US (east coast - New Jersey) -- didn't wait for OTA -- downloaded file, verified MD5, used Voodoo Rootkeeper to save root, flashed the OTA zip via TWRP in recovery, rebooted, used Voodoo Rootkeeper to restore root. All worked beautifully, and my N10 is now running 4.2.2.

tvBilly · Feb 13, 2013

jonstrong said:
Hmmm...I'm running JBSourcery (latest build). Just odd that the files vary like this.

If the ROM developer recompiled something, it could easily change the MD5 without altering the functionality of the code. I sort of wanted to take all the extra variables out of the question, hence just looking for stock ROM N10 MD5s for the /system/bin/debuggerd file, along with what version of the ROM it's from. Not sure how the OS uses the debugger daemon, but I'd like to make sure mine is OK without having to revert back to the factory images and re-update two versions and re-root, re-recovery, and re-install all apps.

Thanks for everyone's help!

devilcaeser2010 · Feb 13, 2013

talktoanil said:
No update for India yet ;(

dude i already got mine updated yesterday morning

bhatbhai · Feb 13, 2013

I finally got my update to work, after battling this Status 7 browserproviderproxy.apk error mess for a day. I guess somehow, my original browserproviderproxy.apk got altered after I backed it up, since it was about 18 kb instead of 24. If anyone else has this problem (or perhaps deleted their original files), go to this thread:

http://xdaforums.com/showthread.php?p=34869471

Download the browserproviderproxy.zip, extract into your \system\app folder, and you shouldn't get an error anymore.

Hope I helped at least somebody.

Android 4.2.2 OTA Update

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts