Develop Bugs

VZW CDMA Galaxy Nexus Bricked / Boot loops help

I own the VZW Galaxy Nexus , and I just unlocked the bootloader and now my phone will not boot-up. The device is stuck on the Google logo splash screen with the lock icon at the bottom of the screen signifying that the bootloader is unlocked. I used the program called Galaxy Nexus Root Toolkit v1.4 from Wugfresh to unlock my phone's bootloader, and now my phone is currently bricked. I can still go to the bootloader by holding down volume and power. Can someone help me restore my phone to a working state?
EDIT: Also I'm sorry if this is the wrong place to be posting this, I don't use this site often and the site would not let me post to Galaxy Nexus Android Development for some reason. I can still go to the bootloader by holding down volume and power.

the reason why ur stuck is because ur stock recovery might be blown up. try and flash stock recovery ....or cwm recovery...
Sent from my Galaxy Nexus using xda app-developers app

actually try a battery pull and startup ..
Sent from my Galaxy Nexus using xda app-developers app

afma_afma said:
actually try a battery pull and startup ..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You think I didn't try that already? And I don't know how to flash a stock recovery, help?

My phone also got stuck at the google screen when it tried to boot. Turned out it was a bad flash when I was trying to install jelly bean. I just went back in and flashed jelly bean again and everything was back to normal. I think you'll be just fine if you just flash a stock rom or whatever rom you want to run on. Look for one of the guides on how to return to stock and just skip the part about relocking your bootloader.
Sent from my Galaxy Nexus using xda app-developers app

In the toolkit there is a "flash back to stock" option. Boot back into bootloader and use it.

Thank you very much wish to continue your work

z06mike said:
In the toolkit there is a "flash back to stock" option. Boot back into bootloader and use it.
Click to expand...
Click to collapse
The flash back to stock option doesn't seem to work, because the cmd window won't read me device. What should I do?

johnc7995 said:
The flash back to stock option doesn't seem to work, because the cmd window won't read me device. What should I do?
Click to expand...
Click to collapse
Where's your folder located?
Sent from my ADR8995 using xda premium

johnc7995 said:
You think I didn't try that already? And I don't know how to flash a stock recovery, help?
Click to expand...
Click to collapse
I didn't mean to thank your post so you owe me one.
Why be an ass to someone who is trying to help you. A simple I tried that and it didn't work would be fine.
If we assumed everyone did what we would suggest then half of people's issues would probably not have gotten fixed.
Like I would assume you new how to flash stock recovery so I would not want to offend you buy telling you how.
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
johnc7995 said:
The flash back to stock option doesn't seem to work, because the cmd window won't read me device. What should I do?
Click to expand...
Click to collapse
Now to be nice because I know a non working phone sucks : )
Put your phone into the bootloader screen to use in the toolkit. To do this. remove battery, place back in....Then hold volume up and down at the same time and then power the device on while holding the buttons. You will then be in bootloader and the toolkit should recognize your device from there.
If it does, try the steps over again or if you can flash back to stock everything and start over. The tollkit give you the instructions where to get the files if you choose that option.

johnc7995 said:
The flash back to stock option doesn't seem to work, because the cmd window won't read me device. What should I do?
Click to expand...
Click to collapse
Shoot me your email and I'll try and help you out through G talk.

blackscreen but fastboot will work? There are no responses, unless i plug it in. i get a driver that is enabling and then disabling. The Driver is called OMAP4440.

ota update issue

Hi guys I'm trying to get my nexus updated to JB. I am on 4.0.4 rooted using the toolkit. I have flashed stock recovery back to the phone using toolkit. I'm getting the attached error. Any ideas anyone?
Thanks

step 1) STOP USING A TOOLKIT!
step 2) http://forum.xda-developers.com/showthread.php?t=1626895

corkie1 said:
Hi guys I'm trying to get my nexus updated to JB. I am on 4.0.4 rooted using the toolkit. I have flashed stock recovery back to the phone using toolkit. I'm getting the attached error. Any ideas anyone?
Thanks
Click to expand...
Click to collapse
Well first of all, I definitely don't recommend you using toolkit. Using it has higher chance of bricking your phone.
It seems like you might have to boot into the clockworkmod recovery and from there, flash the zip. It's faster than the way and also doesn't give you those kind of headache
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Hi guys when I say toolkit its the specific gnex toolkit. I thought this was a well received method for rooting - no?

