yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Handala48:
Yes, Google Maps says I'm running takju. Is that good enough to know that? And btw, I got this same error when I try to run the OTA update.

I figured that's what it meant.
[Samsung Galaxy Nexus] efrant:
What that error means is that the launcher file is not stock. Either you or one of your root apps modified it.
[Samsung Galaxy Nexus] Handala48:
I'm sure I didn't modify it. And for apps the only that I might think of is Volume+. Other than it all of my apps are just regular apps.

Is there a way to fix this? Or do I need to restore ROM?

Thanks
[Samsung Galaxy Nexus] ironside2011:
I hope so! I love my nexus but Verizon is so damn slow
[Samsung Galaxy Nexus] wwjoshdew:
Same here!

First Part: http://bit.ly/WJRboP

Second Part: http://bit.ly/ZZs0Rz
[Samsung Galaxy Nexus] sickopsycho:
Hey Josh! I'm looking into your problem, too- I frequent this forum so if there is an answer you'll find it here for sure. =)
[Samsung Galaxy Nexus] osm0sis:
Did you even read the error in your second video? It says it failed on the radio.
[Samsung Galaxy Nexus] efrant:
You can pull the file out of the stock system image and replace the one currently on your device, or just flash the system image in fastboot. Instructions for both are in the second post.
[Samsung Galaxy Nexus] sickopsycho:
I concur- now do you have anything constructive to tell the man to help him out? Why does it fail on the radio?

---------- Post added at 10:00 PM ---------- Previous post was at 09:54 PM ----------

Did you try installing via ODIN as the instructions suggested? check PM...
[Samsung Galaxy Nexus] osm0sis:
Clearly he isn't running the stock radio to pass the OTA assert. So constructively it should be obvious what he needs to do. ;)

Edit: Wait, that shouldn't be possible on the toroplus since there aren't any regional variants... My bad, but either way the next step would be to reflash the radio. :good:
[Samsung Galaxy Nexus] Handala48:
Got it..

Thanks.
[Samsung Galaxy Nexus] wwjoshdew:
Ah, okay. I missed that I guess. Good eye. I have a 100% stock rom using this method: http://www.youtube.com/watch?v=xAgorfNke_U

https://dl.dropbox.com/u/266817/recovery.log

Since I was 100 percent stock on the first attempts and then tried flashing via twrp (the log above), I don't know what to do.
[Samsung Galaxy Nexus] osm0sis:
Hmm. Toolkit issue maybe? Download the factory image and manually reflash the radio. :)
[Samsung Galaxy Nexus] EthanFirst:
from your log

your device use custom rom

Try to check rom by Nexus Update Checker app --> play.google.com/store/apps/details?id=com.ethanfirst.nexusupdatechecker
[Samsung Galaxy Nexus] wwjoshdew:
Not sure what to do now... https://twitter.com/wwjoshdew/status/291759409682583552
[Samsung Galaxy Nexus] oldblue910:
Can someone verify that both the CDMA and LTE baseband versions are L700.GA02?
[Samsung Galaxy Nexus] osm0sis:
Definitely download the factory image yourself (no toolkits), then reflash the radios manually with fastboot. :good:
[Samsung Galaxy Nexus] wwjoshdew:
I'm gonna try this route: http://nexuscm.blogspot.com/2012/05/sprint-galaxy-nexus-radio-images.html

and see if just flashing the radios works. I'm gonna get this, especially now that I know what the error was! :D
[Samsung Galaxy Nexus] osm0sis:
Haha where do you keep coming up with these sites? Use the actual factory image for the radios so that there is no mistake. ;)

https://developers.google.com/android/nexus/images#mysidspr
[Samsung Galaxy Nexus] EthanFirst:
your log show Android version 4.0.4

but my app show Android version 4.1.1

