Guest fxjade Posted October 24, 2009 Report Posted October 24, 2009 Ok.. I have now compiled android 1.6 from source (android git), the kernel HTC released this week (copied the .config from my phone, which was running a hacked 1.6 from a dream device) but! I have been trying to merge these things together so I can run vanilla 1.6 android with my own compiled kernel without any success. Tried This but it didn't work out very well (new 1.6 generates its own ramdisk.img... tried running mkbootimg with that ramdisk image... no luck). What I've done so far is build 1.6 android from git, the HTC kernel without any mods and merge the kernel with the ramdisk.img to create a boot.img file. Then used flash_image to write boot.img and system.img I *know* you guys have to know how to do this (Paul, you cook your roms so you have to know how to patch up a vanilla android build). Anyone willing to lend me a hand?
Guest JimBob Posted October 25, 2009 Report Posted October 25, 2009 What arguments did you pass into mkbootimg?
Guest Paul Posted October 25, 2009 Report Posted October 25, 2009 fxjade, are you passing the new base address for the Hero into mkbootimg? What is happening (or not happening) exactly? P
Guest fxjade Posted October 25, 2009 Report Posted October 25, 2009 (edited) fxjade, are you passing the new base address for the Hero into mkbootimg? What is happening (or not happening) exactly? P mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel zImage --ramdisk ramdisk.img -o aBoot.img I read recently from Lox's git rep that magic needed this base address... is it the same for the Hero? Lost the page now and can't find it back... the offset would be nice to know again if needed (so it seems) Currently.... phone boots up to the HTC logo (not the animated one) and stops there. No ADB and I don't have any kind of serial conn. Is it ok to use the ramdisk.img created from compiling vanilla 1.6 android? PS: is there anywhere where I can read documentation on how to create those wonderful, signed update.zip files? :D Can't seem to find anywhere where ALL parts are explained (maybe we could patch up a sticky for all who want to try vanilla 1.6 and play with their kernels?) Edited October 25, 2009 by fxjade
Guest JimBob Posted October 26, 2009 Report Posted October 26, 2009 try passing "--base 0x19200000" to mkbootimg.
Guest kendon Posted October 26, 2009 Report Posted October 26, 2009 PS: is there anywhere where I can read documentation on how to create those wonderful, signed update.zip files? :D Can't seem to find anywhere where ALL parts are explained (maybe we could patch up a sticky for all who want to try vanilla 1.6 and play with their kernels?) http://forum.xda-developers.com/showthread.php?t=551711
Guest ArminC Posted October 26, 2009 Report Posted October 26, 2009 fxjade, I have compiled the kernel and used the boot.img from modaco to create a new boot.img I do succeed with that but then when i try to do fastboot I get: writing 'boot'... INFOsignature checking... FAILED (remote: signature verify fail) I will try to make and update.zip to update the boot only orwill try to use flash_image, I hope i can at least get my own kernel to work with modaco 2.7 version. If that works out I am going to try to do what you are doing and that is create an 1.6 android and merg it with my own kernel. Can you point me out how you managed to get 1.6 to work on your Hero?
Guest fxjade Posted October 26, 2009 Report Posted October 26, 2009 fxjade, I have compiled the kernel and used the boot.img from modaco to create a new boot.img I do succeed with that but then when i try to do fastboot I get: writing 'boot'... INFOsignature checking... FAILED (remote: signature verify fail) I will try to make and update.zip to update the boot only orwill try to use flash_image, I hope i can at least get my own kernel to work with modaco 2.7 version. If that works out I am going to try to do what you are doing and that is create an 1.6 android and merg it with my own kernel. Can you point me out how you managed to get 1.6 to work on your Hero? Well... that prevoius post points out how to sign you updates... *but* you can go ahead and flash your images if your are on a rooted rom (that's what i'm doing right now... I neeeded the info on creating signed update.zip's to make this easier for everyone to install once it works). Check out how to root your current android build and go ahead and flash whatever you want (but please, backup with nandroid or something first :D
Guest fxjade Posted October 26, 2009 Report Posted October 26, 2009 BTW, can I get boot output on screen ala normal linux builds? Or is that only available via serial conn.?
Guest ArminC Posted October 26, 2009 Report Posted October 26, 2009 I have managed to flash my own kernel on Hero using flash_image. I am a happy guy now haha. The next step is compile android 1.6 for Hero and make that work with my kernel.
Guest fxjade Posted October 26, 2009 Report Posted October 26, 2009 I have managed to flash my own kernel on Hero using flash_image. I am a happy guy now haha. The next step is compile android 1.6 for Hero and make that work with my kernel. Got it booting with the offset... sort of... it boots... but gets stuck at HTC logo... difference is now i can adb to my phone. Here's a copy of 'ps' PID USER VSZ STAT COMMAND 1 0 288 S /init 2 0 0 SW< [kthreadd] 3 0 0 SW< [ksoftirqd/0] 4 0 0 SW< [watchdog/0] 5 0 0 SW< [events/0] 6 0 0 SW< [khelper] 7 0 0 SW< [suspend] 8 0 0 SW< [early_suspend] 9 0 0 SW< [kblockd/0] 10 0 0 SW< [kmmcd] 11 0 0 SW< [btaddconn] 12 0 0 SW< [btdelconn] 13 0 0 SW< [kondemand/0] 14 0 0 SW< [qmi] 15 0 0 DW< [rpcrouter] 16 0 0 SW< [detection/0] 17 0 0 SW< [krpcserversd] 18 0 0 SW [pdflush] 19 0 0 SW [pdflush] 20 0 0 SW< [kswapd0] 21 0 0 SW< [aio/0] 22 0 0 SW< [panel_on/0] 23 0 0 SW< [cabc_work_q] 24 0 0 SW< [mtdblockd] 25 0 0 SW< [kadspd] 26 0 0 SW< [uSB mass_storag] 27 0 0 SW< [synaptics_wq] 29 0 0 SW< [kstriped] 30 0 0 SW< [krfcommd] 33 0 0 SW< [mmcqd] 34 1000 808 S /system/bin/servicemanager 35 0 852 S /system/bin/vold 36 0 668 S /system/bin/debuggerd 37 1001 11068 S /system/bin/rild 39 1013 21264 S /system/bin/mediaserver 40 1002 1168 S /system/bin/dbus-daemon --system --nofork 41 0 800 S /system/bin/installd 42 0 4396 S /sbin/adbd 62 0 0 DW< [snd_rpc] 229 9999 57296 R zygote /bin/app_process -Xzygote /system/bin --zygote 231 0 740 S /system/bin/sh - 232 0 2072 R ps
Guest fxjade Posted October 26, 2009 Report Posted October 26, 2009 (edited) Ok... offset seems to be working ok, since it actually boots the kernel (though everything stops there on 1.6) I've got my Kernel running on MCR 2.8 (using same ramdisk, overwriting with my own kernel) and the phone works just fine... my guess is that I messed up something with the 1.6 initrd... Edit: Errr, am I ok with this procedure: ? Build 1.6 from git / repo flash system.img to the phone create a boot.img from the 1.6 generated ramdisk.img + my kernel -> flash it to phone reboot. Is there anything else I need to flash / copy ? Edited October 26, 2009 by fxjade
Guest JimBob Posted October 26, 2009 Report Posted October 26, 2009 Is there anything else I need to flash / copy ? - What version of the kernel have you compiled? I think Donut only supports kernel 2.6.29. You would need to identify the diff between hero kernel and 2.6.27 then apply those diffs onto Donut kernel (not a trivial task). Then build that kernel. - Also, remember that the kernel is only one part of the puzzle, HTC have not given us the source for their proprietary binaries. You will probably need these for android to work. Take a look at some of the work Lox_Dev is doing @ http://github.com/loxK/platform_vendor_htc_hero, hes on the right track.
Guest fxjade Posted October 27, 2009 Report Posted October 27, 2009 - What version of the kernel have you compiled? I think Donut only supports kernel 2.6.29. You would need to identify the diff between hero kernel and 2.6.27 then apply those diffs onto Donut kernel (not a trivial task). Then build that kernel. - Also, remember that the kernel is only one part of the puzzle, HTC have not given us the source for their proprietary binaries. You will probably need these for android to work. Take a look at some of the work Lox_Dev is doing @ http://github.com/loxK/platform_vendor_htc_hero, hes on the right track. Had a look before, still looking at Lox's work :D 've been all night working looking on that 2.6.27 - 2.6.29 diff, hehe.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now