yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dawiseguy77:
Hello sir! I would like to say that first I was reading that your kernel has been known to work on a cdma version of the Gnex. It got me curious, so I tried it, and it is running very well actually. Only thing I've noticed is that when the screen dims it has a green tint tint to it. I have adjusted my colors to my liking using CDMA AOKP b28 not sure if is the ROM,or kernel. Not a huge deal. Anyway just wanted to say thanks so far so good. Have you thought about posting in the CDMA. Section? I'm sure you would people more than willing to test for you.

The Taco Cowboy rides again!
[Samsung Galaxy Nexus] Kelvino9:
r190 seems stable to me. Used in on Baseband XXKL1 and UIKL3 in 2G/3G and on Wifi. No crashes or battery drains. Every app I already had installed and tested worked fine. r190 is stable for me.
[Samsung Galaxy Nexus] beekay201:
i also experienced this green tint. tweaked colors a bit more (cm9 color tweaking) and it now looks awesome. no more green tint when screen dims.
[Samsung Galaxy Nexus] Macke93:
Just downloaded #190, going to flash it know! :-)
[Samsung Galaxy Nexus] manager77:
Nika..there is any chance to ad to your kernel 2 way recording module? Thanks!
[Samsung Galaxy Nexus] Flukester69:
OK I think a new problem with 190. I am getting frequent 'this application stopped do you want t report? Again never had these with previous Roms. Happens with games and some apparently like mail when I say combined view.
[Samsung Galaxy Nexus] beekay201:
Name a few.

Also you say previous roms.. You probably mean kernels?
[Samsung Galaxy Nexus] Sdobron:
Try a fix permissions
[Samsung Galaxy Nexus] Flukester69:
Stock email, camera zoom I even rebooted also I am on 181 again with no probably now. Replaced stock email with k9 when I was on 190 and it resolved it. Also experienced odd slow Downs.
[Samsung Galaxy Nexus] renaud:
The fact it works with 181 is strange because this really looks like a ROM problem, like messed permissions or corrupted data. I would really try to wipe first.
[Samsung Galaxy Nexus] Drift spunk:
So this will work on MIUI?
[Samsung Galaxy Nexus] renaud:
r194 is on 3.0.26
[Samsung Galaxy Nexus] odin13:
Sweet :) any changes worth mentioning?

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] renaud:
There is mainly a change in ipv6 multicast, that's about it
[Samsung Galaxy Nexus] kizaros2g:
hi nika, rite now im in the dilemma in rom, any rom that you suggest? basically, of course im using your kernel, rite now im using 190 :)
[Samsung Galaxy Nexus] renaud:
Personally, I use CM9 nightly.

I used liquidsmooth for a small time, but there were too much bugs for my taste.
[Samsung Galaxy Nexus] kizaros2g:
so it is compatible for cm9? i thought it is not. thanks!

---------- Post added at 12:38 PM ---------- Previous post was at 12:21 PM ----------
[Samsung Galaxy Nexus] renaud:
Yes, it is compatible with CM9, I added that in the OP
[Samsung Galaxy Nexus] ludow:
Hi!

193 is unstable for me. When sending and receiving data, I get sudden BSOD.

I have to remove battery.

190 is fine.
[Samsung Galaxy Nexus] bleomycin:
I just got a sleep of death as well with 193, first one in a very long time, also had to cycle airplane mode earlier because i lost cellular data. Didn't have any issues with 190. Sorry i can't be of more help.
[Samsung Galaxy Nexus] renaud:
which ROMs are you using?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bleomycin:
AOKP Milestone 4
[Samsung Galaxy Nexus] beekay201:
reporting back: #190, 4 days 22h no reboots (more than one charge though :p ofc), been using wifi, data call, voice call, lock/unlock, adb, tethering to tf201, no issues. i'd say it's time to update to 3.0.26.

/rant

an adb client for android would totally rock though, from tf201 to the nexus, with adb over network from cm9, that would awesome ;)
[Samsung Galaxy Nexus] renaud:
Please try r195

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zurchpet:
if you want, you can build it yourself: http://stackoverflow.com/questions/5904765/build-android-adb-for-arm-processor
[Samsung Galaxy Nexus] zurchpet:
2 days 4 hours and 4 minutes on R190

