yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mwalt2:
I thought most people here would be able to extract an archive, find the images with radio in the file names inside of the archive, and type "fastboot flash radio radio.img" in a command prompt or put them in another flashable .zip created for flashing radios :). Personally, I like to get things directly from the source.

Interestingly, the MD5 of the LTE radio from the factory image is different from the patched version I pulled from my phone with the adb shell dd command. There are also no problems flashing the LTE radio from the factory image, where as it fails with the patched LTE radio pulled from my phone after the OTA update.
[Samsung Galaxy Nexus] mmedley:
Thanks for the tip. So far, that has helped tremendously for both signal and unlock latency. You rule.
[Samsung Galaxy Nexus] mark manning:
The md5s' should be different I thought? I am assuming your using pure stock which would mean your using the 4.0.2 radio with the 4.0.4 patch right? I might be wrong but that IMO would add up to different md5s'. As for the flashing problem you can't flash a patch from fastboot it has to be in a flashable zip. You can only write full radios from fastboot right?

Please correct me if I am wrong
[Samsung Galaxy Nexus] efrant:
Yes, only full images with fastboot, but when a radio is patched with an ota update to a different version, and you dump (and trim) it, it should generate the same md5
[Samsung Galaxy Nexus] mwalt2:
How do you trim the file? That's probably where the difference is coming from.
[Samsung Galaxy Nexus] adrynalyne:
We can't I don't think. GSM is a little different.

We flash two radios, but both are on the same partition.
[Samsung Galaxy Nexus] efrant:
When you dump anything with dd, it adds a bunch of zeros at the end. Open up you dump in a hex editor and delete everything after the last non-zero byte.

Oh. I wasn't aware of that.

So what are the names of all the partitions that show up in /dev/block/platform/omap/omap_hsmmc.0/by-name
[Samsung Galaxy Nexus] adrynalyne:
/system	ext4	/dev/block/platform/omap/omap_hsmmc.0/by-name/system

/cache	ext4	/dev/block/platform/omap/omap_hsmmc.0/by-name/cache

/data	ext4	/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata

/misc	emmc	/dev/block/platform/omap/omap_hsmmc.0/by-name/misc

/boot	emmc	/dev/block/platform/omap/omap_hsmmc.0/by-name/boot

/recovery	emmc	/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery

/sbl	emmc	/dev/block/platform/omap/omap_hsmmc.0/by-name/sbl

/xloader	emmc	/dev/block/platform/omap/omap_hsmmc.0/by-name/xloader

/radio	emmc	/dev/block/platform/omap/omap_hsmmc.0/by-name/radio
[Samsung Galaxy Nexus] oldblue910:
So you're saying that when you're in fastboot and you flash radio-cdma, then radio, they're both going to the same partition? That's funky. How do you dump the radios and separate them out?
[Samsung Galaxy Nexus] adrynalyne:
Yep, there is a specific order, and you can't.

You can dd out that partition, but I have no idea how you would succeed in using it.
[Samsung Galaxy Nexus] oldblue910:
Does this mean in Fastboot that you should flash one before the other? I know all the official Google packages have flash scripts and in those scripts, they always flash radio-cdma, then radio.

At least once I know I did it the other way around and had no problem though.
[Samsung Galaxy Nexus] adrynalyne:
Right.

The first is the LTE modem, and regular radio is the CDMA modem (I think). Flash LTE, then CDMA. Or maybe its the other way around. The radio flash that takes the longest is the CDMA one, and I believe thats the second flash.

Confused yet?

fastboot flash bootloader bootloader-toro-primela03.img

fastboot reboot-bootloader

sleep 5

fastboot flash radio radio-toro-i515.fc05.img

fastboot reboot-bootloader

sleep 5

fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img ??? typo in name :p

fastboot reboot-bootloader

sleep 5

fastboot -w update image-mysid-imm76k.zip
[Samsung Galaxy Nexus] oldblue910:
Considering that IMM76L is the latest OTA (for the Xoom), has JBQ tagged K or L in AOSP yet?
[Samsung Galaxy Nexus] efrant:
Is that all? On a GSM device, we also have dgs, efs, metadata and param, for a total of 13.