:confused:
[Samsung Galaxy Nexus] osm0sis:
I think that was just the build of twrp he was using providing all those values?
[Samsung Galaxy Nexus] oldblue910:
Can someone who has successfully applied the Sprint GA02 update please verify for me that both baseband versions show as L700.GA02? Thanks!
[Samsung Galaxy Nexus] EthanFirst:
Hi oldblue910.

I found http://gadgetian.com/47929/sprint-galaxy-nexus-android-4-2-1-ota-update-ga02-download/
[Samsung Galaxy Nexus] oldblue910:
That's the same screen posted when the ODIN images came out. It shows the LTE radio as FG01. That radio is two versions old. I don't believe they would regress a radio back one version in an OTA. That's why I'm looking for someone who has actually applied the OTA ZIP (as opposed to the ODIN images) to check it.
[Samsung Galaxy Nexus] director87:
Can't get past recovery mode android with exclamation mark

I'm trying to install the 4.2.1 update for the sprint gnex.

When I get into recovery mode, I push volume up and power button. I do this and it reboots the device. Done this about 8 times now, reproducing the same results. Am I doing something wrong?

This is stock bootloader, unrooted. Just bought it a week ago and haven't touched it yet.

Any help would be appreciated :)
[Samsung Galaxy Nexus] efrant:
That is my error, sorry. I need to revise the instructions: you hold power and then quickly push volume up, not the other way around.
[Samsung Galaxy Nexus] oldblue910:
When you get the OTA installed, would you be willing to check your baseband version in Settings / About Phone post what it says? I'd really appreciate it!
[Samsung Galaxy Nexus] director87:
Thanks for the help!
[Samsung Galaxy Nexus] oldblue910:
Thank you sir!
[Samsung Galaxy Nexus] ryan stewart:
My problem is I flashed that and it took me back to FC12 radios. Then I attempted the update and my assert failed on "omap_hsmms.0/byname/radio:" So I figured it was mad that I had old radios. I updated both to FD02 and Im still getting that error.

So Im on the stock image from Google, the radios posted from the site he was on and still cant update just using ADB. Anyone know of a technique that could get me past this?
[Samsung Galaxy Nexus] oldblue910:
You need to flash all of the images from Google, radio included. OTAs will fail if you're using a radio that's different from the one you're supposed to be using. If you flash the images from Google, make sure you flash radio.img and radio-cdma.img as well. This will put you on the FH05 radios. At that point, the OTA should apply.
[Samsung Galaxy Nexus] ryan stewart:
SO I flashed that massive image listed at the link posted, from Google. When following the process it did flash both radios. Im on FH05 build of 4.1.1 but both radios are FC12. I had flashed to FD02 so this def flashed them back to FC12.

Yay, I finally found some radio images from the Odin thread and that seems to have made her happy. We shall see if it completes (radios and all).

Edit: So updating those images from the Odin thread made it happy, installed on 4.2. Hopefully bluetooth isnt troublesome like some people have reported.
[Samsung Galaxy Nexus] PhazeDelta1:
Thanks for this.
[Samsung Galaxy Nexus] ryan stewart:
If your bootloader is unlocked when you get that screen hold power and press volume up. Then with the phone plugged into your computer set the phone to "receive from ADB" and do an ADB sideload from the computer.

If that is greek to you then you should just wait for the OTA, you might damage your phone otherwise.
[Samsung Galaxy Nexus] Winesnob:
Re: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JOP40D / 4

