Comments on: Factory Image JRO03O Released for Verizon’s Galaxy Nexus

By: Vinyl Skratch

Vinyl Skratch — Tue, 06 Nov 2012 00:56:00 +0000

Stupid question. Will I lose root?

By: bqluong

bqluong — Fri, 28 Sep 2012 15:10:00 +0000

I was having a really tough time flashing the 4.1.1 Jelly Bean to the Galaxy Nexus because Win7 64-bit kept disconnecting and adb didn’t show any devices. There is a file in the zip file called flash_all.bat. So Step 1: adb reboot bootloader. Step 2: flash_all.bat. Then sit back and relax and watch magic happen. It was so frustrating trying to enter each command and then getting and error of either device not found or error image partition invalid.

By: BiggShooter

BiggShooter — Thu, 27 Sep 2012 15:21:00 +0000

has anyone located a ZIP FILE for the JRO03O factory image??

By: Corey Vallejo

Corey Vallejo — Wed, 26 Sep 2012 22:02:00 +0000

Care to explain? I don’t have any issues charging and no immediately noticeable bugs.

By: Eric G Canoy

Eric G Canoy — Wed, 26 Sep 2012 21:30:00 +0000

it’s only authenticating on a corporate network using PEAP or TTLS, where for some reason JB won’t authenticate, but ICS was rock solid

By: 538z

538z — Wed, 26 Sep 2012 20:02:00 +0000

Jelly Bean has lots of bugs including a charging issue. I hope it gets fixed soon!

By: Leland Wilson

Leland Wilson — Wed, 26 Sep 2012 19:01:00 +0000

From you screenshot I don’t see you have a Wifi connection.

By: Jordan Webb

Jordan Webb — Wed, 26 Sep 2012 15:32:00 +0000

People have noted that there’s minor differences in smoothness, but that may be a placebo. Either way, does it matter? I mean, if you find out you’re not on “the path” next time an update rolls out (could be months or never now that we have JB), just use this to climb back on.

Besides, if you’re flashing leaked stuff now, you’ll probably be flashing leaked stuff long before VZW rolls it out OTA in the future.

By: Kerry Saylor

Kerry Saylor — Wed, 26 Sep 2012 13:44:00 +0000

So, the core code is different between JRO03O image and JRO03R. Yea – not so clear….but, good enough! Thanks!

By: PC_Tool

PC_Tool — Wed, 26 Sep 2012 13:33:00 +0000

Most AOSP builds of JB (for any device that is supported in AOSP) have been on R for a while now.

AOSP does not rely on factory images, and is almost always ahead of them in terms of version.

By: PC_Tool

PC_Tool — Wed, 26 Sep 2012 13:31:00 +0000

Yummy,

Factory reset your device. Obviously, something was installed prior to the update that completely hosed the process. (Yes, “hosed” is the technical term)

Factory reset it and you should be golden. Failing that, follow Dave’s advice and flash Bugless Beast. You’ll thank Peter Alfonso later.

By: br_hermon

br_hermon — Wed, 26 Sep 2012 13:29:00 +0000

So does that mean you have a Nexus S 4g? or do you have a different model phone with a rom based off of JRO03R? What Rom?

By: PC_Tool

PC_Tool — Wed, 26 Sep 2012 13:28:00 +0000

The image is the OS (with binaries, presumably O, in this case). You can fastboot flash these image files to bering your phone to a bone-stock (though unlocked) state.

The binaries are for building AOSP. The latest AOSP branch is likely R, thus accounting for the R binaries. Verizon simply hasn’t “approved” R images.

Hope that helps instead of confuses you even more.

By: Kerry Saylor

Kerry Saylor — Wed, 26 Sep 2012 13:18:00 +0000

I was going to ask this… what is the difference between the image vs. binaries? I noticed this difference too and am just curious….

By: PC_Tool

PC_Tool — Wed, 26 Sep 2012 12:52:00 +0000

The funny thing is, the factory image is O, while the binaries are R.

Go figure…