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

[jimsmith80]

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.
****************

 

[rbheromax]

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"

 

[tgamble160]

i see the op is changed to 1.8. is that for a fix or did you start on something new all together?

 

[rbheromax]

I lowered the clock speed
maybe this will get it booting
but can you test this?:
https://www.dropbox.com/s/y9f2434gze39nmd/OC.zip

 

[tgamble160]

Yeah let me make a quick backup

 

[rbheromax]

okay

 

[tgamble160]

Stuck at green android

 

[rbheromax]

did the image change at all?

 

[tgamble160]

No

 

[rbheromax]

ugh...these kernels just dont wanna flash

 

[altaran]

Would it be possible just to removethe oc and recompile with stock speeds just to see if it will install and boot?

 

[rbheromax]

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.

 

[jimsmith80]

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.

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

 

[rbheromax]

Its the logo.bmp in ramdisk. I replaced it. There is a partition titled SPLASH but idk how relevant that is.

 

[andrew.johnson]

Probably won't be able to test much for a little while. No internet connection.

 

[AMOCO]

Probably won't be able to test much for a little while. No internet connection.

I been using my 3g and terminal emulator.

Sent from my N9100

 

[rbheromax]

Smart, I just need to figure out what's going on with this kernel thing.

 

[andrew.johnson]

My phone's off too so I have to be on wifi

 

[jimsmith80]

Smart, I just need to figure out what's going on with this kernel thing.

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

 

[rbheromax]

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.

 

[bcrichster]

Try this - ota keep root
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
Worked for warp sequent when ota JB hit

And this: CWM flashable superuser.apk - credits to chevanlol360
http://androidforums.com/showthread.php?p=5953990

 

[rbheromax]

Were gonna need it. Can someone test the module method in the OP? Just don't delete the /etc/thermald.conf just rename it.

 

[jimsmith80]

Are you building the zimage from 100% avid source and combining it with the ramdisk from the force?

 

[rbheromax]

Yeah, following procedure and everything

 

[junkie2100]

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