Quote:
Originally Posted by vicinc
ok. more digging here. Looks like my ubifs partition is badly "injured" (which according to ubifs zealots is impossible).
it looks like is recovery is trying to read something (i think the device serial - as I think is inserted later during update)
[ 16.404747] EXT2-fs (ram0): error: ext2_check_page: bad entry in directory #4136: : directory entry across blocks - offset=1024, inode=1073783265, rec_len=41760, name_len=131
[ 16.420664] EXT2-fs (ram0): error: ext2_check_page: bad entry in directory #4218: : rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
[ 16.434924] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[ 16.447391] Rebooting in 1 seconds..
and than fails and reboots. looks like the menu / rotate buttons are working, but the recovery is crippled not to proceed if the serial on sys/class/graphics/fb2 properties is missing. anybody has an idea about a modified update.zip that does not check this?
|
This is what I was talking about (check my first reply about a corrupted file system)...It's not the ubifs partition that's b0rked though, it's an ext2 partition. The problem is that the kernel itself can't load. The kernel is really important, and if the update script its trying to load it, I'm sure it is for a reason.