This is a kernel module that disables write protection on the system partition while running the stock kernel.
This module was written by @far2 for the htc one M8 and Desire 816 its source code can be found on his git here: https://github.com/flar2/wp_mod
So credit goes to him.
I have just checked to see if it would be compatible and compiled it against A3UL 1.31.401.3 kernel source. It has been tested to load and work fine with all stock kernels.
This is for stock kernels only and is of no use if you are running JMZ kernel. It will allow you to keep your stock kernel (for better compatibility across regional rom versions) but same as JMZ kernel it allows you to modify the system partition and install mods and fixes that will stick through a reboot without having to do them through recovery.
Install instructions
- download latest supersu-install from here https://download.chainfire.eu/696/Su...etrieve_file=1
- download the attached "A3UL_4.4.2-wp_mod.zip"
- reboot to recovery (TWRP)
- Install Supersu-install.zip (a current supersu install is required as one of it's scripts will load the module)
- Install A3UL_4.4.2-wp_mod.zip
- Reboot
To test if the module is loaded you can open Terminal Emulator and type "lsmod" and wp_mod.ko should be in the list of loaded modules.
For a further test you can run the following in Terminal emulator.
su
mount -o remount rw /system
echo "this is a wp_mod test" > /system/wp_mod_test.txt
sync
reboot
Once rebooted check that the /system/wp_mod_test.txt file you just created has stuck through reboot.
MiniBlu
MiniBlu said:
This is a kernel module that disables write protection on the system partition while running the stock kernel.
This module was written by @far2 for the htc one M8 and Desire 816 its source code can be found on his git here: https://github.com/flar2/wp_mod
So credit goes to him.
I have just checked to see if it would be compatible and compiled it against A3UL 1.31.401.3 kernel source. It has been tested to load and work fine with all but the latest at&t kernel (as I don't have a copy of the latest at&t kernel to test it with but I think it should work for it as well).
This is for stock kernels only and is of no use if you are running JMZ kernel. It will allow you to keep your stock kernel (for better compatibility across regional rom versions) but same as JMZ kernel it allows you to modify the system partition and install mods and fixes that will stick through a reboot without having to do them through recovery.
Install instructions
- download latest supersu-install from here https://download.chainfire.eu/696/Su...etrieve_file=1
- download the attached "A3UL_4.4.2-wp_mod.zip"
- reboot to recovery (TWRP)
- Install Supersu-install.zip (a current supersu install is required as one of it's scripts will load the module)
- Install A3UL_4.4.2-wp_mod.zip
- Reboot
To test if the module is loaded you can open Terminal Emulator and type "lsmod" and wp_mod.ko should be in the list of loaded modules.
For a further test you can run the following in Terminal emulator.
su
mount -o remount rw /system
echo "this is a wp_mod test" > /system/wp_mod_test.txt
sync
reboot
Once rebooted check that the /system/wp_mod_test.txt file you just created has stuck through reboot.
MiniBlu
Click to expand...
Click to collapse
Just to be clear...this is not a kernel but a mod for the kernel? And it has not been tested with the latest rom--1.53.502.11? Thats what I'm currently running. Thanks
KLit75 said:
Just to be clear...this is not a kernel but a mod for the kernel? And it has not been tested with the latest rom--1.53.502.11? Thats what I'm currently running. Thanks
Click to expand...
Click to collapse
Thats right. This zip just adds a loadable kernel module(wp_mod.ko) to /system/lib/modules and a script(install-recovery-2.sh) to /system/etc. Once its installed the supersu script will run the script which loads the module during boot. As there has been no major kernel version jump it should work fine with your at&t kernel but I have been unable to test it. If you could test it that would be great. If it doesn't work for you it can be easily removed by just deleteing those 2 files it creates from recovery(or I can post a zip to remove it)
MiniBlu
MiniBlu said:
Thats right. This zip just adds a loadable kernel module(wp_mod.ko) to /system/lib/modules and a script(install-recovery-2.sh) to /system/etc. Once its installed the supersu script will run the script which loads the module during boot. As there has been no major kernel version jump it should work fine with your at&t kernel but I have been unable to test it. If you could test it that would be great. If it doesn't work for you it can be easily removed by just deleteing those 2 files it creates from recovery(or I can post a zip to remove it)
MiniBlu
Click to expand...
Click to collapse
I will but been waiting for a chance to flash the slimrom. Cant believe its been 11 months ive owned this and both your kernel mod and slimrom post on the same day! But most likely ill have a better chance of using yours as a daily driver. Ill probably post results in a few days. Thats usually enough time to give you an accurate bug report.
Btw--if i test slimrom 1st, should i do a full wipe, restore backup then flash kernelmod in one shot?
Still waiting on a response to my gapps question in the other thread...i haven't flashed it yet. Want an opinion on which gapps to use. Theres no link posted and its not mentioned in install instructions.
Thanks, I've had jmz kernel but had a backup of stock kernel and went back to stock because jmz doesn't support exFAT SD cards , I tested it everything is working, FYI European carrier.
Ok so no obvious fix on the headphone issue with slimrom so I'm ready to test this. I just have a few questions
1. Can I just flash it with my stock backup I made earlier today (factory reset, flash rom, flash wp_mod, reboot system)? This backup already has supersu installed, busybox, etc.)
2. I had already made some modifications flashed through recovery and also altered wifi tethering which you helped me with. Do you foresee any problems having it already setup like this or should I just start from scratch?
I guess thats it for now. Actually just asking because you made it a point to flash su even though I'd imagine most people who are here are already running a rooted stock version. Thanks again!
KLit75 said:
Ok so no obvious fix on the headphone issue with slimrom so I'm ready to test this. I just have a few questions
1. Can I just flash it with my stock backup I made earlier today (factory reset, flash rom, flash wp_mod, reboot system)? This backup already has supersu installed, busybox, etc.)
No. That should be fine.
2. I had already made some modifications flashed through recovery and also altered wifi tethering which you helped me with. Do you foresee any problems having it already setup like this or should I just start from scratch?
No. It will have no affect on things that are already installed.
I guess thats it for now. Actually just asking because you made it a point to flash su even though I'd imagine most people who are here are already running a rooted stock version. Thanks again!
Click to expand...
Click to collapse
As long as you have a fairly recently updated supersu install it should be fine. If it's not working for you then just flash the latest supersu and and check again.
MiniBlu
Flashed it just now with my backup and everything went fine. Itll take a few days to find bugs (if any). This is really cool. Thanks!
*****Update****Nice job. Its running as good as ever with no obvious flaws. I did have one random reboot but ive been messing with quite a few xposed mods. Overall, its been excellent for nearly 48 hours. Thanks again.
@MiniBlu has anyone tested your kernel mod with the new slimrom?
KLit75 said:
@MiniBlu has anyone tested your kernel mod with the new slimrom?
Click to expand...
Click to collapse
I don't know. Not that I've heard of anyway. I've been meaning to have a look at it myself but haven't had time yet. From some of what I've read I think changes to the system drive are already sticking on slimrom so I think it might be runing a kernel based on JMZ kernel. I also haven't seen any link to there slimrom device tree or kernel source which hopefully we can find as could really help to finish of the CM builds I've been struggling with.
MiniBlu
I can confirm now slimrom is able to write to system.
Related
Due to being a new user, I can't reply in the Development forum, so here goes:
I have a Galaxy Player 5.0 US, and wanted to try WT's ROM (http://forum.xda-developers.com/showthread.php?t=1623529). As noted in the thread, there is a (presumably now fixed) issue with its installation. I had that same mounting issue.
So I modified the install script by commenting out the lines that unmounted, formatted, and remounted /system and uncommented the "delete-recursive" line. This provided a successful installation after making sure that the proper filesystems were mounted in CWM.
The ROM then boots successfully with Entropy's kernel, and Wi-Fi, etc. work properly--I didn't notice any issues.
As a side note to the author: would it be possible to put the kernel as one of the options in the setup?
Mevordel said:
Due to being a new user, I can't reply in the Development forum, so here goes:
I have a Galaxy Player 5.0 US, and wanted to try WT's ROM (http://forum.xda-developers.com/showthread.php?t=1623529). As noted in the thread, there is a (presumably now fixed) issue with its installation. I had that same mounting issue.
So I modified the install script by commenting out the lines that unmounted, formatted, and remounted /system and uncommented the "delete-recursive" line. This provided a successful installation after making sure that the proper filesystems were mounted in CWM.
The ROM then boots successfully with Entropy's kernel, and Wi-Fi, etc. work properly--I didn't notice any issues.
As a side note to the author: would it be possible to put the kernel as one of the options in the setup?
Click to expand...
Click to collapse
Thanks for the feedback. I should be able to upload a new release in a day or so.
As for the kernel installation, I did consider the possibility of adding the option to install kernels but in the end I didn't put it in. My logic is that if you have a working CWM to flash this ROM, very likely you already have the correct kernel (because CWM is part of the kernel) and you rarely need to update the kernel.
If I put an option there for user to flash rj's kernel vs Entropy's kernel, I believe sooner or latter someone will flash the wrong kernel on the device which can be problematic.
If I can figure out some reliable ways to check the device type (US vs Intl), then it will be safe to include the kernel.
WT Ho said:
If I put an option there for user to flash rj's kernel vs Entropy's kernel, I believe sooner or latter someone will flash the wrong kernel on the device which can be problematic.
If I can figure out some reliable ways to check the device type (US vs Intl), then it will be safe to include the kernel.
Click to expand...
Click to collapse
That sounds reasonable - installing this rom won't modify your existing kernel at all, right?
A couple of final things:
1. In your next release, could you please update GO launcher? they made some pretty big improvements
2. me being the ocd neat freak that I am, I like it when there are very few folders in the root of /sdcard. Is there a way to put the "rom-settings" folder inside something like "Android"?
Thanks,
Mevordel
LIke the title says, this rom is built from the 4.4.2_r1 image and binaries from the Google repository (no changes or mods). This is pure AOSP KitKat.
This rom contains AOSP versions of Gallery2 and Camera2 which does not contain Google features such as HDR+ or PhotoSphere.
To install:
-TWRP or CWM recovery
-Factory reset, wipe cache and dalvik...if coming from a rom other than stock, wipe data too.
-Flash Rom
-Optional....flash "Photosphere Camera Addon Module" or other "Gapps packages"...only necessary for HDR+ and Photosphere
-Reboot and let install
-For HDR+ and Photosphere, flash "Photosphere Camera Addon Module" right after flashing rom (make sure its for 4.4.2) *see below for link
Rom Download.
aosp_hammerhead-kot49h MD5=34d9d60a4062d590f92746c977af9167
https://mega.co.nz/#!DJkD2QLB!OvMrzzp023VJYJSu-Y0wplRuL6Qlt3oDKNr6DtshoEw
Photosphere Camera Addon Module and all other Gapps-PA-Google apps
http://forum.xda-developers.com/showthread.php?t=2397942
To root-SuperSU 1.86
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
-Flash rom, let it install, place SuperSu into internal storage, reboot to recovery flash and reboot.
Thanks to Google for images and binaries
Thanks to TKruzze for PA-Google apps
Thanks to Chainfire for SuperSU
first... first time
will give it a shot.. lets go
Nice to have solid stock to fall back on. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
So what has been done with this besides just building from source? It's not clear whether or not gapps are added. How was the installer generated?
Gene Poole said:
So what has been done with this besides just building from source? It's not clear whether or not gapps are added. How was the installer generated?
Click to expand...
Click to collapse
Nothing. No gapps necessary.
What do you mean how was the installer generated???
Loving all this new development. Thanks for this
sent from my Hammerhead Nexus
rsa 329 said:
Nothing. No gapps necessary.
What do you mean how was the installer generated???
Click to expand...
Click to collapse
When I build, I get system.img, recovery.img, etc. No installer zip.
My builds seem to be missing some critical components or binary packages. That's why I asked if you added anything, or if you did like me and just followed build instructions here:
http://source.android.com/source/building.html
Gene Poole said:
When I build, I get system.img, recovery.img, etc. No installer zip.
My builds seem to be missing some critical components or binary packages. That's why I asked if you added anything, or if you did like me and just followed build instructions here:
http://source.android.com/source/building.html
Click to expand...
Click to collapse
There is better instruction than what you have there. Later, when I'm near my PC I will pm you and give you some links to better instruction.
Also, before I make I add the binaries from the repo.
Thanks, RSA, for the info in your PM. I got a compile that works, but only for 10-12 hours. After that, the cell provisioning breaks. "No Service" and nothing I can do short of a reboot brings it back. I thought it might be my build, so I installed yours. Same thing. It very well may be something broken on my part, like APN or something (I'm using the stock APNs from the AOSP source) since neither my build nor yours are working right. I needed my phone so I restored factory before I could dig through logcats.
Any ideas? Anyone else running this build fulltime? I'm AT&T if that matters.
Gene Poole said:
Thanks, RSA, for the info in your PM. I got a compile that works, but only for 10-12 hours. After that, the cell provisioning breaks. "No Service" and nothing I can do short of a reboot brings it back. I thought it might be my build, so I installed yours. Same thing. It very well may be something broken on my part, like APN or something (I'm using the stock APNs from the AOSP source) since neither my build nor yours are working right. I needed my phone so I restored factory before I could dig through logcats.
Any ideas? Anyone else running this build fulltime? I'm AT&T if that matters.
Click to expand...
Click to collapse
Interesting. I've been using a debloated version of my aosp for a while now with no problems. I ran this build for a couple weeks before switching and had no issues. Did you do a full wipe? How about ART, are you using art or dalvik? Have you tried your build after doing a system format? What service provider do you use?
Sorry for all the questions, just trying to get an idea of your situation.
I'm with AT&T. I decided to put this back on and wait for it to act up, then get a logcat and go from there. We'll see how it goes.
I've been running this for 3 days now without issue. The only change I made from my first attempt was to: install only the system partition (no recovery or boot); use my own boot image that has some things I need in it(1); and install the latest PA-GApps over it after installation. None of those changes should have negated the behavior I was seeing earlier, so I'm writing it off as odd coincidence.
1. I have modified the boot image to include stuff for mounting external storage to the USB port. This also includes a modified framework-res.apk and SystemUI.apk compiled on my system and inserted at install time to the system partition.
Gene Poole said:
I've been running this for 3 days now without issue. The only change I made from my first attempt was to: install only the system partition (no recovery or boot); use my own boot image that has some things I need in it(1); and install the latest PA-GApps over it after installation. None of those changes should have negated the behavior I was seeing earlier, so I'm writing it off as odd coincidence.
1. I have modified the boot image to include stuff for mounting external storage to the USB port. This also includes a modified framework-res.apk and SystemUI.apk compiled on my system and inserted at install time to the system partition.
Click to expand...
Click to collapse
Very cool! Glad to hear you got it working.
One issue I've just discovered is that the camera, when in video mode, records video files with a green line at the bottom (only visible on playback). I've researched this and found that AOSP source is missing an update in one of the files that makes up the libmmcamera_interface.so shared object. Copying the same filename from the factory image into the /system/lib directory, overwriting the existing file from AOSP build fixes the problem.
Again, no problem with your build; the problem seems to be that Android hasn't committed all their code the the AOSP tree.
rsa 329 said:
There is better instruction than what you have there. Later, when I'm near my PC I will pm you and give you some links to better instruction.
Also, before I make I add the binaries from the repo.
Click to expand...
Click to collapse
Hi RSA,
can you please share the instructions with me as well ? much appreciate your work..
Unofficial build of SlimKat
Dont post in official threads please. I may have messed something up and i dont want to bother other people because of my mistakes.
After leeching for years on XDA (didnt even had an account) i finaly decided to give something back to the community.
Features:
Im using the build scripts from Slimsaber
Features of Slimsaber but not all are working!
Used newest Linaro 4.8.3 (2014.04) optimized for cortex-a15 from here for kernel and rom.
Did some patches so it compiles with strict-aliasing :victory:. But i hate those freaking pointers. So maybe i messed something up.
all the nice placebo compile flags: -O3 -mcpu=cortex-a15 -mfpu=neon-vfpv4 -mfloat-abi=softfp -funroll-loops -fomit-frame-pointer
Other flags:BOARD_USES_HGL := true, BOARD_USES_OVERLAY := true, USE_OPENGL_RENDERER := true, TARGET_USES_ION := true, TARGET_USES_C2D_COMPOSITION := true
all the nice placebo build.prop tweaks: debug.sf.hw=1, debug.composition.type=c2d, debug.performance.tuning=1, persist.sys.composition.type=c2d, persist.sys.ui.hw=1, hw3d.force=1, hw2d.force=1, video.accelerate.hw=1, force_hw_ui=true, debug.egl.hw=1, debug.overlayui.enable=1 (actualy i dont know which ones are working and which ones arent even in the code )
f2fs for data and cache partition. (I think the first released z ultra rom with f2fs. Correct me if im wrong please)
DPI set to 280 (tablet layout).
Install instructions:
Be running at least Android 4.3 or 4.4.2 with an unlocked BL (14.2.A.0.290, 14.2.A.1.136, 14.3.A.0.681 or 14.3.B.0.757 etc)
Make a backup of everything on your phone. Im not responsible for any loss of data!
Boot into recovery
Factory reset/wipe data
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom
Install Gapps (I use this one)
Optional: for even more placebo install this soundmod.
Not Working:
Nothing known
Not Tested (would be nice if someone could test it):
ART
Miracast
Other models then C6833
Bugs:
WARNING: ADB/USB Debbuging is always enabled on reboot! So if you have sensitive data on your phone this ROM is NOT for you! (maybe someone can help. tried to disable it via build.prop and settings.db but didnt work . I think it has something todo with the build scripts from Slimsaber but hadnt had time to check it.)
[*]After installing the ROM for the first time you have to go to developer settings and disable root and reenable it in order for it to work!
Its already set to apps only after installing but it wont work! You only have to do this once. If you reflash you dont have to do it again.
Some graphics glitches because of "USE_OPENGL_RENDERER := TRUE" in some system apps (like Browser).
Actualy i read somewhere that its not needed but it wouldnt be placebo without it
If you use MHL some of the screen will not be displayed (It displays only like 1900*1000)
Downloads:
FormatPartitions-userdata_cache.zip. Credits goto legolas83
PlaceboRom-togari-4.4.2-20140515.zip
RestorePartitions_ext4_userdata_cache. If you want to go back to another rom. Credits goto legolas83
I will try to build every two weeks.
I had only one freeze on my device (C6833) in over 1,5 months (with older builds) but consider these build as NOT STABLE. I dont want that you lose your job because of me.
Special thanks to team slimroms.
Visit official website at http://www.slimroms.net
Slimsaber is the inspiration for this rom. High five @fusionjack.
If I have time i will setup a github account so contributions will be clear.
At the moment im using repos from Slimkat, Slimsaber, CyanogenMod, VanirAOSP, AOKP, Linaro
If i missed something or didnt gave proper credits i can assure that this is a mistake.
Contact me please so i can correct it.
XDA:DevDB Information
PlaceboRom, ROM for the Sony Xperia Z Ultra
Contributors
MusterMaxMueller, fusionjack, [vertigo], dboliver, blueether, Christopher83, legolas83, prbassplayer, SlimRoms, CyanogenMod, VanirAOSP, AOKP, Linaro, FreeXperia, CodeAurora, Google
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.2.A.0.290, 14.2.A.1.136, 14.3.A.0.681, 14.3.B.0.757 or newer
Based On: SlimKat, CynanogenMod, VanirAOSP, AOKP
Version Information
Status: Testing
Created 2014-05-15
Last Updated 2014-05-15
Reserved
Only changes i did to slimkernel was enabling f2fs in defconfig and some buildflags in the Makefile for kernel.
Does anyone know do i have to release my changes to be GPL compliant? defconfig is generated so i think not but what about Makefile?
Im not familiar with GPL but want to do everything correct.
Reserved
OK my install instructions seems to be wrong after reading them again. :silly:
Can anyone confirm? It shouldnt work the first time.
Sorry to anyone who had problems.
I think you have to:
Boot into recovery
Flash PlaceboRom (you have to flash it the first time. Otherwise there might be no f2fs support in your current kernel+recovery)
Reboot to recovery (after that you will have f2fs support)
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom again!
Install Gapps (I use this one)
Optional: for even more placebo install thissoundmod.
Could someone be kind and when installing the rom for the first time report back if this new install instruction is working?
It was some time ago i did it so im not sure anymore.
If somone confirms i will update op.
Looks promising, yah the first F2FS! :highfive:
MusterMaxMueller said:
Only changes i did to slimkernel was enabling f2fs in defconfig and some buildflags in the Makefile for kernel.
Does anyone know do i have to release my changes to be GPL compliant? defconfig is generated so i think not but what about Makefile?
Im not familiar with GPL but want to do everything correct.
Click to expand...
Click to collapse
Any changes in the kernel need to be published, and the aosp/cm/slim code, what is less clear is whether compile flags etc (changes to make files) need to be published - my feeling is that yes they do need to be published. That's some thing I haven't done for carbon as of yet.
At the moment I think you are probably ok?
keep it up mate...looking forward for this rom. :good:
@blueether
I think i dont get you. AOSP/Slim is released under ASL. So changes made to rom dont need to be published? Altough i will when i have time. And is defconfig considered part of the kernel? Because of "make menuconfig"? Does anyone know for sure? If i interpret this and this correctly changes to Makefile have to be published but defconfig not. They even mention build flags!I know its pedantic just want to know. It seems there is no defenite time frame when sources have to be published?
blueether said:
Any changes in the kernel need to be published, and the aosp/cm/slim code, what is less clear is whether compile flags etc (changes to make files) need to be published - my feeling is that yes they do need to be published. That's some thing I haven't done for carbon as of yet.
At the moment I think you are probably ok?
Click to expand...
Click to collapse
I would interpret it as everything that is needed to build the same binary
Not looked at the details of asl
Sent from CarbonROM on my Z-Ultra
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
cameljockey1 said:
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
Click to expand...
Click to collapse
did you flash gapps..I did with gapps and even w dalvik and cache wipe it was hanging up...so i redid procedure again without gapps..booted fine
mac231us said:
did you flash gapps..I did with gapps and even w dalvik and cache wipe it was hanging up...so i redid procedure again without gapps..booted fine
Click to expand...
Click to collapse
That did it thank you.
reread it. i think youre right
blueether said:
I would interpret it as everything that is needed to build the same binary
Not looked at the details of asl
Sent from CarbonROM on my Z-Ultra
Click to expand...
Click to collapse
i have no problems using minimal gapps from op.
try using the one from op.
cameljockey1 said:
I followed direction to the t. and it's hanging at boot animation now for ten minute. Now. What am doing wrong?
Click to expand...
Click to collapse
F2FS mount and sysfs options
For those interested in tweaking F2FS, check my post here.
wrong install instructions
OK my install instructions seems to be wrong after reading them again. :silly:
Can anyone confirm? It shouldnt work the first time.
Sorry to anyone who had problems.
I think you have to:
Boot into recovery
Flash PlaceboRom (you have to flash it the first time. Otherwise there might be no f2fs support in your current kernel+recovery)
Reboot to recovery (after that you will have f2fs support)
Flash FormatPartitions-userdata_cache.zip
This will format data and cache partition to f2fs
WARNING: this will DELETE ALL DATA on your data partition. Even InternalSD! Make a backup beforehand!
Flash PlaceboRom again!
Install Gapps (I use this one)
Optional: for even more placebo install thissoundmod.
Could someone be kind and when installing the rom for the first time report back if this new install instruction is working?
It was some time ago i did it so im not sure anymore.
If somone confirms i will update op.
download not working
The download anyway at Google Drive is not generating any download dialog box upon clicking:
Google Drive can't scan this file for viruses.
SlimSaber-togari-4.4.2-20140515.zip (198M) exceeds the maximum size that Google can scan. Would you still like to download this file?
Download anyway
Please upload to mega or somewhere else
Premananda_laishram said:
The download anyway at Google Drive is not generating any download dialog box upon clicking:
Google Drive can't scan this file for viruses.
SlimSaber-togari-4.4.2-20140515.zip (198M) exceeds the maximum size that Google can scan. Would you still like to download this file?
Download anyway
Please upload to mega or somewhere else
Click to expand...
Click to collapse
I'm uploading to mega atm, should be up in about 20 - 30 min
Google Drive mirror: https://drive.google.com/a/fryett.net/file/d/0B2qGRw4S7bAuUkxWVzVXQzNJOXc/edit?usp=sharing
Mega mirror: https://mega.co.nz/#!9pt1xSQL!ozJyip-yzATId0_Po7sG1_sisWH8UfnNVOhHmxh-4fA
Premananda_laishram said:
Please upload to mega or somewhere else
Click to expand...
Click to collapse
you could also use the download tab ?
not working
Flashing instructions not working. Hangs at boot logo
Premananda_laishram said:
Flashing instructions not working. Hangs at boot logo
Click to expand...
Click to collapse
which install instructions doesnt work?
the first or the second one?
try first without flashing gapps.
This is my personal compiled Kernel for SM-P350.
There is so little resource for my P350,
I need a Kernel with permissive and cifs function for my daily use,
because i frequently read PDF on local network,
with CIFS mount enbled , i can open PDF directly without the need to download it to my device.
However, i search all the forums, no this kind of Kernel i can find.
That's the reason i decide to learn compiling kernel from zero and finally out this kernel.
You may use this Kernel on P350 stock MM or Fenix Rom MM.
I'm currently on Fenix MM,
I cannot guarantee it will work on you P350, so , make a nadroid backup with TWRP first !
Take your risk by yourself.
Kernel Feather:
-Full Permissive
-Cifs built-in
-NTFS enable
Requirement:
-P350 Stock Android MM or Fenix Rom MM
-Device Rooted with TWRP installed
How:
1: Make sure you have 3 files copy to you internal or external storage.
-boot.img (kernel)(extract it first)
-pronto_wlan.ko(wifi module)(extract it first)
-SuperSu.zip (you can download form net , search it)
2: use your file explorer(with root access) copy pronto_wlan.ko to /system/lib/modules/pronto.
replace the old one, chmod to 644. make sure to backup old one first , rename old one to pronto_wkan.ko.bak.
3ower off device and boot to TWRP.
4:Use TWRP to install boot.img(install as boot, DO NOT CHOOSE RECOVERY)
5:Use TWRP to install SuperSu.zp (to get root re-enable)
6:After all, reboot system, first booting time may take some time , wait , be patient.
7:After boot finsh, check your wifi and root are all functional.
8:Now you can start to use cifs function.
Don't ask me what is CIFS and how to use, search on net.
Also, don't ask me to add more function on Kernel, I'm not a developer,
all i need is Cifs enabled Kernel, no other needed.
Update:
V2: add ondemand governor for better battery life, wifi module also need to be update.
Thansk to Ashyx teaching me on Kernl building, and permissive code form he.
Thankk to cbtc helping me to solve Wifi problem and his Fenix Rom.
Nice job!
kevinchg said:
This is my personal compiled Kernel for SM-P350.
There is so little resource for my P350,
I need a Kernel with permissive and cifs function for my daily use,
because i frequently read PDF on local network,
with CIFS mount enbled , i can open PDF directly without the need to download it to my device.
However, i search all the forums, no this kind of Kernel i can find.
That's the reason i decide to learn compiling kernel from zero and finally out this kernel.
You may use this Kernel on P350 stock MM or Fenix Rom MM.
I'm currently on Fenix MM,
I cannot guarantee it will work on you P350, so , make a nadroid backup with TWRP first !
Click to expand...
Click to collapse
Hi Kevin, this is awesome!!! Thanks for posting this! I have been looking for a CIFS solution for a long time.
I have not installed this yet - just wanted to know if this removes any capability from the Fenix ROM?
Ideally I would like to have all functionality that Fenix gives me, with the ability to CIFS mount my NAS.
Just installed Fenix on the SM-P350 and its awesome (thanks heaps cbtc!)
- Matty -ArctiX
kevinchg said:
This is my personal compiled Kernel for SM-P350.
There is so little resource for my P350,
I need a Kernel with permissive and cifs function for my daily use,
because i frequently read PDF on local network,
with CIFS mount enbled , i can open PDF directly without the need to download it to my device.
However, i search all the forums, no this kind of Kernel i can find.
That's the reason i decide to learn compiling kernel from zero and finally out this kernel.
You may use this Kernel on P350 stock MM or Fenix Rom MM.
I'm currently on Fenix MM,
I cannot guarantee it will work on you P350, so , make a nadroid backup with TWRP first !
Take your risk by yourself.
Kernel Feather:
-Full Permissive
-Cifs built-in
-NTFS enable
Requirement:
-P350 Stock Android MM or Fenix Rom MM
-Device Rooted with TWRP installed
How:
1: Make sure you have 3 files copy to you internal or external storage.
-boot.img (kernel)(extract it first)
-pronto_wlan.ko(wifi module)(extract it first)
-SuperSu.zip (you can download form net , search it)
2: use your file explorer(with root access) copy pronto_wlan.ko to /system/lib/modules/pronto.
replace the old one, chmod to 644. make sure to backup old one first , rename old one to pronto_wkan.ko.bak.
3ower off device and boot to TWRP.
4:Use TWRP to install boot.img(install as boot, DO NOT CHOOSE RECOVERY)
5:Use TWRP to install SuperSu.zp (to get root re-enable)
6:After all, reboot system, first booting time may take some time , wait , be patient.
7:After boot finsh, check your wifi and root are all functional.
8:Now you can start to use cifs function.
Don't ask me what is CIFS and how to use, search on net.
Also, don't ask me to add more function on Kernel, I'm not a developer,
all i need is Cifs enabled Kernel, no other needed.
Update:
V2: add ondemand governor for better battery life, wifi module also need to be update.
Thansk to Ashyx teaching me on Kernl building, and permissive code form he.
Thankk to cbtc helping me to solve Wifi problem and his Fenix Rom.
Click to expand...
Click to collapse
YOU WILL HAVE THE FÉNIX ROM THAT YOU CAN SEND ME
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Note 1/19/18: I fixed OTG in 3.2.1-0. Since the LineageOS kernel for the VS995 is known to have broken OTG, I went back to my good old reliable 10b source. I stripped down the options as much as I could to reduce the file size. It seems to be working well. Unfortunatly the only way to tell them apart is the file size or md5.
Old: 24,637,440 bytes / MD5 - ca8bb67c07a81fe17f463eeaacd7c096
New: 24,653,824 bytes / MD5 - d2b25849241b9524b838a11bb0a39093
Here's the build info from the old builds for those looking for breadcrumbs, etc.
OK, this is the first time I've built TWRP so I'm sure there are some issues. Please use this at your own risk. I've done some very basic testing and it seems to work OK for my purposes. I do not plan to build for anything other than the VS995. For other devices I'll lay out my basic workflow in hopes that those still working on other devices can do the same.
Basically I followed the guide here: https://forum.xda-developers.com/showthread.php?t=1943625
Since I already have the LineageOS repositories (with proprietary files from here) installed on my machine, I started with the code from here: https://github.com/omnirom/android_bootable_recovery
I found out LineageOS doesn't have busybox so I added that to my LineageOS system/external folder from here: https://github.com/omnirom/android_external_busybox
Since it failed to build with encryption, I cherry-picked this commit: https://gerrit.omnirom.org/#/c/22096/
I added the recover.fstab from here to the device folder for the vs995: https://github.com/jcadduono/android_device_lge_vs995/tree/android-6.0/recovery/root
Here are the extra lines and flags I added to my default LineageOS BoardConfig.mk
Code:
RECOVERY_VARIANT := twrp
PRODUCT_COPY_FILES += device/lge/vs995/twrp.fstab:recovery/root/etc/twrp.fstab
TW_THEME := portrait_hdpi
RECOVERY_SDCARD_ON_DATA := true
TW_INCLUDE_CRYPTO := true
That's pretty much everything I've done.
Note to developers: This recovery is a true VS995 build. Please add vs995 to your zips asserts.
Know issues:
- ROMs, kernels, mods, etc. whose zips are built with 'elsa' and/or 'vs996' only asserts will not flash. This is not a bug. If your zip tells you it's for another device and not a vs995, please ask the developer to add this to their asserts.
Download: VS995 TWRP 3.2.1-0
Device tree/kernel source
Old Builds:
VS995 TWRP 3.2.0-0
TWRP 3.2.1-0 Changelog
Code:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Thank you very much, even though I don't own a VS995 it's always good to see new development. Thanks again OP.
Link gives me "Access Denied"
wally86 said:
Link gives me "Access Denied"
Click to expand...
Click to collapse
I (think I) fixed it. Please try again.
BackCheck said:
I (think I) fixed it. Please try again.
Click to expand...
Click to collapse
Working now!
I just received my vs995. I'm gonna downgrade to 12A from 15A with uppercut, when use dirtysanta. Should I use twrp 3.0.2-1 like in the guide then then update to 3.2.0-0 or just use 3.2.0-0?
Thanks
wally86 said:
Working now!
I just received my vs995. I'm gonna downgrade to 12A from 15A with uppercut, when use dirtysanta. Should I use twrp 3.0.2-1 like in the guide then then update to 3.2.0-0 or just use 3.2.0-0?
Thanks
Click to expand...
Click to collapse
I would 100% use the 3.0.2-1 from the thread. It has been well tested. From there is you're looking to use a custom kernel or flash a custom rom, then you might test 3.2.0-0. Like I said in the OP, this is the first time I've ever messed with compiling TWRP.
BackCheck said:
I would 100% use the 3.0.2-1 from the thread. It has been well tested. From there is you're looking to use a custom kernel or flash a custom rom, then you might test 3.2.0-0. Like I said in the OP, this is the first time I've ever messed with compiling TWRP.
Click to expand...
Click to collapse
Alright sounds good. I'm gonna try resurrection remix & weta with this version and I'll report back in a few days with how it's working.
Awesome, thanks for keeping the development alive!
Awesome thanks so much. Downloading now. You're great!
Any idea if this is available on the H918 (T-mobile)?
jaysonic88 said:
Any idea if this is available on the H918 (T-mobile)?
Click to expand...
Click to collapse
To the best of my knowledge, there is no 3.2.0 TWRP for the H918, 3.1.1 is the most recent build for it.
This works perfectly with VS995. Thank you!
Any idea how to make this for H990DS ?
Zenns said:
Any idea how to make this for H990DS ?
Click to expand...
Click to collapse
Between the links I posted in the OP and this there are enough breadcrumbs for someone to start building it. That someone isn't me but I would gladly offer advice if needed.
BackCheck said:
Between the links I posted in the OP and this there are enough breadcrumbs for someone to start building it. That someone isn't me but I would gladly offer advice if needed.
Click to expand...
Click to collapse
So I followed your guide (thanks btw!) and successfully compiled twrp 3.2 for the h910 (att) variant. There are some issues for me though. First the terminal in twrp constantly says "child process exited" when I try to type anything in. Also when installing stuff there's a red warning saying "error mount -o bind data/media/0 error 2" or something similar. In the file manager I can access that partition and see files there. Backup and restore seems to work and I tested a couple of magisk zips and they all flashed successfully. Was wondering if you had seen anything like that.
toastyp said:
So I followed your guide (thanks btw!) and successfully compiled twrp 3.2 for the h910 (att) variant. There are some issues for me though. First the terminal in twrp constantly says "child process exited" when I try to type anything in. Also when installing stuff there's a red warning saying "error mount -o bind data/media/0 error 2" or something similar. In the file manager I can access that partition and see files there. Backup and restore seems to work and I tested a couple of magisk zips and they all flashed successfully. Was wondering if you had seen anything like that.
Click to expand...
Click to collapse
Good job. And no, my first build had completely different errors. If you want to PM me your fstab and board config I might be able to look over it sometime and see if I can see anything. Those 2 files look like good places to start.
So I've gone and gotten a sorta working us996 build. Definitely took a couple trys, and my first attempt wiped /data (thanks LG, but this is why I keep backups!) Since I didn't have TW_IGNORE_MISC_WIPE_DATA set. It doesn't have USB otg support like the old 3.0.2 build does (neither does Lineage, but the old build and stock does). I plan on looking at cleaning up my fstab or whatever so that the sdcard is labeled nicely (has internal storage and then storage0 - storage4 with the sdcard being one of those). Havnt tried backups/restoring yet, nor any sort of encryption, but flashing a new lineage build, gapps, and magisk worked. Slightly annoyed I can't build lineage and twrp at the same time (using brunch it pukes out an error about not being able to find some library twrp builds in it's applypatch directory, granted paraphrasing errors doesn't help much) but whatever I can toggle back and forth.
Phoenix591 said:
So I've gone and gotten a sorta working us996 build. Definitely took a couple trys, and my first attempt wiped /data (thanks LG, but this is why I keep backups!) Since I didn't have TW_IGNORE_MISC_WIPE_DATA set. It doesn't have USB otg support like the old 3.0.2 build does (neither does Lineage, but the old build and stock does). I plan on looking at cleaning up my fstab or whatever so that the sdcard is labeled nicely (has internal storage and then storage0 - storage4 with the sdcard being one of those). Havnt tried backups/restoring yet, nor any sort of encryption, but flashing a new lineage build, gapps, and magisk worked. Slightly annoyed I can't build lineage and twrp at the same time (using brunch it pukes out an error about not being able to find some library twrp builds in it's applypatch directory, granted paraphrasing errors doesn't help much) but whatever I can toggle back and forth.
Click to expand...
Click to collapse
I share your pain on the errors with brunch, I get that too. What are you using for fstab? If your using the fstab from jcadduono then OTG is in the file, then it's in there. I don't use OTG so I'm not sure it or encryption is working in mine either. I need testers.
BackCheck said:
I share your pain on the errors with brunch, I get that too. What are you using for fstab? If your using the fstab from jcadduono then OTG is in the file, then it's in there. I don't use OTG so I'm not sure it or encryption is working in mine either. I need testers.
Click to expand...
Click to collapse
No it isn't in jc's fstab, looks like USA-RedDragon has it in his, https://github.com/DesolationRom-Devices/device_lge_h910twrp?files=1 . Going to take a closer look in a day or so.
Well, I got USB otg working, just not the way I hoped. I grabbed the prebuilt kernel image from the repo in my last post and that did the trick when using his fstab as well. So it's probably a kernel problem, since it didn't work with his fstab alone. I tried enabling the more obviously named USB otg kernel config options without success.