yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Driver007:
http://pastebin.com/3JepsfTF

whit "erase"

EDIT: oops it was whit zero (forgot to update zip)
[Samsung Galaxy Nexus] ScardracS:
I've tried to install that on my maguro (with the falled eMMC) and every time the bootloader reboot itself, so i can't use it..
[Samsung Galaxy Nexus] Skylined:
"Type: VYL00M" on my SC-04d, ;(
[Samsung Galaxy Nexus] Castro27:
I just tried it and gotta say its amazing. Sure, it's not as fluid or fast as it could be but it's still pretty amazing. Amazing job.
[Samsung Galaxy Nexus] MWisBest:
Could I get somebody with a VYL00M chip to test this please?: http://xdaforums.com/devdb/project/dl/?id=9486

Make sure to format /system manually before flashing.

If that doesn't boot, I need somebody to open that zip up and flash the included .img files via fastboot:

fastboot flash boot boot.img
fastboot flash system system.img
[Samsung Galaxy Nexus] pvkiniyan95:
Dude, did u even sleep??
[Samsung Galaxy Nexus] MWisBest:
Not really.
[Samsung Galaxy Nexus] pvkiniyan95:
One more thing to fix which I feel is very important, the cell standby drains battery even in airplane mode....battery drain in unusual in airplane mode
[Samsung Galaxy Nexus] cqloveqc:
Thx, i tried, but doesn't work, but where can i find system.img
[Samsung Galaxy Nexus] pvkiniyan95:
Health first, ROM next....

Try to get some sleep first.
[Samsung Galaxy Nexus] MWisBest:
it's right in the zip file you just downloaded :)
[Samsung Galaxy Nexus] cqloveqc:
ok, will try after restored ny phone :)
[Samsung Galaxy Nexus] grh35:
I tried both ways you mentioned but there's still bootloop at google logo.
[Samsung Galaxy Nexus] MWisBest:
Damn...

Alright, last thing to try for tonight I think:

Flash the original zip in the OP ("v2"), no modifications to it.

When it bootloops do the following:

when the Google logo disappears and it starts to reboot again, hold down power + vol up + vol down, should take you into fastboot. Reboot into recovery, and then do this with adb:

"adb pull /proc/last_kmsg"

HOPEFULLY that file will be there, if so give me the contents of it.

edit: please!
[Samsung Galaxy Nexus] sivaseraphim:
Just a warning.

Quoting from chainfire's thread on brickbugs regarding Samsung's eMMC chips.

If you have a VYL00M chip (like mine) :( Also look at your current FwRev.

Be safe when flashing :P
[Samsung Galaxy Nexus] grh35:
sorry it took so long...
[Samsung Galaxy Nexus] Omar1c:
Flashed on my toroplus and this is pretty smooth good job man

Sent From My GPE HTC One M8
[Samsung Galaxy Nexus] pvkiniyan95:
made it to the xda portal

http://www.xda-developers.com/android/lollipop-samsung-galaxy-nexus-s-iii-mini/

congrats [MENTION=3390093]MWisBest[/MENTION]
[Samsung Galaxy Nexus] jejer:
VYL00M fwrev : 0x25

boot loop
[Samsung Galaxy Nexus] MWisBest:
All Galaxy Nexuses that shipped with a VYL00M chip have a firmware revision of 0x25, which does not suffer from the infamous "superbrick" bug.

No problem! I'm just happy that there was something there at all man, I wasn't sure if it'd pull anything.
[Samsung Galaxy Nexus] ScardracS:
I've read the ksgm bit there's nothing interest... It doesn't explain why the phone reboot itself, or i haven't see it correctly ;)
[Samsung Galaxy Nexus] AllAboutTech:
Hi,

NICE RELEASE!!

I have 2questions:

- i don't have network signal, i am not able to call or use my data

- in the .zip file how /where i can change that build.prop file?

Thank you!!
[Samsung Galaxy Nexus] santi1993:
thanks thanks thanks thanks <3

ill buy a new gnex to test all u need, how can i help u with new gpu drivers and camera? we need james bond in there to take libs from texas instruments :D
[Samsung Galaxy Nexus] xaifer:
The bugged chip on galaxy nexus is V3U00M but I think there aren't problems to flash lollipop rom.