Hi guys.

just wanted to share some screenshots: Picture Album

I know 1h and 23 minutes screen on time is rather low usage.

But you can also see it was almost 12 hours awake :)

also the charging bump you can see happend on sunday night.

I automatically, by reflex, just plugged it in, and after 20 minutes remembered that I wanted to test how far I can go with it.

Timeframe:

Saturday 10:00ish to Monday 16:00ish

> 50 hours. not bad IMO :)

Notice: I was at home over the weekend (so mostly wifi) cause I had some wisdom tooth removed.

Battery was at 50 % when I arrived at work on monday morning at 8.

but the noisy wifi at work ate the battery :)
[Samsung Galaxy Nexus] Gregus59:
195 good for me...
[Samsung Galaxy Nexus] renaud:
It seems wifi driver v6 is not ready for 3.0 yet. We may also need a newer firmware.
[Samsung Galaxy Nexus] renaud:
Given that nobody complains about r195, I think I can safely conclude it solves the issues with 193.
[Samsung Galaxy Nexus] rafael-as:
Hi guys.

I'm with drop signal issue and I guess I'm not with the recommended bootloader. Now a noob question. Where I can find the Primekk1 ? Can I flash it using CWM?

Tks
[Samsung Galaxy Nexus] franciscofranco:
All you need is in the OP.
[Samsung Galaxy Nexus] beekay201:
that's your apps not the kernel

#61

stepped up to #62.
[Samsung Galaxy Nexus] renaud:
Did you find something?
[Samsung Galaxy Nexus] zurchpet:
R63 works well...

Latest CM9 kang by fitsnugly seems to have made the compass work erratic... not a kernel issue.... tested it also with other kernels...
[Samsung Galaxy Nexus] slyydrr:
Sorry that you feel that way but I disagree 100%.

All my testing has been on a clean install with no changes in apps and only changes in kernels. W/ a 3.0.16 kernel (by franco for example), I get minimal idle drain but connection drops. With this 3.0.17 kernel, I get a much more noticeable idle drain but no connection drops. Obviously I prefer the second scenario but with 4.0.2 I can get the best of both worlds: no connection drops, minimal idle drain.

The screenshot you showed to me actually supports my argument. About 2% battery drop per hour while doing nothing on the phone, having perfect connection and seemingly having data turned off is what I would consider a higher idle drain. If you'd like I could setup your scenario with another kernel and show you that in that time frame (5.5 hours), I would experience maybe a 2-3% total drop in battery life.

All that being said - I have high hopes for this kernel and continue to use it as maintaining a constant connection is more important than battery life to me for now.

---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------

