yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
Try restoring to stock and then this

http://www.droidviews.com/backup-and-restore-lost-imei-on-samsung-galaxy-devices-without-root/
[Samsung Galaxy Nexus] sergialess:
I no longer have much faith in any recovery method, but I will try everything said in that page. Thank you very much again!.
[Samsung Galaxy Nexus] bsmitty83:
OP Updated

TWRP V.2.8.0.0

Fixed MTP ( tested myself , it works OTG should also work but i havent tested )

F2FS is now native , under wipe/ advanced wipe/ repair or change filesystem :good:

I HIGHLY RECOMMEND UPDATING TO 2.8.0.0. EVERYTHING WORKS AFAIK .
[Samsung Galaxy Nexus] osm0sis:
Basically you should never ever touch efs unless it's to back it up.

Not part of stock images since it's device-specific. He needs to restore an old Nandroid and copy the files from his /radio directory.

Edit: check out this OP and my post on the last page, http://xdaforums.com/galaxy-nexus/general/howto-backup-efs-partition-t1352371
[Samsung Galaxy Nexus] KreNtal:
I will try again maybe when m10 will be released, I will let you know. If it will happen again I will send you a log.
[Samsung Galaxy Nexus] osm0sis:
You could try flashing it over our ramdisk, which if it works would point to a weird incompatibility with CM11's current ramdisk that AK2 exposed.

And if that doesn't work, it might be time for a clean flash. :good:
[Samsung Galaxy Nexus] sergialess:
Nah, the problem is not just that I don't find any backup (if I ever made them), but not having the original /efs folder. At least I can do calls for the moment (but eventually my carrier could ban the generic IMEI).

Thanks anyway!.
[Samsung Galaxy Nexus] KreNtal:
I will try later to re-download the newst kernel and flash it over the old one, otherwise I will proceed with a clean flash. Thanks for suggestions.
[Samsung Galaxy Nexus] osm0sis:
Restoring an efs backup, or copying the files from /radio on a previous backup of userdata will restore your efs partition to the /factory (not /efs on our device) directory and IMEI. Go read those links. I didn't post them for nothing. ;)
[Samsung Galaxy Nexus] bsmitty83:
Can someone who uses otg in recovery download and install the latest twrp in the op to see if it mounts or not . I don't get the "unable to mount otg " message anymore
[Samsung Galaxy Nexus] sergialess:
While it's true that /data/radio contains the current IMEI data, I don't have any previous backup of data pulled out of the phone :rolleyes:

And I've read your link, but that method assumes you have a copy of the original nv_data.bin. Bad luck for me today... :crying:
[Samsung Galaxy Nexus] osm0sis:
Didn't you start by saying you took a backup? /radio should be in there. Doesn't necessarily need to be off-device.
[Samsung Galaxy Nexus] sergialess:
...That was before I flashed via ODIN some factory images, some hours ago.

I did it because I've read that factory images could restore /factory. Naive me... I screwed it up...
[Samsung Galaxy Nexus] motorazrv3:
This device is old and it depends since when you bought or used it but you will say that you never made a backup from which you could restore your efs partition?