If he's on 4.1.1 or better it doesn't matter if the boot loader is unlocked. Stock recovery now permits installing the OTA zip files from SD card out via adb. Just have to do the vol up+ power to get past the android on his back.
[Samsung Galaxy Nexus] bcollado:
Hi, I'm trying to flash 4.2 to my sprint galaxy nexus. But, I'm having the radio error as well when I go to sideload it. I followed what you guys were saying about how to fix it, and then I downloaded the FH05 image and pulled the radio files from it. I flashed them onto my phone. This didn't change the error at all though when I went back in to try to sideload it again.. I don't know what else to do and I'm getting pretty frustrated. Any and all help would be very much appreciated. Thank you.
[Samsung Galaxy Nexus] wwjoshdew:
I gave up after flashing the radios and it still failing as well. Then I install CM10.1 (which is Android 4.2.1) instead. Which I prefer over stock anyways.
[Samsung Galaxy Nexus] ryan stewart:
I flashed the radios from the Odin thread, the FH05 ones, and that got me past the prompt. So my order was FH05 image, LTE to radio partition and then CDMA to radio-CDMA partition. Confirmed in Fastboot that it showed both radios being up to date, then did the ADB push of the new image. Went like butter doing that.
[Samsung Galaxy Nexus] osm0sis:
Yeah that's weird that you guys' radios weren't flashing correctly via fastboot... Glad you got it working via odin though!
[Samsung Galaxy Nexus] DJeremyC:
I am also trying to install the 4.2.1 update for the FH05 nexus version and yes all radios are the FH05. Here is the error message I get from ROM Manager when trying to install either via ROM Manager or just straight from the CWM Recovery.

I have attached the error message as an attachement so I didnt leave anything out, yet not clutter the page.

Thanks for your help...its probably something stupid I am missing as this is the first time I am trying to manually update. Also I have USB debugging mode on and it is rooted/bootloader unlocked to be able to install Franco Kernel to work with my Palm Touchstone Charger.
[Samsung Galaxy Nexus] osm0sis:
Gotcha covered. First make sure you're on stock kernel since you'll fail on that too if you don't. :)

Now, as you can see from the failed assert in your log /system/lib/hw/power.tuna.so is what's failing.

franco.Kernel replaces a system file (the PowerHAL library) to make sure that the max freq doesn't get reset every time the screen turns off.

Don't worry though, I wrote the script that replaces that file and it backs up the file first. ;)

Go to /system/lib/hw/ and move power.tuna.so.fkbak to power.tuna.so, then everything should work fine. Make sure you move the file, not copy, since you'll want franco.Kernel to back up the new one too, and the script only does that when .fkbak doesn't already exist. :good:
[Samsung Galaxy Nexus] DJeremyC:
Still a dead robot

Hey...did what you suggested. Still no luck. Here is more details. Within Franco Kernal Updater I installed the LeanKernel as Franco was taking too much battery. I went in and found the power.tuna.so and replaced it with the power.tuna.so.bak file. Tried install of 4.2.2 and it failed again. Rebooted and it still shows that LeanKernal is the current one installed. So I am taking it that I have lost the stock Sprint JB4.1.1 file for that and was a stupid noob to not back that up prior :crying: Happen to have a copy? Also I have attached the error message from the new attempt but to me it looks about the same - being it still shows LeanKernal as being installed.
[Samsung Galaxy Nexus] efrant:
All the files are here. Extract the system image and the boot image from within, flash them using fastboot, then apply the update.
[Samsung Galaxy Nexus] osm0sis:
But it's likely just the boot.img you need to flash so try that first. You didn't follow my first line which was "go back to stock kernel first." ;)
[Samsung Galaxy Nexus] DJeremyC:
lol....Just flashed boot.img using fastboot and got stuck on the Google bootup logo. Had to do a system restore. This has definitely been a fun first adventure into flashing with android...but least thus far phone still is fixable. I guess I will have to try the flashing of the system image approach. Not sure if this method erases the data on the phone or not.
[Samsung Galaxy Nexus] osm0sis:
You must have flashed the wrong kernel by device or version. You need to flash the one in the factory image for your device for the version you're trying to come from.
[Samsung Galaxy Nexus] efrant:
Re: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JOP40D / 4

It won't erase your data.
[Samsung Galaxy Nexus] Winesnob:
If you flash ONLY the system partition, then no you won't lose data. If you execute the flash all script in the factory image, it will wipe your device clean.
[Samsung Galaxy Nexus] userno69:
I'm wondering if anybody can help me out here. I have a Sprint GNex running official, OTA 4.1.1. I have stock recovery and am not rooted. I want to adb sideload the new GA02 4.2 build to my phone, using the quoted method. I am having a problem, though. I've installed the Gnex drivers from Samsung, and the phone does show up when I plug it into my computer when it is booted to the OS, with USB debugging enabled.