Unfortunately no :( I have been trying to give each kernel a fair share of time and am on r56 right now but still seeing the same results. If you'd like to me to document some comparison graphs for your kernel vs. a 3.0.16 kernel I can to show you a relative comparison. Please let me know if you'd like me to do so.

I am going to jump up to r63 however and give that a try as well.

---------- Post added at 11:51 AM ---------- Previous post was at 11:12 AM ----------

FYI, my plan today (assuming work doesn't get in the way) is to swap through a few different kernels to show comparisons within a single battery graph. Right now I have r56 and r63 on there. I'm going to spend another couple hours with r63, then try r64, and then try franco's kernel and it should give a good comparison I'd think as to the basis for my claim of higher idle drain.

Also, nikademus, I'd be more than happy to continue helping you test out various releases as I know having a constant test scenario helps determine if the situation improves with any patches so let me know if you'd like my assistance.
[Samsung Galaxy Nexus] beekay201:
Yes, there is a higher idle drain than other kernels. But I was referring to awake time and wake locks. My device didn't wake up at all, and you said your device kept waking up in somewhat regular time intervals, and that's why I was saying that it was due to apps, not the kernel.

Obviously, I use the same principals when testing - same rom, no change in apps.

Had a data call drop today, #62+codeworkx latest cm9 kang.

Switched to my aosp build, which I know it does not cause data call+connection drop. Added #62.
[Samsung Galaxy Nexus] slyydrr:
Ahh, good point. I forgot about my comment regarding the random awake time and your screenshot definitely shows none. Thanks for pointing that out. I'll have to revisit that portion to see what was causing that for me.
[Samsung Galaxy Nexus] renaud:
I have built an AOSP/master release if someone wants to try:

https://faramir.eriador.org/r/maguro/full_maguro-ota-eng.zip

EDIT:

- it requires gapps to be flashed

- it does not come with fugumod kernel

- it has no su

- it doesn't have cwm

- you may need to wipe

which means, when you flash, don't forget to flash at least gapps and su afterwards
[Samsung Galaxy Nexus] slyydrr:
Great, I may have to give this a try - assuming this still requires the separate gapps package? If so, any specific one? The one I've been using is gapps-011312.
[Samsung Galaxy Nexus] renaud:
Yes, it needs gapps and you may even need to wipe
[Samsung Galaxy Nexus] renaud:
The AOSP/master build now has all drivers, so everything works.

Version is 4.0.3.0.2.1.0

EDIT: location has changed, consult 1st post
[Samsung Galaxy Nexus] slyydrr:
Hmmm got a data drop w/ this ROM and pretty quickly too... I will continue testing for the remainder of the day with the stock kernel to see if it's a common thing or just a fluke. If all goes well, I'll revert to your kernel and see how that goes for drain.

EDIT: Okay, sadly wasn't a fluke - I might just end up reverted to 4.0.2 for now because I'm having endless issues w/ 4.0.3 :(

---------- Post added at 11:04 AM ---------- Previous post was at 11:03 AM ----------

What AOSP build are you using?
[Samsung Galaxy Nexus] renaud:
It seems heap randomization is one of the points draining battery.

As far as I have been able to see, it wasn't enabled in 4.0.2 and is in 4.0.3.

You can disable it by doing:

echo 0 > /proc/sys/kernel/randomize_va_space

By doing this, you are removing one of the security features to get more battery life, so chose which one is more important for you.
[Samsung Galaxy Nexus] renaud:
My commit 022339db11064c7ce9053648656e58e704072bc2 made the kernel not vulnerable to CVE-2012-0056
[Samsung Galaxy Nexus] franciscofranco:
Good find. I'll take a look on the battery life with it disabled. Thanks.
[Samsung Galaxy Nexus] zurchpet:
Yeah :)

R67 runs with fitsnuglys latest kang.

FuguMod has been adapted to the latest changes of CM9 I see :D
[Samsung Galaxy Nexus] renaud:
And r69 is 3.0.18 based and supports CM9 color settings
[Samsung Galaxy Nexus] manager77:
r69 seems to be very good to me(stability,speed)...only problem is idle drain....3-4%/hour...with IMO's 1.7.3 kernel l've got 1% every 4h...
[Samsung Galaxy Nexus] renaud:
I am still trying to understand this drain as it doesn't happen for everyone

Sent from a Nexus
[Samsung Galaxy Nexus] manager77:
l'm on AKOP#21...same settings,same place.. test it for 4h ...with IOM's 1% and with r69 17%...it's a huge difference!
[Samsung Galaxy Nexus] franciscofranco:
Did you revert the usb pm patch from 3.0.17? It breaks usb power management I think. I had to revert it, otherwise boom, battery went to ****.
[Samsung Galaxy Nexus] rafael-as:
I'm sorry but What is OP?
[Samsung Galaxy Nexus] franciscofranco:
Original post.
[Samsung Galaxy Nexus] zurchpet:
as Francisco said. Original Post or Opening Post. First post of the thread.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] rafael-as:
Tks.

If I undertood I can only flash bootloader with flashboot. I'll flash it later to try to solve drop signal issue. In my case fugumod is the only kernel working at 350-384mhz.

I guess 700 is best choice for me, but i want to fix it
[Samsung Galaxy Nexus] renaud:
For those wishing to test, I have built 4.0.4:

https://faramir.eriador.org/r/full-maguro-ota-en.4.0.4.zip

See full xda thread: http://xdaforums.com/showthread.php?t=1570495

4.0.3 kernels are compatible with it.

A wipe should not be needed, but you will have to root it.
[Samsung Galaxy Nexus] renaud:
As far as I have been able to see, yes, it should work on MIUI
[Samsung Galaxy Nexus] Gregus59:
Hi Nika, I have a question, is your kernel support OTG? I bought a micro usb stick, when I plug it, I can't see it in root explorer, but the led of the stick is on, and if I can unplug it, I have the notification card unplugged... :(
[Samsung Galaxy Nexus] renaud:
Yes, it does, but the ROM must support it too.
[Samsung Galaxy Nexus] Gregus59:
I installed StickMount, I can mount my usbstick, I see it in sdcard/usbstorage/sda1, but when it unmount it, unplugged it, I have the notification usb memory storage unplugged and I don't have access on the internal sdcard...

The dev of the app say it is a kernel problem?
[Samsung Galaxy Nexus] renaud:
Maybe the dev of the app can point me to a patch then. Unfortunately, this is not something I can test as I don't have the cable needed.
[Samsung Galaxy Nexus] Gregus59:
His name is Chainfire on XDA, the app is StickMount 1.3 ;)
[Samsung Galaxy Nexus] renaud:
Look at this one: http://xdaforums.com/showpost.php?p=24040652&postcount=174
[Samsung Galaxy Nexus] Gregus59:
That's solved the problem, thanks very much Nika :-)
[Samsung Galaxy Nexus] mekanismen:
That is a ROM-issue and the fix that Nika linked to is supposed to be included in AOKP B29 which will be released today. :)
[Samsung Galaxy Nexus] Gregus59:
It's solved on the last CM9 with 4.0.4 merged.... :D
[Samsung Galaxy Nexus] Gregus59:
Hi Nika, did you build a kernel for 4.0.4 ?
[Samsung Galaxy Nexus] renaud:
Of course, the 4.0.3 version works just fine on 4.0.4
[Samsung Galaxy Nexus] jake2k1:
Kernel #200 reboots the phone using wifi hotspot with aokp #29.

