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

Root [Boost Mobile] Cyanogenmod 7 progress/updates (daily!)

i have the split_bootimg.zip if you need it, its a perl script. just shoot me a message and i will upload it for you
 
Not sure if that was for me or not, but yeah I have that script. Thanks...

I guess extracting the kernel from boot.img would be a better test, but I have to assume that the kernel file listed in the CM7 build output directory would be the same. Eh, I guess I'll check it anyway. No way to know for sure is until you check it.

Edit: For some reason I can't get the config from the CM7 boot.img. Can extract the boot.img file fine, but extract-ikconfig isn't seeing boot.img-kernel as a valid kernel image. Am I missing something?

Edit again: I can't figure out how to extract the kernel config from boot.img-kernel. All the guides I read say to replace that file with whatever kernel you want to use. None state how to modify/show the configuration of the existing kernel version. (extracted from boot.img) Sooo...unless someone knows how to do this, I'm going to let it go and assume that the kernel version packed in boot.img is the same as the kernel file listed in the CM7 output dir. (which appears to have the same config as stock)
 
Yeah thats what ive been trying to figure out is how to open it (as in boot.img-kernel), and figure out what it even is to begin with. Though, that's not important (except its origin and what its made from) because I don't think we can use a modified boot.img that's been re-packed. It just won't accept it. Ive had better luck with non split images from stock than the ones where i split it, change things, and repack which really makes me wonder if the build process compiles its own boot.img file

That being said, I need to identify what the file "kernel" is (found in /device/zte/warp). That's my top priority for now is figuring out what it is and if its the same thing as zImage. In the mean time, I have one last solution (I had 2 but i realized the boot.img files were the same) to try out (which is make it a nandroid format) and if they don't work then its definitely time to target the kernel.

edit: androidxD our boot.img files are the same.

This is the working boot.img i used that my computer recognized: http://www.mediafire.com/?8avhb7ntcgalwh6

md5: 9cecdd984daf85a0dcdd1a73a39e59aa boot.img

WERE GETTING WARMER (and so is my phone :D) !! Adb is now enabled!!!!

adb devices
List of devices attached
full_warpACF237 device

logcat dump:

Code: 
link_image[1962]:   294 could not load needed library 'libdiag.so' for 'logcat' (load_library[1104]: Library 'libdiag.so' not found)CANNOT LINK EXECUTABLE
\00

So I suspect that I do indeed need to update the files/modules for the phone

edit: it only connects for 2 minutes before disconnecting..

edit: DDDDDERRRRRRRRRPPPPPPPP!!!!!!!!!!!!! I think i found the problem.. there was no bootanimation.zip....... WOW lol no wonder why it wouldn't boot.. I found a cool cm7 boot animation that I put in there and you can edit the bootsound.mp3 if you want

I'm 60% sure that this thing will boot.. if not then im 85% sure I can at least logcat now that I fixed the lib problem
 
Yeah thats what ive been trying to figure out is how to open it (as in boot.img-kernel), and figure out what it even is to begin with. Though, that's not important (except its origin and what its made from) because I don't think we can use a modified boot.img that's been re-packed. It just won't accept it. Ive had better luck with non split images from stock than the ones where i split it, change things, and repack which really makes me wonder if the build process compiles its own boot.img file

That being said, I need to identify what the file "kernel" is (found in /device/zte/warp). That's my top priority for now is figuring out what it is and if its the same thing as zImage. In the mean time, I have one last solution (I had 2 but i realized the boot.img files were the same) to try out (which is make it a nandroid format) and if they don't work then its definitely time to target the kernel.
Click to expand...


Definitely make sure you test any repacked ramdisk files and boot.img files to make sure they extract correctly. I can see that step causing all kinds of problems if not done right.

Also I just figured out my problem from my previous post. Had an extra "kernel" in my command line where the terminal wrapped and didn't notice it. lol Oh well. Anyway, I checked the kernel files from the CM7 zip, /device/zte/warp, /out/target/product/warp and the config files appear to be identical. (diff reports no differences between any of them)
 
lol well that was anti-climactic.. when I was installing the cm7 nandroid it said md5 mismatch.. turns out not all the files copied XD

I'll edit this post with results of the REAL cm7 nandroid I made

edit: still can't logcat: here's the output: "Unable to open log device '/dev/log/system': Permission denied"

edit 2: Didn't boot but once I get that error figured out we can start logcatting and figuring out whats going on inside that thing :D which should help a lot

edit 3: I'll try chmod 777 on that directory to see if that doesn't solve things

edit 4: Nope! I'll try my luck one more time with an edited boot.img then if that doesn't work ill try it with the rom format.

edit 5: back to the kernel when I tried to make it (while im restoring nandroid to pass time) I get this:

Code: 
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
  CHK     include/linux/version.h
  CC      scripts/mod/empty.o
cc1: error: unrecognized command line option
 
FWIW, I actually tried merging the system folder with the "official" system folder for the Zte v9. No dice. Tried copying the warp files over the top of the v9 files, but didn't try the other way around. In any case, same result. Partial boot and reboot into CWM. I don't know. VERY frustrating...
 
