• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Development progress on Cyanogenmod7/9/10 Updated: 5/10

There is no security in the boot.img. The only issue I've seen is fiddling to get the addresses to in the boot image header to match up with what the stock image has. Each version of cyanogenmod needs it set in a different way. With enough trial and error, it is possible to have a boot.img built with the correct addresses in cm 7, 9, 10, and 10.1.
 
giantpune said:
There is no security in the boot.img. The only issue I've seen is fiddling to get the addresses to in the boot image header to match up with what the stock image has. Each version of cyanogenmod needs it set in a different way. With enough trial and error, it is possible to have a boot.img built with the correct addresses in cm 7, 9, 10, and 10.1.
Click to expand...

I'm pretty sure jet found out that if the boot.img doesn't match the exact size it won't boot.
 
Well then we just need to figure out a way to make it work.
What we have done, used mkbootimg with a stock ramdisk, failed.
abootimg into a stock boot.img worked fine.
Are you talking about the base address?
 
What exactly do we need to do, i backported KGSL, Genlock for JB.. Built the kernel. We also fixed the source. We tried packing with stock ramdisk.. bootloop. then we use abootimg to swap out the zimage...same deal. we need to replace the ramdisk with a cm10 ramdisk.. how are you do this?
 
If you set the values in your boardconfig.mk right, you can type "make bootimage" or "make recoveryimage" and you can make it work. The only images I've gotten to boot have the same base address, ramdisk address, and atags address as our stock images. It seems that if you get the base and ramdisk addresses right, the atags will be right without having to adjust it.
 
Have you devs usually noticed that it's almost always harder to port CM and other custom Roms to cheaper low end phones? Or is that not the case? Are they just coded badly or what?
 
DsyMnapTic said:
Have you devs usually noticed that it's almost always harder to port CM and other custom Roms to cheaper low end phones? Or is that not the case? Are they just coded badly or what?
Click to expand...

Not really. More experienced devs tend to go toward higher end devices.
 
sellers86 said:
Not really. More experienced devs tend to go toward higher end devices.
Click to expand...

Yep... Imagine how much support the gs3... One of the best sellers of the year has... Everyone and their mother bought it... Where as the elite and other prepaid phones barely have a root community... It was just as much a pain in the ass for them to get cm for the gs3... But because there are probably more devs with way more experience... Piece of cake... But on the other hand the elite has two teens... A couple of average joes... And a few others I don't know about for dev support... Do you see why this phone doesn't have much? Lol?
 
jetx2x said:
Yep... Imagine how much support the gs3... One of the best sellers of the year has... Everyone and their mother bought it... Where as the elite and other prepaid phones barely have a root community... It was just as much a pain in the ass for them to get cm for the gs3... But because there are probably more devs with way more experience... Piece of cake... But on the other hand the elite has two teens... A couple of average joes... And a few others I don't know about for dev support... Do you see why this phone doesn't have much? Lol?
Click to expand...

Yes, thank you for the extraordinarily blatant explanation :rolleyes:
 
You must log in or register to reply here.
Back
Top Bottom