Reverting to #190 which does not have the issue.
[Samsung Galaxy Nexus] renaud:
Use 201, it solves this issue

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mennozon:
confirmed, 201 fixes wifi AP panic
[Samsung Galaxy Nexus] Gregus59:
Hi Nika, go here :

http://xdaforums.com/showthread.php?t=1571715

Bootloader and new radio just on top... I flash all and I am an happy man now... Lol... ;)
[Samsung Galaxy Nexus] renaud:
They are on my repo for days now :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mekanismen:
I guess this doesn't really belong here, but can I flash the 4.0.4 bootloader and radio if I'm on AOKP b28 which is based on 4.0.3?

Flashing b201 now as I by mistake pressed the toggle for AP and therefore experienced the reboot issue. :)

Edit: It was safe to flash them both on 4.0.3 apparently!
[Samsung Galaxy Nexus] Kelvino9:
Sure you can. had the bootloader on my GNEX since the early leak in February and the XXLA2 since official release. Everything fine so far.
[Samsung Galaxy Nexus] renaud:
Today is a good day to announce r202 which is based on Linux 3.3 kernel

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] odin13:
Is it based on 4.0.4 source?

*guess not...on your site it says r202-4.0.3...will you create one based on 4.0.4 source?

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] neopbm:
Hi,

I am a bit confuse, there seems to be 2 version of this kernel. For 4.0.3 and 4.0.4.

But the one for 4.0.4 is still mentioned 4.0.3 in the filename (http://fugumod.org/galaxy_nexus/stable-4.0.4/kernel_FuguMod_20120331_r201-4.0.3.zip)

Am I missing something ?

Thanks
[Samsung Galaxy Nexus] renaud:
They are the same, the same kernel runs on both versions.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] neopbm:
Ok ok thanks ;)
[Samsung Galaxy Nexus] odin13:
Nika,