If not than you have got really bad luck! If you had red the Faq of our device than you should had noticed how important this efs partition is!
[Samsung Galaxy Nexus] osm0sis:
Shiiit. Sorry bro. :(

Take it to a repair shop. When all else has failed I've heard of them being able to restore it somehow.
[Samsung Galaxy Nexus] Jar3112:
I'll try in a few hours

Sent from my Galaxy Nexus

---------- Post added at 07:26 AM ---------- Previous post was at 06:52 AM ----------

I noticed a message in the new recovery, unknown filesystem "datamedia". What does this mean?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Jar3112:
I confirm USB otg working on newest recovery. Still puzzled about the error message though

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Not sure , but I was getting that message with my last recovery build so I just ignore it .
[Samsung Galaxy Nexus] Jar3112:
Anyway mission complete. I did a full backup on USB otg. Didn't try to restore it but it shouldn't have problems, I didn't see any error

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dbt816:
Anyone else having UI lag and lockups with the 9/4 version (SmittyV AK2)? I've tried on 2 different ROMs (one loaded via clean install) with the same result. Nothing of use in dmesg output...the only thing logcat shows is the resulting UI input errors from windows not being responsive for several seconds. Reverted back to the AK2 build of the 8/30 version from [MENTION=4544860]osm0sis[/MENTION] and have had no issues.
[Samsung Galaxy Nexus] Punkiderma:
I also have them sometimes, but I believed it was rom related since I didn't clean flashed
[Samsung Galaxy Nexus] Nautilus74:
Same problems with DirtyV ak2... :(

Instead OK with previous version....

Instead, the thing that does not work anymore is TETHERING...from several previous versions now! :(
[Samsung Galaxy Nexus] osm0sis:
I had that with the 9.5.14 test build I had up, but it seems to be resolved with 9.6.14. zram was missing an include.

Not sure why you'd see issues like that on DV (unless you're using zram), I didn't have any on SR. As for tethering, I just tested on Carbon and it works fine now that the selinux permissive is set. Can you go to /system/bin and verify hostapd has been replaced, whether you're running selinux enforced or permissive and also add some bug reporting basics like what ROM and build you're on?
[Samsung Galaxy Nexus] bsmitty83:
I'm tethered now as I forgot to pay the cable bill lol . works fine .
[Samsung Galaxy Nexus] pianistaPL:
The latest build is working great with Omni FML, thanks smitty :)
[Samsung Galaxy Nexus] motorazrv3:
I am blind. Where can I download dirty v 30.8. Can't find it on dev-host.
[Samsung Galaxy Nexus] Oehr:
thanks a bunch for the TWRP update: Now it finally works with encrypted F2FS partitions!

However, im getting following error right after starting the recovery in the log: "E:Unknown File System: 'datamedia'

Guess it tries to mount too early there ^^

Also, mounting the encrypted partition is very slow when I compare it to EXT4, but as long as it works, I don't really care <3

P.S. by ui.zip files is being ignored - why?
[Samsung Galaxy Nexus] bsmitty83:
Not sure I don't use a theme , but I think it has to be 2.8 specific ? Sorry for answering your question with another question but its all I got lol [emoji39]
[Samsung Galaxy Nexus] Oehr:
might be. theme is intended for 2.7.x.x, though I dunno what exactly changed for 2.8.0.0 to render it incompatible. for starters, 2.8.0.0 isnt even up on the official TWRP2 site yet, not to mention a list of changes since 2.7.1.0. or are the two changes you mentioned all that has changed since then?

I take it the bump to 2.8 was on you? If it was - maybe you shouldnt have, as once the official 2.8 is out, it might get confusing.

aaaaanyway: neither should render the theme incompatible. unless there is some version incompatibility flag set somewhere. and that I dunno. [MENTION=4544860]osm0sis[/MENTION] should have run into the same issue as me, as hes using the same theme.
[Samsung Galaxy Nexus] bsmitty83:
I simply built twrp from Omni's git . I didn't change a thing except built it in aokp instead of omni but yea if it says 2.8 it's not from me . when I modified the last twrp I seperated it from mainline by an incremental bump to 2.7.1.1
[Samsung Galaxy Nexus] osm0sis:
Haven't upgraded. I'll take a look at it tomorrow maybe to see if I can reproduce it. By that error message, it might be possible that it's mounting /data/media too late to load the theme.
[Samsung Galaxy Nexus] bsmitty83:
Your not blind , but I'm lazy and haven't been keeping up on my old links , just find the link for whatever kernel your looking for and replace the date and you should be able to download it
[Samsung Galaxy Nexus] osm0sis:
By the way, anyone using Xposed and Chrome should get the ChromePie module they just featured on Android Police. It adds the Stock/AOSP Browser "Labs" slide-in pie controls to Chrome. Totally made my day since that was the one thing I hated to lose by switching to Chrome way back. :D
[Samsung Galaxy Nexus] Oehr:
well, the reload theme button does nothing...
[Samsung Galaxy Nexus] JuanG:
Hi! I am having some micro freezing with the latest version of Dirty - V (9-4-14). I use shiny ROM. Someone else?
[Samsung Galaxy Nexus] cujo6801:
New Adaway if anybody needs it....

https://www.dropbox.com/s/hdtxe96mg7tx7tx/AdAway- Block Advertisements (2.9.1).apk?dl=0

Sent from the "DOG" pound
[Samsung Galaxy Nexus] peterlemonjello:
Also available via F-Droid
[Samsung Galaxy Nexus] osm0sis:
The theme definitely works for me on the posted unofficial 2.8.0.0, but I'm having trouble with adb staying active and the screen timeout blanking the screen and not being able to bring it back.

The splash has been taking a long time since I switched to f2fs in general, which causes the screen to timeout sometimes directly after boot, but on FML-TWRP I was able to bring it back by tapping and waiting for the "dim" again. Touches don't seem to register anymore when it happens on Dirty-TWRP. The blanking issue happens regardless of theme.

[MENTION=3390093]MWisBest[/MENTION] [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] Unzitron:
Does it work with Chrome Beta?
[Samsung Galaxy Nexus] osm0sis:
Yup!

My only critique is that by default it has no settings. Check the thread though, someone posted screenshots of a (nearly) default AOSP Browser setup: http://xdaforums.com/xposed/modules/mod-chromepie-add-pie-controls-to-t2869531
[Samsung Galaxy Nexus] Oehr:
had that screen timeout issue as well. dunno about adb, as i didnt use it yet within the new twrp. as for the theme: another encryption related bug? after all, the theme is on the encrypted partition. but the reload theme button should be there for a reason (its not working).

care to test the button for me: rename the zip, reboot twrp, rename zip back again, reload theme. does that work for you?
[Samsung Galaxy Nexus] osm0sis:
Deleting /sdcard/TWRP/.twrps fixed the immediate timeout issue, I guess because I had the timeout at 40s and by default it's 60s. Still can't bring it back once it times out though, so I guess registering screen-off touches is broken in this build. Of course if you're okay with your screen staying on you can workaround it by disabling the timeout altogether.

Reload theme freezes the screen briefly but touching it brought it up correctly! Are you sure you're using z13s1g's latest zip? Maybe delete .twrps as well to see if it resolves anything for you. :good:

Anyway, back to FML-TWRP for me since I rely on the timeout to avoid burn-in when I'm doing sdcard backups. :)

P.S. Something else odd I noticed with the "dimming" that happens before the timeout: If you touch it while dim the screen becomes very bright, almost oversaturated, and the hideous yellow tint goes away entirely. Too bad it can't look that good all the time or I wouldn't be so loathe to use TWRP's default theme! ;)
[Samsung Galaxy Nexus] Nautilus74:
selinux is permissive,

hostapd was not replaced (how solve it?)

in use: Liquid unofficial 9/3
[Samsung Galaxy Nexus] GilGameshn1:
Something very good happened to DirtyV . Apps pop ups is very fast . What a performance ... Nothing to report in 2 days . Thanks [MENTION=4608636]bsmitty83[/MENTION] [MENTION=4544860]osm0sis[/MENTION] for his ramdisk . ?
[Samsung Galaxy Nexus] osm0sis:
You can manually rename /system/bin/hostapd to hostapd.dvbak, then copy ours in from /sbin/hostapd.

Anyone else on that ROM who can confirm that's a problem? Can you take a look and see if there are any other indications that /sbin/dvbootscript.sh isn't running?
[Samsung Galaxy Nexus] Nautilus74:
i've exchanged yours hostapd with the original , but wi-fi ap (in addition to not work anyway) now do not even active....

Tethering usb works fine...

Wifi ap works normally with Fancy and same Liquid instead...
[Samsung Galaxy Nexus] bsmitty83:
Did you set ownership and permissions ?
[Samsung Galaxy Nexus] Oehr:
i dunno, but this kernel revision yields very poor performance for me as well. ranging from microfreezes to just a sluggish performance. this morning, my phone was actually unresponsive and i had to reboot it completely. never happened with one of the earlier builds:crying:
[Samsung Galaxy Nexus] pvkiniyan95:
Just in to say that 9/4 has many freezes in 4.3 so I went back to 15/8 osm0sis combined zip pack and happy with it
[Samsung Galaxy Nexus] midnightdevil66:
No issues here on smittyv 9/4
[Samsung Galaxy Nexus] osm0sis:
Seems much improved in the 9.6.14 test build I'm on, but still the occasional temp freeze. They seem to revolve around Google keyboard, typing in Chrome or Hangouts, and it's SmittyV running zram so I'm thinking in my case it's zram/Android coping poorly with OOM.
[Samsung Galaxy Nexus] marko207:
I also have temp freezes and FS, just one till typing this(swype keyboard, carbon rom). Problems started yesterday. 8.15 was very good for me, not a single problem.

logcat: https://www.dropbox.com/s/tdp9r1wl0pdsno5/2014-09-09-19-54-07.txt?dl=0

Search for this in log:

09-09 19:49:35.745

After that is an error(s).
[Samsung Galaxy Nexus] osm0sis:
Did you try 8.30? I'm wondering if it only started on 9.4.

99% 1689/com.nuance.swype.dtc: 0% user + 99% kernel

Good log. Seems kinda suspect huh? :p
[Samsung Galaxy Nexus] marko207:
I'm currently on 8-30, flashed newest carbon nightly. Will see how is going to work in the next couple of days.
[Samsung Galaxy Nexus] bsmitty83:
If it happens again , please grab me a dmesg , not a logcat . dmesg will give more details about kernel processes logcats are good for diagnosing ROM issues .

I'll have a new kernel up probably after sons of anarchy tonight [emoji39] zram was missing a header include so that should work better now . I've been on a test version for a few days now and all is well
[Samsung Galaxy Nexus] 7175:
Running 9-4-14 on Vanir 4.3.1 final with great results so far (constructed with DirtyV 9-4-14 zImage and 4.3.1 ramdisk as osm0sis posted, linked in OP). No problems so far and speed is fantastic, huge boost from default Vanir kernel. I guess I've just never noticed the differences between Vanir and Dirty V. This is blazing fast.

On another note, I tried flashing the new TWRP 2.8.0.0 linked in the OP. When I try to get into recovery, the screen goes black almost immediately. I'm not sure if this has been posted or anyone else has run into this issue. ADB still works, and I was able to "dd" back TWRP 2.7 recovery.img. Pretty weird, never seen this before.

Nice work though, really liking this speed boost to my already fast Vanir 4.3.1 daily driver.
[Samsung Galaxy Nexus] bsmitty83:
It should go into the normal recovery screen after about 20 sec . something with the screen timeout isnt working , probably in my source . so I'll fix that . until then disable the screen timeout
[Samsung Galaxy Nexus] osm0sis:
If you lowered the timeout to ~40s like I did you'll probably need to delete /sdcard/TWRP/.twrps to reset it to 60s so you can get in and disable the screen timeout.

The issue isn't with the timeout, however, it seems to be with it not registering touches anymore once the screen blanks, so there's nothing to wake it back up. :good:
[Samsung Galaxy Nexus] bsmitty83:
Yea there's a line in the device tree that controls wakeups on screen touch , I'm sure I messed/forgot something
[Samsung Galaxy Nexus] osm0sis:
No need, I guess! TWRP 2.8.0.0 official just got released! :)
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4544860]osm0sis[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] After update TWRP to 2.8.0.0 *from this thread) i get a red information when i wipe some partition - "E: Uknown File System: 'datamedia'" However everything is working fine but in 2.7.1.0 i hadn't this information. Is it something bad with my phone? I have f2fs.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] such dmesg, very freeze, wow systemui, so FC!

