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

Root Kernel Kernel[1.8GHz](WIP) Module method also

have you seen this. I am trying to figure out how to fix it right now

*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_RAMDISK_ADDR is 0x01300000
Please modify mkbootimg.c using the above values to build your image.
****************
 
you have to recompile with:
"mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base x80200000 --cmdline 'androidboot.hardware=qcom user_debug=31 loglevel=7 kgsl.mmutype=gpummu' -o new_boot.img"
 
rbheromax said:
Yeah
https://github.com/newkid313/android_kernel_zte_aurora
its commit#: e34a038
that has the stock speeds
Even compiling stock source wont work because I removed the splash screen (green android) but upon reboot its still there. That shows that the recovery isn't even flashing anything. Apparently all that works are the backups and restores.
Click to expand...


The green android was in two places on the warp. In the recovery and in the boot. It looks like one constant image but its not. The same may apply here. Rather than delete the image replace it. That will tell you more
 
Its the logo.bmp in ramdisk. I replaced it. There is a partition titled SPLASH but idk how relevant that is.
 
rbheromax said:
Smart, I just need to figure out what's going on with this kernel thing.
Click to expand...


All I've read pretty much states that hacking up a dump from the boot partition is unlikely to work. We may have to wait for boost to push an ota update. The good and bad part about that is if they do it will likely be jelleybean. That's good because jellybean is awesome, but bad because plot means back to the drawing board for roms and possibly root
 
It may be a while before jb update comes. I should just take my kernel to the avid side and see if theirs will boot it. It was built with their src.
 
Were gonna need it. Can someone test the module method in the OP? Just don't delete the /etc/thermald.conf just rename it.
 
ok im not 100% sure whats up with that kernel repackaging error, i never get it on version 0.218 of dsixda's android kitchen, BUT i may have a lead on the kernels booting issue, much like the sequent the force wont boot past andy without the stock init binary in the kernels ramdisk, its 97kb as apposed to a built 111kb one and unlike the built one is compatible with the zte kernel

edit...
nevermind i checked its the right binary
 
You must log in or register to reply here.
Back
Top Bottom