Are you sure there is a specific order to flash them. I don't think that it matters.

As for the dd, you could always dd the full image back in, i.e., you could flash both radios combined using dd.
[Samsung Galaxy Nexus] adrynalyne:
No, and he may not. The codebase may be the same as I. Plus the last time the Xoom got their first ICS OTA was for the wifi version, IML77 (4.0.3). It was never tagged.
[Samsung Galaxy Nexus] oldblue910:
I don't think it matters either. Some Google packages (like ITL41D) flash radio-cdma first, then radio. I've done it both ways in the past and have never had any radio issues.

Also, sad as it may be, now that we're past the one week mark with the IMM76K OTA release, and still absolutely nothing for IMM30B, I'm starting to wonder if it's going to show up at all.
[Samsung Galaxy Nexus] adrynalyne:
I've always been told there is a specific order or you lose LTE. Could be a myth, I've never desired to tempt fate with radios.

That said, I watched folks in the Sprint IRC channel when it first released panic because they had flashed Verizon radios. Even a full dd they couldn't seem to do better than getting CDMA back, and that was it.
[Samsung Galaxy Nexus] oldblue910:
That's true, yeah. There may just be some small device-specific stuff in K or L. Who knows. haha
[Samsung Galaxy Nexus] adrynalyne:
One way to find out.

http://www.twitlonger.com/show/hoi391
[Samsung Galaxy Nexus] oldblue910:
He'd certainly be the right guy to ask! ;)
[Samsung Galaxy Nexus] adrynalyne:
Actually, he did tag them.
[Samsung Galaxy Nexus] oldblue910:
K and L both?
[Samsung Galaxy Nexus] adrynalyne:
Yeah. Pushed it yesterday.
[Samsung Galaxy Nexus] spencer88:
There are some instructions online on how to flash back to stock. It didn't explicitly say "do it in this order or else" but it had the lte radios first and then the cdma radios which take a long time to flash. I'll have to find the link. It may have been on Droid life.
[Samsung Galaxy Nexus] adrynalyne:
I just do the flash-all thang.

It lists LTE first as well.
[Samsung Galaxy Nexus] efrant:
In the guide I wrote here, I have put flashing the CDMA radio first (radio), then the LTE radio (radio-cdma) after. Everyone who has used it on Verizon has not had any issues (that I am aware of).
[Samsung Galaxy Nexus] spencer88:
I'm sure the order doesn't matter. If it did you'd think it would be posted somewhere about the consequences of flashing them in the wrong order.
[Samsung Galaxy Nexus] adrynalyne:
Rumor it is, then. Like I said, I don't tempt fate when it comes to radios. I follow the standard methods like a good little boy :p
[Samsung Galaxy Nexus] Zepius:
weirdo
[Samsung Galaxy Nexus] adrynalyne:
I've been witness to hard bricks with radios (not on this device) ;) Makes ya a little skittish.
[Samsung Galaxy Nexus] Zepius:
Thunderbolt right?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] adrynalyne:
To update ya, I didn't check the differences between I and K, but I did I and L, which includes changes from K.

It is Moto Xoom device tree changes (nothing worth mentioning) and Gallery updates.

That is the entire difference between I and K and L.
[Samsung Galaxy Nexus] adrynalyne:
Dinc.

There is a radio patch that hard bricks it (won't ever turn on, ever again). I have it on 4shared still I think :D
[Samsung Galaxy Nexus] efrant:
LOL! Just in case you ever need it, right?
[Samsung Galaxy Nexus] Zepius:
I think he keeps it because he hates everyone

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] adrynalyne:
Exactly!

LMAO.
[Samsung Galaxy Nexus] efrant:
That's why in his 4shared, he named the file name is restore-to-stock.zip
[Samsung Galaxy Nexus] Zepius:
Like a boss

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] oldblue910:
HAHAHAHAHAHA You, sir, win the Internets for a day.

---------- Post added at 01:05 PM ---------- Previous post was at 01:04 PM ----------