However, when I am booted to recovery, at the point where I've selected "Apply update from ADB", my computer no longer recognizes the device, it has a yellow exclamation mark in Device Manager. It no longer shows up when I do "adb devices" in this state, either.

As such, I am unable to flash GA02. Anybody know what on earth is preventing the phone from being detected while it is booted to recovery mode???
[Samsung Galaxy Nexus] efrant:
After you booted to recovery, did you enter the stock recovery menu (hold power and press volume up)? And it still doesn't recognize it? Then re-install the driver when you are booted like that.
[Samsung Galaxy Nexus] EthanFirst:
Try update from USB Drive

[YOUTUBE]iQaD1OaEu04[/YOUTUBE]
[Samsung Galaxy Nexus] wwjoshdew:
UPDATE! mskip's toolkit now updates you to the FH05 radios or GA02!

https://twitter.com/wwjoshdew/status/295359344818667522

So yeah, I'm happy! I had like FC12 before and it needed to be on FH05 for it to update to GA02.
[Samsung Galaxy Nexus] userno69:
Correct, that is the problem I am experiencing. And darn! Your suggestion sounded promising, but didn't work :(

I don't have a micro to full size USB adapter :(
[Samsung Galaxy Nexus] efrant:
Re: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JOP40D / 4

If a toolkit can do it, and you couldn't do it yourself, then either you were typing the wrong commands or using the wrong files. A toolkit is not some magical thing -- it just executes the commands for you and hides them from you. Not the best way to learn IMO.
[Samsung Galaxy Nexus] jasonsf:
This is slightly off topic. I've updated to GA02 via recovery so I'm fine, but this is the first update since I've owned my Galaxy Nexus. Do we expect this to be pushed OTA sometime, or is that not how Sprint Nexus phones are usually updated? Just curious since I've only recently moved to this phone from my Epic 4G.

Thanks for all the great info in this forum!

Jason
[Samsung Galaxy Nexus] wwjoshdew:
Re: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JOP40D / 4

Eh, it's alright. In the end my Nexus has GA02. When installing CM10.1, it gets rid of the radios though. Does anyone have any GA02 radio images or a flashable zip they could link me to?
[Samsung Galaxy Nexus] jasonsf:
I guess this answers my question: http://community.sprint.com/baw/com...blog/2013/01/30/galaxy-nexus-software-updates
[Samsung Galaxy Nexus] DJeremyC:
OTA Finally Arrived

Sorry to blow everyone off and not let you know how my transition to 4.2.1 has gone thus far. Real life sucks and gets in the way of tweaking my technology :silly:

I havent had time to extract the kernal boot.img and see if that would fix my issue, but the OTA showed up on the phone today and crashed trying to install so hopefully I can get it all fixed.

I think the route Ill try is to reflash the boot.img first, and then see if all will update. If not I guess I can add to the list the system.img and see. I didnt want to factory restore and lose data so guess these are the best two options. I have copied over all my Titanium backup stuff and pics etc so if I have to restore I take it that just copying that back over to the phone will allow for titanium to see it and reinstall all my apps and its data.

Thanks for the insight thus far and I will let you know how it goes....hopefully tonight :fingers-crossed:
[Samsung Galaxy Nexus] osm0sis:
Just read the failed assert error messages from the OTA and it will tell you what you need to change back to stock. They are pretty much expected if you've been modding or something. Flashing system.img won't wipe any data and it's pretty much a cure-all so don't be afraid there, you'll just need to reroot and redo any system mods you've done like busybox. Good luck! :)
[Samsung Galaxy Nexus] DJeremyC:
go figure. I flashed the boot.img from stock, and it showed it was running the stock kernal. Replaced the power.tuna.so file and went to flash the OTA update that popped up again. All looked to be going well...then about halfway through my little robot fell over with the red error triangle, this time with no error message. SO CRAP! Rebooted back into 4.1.1 just fine...so debating whether to attempt pushing just the system.img or to actually hope for the best and wipe the whole damn thing....hmm....