[ Attachments removed. ]
[Samsung Galaxy Nexus] omniatic:
Tried to download the official twrp. Keeps coming up as 4.65kb. Know where the full file is hiding?

Downloaded it on the computer. Neither the phone or the tablet could get it right.
[Samsung Galaxy Nexus] osm0sis:
Wow. 2.8.0.0 still doesn't add official f2fs support for us. Pretty ****ing disappointed.

I just sent Dees a PM to request it and a quick 2.8.0.1 for us.
[Samsung Galaxy Nexus] EAK128:
Got it from their official site for toro and it was 7.23MB. http://teamw.in/
[Samsung Galaxy Nexus] Jagoflax:
As I'm reading on the official changelog, this is a new feature

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] KreNtal:
So f2fs isn't officially supported? What are they waiting for? ?

I'd love to try that along with the upcoming cm m10 and dirtyV
[Samsung Galaxy Nexus] bsmitty83:
OP Updated : all 3 kernels

-f2fs from Linux 3.17 (now supports nobarrier Mount flag )

-added missing header include to zram should eliminate some issues

overall its runnig good for me , try it and let me know how it works

:p
[Samsung Galaxy Nexus] cujo6801:
SmittyV 9/10 boots just fine on

SlimKat 7.9 toro...

Thanks bro...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] omniatic:
No problems on CM11 M9, either. DirtyV.

