Jump to content

ZTE BLADE series-Froyo kernel(2.6.32) source code


Recommended Posts

Guest Sebastian404
Posted
Seb, I can actually see some trying this. :unsure:

you dont think it would work then?

Guest minz007
Posted
if you rename them to be boot.img, reovery.img, and then put the rest into a zip file and rename that to system.img you should be able to use clockwork mode restore...

Im getting a quadrant score of 9,000!!

*facts in this post may not be accurate

LOL :unsure:

Guest PeaNut_HU
Posted

Cool.

I just put enableultrafastcpu=1 in build.prop and now i have a 1GHz snapdragon core activated in my blade! :angry: B) :unsure:

Guest rbbrslmn
Posted
you dont think it would work then?

I didnt realise you were joking and have just absolutely wrecked my phone.

really unhappy at the moment. looking for the receipt in the hope that orange will take it back

Guest PeaNut_HU
Posted
I didnt realise you were joking and have just absolutely wrecked my phone.

really unhappy at the moment. looking for the receipt in the hope that orange will take it back

Well you have to be a real idiot if you did it after reading all posts. :unsure:

Guest rbbrslmn
Posted
Well you have to be a real idiot if you did it after reading all posts. :unsure:

bit harsh kicking me like that while i'm down.

Guest isambard
Posted

kernel downloaded. time to set up a cross-compile build environment...

Guest Simon O
Posted
kernel downloaded. time to set up a cross-compile build environment...

Doing that myself now. Taking a while but then I am pulling the 2.2.1 AOSP source in as well :unsure:

Guest dmxpowa
Posted
bit harsh kicking me like that while i'm down.

get into fastboot, reflash recovery, then install any rom. phone recovered. gl chap.

Guest Simon O
Posted
Here's just the zImage for anyone who wants to build their own boot.img.

What command line do you use to build the image? Whenever I try it ends up unbootable.

Guest PeaNut_HU
Posted
get into fastboot, reflash recovery, then install any rom. phone recovered. gl chap.

Trying a Total Phone Transfer ROM might be the easiest to recover...

Guest rayraven
Posted
Doing that myself now. Taking a while but then I am pulling the 2.2.1 AOSP source in as well :unsure:

Sweet! finally, chance to say goodbye to all that stagefright nonsense.

Thanks a lot kallt_kaffe as well!

Guest asturel
Posted

any1 can build a cifs module?

i tried but i got:

ERROR: "slow_work_enqueue" [fs/cifs/cifs.ko] undefined!

ERROR: "slow_work_register_user" [fs/cifs/cifs.ko] undefined!

:unsure:

Guest bugmenot
Posted (edited)

New kernel (kallt_kaffe) booting great here.

And 5 mpix camera is finally working!

Edited by bugmenot
Guest sorrowuk
Posted

Can someone compile this kernel and then build a complete generic froyo for our blades , just 100% original froyo with everything working :unsure:

No crazy patches or mods etc. Then hopefully everything should be stable and no freezes B)

Also if someone makes a cyanogenmod :angry: wooo

Guest sorrowuk
Posted
New kernel booting great here.

And 5 mpix camera is finally working!

Can you get the zte blade with a 5 mpix camera anywhere in the UK ?

Guest rbbrslmn
Posted
Trying a Total Phone Transfer ROM might be the easiest to recover...

cheers guys but I was joking.

Guest rbbrslmn
Posted
Can you get the zte blade with a 5 mpix camera anywhere in the UK ?

you could import one. honestly doubt it would be worth it, the camera isnt bad because its only 3.2mpix (the k800i had a 3.2 which blows most other phone cameras away) its bad cos its cheap and nasty. the 5MP will probably be just as bad.

Guest sorrowuk
Posted (edited)

Also will stagefright work perfect now with it all enabled ?

And do you think zte will release another source for the ZTE Blade chinese froyo kernel, will it be any different ? better ?

And do we have to change anything with this , like RIL librarys etc, or can the phone part etc all work unmodified now on froyo ?

Edited by sorrowuk
Guest Simon O
Posted
any1 can build a cifs module?

i tried but i got:

ERROR: "slow_work_enqueue" [fs/cifs/cifs.ko] undefined!

ERROR: "slow_work_register_user" [fs/cifs/cifs.ko] undefined!

:unsure:

add slow_work to the kernel. Build cifs as modules as they are large.

Guest Simon O
Posted

I'm going to sound like such an idiot here but building the boot.img, is this right:

mkbootimg --kernel ./zImage --ramdisk ./ramdisk.cpio.gz -o ./newBoot.img

I can't find out if the blade needs a command line set or not?

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.