I hope this patch wasn't originally included in an OTA...
[Samsung Galaxy Nexus] adrynalyne:
It was, but for a different device. Sprint yanked it pretty quick (Evo 4G). Verizon tested and failed it.
[Samsung Galaxy Nexus] oldblue910:
I would hope they failed it! So what, do the Evo 4G and Thunderbolt have compatible radio firmware?
[Samsung Galaxy Nexus] adrynalyne:
Yeah. They use the same radios.

Certain things like the provisioning menu and such won't work, but the main functions do.
[Samsung Galaxy Nexus] oldblue910:
That seems odd to me considering the Evo 4G has a WiMax radio and the Thunderbolt has an LTE radio...so obviously it's just the CDMA radios that are the same? It doesn't matter that Sprint and Verizon use different frequencies for CDMA? And I guess that also means that the OTA patch bricked both devices and not just the Thunderbolt?
[Samsung Galaxy Nexus] adrynalyne:
I was talking about the Droid Incredible (check back :p)

And we never used the WIMAX radio.
[Samsung Galaxy Nexus] oldblue910:
Oh whoops...ok Dinc. Got it. It's interesting that HTC writes radio firmware that works across devices that use multiple frequencies. The T-Mobile and AT&T Nexus One devices used the same radios as well. I wonder why Samsung and Motorola don't do that. Seems like it'd save development effort.
[Samsung Galaxy Nexus] fix-this!:
-61? jesus i never dropped below 100. :mad:
[Samsung Galaxy Nexus] spencer88:
I have never dropped below -80. Full 3G or full 4G bars.
[Samsung Galaxy Nexus] adrynalyne:
I live on a cell tower, so its to be expected :D
[Samsung Galaxy Nexus] Zepius:
the microwave exposure explain your craziness.
[Samsung Galaxy Nexus] adrynalyne:
Definitely. But the important things still work, according to my wife.

From my front door (no zoom):
[Samsung Galaxy Nexus] Zepius:
yeah if you didnt have near perfect signal, id begin to wonder.

now remember your tin foil hat to protect you
[Samsung Galaxy Nexus] 3devious:
I think his wife probably *would* complain if he put tinfoil on it! :eek:
[Samsung Galaxy Nexus] adrynalyne:
Of course not. They do not know until the support pdf is updated.
[Samsung Galaxy Nexus] axne1:
Lol:D

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] dmmarck:
Same here. Called and talked to a rep; no dice, mentioned something about ICL53F and pressing *228 and hitting option 2. Neither of which I'm doing.
[Samsung Galaxy Nexus] adrynalyne:
Oh lord. Yeah, NOBODY do that. Idiot techs.
[Samsung Galaxy Nexus] bostonbassman78:
Oh damn all my bad all i seen was possible vzw update to 4.0.4 sorry new to using forums lol btw the razr is beast js
[Samsung Galaxy Nexus] spencer88:
Thanks. I knew those were there but can those be flashed in recovery?
[Samsung Galaxy Nexus] miketoasty:
Posted on Droid-Life. Shop or not?
[Samsung Galaxy Nexus] adrynalyne:
No, fastboot only.
[Samsung Galaxy Nexus] hawkye:
Just use the toolkit.

http://xdaforums.com/showthread.php?t=1392310
[Samsung Galaxy Nexus] dmmarck:
Is that the PapaDroid post?

http://phandroid.com/2012/05/01/verizon-galaxy-nexus-receiving-android-4-0-4/

Can't seem to expand the image on my work compy.
[Samsung Galaxy Nexus] mwalt2:
I already posted the link direct from google in this thread. Mikeyxda also posted instructions (which are also in the archive you download the factory images in).

Here it is again, at the bottom of the page:

https://developers.google.com/android/nexus/images

It will erase everything on your phone if you do the -w argument with fastboot flash.
[Samsung Galaxy Nexus] adrynalyne:
Probably real. Too many different sources in it to be a rickroll.

Sadly, unless they capture the URL...
[Samsung Galaxy Nexus] spencer88:
There's a .zip inside the .tgz. Is that flashable or no? I've always used just .zip files in recovery and used ODIN files.
[Samsung Galaxy Nexus] efrant:
No, that zip is not flashable in recovery.