Are you planning on building a 4.0.4 source based kernel?

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] renaud:
Use r202

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
r203 features linux 3.0.27-rc1
[Samsung Galaxy Nexus] zurchpet:
Here is the list of patches included in 3.0.27-rc1.
[Samsung Galaxy Nexus] Treatcon:
Been using this kernel since it was beta with LiquidSmooth 1.25 and man is it nice! No problems with great battery life! Good shizzz!! :cool:
[Samsung Galaxy Nexus] renaud:
R204 has 3.0.27 final

R205, some wifi fixes

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] blair287:
Does this kernel support OC and does it sort out the signal dropping out when going into standby

flashing this makes hotspot stop working.
[Samsung Galaxy Nexus] zurchpet:
R205

Just wanted to report.

No issues with R205 :)
[Samsung Galaxy Nexus] bigeyes0x0:
Hello there, https://faramir.eriador.org/r/galaxy_nexus/testing-4.0.4/ seems to link to 4.0.3 kernels. What's wrong?
[Samsung Galaxy Nexus] zurchpet:
They just still have 4.0.3 in their name cause nikademus didn't update his packaging script yet.

Just take the ones you find there, they work without issues on 4.0.3 or 4.0.4.
[Samsung Galaxy Nexus] renaud:
What is the point of upgrading version numbers, they are the same

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Kelvino9:
Maybe you should simply remove the redundant download options and combine the 4.0.3/4.0.4 kernel. Both have the same hash tag so they are exactly the same files. People will continuing asking the same stuff over and over if there isn't a clear difference between the various download options.
[Samsung Galaxy Nexus] renaud:
To be honest, that's just a symlink on the server. Maybe I will link the other way round.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nklenchik:
This was recommended to me in a pm. Coming from Franco's, are we using ondemand/384 min?
[Samsung Galaxy Nexus] beekay201:
are you still trying to up version of wifi driver, nika?

seems 205 is going stable, no issues reported so far. i just flashed it, kinda of late, but i will report on how it goes.

Did you search the thread?

No (edit: customizable) oc here, nikademus goes for stable kernel (edit: it does have 1300mhz as last step, i had forgotten about it). as for the signal drop when sleeping, you're talking about wifi signal? currently i can't reproduce the issue. I've been using wifi hotspot sucessfully with my tf201 a few days now with #202.
[Samsung Galaxy Nexus] renaud:
By default, it's interactive governor with 384 MHz minimum

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
The version I use is the latest compatible one. v6 is not ready yet.

Phone runs at 1.3Ghz instead of 1.2Ghz, but it's enabled by default and the 1.2Ghz step has been removed.
[Samsung Galaxy Nexus] Gregus59:
208 out of control... Aaaaaah! Lol!
[Samsung Galaxy Nexus] renaud:
What do you mean? Any problem?
[Samsung Galaxy Nexus] Gregus59:
No problem Nika, just a joke, for fun... ;)
[Samsung Galaxy Nexus] renaud:
OK thanks, I wanted to be sure since someone reported me a random reboot. But this seems more like a coincidence.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gregus59:
No problem with 208 for me.
[Samsung Galaxy Nexus] zurchpet:
Yeah. All well on 208 here too :)
[Samsung Galaxy Nexus] jbeez:
No random reboot since that one isolated incident, so looking good.:thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
had a signal drop on aokp#b29+fugu#205, switching to cm9 latest+fugu#205. since no one reported similar on #205, it was probably rom right? should i just ignore, move to cm nightly and #208?

Sent from my TF201
[Samsung Galaxy Nexus] Macke93:
Flashed the new MoDaCo release yesterday!

So I think it's time to use the FuguMOD kernel :D

Going to flash 4.0.4 test version #208 :)
[Samsung Galaxy Nexus] Kelvino9:
Can AOSP kernel be used with stock ROM which MCR are usually based of? I recall other devices I owned were not able or recommended to use AOSP based kernel on stock based ROMs and vice versa.
[Samsung Galaxy Nexus] franciscofranco:
Its all compatible, this is a Nexus not other lame devices ;)
[Samsung Galaxy Nexus] Kelvino9:
I like that answer allot :)
[Samsung Galaxy Nexus] logi43:
I'm back with the kernel and the performance is very good and got into a cycle of four hours loading screen with the 206 version sheduler noop interactive governor frequencies 384/1338 mHz

