yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Jar3112:
Just asking, but since boype implemented a working uksm, could you possibly take it from his repo?

It's only my curiosity though, not a real request :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
No , there is a lot of commits from newer kernel versions I made to certain parts of the kernel that don't like uksm . that's why they depreciated it I believe. I'd have to revert a lot of commits to make it work that would be a step back IMHO .
[Samsung Galaxy Nexus] osm0sis:
If mainline Linux killed off uksm, and use an updated ksm instead, I'm sure they had their reasons, so Smitty is following their lead. :) :good:
[Samsung Galaxy Nexus] SoftWord:
And so, latest ksm is best than uksm?
[Samsung Galaxy Nexus] osm0sis:
It's what Linux is going with. Don't know any more on the topic to say more than I already have. :p :good:
[Samsung Galaxy Nexus] bsmitty83:
Not really . its just that with the changes I made in my kernel , uksm no longer works . if I didn't make those changes , I would still be using uksm .
[Samsung Galaxy Nexus] SoftWord:
Which are these changes?
[Samsung Galaxy Nexus] bsmitty83:
Pretty much my entire mm/ folder of my source lol . im not sure which specific commit breaks it for me , and there are way to many to try to figure out which . I haven't used uksm for a while now , regular ksm is what I'm going to keep .
[Samsung Galaxy Nexus] GilGameshn1:
The ukms thing bring back memories of this kernel ... I can recall when the dev decide to revert the commit and instead using stable one ... Please do not make headaches for yourself ? ... Kms is OK . thanks .? we have the best dev . ?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
OP Updated - 8-30-14

All 3 Versions

- Added Franco's Sound Control

- Removed Dynamic Fsync , Added Fsync control (off/on)

- Added IVA overclocking , thanks to [MENTION=3990075]Pattyboi[/MENTION]

- Updated ksm from mainline linux

- Updated zram , mm , lz4

- Building kernel with Graphite opt on HOST

- Updated Ramdisk thanks to [MENTION=4544860]osm0sis[/MENTION]

- Probably more but its late and my changelog is always on github

( Also osm0sis made up a new AnyKernel Method that contains all 3 kernels that you choose which one to install with a simple file re-name , its on my github , but i plan on adding it to the op soon , along with an updated Anykernel installer that is now compatible from android version 4.2-4.4 )

Enjoy , these seem to be working pretty good , let me know what you think
[Samsung Galaxy Nexus] osm0sis:
Synapse scripts will need an update for the new/old fsync toggle. I'm camping right now so I'll check it out early next week. :)
[Samsung Galaxy Nexus] hdoraemonk:
Stuck at Google logo. Flash over 8-15-14-3 of om0sis :(
[Samsung Galaxy Nexus] Unzitron:
Sad day... Google logo gets boring to stare at.
[Samsung Galaxy Nexus] krweby:
DirtyV-UR hung at Google logo.
[Samsung Galaxy Nexus] sergialess:
Same here. Thanks anyways for the effort.
[Samsung Galaxy Nexus] CommanderDuplex:
+1 stuck on Google Logo

Edit:

Omnirom
[Samsung Galaxy Nexus] osm0sis:
And what ROMs are all of you using?
[Samsung Galaxy Nexus] Edward Stanbury:
its strange im getting the occasional power button spam to wake phone after it hits deep sleep but if i use double tap to wake it fires up with out a problem :P hahah no clue whats going on there ah well the battery savings are pretty awesome ps using your settings on the normal version not SR
[Samsung Galaxy Nexus] bsmitty83:
Try this

https://www.dropbox.com/s/w9bwscztd4id1o2/SmittyV3-Linaro-fixedinstall.zip
[Samsung Galaxy Nexus] Firewalker1980:
Nephilim, I've tried a few versions of the DirtyV kernel with your settings and I've experienced the lag on screen wakeup too, but only if you wait a little before waking the device. Turning it off and on again without a pause does not give me any lag, but if I wait a while, I have to press the powerbutton 3 times before it comes on.
[Samsung Galaxy Nexus] vlc_marcos:
[MENTION=4608636]bsmitty83[/MENTION] - let me see.

well it work. i just boot the phone. thanks. now i will try and leave my feedback. :)
[Samsung Galaxy Nexus] Edward Stanbury:
omg you have an X5! :DD i use to own one of those bad boys then it died on me just as blefish was releasing JB :( sorry for the OT your sig got me excited ;) hahaha
[Samsung Galaxy Nexus] Nephilim:
Yea, haven't had that once on SR2 linaro. Maybe the mix of LiquidSmooth has something to do with it, don't know but I love this kernel and it will stay on my device as a backup while trying any new update from smitty! :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Firewalker1980:
Running DirtyV2-SR-Linaro now on AOSPA beta 4. I'll change to Mpokang cause I wanna test these settings from Wavedashdoc (see http://xdaforums.com/showthread.php?t=2573665&page=21) but I'll test a new release of DirtyV with your settings and see how that goes. I'm sure it'll get sorted :)
[Samsung Galaxy Nexus] fracama87:
No wake up lags here on cm-remix... Maybe it's related to aospa rom...

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Charmacas:
Holding the power button for a second wakes the device up. Every time! :) Try it out guys! ;)
[Samsung Galaxy Nexus] Edward Stanbury:
Perfect ! Thanks :)
[Samsung Galaxy Nexus] Rushead:
Actually, it would lead to even more questions such as, "What's this FAQ app all about?" "Can I delete it?" "My phone won't wake up in less than a nanosecond. Is the FAQ app causing this?"

