yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MWisBest:
Not sure what's going on with bootloops... just a hunch here, can you bootloopers boot into fastboot (hold all 3 buttons on boot-up) and tell me what it says for "BOOTLOADER VERSION"? e.g. something like PRIMEMD04.

Also I'd make sure that you format /system manually before flashing, just to be safe.

In addition, I strongly recommend that you do not use CWM as your recovery, for those of you that are; make sure you're using TWRP 2.8.1.0.

I've seen this happen on occasion as well. This can be avoided by doing this:

1. Flash the ROM zip, and ONLY the ROM zip.

2. Go back to the TWRP main menu, open the Mounts menu, and make sure "system" is unchecked. If it is checked, press it to uncheck it.

3. Flash the GApps zip, and ONLY the GApps zip.
[Samsung Galaxy Nexus] Driver007:
PRIMEMD03

And yes I formated system manually
[Samsung Galaxy Nexus] macropp:
HW - 9

BOOTLOADER - PRIMEMD04

BASEBAND - I9250XXLJ1

I'll try formatting system now.
[Samsung Galaxy Nexus] vivekbalan:
Hw - 9

bootloader - primelc03

baseband - i9250xxlj1
[Samsung Galaxy Nexus] macropp:
Same bootloop after formatting system manually and installing ROM and GAPPS.
[Samsung Galaxy Nexus] AbhishekS:
Wow! This is freaking awesome. Once the SIM card starts working I'm definitely jumping to Lollipop. :D
[Samsung Galaxy Nexus] alboz83:
Oh thanks works. I have flashed the Rom+Gapps but i have Unknow baseband

In fastboot i have:

HW - 9

BOOTLOADER - PRIMEMD04

BASEBAND - I9250XXLJ1
[Samsung Galaxy Nexus] pvkiniyan95:
supersu works fine in this build..just rooted..

AOSP browser force closes btw
[Samsung Galaxy Nexus] garyngkt:
I tried doing this :-

I've seen this happen on occasion as well. This can be avoided by doing this:

1. Flash the ROM zip, and ONLY the ROM zip.

2. Go back to the TWRP main menu, open the Mounts menu, and make sure "system" is unchecked. If it is checked, press it to uncheck it.

3. Flash the GApps zip, and ONLY the GApps zip.

Bootloader : PRIMEKK15

Variant : maguro

But getting bootloops and yes format system everytime before flashing L zip file
[Samsung Galaxy Nexus] revanmj:
I'd try updating the bootloader - you have quite old version of it (PRIMEKK15 is from ICS days, the newest one is PRIMEMD04, which is five versions newer than yours).
[Samsung Galaxy Nexus] Master94ga:
I have "PRIMEMD03", how to update to 4?

You are here :D

http://www.androidworld.it/2014/11/...nti-aosp-per-tutti-i-nexus-e-xperia-z-256976/
[Samsung Galaxy Nexus] revanmj:
Simply download img file (or ZIP) and flash it just like recovery. There is a thread here on xda somewhere with all bootloaders for GNex.
[Samsung Galaxy Nexus] alboz83:
i tried to flashed the last baseband DVMK1 but not work. I wait for SIM working and i jump to lollipop because is awasome, fast and good, but now i must return to kitkat. Good work MWisBest
[Samsung Galaxy Nexus] Master94ga:
Me too, just waiting phone and sms! :D
[Samsung Galaxy Nexus] garyngkt:
Is this the thread? :D http://xdaforums.com/galaxy-nexus/general/ref-bootloader-collection-t1587498

So I should flash the primemd04 in TWRP recovery correct?. I am using TWRP 2.8.0.1
[Samsung Galaxy Nexus] revanmj:
Yes, this is the thread. I don't know if those zips work in TWRP (I flashed it long time ago in CWM), but if they don't, you always can extract img file and flash it via fastboot :)
[Samsung Galaxy Nexus] vivekbalan:
I used v2 zip file many times but still bootloop. I followed all the steps suggested.

If possible, can you share your modified v1 zip file?