Using f2fs instead of ext4 can resolve all the problems of Galaxy Nexus (maguro) with V3U00M chip?
[Samsung Galaxy Nexus] sivaseraphim:
Thanks. That's reassuring for all maguro, toro, and toroplus users ><
[Samsung Galaxy Nexus] aosp:
No worries fellas maguro can't supebrick EMMC Bugs – CyanogenMod - http://goo.gl/mDtrff

Maguro users will benefit from the below commits soon [MENTION=3390093]MWisBest[/MENTION] is on it :)

[MMC] Improve error handling of Samsung e-MMC wear leveling quirk � 3641ad3 � rbrune/android_kernel_google_steelhead_orig � GitHub - http://goo.gl/shsKWZ

Prior to this change, errors when reading from the e-MMC during

the handling of the quirk would not be detected.

In addition, if an error did occur, the actual error code would

be overwritten by the code that exits the special OEM mode.

[MMC] Provide access to Samsung's e-MMC Smart Report via sysfs � 7ec5227 � rbrune/android_kernel_google_steelhead_orig � GitHub - http://goo.gl/62YLz9

Added CONFIG_MMC_SAMSUNG_SMART which enables code that will

expose Samsung's proprietary e-MMC health information to sysfs.

Example output:

$ cat /sys/devices/platform/*/*/mmc_host/mmc*/mmc*/samsung_smart

version : 0

error mode : Normal

super block size : 4194304

super page size : 32768

optimal write size : 32768

read reclaim count : 0

optimal trim size : 262144

number of banks : 2

initial bad blocks per bank : 10,4,0,0

runtime bad blocks per bank : 0,0,0,0

reserved blocks left per bank : 131,137,0,0

all erase counts (min,avg,max): 0,760,65535

SLC erase counts (min,avg,max): 0,5,74

MLC erase counts (min,avg,max): 0,790,65535

ARM: omap4: steelhead: Enable CONFIG_MMC_SAMSUNG_SMART � 097ed3b � rbrune/android_kernel_google_steelhead_orig � GitHub - http://goo.gl/34tkjK

mmc: core: new discard feature support at Samsung eMMC v4.41+. � 50c7f9d � verygreen/green_kernel_omap � GitHub - http://goo.gl/vpoiK3

Support discard feature if MID field in the CID register is 0x15, EXT.CSD[192]

(device version) is 5 and Bit 0 in the EXT.CSD[64] is 1. Also removed REQ_SECURE flag

check to avoid kernel hang.

This patch is released from samsung.
[Samsung Galaxy Nexus] Master94ga:
Gapps for lollipop: https://s.basketbuild.com/gapps
[Samsung Galaxy Nexus] Loureiro:
Damn why can't I get into fastboot while bootlooping...

Sorry MWisBest, I can't get you any kmsg :(
[Samsung Galaxy Nexus] AllAboutTech:
Hi,

I anyone having the issue with no signal on Lollipop and not able to call or be called?!

thanks.
[Samsung Galaxy Nexus] skyleth:
Ril not working yet
[Samsung Galaxy Nexus] AllAboutTech:
"Ril"?
[Samsung Galaxy Nexus] Ashutos1997:
So there must be a way to boot L on the gnex's which causing bootloop atm ?
[Samsung Galaxy Nexus] andreadec:
Radio Interface Layer

http://en.wikipedia.org/wiki/Radio_Interface_Layer
[Samsung Galaxy Nexus] Ashutos1997:
My eMMC is VYL00M, . I think there's some prob with the VYL00M Chip that causes bootloop and is widespread.
[Samsung Galaxy Nexus] ScardracS:
Ok guys, so i'll return on Ubuntu after lots of months and see if i'll can make somethings for the maguro... if [MENTION=3390093]MWisBest[/MENTION] and other devs who already works on this project will send to me all their knowledge and progress about that rom i'll be really happy :D

