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

Ya I've used both, with the config from the phone, but, still won't boot, I've tried putting the zImage into a cm7 build, renamed it kernel. I thought maybe I wasn't packing the boot img correctly. Still no go, the source isn't correct

how do you root the zte warp?

Go to this thread http://androidforums.com/showthread.php?t=509853

Sent from my N860 using Tapatalk 2 Beta-5

shinru2004 said:

Sebastian emailed his internal source at zte, we might get a working source...... i hope, but hes had pretty good luck with them so far

Click to expand...

did he pm u that info or somethin

Hi All

I can get the kernel source code to build, and I can also get the zImage that I have compiled to boot to an adb prompt, but I cannot get it to boot Android, and I am experiencing some weird security stuff when trying to run some commands in adb

Let me first explain how I build my zImage
After I have downloaded and unzipped (twice) and un-tarred the files (jeeze)
I edit the Makefile and change this section

From

To


I copy the config file from the phone into the kernel directory




Then I build the zImage



After about 15 minutes I get a zImage in /home/hroark13/kernel/arch/arm/boot

I pack this zImage with a ramdisk that I have made, which is a modified version of my CM7 ramdisk

I use my packer for this

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



The mods that I made that are getting me into adb are in the "on init" section of the init.arthur.rc

and i also copied a lot of files from CWM sbin, CM7 bin and CM7 xbin into the sbin folder


and it boots into adb, but will not boot Android


It does not want to mount the partitions

I have tried making scripts and and stuff to get the partitions to mount from the init.arthur.rc, but it will not work


however once I get into adb I can run a mount command and mount the partitions

I also get permission erors trying to run some commands

I am not a kernel or Linux expert, so maybe some of this info will shed some light on what is happening

Maybe we can put some diagnostic binaries in the ramdisk and figure out what the heck is wrong with the zImage that gets compiled


Here is the file i produced, it is flashed with CWM, you guys / gals can un-pack the ramdisk and try to produce your own zImages to see if you get the same results


make sure you backup before you flash it


zImage_test.zip




,

QuietStorm1785 said:

Im still trying to figure out why the kernel isnt booting, I got about as far as you did hroark. Wouldnt mount partitions, was able to start adb.. etc etc. mind racking crap here..

Click to expand...

yeah, it is weird

but at least it is booting into adb, so we are making some progress,

and maybe we can get some Linux kernel gurus to run some commands and figure some stuff out

I was wondering is it possible to unpack the boot.img of the phone and tweak the ramdisk and zimage and repack it into the boot.img?

moses166 said:

I was wondering is it possible to unpack the boot.img of the phone and tweak the ramdisk and zimage and repack it into the boot.img?

Click to expand...

you can tweak the ramdisk

for now we are stuck using the stock zImage

OK


so I have made some more progress


I am now able to have my compiled zImage boot my CM7 (i have not tried stock yet)

The problems is, that after about 20 seconds the phone shuts down, it did this before, but now it is just boot looping on the boot animation

this is definitely farther then we have been getting, and I think we will eventually hone in on the issue


What I have done to get this to work is modify the board-zte-arthur.c

I compared it to the board-zte-v9plus.c found in the V9 Plus source code

and changed a lot of the settings to match the V9 Plus file

The Warp and V9 source code is just about identical

attached is a zip file with

board-zte-arthur.c.org (original)
board-zte-arthur.c.v9mod (my mod)
board-zte-v9plus.c (found in v9 Plus source)
dconfig (the config I am using with debug enabled)

krnlmods.zip



if you want to try my modded board file, rename it to board-zte-arthur.c

and overwrite the file located in /arch/arm/mach-msm

if you want to use my dconfig

cp dconfig .config


This is not done yet, and is only for testing

But I do need some help with this, because I am a little out of my element

Like I said I have not tried this with a stock ROM, I have CM7 on my phone and I am testing with that

here is another thing i noticed

if you use the B08C init binary, it will not boot


B07, B07, and B08 is boot looping for me now

here are all the ramdisks B06-B08C

ramdisks.zip

ok

so I have decided to go back and change on thing at a time in the and use the original config (instead of the debug config)

board-zte-arthur.c

and it I was able to produce the same results with adding just one line that the v9 plus had

#include <linux/init.h>

it should look something like this at the top if you make the change





ok so now I am going to see if I can figure out why it is boot looping

have u guys tryied the ZTE N850 Series - Gingerbread kernel(2.6.35) source code

aenoch said:

have u guys tryied the ZTE N850 Series - Gingerbread kernel(2.6.35) source code

Click to expand...

lol

shinru2004 said:

I have and cant even get it to build, even tried editing it. But the files are different when compared to the warp source

Click to expand...

at first i thaught it was the warp source when i first seen it but then relized it said n850 it was released 3-26-12 and had the same kernal name

i tryied again to send an email to zte and they told me it was highly confidental instead of dirrecting me some place else

what was highly confidential?

the kernel source so i replied what the hell you already released it whats the difference now

aenoch said:

have u guys tryied the ZTE N850 Series - Gingerbread kernel(2.6.35) source code

Click to expand...

yes, I have


it is very similar

Im guessing theres no way to rip the kernel from the phone then reverse engineer it

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

DM? im guessing that dose not mean diagnostic mode