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

Root [Boost Mobile] Cm7??

Z

ztewarpcm7

Member
does anyone have the vendor files for the warp i have all other proprietary files to build except for the vendor one thanks in advance
 
quietstorm's github: https://github.com/QuietStorm1785

edit: he said it was possible to build cm7 from that but he couldn't figure out how. Are you going to help develop cm7 for this phone? If so AWESOME! I have been trying but I went into doing so too early and i havn't gotten to start from the beginning yet, hepatic week. Try checking out this thread for the stuff me and JBdr found out: http://androidforums.com/warp-all-things-root/501493-cyanogenmod-7-progress-updates-daily.html

edit 2:
Spiyder said:
Someone get this guy the vendor file stat!!!
Click to expand...

lol
 
YOU ARE MY HERO. If you do get it built, please PLEASE let me know what was wrong with the device tree. I would like to know what was missing or whatnot. I have a build that I can adb in but it wont get past splashscreen if you wanna look at it. I almost say I will give it to you but Im just making sure if you wanna take a look or not at it

also what files are you missing?
 
I know about BoardConfig.mk but not sure about BoardConfigVendor.mk.. also not sure about the other 2 because I dont remember a lot of files with "vendor" in their titles
 
well if you check your cm7 repo you will see in the folder system/devices and run the command . extract-files.sh all the devices listed has those files which are required to build cm7 and for it to work maybe thats what we are missing
 
So does the one for the zte blade work for the warp to extract those files?
 
well i actually found out when you use zte blade extract files command it uses adb to pull the correct files you need to build but i got an error saying it didnt find the device warp in the cyanogen repo
 
I've been trying to figure this out as well and I've never seen any of these files.

BoardConfigVendor.mk
warp-vendor.mk
warp-vendor-blobs.mk

All we have is what QuietStorm has in his github. The Extract-files.sh script is part of that so you can get it from the link in Snake's previous post. Snake and I also got the error regarding the Warp not being in the Cyanogen repo. Had to take QuietStorm's files and save them to ./device/zte/warp. Once we did that, the build process worked as expected.

As a side note, I'm really glad to see someone else working on this. I'm close to the end of my rope trying to figure this out.

Edit: Oops...I just double-checked and I don't see the extract-files.sh script in the github. It's been a while since I started messing with this so apparently I grabbed my ver from another device. So it's highly probable that it is not configured to grab all the needed files for the Warp. I don't really use it though as QuietStorm has provided the majority of the files from the phone in his github and I just copy in whatever's needed after the build is done. Regardless, sorry about the bad info...
 
Yeah I was about to say that we don't have an extract-files.sh file and im not sure how to create one. All the guides assume you have one xD but we dont rly
 
ztewarpcm7 said:
well i actually found out when you use zte blade extract files command it uses adb to pull the correct files you need to build but i got an error saying it didnt find the device warp in the cyanogen repo
Click to expand...

https://github.com/QuietStorm1785

^ that is the repo for the most part.. The warp doesn't have a device folder by default (its not officially supported) so you make a folder called warp in /device/zte and put the files in there
 
JBrd400 said:
I've been trying to figure this out as well and I've never seen any of these files.

BoardConfigVendor.mk
warp-vendor.mk
warp-vendor-blobs.mk

All we have is what QuietStorm has in his github. The Extract-files.sh script is part of that so you can get it from the link in Snake's previous post. Snake and I also got the error regarding the Warp not being in the Cyanogen repo. Had to take QuietStorm's files and save them to ./device/zte/warp. Once we did that, the build process worked as expected.

As a side note, I'm really glad to see someone else working on this. I'm close to the end of my rope trying to figure this out.

Edit: Oops...I just double-checked and I don't see the extract-files.sh script in the github. It's been a while since I started messing with this so apparently I grabbed my ver from another device. So it's highly probable that it is not configured to grab all the needed files for the Warp. I don't really use it though as QuietStorm has provided the majority of the files from the phone in his github and I just copy in whatever's needed after the build is done. Regardless, sorry about the bad info...
Click to expand...

I've been on vacation for the last couple of days, i've been modifying the blade setup to work with the warp, when I get home i'll upload my work
 
Cool. I really hope you figured it out...

I've also been spending lots of hours comparing the files and file contents of the blade and skate, both stock and CM7 and have nothing to show for it. Went through all the init-type scripts looking for files that were called and made sure they were included where the scripts were looking for them and it still hangs with no adb support. Since there's no adb, no error on the screen, and no way to validate that the updater script is even doing what it needs to be doing, this is really like finding a needle in a haystack blindfolded. I've read that adb is actually part of CWM for other phones. Anyone know why does the Warp's version not have it? Is the issue the version of CWM that was ported or just something that wasn't included in the porting process? (or something else?)

