forced 4K boot.img for stock?

[gaijin1%]

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.

 

[Sepo190]

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.

 

[Miustone]

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.

Could You share the Image with us?:angel:

 

[Sepo190]

Could You share the Image with us?:angel:

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?

 

[iArvee]

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

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?

 

[Sepo190]

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?

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.

 

[iArvee]

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.

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.

 

[gaijin1%]

This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?

 

[Sepo190]

This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?

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.

 

[gaijin1%]

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.

That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated

 

[amakuramio]

Watching gravure will be so much more satisfy ing, thanks

 

[Sepo190]

That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated

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.

 

[gaijin1%]

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.

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?

 

[Sepo190]

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?

I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?

 

[raven213]

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?

So if this actual 4k?? Like native 4k?? How's battery life/performance??

 

[gaijin1%]

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.

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.

 

[saved-j]

I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?

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

 

[Sepo190]

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

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.

 

[NYGGAZ]

It's not possible to enable 4k just édit build prop?

Envoyé de mon G8141 en utilisant Tapatalk

 

[Sepo190]

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