Ah, one last thing.. that could be useful make a chat on Hangouts (or one IM) to speack about progress, ideas and other things ;)
[Samsung Galaxy Nexus] ScardracS:
Just one thing.. As [MENTION=2838735]aosp[/MENTION] said, the VYL00M chip on the galaxy nexus isn't affected by "Superbrick", so it won't kill your galaxy nexus.. I'll need to dig a bit on the codes and found the modules wich control that things so if somebody know where they are i'll control if I'm able to make all the necessary changes
[Samsung Galaxy Nexus] Ashutos1997:
The only problem is that gnex's with this VYL00M chip isn't booting the rom. Keeping it in Bootloop .
[Samsung Galaxy Nexus] flip360:
You are a living walking github aosp! Great work everyone!!!
[Samsung Galaxy Nexus] dictionary:
Experiencing the same. ROM runs great, but since I don't have service on my phone, I put it on airplane mode. Woke up with steady drain. Absolutely loving you guys keeping this old device purring
[Samsung Galaxy Nexus] RoadToNever:
It's already fixed in AOSP: http://www.androidpolice.com/2014/1...ght-be-on-hold-because-of-a-serious-wifi-bug/
[Samsung Galaxy Nexus] christianpeso:
That does not have anything to do with this I believe. For one, that bug was for Nexus 5 users. And 2, the issue right now is the RIL(Radio Interface Layer) which controls getting data to and from your phone to Verizons network. Nothing to do with wifi. Wifi works fine right now.

Thanks MW for this!!
[Samsung Galaxy Nexus] MrPutuLips:
Sorry to be a lazy bum, but the last few pages I tried reading through were just technical jibber jabber. What's working and what isn't for the 06/11/2014v2? Is it worth installing for a daily driver?

Thanks
[Samsung Galaxy Nexus] MrJoas97:
Camera is not working.

RIL is not working (phone+data).

Recents is a bit laggy.
[Samsung Galaxy Nexus] ScardracS:
No, it isn't daily driver because RIL doen't work (that mean you can't use any connection.. only wifi working right now)
[Samsung Galaxy Nexus] sgspluss:
Read OP then you will know if you can use it as daily driver or not!

Dont know why some writte such infos in OP and people are to lazy to read...

Hmm maybe the dev's are also gone to be lazy to build and work on our phone, oh ahm i forgot then we never got kitkat or even lollypop!

BTW: a huge thanks goes to [MENTION=3390093]MWisBest[/MENTION] for all the work he done and will in future do :good:
[Samsung Galaxy Nexus] lo97:
Phone and sms doesn't work....not ready for daily driver, just for test
[Samsung Galaxy Nexus] girkev:
Yes. Indeed
[Samsung Galaxy Nexus] MrPutuLips:
Aight thanks :)

I read it. Didn't know if it had been updated for v2 (I presumed that v2 would be a huge improvement over v1?)
[Samsung Galaxy Nexus] Ashutos1997:
Not much I guess. BTW anyone got any Sol to boot Lollipop on VYL00M eMMC chip based gnex ?
[Samsung Galaxy Nexus] dictionary:
Just wasn't sure if that was already included or not. It's my toy phone so it's fun to test.
[Samsung Galaxy Nexus] aosp:
[MENTION=4630140]ScardracS[/MENTION] [MENTION=4560975]santi1993[/MENTION] if both of you are serious about hacking the tuna and want to join the team on hangouts feel free to send me a message so I can add you both to the Operation Optimus Prime hangout ?
[Samsung Galaxy Nexus] ScardracS:
I've send to you a message on hangouts ?
[Samsung Galaxy Nexus] Croc97:
Guys if you want i could be a beta tester because I have the "buggy" eMMC and so i could test if the build works ;)
[Samsung Galaxy Nexus] Ashutos1997:
U have VYL00M eMMC chip ?
[Samsung Galaxy Nexus] dpunx:
My GNeX is VYL00M :crying:. Waiting for new version.

Big thanks for this great job men!
[Samsung Galaxy Nexus] Ashutos1997:
Same here :)
[Samsung Galaxy Nexus] objaa:
Hello, i have VYL00M chip too. Can i help you? (alpha\beta test)

Thanks!;)

p.s when i can check fresh news? twitter \ any social?

(2-3 posts not upd) ;(
[Samsung Galaxy Nexus] NetBender:
Same here :)
[Samsung Galaxy Nexus] Ashutos1997:
Same here. I know [MENTION=3390093]MWisBest[/MENTION] is working hard and will surely fix the error for VYL00M eMMC chips :)
[Samsung Galaxy Nexus] Croc97:
Yes, I have the VYL00M eMMC chip.