I congratulate:D
[Samsung Galaxy Nexus] renaud:
r210 features a newer wifi driver and some updates to the interactive governor.
[Samsung Galaxy Nexus] KSTu:
nice to have you here, i used your kernels on SGS1,the best kiernels i ever had :P
[Samsung Galaxy Nexus] logi43:
Thanks, trying r210.
[Samsung Galaxy Nexus] fireon123:
210 working flawlessly here! Thanks!
[Samsung Galaxy Nexus] skdubg:
hi nikademus

did you plan to add the fastcharge option from Chad0989?

thanks
[Samsung Galaxy Nexus] renaud:
Hi,

No I don't. I don't feel this helps at all.
[Samsung Galaxy Nexus] skdubg:
ok no problem. :)

so i must charge over AC
[Samsung Galaxy Nexus] akash3656:
Love your kernel man! It works very well... xD I finally found a kernel to keep.

I was about to ask about Fast Charge, but you said you don't want to add it in. It would be great if you added support for it. But either way, nice kernel.
[Samsung Galaxy Nexus] jbeez:
210 running great, this kernel has fixed my wifi big time(not just 210). I can't believe how many issues i had with bone stock wifi on the cisco controllers at my work.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Macke93:
Just flashed test #212 4.0.4 version! :D

Getting great battery time with youre kernel nikademus! :)
[Samsung Galaxy Nexus] zurchpet:
Yeah, #212 is Linux 3.0.28-rc1 :)

PS: nikademus is trying to build a surprise...
[Samsung Galaxy Nexus] Macke93:
Sounds very interesting! :D

I'll be waiting for it! :)

Edit: works great with latest #212 :D
[Samsung Galaxy Nexus] sakuhei:
using 213 for a day

screen on time with 3.5 hr with 30% battery left

that's really nice, better than the avg 4hr screen on time! nice kernel!!!
[Samsung Galaxy Nexus] Gregus59:
214 is ok... So Nika, what's the surprise?
[Samsung Galaxy Nexus] beekay201:
#212 ran well.

Switched to #214. Also found supercurio's voodoo galaxy nexus display experiment 0.2, fc's with fugu. Would it be possible to support it, nika?
[Samsung Galaxy Nexus] renaud:
As far as I can see after a quick search, and given supercurio mentions "standard/official kernel, or any custom one without randomly unchecked build options.", supercurio probably uses again tricks to make his app work (like writing directly in /dev/mem), which will never be supported on my kernel. The options I unchecked are not randomly unchecked.
[Samsung Galaxy Nexus] sakuhei:
http://xdaforums.com/showpost.php?p=20843237&postcount=1

hi nika, there is a new IMM76I update (a kernal update i think) for 4.0.4 and it seems to solve the data drop problem. can you use that in your latest build of fugu kernel?
[Samsung Galaxy Nexus] renaud:
I will have a look after the week end. 216 needs some testing
[Samsung Galaxy Nexus] renaud:
I have added some patches for 217, maybe some will solve data drops
[Samsung Galaxy Nexus] Macke93:
#216 runs smoothly and with great battery time! :)
[Samsung Galaxy Nexus] GeyerA:
Hi. just updated my CM 12-04-18nightly with your kernel using the stable release. Hope will solve my issue on signal drops (XXLA02 radio).

One question for the bootloader posted on page 1. I am after the PRIMEKL03 but you post PRIMELA03. Is this the same just a spelling issue? I got the KL03 from the matrix you referred to

http://source.android.com/source/building-devices.html

can somebody point me to the fastboot file..? thanks
[Samsung Galaxy Nexus] Kelvino9:
PRIMELA03 is the latest Bootloader available. Click on the link in my signature for the Bootloader.
[Samsung Galaxy Nexus] GeyerA:
Hi, seems you can not sleep.:-)

I took your file and extracted the bootloader.img went into fastboot mode and flashed

sudo ./fastboot flash boot bootloader.img

and restarted bootloader but then got in red "fastboot mode - no boot or recovery img"

restoring my nandroid....:-(

UPDATE - restored my nandroid and found a flashable version. All done. Thanks.