Discussion in 'Android Devices' started by Snake X, Feb 17, 2012.
ok, ill try that tomorrow
that should work also
Here's quietstorm's github
yeah, tho in order for me to make a build at all I had to have had some stuff from his github to begin with. Jbdr gave me new hope as to some links that may be missing here..
Good job Snake. First of all for taking on such a challenge.
I say we all pitch in with a $5-10$ donation or whatever you can afford, and get someone who has actually built a cm7 build, or maybe we could even get cm9 on the WARP. With the donation they can get a warp and some beer money. All we have to do is set up an account for a known developer and get him on this. I wish XDA-Devolopers had a forum for the WARP, or if we could even get some of the talent from there over here, because we need some action over here. I'm pretty sure XDA has already has the lower end models of the ZTE phones with developers building, why no WARP? I'm thinking the Prevail or Transform Ultra or devices with similar specs as the Warp, same CPU, RAM, Board, that is the developers we need to get involved. You know money changes a lot of stuff, I don't think it would be that hard for them to develop a build for us. Maybe even a developer that is a Boost customer, lets get him a warp and get this built.
I would really like to see cm9 on here but even cm7 would bring a smile my way. I don't know who to contact for this stuff, I've never developed anything so I'm not in the "in crowd" so to say I don't know who to contact, but I'm sure other here do. I have already heard some names mentioned. I will donate money to the cause though, whats $5-$10 dollars when we will have a bad ass phone when its done. Could you imagine ICS on the WARP!
When money gets involded thats when we are going to get what we want on our phones, at least that's the fastest way for us to see cm7 or cm9. Get someone a Warp and let them develop their @ss off!!!
I agree.... as the saying goes money walks etc etc
lol im already working on developing it though.. Unless you want another dev on here
Nope will donate to u kind sir.
ok progress update! I'm going to be dumping my boot.img (i did it wrong initially) so that I can continue workin on a debuggable cwm build
is this what you are looking for ?
Me too. Really appreciate your efforts.
no, that's different. Though, I think i may be able to dump it now that I realized i had to run it from my phone via adb shell... though havin problems with that (getting it sorted out)
let me know if you have questions. You should be able to use dd via the adb shell to save boot as an .img file.
dd wasn't a reconized command either..tho ill try again and edit if it works
edit: wait what was the full command for it?
This is what I used to save to my sdcard. Once you have it on your sdcard, you can grab it with adb pull.
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/dd_backup/boot.img bs=4096
adb shell dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/dd_backup/boot.img bs=4096
/dev/block/mmcblk0p12: cannot open for read: Permission denied
Did you su first?
yeah, i did sudo su first and the phone is recognized
edit: meet me in #ztewarpdev on freenode? That might be best instead of making 20 replies
No, I mean su within adb shell.
No that isn't what I meant at all, I was just saying that maybe a little help your way or a collaboration would probably help you out with the problems your having. I don't know your skills, what you can and can't do but help and other people working on a project wouldn't hurt. Ya know. I will donate to you or anyone. I know you are hard at work with cm7 but do you think cm9 is even possible with the specs of the WARP?
Actually jbdr400 helped me a crapload and so did the guys at #cyanogenmod-dev and so did shabbypenguin!
Ok so shabbypenguin has told me that I need to enable adb in the kernel. He told me to edit the default.prop when I unpack it. However, I'm not sure where that's located on the phone (sense he told me thats where it was) and what im even unpacking.. and idea's?
You have to unpack boot.img. That will give you the kernel and the ramdisk files. Default.prop is one of the ramdisk files that gets extracted.
Edit: Just noticed that the latest ROM I sent you had build.prop in it and not default.prop. Not sure if these are truly different files or whather build.prop should be renamed default.prop.
Edit again: They are 2 different files. The build.prop file is generated by the make process. Default.prop is inside the boot.img file. I only changed build.prop, not default.prop. However, looking at the settings, adb should be enabled already.
but he said i edit it when i unpack the kernel which im assuming means its inside the kernel?
There is (also ?) on the root of the phone (/default.prop)
I haven't messed around with the kernel yet, but I think he is using the term kernel in a generic way. I don't believe the kernel contains actual files per se. I can confirm that default.prop is part of the ramdisk files though. You might double-chck that my assumption is right. Pretty sure we're talking abut the same thing.