Sent from a flashead cracker.
[Samsung Galaxy Nexus] pkgnex:
I have the power button issue on V2 bigmem linaro as well - with either stock or Neph's settings, and with SR on or off.

Yes, holding the power button for about a full second works, but it's still something that should be figured out an corrected, if possible.
[Samsung Galaxy Nexus] bsmitty83:
Haha you'd need an FAQ app for your FAQ app
[Samsung Galaxy Nexus] bsmitty83:
I would love to , in fact that was the whole point of my last test zip . I know the other kernels suffer from it . but I was trying to see if I corrected it or not . that's what all these posts are about
[Samsung Galaxy Nexus] pkgnex:
Sorry - I missed the test zip post in my haste to come up to speed.

BTW - No offense intended... just giving my opinion on the long-press as a work-around. Thanks for your all your efforts.
[Samsung Galaxy Nexus] TheMan0790:
The test build kernel, so Linaro V3, works very well for me so far. Awesome!

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] Nephilim:
Technically not v3 because its smittys test build. :p

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Hey I need some way to keep track of everything . lol
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4608636]bsmitty83[/MENTION]

I have a little problem - i can't set min Screen Off CPU clock lower than 350MHz (on Dirty_V-SR v2).

I use Trickster and when i choose 230 or 180MHz and click "apply" then clock automatically back to 350MHz.

Should i share some logs?
[Samsung Galaxy Nexus] bsmitty83:
Not sure , I just flashed same kernel and all freq stick . try wiping trickster app cache
[Samsung Galaxy Nexus] faber_93:
same here! :/
[Samsung Galaxy Nexus] AquilaDroid:
First time we've had a consensus here?

From my Nexus 5
[Samsung Galaxy Nexus] bsmitty83:
Not sure what happened , looking into it now
[Samsung Galaxy Nexus] bsmitty83:
OP FIXED , ALL 3 KERNELS SHOULD BE GOOD TO GO .

Sorry about that fellas
[Samsung Galaxy Nexus] rajputrajat:
Yep, working fine now... :beer:

Thanks a lot Sir
[Samsung Galaxy Nexus] Unzitron:
Omni
[Samsung Galaxy Nexus] cujo6801:
DirtyUnicorn

Sent from the "DOG" pound
[Samsung Galaxy Nexus] hdoraemonk:
Working on PA, thanks :good:
[Samsung Galaxy Nexus] GilGameshn1:
As always working ... LS / Carbon / Slim ... Thanks bro .?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Oehr:
dirtyunicorns + f2fs + encryption + dirtyv 14-8-30 = no love

im stuck in a boot animation of the rom and never get to the point where I enter the password for decryption.

