Kernel Flasher invalid ramdisk in boot.img: How to Fix
Recently, a user dropped in his query in my Telegram channel about the inability of the Kernel Flasher app to function properly even after successfully obtaining root via KernelSU. When the basic workarounds like using the nightly build of KSU and toggling Flasher from the app’s SuperUser section didn’t get the job done, I decided to emulate this issue on my end, as it would then be easier to find the root cause of the problems and hence find the fix.
But when I proceeded to do so, I was greeted with an altogether different error. After obtaining root, when I launched Kernel Flasher, it gave out the “invalid ramdisk in boot.img” error. The app will display this error full screen, and won’t let you use any of its features. Fortunately, the fix for this problem is quite a short and easy one. So without any further ado, let’s check it out right away.
Fix Kernel Flasher invalid ramdisk in boot.img
Before starting, please take a complete device backup, just to be on the safe side. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.
- First off, uninstall the Kernel Flasher app from your device.
- Then download and install the allow-error version of Kernel Flasher. Now launch it.
- While you might still see the “invalid ramdisk in boot.img” at some places, that wouldn’t conflict with the app’s normal usage behavior.
- I was able to flash the AnyKernel ZIP in the active slot while the error was still being shown.
- The result? The flashing went fine without any issues, and I’m currently on that custom kernel!
- KernelSU Shows Rooted, But Apps Cannot Access Root [Fix]
- KERNELSU V2 SIGNATURE NOT FOUND IN KERNEL [Fixed]
- Root via AnyKernel and Magiskboot [Without Patching Init_Boot]
- KernelSU SUCompat Disabled/Modules Missing [Fixed]
- How to Root via Magisk when it’s Already Rooted via KernelSU
(Cancel Reply)
Δ
