Galaxy Nexus (VZN) System Update: JRO03O

Search This thread

georgiapi

Senior Member
Oct 28, 2011
448
53
North GA
alcphoto.net
Just curious, I'm one who cannot get past the animation on any JB ROM, trying this one now.

How long after flashing the rooted one do you guys wait for boot. I am in the animation screen now for 15 minutes. It went by the Google pretty fast.
 

tarund

Senior Member
Oct 17, 2010
301
75
http://d-h.st/MxW

Here it is....

Sent from my Galaxy Nexus using xda app-developers app

Yes it was too late ....I just finished flashing before I saw ur post...now I lost root...:eek:

Sent from my Galaxy Nexus using xda app-developers app

:( Sorry to hear that, man. Well, I'm sure a rooted file will be available on faster mirrors soon. I will be creating a torrent as soon as I get the rooted ZIP. I will share the torrent link here once ready. :D

---------- Post added at 10:17 PM ---------- Previous post was at 09:59 PM ----------

Rooted ZIP with Trinity Kernel located here: http://goo.im/devs/ThunderStick/Toro
 

afma_afma

Senior Member
Dec 7, 2009
1,511
25
I flashed super user for ARM device specific and I am now good...I have root access now...

Sent from my Galaxy Nexus using xda app-developers app
 

felix_morariu

New member
Apr 21, 2011
3
0
My Verizon App

Did any of you manage to get the My Verizon app working on this build? Logs me in but app gives an error.
 

Ravenbf

Member
Apr 11, 2012
29
4
Did any of you manage to get the My Verizon app working on this build? Logs me in but app gives an error.

I just flashed this earlier......And I blew past the part about saving root, but I had Voodoo OTA Rootkeeper and I was able to save my root. Everything is working great, including the My Verizon app. I can't tell if the new radios are an improvement for me yet because I am in an area that has poor signal and no 4G, but I am looking forward to seeing how it is when I get home Friday. So far runs smooth as butter and I am enjoying finally having JB on my Nexus.....was about to flash Bugless Beast this weekend. Good luck everyone!!!
 

Jimmah555

Senior Member
Jul 27, 2009
371
122
Las Vegas
Did any of you manage to get the My Verizon app working on this build? Logs me in but app gives an error.

I couldn't get it to work either. Then I installed Lean Kernel on the stock ROM, and everything was working when I checked it a while later. I'm not sure if VZW had to enable something or what, but I accessed it through the data usage widget when it worked the first time so maybe that had something to do with it.

Prior to that, I flashed the old radio for a minute to test out the speeds and compare, then I flashed the new ones again, then Lean Kernel.

I can't tell you what exactly worked, only what I did :)
 
Last edited:

mduran1023

Member
Dec 4, 2011
25
7
Just finished flashing, only problem so far is that I can't download wallet from the market anymore.

Up to this build I was still able to install it from my app history.

Sent from my Galaxy Nexus
 

Winesnob

Senior Member
May 20, 2012
826
294
Lorton, VA
Just finished flashing, only problem so far is that I can't download wallet from the market anymore.

Up to this build I was still able to install it from my app history.

Sent from my Galaxy Nexus

Me too. Did a factory reset after loading the JB zip (too many app errors after update, and the reset seems to have worked), and now the Play Store shows both of our Nexi as incompatible. Fortunately The Android Source has the most recent apk file posted - did a side load and it now appears in my Play Store device profile as installed. Not sure how or if automatic updates will work in the future.

Aside from this little glitch, this build is spectacular.
 

teddy333

Member
Oct 23, 2007
43
5
The upgrade went very well for me (Coming from Vicious V1). My nexus runs alot smoother with this version. I was able to get root back by installing "Superuser-3.1.3-arm-signed.zip" after installing the update. It can be found at http://androidsu.com/superuser
 

Beamer9408

Senior Member
Jul 17, 2011
938
169
Why does everyone worry about losing root? Once you flash the new ota can't you just unlock bootloader install CWM and flash the su zip? I didn't think we needed an exploit for root on this phone.

Sent from my Galaxy Nexus using xda premium
 

miketoasty

Senior Member
Sep 13, 2010
2,467
487
Why does everyone worry about losing root? Once you flash the new ota can't you just unlock bootloader install CWM and flash the su zip? I didn't think we needed an exploit for root on this phone.

Sent from my Galaxy Nexus using xda premium

Most people are coming from non-Nexus phones where if you updated your phone you could possibly lose root and never get it back. I completely understand their concerns. Luckily we do have a phone where losing root forever is not an issue what so ever.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 44
    I received the system update notification (JRO03O) within the past hour. See pic.
    25
    OK gentlemen, this is definitely a testing build. It requires you first install the IMM76Q update. So you need to flash to IMM76K, upgrade to IMM76Q, then to JRO03O. The link is here:

    http://android.clients.google.com/p....signed-mysid-JRO03O-from-IMM76Q.4a91da6c.zip

    All the thanks goes to El Madhatter. I'm mirroring the file at randomphantasmagoria.com as I speak.
    8
    Somehow El Madhatter has a VZW testing phone. He got the IMM76Q update that borked search as well. He's credible. As with the IMM76Q update, I'm working with him via PM to get the filename. Everybody go rub one out and chill. We'll get the filename soon enough. :)

    Since there's no support documentation, this is most definitely a testing build. Who knows if this will be the actual OTA, but at least we know it's being tested!
    5
    Looks like the Sprint GNex just received JRO03U with radio FH05 for both CDMA and LTE. Kernel date 8/28. Given that both are CDMA/LTE devices, can we assume that Verizon has yet another version of JB in testing?

    Nope, apples and oranges. The Sprint Gnex has a kernel that's built by Samsung, not Google. Notice the se.infra@SEI-29 and the build date being in KST (Korean Standard Time). That's because the Sprint Gnex gets updates from Samsung, not Google. Verizon gets updates direct from Google and uses the AOSP kernel. So an 8/28 build date on the kernel only means that's when Samsung built it. It doesn't mean Google has done a new build for Verizon.

    I wouldn't doubt it. Remember how the Verizon Gnex saw that 4.0.3 leak that never became official? I'm sure that's what's happening now.

    IMM30B is what you're talking about. That was actually an early build of 4.0.4. But another IMM30B is probably not what we're seeing here. Keep in mind that every single Google-updated Nexus device (including the WiFi-only and VZW Xoom) are getting JRO03(X) builds for Jelly Bean:

    JRO03C (GSM Gnex)
    JRO03D (Nexus 7)
    JRO03E (GSM Nexus S worldwide except Telstra Australia)
    JRO03H (WiFi Xoom and VZW has approved this for their Xoom and will hopefully be rolling it out soon)
    JRO03L (GSM Nexus S on Telstra Australia)
    JRO03O (VZW Gnex Testing Build)
    JRO03R (Nexus S 4G on Sprint)

    The only one we still don't know about is the Korea Nexus S, though my money is on JRO03E.

    If Jelly Bean had an IMM30B case, it would have probably been JRN84D which shipped on the Nexus 7 and was also released to those GSM Gnex devices that they gave away at IO 2012. That was the one that let them work out the bugs.

    If 4.1.1/JRO03(X) builds weren't intended for every Google-updated Nexus device, they would have done a limited rollout to one or two devices, a-la 4.0.3 and made everyone else wait for a 4.1.2 release. Also, historically, whatever updates the GSM Gnex gets, Verizon gets too eventually. They both got ITL41(X) builds for 4.0.1, they both got ICL53F for 4.0.2, they both got IMM76(X) builds for 4.0.4. The GSM Gnex never got 4.0.3 and neither did Verizon.

    The only devices that got 4.0.3 were the 900 MHz (T-Mobile) GSM version of the Nexus S and the WiFi-only Xoom. All other Nexus S devices, as well as the VZW Xoom and all Galaxy Nexus devices stayed put on whatever their most recent firmware was until 4.0.4 came out. There was much ire out of the Nexus S camp that the AT&T and Sprint devices were stuck on Gingerbread until 4.0.4 came out, while the T-Mobile camp got to have all their ICS goodness. What they didn't realize was that the 4.0.3 build for the Nexus S was anything but "ICS goodness". It was absolutely craptastic and most of us who ran it as a daily driver hated it. There were more problems with that build than I could possibly list. haha Apparently the 4.0.3 build for the WiFi-only Xoom (IML77) was much better and I remember being really bummed that VZW didn't get it...and to pour salt on the wound, we got a system update a month after the WiFi Xoom got ICS...but the VZW update wasn't ICS...it was a Honeycomb update that did nothing but fix an issue with restoring data connectivity after coming out of airplane mode. haha