Android 4.2.2 OTA Update

stealthj · Feb 13, 2013

jarjar124 said:
Unmount system.

Sent from my Nexus 7 using xda premium

still won't work, system auto-mounts if you try to update, keep disabling, and it keeps auto mounting.

Fromako · Feb 13, 2013

stealthj said:
still won't work, system auto-mounts if you try to update, keep disabling, and it keeps auto mounting.

Are you still on the corrupted factory image that Google had to replace? Did you use one of the modified patches found here on XDA to get 4.2.1 installed?

Koopa777 · Feb 13, 2013

irishrally said:
The red triangle is just stock recovery.

I didn't think you needed to rename recovery-from-boot.p anymore so you may not be flashing recovery correctly. Anyway, here are the twrp instructions for the N7 since the recovery-from-boot.p part is not in the N10 instructions, just in case you need it.

Yeah I'm a moron. I forgot that was the stock recovery, then I realized I was trying to flash TWRP 2.4.1.3 for the Toshiba Thrive and wondered why it didn't work. I used 2.4.1.0 for the Manta and it took instantly. I appreciate all the help you guys! :good:

stealthj · Feb 13, 2013

Fromako said:
Are you still on the corrupted factory image that Google had to replace? Did you use one of the modified patches found here on XDA to get 4.2.1 installed?

I'm not sure. I have 40d from last week thru Google. When did they replace them? I don't believe I'm on those

Fromako · Feb 13, 2013

stealthj said:
I'm not sure. I have 40d from last week thru Google. When did they replace them? I don't believe I'm on those

You would only have the corrupted version if you used the factory restore image posted on Google's website before Dec 1st. It doesn't sound like it would be the case for you.

stealthj · Feb 13, 2013

Fromako said:
You would only have the corrupted version if you used the factory restore image posted on Google's website before Dec 1st. It doesn't sound like it would be the case for you.

Ooh OK I see. Yeah I don't have that. Just stock with cwm and super su. I don't have much on the device so I'll just flash factory images and let it ota I guess... Or I'll just wait till I get home and just push the ota images inside the zip with adb... Hmm.. Wondering what the deal is here... Hopefully nexus 4 doesn't have the same issues...

jackie_jagger · Feb 13, 2013

uncleswoop said:
Do I have to create the "backup" folder under TWRP? Or can I just put the files under the TWRP folder? Because there are 2 small files under the TWRP folder, but no subfolder.

This is where I placed the Boot folder

Code:

sdcard/TWRP/Backups/R32XXXXXX/Boot 2013_01_05

R32XXXXX corresponds to the folder that TWRP created, you could try place the extract folder under backups but I'm not sure if it would work or not - what I have mentioned above worked without any issues.

Hope that helps

filthygoat223996 · Feb 13, 2013

Any word when nexus 10s in Canada will get the update?

Sent from my Amaze 4G using xda app-developers app

mistermidas · Feb 13, 2013

Sssoo, I've read through the entire thread looking for a change log, and didn't see anybody post one. But from what I can tell, it didn't update anything significant, and even more, people are STILL getting random idle reboots. Conclusion: I'll just stay on AOKP 4.2.1....

Sent from my LG-LS970 using xda premium

ninfragile14 · Feb 13, 2013

I am on cm 10.1 with clockwork recovery right now. I would really like to try out the update. I have tried several times to flash the stock image with fastboot so I can go through the upgrades. However, everytime, it stops at sending.... bootloader and just sits there. the drivers are installed and fastboot sees my device but wont flash anything. any tips??

Fromako · Feb 13, 2013

mistermidas said:
Sssoo, I've read through the entire thread looking for a change log, and didn't see anybody post one. But from what I can tell, it didn't update anything significant, and even more, people are STILL getting random idle reboots. Conclusion: I'll just stay on AOKP 4.2.1....

The summary so far is fixes for bluetooth streaming, long-press quick toggles and general bug fixes. I'm giving 4.2.2 a chance but if I start getting reboots I'll go back to AOKP as well.

ninfragile14 · Feb 13, 2013

mistermidas said:
Sssoo, I've read through the entire thread looking for a change log, and didn't see anybody post one. But from what I can tell, it didn't update anything significant, and even more, people are STILL getting random idle reboots. Conclusion: I'll just stay on AOKP 4.2.1....

Sent from my LG-LS970 using xda premium

For me the bluetooth fixes would be a big deal. I can't use a mouse and keyboard while on wifi and movies studder while listening via bluetooth. I really need bluetooth to work properly.

pfmiller · Feb 13, 2013

mistermidas said:
Sssoo, I've read through the entire thread looking for a change log, and didn't see anybody post one. But from what I can tell, it didn't update anything significant, and even more, people are STILL getting random idle reboots. Conclusion: I'll just stay on AOKP 4.2.1....

Did you try this thread?

Some changes relating to the soft restarts are mentioned in the change log, so it should be better now. I've only seen one person reporting a reboot post 4.2.2, so it seems a little soon to say it's not any better.

sl4y3r88 · Feb 13, 2013

What is the basis that Google uses to push updates? Why don't all Takju users get it at the same time? Is it IP based? Are there any priorities or something like that? Just curious.

mistermidas · Feb 13, 2013

pfmiller said:
Did you try this thread?

Some changes relating to the soft restarts are mentioned in the change log, so it should be better now. I've only seen one person reporting a reboot post 4.2.2, so it seems a little soon to say it's not any better.

Nope, I'll take a look at that, thanks. Either way though, I like the setup i have now a lot. So unless i see something major updated, more than a Wi-Fi/Bluetooth toggle and some animations, I'll just wait until the developers, namely for AOKP roll out the 4.2.2. ROMs.

Sent from my LG-LS970 using xda premium

espionage724 · Feb 13, 2013

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.

xXFallenXx · Feb 13, 2013

filthygoat223996 said:
Any word when nexus 10s in Canada will get the update?

Sent from my Amaze 4G using xda app-developers app

I got mine around 10pm. I had to clear the google services framework data.
I flashed the factory image, got the 4.2.1 ota, and then waited a while but the 4.2.2 didn't come on its own(*unlike 4.2.1)
Clearing the google services framework data and then checking for updates worked immediately.

mieszk3 · Feb 13, 2013

I merged updates of google apps with ROM using Titanium Backup and now OTA update doesn't go because of hash code checking. Does anyone have original apks from 4.2.1 version? Or maybe some hint how to get them?
I need: CalendarGoogle.apk, Chrome.apk, Currents.apk, Gmail2.apk, GmsCore.apk, GoogleEarth.apk, Maps.apk, Music2.apk, Phonesky.apk, PlusOne.apk, Street.apk, talkback.apk, Velvet.apk and YouTube.apk. And the proper odex files if exist.

Thanks in advance.

----- Edited -----
Ok, i extracted origonal apk from stock system.img. Now I will try to downgrade apks to stock one.
I failed on odex.p files and patches.

pfmiller · Feb 13, 2013

sl4y3r88 said:
What is the basis that Google uses to push updates? Why don't all Takju users get it at the same time? Is it IP based? Are there any priorities or something like that? Just curious.

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.

teodor_ch · Feb 13, 2013

Everyone with 4.2.2 please install
https://play.google.com/store/apps/details?id=se.mumu21.bootlog&hl=en
to find out if you get crash/restarts

Mine happened while I was watching TV so I could miss it and now think that they totally fixed it.

The good news is that it is much LESS frequent for me now.

EDIT:
I think here is the half fix for now related to Location services

https://android.googlesource.com/platform/frameworks/base/+/6c5406a

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

Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Member

Similar threads

Top Liked Posts