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

[tookah]

Ok I think what would greatly help me at this point is figuring out the actual build process of cm7. By this, I mean what generally takes place, what files are pushed/pulled around in lamens terms and what kind of setup needs to take place in order for the correct files to go where they need to go. The reason I'm asking about this, I can't figure out what needs to be done to pull files from my warp as what I understand is what happens when you build cm7- it takes files off your phone.

Then again, I could try to go through what jbdr gave me first then ask questions afterwards, but im asking now

edit: progress update: none so far.. Workin on getting something to say.. lol

If you want Ill port it for you....



Jk

I, myself appreciate what you are doing but you seem kinda clueless LOL


Maybe this is what you are missing for this rom to run

Free Your Android - How to Port Android to Another Device

 

[JBrd400]

No, haven't tried contacting anyone other than Snake. I'm not a dev or anything, just trying to help out however I can. Definitely learning a lot, but there's no substitue for experience.

 

[JBrd400]

Well I am asking questions in the cm dev irc channel, so that should give an insight to something..

edit: I need to know how to make a extract-files.sh..

That's the issue I ran into. That file was already present for the other devices. You can look at the configs under the device folder to get an idea of what's in it, but the real question is how to know which specific files need to be copied.

 

[Lordvincent 90]

extract_files.sh cm7 - Google Search

[Q] Compile CM7 from sources - xda-developers

[CM7]KANG discussion - Page 11 - xda-developers

 

[Snake X]

extract_files.sh cm7 - Google Search

[Q] Compile CM7 from sources - xda-developers

[CM7]KANG discussion - Page 11 - xda-developers

Unfortunately this doesn't help.. Though thanks for trying! I appreciate all the help that is given to me because you all care

 

[Deleted User]

http://forum.cyanogenmod.com/topic/24137-compiling-cm7-no-rule-to-make-target-modembin/
Kinda random, but he talks about pulling libraries from the phone.

 

[Snake X]

essentially what I need to do is adb while in cwm so I can mount /system and look at files that were installed to show the people that can help me if the files were installed.. but seeing it right now theres no way to do that.

 

[Snake X]

Enea Android Blog: The init process and init.rc now THIS may give me some insight as to what I need to do.. and apparently init.rc has its own language? xD

I'll look into starting up the adb process so that can be enabled at least

 

[Lordvincent 90]

Snake, read the links... The last one talks about all that

If you're stuck on the step where you need to ADB to pull proprietary files from the phone, just:

1. download a CM7 nightly zip file
2. unzip the zip file somewhere
3. edit the adb script that pulls the proprietary file (I forgot the name, but you can search for it in the device specific folders, and grep for adb) to "cp" instead of "adb pull" from the folder you've unzipped from.
4. ????
5. PROFIT!

 

[Lordvincent 90]

I think cwm ha to be modified it include adb in recovery... Or the kernel ramdisk has to be edited

 

[Snake X]

yeah im trying to figure that out..

what is the code name of the zte warp? This is important.

 

[Lordvincent 90]

Unfortunately this doesn't help.. Though thanks for trying! I appreciate all the help that is given to me because you all care

You're right... I do care (about this phone becoming worth owning) if you actually take the time to read those links THOROUGHLY you would notice the KANG one is ALL ABOUT MAKING.CM7 FOR NEW DEVICES and the process...
Also Hroark13 will have some insight about init.rc

 

[Lordvincent 90]

He made a packer/unpacker for the prevail ramdisk

http://androidforums.com/galaxy-prevail-all-things-root/410648-prevail-kernel-ramdisk-packer.html

 

[Snake X]

sorry.. I will re-read the last one in that case.

https://github.com/sebastian404/android_device_zte_arthur I found sebastion's github!! I'll try this..

edit: it seems incomplete and doesnt work :L

 

[tjonline1991]

Maybe the cyanogemod guys will help us figure this out if we all asked them. They made a mod for the ZTE Blade, so why not the warp?

 

[Snake X]

Maybe the cyanogemod guys will help us figure this out if we all asked them. They made a mod for the ZTE Blade, so why not the warp?

that is the ONE thing I cannot figure out lol why they would support such an outdated device i mean its not even 1 GHz o:

 

[Deleted User]

i found another link, this guy made a stable cm7 for the zte skate, mind you it's a different processor, but the skate has many similar features, check it:
https://github.com/tilal6991/android_device_zte_skate
forum i found it on,
CyanogenMod 7 for ZTE Skate (Updated 06/01!&#33 - Android @ MoDaCo

 

[tjonline1991]

Hmm I wonder if each cm7 mod is exclusively set for the selected device. If not, then what is stopping us from testing out a cm7 mod designed for a different phone with similar features on our warps?

 

[Deleted User]

Drivers, mounts, it would be like taking one installation of ms windows and expecting it work on a completely different computer. Now the zte warp is a completely new phone, so this is pretty much building from scratch, i was just seeing if i could find so info to help with some missing links

 

[Deleted User]

Ok, i need to make something clear for those who haven't read this entire thread, DO NOT FLASH A ROM THAT WAS NOT MADE FOR THE WARP. I seen someone else post something about the zte skate's cm7, in another thread. I just want everyone to know it doesn't work, thank you

 

[Snake X]

Well I do have some very good news for the progress of cm7:

from a pm that shabbypenguin sent me:

Are you willing to help me with porting cm7 to the ZTE warp? I am pretty stuck and in a tight spot.. I have managed to build it but not without a lot of warnings and it won't even enable adb. It won't boot let alone reach the boot screen (sticks at splash image). I can't figure it out for my life, and I'm running out of options it seems like.. Here's my whole build output: PasteAll.org

I am using config files for cwm (https://github.com/QuietStorm1785) (I pasted those files in the /device/zte/warp folder I made) but the dev who made it for this device said it was possible to make cm7 from them but he didn't know how.

Thanks

warnings are fine, its errors that will throw ya off.

does adb devices see the phone? if os then it may jus be a matter of /system not getting mounted.

This takes care of A LOT of things seeing that most of the output that isn't smooth is just warnings. This also gives me a good sign because that might be all I need to do as he says..
BUT!
one.. small.. problem..

as of right now the only way adb works is through the stock rom and nothing else including cwm and my build. Thus, I need to ask quietstorm to add adb support to his next release of cwm... if he ever gets on again :S

 

[Snake X]

ok progress! I am on the fast-track to building a CUSTOM custom recovery.. thats right! This cwm will have adb enabled (no im not releasing it as its not necessary) so that I can do some things that need to be done to analyze the install of cm7

 

[tjonline1991]

ok progress! I am on the fast-track to building a CUSTOM custom recovery.. thats right! This cwm will have adb enabled (no im not releasing it as its not necessary) so that I can do some things that need to be done to analyze the install of cm7

Thats great news bro! Im so happy to see you doing all you can for us Warp owners. Im still on the ignorant side of building and/or analyzing custom roms, but Im not a complete noob. So if there's anything I can do to help, let me know.

 

[Snake X]

hmm im having trouble building cwm..

removed@removed-MS-7681 ~/cm7/system $ build/tools/device/mkvendor.sh zte warp ~/Desktop/stock_recovery.img
unpackbootimg not found. Is your android build environment set up and have the host tools been built?

 

[JBrd400]

It's always something... However I ran into that one earlier. Check and see if the unpackbootimg file is located in: ./out/host/linux-x86/bin. If so, just add that folder to your path and it should work.