But the system and boot images should be able to be repackaged in a CWM-flashable format.

I've done it for a maguro device, but not for a toro (as I don't own one). I can post the zip if you want, and you can try dropping in the system and boot images from the zip you just mentioned. No guarantees it will work though.
[Samsung Galaxy Nexus] TeeRom:
Is stock recovery required to actually go through with the update?
[Samsung Galaxy Nexus] mwalt2:
If you want to be stock, the easiest way is to use fastboot. You can't flash a .zip from the stock recovery, and you'll need the stock recovery if you want to be stock :).

Didn't everyone use fastboot to put a custom recovery on their phone? Oh wait, toolkits...;)
[Samsung Galaxy Nexus] efrant:
To have it install OTA, yes. Once we have the link, no -- CWM will work just fine.
[Samsung Galaxy Nexus] krazie1:
So all the people if not Devs if you see the update window pop up on your phone you should stop there and post here on what to do to try and get the download location. That'd be very helpful and greatly appreciated.
[Samsung Galaxy Nexus] tat2messiah:
What is this link to?
[Samsung Galaxy Nexus] spencer88:
I did use fastboot to flash my recovery.
[Samsung Galaxy Nexus] mwalt2:
That should make it easy if you really want to restore to stock then. It's pretty much the same thing, only it'll wipe your phone if you include the -w when flashing the .zip from fastboot.

I wasn't directing my comment at you or anyone in particular. It was more just a lame attempt at being sarcastic because I think sometimes it would be better if everyone understood more how things work.

Has anyone else gotten the update? I sadly didn't upon restoring to 4.0.2.
[Samsung Galaxy Nexus] spencer88:
OK I understand what you were saying. I'm just not wanting to revert completely to stock, just the stock ROM so I can check for the update and possibly capture the URL and the files that it downloads. That's all.
[Samsung Galaxy Nexus] Wingman520:
that's what i am now... stock with root and logcat running waiting to pull the file
[Samsung Galaxy Nexus] spencer88:
Well I guess nvm then. You beat me to it.
[Samsung Galaxy Nexus] digweed4me:
You ppl gonna love this 4.04 update amazing batt life and no los issue. As soon as i got my gsm nexus from google play turn the phone on wallah there was an update waiting for me.
[Samsung Galaxy Nexus] adrynalyne:
Verizon is not GSM. We don't want IMM76I. We want the new update for radios ;)
[Samsung Galaxy Nexus] patt2k:
We were on 4.0.4 before sprint had GNEX.
[Samsung Galaxy Nexus] spencer88:
Yes. Fixed radios would be awesome.
[Samsung Galaxy Nexus] BlackHoleSlam:
Agreed can't wait

for me, by me and I love you
[Samsung Galaxy Nexus] thenamesian:
does 4.0.4 fix the SMS app's issues?

saving "drafts" after deciding to not send them and repeatedly trying to delete them? they still show up...

having me press the back button 5,000 times to get back to the SMS app to send a text?

i am seriously more interested in bugfixes than new radios... and no, i'm not rooting yet. just want to know if those issues are fixed in 4.0.4
[Samsung Galaxy Nexus] axne1:
Nothing?

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] krazie1:
I just fastbooted to stock 4.0.2, stock recovery and locked bootloader. Keep checking for update but nothing here in California.
[Samsung Galaxy Nexus] martonikaj:
Shouldn't have relocked the bootloader. Has nothing to do with your ability to receive or apply OTA, but now you're going to wipe the phone to unlock it again.
[Samsung Galaxy Nexus] calamity:
I'm going to have to have a galaxy nexus to get the update?

Jk omg people your phone has to be completely stock.

Not rooted.

make your phone the way it was when you first bought it.

Stock recovery

Stock bootloader

Stock ROM 4.0.2

