Related
[ROMs][GPL] Tenzo's Stock "Plain" HTC 2.1 ROMs - 2.37.605.4 w/JulyOTA [10-01-10]
Many of my recent efforts have lead me to take a few steps back in discovering a few things (does that makes sense?). In working on fixes for 3GP Vanilla MMS and the 50% TWS "issue" I have put these together.
Should hopefully help others, especially those new to cooking that want an easy, trouble free base to start with (no "extra fonts" and no "updating" the JulyOTA manually).
EDIT: if you have "issues" with either wired or wireless tether, you can use the apk's attached below. (thanks Conap, bugger561, and T2Noob)
I have built all of these ROMs from the RUU and integrated the JulyOTA. All ROMs are deodexed. Information below:
ROMs built with dsixda's 0.97 Android Kitchen
---------------------------------------------------------------------------
Tenzo-Official2.1-JulyOTA.zip (95.22 MB)
http://www.multiupload.com/UTESX66PBP
md5 - F3047E1D78251A4150367F5265F57457
sha1 - CFDF4720B44F8CB23B3B2489C6CC9EE594D7BC04
Tenzo-Official2.1-JulyOTA.zip
Stock ROM built from RUU
JulyOTA Update applied
ROM Deodexed
Removed System Updates (systemupdater.apk)
Added adb/debug capabilities on by default
Will not update radio, recovery or bootloader
NO ROOT OR ANY EXTRAS
---------------------------------------------------------------------------
Tenzo-Official2.1-JulyOTA-Root.zip (97.01 MB)
http://www.multiupload.com/776C431YTM
md5 - 7241DEB69057FD5E4C857E0A7C621FBA
sha1 - 9AF1C84258C6E30D46E1F69D806BFDC313DDD6B7
Tenzo-Official2.1-JulyOTA-Root.zip
Stock ROM built from RUU
JulyOTA Update applied
ROM Deodexed
Removed System Updates (systemupdater.apk)
Added adb/debug capabilities on by default
Will not update radio, recovery or bootloader
v5 cfs kernel
root (ChainsDD 2.3.6.1)
busybox
wired tether
wireless tether
Changed CPU govenor to "ondemand" (Kernel defaults to "performance")
---------------------------------------------------------------------------
Tenzo-Official2.1-JulyOTA-A2SD.zip (100.17 MB)
http://www.multiupload.com/73RVCD8IWI
md5 - 60FDE63FF4B55266F0321106D6A564DE
sha1 - AE279F1BB88F118B96F4FC03B29C8398516004B8
Tenzo-Official2.1-JulyOTA-A2SD.zip
Stock ROM built from RUU
JulyOTA Update applied
ROM Deodexed
Removed System Updates (systemupdater.apk)
Added adb/debug capabilities on by default
Will not update radio, recovery or bootloader
v5 cfs kernel
root (ChainsDD 2.3.6.1)
busybox
wired tether
wireless tether
Changed CPU govenor to "ondemand" (Kernel defaults to "performance")
A2SD 2.7.5.1 (non busybox run-parts method)
---------------------------------------------------------------------------
Tenzo-Official2.1-Cache.zip (100.17 MB)
http://www.multiupload.com/6AB22H8PQ3
md5 - C9F54A0A5454931C2BB3DEE41B53FD51
sha1 - 0904B696C38A54B1A68557F7DA68A5031026E837
Tenzo-Official2.1-Cache.zip
Stock ROM built from RUU
JulyOTA Update applied
ROM Deodexed
Removed System Updates (systemupdater.apk)
Added adb/debug capabilities on by default
Will not update radio, recovery or bootloader
v5 cfs kernel
root (ChainsDD 2.3.6.1)
busybox
wired tether
wireless tether
Changed CPU govenor to "ondemand" (Kernel defaults to "performance")
A2SD 2.7.5.1 (non busybox run-parts method)
Cache2Cache enabled (Over 150MB+ of Internal Storage)
---------------------------------------------------------------------------
No Spareparts or DevTools!!! Use attachments below if you want/need these.
---------------------------------------------------------------------------
Acknowledgments / Thanks:
dsixda - Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
tkirton - Apps2SD - http://forum.xda-developers.com/showthread.php?t=715116
Conap and decad3nce - CFS Kernel - http://forum.xda-developers.com/showthread.php?t=774211
Please donate to one of the Dev's above. Seriously, if it wasn't for them, your phone would suck
10/01/10
Added Cache2Cache Version
Added WiredTether v1.4 (to attached downloads)
09/27/10
Initial Uploads
I just flashed this and now I am having troubles getting wi-fi to work. Whenever I try to enable it, I get an error saying "Unable to start wi-fi". I wasn't having any problems previously with any roms and I just did a full wipe from KaosFroyo V35. Any ideas?
-Allen
THIS HAS BEEN FIXED... SO PLEASE IGNORE THIS POST (UNLESS OF COURSE YOU DL'ED BEFORE I FIXED THE LINKS)
homaygfresh2000 said:
I just flashed this and now I am having troubles getting wi-fi to work. Whenever I try to enable it, I get an error saying "Unable to start wi-fi". I wasn't having any problems previously with any roms and I just did a full wipe from KaosFroyo V35. Any ideas?
-Allen
Click to expand...
Click to collapse
which ROM?
----------------------
crap... it was either the A2SD or ROOT version, yes? my goof... pulling links... will be back up soon
if you don't want to wait/reflash... unzip the attachment and put them in androidsdk\tools folder...
then:
adb remount
adb push tun.ko /system/lib/modules
adb push wlan.ko /system/lib/modules
------------------------------------------
SORRY BOUT THAT!!!
I have the same problem on Tenzo-Official2.1-JulyOTA-Root.
Why don't you just flash PlainJaneT2 which is total Stock with A2sd, and are able to enable JIT through a2sd with By typing "a2sd jit"
Everything works, on it is pretty fast for a HTC rom.
http://forum.xda-developers.com/showthread.php?t=718092
Just wondering Why you made another rom thats already out there...
I didn't mean to take over the thread just curious what the difference between PlainJane and this.
Another question is if you tested wired tether?
Because if you just dropped it in the rom I CAN GUARANTEE that it is not working, thats why I didn't add it to the rom, And If you did get it to work can you tell me how you did it?
If you included SETCPU i suggest you take it off if you don't want to have problems with the SETCPU developer later in the future..... A Member has been kicked because he included apps that developers had told him to get rid of.
This has the newest build of 2.1 by HTC. And wired tether has been updated to work on the Eris and incredible. Plainjane, even though it is older than this and T2 is still better for those who do jot care about JIT or A2SD. I've tried both as well as this and jcase's Rom features the most free memory. I uninstall a lot of stock apps and then add maybe 25-30mb of market apps. Plainjane left new with 95+mb free. This and T2 leave me with roughly 70mb.
bugger561 said:
I have the same problem on Tenzo-Official2.1-JulyOTA-Root.
Click to expand...
Click to collapse
you can do the same thing posted above
t2noob said:
Why don't you just flash PlainJaneT2 which is total Stock with A2sd, and are able to enable JIT through a2sd with By typing "a2sd jit"
Everything works, on it is pretty fast for a HTC rom.
http://forum.xda-developers.com/showthread.php?t=718092
Just wondering Why you made another rom thats already out there...
I didn't mean to take over the thread just curious what the difference between PlainJane and this.
Another question is if you tested wired tether?
Because if you just dropped it in the rom I CAN GUARANTEE that it is not working, thats why I didn't add it to the rom, And If you did get it to work can you tell me how you did it?
If you included SETCPU i suggest you take it off if you don't want to have problems with the SETCPU developer later in the future..... A Member has been kicked because he included apps that developers had told him to get rid of.
Click to expand...
Click to collapse
hmmm
this is completely stock... no extra scripts, no extra fonts, no a2sd, etc. it's stock... with july OTA integrated and deodexed. that's all i did. can you point out where the other completely stock ROM with JulyOTA integrated is? If i missed it, i apologize. again... other than not trashing bootloader, recovery, etc, it's as "stock" as it gets. no symlinks changed in update-script, etc. again, this is the only stock ROM w/July OTA integrated that i've seen on the forum. did i miss something? (Official Obsession is close... but that requires you flash over the update. not easy for beginning cooks trying to customize a ROM... and it's not deodexed)
the "other" 2 ROMs are different as well... one is almost stock, with just latest ChainsDD superuser (root) added (no a2sd), with Conap's CFS kernel. the other is the same, with latest a2sd added (which allows the ability to add cache2cache as well).
i've enjoyed PlainJaneT2... and it is still my base for TT2.1. i've given full props to you with links and request even for donations in that thread. if i've upset you, again, i apologize.
also, no "extra" apps (setcpu, etc) are included... i know the rules
i'm not trying to "ruin" any experience for anyone... or step on anyone's toes. i'm just trying to help out and contribute. certainly have never tried to upset anyone on this forum EVER!
bugger561 said:
This has the newest build of 2.1 by HTC. And wired tether has been updated to work on the Eris and incredible. Plainjane, even though it is older than this and T2 is still better for those who do jot care about JIT or A2SD. I've tried both as well as this and jcase's Rom features the most free memory. I uninstall a lot of stock apps and then add maybe 25-30mb of market apps. Plainjane left new with 95+mb free. This and T2 leave me with roughly 70mb.
Click to expand...
Click to collapse
one thing you can do with a2sd 2.7.5.1 is run the cache on the cache partition.
adb remount
adb shell
a2sd cachepart
when it's done, it will reboot the ROM. pull the battery and clear dalvik (or else you'll get a few FC's when you reboot).
you can try the above with "a2sd cachepartreset" and it "should" clear dalvik for you... but it hasn't worked well for me
t2noob said:
Another question is if you tested wired tether?
Because if you just dropped it in the rom I CAN GUARANTEE that it is not working, thats why I didn't add it to the rom, And If you did get it to work can you tell me how you did it?
Click to expand...
Click to collapse
There was a version of wired tether put up here on xda somewhere that did work with our phones....
Conap said:
There was a version of wired tether put up here on xda somewhere that did work with our phones....
Click to expand...
Click to collapse
added to first post big thanks (as always) Conap!
tenzomonk said:
added to first post big thanks (as always) Conap!
Click to expand...
Click to collapse
The official wired tether 1.4 integrated the fix for our phone. So the latest from the official site will work.
bugger561 said:
The official wired tether 1.4 integrated the fix for our phone. So the latest from the official site will work.
Click to expand...
Click to collapse
good to know thanks......
Hey, I pasted those two files into the correct directory using rootexplorer. I've done it twice now and rebooted, WiFi is still not working.
bugger561 said:
Hey, I pasted those two files into the correct directory using rootexplorer. I've done it twice now and rebooted, WiFi is still not working.
Click to expand...
Click to collapse
try the "new" DL and just flash over (no wipe should be needed). what does it say your "kernel" is under software info?
t2noob said:
Another question is if you tested wired tether?
Because if you just dropped it in the rom I CAN GUARANTEE that it is not working, thats why I didn't add it to the rom, And If you did get it to work can you tell me how you did it?
If you included SETCPU i suggest you take it off if you don't want to have problems with the SETCPU developer later in the future..... A Member has been kicked because he included apps that developers had told him to get rid of.
Click to expand...
Click to collapse
Conap said:
There was a version of wired tether put up here on xda somewhere that did work with our phones....
Click to expand...
Click to collapse
In here, the version that was taken from the EVO guys:
http://forum.xda-developers.com/showpost.php?p=7666883&postcount=12
tenzomonk said:
try the "new" DL and just flash over (no wipe should be needed). what does it say your "kernel" is under software info?
Click to expand...
Click to collapse
I have Conap's CFS #5
sickbox said:
In here, the version that was taken from the EVO guys:
http://forum.xda-developers.com/showpost.php?p=7666883&postcount=12
Click to expand...
Click to collapse
Why use this old 1.2 when the official 1.4 does it cleaner: http://code.google.com/p/android-wired-tether/
Perfect timing on this! My lady is techologically challenged and having a ROM like this is perfect. She kept busting my bawls about not having teeter... Every time I installed it via an APK it would always FC after a bit.
Edit this was on a different rom, so far only issue I've had with this rom is a FC when trying to auto-update google maps.
tenzomonk said:
you can do the same thing posted above
hmmm
this is completely stock... no extra scripts, no extra fonts, no a2sd, etc. it's stock... with july OTA integrated and deodexed. that's all i did. can you point out where the other completely stock ROM with JulyOTA integrated is? If i missed it, i apologize. again... other than not trashing bootloader, recovery, etc, it's as "stock" as it gets. no symlinks changed in update-script, etc. again, this is the only stock ROM w/July OTA integrated that i've seen on the forum. did i miss something? (Official Obsession is close... but that requires you flash over the update. not easy for beginning cooks trying to customize a ROM... and it's not deodexed)
the "other" 2 ROMs are different as well... one is almost stock, with just latest ChainsDD superuser (root) added (no a2sd), with Conap's CFS kernel. the other is the same, with latest a2sd added (which allows the ability to add cache2cache as well).
i've enjoyed PlainJaneT2... and it is still my base for TT2.1. i've given full props to you with links and request even for donations in that thread. if i've upset you, again, i apologize.
also, no "extra" apps (setcpu, etc) are included... i know the rules
i'm not trying to "ruin" any experience for anyone... or step on anyone's toes. i'm just trying to help out and contribute. certainly have never tried to upset anyone on this forum EVER!
Click to expand...
Click to collapse
Like I said I was just asking and playing devils advocate I was gone for a month a half so I have no Idea of what happened I'm just catching up. Take no offense to what I said I was just curious.
first post updated w/new Cache2Cache version
ALL CREDIT GOES TO ATINM FOR CREATING THIS(and allowing me to share)
Thanks To Kaik541 for being awesome....and being the main tester
Atinm currently has bigger fish to fry then this Kernel, therefore
THIS ISNT BEING SUPPORTED FOR FURTHER DEVELOPMENT
Kaik541 said:
guys, the "unsupported" part of this doesn't mean development has stopped or stalled, it means do not expect things like changelogs or walkthroughs. me and warri can help you troubleshoot, but installing this is done so at your own risk with no promises it will work.
Click to expand...
Click to collapse
Atinm has created a very nice Kernel, and has allowed me to share it with the Public. HOWEVER, there is no support offered, we have done some testing and it works for us, this does not mean we guarantee it will work for you:
Included:
Modified ClockworkMod Recovery to replace Stock 3e (Backup/Restore with Voodoo Enabled)
The Voodoo Lagfix
Captivate Kernel
Custom Boot Image Support (place any WVGA bootanimation.zip in either /system/media or /data/local thanks Kaik)
How To Install :
Download File From Link Below
Place the Link on your /sdcard/ (internal)
Flash through ROM Manager, or ClockworkMod Recovery
Enjoy the VooDoo Lagfix
If you are having issues with installation please follow KaiK's Instructions found here (can be used on 1.14)
Download:
http://github.com/atinm/captivate_multistage_initramfs/downloads
**Disclaimer** I am not responsible for anything that is done to your device. This is provided as is, I hold no liability for your actions.
I hate you wArri atinm, I just got Voodoo into my custom kernel...
Ok, well, guess this is no longer being worked on, I feel better now..
oh snap!
Flashing time again. mmmmmmm
THANKS!!
warri said:
ALL CREDIT GOES TO ATINM FOR CREATING THIS
Atinm currently has bigger fish to fry then this Kernel, therefore
THIS ISNT BEING SUPPORTED FOR FURTHER DEVELOPMENT
Atinm has created a very nice Kernel, and has allowed me to share it with the Public. HOWEVER, there is no support offered, we have done some testing and it works for us, this does not mean we guarantee it will work for you:
Included:
Modified ClockworkMod Recovery to replace Stock 3e (Backup/Restore with Voodoo Enabled)
The Voodoo Lagfix
Captivate Kernel
How To Install :
Download File From Link Below
Place the Link on your /sdcard/ (internal)
Flash through ROM Manager, or ClockworkMod Recovery
Enjoy the VooDoo Lagfix
Download:
http://github.com/downloads/atinm/captivate_multistage_initramfs/cwm-ext4-v1.11.zip
**Disclaimer** I am not responsible for anything that is done to your device. This is provided as is, I hold no liability for your actions.
Click to expand...
Click to collapse
I'm working on CyanogenMod6 for our phones and this happened to by on the way there because I was futzing in recovery so I put it out as ppl seemed to be asking for Voodoo support in Froyo. If it doesn't work for you, don't worry - the performance difference between stock RFS and Voodoo on Froyo isn't as significant as it was with Eclair (the 'Q' number is near 1400 rather than above 1700 - I guess still somewhat better than stock).
-Atin
atinm said:
I'm working on CyanogenMod6 for our phones and this happened to by on the way there because I was futzing in recovery so I put it out as ppl seemed to be asking for Voodoo support in Froyo. If it doesn't work for you, don't worry - the performance difference between stock RFS and Voodoo on Froyo isn't as significant as it was with Eclair (the 'Q' number is near 1400 rather than above 1700 - I guess still somewhat better than stock).
-Atin
Click to expand...
Click to collapse
haha, he posted this right as I finished up my Kernel, was about to update to beta9... heh
Thanks again you warri and atimn for all your hard work and help, will be applying this to my setup.
designgears said:
I hate you wArri atinm, I just got Voodoo into my custom kernel...
Ok, well, guess this is no longer being worked on, I feel better now..
Click to expand...
Click to collapse
It's cause I'll do it a whole different way next time. But don't let me stop you from working on the kernel, the more ppl who take up the slack the better so I can focus on what I need to work on (CyanogenMod!).
designgears said:
haha, he posted this right as I finished up my Kernel, was about to update to beta9... heh
Click to expand...
Click to collapse
Are you still going to post beta 9? I can't wait to try it!
airbillion said:
Are you still going to post beta 9? I can't wait to try it!
Click to expand...
Click to collapse
yup, just doing some final testing
AHHHH Thanks a million. I've been waiting for this since Froyo hit. Looking forward to B9 DG. Thanks for all the hard work guys!!
designgears said:
I hate you wArri atinm, I just got Voodoo into my custom kernel...
Ok, well, guess this is no longer being worked on, I feel better now..
Click to expand...
Click to collapse
You can work on the colorfix, and I believe you had the bootanimation.zip incorporated into your kernel?
Bowsa2511 said:
You can work on the colorfix, and I believe you had the bootanimation.zip incorporated into your kernel?
Click to expand...
Click to collapse
colorfix can't be done without sources and this kernel will have aosp bootanimation.zip support soon as well.
and speak of the devil, anyone wanting AOSP boot animation support, use this kernel here:
http://github.com/downloads/atinm/captivate_multistage_initramfs/cwm-ext4-v1.14.zip
same as above, flash in CWM, place any WVGA bootanimation.zip in either /system/media or /data/local
Kaik541 said:
colorfix can't be done without sources and this kernel will have aosp bootanimation.zip support soon as well.
Click to expand...
Click to collapse
That's right.. can't wait for our froyo source
Kaik541 said:
and speak of the devil, anyone wanting AOSP boot animation support, use this kernel here:
http://github.com/downloads/atinm/captivate_multistage_initramfs/cwm-ext4-v1.14.zip
same as above, flash in CWM, place any WVGA bootanimation.zip in either /system/media or /data/local
Click to expand...
Click to collapse
Is that a ext4/lagfix + bootanimation kernel only?
Is it 2.2, and does it have recovery 2e?
Kaik541 said:
and speak of the devil, anyone wanting AOSP boot animation support, use this kernel here:
http://github.com/downloads/atinm/captivate_multistage_initramfs/cwm-ext4-v1.14.zip
same as above, flash in CWM, place any WVGA bootanimation.zip in either /system/media or /data/local
Click to expand...
Click to collapse
Does that mean we can use custom boot animations now?
Bowsa2511 said:
That's right.. can't wait for our froyo source
Is that a ext4/lagfix + bootanimation kernel only?
Is it 2.2, and does it have recovery 2e?
Click to expand...
Click to collapse
All of the above. But CWM recovery is default, you can boot into 2e if you want from that. I prefer CWM recovery as my default, so that's how it is.
atinm said:
All of the above. But CWM recovery is default, you can boot into 2e if you want from that. I prefer CWM recovery as my default, so that's how it is.
Click to expand...
Click to collapse
With bootanimation support.. I assume unsigned .zips are supported?
It seems to hate clockwork... it won't install no matter whick way I flash it in clockwork
sent with mental telepathy
(CDE ROM + OCLF +z4mod)
Bowsa2511 said:
With bootanimation support.. I assume unsigned .zips are supported?
Click to expand...
Click to collapse
these two things are unrelated, bootanimation.zip goes on your phone, unsigned zips are run from recovery. this kernel as clockwork as the default recovery.
DOAlaboratories said:
It seems to hate clockwork... it won't install no matter whick way I flash it in clockwork
sent with mental telepathy
(CDE ROM + OCLF +z4mod)
Click to expand...
Click to collapse
works fine for me, but you can also try renaming it to update.zip and trying that way... the only way to tell if it's working is with a custom boot animation or verifying the output of build.txt in the root of the phone
Kaik541 said:
these two things are unrelated, bootanimation.zip goes on your phone, unsigned zips are run from recovery. this kernel as clockwork as the default recovery.
works fine for me, but you can also try renaming it to update.zip and trying that way... the only way to tell if it's working is with a custom boot animation or verifying the output of build.txt in the root of the phone
Click to expand...
Click to collapse
no dice that way either.all the update-script text comes up, says it's done flashing the kernel, and then reboots, but the name of the kernel doesn't change. plus when i tried as update.zip it stuck at the boot screen and i had to flash an older kernel to get it to boot.
Ihtfp69 tip toes in and closes the door
I realized after releasing a ROM that no one was using Koush's AnyKernel method for flashing kernels. This poses a problem for ROMs with custom ramdisks. Someone mentioned the AnyKernel method did not work on this phone. So I did some investigating. With a few changes to the script, I have it working perfectly.
Credits here, of course, go to Koush. I just modified his script. The kernel zip attached here contains the kernel from the latest leak. Because this uses the AnyKernel method, you can flash this on ANY GB Sense ROM and it will work and not break WiFi.
EDIT: I guess Ziggy did a version as well a few months ago. Here is a link to his: Ziggy's AnyKernel MOD
Download Mine --> Tbolt_AnyKernel.zip
a true asset to this community.
thanks for all your hard work!
cant wait for skyraider zeus v2
Sense ROMs only?
jc
ihtfp69 said:
Ihtfp69 tip toes in and closes the door
I realized after releasing a ROM that no one was using Koush's AnyKernel method for flashing kernels. This poses a problem for ROMs with custom ramdisks. Someone mentioned the AnyKernel method did not work on this phone. So I did some investigating. With a few changes to the script, I have it working perfectly.
Credits here, of course, go to Koush. I just modified his script. The kernel zip attached here contains the kernel from the latest leak. Because this uses the AnyKernel method, you can flash this on ANY GB Sense ROM and it will work and not break WiFi.
Download --> Tbolt_AnyKernel.zip
Click to expand...
Click to collapse
Surprised to see you here? Glad to see your support for the community.
mrchambo said:
Sense ROMs only?
jc
Click to expand...
Click to collapse
Yes, it's the stock kernel from the new leak, which is Sense.
Okay, thank you. That's what I thought...
jc
Applying this gave me bootloops in Gingervitis 1.2.1 GB. Won't go past the splash screen
mrchambo said:
Sense ROMs only?
jc
Click to expand...
Click to collapse
The scripts should work on AOSP and Sense ROMs. The kernel included is Sense only.
JaydenR said:
Applying this gave me bootloops in Gingervitis 1.2.1 GB. Won't go past the splash screen
Click to expand...
Click to collapse
Hmmm ... it shouldn't matter, but I will wake a look and see if I can duplicate it. Make sure the file you downloaded is around 3.4 MB. If not, grab it again.
First download was 2.89 second was 3.4 I believe. Both had the exact same result. Boot loops
Ziggy already did this for the tbolt. Ive been using anykernel for over a month now. It what iuse when i extract the kernel from synergy.
fixxxer2008 said:
Ziggy already did this for the tbolt. Ive been using anykernel for over a month now. It what iuse when i extract the kernel from synergy.
Click to expand...
Click to collapse
Is he sharing? I seem to be misinformed then. Why is everyone else still using boot.img files then?
ihtfp69 said:
Is he sharing? I seem to be misinformed then. Why is everyone else still using boot.img files then?
Click to expand...
Click to collapse
yeah it's under the thunderbolt section at ppcgeeks. been there for awhile now.
http://forum.ppcgeeks.com/htc-thunderbolt-development/143287-anykernel-thunderbolt.html
cool beans. I'll just link to his then.
What is the purpose of this kernel updater?
I'm not sure I understood how Ziggy explained it.
johnnysyeah said:
What is the purpose of this kernel updater?
I'm not sure I understood how Ziggy explained it.
Click to expand...
Click to collapse
lol! Gotta love Ziggy but, he definitely thinks on a higher plane than most! I have trouble following him lots of times as well.
ihtfp69 said:
Ihtfp69 tip toes in and closes the door
I realized after releasing a ROM that no one was using Koush's AnyKernel method for flashing kernels. This poses a problem for ROMs with custom ramdisks. Someone mentioned the AnyKernel method did not work on this phone. So I did some investigating. With a few changes to the script, I have it working perfectly.
Credits here, of course, go to Koush. I just modified his script. The kernel zip attached here contains the kernel from the latest leak. Because this uses the AnyKernel method, you can flash this on ANY GB Sense ROM and it will work and not break WiFi.
EDIT: I guess Ziggy did a version as well a few months ago. Here is a link to his: Ziggy's AnyKernel MOD
Download Mine --> Tbolt_AnyKernel.zip
Click to expand...
Click to collapse
I just tried this, and it broke Wifi on my Tbolt. Any idea what the reason could be? I extracted the Zimage from my target ROM, replaced it in the .Zip, and flashed it. Anything else I should be doing?
onyx_64 said:
I just tried this, and it broke Wifi on my Tbolt. Any idea what the reason could be? I extracted the Zimage from my target ROM, replaced it in the .Zip, and flashed it. Anything else I should be doing?
Click to expand...
Click to collapse
You need to pull the bcm from /system/lib/modules also.
Sent from my SHIFTAO5P using XDA App
DroidTh3ory said:
You need to pull the bcm from /system/lib/modules also.
Sent from my SHIFTAO5P using XDA App
Click to expand...
Click to collapse
oh, yeah, forgot to mention that I copied the 2 files (bcm4329* and sequans*) from the target ROM into /system/lib/modules After I had flashed. Should I have copied it to the .zip first and then flashed it? does it sit anywhere other than /system/lib/modules?
The reason i didnt do it is because I assumed the existing files should work.
onyx_64 said:
oh, yeah, forgot to mention that I copied the 2 files (bcm4329* and sequans*) from the target ROM into /system/lib/modules After I had flashed. Should I have copied it to the .zip first and then flashed it? does it sit anywhere other than /system/lib/modules?
The reason i didnt do it is because I assumed the existing files should work.
Click to expand...
Click to collapse
The bcm spits out at the end of compiling the kernel and it is specific to the kernel. Pull the zimage and the modules from the ROM, put them in the correct folders in the zip ... Wipe Cache and Dalvik for kicks and flash. Should be fine.
Sent from my SHIFTAO5P using XDA App
DroidTh3ory said:
The bcm spits out at the end of compiling the kernel and it is specific to the kernel. Pull the zimage and the modules from the ROM, put them in the correct folders in the zip ... Wipe Cache and Dalvik for kicks and flash. Should be fine.
Sent from my SHIFTAO5P using XDA App
Click to expand...
Click to collapse
Wow man.. you are quick. Let me try that way. Thanks so much!
UPDATE:
That worked like a charm!.. Flashed with the lib/modules after wiping cache n dalvik. Thanks again!
(6/30/15) Newest LLFK for T-Mobile Note EDGE N915T Lollipop.
Now has TCP congestion control options with default TCP Westwood
This version is flashable using TWRP.
Features:
SELinux=Permissive option
init.d support
adbd insecure
TCP congestion controls: TCP options include Westwood, cubic, reno among others: default is Westwood
Modifications that need to be made when using LLFK kernel
1)In build.prop set
ro.securestorage.support=false
2)For those that use AllShare Cast you will need to do two things.
First, add the following line at the end of build.prop
wlan.wfd.hdcp=disable
second, you need to have the Xposed module Wanum Xposed installed. In Wanum select "security hacks" then check box of Fake system status
Download link:
https://www.dropbox.com/s/6bg9l8qqcmmh83x/llfk_permissive_initd_adbd_tcp_lpop.zip?dl=0
Check below for other information that might come in handy and good luck!
(06/11/15)New Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (lollipop)
I've added adb insecure to kernel. This gives you root access to modify /system on phone from a pc
Features:
SELinux = Permissive option
init.d support
adb insecure
download link
https://www.dropbox.com/s/kr7xb22449p497w/llfk_permissive_initd_adbd_lpop.zip?dl=0
(06/10/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T)
Two new flashable kernels. One for Lollipop the other for Kitkat.
Lollipop: This new version has init.d support so, for example, you can write scripts that run on boot up. (more below).
Features:
SELinux = Permissive option
init.d support
https://www.dropbox.com/s/k8w423ecoj1covs/llfk_permissive_initd_lpop.zip?dl=0
Kitkat:This version now has TCP congestion control options available (e.g. Westwood)
Features:
SELinux = Permissive option
init.d support
adb insecure (allows you to have r/w access to phone's /system from you pc)
TCP congestion control options
Thanks to JT man for testing
https://www.dropbox.com/s/jbifzsuztb73wpg/llfk_permissive_initd_adbd_tcp_kkat.zip?dl=0
Example of init.d script to automatically set SELinux=permissive given here
https://forums.oneplus.net/threads/how-to-selinux-permissive.314120/
couple notes on how-to-selinux-permissive
1)You only need have permissions of /sys/fs/selinux/enforce set to 644
2)Make sure permission of init.d script is 775
One more thing, knox based warnings can be silenced using wanum.
(05/27/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T) running Lollipop.
For those that miss having SELinux=Permissive on their T-mobile Note Edge running lollipop, here is a kernel
that supports this setting. The kernel is based on the Tmobile Note Edge Lollipop source code. The only thing that was
changed was a setting in the kernel's Makefile to allow the user to choose whether they want to have SELinux=Permissive
as described for the previous Kitkat version of LLFK below.
NOTE: This time around, the kernel is packaged as a zip file than can be directly flashed in recovery.
But before I go any further I need to give credit to @TEKHD for providing a zipped
version of the T-Mobile kernel I could modify and, in addition, for testing it.
Please buy him a well deserved cup of coffee!
Once you have flashed the kernel and rebooted you are ready to set SELinux=permissive by opening a terminal and typing
su
and
setenforce 0
To check it worked, go to settings > About device and you should see, under SE for Android status, that it is now set to Permissive.
An alternative way to change the setting with this kernel is to use the apk SeLinuxModeChanger. Unfortunately this apk is no longer
available at the play store but you can still download it from the F-Droid site.
https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
A third option would be to set up an init.d script if your rom permits it.
I must admit, at the time of this writing, I'm still on KitKat and have yet to try this on my phone. I'll be checking out lollipop soon
but till then, let me know if/how it works. If successful I'll start adding a few more low lying fruit I've picked!
Remember to do a full nandroid back-up before trying this so your phone can return to its original state before trying llfk if needed.
The usual disclaimer applies!
Good Luck!
lollipop LLFK download link:
WAIT! Only one person has tried this version and although it worked for him, I still consider it beta at best. You have been warned!
WAIT! WAIT! One more thing: You need to do the following otherwise you may experience problems with WIFI:
Download the apk BuildProp Editor and use it to set
ro.securestorage.support=false (thanks @TEKHD for checking this)
WAIT! WAIT! WAIT! May be an issue with private mode not working (see http://forum.xda-developers.com/showpost.php?p=61033627&postcount=109 ). I did not have this problem on kitkit. I am unable to test till next week so if someone can check it out that would be great.
http://www.4shared.com/zip/Z8g1u3FHba/llfk_permissive_lpop.html
dropbox link
https://www.dropbox.com/s/ud84t2fc3n9sqdg/llfk_permissive_lpop.zip?dl=0
Below only applies to the KitKat version.
(04/07/15) Update:
Well, I had a little time and decided to add a feature to LLFK. So for now it has the following three capabilities.
1)Allows you to set SELinux = Permissive
2)adb insecure
3)init.d support
Here is the link for the tar file. (follow same instructions given below to install via ODIN):
http://www.4shared.com/archive/2PepSJcPce/llfk_permissive_initd_adbtar.html
Let me know if/how it works...
New features:
The kernel is now adb insecure. This was accomplished by replacing the adbd file in ramdisk with one due to @freeza. Big thanks to him (as in buy him a cup of coffee!) for giving me permission to use it. With adb insecure you can now remount system as r/w from your pc which can come in handy at times.
The kernel has init.d support (Allows you to run scripts from boot) by modifying the ramdisk using the instructions in STEP 1 (Making kernel ready) of the following post
http://forum.xda-developers.com/showthread.php?t=2287540
So this part is done for LLFK
For it to work, the user still needs to make some minor modifications (add a file and create a directory) in their rom. To do this, please follow all 4 parts of STEP 2 (Making Rom Ready) in the same post.
Once you have completed STEP 2 you are ready to try some scripts.
You can search the Internet for init.d scripts to try.
For example there are some init.d scripts in the later half of the following post to give you an idea.
http://en.miui.com/thread-5685-1-1.html
If folks can experiment to see what scripts work I will make a list and post it here.
Seems to work OK on Hyperdrive and Lab Rats (let me know otherwise).
CAVEAT: When testing whether init.d support was successfully implemented I had tried some scripts (like echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb; ) that should have modified some kernel settings at boot up. But as it turns out there are a set of scripts that run after boot up that supersede these settings. These scripts are in the file /etc/init.qcom.post_boot.sh. (some other neat stuff to play around with in there!) If you want those scripts to not take effect you can simply comment them out and then your init.d scripts will work.
The usual disclaimer and Good Luck
Original post 1/30/15
**********************************************************************************************************************************************************************
Hi. I thought I'd give out this kernel which allows one to set SELinux=permissive for a rooted T-Mobile Note Edge with base NK3. This setting is needed if you would like to run Linux on Android and, I believe Viper4Android if you are so inclined, as well as some other specialized apps (for future reference, let me know what apps you use that need this setting). Once you have loaded this kernel you can use the app SELinuxModeChanger, found in the play store, to set SELinux=Permissive and back to Enforcing. Note, this setting is maintained until you change it back in the app (rebooting will not change the setting). Anyways, what I am providing is a gzipped tar file that you can download, gunzip and then load on your phone using ODIN (version 3.07 worked fine for me, goes in PDA). Remember, this kernel is ONLY for the T-Mobile N915T NK3 rom. Actually, I have only tested it on the Lab Rats rom so hopefully it will work on other roms for T-Moble N915T with NK3 base.
As most folks like to have a name for their kernel I've decided to call this the "Low Lying Fruit Kernel" (LLFK) because it only has a minor change made to it. Indeed this kernel is about as low as it goes (lol) as not a single line of code is changed. I only changed an option in the Makefile from true to false. Details are given at the following github site.
https://github.com/mscion/Permissive-Kernel-N915T-EDGE/
Anyways, I've been using this kernel for over 10 days with no problems, but, of course , for those that try LLFK, the usual warnings apply! I am not responisble for anything that happens to your device as a conseqence of
using this kernel. Indeed you have to be crazy to try it as I have zero experience at this! You also might want to read this before you try setting SELinux=permissive:
http://en.wikipedia.org/wiki/Security-Enhanced_Linux
One more thing, while my preference is that an experienced dev make a kernel worthy of the N915T EDGE, I am open to suggestions to make some more modifications assuming the request are somewhat consistent with the philosophy of LLFK.
Thanks to @jimmydene84 for boot.img and @deeznutz1977 for testing!
Don't forget to do a full back up! Good luck!
Kernel Download link: For SELinux=Permissve option only
http://www.4shared.com/archive/oH5fE053ba/llfk_permissivetar.html
Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?
VenpaCasa said:
Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?
Click to expand...
Click to collapse
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...
Awesome @mscion
deeznutz1977 said:
Awesome @mscion
Click to expand...
Click to collapse
Thanks! What would be even more awesome is if someone tries it and it works! lol.
I'll flash it now kind sir
mscion said:
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...
Click to expand...
Click to collapse
Omg dude if ur really serious, hell yeah I'm willing to test. I'm extremely greatful n lost for words right now. Thanks so much for just attempting ?? at least. Made my day lol
deeznutz1977 said:
I'll flash it now kind sir
Click to expand...
Click to collapse
I hope you mean Odin it! Drum roll please....
mscion said:
I hope you mean Odin it! Drum roll please....
Click to expand...
Click to collapse
kernel is not se android enforcing
@mscion you still had to use the selinux changer app correct?
deeznutz1977 said:
kernel is not se android enforcing
Click to expand...
Click to collapse
Hi @deeznutz1977. Depending on rom, I think when you boot up you will get that message. Please check in settings > about device and see what SE for android is showing. For now I have pulled the kernel because I unwittingly used the boot.img from lab rats rom to pack in my zImage file that allows permissive setting, cause I thought it was not modded. I am currently waiting to hear from @jimmydene84...
deeznutz1977 said:
@mscion you still had to use the selinux changer app correct?
Click to expand...
Click to collapse
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...
mscion said:
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...
Click to expand...
Click to collapse
Stock deodexed. And sorry about not reading the op. Don't you know that all of the cool people don't read ops
Sent from my SM-N915T using Tapatalk
@mscion I asked jimmydene to pm you ...
deeznutz1977 said:
@mscion I asked jimmydene to pm you ...
Click to expand...
Click to collapse
Thanks very much! We're all good. I'm putting the link back up shortly.
Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.
VenpaCasa said:
Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.
Click to expand...
Click to collapse
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)
mscion said:
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)
Click to expand...
Click to collapse
Honestly your awesome. I was starting to regret my purchase too. I'll assume you weren't asking me if it's ok but if you were, yeah that's fine. I'm actually any using that ROM
EDIT: Just saw your edit n thanks (to both) that's so awesome! I owe you guys!
When ubr done are you going to post here or a new thread?
VenpaCasa said:
When ubr done are you going to post here or a new thread?
Click to expand...
Click to collapse
Just pm'd you with link. If it works I'll post it in this thread.
I know there are a few kernels/boot.img to force native 4K all the time on AOSP based ROMs, but are there any for Stock or Stock based ROMS?
*Dang! Thought I was in the Q&A and just realized I posted this in the wrong section and can't delete or move it.
You might be able to remove the 1080p configuration in the copyleft archive just like in the aosp kernel to get a 4k stock kernel. I haven't looked at it so I don't know if it will work for sure, but its worth a try.
Edit: Looks like it might have worked.
Sepo190 said:
You might be able to remove the 1080p configuration in the copyleft archive just like in the aosp kernel to get a 4k stock kernel. I haven't looked at it so I don't know if it will work for sure, but its worth a try.
Edit: Looks like it might have worked.
Click to expand...
Click to collapse
Could You share the Image with us?:angel:
Miustone said:
Could You share the Image with us?:angel:
Click to expand...
Click to collapse
Yeah, sure. This is a .235 kernel that has been working surprisingly well for me. I used the ramdisk from shoey63's kernel repack here https://forum.xda-developers.com/xz-premium/development/kernel-repository-t3801795, so you need to flash that drmfix.zip too.
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Does anyone know what changes the drmfix requires other than adding "export LD_PRELOAD drmfix.so:drm****.so" to the init.environ.rc in the ramdisk?
Sepo190 said:
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Click to expand...
Click to collapse
If I'm currently on 235, basically all I need to do is flash your kernel + drmfix, right? Or is a fresh install really needed? Btw, do you pass safetynet on your kernel?
iArvee said:
If I'm currently on 235, basically all I need to do is flash your kernel + drmfix, right? Or is a fresh install really needed? Btw, do you pass safetynet on your kernel?
Click to expand...
Click to collapse
I'm pretty sure you're going to need to do a fresh install. You can try without, but I have a feeling you are going to bootloop. It doesn't pass safteynet, but I can probably add the patch in for you. I'll take a look at it later tonight or tomorrow. Now that .270 CE1 is out I was going to move to that, but I can do the .235 one too if you want.
Sepo190 said:
I'm pretty sure you're going to need to do a fresh install. You can try without, but I have a feeling you are going to bootloop. It doesn't pass safteynet, but I can probably add the patch in for you. I'll take a look at it later tonight or tomorrow. Now that .270 CE1 is out I was going to move to that, but I can do the .235 one too if you want.
Click to expand...
Click to collapse
If it's not too much trouble, can you do the .235? I'm most likely not going to be updating to 270 any time soon. Willing to try it out without a fresh install.
This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?
gaijin1% said:
This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?
Click to expand...
Click to collapse
https://mega.nz/#!JhtF0bCJ!G0zOmqZYoNeFwSvLQnh5GAMh3_E--XQWAYjzrm4buC0
Yeah. I'll do one for .270, but it might be a week or so. I just got really busy.
Sepo190 said:
https://mega.nz/#!JhtF0bCJ!G0zOmqZYoNeFwSvLQnh5GAMh3_E--XQWAYjzrm4buC0
Yeah. I'll do one for .270, but it might be a week or so. I just got really busy.
Click to expand...
Click to collapse
That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated
Watching gravure will be so much more satisfy ing, thanks
gaijin1% said:
That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated
Click to expand...
Click to collapse
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Sepo190 said:
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Click to expand...
Click to collapse
I actually got it set up with 235, but for some reason I can't get it to root. Magisk installs fine, but nothing can get root permission. What version of Magisk did you use?
gaijin1% said:
I actually got it set up with 235, but for some reason I can't get it to root. Magisk installs fine, but nothing can get root permission. What version of Magisk did you use?
Click to expand...
Click to collapse
I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?
Sepo190 said:
Yeah, sure. This is a .235 kernel that has been working surprisingly well for me. I used the ramdisk from shoey63's kernel repack here https://forum.xda-developers.com/xz-premium/development/kernel-repository-t3801795, so you need to flash that drmfix.zip too.
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Does anyone know what changes the drmfix requires other than adding "export LD_PRELOAD drmfix.so:drm****.so" to the init.environ.rc in the ramdisk?
Click to expand...
Click to collapse
So if this actual 4k?? Like native 4k?? How's battery life/performance??
Sepo190 said:
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Click to expand...
Click to collapse
I tried several things but couldn't get 235 to root for the life of me.
Now I really want the new ROM [O][8141/8142][.270] M-ROM: Xposed, Daydream compatible so I hope that a .270 based 4K kernel will work with it. Really want that Daydream in 4K. I wonder if your .235 kernel will work with it or if your .270 version will get the drm fix using the Kernel Patch from JanJan.
Sepo190 said:
I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?
Click to expand...
Click to collapse
Hi man, sorry to interrupt your business, but are there any updates? Could you share with us how exactly you implement the 4k in the kernel? Maybe we could use the manual you're following, and do the work by ourselves.
I'm really curious. More and people are joining in
saved-j said:
Hi man, sorry to interrupt your business, but are there any updates? Could you share with us how exactly you implement the 4k in the kernel? Maybe we could use the manual you're following, and do the work by ourselves.
I'm really curious. More and people are joining in
Click to expand...
Click to collapse
Sorry I haven't given an update in a while. I haven't been on here in a while. I had an unexpected move, so my server wasn't hooked up and then I didn't have internet for a while. Just got it hooked up today actually. I have one with the drm fix working for the newest update using the ramdisk from JanJan's kernel. I can take another look at .270 probably this weekend if you want. I don't have a manual or anything, I'm just removing the 1080p configs from the dts file. I don't remember the file path off the top of my head and I'm not home right now.
It's not possible to enable 4k just édit build prop?
Envoyé de mon G8141 en utilisant Tapatalk
16.20 kernel
Here is a 4k 16.20 kernel that has been working for me for the past week if anyone wants it. I used the ramdisk from JanJan's kernel. Flash it and then everything in his drm-patching zip. The file I have been editing is dsi-panel-maple.dtsi btw, since someone asked earlier.
https://mega.nz/#!R5UhhKjA!U2kp2Zl4gYGddiSIkpJMaOlVYuAcakb514CwHq3jEH4