Code:
kinit: Unable to mount root fs on device dev(179,2)
No file-system on /dev/mmcblk0p2 (device 179,2)
It got trashed in the process.
There is no reason to version match parts of 'main' with parts of 'diags' - -
The series 5 devices are true 'dual boot' - like having WinXP and Win## installed on the same computer.
Not a big deal, you can run approximately forever without 'diags' system.
And, it can be installed with fastboot (although you still need the serial port to get into fastboot).
Now all we need is a volunteer with a working KV to grab an image copy of the 'diags' kernel and OS file-system (I don't have a KV and neither does NiLuJe).
By the way - This device is a KV - since it appears to have working hyptic buttons - but it does not behave as expected for a KV.
What are the first six characters of the serial number? <<--- important info.
What firmware version (in 'main') is shown as installed? (including build number).
Both found at: Home -> Menu -> Settings -> Menu -> Device Info
Did you have to re-name the image file I sent you?
Did you have to do anything unexpected to use it?
The u-boot version **should** have changed, that is expected, since the KV-5.6.5 update package contains a (main) u-boot image.
Plus, this is an original factory firmware build, from a machine shipped the first day -
Long before the December build date of the u-boot you did have on it.
PS: Keep the device away from a network connection - - we don't want it updating to the current 5.6.5 just yet.
Plus: It now claims to be a Special Offers device - that wasn't evident before.
So it will be hungry for a network connection - keep it off the network.
Your (diag) u-boot and kernel/initramfs (a single image file) is working just fine, don't mess with it.
The device can be jail broken with what you have now (from the 'diags' initramfs).
Although I'll let NiLuJe speak up about where /dev/mmcblk0p1 should be mounted for it to work (it's a recent refinement to the JB process).