Sorry to be the PITA, but had to vent to make myself feel better :rolleyes:
[Samsung Galaxy Nexus] osm0sis:
You didn't say what failed this time. Whatever it says is what you need to replace with stock. Either way, pushing the 4.1.1 system.img should correct whatever is failing and not have any adverse affects.
[Samsung Galaxy Nexus] funkyblue04:
Anyone get the Vodafone AU update yet? I am desperate for the new radio...

Android Version:	4.1.2

Baseband Version:	I9250TDVLH1

Kernel Version:	3.0.31 – g4f6d371Android-build@vpbs1)#1 SMPPREEMPT Mon Sep 10 13:41:13 PDT 2012

Build number:	JZ054K.I9250TDVLK2

http://support.vodafone.com.au/articles/FAQ/Samsung-Galaxy-Nexus-Android-4-0-4-Update

I am also not sure what variant Vodafone AU was yakjuxw? etc.
[Samsung Galaxy Nexus] DJeremyC:
Sorry...but thats just it...basically I replaced the kernel back to stock (flash boot.img) and the power.tuna.so file that was changed during the FrancoKernelUpdater. When I rebooted the OTA system update came back up, so I pushed install...during the installation of the Sprint JB4.2.1 OTA update, the robot screen stopped, he fell over with a red triangle <!> and that was it (no error, nothing) did a battery pull to reboot back into JB4.1.1

So other than that, I cant tell ya what really failed at all...I will push the system.img tonight and see what happens. Otherwise I guess factory image, re-root, and copy back my Titanium app/appdata to see if I can get it back up to normal quickly.
[Samsung Galaxy Nexus] osm0sis:
That just means you're in stock recovery. Perhaps consider using CWM and flashing the OTA that way. :)
[Samsung Galaxy Nexus] thephantom:
Re: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JOP40D / 4

That's yakjudv. 1st post doesn't have that update yet. Perhaps none have shared it to date
[Samsung Galaxy Nexus] DJeremyC:
GENIUS!!!!! :good:

Thanks for putting up with me.

Guess the way it was trying to push just wasnt doing the trick. What I had to end up doing...reflashed the boot.img stock (as I had changed it back to Franco for charging) and also replaced power.tuna.so just in case. Then I went into ROM manager and reflashed the CWM recovery. Booted into CWM Recovery from ROM Manager and pushed the update (easy enough) Now I am booted into stock JB4.2.1 :highfive:

Making a Titanium backup now of the whole system (lessoned learned). Hoping to repatch kernel for charging, but didnt see the boot.img files as easily in the zip file for 4.2.1 as it was in 4.1.1 so not sure how to get that yet. Would like to grab that so I wont run into this problem again.

;)