Thanks,

Sent from my SM-P605V
[Samsung Galaxy Nexus] Kaemo:
Hey guys! Decided to check out the GNex forum after so many months.

I really, really cannot put into words how much reading this thread makes me happy. Last time I came here, I did and said the same things, and I'm still in disbelief at the amount of effort you put into this project and into the GNex itself.

You guys are my definition of heroes. Even with the hardware restraints, the dropped software support, and the overall age of this device, you're still as active as you were on Day 1. And that feels important to me. It's nice to know there are people out there that go to extremes to support the community and please everyone sometimes completely ignoring their own lives in order to focus on things going forward from a development standpoint.

You ROCK, and I could not be more proud to say I spent hours every single day reading your posts and engaging with people in this forum - and particularly in this thread - until the very last time I held my GNex.
[Samsung Galaxy Nexus] cmoG530:
So far, so good with the latest Vanir nightly. No complaints at all. Thanks! :)
[Samsung Galaxy Nexus] cujo6801:
Yeah the only problem I have with it is now my phone keeps texting me (who's your daddy)

and I have to reply Smitty

And that's not the worst part..

Because then it sends a text saying (that's right *****) :o

Sent from the "DOG" pound
[Samsung Galaxy Nexus] bsmitty83:
Lmao [emoji39]
[Samsung Galaxy Nexus] Hetalk:
lol ... man ... you are awesome :cowboy::cool::highfive:
[Samsung Galaxy Nexus] imam.krismanto:
Twrp 2.8 already support f2fs???
[Samsung Galaxy Nexus] gautam_nexus:
No still no Official support :(
[Samsung Galaxy Nexus] imam.krismanto:
Twrp on first page i mean, still official or support f2fs?
[Samsung Galaxy Nexus] GilGameshn1:
Not official ... It is compiled by [MENTION=4608636]bsmitty83[/MENTION]

And f2fs support .
[Samsung Galaxy Nexus] imam.krismanto:
Already modified to support f2fs?
[Samsung Galaxy Nexus] GilGameshn1:
Yes ... The another alternative is FML twrp . both have f2fs support .
[Samsung Galaxy Nexus] lollipop:
Sorry for my bad english

Today i flashed the lastest unoficial liquid by [MENTION=3927368]poo706[/MENTION] a long side with dirty v 9-10 f2fs but i have a problem my phone freeze every 2minutes about 1sec or 2 .it happen always i try wiping dalvik and cache but no solution.please any idea why ?
[Samsung Galaxy Nexus] Jar3112:
I'm using Dirty-V on cm 11 and absolutely no problem. Rom issue?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dbt816:
I've had a few mini-lockups with the 9-10 version, but it's almost insignificant, especially compared to the 9-4 version. I still cannot correlate the mini-lockups to anything in dmesg output. The closest I can get are messages tagged with "max17040 4-0036" such as:

max17040 4-0036: online = 1 vcell = 3973750 soc = 76 status = 1 health = 1 temp = 240 charger status = 0

But again, I'm not sure if there is any relationship.
[Samsung Galaxy Nexus] KreNtal:
Some freezes even for me on latest version but abolutely less than the previous one.
[Samsung Galaxy Nexus] cmoG530:
Getting freezes here as well. Will try to bring more info later today.
[Samsung Galaxy Nexus] GilGameshn1:
It is very important that dirty flash your ROM and flash this kernel . you can read this few page back that [MENTION=4544860]osm0sis[/MENTION] mentioned this . could solve some problems . the lags become very few in time and count in this version . ?
[Samsung Galaxy Nexus] dbt816:
Seeing these old SYNC errors again as well:

[10932.071746] dhd_set_suspend: Remove extra suspend setting

[10932.326599] DSSCOMP: dsscomp_late_resume

[10932.326904] omapdss DISPC error: SYNC_LOST, disabling LCD

[10932.327026] omapdss DISPC error: First SYNC_LOST.. ignoring
[Samsung Galaxy Nexus] Jar3112:
Not if you are updating, if I remember..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Nephilim:
Could someone please link me SmittyV 8-30 and SmittyV 9-4? I've been away for some time and the last used was 8-15. Tried using 9-10 last night and I've gotten an excessive amount of random reboots as well as quite a lot of micro-freezes especially when typing or trying to open resource heavy apps. Hoping one of the above mentioned kernels works better.
[Samsung Galaxy Nexus] Nautilus74:
the same problems are also with 9-4 versions ....even more pronounced !

8-30 versions go perfectly ! (but not as fast as the versions in September :( )

But I've only DirtyV-UR version....
[Samsung Galaxy Nexus] Nephilim:
Well if that's the case then I request someone please share the 8-30 SmittyV lol.
[Samsung Galaxy Nexus] motorazrv3:
Really best would be if Smitty will find some time to upload the missing previous kernels to his dev-host. Hopefully nobody will ask again for a link.
[Samsung Galaxy Nexus] D1BB:
Been running 9/10 since yesterday and haven't had a hickup. Over 17 hrs up time. Vanir 4.3.1. with zram disabled.

Edit: started experiencing 1-2 micro-freezes per day.
[Samsung Galaxy Nexus] hcasquet:
Sure, :cowboy:

SmittyV 8-30 HERE (Unified Ramdisk)

SmittyV 9-4 HERE (Any-kernel2 installer)

To download other versions you only have to guess and try the date or version of them, i assume he has all versions uploaded on same server.

Myself, I'm using 8-30 version on my Gnex, and i have to say that if i install a newer version, i get freezes or random reboots. Something isn't right.

As another note, [MENTION=4608636]bsmitty83[/MENTION], I'm using the EXT4 to F2FS Tool by poo706 to convert plain CM11 nightlies to F2FS, and i was using your kernel as boot.img to provide an F2FS kernel.

As it is now, there isn't a boot.img anymore because of Anykernel2 so... I'm afraid of dirty flashing them on top of the older kernel. Will it be possible to provide a UR version of new releases too?

Can we dirty flash the Ak2 versions on top of the older UR versions? I know it will be best to just do flash stock CM11 before applying Ak2, but, as i'm using the EXT4 to F2FS, kernel isn't stock anymore... :eek:

What's your thoughts on this? And of course, thanks for your hard work.
[Samsung Galaxy Nexus] bsmitty83:
It should be fine to dirty flash over the ur kernel just because they both do the same thing . so really all its doing is changing zimages so I say unless you get bad results , go for it .

Next release will be smooth , I eliminated the choppiness I think
[Samsung Galaxy Nexus] Nephilim:
Any idea why I would be getting random reboots? Seems to be only when the device is on the charger.

Sent from my Android 4.4.4 Galaxy Nexus