Anyone know anything about this line i keep seeing in my kernel boot up logs? This is an ICS kernel for the mecha
kgsl_ioctl_rb_issueibcmds| invalid cmd buffer ibaddr 000171b0 sizedwords 1
It seems that the boot process encounters this and starts re-processing from the htc-acoustic peice onwards, until the above is encountered. Stuck in a loop.
Any help is much appreciated. Thanks
Related
Anyone know anything about this line i keep seeing in my kernel boot up logs?
kgsl_ioctl_rb_issueibcmds| invalid cmd buffer ibaddr 000171b0 sizedwords 1
It seems that the boot process encounters this and starts re-processing from the htc-acoustic peice onwards, until the above is encountered. Stuck in a loop.
Any help is much appreciated. Thanks
Hi,
I'm porting the cyanogenMod12.1 to a new device, as I have the source code of the device, so I port the bootloader and kernel source to cyanogenMod project and use the many config files under /device/../..
And then make the bootimage, but after I flash the boot.img to the device, it failed with below errors.
[400] use_signed_kernel=1, is_unlocked=1, is_tampered=0.
[400] boot_verifier: Device is in ORANGE boot state.
[410] Device is unlocked! Skipping verification...
[410] Loading boot image (31348736): start
[610] Loading boot image (31348736): done
[840] ERROR: Bad magic in device tree table
[840] ERROR: Cannot validate Device Tree Table
[840] ERROR: Could not do normal boot. Reverting to fastboot mode.
[850] fastboot_init()
And I unpacked the boot.img, and I found the "BOARD_DT_SIZE 6868992" which is different with the value "BOARD_DT_SIZE 8192000" which unpacked from the original boot.img getting from the device.
Can anyone tell me what's wrong with my boot.img ? And where the "BOARD_DT_SIZE " is set ?
Thanks.
Linda
lindakang2007 said:
Hi,
I'm porting the cyanogenMod12.1 to a new device, as I have the source code of the device, so I port the bootloader and kernel source to cyanogenMod project and use the many config files under /device/../..
And then make the bootimage, but after I flash the boot.img to the device, it failed with below errors.
[400] use_signed_kernel=1, is_unlocked=1, is_tampered=0.
[400] boot_verifier: Device is in ORANGE boot state.
[410] Device is unlocked! Skipping verification...
[410] Loading boot image (31348736): start
[610] Loading boot image (31348736): done
[840] ERROR: Bad magic in device tree table
[840] ERROR: Cannot validate Device Tree Table
[840] ERROR: Could not do normal boot. Reverting to fastboot mode.
[850] fastboot_init()
And I unpacked the boot.img, and I found the "BOARD_DT_SIZE 6868992" which is different with the value "BOARD_DT_SIZE 8192000" which unpacked from the original boot.img getting from the device.
Can anyone tell me what's wrong with my boot.img ? And where the "BOARD_DT_SIZE " is set ?
Thanks.
Linda
Click to expand...
Click to collapse
Sounds like your trying to hack into someone else device stay out of other peoples phones
Sent from my XT1064 using Tapatalk
I've compiled it without any errors and applied the necessary patches too. I used cm12.0's boot.img so that I can get logcat (can't get logcat from cm12.1's boot.img). But whenever I try to boot cm12.1, it stucks at bootlogo and never goes ahead. I can get logs from adb but can't figure out, can you help me fix this problem while booting? Here's the logcat: https://paste.ee/p/A5GHK
I contacted a developer and he said that the problem is in this line:
Code:
[ 01-27 10:33:43.634 116: 116 E/HAL ]
load: module=/vendor/lib/hw/gralloc.mt6589.so
dlopen failed: library "libcorkscrew.so" not found
But I'm not sure on how to fix it, I applied a patch regarding libcorkscrew but then too can't fix that. Help me please. Thank you
early console in decompress_kernel
input_data: 0x01556101
input_len: 0x004eb1fd
output: 0x01000000
output_len: 0x00a30490
run_size: 0x00adc000
Decompressing Linux... Parsing ELF... No relocation needed... done.
Booting the kernel.
same message displayed both the time first i tried with the 64 bit version then the 32 bit
please help.
Same happend to after updating to 2.0.402
and besides from that message, below appears this:
.
[ 0230018] Failed to find cpu0 device node
Detecting android-x86... foun at /dev/sda7
Checking data partition ...
[email protected]_x86_64:/ #
Hi everyone,
I have recently been trying to port Ubuntu Touch to our beloved surnia.
I'm using the phablet-5.1 tree with AOSP-5.1 device, vendor, kernel and other repositories.
I managed to finish the build with the kernel config adapted to work with Ubuntu. (using jamino's phablet-porting-scripts (on github) and patching some files about uid/gid errors). But this isn't the problem, the default defconfig causes the same problems.
I can confirm my kernel/e3 recovery both work and can mount partitions etc, but only when I'm using the
Code:
fastboot boot recovery.img
command AND my custom boot.img isn't flashed to the device.
When trying to boot the recovery directly from the phone I get a
Code:
Error: Failed to load kernel!
error message in the bootloader log.
If my boot.img is flashed to the phone, whatever file I try to load with
Code:
fastboot boot
, I get an error from my computer :
Code:
booting...
FAILED (remote failure)
but no error from the phone
I had to replace the prebuilt gcc toolchains in the android source tree with my system's ones, could it cause the problem?
I'm quite new to android development and all so please don't blame me if the fix is obvious.
Thanks in advance