hitman_dreams
New member
- Nov 29, 2010
- 1
- 0
- 0
so if wifi doesn't work, is there an easy way to fix it instead of building and packaging and installing everything over again?
I had the same Problem 1, use unpack-bootimg.pl - worked for me.I'm having some problems following this for my Huawei U8150 running Froyo.
Problem 1: I'm unable to extract the ramdisk from the boot.img file. It complains about it not being gzipped.
Problem 2: I'm not really sure if I'm using the right wlan.ko file for this. My phone doesn't appear to have one, but it does have a system folder in the ROM that includes a wifi folder and a "ar6000.ko" file. Should I rip that out of my existing ROM?
fastboot -c "mem=211M console=ttyMSM2,115200n8 androidboot.hardware=huawei console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0" -n 4096 -b 0x00208000 boot clean.img-kernel.gz orig_boot.img-ramdisk.cpio.gz
emulator: control console listening on port 5554, ADB on port 5555
emulator: sent '0012host:emulator:5555' to ADB server
emulator: ping program: /home/mahiti/android-sdk-linux_x86/tools/ddms
emulator: ping command: /home/mahiti/android-sdk-linux_x86/tools/ddms ping emulator 10.0
Unknown cp14 read op1:3 crn:5 crm:13 op2:1
qemu: fatal: goldfish_switch_write: Bad offset ffc
R00=ff019000 R01=000005a1 R02=00000100 R03=00000000
R04=fd9633d0 R05=00000000 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=00000000 R11=00000000
R12=00000000 R13=00000000 R14=00810020 R15=00010000
PSR=000001db ---- A und32
Aborted
adb reboot bootloader
fastboot boot /path/to/boot.img
I have an HTC Evo View 4G, and I'm interested in compiling my own custom kernel for it.
I have compiled AOSP ROM's and CM9 before, but now I want to try custom kernels because it seems to be the next level. I downloaded HTC's kernel source for the View, but what I'm really interested in is customizing it. I'm curious about updating it to a more recent version of the Linux kernel, is that possible? If not, what are some general optimizations that I could work on?
After pulling the config file from the device, what would happen if I dropped it into the generic Android kernel source from their GitHub? Would it make a functional kernel? Say I wanted to make a kernel based on Android-3.3, or a different branch of the source, how would that work?
And also, this thread is from almost 2 years ago, and was for the HTC Hero. What has changed since then? What do I need to know now that could help me understand all of this better?