Are you sure you flashed the right stock recovery for your phone?

Ya definitely flashed right stock recovery. It's very easy using the toolkit.

corkie1 said:
Ya definitely flashed right stock recovery. It's very easy using the toolkit.
Click to expand...
Click to collapse
so is fastboot
fastboot flash recovery nameofrecovery.img

I've used the toolkits and fastboot on 3 different gnex's and not had problems either way. If you fastboot incorrectly as well it's possible to brick your phone right?

wisniphi said:
I've used the toolkits and fastboot on 3 different gnex's and not had problems either way. If you fastboot incorrectly as well it's possible to brick your phone right?
Click to expand...
Click to collapse
well yeah if you fastboot the wrong recovery, but if you typo the command, it errors and wont flash it.

The OTA failed not because of your recovery but because of /system/usr/keylayout/generic.kl not being stock or missing.
You can either find that file and push it back and then run the OTA hoping that's the only file you modified.
Or flash the stock JB image following the link Zepius posted in the 2nd post.

I used this thread to help me update to JB when the OTA wasn't showing up for me (I was impatient).

wisniphi said:
[snip]
If you fastboot incorrectly as well it's possible to brick your phone right?
Click to expand...
Click to collapse
Nope. Odin yes. Fastboot no.
OP: And as El Daddy said you (or one of your root apps) prob changed something related to your keyboard, so you need to replace that file with the stock one.
Sent from my Galaxy Nexus using Tapatalk 2

I can't agree more! This is literally the third straight post I've read with an issue that started with 'I'm rooted using X toolkit...'
Sent from my Galaxy Nexus using xda app-developers app

El Daddy said:
The OTA failed not because of your recovery but because of /system/usr/keylayout/generic.kl not being stock or missing.
You can either find that file and push it back and then run the OTA hoping that's the only file you modified.
Or flash the stock JB image following the link Zepius posted in the 2nd post.
Click to expand...
Click to collapse
Hiya - thanks - I browsed to the location and found a generic.kl.bac file - renamed this rebooted and the OTA went through no problems

JB OTA won't install- says install untrusted zip? in cwm

I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app

Your phone is rooted? If yes you can't install OTA updates

I'm rooted yes. So what do I do? Unroot?
Sent from my Galaxy Nexus using xda app-developers app

htc_woe_is_me said:
I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
polimeno said:
Your phone is rooted? If yes you can't install OTA updates
Click to expand...
Click to collapse
Not true. Root makes no difference.

efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
So either way I will lose all my settings, home screens and what not?
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?

efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
It's exact. But root can only be done if you have bootloader unlocked, and with unlocked bootloader can not install OTA updates

htc_woe_is_me said:
So either way I will lose all my settings, home screens and what not?
Click to expand...
Click to collapse
No, updating using an OTA update file will NOT make you lose anything.
htc_woe_is_me said:
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?
Click to expand...
Click to collapse
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.

efrant said:
No, updating using an OTA update file will NOT make you lose anything.
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.
Click to expand...
Click to collapse
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.

htc_woe_is_me said:
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.
Click to expand...
Click to collapse
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img

efrant said:
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?

htc_woe_is_me said:
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?
Click to expand...
Click to collapse
Gnex Toolkit wasn't working because of some missing file... re-installed it and flashed the stock recovery via Gnex Toolkit (I think). Is there a way to check which recovery is running? Anyway, if it is indeed stock, I just got prompted again for the OTA JB update.. it's installing now.... fingers crossed!!!
..OK so now it rebooted... started installing, got about halfway through.. paused, then it went to the stock recovery screen and stayed with a red triangle around an exclamation point! What is happening here?!
I have now re-locked the bootloader and received the prompt for OTA again....

Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app

htc_woe_is_me said:
Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Follow the instructions in the "update" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2

