FORUMS

Analysis & Opinion

Top Forum Discussions

Android 4.2.2 OTA Update

401 posts
Thanks Meter: 159
 
By nightfox11, Senior Member on 12th February 2013, 05:02 AM
Post Reply Subscribe to Thread Email Thread
13th February 2013, 07:43 PM |#121  
Member
Thanks Meter: 9
 
More
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://forum.xda-developers.com/show...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.
 
 
13th February 2013, 08:38 PM |#122  
blackhand1001's Avatar
Senior Member
Thanks Meter: 689
 
Donate to Me
More
Quote:
Originally Posted by espionage724

Here's exactly how I updated:

- Used 4.2 Factory Image
- Rebooted immediately back to Bootloader after the flash-all.bat was complete (didn't let OS boot)
- Locked Bootloader
- Went to Recovery
- Sideloaded the 4.2 to 4.2.1 update
- Sideloaded the 4.2.1 to 4.2.2 update immediately afterwards
- Wiped Data and Cache
- Rebooted

So far everything seems well.

For some weird reason when I first restocked my device, I wasn't able to access Recovery after OTA updating from 4.2 to 4.2.1 (got "No command."). No idea what was up with that.

No need to lock the bootloader.
13th February 2013, 08:46 PM |#123  
espionage724's Avatar
Senior Member
Thanks Meter: 523
 
Donate to Me
More
Quote:
Originally Posted by blackhand1001

No need to lock the bootloader.

Yeah I know, but when I restock, I go complete, including locking the bootloader lol
13th February 2013, 09:43 PM |#124  
Junior Member
Thanks Meter: 0
 
More
I've been trying to sideload the OTA. The device shows up while it's on the OS, can do an "adb devices" and it shows up and a, 'adb reboot recovery' and it reboots, but once I get into recovery, it no longer shows up. What am I missing...?
13th February 2013, 09:47 PM |#125  
Member
Flag Centurion
Thanks Meter: 8
 
More
Re: Android 4.2.2 OTA Update
Got the 4.2.2 OTA a few minutes ago in South Africa. Installed and I didn't loose root. Happy Chappy.


Sent from my Nexus 10 using xda app-developers app
13th February 2013, 10:31 PM |#126  
PantechBurstOwner's Avatar
Senior Member
Flag Detroit, MI
Thanks Meter: 30
 
More
5:31 EST, still no update. da hell man....
13th February 2013, 10:51 PM |#127  
Junior Member
Thanks Meter: 0
 
More
Re: Android 4.2.2 OTA Update
OTA in spain.

Enviado desde mi Nexus 10 usando Tapatalk 2
13th February 2013, 11:07 PM |#128  
Junior Member
Thanks Meter: 0
 
More
Re: Android 4.2.2 OTA Update
Sort of a newb question but does the update not show up if ur unlocked and rooted? I wouldn't think that would matter, but it wasn't showing up yesterday so I downloaded and flashed with CWM late last night. I kept root which was nice. I used the superSu root survival mode, but CWM also asked me if I wanted it to stop the update from removing root, so I'm not sure if which one gets the credit, but its nice not having to reroot

Sent from my Nexus 10 using XDA Premium HD app
13th February 2013, 11:12 PM |#129  
NeoMagus's Avatar
Senior Member
Flag East Coast
Thanks Meter: 472
 
Donate to Me
More
Forced it here on mine by clearing the services framework. No issues with Rootkeeper restoring root, good to go
13th February 2013, 11:42 PM |#130  
DowntownRDB's Avatar
Senior Member
Thanks Meter: 185
 
More
Quote:
Originally Posted by NeoMagus

Forced it here on mine by clearing the services framework. No issues with Rootkeeper restoring root, good to go

+1, clearing framework worked here also.
14th February 2013, 12:08 AM |#131  
tgrgrd00's Avatar
Senior Member
Flag New Orleans
Thanks Meter: 89
 
More
Re: Android 4.2.2 OTA Update
Quote:
Originally Posted by timesgodjillion

I've been trying to sideload the OTA. The device shows up while it's on the OS, can do an "adb devices" and it shows up and a, 'adb reboot recovery' and it reboots, but once I get into recovery, it no longer shows up. What am I missing...?

Did you verify all of the correct drivers are installed? I used the N10 Toolkit to install the drivers.

I seem to remember that when I booted in to recovery it installed a 2nd driver for recovery specifically. So when I got in to recovery and plugged in the usb it had a popup about installing driver.

Anyway try getting all of the drivers from the N10 toolkit and see if that helps. It was the toolkit by Mskip.

Sent from my EVO using Tapatalk 2

Read More
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes