yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] thelegbra:
just reporting: flashed twrp 2.8.6 maguro using the flash zip option from my previous twrp, nothing is wiped but i cannot mount partitions from recovery, system data sdcard nada. i can reboot into the normal system with no problem.

the console shows the following in twrp:

E:Primary block device '/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata' for mount point '/data' is not present!
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/sbl'
E:Unable to find partition size for '/xloader'
E:Unable to find partition size for '/radio'
E:Unable to find partition size for '/efs'
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to set emmc bootloader message.
E:Unable to mount '/cache'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
[Samsung Galaxy Nexus] wbedard:
[Update: Looking at your post more closely, if you're not able to mount /system, then the following post may not apply to you. It only refers to a minor side-effect of having an encrypted device with a TWRP recovery.]

Same here. As far as I know, this is a known bug in TWRP (see their forums and Google+ community...). While this mostly affects one's ability to flash downloaded ZIP packages, I have been working around it by moving them to a USB stick and mounting that from TWRP.

BTW, I haven't followed this issue too closely but I think it may only be a problem for devices that were encrypted under KitKat but later upgraded to Lollipop. Since TWRP added support for LP encrypted devices a while ago, I suspect that a factory reset followed by re-encrypting under LP might work around this bug. Testing this has been on my "todo" list for a while... just haven't made time for it.

R/

wbedard

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

Hey [MENTION=4608636]bsmitty83[/MENTION] !

Could you also prepare a kernel image with SELinux in enforcing mode as you did before? There's no particular hurry...just whenever you have the time! Thanks in advance...:>)

R/

wbedard
[Samsung Galaxy Nexus] Punkiderma:
How much zram do you reserve? 72 mb?

Also, synapse for me fail to activate zram, it says "sseekbar has failed" and then "can't create sys/block/zram0/" and something liek this. What can I do?
[Samsung Galaxy Nexus] osm0sis:
Reset Synapse from the Backup & Restore page and then immediately reboot. It's usually a leftover settings issue.
[Samsung Galaxy Nexus] Punkiderma:
Is not working, and now I see I can't even save a backup of my config, even if I have the latest busybox

EDIT: I can save profiles, but I get some errors about KSM while backing up
[Samsung Galaxy Nexus] thelegbra:
even though you said that it doesn't apply to me, just wanted to clarify and give info about it :P i have never used encryption at all.
[Samsung Galaxy Nexus] Djalaal:
How did you guys flash the new recovery? Using .zip from old recovery, or using .img in fastboot?

This is quite strange. I've encountered no such issues. In fact, I flashed Full Auto R13 using the new recovery. Other people reported it works fine too. What happens if you flash the recovery.img from fastboot?
[Samsung Galaxy Nexus] thelegbra:
just re-flashed the extracted recovery.img from fastboot.

same errors on twrp console. it can't mount partitions.
[Samsung Galaxy Nexus] bsmitty83:
R13 added to the downloads section (finally) .......
[Samsung Galaxy Nexus] venni:
Also getting the same errors still. No partitions found. /data and /cache are f2fs. Tried flashing the zip and the img through fastboot. Flashing back to 2.8.0.0 returns everything to normal with no data loss. Never used encryption before.
[Samsung Galaxy Nexus] osm0sis:
Try it again, it's finicky. Try Restart Synapse first. Also make sure you're using my latest injector zip. I just uploaded a couple fixes the other day.
[Samsung Galaxy Nexus] bsmitty83:
here you go
[Samsung Galaxy Nexus] nikodr:
If i have the one posted in op can i use an application from google store to change state to and from enforcing?
[Samsung Galaxy Nexus] bsmitty83:
Yes , this is just a version that's set on boot to be enforcing instead of permissive
[Samsung Galaxy Nexus] christianpeso:
Using your Toro 2.8.6 recovery, changing /data and /cache to f2fs shows successful, but after sideloading a ROM and booting back up, all info is still on the phone and I remember when I did this before it actually wiped my device. When I booted back into recovery, /cache and /data were showing ext4 again. Dont think changing to f2fs is working with this recovery.

---------- Post added at 10:53 PM ---------- Previous post was at 10:32 PM ----------

EDIT:

Flashed back a 2.8.4 image with F2FS that I had and formatted /cache and /data F2FS and restarted and all was wiped from my phone as supposed. Booted back into recovery and both are still showing F2FS. Your recovery is not formatting correctly I believe on Toro.
[Samsung Galaxy Nexus] Punkiderma:
Now works without errors, but if I try to disable zram, it reactivate itself automatically XD

Also, how many MBs do you advice to reserve for zram?

Thanks
[Samsung Galaxy Nexus] osm0sis:
I limited the slider within reason for our device already, so feel free to experiment, but Smitty's usual 64 mb is a good amount to increase by without bogging things down.
[Samsung Galaxy Nexus] bsmitty83:
I checked this myself after reading your post and you are correct . I'm not sure why , but going from f2fs to ext is fine , but ext to f2fs does not work even though twrp says it does . the actual partition never changes .

I built the recovery in the same way as my recovery in the dirtyV thread , so I'm not sure why its not changing the fs , even though its saying its using the f2fs tools when repartitioning .

So I removed the recovery as its no different than the one in the twrp thread for all intents and purposes .

If I can get it to actually change the fs , I'll post it .

Thanks for sharing your find BTW , as I was under the impression it was good seeing it go from f2fs to ext4 .
[Samsung Galaxy Nexus] ramosroger:
Hey everybody, ziyans zmod kernel recently got updated to 762mb ram. Could I set a request for full auto kernel to get upgraded to that and be compatible with the 3/30 build
[Samsung Galaxy Nexus] Punkiderma:
Thanks, but now synapse doesn't let me set a lower value than the one before.

If for example now is set on 72 mb, when I try to set it to anything lower it automatically goes back to 72. I tried 128, and now I can't go lower than this. Already tried reset synapse.

What do you think it could be?

Thanks!
[Samsung Galaxy Nexus] osm0sis:
Not sure. I had trouble like that before when I was first working all that stuff out for DirtyV but I'd fixed it. I'll take another look.

A Reset Synapse and immediate reboot should fix it for now.
[Samsung Galaxy Nexus] varadparulekarofficial:
Hey, [MENTION=2769491]wbedard[/MENTION] there is an app on Play Store 'Kernel Adiutor' which can let you change SELinux status from Permissive to Enforcing and vice versa any time..
[Samsung Galaxy Nexus] wbedard:
Thanks for the follow-up! I actually already run that program and have seen that function listed. However, I have not looked into how that function is implemented and there are several avenues (kernel cmdline, init. rc, post-boot su + setenforce, etc?) to arrive at SELinux in enforcing mode from a reboot. I only asked [MENTION=4608636]bsmitty83[/MENTION] to provide the special build since he can compile a version which sets the kernel cmdline, which I believe is the earliest point in the boot process to set SEL in enforcing mode.

Point of fact though, I don't think I specifically asked him and have not checked whether his build actually sets the kernel cmdline or simply modifies the ramdisk with an init.rc entry.

R/

wbedard
[Samsung Galaxy Nexus] bsmitty83:
Its in the command line , I don't use a ramdisk , they are in "any kernel " format .
[Samsung Galaxy Nexus] wbedard:
That's right, I do recall that. Looking through your install script was the first time I became aware of koush's "any kernel" installer...pretty neat! Thanks again for the build...:)

R/

wbedard
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Kernel is not working with the Zmod rom :confused:
[Samsung Galaxy Nexus] Driver007:
Working whit no problems.
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Really ?

After flashing it and rebooting I get a blank screen after the google logo. Taking out out the battery and restarting results in white lines at the bottom of the screen.
[Samsung Galaxy Nexus] netreign:
me too...!
[Samsung Galaxy Nexus] eternal70:
You're not using Ziyan's latest build
[Samsung Galaxy Nexus] Driver007:
Oh I forgot it, using first zmod version and r13
[Samsung Galaxy Nexus] GilGameshn1:
Hey there bro ... First thanks for the hardwork .... And second :D .... Flash it on ZMod ( Latest One ) with every possible known route ,,, And stock in artifact on bottom screen after google logo ... Any solution ... I must add that Zmod stock kernel give 762 mb ram .Thanks in advance ,,,
[Samsung Galaxy Nexus] bsmitty83:
try this
[Samsung Galaxy Nexus] GilGameshn1:
Will do . thanks

---------- Post added at 07:16 PM ---------- Previous post was at 07:07 PM ----------

Ok ... Good news ... Worked finally ... ZMod + FullAuto 13.1 like a fresh air . Big Thanks to [MENTION=4608636]bsmitty83[/MENTION] ... ??????
[Samsung Galaxy Nexus] rajputrajat:
Should we upgrade to this version too...?

I mean are there any other improvements in this version?

Thanks a lot.
[Samsung Galaxy Nexus] bsmitty83:
Only if you are using zmod ROM . it will work on any other ROM but really it was compiled so people using that ROM could use this kernel .
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Awww yea

Been waiting for this [emoji41]
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Flashing it makes my phone near unusable [emoji24]
[Samsung Galaxy Nexus] GilGameshn1:
Something other than that is wrong .. I have Zmod + FA13.1 and my phone flying with least possible battery consumption .
[Samsung Galaxy Nexus] CoDe LaZaRuS:
System is fine with the stock kernel but as soon I flash smittys kernel system slows down to extreme proportions. Will try to provide log files once I get the time :p
[Samsung Galaxy Nexus] bryantjopplin:
A few times mine has done this as well.
[Samsung Galaxy Nexus] Nephilim:
Soooo...... Been awhile. Guess I should go ahead and flash the latest FML rom and Full_Auto kernel....
[Samsung Galaxy Nexus] bsmitty83:
You get one of these yet ....?
[Samsung Galaxy Nexus] Nephilim:
End of the month, Getting an N6 for myself and my mom and a new TV. (Got a substantial promotion at work last week. ;))
[Samsung Galaxy Nexus] Nephilim:
So guys, been having this weird issue today, even since before updating, when on 4G my network either shows "US" or nothing at all under the signal in pulldown, I still have normal Verizon data with no issue but it hasn't said Verizon on the pulldown or lockscreen at all. Any ideas? Also, it reads "unknown" next to network in "about phone" where it should say "Verizon".
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Looking forward to New settings from you :D
[Samsung Galaxy Nexus] rogerkiller1979:
i am having problems to install this Kernel

i have install rom FML: Fork My Life

can i just put the zip file and install from recovery?

or there is other way to do it?

can some one help me install the kernel

sorry for the noob question but i am learning :)
[Samsung Galaxy Nexus] christianpeso:
Yes you are correct. Just install the kernel from Recovery the same way you installed the ROM. What problems are you having? Any error messages?
[Samsung Galaxy Nexus] rogerkiller1979:
no problem :)

install was good now testing

how can i go the the features of this Kernel ?
[Samsung Galaxy Nexus] GilGameshn1:
Trickster Mod app .
[Samsung Galaxy Nexus] wbedard:
Hey [MENTION=4608636]bsmitty83[/MENTION] !

I finally flashed your "enforcing" build of R13 (been waiting on a replacement OTG cable...) and had a question for you. For R13, when I look in the "About phone" screen, it still show SELinux in Permissive mode. I went back and forth btwn R12 and R13 making sure I had the right version of R13 from your post and there's little room for me to have made a mistake. As you have time (again, there's no hurry at all on my part...), could you review the build of R13 you did for me to see if there was some oversight on your end. Just let let me know when/if you find anything. Thanks in advance!

R/

wbedard
[Samsung Galaxy Nexus] bsmitty83:
lol , I'm not sure what happened , I must have made it without running " make clean " and the change never got picked up or something ,

anyways heres the latest I got set enforcing for you , sorry bout that :angels:

I tested this one before I uploaded , so no excuses lmao
[Samsung Galaxy Nexus] wbedard:
Yeah, I've also been caught by not cleaning up my sources before a build. Anyhow, this new build did the trick! Thanks for the quick turnaround and for making the time to test it personally. I really appreciate it...:)

R/

wbedard
[Samsung Galaxy Nexus] Culex316:
By the way, what's different about this 13.1 kernel build? Is it the RAMDISK that's been tweaked or some new commits?
[Samsung Galaxy Nexus] wbedard:
You should follow him over at his Github page. You can see all of his commits, post any issues you may have, etc. Highly recommended... (at least for answering your question!)

R/

wbedard
[Samsung Galaxy Nexus] bsmitty83:
It has a 2nd framebuffer enabled to work with zmod ROM , and some f2fs commits . a few other commits but nothing major .

There is no ramdisk with my kernel , it patches the existing bootimage by replacing just the zimage
[Samsung Galaxy Nexus] Culex316:
I do follow him and I have even forked his kernel to make my own version with some additional compiler flags to satisfy my geeky need to **** with the kernel every so often.

Awesome, thanks for the info! Time to bring my fork up to speed then.!
[Samsung Galaxy Nexus] Punkiderma:
using 13.1 on Zmod, I have micro lags and stutters, and sometimes the phone hangs for some seconds.

I think it's because of a wrong setting of mine, but I don't know what to do.

Could be FSYNC on?

What settings are you using?

Thanks!
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Its the same issue I am facing so returned to stock :(
[Samsung Galaxy Nexus] Nephilim:
I think my mobo is starting to go, I can't seem to connect data transfer to my PC anymore only charge (fast charge is off) and my phone keeps saying "us" or "roaming" instead of Verizon in my pulldown and lock screen even though I have full 4g and am not actually roaming. Can't wait for payday so I can snatch up an N6. I love this community and will still contribute but the fact of the matter is Gnex is showing its age at this point, which makes sense, its 3 generations old.
[Samsung Galaxy Nexus] bsmitty83:
I'm very happy with the n6 , its an amazing device . definitely worthy of a buy if your on Verizon .

My gnex is running amazingly well ATM , since adding discard , inline_data and no barrier mount options to fml's ramdisk for f2fs , there's no lag over time , app installs from play store are lightning fast and without lag .

Since there are so many top devs working on the n6 , I will keep pushing the gnex . I still like the phone and like the community even more , so even if I can't get a working 3.4 kernel , I think I can push the 3.0 pretty hard .

Glad your still gonna be around neph , congrats on the promotion at work , and once you get an n6 , make sure you de-encrypt the sdcard partition before you load it up , cause to do so wipes the partition so it will be pointless .
[Samsung Galaxy Nexus] christianpeso:
Do you guys have unlimited data? Did you pay full price for your devices or upgrade price? Just curious as I am trying to get one as well but of course I am not near my upgrade date and even if I was, I am not giving up unlimited data.
[Samsung Galaxy Nexus] bsmitty83:
I gave up my unlimited data to buy one for 250$ , since I really don't need unlimited , and once my contract is up I'll take this phone to another carrier anyways since it works on all of em .

If I wanted to keep unlimited data I was going to buy a 1st gen motoX developers edition from eBay , since I won't own a phone with a locked boot loader , it was that or a s4 Dev edt .

Plus I heard that Verizon won't activate non Verizon n6's anymore so your options are limited unless you wanna buy one full price .
[Samsung Galaxy Nexus] bryantjopplin:
No they will still activate at some locations. Its where you go really. I paid full price for my n6 to keep my two unlimited lines. I have used 30+ gigs this month.

---------- Post added at 07:37 AM ---------- Previous post was at 07:33 AM ----------

By the way check this out. Go full screen and turn you phone. Vr system on a phone

Time Couch - VR Demo by StressLevelZero: https://youtu.be/7IaYJZ2Usdk
[Samsung Galaxy Nexus] cujo6801:
Pretty kool....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] bsmitty83:
i was referring to this

http://www.androidpolice.com/2015/0...te-one-that-wasnt-purchased-from-the-carrier/
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Guy help me out here. I am gonna upgrade my phone in a month. I live in pakistan and unlike you guys I can't get a flagship phone super cheap on a contract. I have to pay full price. N6 is out of the question with mediocre camera and battery and high price tag. Originally I was thinking of getting a one plus one but as its not avalible here through official channels it costs about 520 us dollars which is affordable but considering that a new version will be arriving soon it's not worth it. What I've decided on is the note 4 which has killer specs, SD card slot and considering that it costs 610 us dollars I can afford it. But i want a developers opinon
[Samsung Galaxy Nexus] past_pluto:
I put in a new USB charging port and that fixed data transfer over USB. The Anker 10ft USB cord is super nice too. Idk what I'd do without it. I seem to have a knack of dropping my phone while charging. I'm on my 3rd USB port and 5th cable.

Is eBay the only place to get Dev editions? I'm looking to upgrade and a friend offered his S3 but I'm afraid any processor under 2ghz won't be worth the cash. The Saygus looks promising if it comes to big red.
[Samsung Galaxy Nexus] Nephilim:
It connects to my PC but gives an error message instead of properly connecting, that along with the odd carrier labeling lead me to believe its most likely the mobo sadly.
[Samsung Galaxy Nexus] zzpianoman:
Perhaps your /factory partition is damaged somehow?
[Samsung Galaxy Nexus] Nephilim:
You think that would cause the carrier to read roaming even though I'm actually connected to Verizon at full 4G?
[Samsung Galaxy Nexus] nikodr:
It could be the usb charge port. I had a damaged one and did the same when i changed it all was fixed. Its cheap too. Unfortunately those phones are four years old. Hardware failures like the one you mentuin are common unfortunately. Pc could not understand what device was connected. And had errors.all fixed now:)
[Samsung Galaxy Nexus] bryantjopplin:
Yep and that part is only 6$ on eBay. Bought me one last year as a spare.
[Samsung Galaxy Nexus] jakiej:
hi there,

thanks for the great kernel!

i've got a minor problem: i see that init.fml.rc initializes /system/etc/init.d

but when I put a shell script (remounting data/cache with f2fs options recommended by [MENTION=4608636]bsmitty83[/MENTION]) in that folder, it doesn't seem to be picked up.

any pointers?

thanks

j
[Samsung Galaxy Nexus] bsmitty83:
I'm not sure how it can be done that way , I just make a boot.IMG with the fstab modified .
[Samsung Galaxy Nexus] bsmitty83:
R14 is up in the downloads section

- added synapse support via anykernel2 installer method ( credit goes to that genius [MENTION=4544860]osm0sis[/MENTION] )

- added wifi drivers and hostapd from linux 3.4 kernel

- been working on EXT4 , since alot of people use it , been working on bringing it up to 3.4+

- enjoy , as always let me know how it is (or isn't) working
[Samsung Galaxy Nexus] rajputrajat:
Running great so far. :)
[Samsung Galaxy Nexus] netreign:
for me.... i have a problem with sim...no connection
[Samsung Galaxy Nexus] h4xx0rr:
Me too :(
[Samsung Galaxy Nexus] eternal70:
Change SELinux from enforcing to permissive. I use kernel adiutor. [MENTION=4608636]bsmitty83[/MENTION] can you reupload the kernel with SELinux permissive by default ?
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Using Zmod rom. No sim connection after flashing this kernel
[Samsung Galaxy Nexus] smsesch:
Runs perfect with AOSP 5.1.

I actually have a better performance on R14.

Good work. :good:
[Samsung Galaxy Nexus] bsmitty83:
I reuploaded R14 with selinux set on boot to permissive , I dont have a sim card in my gnex so i didnt notice lol
[Samsung Galaxy Nexus] Culex316:
I'm on maguro running Zmod 3-31 (the one that required the special 13.1 version of full auto) and I can also confirm that r14 borked my mobile network connection.

I had to dirty flash my ROM again too since **** was force closing like a ***** once I reflashed r13.1

Will it work like r13.1 now that selinux is disabled?

Thanks!
[Samsung Galaxy Nexus] bsmitty83:
It would have worked fine if you had opened up a terminal app and typed” setenforce 0 ” to set selinux to permissive , but yes it will be fine now
[Samsung Galaxy Nexus] netreign:
with new build sim is on.... but everything like google service, google store, keyboard, dialer has stopped....
[Samsung Galaxy Nexus] eternal70:
[MENTION=4608636]bsmitty83[/MENTION] the new build fixed sim. But it makes nfc service, launcher, etc crashed. Please fix this soon !
[Samsung Galaxy Nexus] bsmitty83:
lol , already fixed , try R14.1 in the downloads . :p

is that soon enough ?

DIRTY FLASH YOUR ROM BEFORE INSTALLING TO RESET THE RAMDISK
[Samsung Galaxy Nexus] netreign:
tnx a lot bsmitty83.... very cool
[Samsung Galaxy Nexus] bsmitty83:
Lol yea, I noticed it on my end , thought it was from work I was doing that hasent been posted , then I saw that the permissive R14 was doing it , so I realized it was an ak2 problem , fixed it , but not before reverting a lot of ext4 progress on my end lol , so I'm bummed about losing 20+ commits , but them's the breaks [emoji6]
[Samsung Galaxy Nexus] Culex316:
So it was the ext4 commits that caused all those FC messages?
[Samsung Galaxy Nexus] bsmitty83:
No it was some things in the anykernel2 bootscript that I deleted the commits were fine
[Samsung Galaxy Nexus] Culex316:
I knew it had to be something in the bootscript. I looked through your commits and couldn't find anything that could **** it up.

In the future, could I just extract the zImage from any future kernel release that doesn't include the workaround for the zMod ROM and flash it directly to avoid this mess?