Not rooted
[Samsung Galaxy Nexus] miketoasty:
Or just use superboot.img, as you need to be rooted to get the update off of the phone.
[Samsung Galaxy Nexus] efrant:
NO. Not true. You CAN have a rooted stock ROM, and you can have an unlocked bootloader, and the OTA update will still work.
[Samsung Galaxy Nexus] krazie1:
Didn't know that but hey i'll just unlock it again right now. Thanks for the info. I installed a logcat app to see if the update shows up i'll have it logged.
[Samsung Galaxy Nexus] efrant:
You should also be able to look at the log files in /cache/recovery. The update name should appear in there.
[Samsung Galaxy Nexus] slickrickstyles:
finally...cant wait to get these radios the service in my area has been horrid...2 bars max on 3g
[Samsung Galaxy Nexus] martonikaj:
Compared to other VZW devices? The new radios aren't going to install new towers near your house :p
[Samsung Galaxy Nexus] slickrickstyles:
Also here is an image I found on another forum from a guy named scotts1474 who states that he found this at a Local Verizon store this afternoon on one of the display devices.

Uploaded with ImageShack.us

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

haha no my droid x never had an issue...i still only get 2 running Milestone 5 and the previous leaked radios
[Samsung Galaxy Nexus] krazie1:
Can the people seeing the updates on the phones instores just try and get the file location on that phone?
[Samsung Galaxy Nexus] dmmarck:
Shhhh, you don't know that!
[Samsung Galaxy Nexus] forsaken82:
im hoping it fixes my signal issues too. my bionic got better signal that my gnex even before the fixes to make the bionic work right. i had almost full 4g at my house and i only get 1-2 bars of 3g if that on the nexus. im rather annoyed at that fact
[Samsung Galaxy Nexus] hawkye:
I am in the same boat. At work I used to get a decent 4G signal with my Bionic and now I barely get a 3G signal with my GNex.
[Samsung Galaxy Nexus] adrynalyne:
Methinks store reps might be more than a little curious if someone hooks up their display devices to a laptop....
[Samsung Galaxy Nexus] krazie1:
Oh you need a laptop to get the file location. I thought it'd work if just installing a logcat and going from there. I never did a file pull so idk how it works.
[Samsung Galaxy Nexus] miketoasty:
Nah, just tell them you are testing out the transfer speeds. Lolololol.
[Samsung Galaxy Nexus] adrynalyne:
I suppose you could try with an app...
[Samsung Galaxy Nexus] imnuts:
Technically, you should be able to get the update by restoring the stock build.prop and having the update function enabled on the ROM correct? I thought that it only looked at the build.prop stuff to see if you need an update, then worried about the rest later. Would be much easier than flashing back to stock completely when all we really want is a file and/or url.
[Samsung Galaxy Nexus] adrynalyne:
I suppose, but in my case I had all that stuff either missing or disabled. So I had to go back.
[Samsung Galaxy Nexus] axne1:
Are we sure this isn't the sprint update. They are supposed to be receiving updates for the next few days. I want something that says verizon now nobody's been able to receive an update after restoring stock. I want verizon proof!

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] adrynalyne:
LOL....
[Samsung Galaxy Nexus] axne1:
Oops it says it right on the damn screen!! Lol.

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] axne1:
:D:confused: lol

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] krazie1:
So just to make sure if i were to go to a store and see the update and install catlog or alogcat what would i be looking for in the logcat?
[Samsung Galaxy Nexus] efrant:
To be even more specific, it checks the ro.build.fingerprint line in your build.prop file and that's it.
[Samsung Galaxy Nexus] winner00:
You would cancel it. Install alogcat and start the update again but don't click install and restart. You would be looking for a address or a file location.
[Samsung Galaxy Nexus] efrant:
Search for something ending in .zip
[Samsung Galaxy Nexus] krazie1:
OKay so i'd be looking for a url address and a file ending in .zip? Imma go to a store in 30min - 1hour.
[Samsung Galaxy Nexus] efrant:
No, not a URL. Look at this example from a GSM update:

V/SystemUpdateService( 546): onStartCommand: launching task

V/SystemUpdateService( 546): UpdateTask.doInBackground

I/SystemUpdateService( 546): download in progress: [id: 6 compl: true succ: true bytes: 195101582 reason: 0 fn: /cache/0ce2bc924e74.update_yakjuux_IMM48.zip]