Guys i am having this EXACT problem, except on a S4 (I337M to be exact)
Here is my thread with the details
http://forums.androidcentral.com/as...t-update-ota-failure-using-triangle-away.html
But basically, im just wondering how i can get stock recovery back and get this ota to work!!!
Thanks!

please help (odin)

hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.

yashade2001 said:
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
Click to expand...
Click to collapse
why would you use odin? thats an awful hacker tool, leaked, no documentation, press one wrong button and your nexus is dead. google has made fastboot, use that to flash images. you find a tutorial in the galaxy nexus toolkit thread, you might aswell use that, though, it relies on fastboot and adb.

For people that came from samsung devices Odin is a very useful and the most comfortable tool. Fastboot is safer indeed but....sometimes u just don't want to write plenty commands in terminal when in Odin is just a one click.

gnextoolkit is one click aswell, its safe as milk, its clean, well documented and theres not much you can do wrong. dont harass poor nexus with odin. for all we know the guy could have just killed his phone, stuck at 12% doent sound so nice, hope it still came trhough.

Ok guys i repaired. From so diffcult way
Sent from my Galaxy Nexus using xda app-developers app

Yeah sure, if Odin fails then it's the time to use different means. I only use Odin when I want to perform a clean flash with full wipe. Otherwise (most of the time) I use fastboot. Toolkit goes very seldom.
EDIT: Great!!! How did you fix it?

molesarecoming said:
gnextoolkit is one click aswell, its safe as milk, its clean, well documented and theres not much you can do wrong. dont harass poor nexus with odin. for all we know the guy could have just killed his phone, stuck at 12% doent sound so nice, hope it still came trhough.
Click to expand...
Click to collapse
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum.
This will put him into the right path:
http://forum.xda-developers.com/showthread.php?t=1529058
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
yashade2001 said:
hello guys,
i flashed unroot file using odin for galaxy nexus gsm. its unrooted but the boot.img isnt changed. there is a unlock icon under the google logo.
then i change boot img file in odin pda tar file from a nexus factory image.
my problem is :
now i flashing changed tar file using odin but it paused in boot.img level.(around 12%)
can you help?
thx.
Click to expand...
Click to collapse
Boot.img have nothing to do with the padlock icon..
Padlock icon means unlocked bootloader.
fastboot oem lock to get rid of it.

Mach3.2 said:
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum.
This will put him into the right path:
http://forum.xda-developers.com/showthread.php?t=1529058
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Boot.img have nothing to do with the padlock icon..
Padlock icon means unlocked bootloader.
fastboot oem lock to get rid of it.
Click to expand...
Click to collapse
Thx very much.
Sent from my Galaxy Nexus using xda app-developers app

m.kochan10 said:
Yeah sure, if Odin fails then it's the time to use different means. I only use Odin when I want to perform a clean flash with full wipe. Otherwise (most of the time) I use fastboot. Toolkit goes very seldom.
EDIT: Great!!! How did you fix it?
Click to expand...
Click to collapse
Long story...
Sent from my Galaxy Nexus using xda app-developers app

yashade2001 said:
Long story...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This information can be useful for other users. U sure you don't wanna share it?

m.kochan10 said:
This information can be useful for other users. U sure you don't wanna share it?
Click to expand...
Click to collapse
Ok. İf you wanna know,
İ unpugged my phone. Then its bricked of course. And i unbricked this using linux. İ installed ubuntu to my computer. İ used terminal. But it isnt finished . İ have to use mac os x. For a program. İts command line osx. Then its unbricked and i flashed original rom with odin.
Sent from my Galaxy Nexus using xda app-developers app

Mach3.2 said:
Well, problems with toolkits is they run commands in sequence. Not to mention the user knows nothing and almost always ends up in the Q&A section asking for help because they get bootloops trying to flash a ROM/mod downloaded from what they think is a make my nexus kewl forum..
Click to expand...
Click to collapse
i have rather an established toolkit running official google components in sequence than a hacked/leaked samsung app that is neither documented nor known as to what it does and how it does it (and it will run stuff in sequence though). i own the s2 and know their forums, it is overfull of odin broke this odin broke that, pressed a wrong button phone dead, try jig here send it in for repair there. gnextoolkit is a great tool and the guy has put so much effort in it to keep it up to date and documented. every single thing he does there is laid out in the tutorial, fastboot commands aswell. i would recommend that tool to new users in a heartbeat.