Thanks.
[Samsung Galaxy Nexus] Driver007:
updating bootloader did't helped, still bootloops
[Samsung Galaxy Nexus] flip360:
Neither v1 or v2 of the zips work for me, cant get past the Google logo, Maguro GSM, TWRP 2.8.1.0, ext4, PRIMEMD04 bootloader
[Samsung Galaxy Nexus] drmxmyt:
yeah same:(
[Samsung Galaxy Nexus] piterdemon:
1. Install TWRP 2.8.1.0

2. Make sure You have all partition on ext4

3. Wipe system/data/cache

4. Install ROM

5. Go to mount options and uncheck system

6. Flash GAPPS

7. Reboot

Boot take ~2 minutes, SIM dont work, Camera dont work, recents arent smooth, there are a little lag. I dont saw more problems
[Samsung Galaxy Nexus] sergialess:
I'll wait for a stable version, with all working, F2FS support, new GPU drivers, Linux kernel 3.4 and a lollipop getting out of the USB port.

Just kidding... ;PPP
[Samsung Galaxy Nexus] vivekbalan:
Which ROM zip you used? V2 or manually modified v1 zip file?
[Samsung Galaxy Nexus] sagara.sandaru:
Tried everything.. Updated bootloader. Wiped system, cache. Stuck on bootloader. ?

Recovery: twrp 2.8.0.1

Is there any logs I can give you? [MENTION=3390093]MWisBest[/MENTION]
[Samsung Galaxy Nexus] Castro27:
Holy F*cking Sh*t that was fast. I'll try as soon as I get home. Awesome work
[Samsung Galaxy Nexus] vivekbalan:
I am also stuck with the same issue. Phone keeps restarting and stuck in google logo.
[Samsung Galaxy Nexus] chrislam1220:
How can i back to ex4 if i have flash to f2fs before?i have flash the latest recovery and there are no button for me backing to ex4
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Let me start by saying that [MENTION=3390093]MWisBest[/MENTION] you are the best dev ever. I mean a lollypop rom just 48 hours after Google had made the code public amazing. Not only that you gave our device new life by creating the updated gpu drivers. You are the best hands down :D

I know these things take time but how long do you suppose it will take for a stable lollypop build
[Samsung Galaxy Nexus] marcovittori:
i'm trying lollipop from this morning and i've found some little glich in the audio,facebook is very laggy and even g+ lags too much,for the rest is very smooth.

Thank you for your work :)

EDIT: the rom rebotting itself and goes in bootloop after you uninstall an app
[Samsung Galaxy Nexus] croccio:
is there any way to enable baseband? i've flshed old baseband, but it doesn't work
[Samsung Galaxy Nexus] flip360:
RIL is broken, i dont think just swapping things will make it work unless you go into sources to find a fix
[Samsung Galaxy Nexus] croccio:
so i can't enable it?

______

this rom is great :D thank you :D
[Samsung Galaxy Nexus] alboz83:
Guys we need to wait MWisBest, i'm sure that in a few time he will fix all bugs, first the RIL.
[Samsung Galaxy Nexus] marcovittori:
No,we need to wait a fix from MWisBest
[Samsung Galaxy Nexus] piterdemon:
V2
[Samsung Galaxy Nexus] Ashutos1997:
Will the rom boot if i flash it using cwm ?
[Samsung Galaxy Nexus] piterdemon:
Use twrp 2.8.1.0 like I wrote 2 pages earlier
[Samsung Galaxy Nexus] croccio:
how do you install it? i installed from playstore but doesn't work
[Samsung Galaxy Nexus] revanmj:
Most likely you have to install it via recovery. I think there is ZIP installer on author's webpage.
[Samsung Galaxy Nexus] piterdemon:
DirtyV 4.4 vs Lollipop 5.0
[Samsung Galaxy Nexus] Master94ga:
Very good, so the performance are already good :)
[Samsung Galaxy Nexus] vangtsog:
Someone to post a video from lollipop!!!
[Samsung Galaxy Nexus] pvkiniyan95:
Flashed the zip
[Samsung Galaxy Nexus] pistlman:
I've installed the rom just now. be patient for a while and I'll post a short video!
[Samsung Galaxy Nexus] pvkiniyan95:
A few more bugs....

Aosp browser doesn't work

None of the email clients work...(every time I open an email it closes)

Certain apps installed via play store gets uninstalled without any notice (after an hour few of my apps are gone)

Video playback is a hit and miss
[Samsung Galaxy Nexus] Loureiro:
Impressive I may say. Booting build right after lolipop code hits AOSP. You're on the egde.
[Samsung Galaxy Nexus] freshgiammi:
Okay, everyone calm down.

