[Verizon] Verizon 4.2.2 leak now available.

[jhawkkw]

If the leak is out, the OTA can't be far behind. I had been hoping for a birthday gift from Verizon.

Maybe, this might turn out not to be the OTA like what happened to build IMM30B. Plus once the JRO3HO got leaked, it took Verizon over a month to push it to users.

 

[tzoller]

I updated to the 4.2.2 without problems but the Droid Life article also had info about new radios. I would like to install the new radios wich are ina zip file. How do you do that?

 

[jhawkkw]

I updated to the 4.2.2 without problems but the Droid Life article also had info about new radios. I would like to install the new radios wich are ina zip file. How do you do that?

If you installed the leak and not a custom rom, then the radios already installed. So you'd be good to go.

 

[nomarsgirl]

Any downside to installing the leak? Maybe I'll go for it.

 

[jhawkkw]

Any downside to installing the leak? Maybe I'll go for it.

Personally, I don't think the radios are as good signal wise, but I have seen better battery life with them. So I'm conflicted on whether to change them back. I'd say go for it because of this doesn't turn out to be the actual OTA, it's not difficult to get back to 4.1.1. Are you unlocked and rooted?

 

[dhworph]

Any downside to installing the leak? Maybe I'll go for it.

I haven't tried it, but haven't read about any big issues, other than what is already in many 4.2.2 custom roms... no big improvements either, it seems.

However, the update zip seems to have a recovery in it, so it will probably overwrite your custom recovery. SOmeone please correct me if I'm wrong.

 

[jhawkkw]

I haven't tried it, but haven't read about any big issues, other than what is already in many 4.2.2 custom roms... no big improvements either, it seems.

However, the update zip seems to have a recovery in it, so it will probably overwrite your custom recovery. SOmeone please correct me if I'm wrong.

When I looked in the zip file, there was no actual recovery image in it, but it did have the patch file that auto rewrites the stock recovery on each boot. So it essentially accomplishes the same thing.

 

[FramCire]

If the leak is out, the OTA can't be far behind. I had been hoping for a birthday gift from Verizon.

Happy Birthday!!!!!! Wish the oTa had hit on your birthday but maybe soon.

 

[nomarsgirl]

I haven't tried it, but haven't read about any big issues, other than what is already in many 4.2.2 custom roms... no big improvements either, it seems.

However, the update zip seems to have a recovery in it, so it will probably overwrite your custom recovery. SOmeone please correct me if I'm wrong.

I'm completely stock, unrooted. I'm just tired of waiting.

 

[nomarsgirl]

On, I've never done this before. I downloaded the android SDK and the leak file. I connected my phone to my PC but it doesn't recognize it. What am I doing wrong?

 

[jhawkkw]

You probably need to install and configure the samsung signed ADB/Fastboot drivers. You can do this manually, or use wugs nexus toolkit which gives you a step by step instruction to do so.

 

[dhworph]

Looks like you are on Windows XP... I suggest connecting your phone via usb and launching windows update to see if it shows an drivers... possibly under the optional and/or hardware section in windows update.

 

[umataro42]

Tried installing the zip using CWM v6.0.2.3 (touch), and got a status 7 error, from the "Verifying current system..." step.

assert failed: apply_patch_check ("/system/build.prop", 17aec846533d952fd21c0ab609c5b4aa31db39f", "54d207f79faf9be3db5b7da6f9c1e70e26528129d")
E: Error in ... 5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98-1.zip
(Status 7)
Installation aborted.

My phone is rooted, but stock.
4.1.1 / JRO03O
Kernel version: 3.0.31-g396c4df
android-build@pbs1)


I've tried flashing stock recovery, but whenever I use that I automatically get the Android laying down with the red triangle over his open panel, which is one of the reasons I use CWM to begin with.

Anyone know of a way around it? I've checked a couple other forums, and have seen I'm not the only one experiencing this, but nothing so far about a way to fix it. There was one way involving revising the updater-script but that just led me to a Status 6 error. I also sent an error log to CWM using ROM Manager, but haven't heard back so far.

 

[nomarsgirl]

Looks like you are on Windows XP... I suggest connecting your phone via usb and launching windows update to see if it shows an drivers... possibly under the optional and/or hardware section in windows update.

Thanks. I never did figure it out, but I got the OTA on Tuesday.

 

[az_r2d1]

Tried installing the zip using CWM v6.0.2.3 (touch), and got a status 7 error, from the "Verifying current system..." step.

assert failed: apply_patch_check ("/system/build.prop", 17aec846533d952fd21c0ab609c5b4aa31db39f", "54d207f79faf9be3db5b7da6f9c1e70e26528129d")
E: Error in ... 5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98-1.zip
(Status 7)
Installation aborted.

My phone is rooted, but stock.
4.1.1 / JRO03O
Kernel version: 3.0.31-g396c4df
android-build@pbs1)


I've tried flashing stock recovery, but whenever I use that I automatically get the Android laying down with the red triangle over his open panel, which is one of the reasons I use CWM to begin with.

Anyone know of a way around it? I've checked a couple other forums, and have seen I'm not the only one experiencing this, but nothing so far about a way to fix it. There was one way involving revising the updater-script but that just led me to a Status 6 error. I also sent an error log to CWM using ROM Manager, but haven't heard back so far.

I get the same thing when using cwm.
Did you figure it out ?

 

[politzer]

How do you figure out which of the two rooted options you are? I rooted (by mistake) to 4.1.1 Build JRO03O. Does that tell me?

 

[DonB]

Going to move this thread to the ATR, seems to me more suited for there. If anyone has an issue with this drop me a line

 

[umataro42]

I get the same thing when using cwm.
Did you figure it out ?

Wasn't able to figure it out, so instead I tried flashing my first ROM. I went with Shiny because its basically Stock with just a few minor tweaks.

I ended up getting a boot loop after flashing the ROM and new radios, but that might be related to whatever was causing the Status 7. After a factory reset (also done from CWM), it started up fine. So make sure you back everything up and copy the backup to somewhere off your phone, just to be safe. A little warning - I wasn't able to restore my SMS messages from TB.

 

[az_r2d1]

Wasn't able to figure it out, so instead I tried flashing my first ROM. I went with Shiny because its basically Stock with just a few minor tweaks.

I ended up getting a boot loop after flashing the ROM and new radios, but that might be related to whatever was causing the Status 7. After a factory reset (also done from CWM), it started up fine. So make sure you back everything up and copy the backup to somewhere off your phone, just to be safe. A little warning - I wasn't able to restore my SMS messages from TB.

I figured out how to fix it.
I first downloaded the full imm76k image. (Samsung Galaxy Nexus (toro) - RootzWiki)
Then I opened it with 7zip and pulled the system.img from it.
I used wugfresh toolkit to install the image and voila, the upgrade to 4.2.2 worked fine after that.

Not sure what or who messed with the system/bin directory but this resolved it.

 

[umataro42]

Good to know for future reference, and I'm glad it worked out for you. Other than losing video messages I was unable to restore, I'm happy to have finally tried flashing a ROM, so I'd say it worked out for me too.