Hope i can help you devs for testing :)
[Samsung Galaxy Nexus] ScardracS:
Guys i'm working on mpokang kernel to make it for android 5.0... I know that will be diffiucult (it's really outdated), but it still remain the best kernel for our device and i'm thinking all the optimizations in that kernel will be useful... Plus i'm working on android 5 (i'll download all the codes tonight) and see if i can make something
[Samsung Galaxy Nexus] nikodr:
Apart from being outdated,that kernel was a violation of gpl .Plus have you checked latest dirty -fancy or other kernels?I dont think that mpokang offers much anymore.Hell i mean it is 2014 and other developers are doing their best to offer us kernels,it just doesn't sound right to claim that it remains the best kernel for our device.
[Samsung Galaxy Nexus] Ashutos1997:
Hmm.
[Samsung Galaxy Nexus] Master94ga:
I'm the only one that don't know this kernel? Why you think is still the best?
[Samsung Galaxy Nexus] ScardracS:
I don't know if you have the lucky to try it, but hey, when i said it still remain the best kernel for our device i'm not kidding...

For the GPL's violation i know that, but remember the galaxy nexus is a "died" device, when during mpokang's kernel time it was still selled officially, so I can play with that kernel and tried to make some more optimized.

Anyway, if I can't use that type of kernel I'll pray a Moderator to say me what I can use and what I can't

--EDIT--

Sorry for my English and for my rude tone, but i really hope i'll able to d this thing
[Samsung Galaxy Nexus] ScardracS:
It's a long story, but I'll make it short..

When android was on android 4.3 and the Galaxy Nexus was officially supported there was a developer who built the mpokang kernel, the best, most optimized and most ram free kernel all over the forum of xda.. But, like all the good things, there was a "small" bug: he have used some stolen drivers from Texas Instrument and for that thing he lost all his work, but the github profile wasn't closed. That drivers still remains the most optimized, but they are outdated, so if we're able to add that drivers with the GPU's updated drivers we'll able to build an excellent, and more optimized, rom
[Samsung Galaxy Nexus] skyleth:
I really don't understand why you say it's the best kernel. I've tried fancy and so far, I'm getting the best performance-battery life on my gnex since I bought it ;)
[Samsung Galaxy Nexus] ScardracS:
I have the galaxy nexus from 2012... I know what i mean the mpokang remains the best kernel all over the world for our device ;)
[Samsung Galaxy Nexus] Kustaa:
+1 for that. I've tried many kernels, and even if it's outdated, none of the others gave me the performance, stability, battery and ram management of mpokang.

Actually I'm using v12 right now.

Sorry for the off topic.

On: Awesome work you guys, thanks! Here's another one with the buggy chip.
[Samsung Galaxy Nexus] haakuturi:
I have a VYL00M maguro device - I'm keen to help out with testing!
[Samsung Galaxy Nexus] ScardracS:
Sorry for my long off-topic but i think we can make more than we think with the mpokang
[Samsung Galaxy Nexus] Ashutos1997:
I am also ready to test 5.0 for VYL00M eMMC chip :D
[Samsung Galaxy Nexus] Nautilus74:
what does it mean? Do you have some news to tell us? :)
[Samsung Galaxy Nexus] ScardracS:
Not yet, but if my idea will work, we'll have the best kernel both on android 4.4 and 5.. But i need people who want to resume that type of kernel
[Samsung Galaxy Nexus] freshgiammi:
Please, don't post about Mpokang.

This rom WON'T work with a kernel who hasn't got the updated GPU drivers (because of MW's modifications)

We're trying to give you the best experience with Ziyan's rebased OZ Kernel which is a ultrasuperpumpedup version of the stock one, right from TI.

Also, GPL Violations.

(Be aware that kernels doesn't need to be ported to different android version: they mostly need ramdisk modifications only.)

EDIT: Did i tell you that Mpokang is super risky because of commits which could corrupt your CPU Cache, resulting in a completely fubar CPU?
[Samsung Galaxy Nexus] tommrazek01:
MWisBest, you're the man! It's happenning! But are you planning to fix the WYL00M emmc bootloop? I have this chip but would love to try the ROM out.
[Samsung Galaxy Nexus] cosmos321:
Just want to try the lollipop rom. Installation successful, but i can not install the gapps-package. Some error with the updater script and a thick red FAILED in TWRP-Recovery (use the recovery and the gapps package from the first post)! Could someone help me!
[Samsung Galaxy Nexus] Castro27:
Just reboot the recovery, the partition needs to be remounted before flashing gapps
[Samsung Galaxy Nexus] cosmos321:
ok thx, will try!

EDIT: THX, worked perfectly, lollipop running on my device :D, great work!
[Samsung Galaxy Nexus] raymond1688:
Then go ahead and start a new thread for that.
[Samsung Galaxy Nexus] ScardracS:
You need to unmount /system after flashing the rom
[Samsung Galaxy Nexus] ScardracS:
So after spoke for about 3 hours wirh others devs we have reached a conclusion: mpokang was (and is) unsafe to use for some things.

1) it's on violation of GPL license

2) it use double linefill and that explain when, if you use a memtester, the memory could be brick