Anyway, I'm pretty sure I should have the necessary files needed to at least boot, but have no way of knowing for sure. (I have all the ones called by the init scripts...many of which were not added as part of the CM build process. I believe my issue is with the init scripts somewhere. My latest suspiscion is due surrounds the fact that the warp has an ext4 system partition. All the other CM7 init scripts I've seen are phones that use yaffs2. Would really like to how init.rc is configured for a CM7 port that uses ext4. Tried using stock partition settings in init.rc, but didn't help.

Anyway, unless we get some kind of logging ability, I probably won't be doing a whole lot more on this. If there was some kind of way to view logs & files on the phone (after flashing) I *might* be able to figure something out, but it is an exercise in futility at the moment. Someone with an actual dev background would not need to try reverse engineering everything and may do just fine. Devs have a much better chance of looking at code and being able to tell if it's right vs. relying on errors/logs to tell them it's wrong.
 
JBrd400 said:
Cool. I really hope you figured it out...

I've also been spending lots of hours comparing the files and file contents of the blade and skate, both stock and CM7 and have nothing to show for it. Went through all the init-type scripts looking for files that were called and made sure they were included where the scripts were looking for them and it still hangs with no adb support. Since there's no adb, no error on the screen, and no way to validate that the updater script is even doing what it needs to be doing, this is really like finding a needle in a haystack blindfolded. I've read that adb is actually part of CWM for other phones. Anyone know why does the Warp's version not have it? Is the issue the version of CWM that was ported or just something that wasn't included in the porting process? (or something else?)

Anyway, I'm pretty sure I should have the necessary files needed to at least boot, but have no way of knowing for sure. (I have all the ones called by the init scripts...many of which were not added as part of the CM build process. I believe my issue is with the init scripts somewhere. My latest suspiscion is due surrounds the fact that the warp has an ext4 system partition. All the other CM7 init scripts I've seen are phones that use yaffs2. Would really like to how init.rc is configured for a CM7 port that uses ext4. Tried using stock partition settings in init.rc, but didn't help.

Anyway, unless we get some kind of logging ability, I probably won't be doing a whole lot more on this. If there was some kind of way to view logs & files on the phone (after flashing) I *might* be able to figure something out, but it is an exercise in futility at the moment. Someone with an actual dev background would not need to try reverse engineering everything and may do just fine. Devs have a much better chance of looking at code and being able to tell if it's right vs. relying on errors/logs to tell them it's wrong.
Click to expand...

It should work ro.adbpersistent=1 is on
 
Problem is, I dont think the phone is even booting far enough to where adb is started. I have this in default.prop. Different than yours, but I assume does the same?

persist.service.adb.enable=1
 
Okay. I dunno then. I did find something funny when I was screwing around with the system partition stuff in init.rc. When there were no commands to create an ext4 system partition, adb worked...sorta. It identified the device as CM7_Warp (I think), however if you tried to do any other adb commands it would say that it couldn't find /system/bin/sh. The file was present in the system folder in the ROM so without any way of browsing the phone's file system, I had no idea as to how to troubleshoot further. After messing around with it some more, I noticed that the ext4 section was missing from init.rc. Once I added the part of the init.rc that creates the ext4 system partition, it went back to hanging after boot and no adb support at all. Go figure?

If we had adb support in CWM, theoretically we'd be able to validate that partitions are created, files are copied, etc. Without that, it's anyone's guess as to what's happening.
 
Well like I said, when I get home i'll finish up the my idea, I got the extract script working, I just need to finish up compairing and modifying the rest
 
I got a build lying around that has adb working on it if you wanna try that.. however when you logcat it gives you a permissions denied error
 
Snake X said:
I got a build lying around that has adb working on it if you wanna try that.. however when you logcat it gives you a permissions denied error
Click to expand...

Sure, I'd love to take a look at it. Sounds like you are pretty close to having it working.
 
I found that the Nexus S uses an ext4 system partition and it doesn't have the "on emmc-fs" section in init.rc like the warp does. (stock) So, I went ahead and removed it again and it's back to giving the "- exec '/system/bin/sh' failed: No such file or directory (2) - " errors again. Based on what I've found, adb does appear to be working as I can use adb pull to pull init.rc from the root of the phone's file system, but it fails when I try to pull anything from /system. Soooo...I guess that proves that the system partition is not being created correctly. Just not sure what needs to be tweaked to fix it.

Snake - I was able to reproduce the issue of getting permission denied errors when using adb. Make sure your adb file (in android sdk) has the execute permission set. I found that if it was unchecked, I would get the same errors. Just something to check if you haven't already.
 
You must log in or register to reply here.
Back
Top Bottom