also, it takes forever for the animation to actually start. first minute or so is a black screen.

[MENTION=4544860]osm0sis[/MENTION], we need your bright ideas again :D
[Samsung Galaxy Nexus] bsmitty83:
I used the ramdisk from 8.15.14 , I'm working on the new ram disk , not sure but I thought encryption was fixed on 8.15 , if not it should be in the next release

And DU takes that long to boot anyways , I'm using it now .
[Samsung Galaxy Nexus] Oehr:
it was broken on 8-15, but osm0sis fixed it and comitted the changes to the source. afaik, 8-15 never received an update to fix f2fs encryption, so i am back on osm0sis testbuild, which should only marginally differ from the original 8-15 release.

also, DU does take a bit to boot, but with 8-30, it really does take a minute for the animation to actually start. with the working one by osm0sis, it appearrs within the first 10 seconds minimum.
[Samsung Galaxy Nexus] bsmitty83:
OK should be fixed next upload . osm0sis did fix encryption but I didn't use the latest ram disk to fix the booting . I'm going to try to get the new ram disk out . I'm testing a few things to it now
[Samsung Galaxy Nexus] Rushead:
Had another GLBL. Awoke the phone to a message saying no network, sim card was removed, network will return after reboot. Hit reboot and got a GLBL. After restarting the phone, all is fine. Rebooted successfully since then. On Shiny, Smitty 8-15
[Samsung Galaxy Nexus] osm0sis:
I might be camping but I'll still take a couple minutes to hook a brother up. ;)

http://v.ht/osmod

[MENTION=4608636]bsmitty83[/MENTION] No issues with my latest updates booting on anything, including Omni. :p
[Samsung Galaxy Nexus] bsmitty83:
I'm pretty sure the next update will be on the any kernel install method .

[MENTION=4544860]osm0sis[/MENTION] did masterful things to both the ramdisk and anykernel installer . I'm very grateful that he took the time out to make DirtyV far more than just my personal , daily driven kernel . I've been using his new any kernel installer myself the past week or so and its great . I'm working on some things now and will try to get at least a SmittyV out in a little bit .
[Samsung Galaxy Nexus] Oehr:
hitech camping, heh?

anyway im grateful for all this work you put into this - especially since i seem to be the only f2fs encrypting tin foil hat out there! thanks [MENTION=4608636]bsmitty83[/MENTION] and [MENTION=4544860]osm0sis[/MENTION] :good:

P.S. yes, it works :D
[Samsung Galaxy Nexus] osm0sis:
Haha no glamping or anything, just happen to have a good H+ signal for once. ;)

And honestly Smitty, it was already more than your daily driver when I showed up, but I've always liked boot.imgs personally and have been happy to lend what little I've learned along the way here on xda to maintaining a working cross-ROM ramdisk for your excellent kernel. :)
[Samsung Galaxy Nexus] randommmm:
If I want to make everything exactly the same as your put in the OP except changing the ASRAM to a different number ( I want to find a optimize between 748MB - 688MB to fit my need ), which branch I should compile with?

Is the available RAM size is the only difference between those 3 builds?

**edit**

Is the present builds built with Linaro 4.7 toolchains?
[Samsung Galaxy Nexus] freshgiammi:
The branch you should compile is DirtyV-f2fs. The defconfig is SmittyV. To change the asram you need to change the line #define OMAP_TUNA_ION_HEAP_TILER_SIZE (SZ_1M * 31) in board-tuna.c from 31 to whatever you want. 31 is 748mb, 81 is 688mb. However, reducing that gives no improvements. I think the only change bsmitty did is to add 5mb for the google camera.

