• 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 first dont we have to have an ics phone with the resolution of the warp to port? I didnt think u can convert hdpi (i think thats the abbreviation) roms to mdpi phones?
 
Development is always exciting, but extremely difficult if you are not well versed in android. Anyways patience is key here. I'm sure donations are always welcome but it doesn't help something get done faster. I'm not trying to offend anyone, just trying to point out that money doesn't make things move faster on a new phone. After its developed please do donate for the dev 's hard work!
 
news: snow day
status: lazy.
reason: terraria and tf2 with irl friends
progress: none since my last update :p

Yeah sorry I havn't updated my progress, ive been lazy recently and occupied by friends so I'll get to it hopefully by this week. I'm due at the beginning anyways, learning how linux works generally and going from there. That doesn't mean im dumping all my files also lol that would be a BIG waste.
 
Don't give up. I have been keeping up with progress and am very thankful for you guys putting so much effort into this I am looking forward to CM7 I hope you guys are just one script from porting it to the warp. Good luck and thank you for all of your efforts it will pan out just don't give up.
 
I know I haven't posted in a while, but found a couple things that may be contributing to the CM7 boot issues. I noticed that the partition sizes specified in boardconfig.mk don't seem to match up with the sizes listed in 'cat /proc/partitions'. I'm not positive I'm converting blocks to disk space correctly, but I believe the partition values listed in boardconfig.mk are smaller than they should be. (do your own research and confirm)

Don't know if anyone's noticed this already, but just thought I'd throw them out there. Even with these settings updated in boardconfig.mk, my phone still wouldn't even try to boot so there's still something else going on, but I think they should be updated regardless.

Edit: Thought I found an issue related to the kernel command line too, but I think it's okay after all.
 
if your using the old kernel or even a new kernel for the warp you need to install the modules or the phone wont boot, that could also be an issue. The modules are signed to where they will only work on the current kernel installed. Which may be why our new kernels wont boot the phone
 
Yeah, I've been trying with stock and custom kernels but have been adding any compiled modules to the /system/lib/modules folder. I just found another contributing factor as to why my stuff wouldn't boot though. There's an option for mkbootimg that I didn't see mentioned on any of the guides I've looked at. (mkbootimg repacks the kernel/ramdisk in a new boot.img file) Once I added "--pagesize 4096" to the mkbootimg command line (along with the kernel cmd line and kernel offset) the phone at least tries to boot when using a non-stock kernel. It still hangs at the android screen, but at least the red light goes out so it's getting farther than before. Without the --pagesize option being specified, it defaults to 2048 and apparently that causes the phone to freeze immediately at startup. (red light never goes out)

I'm actually thinking the issue may be with the init scripts/ramdisk at this point. If that is the case, I don't see myself figuring it out. They appear to be different for each device. Additionally after comparing stock init scripts vs cm7 init scripts for the same device there appear to be some changes made, but don't know enough about that stuff to make the same changes for the Warp. I'm mainly referring to the init.<device>.rc file, but there may be issues with the other init scripts as well.
 
the one for the zte blade is only for that phone we need a device folder for the warp with a extract-files.sh in order to have everything we need for a working build ive been working a lot so havent had time to look into but dont worry i stay on top of it on my free time
 
You must log in or register to reply here.
Back
Top Bottom