I wouldn't exaggerate though. I owned Galaxy R, then S2 for more than year totally. I've never had one single issue with Odin (and I am a flashoholic ). Yes there were some instances when people messed around using it in a mindless way (or simply had bad luck...or Kies turned out to be a villain...) but the majority used it regularly without bigger problems. I'm not trying to say that Odin is perfectly safe...no no but if you follow the guide, have all required drivers installed (and Kies turned off) I don't see the reason why I should discourage users from running it.

odin
molesarecoming said:
i have rather an established toolkit running official google components in sequence than a hacked/leaked samsung app that is neither documented nor known as to what it does and how it does it (and it will run stuff in sequence though). i own the s2 and know their forums, it is overfull of odin broke this odin broke that, pressed a wrong button phone dead, try jig here send it in for repair there. gnextoolkit is a great tool and the guy has put so much effort in it to keep it up to date and documented. every single thing he does there is laid out in the tutorial, fastboot commands aswell. i would recommend that tool to new users in a heartbeat.
Click to expand...
Click to collapse
yeah, i perefer fastboot and gnex toolkit too but this time i hav to use odin.

use always odin and don't post if you will have problems.as molesarecoming sad you,fadtboot it's the way to go.odin works too,but fastboot is better,and don't say "fastboot has command to write,it's more difficult bla bla bla" all ****,there are not more than 5 commands to know for the major parts of operations.tools works withouyt commans,but i prefer manually because i know what i'm doing and i know if seomething goes wrong,at which type of command the phone was when occured the problem.

Galaxy Nexus 4.2 OTA ERROR

I received the update through the "Clear data" on the "Google Services Framework".
I downloaded the ota normally, but when the system enters in fastboot (the green robot with open belly) I get a red exclamation over it and the update don't finish, resulting in gnex to reboot and keep the 4.1.2 version.
That happened twice.
What is happening?
Sent from my Galaxy Nexus using xda app-developers app

Is this takju or yakju? Is there an error code?

It is JZ054k, and no, no error code. Just a red exclamation over the green droid and after some seconds the system reboots, entering in normal 4.1.2.
Sent from my Galaxy Nexus using xda app-developers app

shinayser said:
I received the update through the "Clear data" on the "Google Services Framework".
I downloaded the ota normally, but when the system enters in fastboot (the green robot with open belly) I get a red exclamation over it and the update don't finish, resulting in gnex to reboot and keep the 4.1.2 version.
That happened twice.
What is happening?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Dude seriously you need to get a log cat for anyone to help you so they can test the ota, you need to think before clicking install every time.
Sent from my Galaxy Nexus using xda premium

lol.. everyone that gets the yakju ota click install and then it cancels.. karma?

shinayser said:
It is JZ054k, and no, no error code. Just a red exclamation over the green droid and after some seconds the system reboots, entering in normal 4.1.2.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
that's stock recovery, not fastboot.
power down the device, then press power+vol up+vol down, until you see android on a rocket

galaxy nexus 4.2 error in update
im having the same problem. i try everything. my phone even unlock bootloader and rooted. i got ota update and at the time i didnt have clockwork mod recovery installed it rebooted but back to 4.1.2 and then i did google service framework move and still give me a error all i seen was code 7 or something. i update 4.2 so many time it wont let me do it. i even try to flash the zip 4.2 file and still dont work. i cant find nobody else with this problem idk why it wont let me download it. my last resort is backup files and wipe data and update but why would i have to do that for a ota update that stupid. please help because i want android 4.2.

Happened to me too.
Android version: 4.1.2
JZ054K

shinayser said:
I received the update through the "Clear data" on the "Google Services Framework".
I downloaded the ota normally, but when the system enters in fastboot (the green robot with open belly) I get a red exclamation over it and the update don't finish, resulting in gnex to reboot and keep the 4.1.2 version.
That happened twice.
What is happening?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
something on your phone isnt stock, thats why its failing.