3) battery drain really fast (more speed need more battery)

4) it's outdated (some things still be useful, but we can replace them normally)

5) some modules on the kernel are really dangerous (but nobody cares about that things)

With this post the discussion of mpokang is closed, so do not ask to me and/or other devs about it.. If you want you can build it yourself (the codes of V9 are on github so everybody feel free to play with it)
[Samsung Galaxy Nexus] flip360:
Great. Another wasted post on the kernel we shouldnt mention and this one also.
[Samsung Galaxy Nexus] bsmitty83:
Only thing that should be clarified , the kernel used to be in violation of the GPL , but the source has been updated for some time .

The rest is pretty accurate . especially when the linaro guys who originally wrote the patch say it will only benefit benchmarks.

So I say as long as its mentioned explicitly that this is still enabled , build it if you want .
[Samsung Galaxy Nexus] sohailazam:
Is network , WiFi , and camera working ? And how is the ROM running ?
[Samsung Galaxy Nexus] ScardracS:
Network doesn't work, camera partially works only if you use another camera app, but [MENTION=3390093]MWisBest[/MENTION] could be more clarified
[Samsung Galaxy Nexus] cosmos321:
So it is. Networks running well, stock-camera not (so the flashlight).

Moreover the speed of the rom is quite fast. absolutely remarkable in this early stage.

Edit: I am also affected by the battery drain. Have lost 30% in 9h30min in airplane mode ( overnight, not in use).

Gesendet von meinem Moto G 2014
[Samsung Galaxy Nexus] andreadec:
Is there a downloadable zip with working RIL? Or can you link me the Git repository you used to build it? Thanks.
[Samsung Galaxy Nexus] ScardracS:
Ril is not working yet. I'm working on it with other devs for fix as soon as possible
[Samsung Galaxy Nexus] jonathanpeter:
Stuck in Bootloop.

So I flashed the rom and included gapps on my phone, and now it's stuck in the google boot screen. I're tried re flashing it but then it doesn't boot up at all.

How do I fix this? I'm on a Mac and have no access to Wug's Toolkit. Please help me.
[Samsung Galaxy Nexus] soder:
So, I checked my phone with the app, and it says my phone is a VYL00M-version. Can't I use this ROM then, or is it that it might not work?

The app says "Brick Bug? NO. Sane chip". Does that mean, that my phone is OK even if it's a VYL00M or what does that mean?