Maguro variant is having RIL issues but don't worry. I'm the only Dev with a maguro (until Ziyan fixes his one), so if there are Maguro issues i can check them out. Also, Kyle is probably able to fix it in some hours.

OMX, Video Decoding and camera stuff are probably borked because of newer GPU drivers, but we're looking at it. Just be patient, at the end AOSP got released 48h ago, right? At least we got a more or less working build thanks to MW ;)

RECENTS MENU LAG: that's because we're missing a commit from Nexus 4 repo, it's going to be fixed soon.

Happy Christmas, fellas!
[Samsung Galaxy Nexus] Ashutos1997:
When i flashed rom and unmount system, says OS not found when tried to reboot ?

---------- Post added at 08:55 PM ---------- Previous post was at 08:38 PM ----------

UPDATE : Forgot to flash the gapps :v
[Samsung Galaxy Nexus] freshgiammi:
Also, remount the partition before rebooting. Just so.
[Samsung Galaxy Nexus] Ashutos1997:
Still bootlooping:(
[Samsung Galaxy Nexus] RoadToNever:
Found few bugs: Clock crashes. Dropdown torch is proken.

Was great fun playing with Lollipop today. Looking forward to fixed RIL and screen color controls. Big thanks to [MENTION=3390093]MWisBest[/MENTION] and [MENTION=4986658]freshgiammi[/MENTION] :good:
[Samsung Galaxy Nexus] piterdemon:
Torch is broken because of doesnt working camera
[Samsung Galaxy Nexus] Ashutos1997:
Any help ? I followed the process but stuck on google logo for >2 Minutes :(
[Samsung Galaxy Nexus] RoadToNever:
Be patient it takes a while.
[Samsung Galaxy Nexus] Ashutos1997:
Sir, i am coming from 4.3 JB (Due to some prob), it will boot na after following the process ?
[Samsung Galaxy Nexus] freshgiammi:
I'm aware of torch and it's probably part of the camera mess, but thanks ;)
[Samsung Galaxy Nexus] Sain Choe:
In Google reference nexus forum, one of the nexus users forum in Korea, a member got some feedbacks and knew that problem is caused by flash memory(eMMC) chip.

The earlier chips, VYL00M causing google logo loop.

The later, V3U00M, there is no problem, yet.
[Samsung Galaxy Nexus] Croc97:
Trying to flash lollipop, after 30 minutes it hasn't done anything! So I pulled out the battery and now i'm retrying (the first time i've only wiped all and the flashed the rom, now i'm trying to flash after unmounting system). I'm on twrp 2.8.1.0. Am I doing something wrong?
[Samsung Galaxy Nexus] Sain Choe:
I think that problem is caused by flash memory chip.

Please read my reply.
[Samsung Galaxy Nexus] Ashutos1997:
Can anyone just make a YouTube video on how to boot L ? It would help me and all others.
[Samsung Galaxy Nexus] Master94ga:
How we know which chips we have?
[Samsung Galaxy Nexus] Croc97:
But im' not having bootloop issues, the rom simply doesen't flash! On the recovery it remains stuck after the md5 checking.

EDIT:
[Samsung Galaxy Nexus] Ashutos1997:
Then ours is earlier one which causes bootloops .
[Samsung Galaxy Nexus] Loureiro:
You need to run an app called EMMC Brickbug check.
[Samsung Galaxy Nexus] tostep:
eMMC Brickbug Check show information about eMMC chip.
[Samsung Galaxy Nexus] Master94ga:
Thanks, I have VYL00M, so if i flash I will got bootloop?
[Samsung Galaxy Nexus] Nautilus74:
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=it
[Samsung Galaxy Nexus] Carlos_Manuel:
You can try and see what happens..

I'm wondering if the EMMC type really is the problem causer.. then how can it be fixed... I also have VYL00M :good:
[Samsung Galaxy Nexus] tostep:
It's only assumption, that VYL00M is the cause of google logo loop. ;)
[Samsung Galaxy Nexus] pistlman:
I'm uploading a video on youtube. Here the link and I have written a post in my blog about this great work.

I have installed this rom with CWM Recovery after wiping all. All is gone ok. No problem. Thanks man, you're the best!:D
[Samsung Galaxy Nexus] Loureiro:
For those who don't have a bootable device, you can check you EMMC model via adb shell.

Running from a terminal with right permissions:

~ $ adb shell

cd /sys/class/block/mmcblk0/device
cat name

Mine is VYL00M and I got it bootlooping with v2 build.
[Samsung Galaxy Nexus] flip360:
Same here
[Samsung Galaxy Nexus] Driver007:
True, I have older version and I got bootloop
[Samsung Galaxy Nexus] Master94ga:
Also who have the rom that work can check which model of EMMC have :)

