Hi,
I have downloaded kernel sources from HTC for wildfire and compiled zImage. using unpack and repack scripts I successfully installed the boot.img via update.zip. Now I see the device reboots fine, but I cannot unlock the screen, and none of the keys are functional.
I have no Idea what is still missing or have I done something wrong?? your help is need here.
Indeed I tried to compile jacobs kernel image from github but no luck.
Regards
bram
Related
Hai ,
I downloaded my phones kernel source and compiled with some additional configuraton..
Now I got these files .vmlinuz,image,zimage,and a tar'ed archive of zimage with name kernel_......_.tar
how can I make odin flashable (or any how flashable) rom file from this?
I tried to make boot.img with mkbootimg and initrd extracted from original stock rom
Flashing was succes according to odin But It doesnt boot.
any one please help me
I also like to know is there any way turn off splash screen and see the debug msgs from kernel during boot?
Any one please help
My phone is galaxy young GT-S5360
Update:
I figured out that problem is not with the additional configuration options I given during kernel compilation.
Problem is with the tools (or incorrect usage of tools) .
I tried making boot.img with original kernel and initramfs and that also not worked (flashing was successful.but
Booting failed).
I don't have much experience in android.i only know some linux
Any one please help me
Please please please.......
Update:
Finally I think I found how to make boot.img from kernel(zImage).The problem was with the "--base-address" option in the mkbootimg toool. I found my device's base address from kernel configuration file (.config).
now , boot.img produced from the kernel which was extracted from stock rom works well.
but boot.img produced from my custom kernel boots,but nothing displys in the screen.
I dont know how to debug it . I cant even see the debug messages from the kernel
Any one knows any clues,hints or any thing regarding this please please help me
i dont know why any no one replay to my post.
I dont have privilege to post this question in developers thread.thats why i am asking it here
Is it a wrong way? I dont know.
Click to expand...
Click to collapse
Thank you sir to be the first succefully create custom kernel...
Far before anyone can create it...
I'm always waiting ur great work again into sgy device...
nfinitefx45 did this build by my request. but after flashing with his rom my kf stucked at kf boot logo. i solved this cause by replacing original boot.img by boot.img from stock rooted for dualboot. now my kf work perfectly. hope it`ll be useful for someone.
remember that this is only update. at first you need to install stock for dualboot. you can find it in android development thread in fff ex. bootloader section
this is link for download:
http://www.mediafire.com/?j5kh3y1tqj2gayw
I wanted to thank you for this ROM version. It works as advertised!
Thanks... plee3
updàte
Has anyone tested this rom? What's your feelings?
I only used it for a short time to make sure it was working correctly. But I am currently using Modaco Gr8 on my primary partitions and the stock ROM on the secondary partitions was too limiting (no play store and google apps).
So I tried to modify the Modaco Gr8 to run in the secondary partitions, but it would not boot correctly. Nor could I make any of the CM9/AOKP ROMs run on the secondary partitions. I followed all the listed steps to the init.omap4430.rc and updater-script files, but they would not boot up correctly.
In fact, the only other ROM that would boot correctly was the CM7 ROM that eldarerathis provided in his original thread.
Of course in performing these experiments wiped out the NFX ROM, so I no longer am running the NFX ROM on the secondary partitions.
I hope this helps... plee3
i know. we should make three different boot.img and updater-script files. if you want to covert your primary boot rom to alternate boot rom simply change these files. i expect boot.img and updater-script altboot for cm9
Thanks so much for this. Works great. Also using Modaco Gr8
DukeSilver79 said:
Thanks so much for this. Works great. Also using Modaco Gr8
Click to expand...
Click to collapse
Are you saying that you have Gr8 running in the secondary partitions?
If so, what additional changes did you make to change the Gr8 ROM?
Thanks... plee3
Change updater-script and replace by insecure boot.img from stock for altboot
I downloaded it. I have installed the proprietary drivers. I compiled it. I flashed it.
Black screen and CPU is running hot.
Official 4.2.2 firmware works fine.
Have someone the same problem or a solution?
I compiled the same branch for Galaxy Nexus and it works fine.
I suppose you could start by unpacking a known working standalone boot (e.g. a custom recovery) and replace it's kernel with the prebuilt kernel from the Google git tree. Re-pack it and see if it boots.
If that doesn't work you are either packing it wrong (load address?) or the prebuilt kernel is borked. But at least that lets you discriminate between a bad boot image (kernel) vs. a problem with the ROM?
good luck
I'm trying to compile PAC for Micromax A116
I used these sources :
https://github.com/zeetherocker/android_device_micromax_a116
https://github.com/zeetherocker/android_vendor_micromax_a116
I haven't used a kernel during compilation But the sources are here :
https://github.com/zeetherocker/android_kernel_micromax_a116
The kernel sources are a little different for the mediatek devices... I didn't get the procedure for compiling it so I just removed it and didn't use it for compilation...
The rom compiled without any probs... But then when I flashed it it didn't go beyond the Canvas logo... And I'm not even able to take log... ADB doesn't detect it... I flashed a custom kernel too but no luck still stuck in the same state...
I downloaded cm11 for the device which was ported from a different device for A116... I unzipped it changed a few files from the etc, lib and bin folders.... Then it started showing the bootanimation... But still didn't boot up and still no luck with ADB...
I need help with this... Thanks in advance..!!
I just spent a few days compiling this kernel. Fixed the paths and whatnot for RNDIS, etc. Its compiling fine but upon packing it with AnyKernel2 and flashing, I get a System Destroyed message, where I have to boot a TWRP img via fastboot and restore a working boot.img. I tried a brand new kernel source with no edits as well, same issue. What am I missing?
I did a make for tissot-perf_defconfig first, then I built it with make -j4 (i have 4 threads). Compiles to a Image.gz-dtb, place it in the AnyKernel2 root and zip it and flash. Flashes fine, boot fails before boot anim.
I tried manually packing the kernel into a boot.img i pulled from a TWRP backup (RR), but fastboot complains its missing DTB no matter which kitchen I use (AIK, Carliv Image Kitchen). Maybe this is the issue?
Thanks!
PS: I'm running it on top of RR 8.1 if that affects anything.
Also is there a Telegram I can join for these questions?
edit: tried pulling the config from a stock boot img using extract-ikconfig. still the same issue booting.