Also, everytime he pushes something to the repo, you're supposed to sync your local files with the remote ones from github.
[Samsung Galaxy Nexus] hdoraemonk:
I have a question? Why battery still drain while charging and screen on? :(
[Samsung Galaxy Nexus] GilGameshn1:
It could be your charger cable or charger itself that corrupted ... Everything fine here .
[Samsung Galaxy Nexus] randommmm:
Thank you very much.

In fact, the reserve RAM is also related to the hardware video play-back, the less the reserved RAM it is, the weaker HW play-back will be. And I can accept the sacrifice only when it doesn't go too much... ( I got some AVC-1 videoes in different scale and parameter, and I'll try them one by one when I've done buiding.:laugh: to see how the HW play-back feature is affected... )
[Samsung Galaxy Nexus] bsmitty83:
To change ram versions , I added a build time configurable to change what reclaim you want back . when you "make menuconfig" it will be under System type / ram reclaim .

Also no toolchain is set from make file. You have to add it yourself or manually set it in your terminal shell .
[Samsung Galaxy Nexus] randommmm:
Thanks. I want pretty much the same you provided in OP, just the RAM is changed, so would you tell me what toolchain you use to build currently?
[Samsung Galaxy Nexus] bsmitty83:
Linaro 4.9.1

Specifically the toolchains built by [MENTION=4825437]Christopher83[/MENTION] . you can find them here

http://xdaforums.com/showthread.php?p=55149136
[Samsung Galaxy Nexus] pianistaPL:
Does 8-30-14 build have latest Linaro 4.9.2 2014.08? 8-15-14 version has a little bit outdated Linaro 4.9.1 2014.05.
[Samsung Galaxy Nexus] randommmm:
[IMG="haha"]http://i763.photobucket.com/albums/xx277/dindogrr/Screenshot_2014-09-01-01-05-40.png[/IMG]

Thanks. [MENTION=4608636]bsmitty83[/MENTION] [MENTION=4986658]freshgiammi[/MENTION]

Hello, world!
[Samsung Galaxy Nexus] Jar3112:
[MENTION=4608636]bsmitty83[/MENTION] in latest build WiFi ap seems not to work

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Should be working , I tried it out , worked for me . try flashing the kernel again , and wiping /cache .
[Samsung Galaxy Nexus] bsmitty83:
Still 4.9.1 , I just haven't downloaded the new one yet [emoji14]
[Samsung Galaxy Nexus] Jar3112:
Tried, no luck. Dirty-V.

https://www.dropbox.com/s/fzp6wjxzl2107yc/log1.txt?dl=0

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Jar3112:
Update: WiFi hotspot correctly working on smitty but not on dirty

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
SELinux on the boot.img command line? Without it tethering breaks on CM-tree ROMs.
[Samsung Galaxy Nexus] Nephilim:
Happy Labor Day folks! I will be celebrating by sitting in my pajamas on my couch playing Infamous: Second Son on my PS4 all day. :D
[Samsung Galaxy Nexus] TheMan0790:
I will be watching my Argos in some solid CFL action....nah, I'm getting ready for my Broncos against the Colts! (yes, I live in Toronto).
[Samsung Galaxy Nexus] amd_h4x0r:
I'm still getting bootloops on 8-30, but I've learned to just live with it. It's a pretty small tradeoff for keeping this phone running like a champ.
[Samsung Galaxy Nexus] osm0sis:
Updated 8.30 boot.img with fixed Synapse: http://v.ht/osmod

Edit: And reuploaded to add androidboot.selinux=permissive to the boot.img command line, which should fix Wi-Fi tethering on CM-tree based ROMs.
[Samsung Galaxy Nexus] dbt816:
Been running the 2014-07-26 version of FML ROM and the last few SmittyV kernels up to the 2014-08-15 release with little to no issues. Upgraded to SmittyV 2014-08-30 and I've had SODs while the phone sits on the charger overnight for the last two nights (thankfully I usually wake up before my alarm!). I've also noticed that the GPS performance (i.e., time to obtain a location lock and accuracy) has degraded as well. Unfortunately, there was no forensic data to help troubleshoot, so this is really just an FYI.
[Samsung Galaxy Nexus] osm0sis:
Did you try the one above with my updated ramdisk?
[Samsung Galaxy Nexus] tripfish:
I was on Shiny ROM for some weeks. Flashed at the beginning Dirty_V and got often bootloops (google logo) when rebooting the phone. Thought it was a shiny problem. Now I'm on PA ROM with Dirty_V (8-15) and here the same.

Is it possibe to fix it?

Thanks very much!
[Samsung Galaxy Nexus] GilGameshn1:
Booting to recovery and reboot could make the trick ... It could help . ?
[Samsung Galaxy Nexus] Punkiderma:
I had the first bootloop after a very long time! (Latest two releases)

Again, my phone became extremely slow, so I've rebooted and this time I had a bootloop!
[Samsung Galaxy Nexus] Jar3112:
I can flash it with flashify, am I right?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
You got it! Also I've written image flashing into Synapse, and made my own "Flashify" flashable zip script (in my Odds and Ends thread) that flashes the first image found in the same directory as it; lots more options than fastboot now! ;)
[Samsung Galaxy Nexus] Unzitron:
I've been putting off updating OmniRom nightly until I get an .zip to drop in opendelta/flashafterupdate. Will the flashify script mentioned by [MENTION=4544860]osm0sis[/MENTION] make that kind of zip?
[Samsung Galaxy Nexus] osm0sis:
I'm not sure how the flashafterupdate thing works, but you should put my Flashify zip with whatever boot.img you want and let us know if it works! ;)
[Samsung Galaxy Nexus] dbt816:
If that was directed at me, I just loaded the one above :laugh:
[Samsung Galaxy Nexus] Unzitron:
Flashafterupdate just flashes you kernel automatically after the opendelta update. Does the script just make an update.zip?
[Samsung Galaxy Nexus] osm0sis:
Well, technically it flashes, in order, whatever you put in there. I meant I just didn't know how it goes about that. My script looks in its own directory for the first boot (or recovery or baseband) image it finds and flashes it directly, so provided flashafterupdate doesn't move the zips around it should work, hence give it a try and let us know for sure. ;) :)
[Samsung Galaxy Nexus] djsarab:
Brilliant update, had my first normal reboot after ages..no more bootloops..lol. Guess now the High performance sound is OVA OC, can't get the Volume boost to 2 though.
[Samsung Galaxy Nexus] freshgiammi:
Most probably the values are 0= disabled, 1= enabled. More than 1 should set the value to 0.