Zepius said:
something on your phone isnt stock, thats why its failing.
Click to expand...
Click to collapse
Mine is. Running standard rom...

AntaeusDK said:
Mine is. Running standard rom...
Click to expand...
Click to collapse
what radio version are you using? you can find this out in settings > about phone

A thought.
Since I run the stock rom from Google, it finds out I do not live in america and fails? Because wallet does not work in denmark
---------- Post added at 05:21 PM ---------- Previous post was at 05:17 PM ----------
Zepius said:
what radio version are you using? you can find this out in settings > about phone
Click to expand...
Click to collapse
4.1.2
I9250XXLA2
3.0.31-g4f6d371
JZO54K

thats why. your radio isnt XXLF1

Zepius said:
thats why. your radio isnt XXLF1
Click to expand...
Click to collapse
Just tried googling, with not much info coming up.
What is the difference?

Same here with me.
Completely stock. XXLA2 4.1.2
Getting the update OTA, the 74MB update downloads, device restarts and shows that its updating but then Android with red exclamation mark. After a while it reboots and still on 4.1.2.
It's happened 3 times so far.

Zepius said:
thats why. your radio isnt XXLF1
Click to expand...
Click to collapse
This. This. This. This.
I have been fighting with my phone for hours thinking I had an issue with recovery or boot partitions. Thank you kindly. Any idea why my baseband was different than what it was supposed to be? I did convert my device from yakju to takju during Google I/O but I've had no update issues since.
4.2 OTA Installed! <3
To those of you having the same issue, do this:
Go here and get the radio image: http://forum.xda-developers.com/showpost.php?p=27984443&postcount=1097 (edit: Or you can pull it from the (JZO54K) factory image on Google's site (extract archive once downloaded to find it)).
Extract the .img from the .zip file, put it in the ADB directory (you'll need adb files or android SDK for this). I renamed it to radio.img for ease.
Boot into fastboot, and from adb console type "fastboot flash radio radio.img".
Now the OTA will install and all will be well in the world.

numberoneoppa said:
I have been fighting with my phone for hours thinking I had an issue with recovery or boot partitions. Thank you kindly. Any idea why my baseband was different than what it was supposed to be? I did convert my device from yakju to takju during Google I/O but I've had no update issues since.
Click to expand...
Click to collapse
when you converted, you didnt use the correct radio OR you never flashed it.
---------- Post added at 03:52 PM ---------- Previous post was at 03:52 PM ----------
sibyy said:
Same here with me.
Completely stock. XXLA2 4.1.2
Getting the update OTA, the 74MB update downloads, device restarts and shows that its updating but then Android with red exclamation mark. After a while it reboots and still on 4.1.2.
It's happened 3 times so far.
Click to expand...
Click to collapse
its because your radio isnt XXLF1. fastboot flash the xxlf1 radio and then try the update. bet it will work.

numberoneoppa said:
This. This. This. This.
I have been fighting with my phone for hours thinking I had an issue with recovery or boot partitions. Thank you kindly. Any idea why my baseband was different than what it was supposed to be? I did convert my device from yakju to takju during Google I/O but I've had no update issues since.
4.2 OTA Installed! <3
To those of you having the same issue, do this:
Go here and get the radio image: http://forum.xda-developers.com/showpost.php?p=27984443&postcount=1097
Extract the .img from the .zip file, put it in the ADB directory (you'll need adb files or android SDK for this). I renamed it to radio.img for ease.
Boot into fastboot, and from adb console type "fastboot flash radio radio.img".
Now the OTA will install and all will be well in the world.
Click to expand...
Click to collapse
Ok, now I have to get through the whole day at work before I can get home and try this!
Thanks!

Ota went fine for me on stock 4.1.2 factory image. Sounds like you changed something
Maguro Stock 4.2

I have the correct radio...it must think something else isn't stock.
What all does it look for? I unrooted...but still have clockworkmod installed. And still have unlocked boot loader.
What all needs to be "stock".
For the record..I didn't have this problem with the 4.1.2 otA update.