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

Root [Boost Mobile] kernel source code won't build

aenoch said:
have u guys tryied the ZTE N850 Series - Gingerbread kernel(2.6.35) source code
Click to expand...



I have actually made a kernel with that source, plus some files I had to change and MOD

I am trying to work around the security issues

8069114.png
 
does anyone who has the older boot loaders

that do not have the the screen wake up issues

want to test a kernel for me ?
 
hroark13 said:
does anyone who has the older boot loaders

that do not have the the screen wake up issues

want to test a kernel for me ?
Click to expand...


this is a test kernel for stock rom

it is installed in CWM

BACK UP IN CWM before you install it, because later you will need to do an advanced restore and restore boot

a lot of things probably will not work because the magic strings will not match, like the wifi modules and stuff

I am just curious if this will boot on phones with the older boot loaders

the zImage does boot my CM7, but then I have screen wake issues

test-kernel-2-6-35-11.zip

edit : see next post, i will leave this file here for anyone who wants to test it, but it does not work
 
hroark13 said:
this is a test kernel for stock rom

it is installed in CWM

BACK UP IN CWM before you install it, because later you will need to do an advanced restore and restore boot

a lot of things probably will not work because the magic strings will not match, like the wifi modules and stuff

I am just curious if this will boot on phones with the older boot loaders

the zImage does boot my CM7, but then I have screen wake issues

test-kernel-2-6-35-11.zip
Click to expand...


OK that kernel is not booting the Stock ROM for me

This one does

it is the same zImage as before, but the ram disk is the one I made for CM7

it does boot the stock rom on my phone, but I still have the screen issues

test-kernel-2-6-35-11-cm7-ramdisk.zip

ZTE is getting on my nerves with all their security crap




.
 
Sebastian404 said:
ZTE had sent me a message on Twitter asking me to follow them so they can send me a DM.... not sure if its going to be any help, or just a way to bump their numbers up..


if you boot your device with a regular kernel and then use and ADB shell look at dmesg, the VERY first line will tell you which version of GCC was used to build it.

the only way I could get the raw source to build was to use the tool chain that came with android-ndk-r5c, (ie 4.4.0).
Click to expand...


CROSS_COMPILE ?= /home/hroark13/arm-eabi-4.4.3/bin/arm-eabi-
 
hroark13 said:
OK that kernel is not booting the Stock ROM for me

This one does

it is the same zImage as before, but the ram disk is the one I made for CM7

it does boot the stock rom on my phone, but I still have the screen issues

test-kernel-2-6-35-11-cm7-ramdisk.zip

ZTE is getting on my nerves with all their security crap




.
Click to expand...
i flashed this little lag and i tried to log in to android forums using phone ,it keep setting me back to my phone home screen i guess you would say,going to use t.b. and see what happens as i will use it a little while
 
moses166 said:
I've tried the kernel and I don't have any problems with it. Is this the kernel made with the zte fury source?
Click to expand...


your wifi probably does not work

and other things are probably buggy

it was made with the fury source, but I have modified some of the files to get it to compile


I will upload the source, in a bit, and post a link
 
mholloway said:
i flashed this little lag and i tried to log in to android forums using phone ,it keep setting me back to my phone home screen i guess you would say,going to use t.b. and see what happens as i will use it a little while
Click to expand...
everything is force closing
 
Rally 517 said:
yup im getting wifi error. still testing
Click to expand...


probably have to copy the new modules to the system/lib/modules folder

and there might be some wrong settings in the init.rc files


like i said this stuff is not usable

this is for testing and development only

i am still uploading the source, should be done soon
 
This is not finalized source code, this is for testing, and trying to make good working source code

for advanced users only



un-tar the file to your home folder


edit the /home/user/sean/Makefile to point to the location of your arm-eabi-4.4.3 folder

like this
Code: 
ARCH        ?= arm
CROSS_COMPILE    ?= /home/hroark13/arm-eabi-4.4.3/bin/arm-eabi-
open terminal

cd sean
make mrproper
cp config2 .config
make ARCH=arm

after a while you should get a zImage in arch/arm/boot

you will need to pack that zImage with a ramdisk


see my packer thread

http://androidforums.com/warp-all-things-root/520947-warp-kernel-packer.html

I am attaching the sean source code I modified

and the ramdisk I am currently using to try to get CM7 working

kernel source
http://www.mediafire.com/?wwm0w01sd7w0l2m
ramdisk
cm7a_ramdisk.tar.gz



edit:

removed source

see this thread

http://androidforums.com/warp-all-things-root/535629-hroarks-warp-kernel-source-2-6-35-11-a.html
 
Stephen184 said:
Ive tried multiple times, but I have no background in Linux so I have no clue where the issues could be. I've written a lot of programs in visual basic, but that's pretty much the easiest programming language ever
meimiao1.jpg
jh88.jpg
test.jpg
dh.jpg
pad.jpg
Click to expand...


tried multiple times at what ?
 
at this point I am not too sure if I should keep working with the sean (Fury) source which is 2.6.35.11

or work with the arthur (Warp) source which is 2.6.35.7


there are a a lot of differences between the sean and arthur sources because they are different versions


the arthur (Warp) and V9PLUS kernel sources are basically identical

the V9Plus has a few more files, but 99.98 % percent of the files in those two sources are identical
 
i have noticed if I open Gallery

the phone will freeze after a while, and you have to do a bettery pull


and then it does not boot

so you you have to do a factory wipe in CWM

and then pull the battery out

and hold the power button for 20 seconds while the battery is out and it is unplugged from power source

and then it boots again


I think something is getting flagged, some type of security type stuff
 
aenoch said:
did i help with something?
Click to expand...


I do not know


I have downloaded source code for about 10 different ZTE phones and 5 other phones that have a similar CPU and been comparing them

I have downloaded the n850 source before you posted


I have been working very hard on this and spending a lot of time on it


the fact is we can use the Fury source, we can also you the V9 Plus source, or the Skate Plus source (if it is available)
 
thanks for all your hard work this is my first android phone and would love to see more mod i love mods on games systems toys so making this more modable would be a great first exsperence on the buillten the n850 source was on there were many older zte sources but that was the newest
 
i think I may have figured out why the new phones have screen issues with the older zImages

hopefully this is something we can fix in the kernel source

it seems they may have change panels or something, I see this in the EMMCBOOT.MBN (/dev/block/mmcblk0p11)

when I compare between B08 and B08C

8069374.jpg
 
aenoch said:
whats the difference in the new/old phones how do you know what you have

not sure what phone this is but it came out on the 9th of this month Service Bulletins Detail

did u update your android version that menu looks different then mine and my version is .5 urs is .7
Click to expand...


I was running CyanogenMod when I took that Screen Shot

CyanogenMod is 2.3.7

The stock ROM is 2.3.5

and the icons, menus and stuff will look different
 
hroark13 said:
i think I may have figured out why the new phones have screen issues with the older zImages

hopefully this is something we can fix in the kernel source

it seems they may have change panels or something, I see this in the EMMCBOOT.MBN (/dev/block/mmcblk0p11)

when I compare between B08 and B08C
Click to expand...


looks like we will need to modify the

sean/drivers/video/msm/lcdc_panel_wvga_arthur.c


to fix the screen issue on the newer phones

this is what I am going to work on




Is anyone else messing with this stuff ?

Because I do need help
 
You must log in or register to reply here.
Back
Top Bottom