• 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!)

Well that's the thing we just don't know which files we need, well once the upload is complete, i'll post the links to the two adb pulls I did
 
well here is a blade pull, i made a custom script, i'm gonna go back and check a couple of other extract-files.sh to compare the differences
extracted.zip
i'll be gone for the next couple of days, i'll post my notes later
 
All I seen it extract is mainly lib files I'm pretty sure we need more than that what we need is a device folder like all the others
 
yup at this point we need to know which libs need to be pulled and where they go. If we can do that we have out extract-files.sh. Is there such thing as including too many libs by any chance?
 
Try this i made it using the ZTE V9 because the build similarities are very close, if it doesn't work then i will edit it and add more files. but as of right now its all we have to go on :)

PS: just change the extension to .sh and it will work

Snake X said:
yup at this point we need to know which libs need to be pulled and where they go. If we can do that we have out extract-files.sh. Is there such thing as including too many libs by any chance?
Click to expand...

I don't see where to many would be a bad thing. i would say the more original files we have the better a chance to remove and find the specific ones needed
 
I have my first real Android phone on the way, and the first thing I did was come here to find come CFW or CM. I'm really excited to see someone working on CM7 for the Warp. I don't have any experience with Android and only a little with Linux, but I'd love to help if I can. It's great to see someone doing this! Thanks!
 
ztewarpcm7 said:
Update: ok i seem to have all the files needed device folder in place everything is ready to build i will update you guys tomorrow and let you know if it boots up it should because i finally got all thats needed
Click to expand...

I've got my fingers crossed for ya! I've been following this forum for about 2 weeks now since I rooted my Warp. Good luck, bro!
 
also, i compared the zte blade and warp sources for the kernel, they are almost exactly the same, except for some debugging lines of code in a handful of files. i used a program to compare the sources.
 
downthemachine said:
also, i compared the zte blade and warp sources for the kernel, they are almost exactly the same, except for some debugging lines of code in a handful of files. i used a program to compare the sources.
Click to expand...

nice work!! Maybe we can build extract-files.sh based on the files that are different?
 
Not sure where I should post this stuff to since we sorta have 2 CM7 threads going, but here goes...

Got adb working somewhat, but I've discovered that the system partition is not being mounted. (among others) Since adb works for anything that doesn't require any files on the system partition, I was able to do adb pull to get /proc/mounts and /proc/partitions. /proc/partitions looked good...all partitions appear to have been created same as stock, however here's the result of /proc/mounts. Items in red are not being created.

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p15 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p18 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

So, the parition mounting process is choking on the ext4 partitions. The "on emmc-fs" section of the stock init.rc seems to handle adding ext4 partitions on the stock phone, but I've not been able to find any CM7 init.rc files that have similar entries. Found that the Nexus S also uses ext4 for /system and the official CM7 init.rc for that phone only has the "on fs" section which mounts the yaffs2 partitions. Haven't been able to figure out where the Nexus mounts the ext4 stuff so I'm not really sure what to do as far as the Warp goes. Anyone have any ideas? I may mess around with the "on emmc-fs" settings again, but thought I'd post hoping someone knows something about this.
 
:)I just wanted to say its pretty cool reading this from page 1. Im new so i was checking it out and its the story of programming, I love it!! Thanks for the hard work, and have fun with it.:D
 
I just seen in prevail section Hroark is building CM9. He is amazing. I pm him to ask if he could give us a hand but he doesn't have this phone. We should all chip in and get him one . Just a thought
 
JBrd400 said:
Not sure where I should post this stuff to since we sorta have 2 CM7 threads going, but here goes...

Got adb working somewhat, but I've discovered that the system partition is not being mounted. (among others) Since adb works for anything that doesn't require any files on the system partition, I was able to do adb pull to get /proc/mounts and /proc/partitions. /proc/partitions looked good...all partitions appear to have been created same as stock, however here's the result of /proc/mounts. Items in red are not being created.

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p15 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p18 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

So, the parition mounting process is choking on the ext4 partitions. The "on emmc-fs" section of the stock init.rc seems to handle adding ext4 partitions on the stock phone, but I've not been able to find any CM7 init.rc files that have similar entries. Found that the Nexus S also uses ext4 for /system and the official CM7 init.rc for that phone only has the "on fs" section which mounts the yaffs2 partitions. Haven't been able to figure out where the Nexus mounts the ext4 stuff so I'm not really sure what to do as far as the Warp goes. Anyone have any ideas? I may mess around with the "on emmc-fs" settings again, but thought I'd post hoping someone knows something about this.
Click to expand...

well, im no pro myself, but from what i was able to tell from stock kernel, I couldnt find the ext4 module for the linux kernel. I also couldnt tell if the module was included in the zImage for the stock kernel, but it's not in the ramdisk, so it could be that we just need an ext4 module. I was having the same issue when i was building cm7. Maybe since this is my only day off in 2 weeks, I could give it a try.
[EDIT]
also when i was building the kernel from source, I noticed that the stock .config file thats included in the phone didnt have the ext4 module built. Im curious as to how zte is getting the ext4 partition loaded on boot. maybe they built the module seperately from the kernel, and used the same module for each build.
 
Glad to see you around and that you are also working on CM7. I'm also glad to see I'm not the only one having these issues. :)

As shinru mentioned, I think ext4 is built into the stock kernel. If I look at the .config for my stock phone's kernel, I see these 2 lines which I assume would take care of ext4.

CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y

Sorry to hear you're putting in so many hours at work, but it's good to know you're still around helping out when you can!
 
You must log in or register to reply here.
Back
Top Bottom