Iva* OC is something else ;)
[Samsung Galaxy Nexus] djsarab:
LOl..yeah that makes sense. Since, high performance sound option is missing I thought IVA OC is an upgrade. Btw, what is IVA ?
[Samsung Galaxy Nexus] Rushead:
Interplanetary Vulcan Alliance
[Samsung Galaxy Nexus] Jar3112:
Something strange happened today. I found the phone turned off, without a reason (it was in my pocket).

Here is last_kmsg, could it be kernel related? Cm11 snapshot m9

https://www.dropbox.com/s/0kdsbzhqhfftv2j/last_kmsg?dl=0

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
How long was it on? That log only goes for 100 seconds. :confused:

There's a DSI error but I doubt that's it when the log is so short.
[Samsung Galaxy Nexus] Jar3112:
Maybe something weird happened... Anyway i Just got a reboot, while browsing Facebook. https://www.dropbox.com/s/0kdsbzhqhfftv2j/last_kmsg?dl=0

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Nice little stack trace and dump in that one for [MENTION=4608636]bsmitty83[/MENTION] :good:
[Samsung Galaxy Nexus] freshgiammi:
IVA is Image Video Audio. Basically what decodes all media stuff.

CORE is GPU, while MPU is the processor.
[Samsung Galaxy Nexus] Punkiderma:
so IVA OC will also affect, for example, the time took by camera to shoot a picture?
[Samsung Galaxy Nexus] freshgiammi:
It could. However, i don't think the improvement would be big.You probably won't even notice the change.
[Samsung Galaxy Nexus] pattyboi:):
CORE can also sometimes count as the main device bus/ram :P
[Samsung Galaxy Nexus] cmoG530:
If it's not too much & if you have the time, could you make a Big Ram version of this? I flashed this and totally forgot that I can't watch YouTube or Twitch.lol
[Samsung Galaxy Nexus] bsmitty83:
I'll try to get some new versions out tonight . I'll be using any kernel for this drop so it should be what your looking for
[Samsung Galaxy Nexus] cmoG530:
Sweet. Thanks. :)
[Samsung Galaxy Nexus] sergialess:
Hi. Sorry for the OT, but now I have a big problem. I've just done a NANDROID backup with your F2FS-TWRP recovery.