What else is there to use that is an official CM build? The majority of the stuff was the same, except the v9 had some extra files and folders that the Warp didn't. One of which was libdiag.so, which you discovered was missing a couple posts back. Besides, I copied the Warp files over the v9 files so anything hardware or config-related would get overwitten with Warp files.

Edit: Note the Zte Skate looks like it has the majority of the same files as the v9. So just by looking at some other "official" configs, it looks like there are core files that exist between phones. (which are not present by default after the Warp build process)
 
I think I saw a brief reference to something like that too. I think it was specific to Ubuntu though. Good to know regardless. So do you know what settings need to be added/changed in the kernel? Without knowing that, I'm not sure rebuilding the kernel will do much good. Just for grins, I started to compare config files for the stock kernel and the official v9 one and there were A LOT of differences. Of course some are due to hardware differences, but I don't think all can be attributed to that.
 
Soz for the lack of activity :p I had to some stuffs

Ok, well I was told that the fix permissions feature would fix it (I hope) so in theory that should work.. If all goes well I'll post the logcat output here

Ok, so it seems when I merge EVERYTHING from /system to the one produced by cm7 I get stuck. So now I know it was something in there that made it do that I believe..

edit: Due to folder disorganization or whatnot, I have yet to test my new nandroid.. I got boot.img files messed up and now ive reorganized to prevent this from happening again.. lol sorry about that :p
I should be able to test it still tonight though

Ok. so I finally got it running (no not the cm7) but I mean the nandroid up and booting. The adb is connected and this time it doesn't seem to disconnect after 2 minutes o.O so progress! I'll reboot and fix permissions and hopefully with that I can logcat!

edit 2: Unfortunately I got the same result.. no logcat yet. Still working out with the guys at #cyanogenmod-dev

I need to find out what sets these permissions for /dev/log/system so I won't be denied permission. :/

EDIT:

I found in ueventd.rc this:

# logger should be world writable (for logging) but not readable
/dev/log/* 0662 root log

would that be why im not able to logcat? why shouldnt it be readable if thats what I need it for?
 
Ok, so it looks like im actually further back than what I thought. WAAAAAAAAY further back. It turns out that I was told that I my device tree is the problem.. I don't think its complete
 
yeah at this point im not sure what it could be.. I need a prebuilt zImage for the warp tho

edit: at the current point.. I'd say the warp is SOL.. we have only 2 ppl: a very busy developer and one who doesnt know jack squat lol (me :p)

I really don't know much about how linux works.. I think I got into doing this a bit too early... I should read a crash course into it first before continuing on

edit: quietstorm, do you have any suggestions on what to do?
 
Well, better get 'crackin! I did promise this would be updated daily :) so I should honor that. Tho im depressed about the whole thing because i went into it blindfolded practically and it just confused me. I think i'll start from step 1 with reading a crash course on how linux works in the first place

edit: first lol i wanna install titanium backup so I dont have to restore EVERYTHING back from the end of the day :p
 
We have faith in you man. I know you can Do this and for extra motivation I'm sure a lot of us would love to donate to you when you get this done..
 
yeah.. :) Thanks then

I have been quite busy today so maybe the weekend ill get some stuff done :p
I have 2 hrs to work on it left for 2day

edit: does anyone have a good lesson on how linux works in general?
 
20120301175631.png





:) try this book lol
 
First of all thanks to Snake JBrd400 and everyone else for trying to help make this happen!!! A lot of effort has been put into this for a beginner you have done a great job man.

I don't know shit about Linux I can install CWM, Fastboot, and Root but my devices that's it.

The problem I see is like I said before we need someone that has done this more than once, maybe someone, anyone really from the prevail build or from the other ZTE or Transform Ultra phones anyone that has the knowledge of doing it before. I know one ZTE phone is running either cm7 or cm9 over at XDA someone should be able to help if we all pitch in on it I would really like to see cm9 if it would be possible?

I got $10 myself on it guaranteed maybe more depends how funds look at the time. Thats all of us if we want it we need to make it worthwhile for someone that don't even use boost or have Warp phone to get involved and help develop we gotta pay, that's the only way I see us getting anywhere as of now.

Maybe a more formalized chat room instead of a message board, where everyone can can talk in real time, set one up. I see a lot of developers doing this on IRC. Get a group together in a chat room and work together on the same page.

We (the ZTE owners) might have to pay up front but oh well it would be worth it especially for cm9, I got the asus prime with ICS and its sweeeeet man. cm9 would kick ass on this phone 4.5 screen overclocked to 1.5 or more with cm9, would be a galaxy note wannabe. The touchpad guys got cm9 running easier than cm7, at least it seems that way. they have all kinds of cm9 roms getting built now my touchpad runs smooth as butter. It still has some issues that need sorted out but its new. (cm9 for Touchpad)

Hell I would be happy just to be able to overclock this thing for real a kernel.

I do want to say thanks again to everyone here who has put in all the time trying to get everyone (us) on here a Rom. Thanks maybe one day we will see it. I dont know how we don't have any devlopers this is the best Boost phone IMO. I took my Transform Ultra back as soon as I played around with the Warp.
 
You must log in or register to reply here.
Back
Top Bottom