pomelohan
commented
2 months ago It's really hard to fix without device. If you have kernel source code, you can recompile kernel with CONFIG_KALLSYMS=y and CONFIG_KALLSYMS_ALL=y if possible.
Open Skorpion96 opened 2 months ago
pomelohan
commented
2 months ago It's really hard to fix without device. If you have kernel source code, you can recompile kernel with CONFIG_KALLSYMS=y and CONFIG_KALLSYMS_ALL=y if possible.
Skorpion96
commented
2 months ago Will give a try
MaiSan9999
commented
3 weeks ago Will give a try
hey did you manage to boot with apatch? same issue flashed patched boot.img with trwp now it's stuck on bootlogo_android.bmp
Skorpion96
commented
3 weeks ago Will give a try
hey did you manage to boot with apatch? same issue flashed patched boot.img with trwp now it's stuck on bootlogo_android.bmp
I still have to try, I think we have to build it or wait for apatch to support CONFIG_KALLSYMS_ALL=n
MaiSan9999
commented
3 weeks ago Will give a try
hey did you manage to boot with apatch? same issue flashed patched boot.img with trwp now it's stuck on bootlogo_android.bmp
I still have to try, I think we have to build it or wait for apatch to support CONFIG_KALLSYMS_ALL=n
before flashing the patched boot.img i checked for requirements and it actually output CONFIG_KALLSYMS_ALL=y so i don't know why it didn't work. mariko oled
Skorpion96
commented
3 weeks ago Will give a try
hey did you manage to boot with apatch? same issue flashed patched boot.img with trwp now it's stuck on bootlogo_android.bmp
I still have to try, I think we have to build it or wait for apatch to support CONFIG_KALLSYMS_ALL=n
before flashing the patched boot.img i checked for requirements and it actually output CONFIG_KALLSYMS_ALL=y so i don't know why it didn't work. mariko oled
Well.... The real problem here is that we can't do boot logs so knowing why it fails to boot is tricky
Please check before submitting an issue/在提交 issue 前请检查
Version requirement/版本要求
Describe the bug/描述 bug
I patched boot from Lineage from switchroot and Crdroid from:https://github.com/Lost-Entrepreneur439/nvidia-tegra-x1-crdroid-releases/releases/tag/02-15-2024 but on both it was stucking on logo so i think APatch is incompatible with Nintendo Switch. All this said would be possible to make it compatible? I'm using a Nintendo Switch lite with a Modchip on latest 18.0.0 firmware on hekate and nyx. To flash the patched boot i used TWRP recovery. I will try now to compile KernelSU, let's see what will happen
Reproduce method/复现方法
Extract boot image from lineage or crdroid or wathever rom zi, give it to APatch app, let it patch. After that reboot the nintendo switch to TWRP, then tap Install, install image, select the patched image, select the boot partition, then tap reboot. After doing all these steps the device will remain on switchroot lineage bootlogo
Expected behavior/预期行为
Obliviously the expected behaviour is that it would pass to the next boot phase (bootanimation) and boot correctly
Actual behaviour /实际行为
The device stucks on bootlogo after APatch image flash, while for example Magisk works, and it's not a problem of permisive kernel as that Crdroid rom i tried had it by default.
Screenshots/截图
No response
Logs/日志
About the logs maybe tomorrow i will try to do some, although since the device stucks on bootlogo maybe i won't be able to take them
Device Name/设备名称
Nintendo Switch/Nintendo Switch Lite (my model)
OS Version/系统版本
Android 11
APatch Version/APatch 版本
Latest
Kernel Version/内核版本
4.9.135
KernelPatch Version/KernelPatch 版本
-4.9.135 ? i would say i lie i swear, but i gave you the sources so better than this....
Additional context/其他信息
here are kernel sources:https://github.com/CTCaer/switch-l4t-kernel-4.9/tree/linux-dev I just hope this won't be closed as would be great to have a good root on the switch and sadly magisk isn't anymore in my opinion as any app can see it. So please if possible let's fix APatch on the switch. Obliviously i will give a try on KernelSU if possible (let's see if tomorrow i can compile the kernel with ksu)