/Söder
[Samsung Galaxy Nexus] ScardracS:
You probably have the VYL00M chip (I bet you haven't read all the op!) so you can't use that as your rom right now

read the op, the VYL00M version isn't fixed yet so you aren't able to try it

I hope that's the last time weneed to say it, there is an OP specially for that thing
[Samsung Galaxy Nexus] Master94ga:
You have to wait a fix, lollipop doesn't work on all Gnexus :)
[Samsung Galaxy Nexus] skyleth:
Battery pull, boot recovery and restore your previous rom

Your chip is OK, but now we can't use the ROM because it's not booting
[Samsung Galaxy Nexus] Castro27:
Don't flash it, it will bootloop if you do since this chip is the one having problems. You are gonna have to wait for a fix.
[Samsung Galaxy Nexus] theBlackEnd:
Just a recap for newcomers.

If you have VYL00M chip, just restore a working backup from recovery. [MENTION=3390093]MWisBest[/MENTION] is working to fix that.

If you don't have a backup, check THIS.

EDIT:

RIL is NOT working atm. If you have VYL00M eMMC chip and don't want a bootloop, DON'T FLASH FML 5.0. Just wait for MWisBest and testers to solve the problem.
[Samsung Galaxy Nexus] girkev:
Remove The Battery. Press all three buttons at The same time. Now you can enger The recovery and restore a backup.
[Samsung Galaxy Nexus] jonathanpeter:
Yes, I just saw the part of the op stating the VYLOOM chip thing. I flashed it half awake in the morning out of excitement, and now I have an unusable phone.

Does anyone know of any way to transfer a rom file to my phone? I don't have a backup nor a rom zip on my phone and it can't go past the google screen.

I'm on a Mac.
[Samsung Galaxy Nexus] santi1993:
Try adb sideload command and ull be fine
[Samsung Galaxy Nexus] ScardracS:
You could try to restore it via odin.. You can ceck on internet how to do that, but that will kill all your data
[Samsung Galaxy Nexus] tommrazek01:
Look for the option "ADB Sideload" In your recovery - if it's at least somewhat recent, it should have it. Tap/press/click on it and connect it to your mac. Then download the Android SDK for mac. Navigate to "platform-tools" of the SDK with your terminal and use the command "adb push your_rom_file.zip". Your recovery will automatically transfer and install the file (if everything goes well :p)

Edit: ScardacS beat me to it. His method is certainly more reliable, but mine should hopefully keep you your data :D
[Samsung Galaxy Nexus] MrJoas97:
First connect you phone to the mac with a usb cable.

On the mac: download the android sdk. There will be a folder adb in it. Open terminal and ise the cd command to get to that directory.

On the phone: boot to recovery. Go to the advanced menu and select adb sideload. Then go back to your mac and type this in terminal but dont execute it yet(without the quotes): "adb sideload ". Then drag the zip you want to flash to the terminal window and push enter. The phone should now flash the zip file you dragged to the window.
[Samsung Galaxy Nexus] theBlackEnd:
Download the zip file attached to the first post of this thread, it contains adb for MAC.

Then connect your device to the PC and boot your device in recovery mode (volume down + volume up + power on).

Extract zip, put the zip file of your rom in that directory and rename it to "rom.zip"

Open ADB directory from shell (terminal) -> cd DIR
adb push rom.zip /data/media/
[Samsung Galaxy Nexus] jonathanpeter:
Thanks everyone. I haven't been successful though. SO, I did the adb through terminal method. I went to dab side loading on my phones recovery and followed all steps to sideload the rom.zip from my mac, but after I press enter, nothing happens on the phone. Am I missing something?

EDIT: I've done it! I happened to miss a "/" in the command.

Again, thanks guys!
[Samsung Galaxy Nexus] xxSAKISxx:
Sry bro i hope you recover your nexus BUT next time do what all devs suggest from first place before you try anything to your phone . MAKE A NANDROID. Is just so simple.. Wish you the best.
[Samsung Galaxy Nexus] jonathanpeter:
I've side loaded a Paranoid Android rom via adb. Now my phone is working. I just saw the VYL00M test file. Will be flashing now!
[Samsung Galaxy Nexus] Kewyang:
HI All,

I have just flashed the stable version, but would u recommend me to flash the beta 1015 version if I dont mind the radio issue? And which launcher and kernel would you recommend ? Thanks
[Samsung Galaxy Nexus] tommrazek01:
I think I must be blind, but I didn't notice a test file. Can you point me to it? Thanks a lot ;)
[Samsung Galaxy Nexus] bankov:
http://xdaforums.com/devdb/project/?id=4352#downloads
[Samsung Galaxy Nexus] Master94ga:
Good, hope it work :o
[Samsung Galaxy Nexus] Ashutos1997:
Report here if the VYL00M package works.
[Samsung Galaxy Nexus] the_f4b1:
For me it doesn't. Also the GAPPS-Installation-Process failed. Will post the error soon.

//E:

file_getprop: failes to stat "/system/build.prop": No such file or directory

E:Error in /data/.../FML-GApps-AOSP-5.0.zip (Status 7)
[Samsung Galaxy Nexus] Ashutos1997:
Hmm
[Samsung Galaxy Nexus] dpunx:
Not working for me. Loops Loops Loops :/
[Samsung Galaxy Nexus] Castro27:
Did you reboot the recovery after flashing the rom?
[Samsung Galaxy Nexus] the_f4b1:
Didn't help.
[Samsung Galaxy Nexus] Ibanez33:
I don't know about anyone elses device but mine says the install is succsessful but then reports when i go to reboot that no OS is installed?

Trying VYL00M test version