How to fix baseband unknown caused by Custom Kernel

rahmatyus20

Member
May 3, 2016
17
1
0
I have a J5 Pro SM-J530Y variant.
I installed several Custom ROMs from ROM Section. Most of them said that their Custom ROMs support all models of J5 Pro (2017). But, after I install it, it has a bug on Baseband which is Unknown. I tried many ways to fix it, like restoring EFS and Modem backup, reflash Modem And BL file via Odin, and also reinstall ROM twice. They said that I need to upgrade my device's bootloader (firmware) to the latest one. I did it but still Baseband became unknown Everytime I install their Custom ROM.
Then I doing a research. The problem is on Kernel. I tried to restore "Magisk Patched Stock Kernel" after installing those custom ROMs, Baseband is fixed. I also tried other way by replacing boot.img-dtb and boot.img-zImage from stock kernel to custom kernel, and it's fixed the problem. Problem solved here for OneUI custom kernels only, because there's only OneUI with working Baseband kernel for my device (stock kernel obviously).
But, then, I found a thread that we can install GSI on this device. I tried to install one (treble GSI). Most of them are bootable, but the problem come again. Baseband Unknown. I tried to fix it using the way I did before but it got bootloop. I also tried to replace boot.img-dtb and boot.img-zImage from stock kernel (OneUI) to custom treble kernel for my device, it got bootloop. Of course, because I use stock kernel base OneUI not AOSP.
How to fix this? Anyone please help me to fix this issue. There's no development for my J5 Pro SM-J530Y variant. I need guidance to fix the Baseband Unknown which is causing by Kernel. I also need a guidance to fix or edit boot.img-dtb and boot.img-zImage, do I need a device tree blob files? Please tell me how to do. Please help