Stayboogy it is quite clear you are dead-set on hating every chance at making CM 7 work. but your opinion i do not share. CM 7 has features that i haven't been able to implement without adding apps which take up valuable space and RAM in doing so. you have made it clear over and over again that you don't care. but i do. and i'm not giving up. i would like to TRY making it work. i know from my past logcats that the phone kernel panics because the kernel from a ZTE Blade ROM are not compatible. so i was thinking of trying to see what making a Merit/Avail Kernel over top of a KANG ROM or RC would do. i heard someone somewhere mention they got a French Avail to run CM but not sure the details (i neverk knew open source had classfied stuff but..) but i'm not giving up. if the Merit will never have a CM 7 ROM i will just replace the phone. it's my favorite companion to GB ROMs and i refuse to use a device without it. i'm still holding out hope it will be available some time....but i'm only giving it months before i just reactivate my old Optimus V and live with the horrid signal from Sprint
I am not *Nix expert but i do know Android is Android...the only thing that is changed is the kernel--the drivers, boot images, for parts of the phone/tablet. Android runs on top of a kernel much like Linux Window Managers and X run on top of the kernel. the kernel so far is what is bootlooping. it panics because the drivers are not compatible. so whether CM 7 would boot or not is not going to be an issue if i can't even get it to attempt to start. which is why i plan on trying a working Merit boot.img and custom kernel that does boot. sure, i may get looping at the CM 7 logo but it would still be progress.
Stayboogy, i can see you and i will disagree with this but since you're not the only dev, and since Android is a community effort with respect to ROMs and other things, i would greatly appreciate it if you would not hijack every thread i make regarding any progress or chance at CM 7 to show your opinion. the first time was enough.
it's not opinion, it's fact. what you're wanting to do is not how it's done. why can't you understand that???
i think it would be cool if you got it working, it's just that it's not going to work the way you are going about it.
even if you did get it to boot, and even if it seems "functional" to you, it won't be. it requires specific files from our phones to work, many of which do not exist. i'm just trying to tell you that you're not going to be able to do by using CM7 from another phone and swapping boot.img files. it doesn't work like that.
if you want CM7, you will need a dev environment, cyanogenmod repo, and the sdk built. then you will need to pull five dozen files from your phone, then you will need to edit about 10 .mk files in the sdk, then you will need to build and fix the several errors of missing dependencies when you build, then you will need to edit the build because it won't work, and then it still might not work.
i've already done all this. i'm not telling you what i think, i'm telling you WHAT I KNOW
i'm not trying necessarily to discourage you, but i am telling you that your presuppositions about how it works and how it's built and ported are nowhere near correct. i've been trying to tell you this over and over but you assume that you're correct and you're not. that's all there is to it.
i'd like to see someone get it working, but it's not going to happen by doing a little two minute swap of a file and rewriting an updater-script. it doesn't work like that.
and i'm not hijacking your thread, and actually telling you how it works, which apparently you don't care, which means you won't make any progress.