However why the problem come only with android L and not other release, what is different in emmc and how it work?
[Samsung Galaxy Nexus] cqloveqc:
I just flashed the rom from CM Nightly 11.02 build, and never succeed to boot into the rom,

Maybe i need flash another rom first ?
[Samsung Galaxy Nexus] nikodr:
video is private
[Samsung Galaxy Nexus] Sain Choe:
I used eMMC brickbug check app, on playstore
[Samsung Galaxy Nexus] MrJoas97:
I have Lollipop installed and I have the V3U00M type.
[Samsung Galaxy Nexus] sgspluss:
[MENTION=2238316]pistlman[/MENTION] the video you share are privat...
[Samsung Galaxy Nexus] Sain Choe:
Yeah, I checked and I got it now!

I also have same issue, and I have older one.
[Samsung Galaxy Nexus] MWisBest:
As you guys have so kindly figured out for me,

VYL00M eMMCs are bootlooping.

I'm looking into it right now.
[Samsung Galaxy Nexus] Sain Choe:
Thanks for all your efforts! :D
[Samsung Galaxy Nexus] pistlman:
Try now!
[Samsung Galaxy Nexus] Castro27:
It looks quite smooth
[Samsung Galaxy Nexus] MWisBest:
Alright I've got a pretty good idea of what's going on.

VYL00M eMMCs have been a real bug-fest for many devices, so I'm not exactly surprised that that's the eMMC to be causing trouble.

With Lollipop, they're using this weird new format for OTA zip flashing. I don't exactly know why they did it, but it certainly seems that's what is causing the issue here. I'm just hoping this hasn't completely hosed anybody's eMMC.

A system.img flashed in fastboot may be a potential temporary workaround until I figure out what the hell is going on. I'll do a new build like that soon, I've currently got toroplus building and I don't think I can do two builds at once...
[Samsung Galaxy Nexus] Master94ga:
Yes, animations are smooth, only opening of apps is a bit slow
[Samsung Galaxy Nexus] Castro27:
It could be kernel related. Besides, this is only the second build, optimizations will come along the way.
[Samsung Galaxy Nexus] Croc97:
Nobody can help me? Now it's about an hour that is flashing :( (Attention: flashing, not in bootloop).
[Samsung Galaxy Nexus] flip360:
read a few posts up, what kind of EMMC do you have?
[Samsung Galaxy Nexus] MWisBest:
Got an idea on the eMMC problem.

If somebody with the older eMMC is willing to test, please try the following:

Open up the ROM zip, and find the file titled "system.transfer.list". It's just a text file, so open 'er up in a text editor and do this:

On the third line of the file, you should see it begins with the word "erase". Change that to "zero", meaning instead of that line saying "erase 2,0,167424", it'd say "zero 2,0,167424".

Then try flashing like usual.

Even if this doesn't work, it will help me to at least narrow down the cause of the issue.
[Samsung Galaxy Nexus] Croc97:
I have the VYL00M, but the problem is not that it goes on bootloop, it is stuck at the flash. Wait a sec and i'll post a photo (just the time to post it with my nexus 5).

Update:

Here it is
[Samsung Galaxy Nexus] Driver007:
will try in a few moments
[Samsung Galaxy Nexus] chongns:
Hi people, try change those 3 animation scales to 0.5, feel the different.
[Samsung Galaxy Nexus] AllAboutTech:
Hi,

What tricks are included in this ROM?

non-intrusive call?

lock screen notifications?

navbar customization?

hold back button to kill?

themes?

Thank you in advance for your quick response.
[Samsung Galaxy Nexus] AbhishekS:
1. Yes

2. Don't know

3. Yes

4. Yes

