[Kernel] Hydra-kernel **UPDATE 8/20**
- Thread starter opcode1300
- Start date
It 'should'..
I did get into adb/recovery and loaded the new recovery. it looks like it flashed. but on reboot...
so I am guessing my update script failed.
I did get into adb/recovery and loaded the new recovery. it looks like it flashed. but on reboot...
Code:
ro.secure=1so I am guessing my update script failed.
script
*edit*
looks like the update script is the issue. (p.s I miss fastboot
)
Code:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/inc/inc/inc:2.1-update1/ERE27/161493:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/inc/inc/inc:2.1-update1/ERE27/161494:user/release-keys");
assert(getprop("ro.product.device") == "inc" ||
getprop("ro.build.product") == "inc");
set_progress(1.000000);
ui_print("Writing boot image...");
write_firmware_image("PACKAGE:boot.img", "boot");
set_progress(1.000000);*edit*
looks like the update script is the issue. (p.s I miss fastboot
)
Code:
// write_firmware_image(file, partition)
//
// partition is "radio" or "hboot"
// file is not used until after updater exits
//
Last edited:
Try this in recovery:
Then, open a shell to your phone via 'adb shell', get root, and do the following two commands to flash your new boot image:
Code:
adb push ./boot.img /sdcard
Code:
# cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/boot.imgYes, sorry. I took that for granted. Here is the revised instructions. I attached flash_image.
Try this in recovery:
Then, open a shell to your phone via 'adb shell', get root, and do the following two commands to flash your new boot image:
Try this in recovery:
Code:
adb push ./boot.img /sdcard
adb push ./flash_image /sdcard
Code:
adb shell
$ su
# /system/bin/cat /sdcard/flash_image > /system/bin/flash_image
# /system/bin/chmod 755 /system/bin/flash_image
# /system/bin/cat /dev/mtd/mtd2 > /sdcard/mtd2.img
# /system/bin/cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# /system/bin/flash_image boot /sdcard/boot.img
Last edited:
that didnt work.. resetting...... try again tomorrow
the kernels good. just getting it installed...
the kernels good. just getting it installed...
So I know this doesn't have much to do with this kernel buuuut for some reason last night in SetCPU the only thing I could adjust was idle speeds updated SetCPU and have access too the full bit? Max says 998400 min 24500... hmmm? Any ideas?
How do you know if the kernel is good if you cannot flash it? I compiled a kernel as well and got it installed but it stuck my phone at the HTC logo...
I used the same build setup i've used for the mytouch. and got no errors building it
I have never done this before but is it possible to just copy the kernel on our phone, unpack it, edit the default.prop and repack it? I don't have Linux or I would try it myself. Check out this wiki. It explains how to do it. It seems easy enough for someone who knows how to compile a kernel.
http://android-dls.com/wiki/index.p...s#Flashing_your_new_image_back_onto_the_phone
http://android-dls.com/wiki/index.p...s#Flashing_your_new_image_back_onto_the_phone
this is the process i used to unpack the ramdisk and edit the default.prop and repack the ramdisk and the new kernel
Similar threads
- Locked