It seems that /factory partition (efs) was in EXT4 while the rest were in F2FS. The /factory backup resulted surprisingly just empty!. Then when I restored that NANDROID backup, my /factory partition was first deleted. So now I don't have efs and I don't have a copy. I'm with a generic IMEI and my network tells me I'm offline and I don't know what can I do...

Why /factory was not successfully backed up?

Any help will be appreciated.
[Samsung Galaxy Nexus] bsmitty83:
OP updated :

- Switched to anykernel2 install , it does everything the ramdisk version does , but is compatible from android version 4.2 , 4.3 , and 4.4

- some minor updates to zram and ksm , few others .....

- bulit with Linaro 4.9.2 GCC

as always , let me know how their working .

Reminder , we all know by now , but make sure you dirty flash your current ROM before you flash the Anykernel package

(Also if your simply looking to update from the last build , you can flash this on top of my ramdisk builds and it should be fine )
[Samsung Galaxy Nexus] osm0sis:
Since I made our tweaks bulletproof, yeah you can likely get away with dirty flashing our AnyKernel2 zips over our own ramdisk. As a general rule for AK2 I probably wouldn't recommend it though, since who knows if the dev has added all the tweak checks correctly like I have. :)

Definitely still don't flash it over another custom kernel.

P.S. Can you make those say AK2 buddy? I feel like it should be differentiated from Koush's simple old AnyKernel. ;)
[Samsung Galaxy Nexus] Jar3112:
Can someone link to the previous Dirty-V version? I'd like to flash the latest anykernel version but I accidentally removed the normal version to update from it

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tripfish:
I'm on PA ROM with Dirty_V (8-15). Noticed yesterday, that the bluetooth connection to my BT car headset is lost, as soon as the display goes off.

Now I've restored my Shiny ROM NAND backup with Dirty_V (8-15) and tried it today again... And here the same. Display off - BT connection lost.

Is it possible that this is caused by the kernel?

I'm using the flight mode at night. I don't know if this can be related to.
[Samsung Galaxy Nexus] KreNtal:
So many apps are force closing after installing latest dirtyV SR and the whole phone is lagging too much. I dirty flashed the rom (cm11 M9) and after that the new AK2 kernel.
[Samsung Galaxy Nexus] osm0sis:
No issues with force closes with my testing on Carbon (CM-tree based). Can anyone confirm?
[Samsung Galaxy Nexus] Jar3112:
Latest dirty, smooth and no problems

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] KreNtal:
I switched back to previous version, I will let you know
[Samsung Galaxy Nexus] mrgnex:
When you download the new version just replace the date in the URL with a previous version.
[Samsung Galaxy Nexus] KreNtal:
Lagging and force closing seem to be gone on previous version... Maybe a bad installation?
[Samsung Galaxy Nexus] osm0sis:
I'd definitely like to hear if anyone else running CM11 has a similar experience with the AK2 zip. I tested 8.15 AK2 style on Carbon with no issues and I'm running 9.4 now with a ramdisk and it's speedy.
[Samsung Galaxy Nexus] nonoperez:
Working with PA

SR AK2 working perfectly in lastest PA. Smooth and speed with no reboots atm.

Tx dev.
[Samsung Galaxy Nexus] omniatic:
No issues with Dirty 9/4 on CM11 M9. Still fast, still smooth.

Flashed over the last build, didn't reflash the rom, just had to reset the settings in Trickster.

All good.

Sent from my SM-P605V
[Samsung Galaxy Nexus] bsmitty83:
When I make a backup I don't even have the efs option in my twrp so idk how that happened , but there are quite a few guides on how to get your imei back . pretty sure a restore to stock from fastboot using the factory images will work .
[Samsung Galaxy Nexus] sergialess:
Thanks for your prompt response, but no luck. I've flashed via ODIN several factory images (from 4.0.4 to 4.3.0) and the IMEI remains still the same (0049...). I made and appointment with Samsung Support and see what they tell me. Stupid of me that I didn't make/find any backup of EFS folder...