Proper boot.img compile code?

[Guest Harness]

Just edited old topic instead of making another new.

Edited November 25, 2010 by Harness

[Guest pajn]

1. Use adb reboot bootloader after you have activated usb debugging 8you can find adb in malez install packages)

2. What I can remember, yes. Try? It will probably need to be signed.

[Guest Harness]

1. Use adb reboot bootloader after you have activated usb debugging 8you can find adb in malez install packages)

2. What I can remember, yes. Try? It will probably need to be signed.

I can't get my phone to recognize adb. After I'm in fastboot I can access flash a new boot image/flash malez (only accessible once)

[Guest Chewy11]

did you try malez .exe easy instalation file?

do you have your drivers installed?

[Guest Harness]

did you try malez .exe easy instalation file?

do you have your drivers installed?

Requires adb; on linux for proper dev. anyhow.

I've used adb before on linux as well so I know it works right.

[Guest Delnar_Ersike]

Doesn't [Power On + Volume Up + Camera] boot into the bootloader, the same way the same combination with Volume Down instead of Up boots into recovery?

[Guest Harness]

Tried. Didn't work.

[Guest Harness]

I'm compiling the boot fine, no errors and whatnot (Oh, and I managed to fix my issue a little bit), but.

liquidmkbootimg --cmdline 'panic=10 no_console_suspend=1 console=null' --kernel $path_to_kernel.gz --ramdisk $path_to_newramdisk.cpio.gz -o $path_to_newboot.img

I'm using that to compile. Am I using the right command? Or has this been changed?

[Guest Borkata]

If you have troubles booting try:

liquidmkbootimg --cmdline 'panic=10 no_console_suspend=1 console=null' --kernel $path_to_kernel.gz --ramdisk $path_to_newramdisk.cpio.gz --deploy=0 -o $path_to_newboot.img

or

liquidmkbootimg --cmdline 'panic=10 no_console_suspend=1 console=null' --kernel $path_to_kernel.gz --ramdisk $path_to_newramdisk.cpio.gz --deploy=1 -o $path_to_newboot.img

Edited November 25, 2010 by Borkata

[Guest Harness]

If you have troubles booting try:

liquidmkbootimg --cmdline 'panic=10 no_console_suspend=1 console=null' --kernel $path_to_kernel.gz --ramdisk $path_to_newramdisk.cpio.gz --deploy=0 -o $path_to_newboot.img

or

liquidmkbootimg --cmdline 'panic=10 no_console_suspend=1 console=null' --kernel $path_to_kernel.gz --ramdisk $path_to_newramdisk.cpio.gz --deploy=1 -o $path_to_newboot.img

The second one there wound up working. I forgot about trying deploys...

Thanks!

Harness.