Flashing kernel.img not working

Echoa89

So it's been a while since I worked on my rk3288 (it got crushed accidentally). I compiled the kernel from source like I always use to on 4.4 when I made my overclocking kernel that I posted a how to on my old forum account I can't access anymore.

Anyway the issue is when I flash the kernel.img the kernel doesn't change, tried every combo of kernel+boot+parameter+etc. That I could think of to get it to work but nothing. No matter what I do I can't flash the kernel even though it says successful nothing changes. It's always the same default kernel regardless of what IMG i flash

I'd like to add that I'm using the flashtool from the mini rk3288 board as the links in the original rk3288 wiki are broken and don't go anywhere. Is this a flash tool issue? What is going on with the Android 5.1 source? Did the location for the kernel change?

Any help is appreciated as I'm out of the loop on things and following how I use to do it and how the wiki says to don't work (and wiki isn't up to date it seems)

leung先森

You need to flash a boot.img without resource
if boot.img is with kernel and resource , whatever you change kernel to flash , it was not working.

Echoa89

leung先森 Posted at 12/29/2017 14:52
You need to flash a boot.img without resource
if boot.img is with kernel and resource , whatever y ...

My kernel and boot.img are separate, so you're saying I need to pack the kernel into the boot.img now? Didn't have to do that before but if that's the case easy enough
It use to be just flash resource+kernel.img

leung先森

Echoa89 Posted at 12/29/2017 15:27
My kernel and boot.img are separate, so you're saying I need to pack the kernel into the boot.img  ...

U just run "./mkimage.sh" under the root directory of the SDK.
then flash the boot.img , your kernel and resource will be effective

mikecarney

In my spare time, I like to play the thrilling and captivating online snowboarding game snow rider. Players embark on an exhilarating journey down snow-capped slopes that is full of surprises, leaps, and obstacles.

jennykang

It sounds like the flash tool might not be writing the new kernel to the correct location or partition. A few things to check:
- Make sure your `parameter` file matches the current partition layout and points to the correct kernel partition.
- Try unpacking the boot.img using tools like `rk-unpack` or `Android Image Kitchen` to verify what's inside.
- Are you flashing in **MASKROM** mode or **Loader** mode? Some tools behave differently depending on mode.
- If you built your kernel correctly but it's not changing, maybe the bootloader is ignoring the new kernel due to signature checks or config mismatch.
Let me know what your `parameter` file looks like - happy to take a look, steal a brainrot