5. No
[Samsung Galaxy Nexus] boonz19:
Would love this as well! Cheers
[Samsung Galaxy Nexus] Driver007:
Have one problem whit this ROM that gps is not working. Whit the newest build. How to solve this problem or give logs to find out?
[Samsung Galaxy Nexus] chongns:
hi dude, gps is working good, i used it 4 times today, with sygic navigation.
[Samsung Galaxy Nexus] Driver007:
Hm strange can't get GPS lock
[Samsung Galaxy Nexus] chongns:
Opps. sorry, i used dirty v kernel, not the fml original. Someone please help to check this out?
[Samsung Galaxy Nexus] MWisBest:
Can you open up a root-enabled file explorer and do the following?:

1. Go go the /data folder.

2. Scroll until you see a "gps" folder, and open it.

3. If there is NOT a file called "xtra.bin" inside the gps folder (which, if my hunch is correct, there won't be), try to delete the gps folder and then reboot your phone.

If there is an xtra.bin file there, make sure you've tried using the GPS Test app on the Play Store and not just Maps or something like Maps.

If the first thing fixes it, then you shouldn't have to do this again, and if it does then I'll know how to (automatically) fix this for anybody flashing FML in the future too.

Thank you!
[Samsung Galaxy Nexus] Driver007:
So I deleted gps folder and there was xtra.bin file, rebooted and I got gps lock in about 2 minutes.

Thanks.
[Samsung Galaxy Nexus] iHeadhunterz:
I'm really enjoying this ROM with Dirty V SuperRAM, but I have a couple questions/requests?

Not sure if it's OMNI in general, but

1. Is it possible to remove or add tiles from the quick settings like in CM? I feel like there's too many tiles currently

2. Does this ROM have any volume increases? I compared them side by side to CM and this one with OMNI was lower. (I have trouble hearing my alarm in the morning >.<)

3. I noticed that when using the keyboard, it vibrates VERY STRONG ;O. Is there an option to lower the vibration strength or could it just be a bug? Because everywhere else the vibration is fine, EX: Hitting the on screen buttons and unlocking. But for some reason when typing, it's very strong!

4. Do you think the home button short lag could be in connection with the short lag that you experience when pressing the recents button? This one isn't a con,since it isn't too bad. but just wondering :p

Again, thank you Dev for a very fast and stable ROM. I especially like the optimized Dalvik, it feels very speedy! :good:
[Samsung Galaxy Nexus] dezful:
FYI, Android 4.4.3 is up! ;)
[Samsung Galaxy Nexus] nachiket_xda:
+1
[Samsung Galaxy Nexus] fedelamb:
1) Have you pressed the "Pencil Icon" on quick settings panel ?

Then click on the image of the tiles to disable it or long-press and move to change its position

2)To me volume seems good..

3)Check "Launguage and Input > Android Keyboard (Aosp) settings > Advanced Settings >Keypress duration effect"
[Samsung Galaxy Nexus] nischalnischal:
How do we get to see the Battery % in the battery icon, any clues or hints?
[Samsung Galaxy Nexus] Ci@cKi:
You need to go to settings, battery. And there're present two optional settings, one of those let you choose the battery icon.
[Samsung Galaxy Nexus] MWisBest:
See:

4)Yes it seems pretty similar so I'm thinking it could be related to it, but I'm not going to rule out them being separate issues. When you start thinking closed-minded like that on bugs you can end up missing some pretty obvious stuff you would otherwise notice!

Regarding the sound volume, try playing around with DSP Manager (the options under Speaker are what you're looking for I presume so make sure you aren't in the Headset section). It looks like the Equalizer will let you boost the volume by up to 12dB per EQ band, a 10dB increase should be double the perceived volume, however it will probably sound distorted at anything above 7 or 8. You might want to keep the two EQ bands at the far left where they are though, I've found too much bass with this phone's speaker limits the volume of the mids and highs and those are what's going to wake you up more with this speaker anyway. Bass and small speakers just generally don't mix! Obviously make sure you have the alarm volume turned up all the way, and also you might want to try turning on vibration for the alarm if you haven't already.

BTW, for the alarm sound I recommend Sad But True by Metallica... nothing wakes me up like that song does :eek:

Yeah, I've just been waiting on OmniROM to merge in all the 4.4.3 stuff which it looks like they did this morning. I'll get a new build with 4.4.3 stuffs up later today I hope, however that'll probably be the only change. I have some big stuff planned, but it's usually a bad idea to do too much at once so the 4.4.3 merge will be the major change for the next build.