I/SystemUpdateService( 546): verification is successful

I/SystemUpdateService( 546): OTA package size = 195101582

I/SystemUpdateService( 546): sIsActivityUp = false
​
[Samsung Galaxy Nexus] jkc120:
So all we have to do is hack the build.prop and even if we're on say AOKP we could potentially capture the url at least? I'm willing to modify my build.prop to possible catch the OTA as long as it doesn't have any negative side effects.
[Samsung Galaxy Nexus] slickrickstyles:
Yeah I would run it then take a picture of it with your phone...Maybe that would look less suspicious then writing the information down lol
[Samsung Galaxy Nexus] efrant:
Assuming that AOKP (which I've never used) doesn't have any service running that kills update notification, yes, all you have to do is make sure that the ro.build.fingerprint line matches the one in a stock 4.0.2 ROM. (But obviously this doesn't mean you will get the update immediately, just that you will get it.)

No negative side effects at all (but back up your current one before obviously).
[Samsung Galaxy Nexus] DroidRC1:
What is the exact ro.build.fingerprint for 4.0.2 stock?

follow me @DroidRC1
[Samsung Galaxy Nexus] efrant:
I have no idea. Maybe someone running 4.0.2 could help out?
[Samsung Galaxy Nexus] DroidRC1:
Mine says

google/mysid/toro:4.0.2/ICL53F/235179:user/release-keys

And I'm on 4.0.4 AOKP

follow me @DroidRC1
[Samsung Galaxy Nexus] efrant:
That does look like the right one. Make sure that there is no service like FOTAKill running in the background as well.
[Samsung Galaxy Nexus] krazie1:
Theres a system dump on droid life im downloading now to see if its the full package with radios.
[Samsung Galaxy Nexus] winner00:
It won't be. Radios are separate from system.
[Samsung Galaxy Nexus] krazie1:
Your right, its just the rom. I checked the build.prop and this is what i see

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=IMM76K

ro.build.display.id=IMM76K

ro.build.version.incremental=336647

ro.build.version.sdk=15

ro.build.version.codename=REL

ro.build.version.release=4.0.4

ro.build.date=Fri Apr 20 17:22:24 PDT 2012
[Samsung Galaxy Nexus] K.AuthoR:
A system dump will not contain radios. They're stored separately.
[Samsung Galaxy Nexus] cky2000:
Yes, that is the right fingerprint for 4.0.2. Looking at it right now :D
[Samsung Galaxy Nexus] DroidRC1:
But its my fingerprint right now running AOKP milestone 5 which is 4.0.4

follow me @DroidRC1
[Samsung Galaxy Nexus] efrant:
So? That doesn't mean anything. AOKP is not an official build, and whoever built the version you are running left it as the fingerprint from ICL53F.
[Samsung Galaxy Nexus] DroidRC1:
Okay I was just alil confessed why it said that while on 4.0.4

follow me @DroidRC1
[Samsung Galaxy Nexus] cky2000:
I just went back to total stock 4.0.2 and that's what the fingerprint says.
[Samsung Galaxy Nexus] JRJ442:
I think I read somewhere that the fingerprint has to remain whatever the official current ota is for the market to work correctly. AOKP is 4.0.4, but the fingerprint has to say whatever the current official build is. It checks it or something. I could be wrong though. I'm pretty sure every rom out says that in the fingerprint
[Samsung Galaxy Nexus] DroidRC1:
That makes a lot of sense

follow me @DroidRC1
[Samsung Galaxy Nexus] Turb0wned:
So I decided to go back to 4.0.2 to see if I see an update and try to help out. Can someone explain to me how is it that (I'm still on leaked 4.0.4 radios) I now get 4G where Ive currently at for the last 4 months? It has been on in the settings with all my custom roms.....
[Samsung Galaxy Nexus] axne1:
Because your radios stay until use flash stock radios

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] kangxi:
If he flashed the stock 4.0.2 image, the radios are included.
[Samsung Galaxy Nexus] krazie1:
I came and look what I see. :)