Thanks osm0sis, and everyone else here....great group :cool:
[Samsung Galaxy Nexus] osm0sis:
Glad it worked! For the latest Franco follow the thread link in my sig and it links to where his 4.2 zips are in the OP. Or you could buy franco.Kernel updater to support Franco and flash it that way (the free version hasn't been updated to support 4.2 yet).
[Samsung Galaxy Nexus] DJeremyC:
Well poo-poo...All went downhill. Ended up just flashing the 4.1.1 factory image after all and erasing everything. So phone is booted back up and the update showed up again...but still failed...so totally confused. Wouldnt think anything should fail if it is totally stock again. hmm...
[Samsung Galaxy Nexus] Winesnob:
I've read a number of places that the FH05 radios have 2 different versions (no idea why), causing the system 7 errors on the OTA. There is an UNOFFICIAL factory image for GA02 at http://goo.im/devs/mskip/stock/toroplus, along with both FH05 images (new radios, old radios). Might be worth a shot. Worst case is you fall back to FH05 from the Google hosted images.
[Samsung Galaxy Nexus] osm0sis:
If you'd flash CWM/TWRP like I said it will tell you what failed in the OTA. Then you will know how to fix it.

You're making this much harder than it should be. ;)
[Samsung Galaxy Nexus] DJeremyC:
I did...just was confused a bit I guess. But figured out what I did wrong. I guess the factory image I pushed from the Nexus Toolkit installed the FC radios instead of the FH radios...so downloading them now and hoping to push them standalone.

Thanks again...definitely getting to know how to do this in-and-out.
[Samsung Galaxy Nexus] KSUJedi:
So having some trouble with this and hoping someone can help. I've got a Sprint GNEX, unlocked bootloader, rooted, running stock 4.1.1 trying to update to 4.2.1. I've never flashed any different radios. Did flash stock Wi-Fi tether patch. Followed Revoked's modified Method 1, installed, ran, and temp unrooted with OTARootKeeper, rebooted into recovery (have tried CWM 6 non-touch, and TWRP 2.4), chose to install the zip, and with both recoveries, got....

Installing '/sdcard/c5ea6e959840.update_mysidspr_FH05_to_GA02.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found.

installing samsung updater extensions for toroplus

Verifying current system...

file "/system/framework/framework-res.apk" doesn't have any of expected sha1 sums; checking cache

failed to stat "/cache/saved.file": No such file or directory

failed to load cache file

script aborted: assert failed: apply_patch_check("/system/framework/framework-res.apk", "bb4e8e7a4eee1d656067ba60d204467d36c5a099", "0e876757855bdb4dc572effbf0b06a8b921d4e69")

assert failed: apply_patch_check("/system/framework/framework-res.apk", "bb4e8e7a4eee1d656067ba60d204467d36c5a099", "0e876757855bdb4dc572effbf0b06a8b921d4e69")

E:Error in /sdcard/c5ea6e959840.update_mysidspr_FH05_to_GA02.zip

(Status 7)

Error flashing zip '/sdcard/c5ea6e959840.update_mysidspr_FH05_to_GA02.zip

So seems to be telling me its something in the framework-res.apk that's causing a problem, maybe because it's not stock from what I understand from osm0sis's posts above. Maybe because of my flashing the stock tethering patch?

Update... Ok, as I was basically thinking/posting out loud and started thinking it was my tethering patch causing the problem, I flashed the "return to stock" tethering zip, then attempted the 4.2 update again, and it's currently installing, so looks like that solved it. Guess I'll just leave this here in case anyone else comes across the same problem and it can help.
[Samsung Galaxy Nexus] Barbatos19:
Good day everyone. Can anyone teach me on how to unlock a galaxy nexus locked from a carrier called smart telecommunication here in philippines? and does this Phone is compatible with all the rooting and flashing paranoid android 2.99 even though its locked from a carrier? (what mean is, does the carrier plays a role if we flash PA 2.99 on this phone? tnx for the reply
[Samsung Galaxy Nexus] amogil:
try wug fresh one click

---------- Post added at 02:49 AM ---------- Previous post was at 02:49 AM ----------

no ota updates
[Samsung Galaxy Nexus] ogre_x:
Takju is out:

http://android.clients.google.com/p...3.signed-takju-JDQ39-from-JOP40D.472aafeb.zip

Source: https://plus.google.com/u/0/103876278794381402383/posts/3coHFSrFeQq
[Samsung Galaxy Nexus] flixos:
Waiting for the Yajku version here...by the way, are there any improvements so far with the new build?
[Samsung Galaxy Nexus] thephantom:
Re: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JOP40D / 4

Thanks. Updated my gnex with it
[Samsung Galaxy Nexus] osm0sis:
F**k yes!
[Samsung Galaxy Nexus] oldblue910:
Re: [REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JOP40D / 4

The takju update has been mirrored on randomphantasmagoria.com.