(EDIT: I'm going to be upset if they don't do a 4.4.4, because 1: It's 3 4's! How awesome is that?! 2: There's 4 KitKat bars in a KitKat package! Duh!!)

Yeah, that was something it took me a bit to figure out when I first switched to OmniROM, but when I finally figured it out I was like "OMG this makes so much sense! Goes to show how stupid some things have been with Cyanogen Inc. dominating for so long!" :p
[Samsung Galaxy Nexus] AbhishekS:
I love the way you always call CyanogenMod as Cyanogen Inc. :P :thumbsup: ?
[Samsung Galaxy Nexus] qtoo941:
Oooouh yeah, FML 4.4.3 is coming soon. Damn this is my happy day. I had hard final exams in uni last week and today i understood my marks. I passed this exams, daaamn. I thought this day cannot become better until i saw last answers. I think i gotta get drunk or high in the end of the day :D

I hope vibration feedback on quicktiles and kill via back button will be included in next release even if it's 4.4.3. If this happen i'm totally going to high myself :D
[Samsung Galaxy Nexus] MWisBest:
New build up, Android 4.4.3!

Also, that 2.7.1.0 TWRP version number is not a typo. :)

Long press back to kill works on everything but Settings it seems, I'm not quite sure why Settings is being stubborn.

Since the 4.4.3 update was bigger than I expected I've kept out any new features and stuff like that for this build unfortunately, sorry :( It's just annoying when big changes pile up because then when something goes wrong you don't know where to look to fix it!
[Samsung Galaxy Nexus] diegosolor:
After change "erase" to "zero" in the file system.transfer.list the phone still don't boot, but at least now doesn't loop/restart over and over again, it just stays freeze with the "Google" screen

Thanks for the effort anyway!
[Samsung Galaxy Nexus] MWisBest:
To others: Don't be discouraged by this just yet, confirmation from a few more people would be helpful still!
[Samsung Galaxy Nexus] Loureiro:
Yes the same happens on my maguro.

edit: It only reboots once before freezing at Google logo
[Samsung Galaxy Nexus] Driver007:
now it just freezes at google logo
[Samsung Galaxy Nexus] sohailazam:
Excited

IM REALLY VERY EXCITED WAITED SOOOOO LONG FOR THIS :D CHEERS TO DEV FOR THIS :good:

BUT IM NOT FLASHING IT NOW , caues Gnex is the only phone i have got right now its my daily driver and i guess the ROM got few bugs here and there , never the less ,

can i flash this rom with GSM GALAXY NEXUS( maguro ) ?

can is the wifi and network working ?

can we download apps ?

hoping for a reply ,!
[Samsung Galaxy Nexus] MWisBest:
Alright, guess my idea on the eMMC problem didn't work :(.

Sorry to bother you guys again about it, but please remember I don't even have a maguro, let alone one with this problematic eMMC.

I need the recovery.log file now.

Basically I need you to flash the ROM zip, then in the TWRP "Advanced" menu there should be an option to copy the recovery.log to the "sdcard" (internal storage), press it. Then boot into a working ROM, and give me the contents of that file.

I apologize for all the troubles!
[Samsung Galaxy Nexus] flip360:
You are in the maguro thread so yes

WiFi works no network just yet

Dunno
[Samsung Galaxy Nexus] cqloveqc:
Thx for the great job, i tried, this, but it still doesn't work
[Samsung Galaxy Nexus] Loureiro:
Let me just grab something to eat and then I'll post here the .log

I grabbed my old nokia 5000d to be my daily driver while my maguro is reserved now for testing this.
[Samsung Galaxy Nexus] xxSAKISxx:
You don't have to apologize for anything [MENTION=3390093]MWisBest[/MENTION].You are the one that bring lollipop to our Gnex so we HAVE to help you in any way to make this running percect.
[Samsung Galaxy Nexus] Loureiro:
Ok here's the recovery.log after flashing v2 build.

http://pastebin.com/rXe2Jb71
[Samsung Galaxy Nexus] MWisBest:
"writing 75720 blocks of new data

wrote 243144 blocks; expected 75720"

Well that can't be good! Thanks for the log. If somebody could snag me a log with the "erase" command instead of the "zero" command (just a clean, unmodified ROM zip) that would be helpful too :)