Database Info

[ROM - 32B] ZeroXd 5.2r4 / JACHeroSki-v2.0 [09/11/2009 - 11:47AM EST]

I will be accepting donations if you like my work. After contacting HTC, they informed me that my device is not under warranty, as a technician determined it to be "user related" damage and that all repairs will be at owner expense.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8141983
If you follow my twitter, you know I bricked my G1. I am trying to get it repaired, but due to the long response time I had to buy a mytouch (no point having two G1s IF the other one gets repaired). Using this bad luck to my advantage, I scripted a way for hero to run on both with two simple commands.
How I rooted a brand new "perfected SPL" MT3G and installed Hero in 15 min:
http://forum.xda-developers.com/show...&postcount=154
Link to original thread: http://forum.xda-developers.com/showthread.php?p=4365404#post4365404
Updated, but still feeling slow? Back up. Try rm system/sd/app_s then reboot to recovery and wipe data. then install fresh. Before restoring your data, open the backup folder on your sd card and remove the subfolders for programs you no longer have or need to have backed up.
I noticed a 10% increase in speed and my phone was far from lagging to begin with.
Losing messages? Make sure that system/sd/app/com.android.mms.apk does NOT exist, as this was an old release. Go into settings for messaging (from the conversation list panel) and set priority to "High"
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-6.0.zip
Now includes dynamic swap. Rewrote the method of apps to sd for myTouch.
Build will move system apps, user apps, and dalvik to sd on a g1 device.
Build will ONLY move user apps to the sd when using a myTouch.
This will allow the system apps and dalvik to remain on internal device.
This is a completely new method of doing a merge build so bear with me.
I am going to be rewriting things for users without a lot of user apps, like myself.
This will allow the entire build to be placed onto internal for mytouch users.
Once you have updated and are ready to use the phone, execute Terminal and enter the following commands:
su
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
Bluetooth restored in MT3G
Porting my own boots for MT3G
Based on the System Image from Haykuro
Using the Kernel and Boot.img from JAC
Extensive system script edits were done
SwitchROM installs itself to system/sd/
LEDs are at about 90-100% brightness
CPU Optimization turned off by default
Enhanced Terminal included
Fixed My Account included
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.2r5.zip
http://twistedumbrella.slackdev.com/Resources.zip

twistedumbrella said:
MultiTouch for MT3G being patched NOW
Click to expand...
Click to collapse
Does that mean multitouch doesn't work and one more unanswered questio IS it from the latest release that modaco did, i asked it since 5.0 so please answer

White Rosie doesn't work i tried it but i doesn't show up and it doesn't even install shows parse error, can you do something about that. Really appreciate your work. Will donate as soon i finish with my exams, I came to US for a holiday for 3 months and as i came back i have exams, only 3 left, have to finish 6 books per subject (thats f*****ng 3 months syllabus) and i have exams after 2 day holidays , thats why i have been a bit inactive in the community, will be active on 24 and will provide a special version of HERO based on my favourite ZEROXD.

Installed JACHeroSki 2.0 and i get stuck on a boot loop. i've tried wiping and re-flashing and same thing.

mgorman said:
Installed JACHeroSki 2.0 and i get stuck on a boot loop. i've tried wiping and re-flashing and same thing.
Click to expand...
Click to collapse
For me 2.0 working fine,but cannot install ZeroXd-5.2r4-installation aborted:/
In v2.0 cannot run wifi:/somebody else?

Had to fix scripts. Check the link on original thread for download. They are the same files. The verification fail happens when your downloading as I upload. It was a last minute fix on the way to work. Sorry for the issues.

hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?

tq745 said:
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
Click to expand...
Click to collapse
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother

tq745 said:
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
Click to expand...
Click to collapse
Thank you... h.nocturna for the fix, and nacron for the heads up...
Here is the fix for auto-complete... Worked for me on 5.1r2
Everything in
open dos prompt.
adb remount
(***back up the original***)
adb pull /system/sd/app_s/HTC_IME.apk c:\(*your directory*)\HTC_IME.apk
(***install the new one***)
adb push c:\(*your directory*)\HTC_IME.apk /system/sd/app_s/HTC_IME.apk
start your Messaging it will crash the first time you want to use the keyboard... restart Messaging and it should work...
HTC_IME.apk here: http://www.mediafire.com/?te0symyx4yz
Mms auto-rotate works for me in 5.1r2 so I dont know. But possibly you still have the old Mms.apk. Try pushing the new one from 5.0 or later rom...

Twisted are you using BFS in your new builds??? Post 5.1 that is....

twistedumbrella said:
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
Click to expand...
Click to collapse
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambesey's way

twistedumbrella said:
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
Click to expand...
Click to collapse
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambezy's way

same issue as above :-(

1.8 is running pretty awesome.
i guess its safe to assume that i shouldn't try 2.0 yet? lol

zeroxd 5.2r4 seems to be faster than jacs 2.0 but i cant get auto rotate to work or multitouch and when i try the commands in first post i get "/system/xbin/su: not found''

did you try running the commands via adb ?

im not familiar with doing it that way i dnt even know wat adb is

just connect your phone to the pc
install the drivers from android SDK
start > run > cmd
cd to the android tools directory
and adb shell
that's how i did with my phone and works perfectly

im not gona risk any damage ill deal without the rotate for a day till its fixed

tq745 said:
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambezy's way
Click to expand...
Click to collapse
should be under /system/bin not xbin

FIXED: Tethering in Stock ROM w/ Root

Hello,
This is a dead easy fix to get tethering working completely with android-wifi-tether (http://code.google.com/p/android-wifi-tether/):
UPDATE
New development version has support for this rolled in, instructions are no longer necessary:
http://code.google.com/p/android-wi...name=wireless_tether_2_0_2-pre14.apk&can=2&q=
Steps:
1. Open adb shell (start cmd.exe, run "adb shell")
2. Issue the following commands:
- "mkdir /sdcard/android.tether"
- "cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
3. Download and install the android-wifi-tether application, start tethering.
Your log from android-wifi-tether should look like the attached image.
Happy configuration free tethering!
NOTE: This works because of the two separate firmwares that HTC has included in /etc/firmware. One is specific for AP-mode and must be more open to this kind of stuff. The original bug stemmed from the usual firmware dropping ARP requests pretty consistently, possibly as a powersaving measure.
The second firmware is loaded using the firmware_path option when loading the bcm4329.ko kernel module.

anyone else confirm this working please.

I confirm this working...

You will need to have root to run the app of course but 2 or 3 people have confirmed it on bug 362 already on the google project.

Not working for me

AWESOME!!!
actually i ever use wifi tether but this is pretty cool because it actually worked. i know on the heroC we had issues with wifi tether all of a sudden not wrking after 2.1. nice to see that its been fixed. good work spreading the word

ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.

would be cool if someone can confirm 4g is able to be tethered.

fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
same here. any ideas?

toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
Not confirming but based on what I read harry_m stated the wifi tether app uses the current connection, so in theory if you switch between 3g and 4g the app will switch accordingly.

i can confirm
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.

fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.

toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
dcmtnbkr said:
same here. any ideas?
Click to expand...
Click to collapse
It should work according to one of the comments given about the issue. http://code.google.com/p/android-wifi-tether/issues/detail?id=362#c36
Because I am weary of rooting my phone not being able to return it to stock, I am gonna try it with the unrevoked root first.

goodfellaslxa said:
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
Click to expand...
Click to collapse
i followed this same exactly.
andrew500 said:
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
Click to expand...
Click to collapse
no errors in adb.
and the .bin file is sitting in the directory.
and the log looks like yours.

running toasts ROM
can't get this to work
followed instructions, and when i click on the tether button it instantly says: unable to start tethering, please try again!
log screen is completely blank
any ideas?

fdot said:
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.

"Unable to start teterhing try again"
I skimmed this thread, I am using toast's rom.

I have just applied the Unrevoked root. I cannot access the sdcard via adb shell. Any ideas?

When i send command
"cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
it gives me error msg
"cannot creat /sdcard/android.tether/fw_bcm4329.bin: directory nonexistent"

i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
Click to expand...
Click to collapse
I have not done the ota.
-------------------------------------
Sent via the XDA Tapatalk App

[GUIDE] Bad WiMax MAC? Broken 4G after update? Fix HERE!

Well I know I'm not the only one who got a bad WiMax MAC address after trying to update my WiMax radio image. I should learn to not try and fix things if they aren't broken
If you've gotten the dreaded "00:16:08:00:24:05" MAC address like I did, this guide will help you fix it. You'll need fastboot set up, a NAND unlocked phone with Toast's part 2 method, your correct MAC address for WiMax, and the files below.
FILES:
New radio
New WiMax
You MUST download & flash these again even if you already have. I don't care if you think you already have the right ones, download these. If you don't, don't ask me for help if you use the wrong ones.
STEP 1: Fix MAC
First, get your right MAC address. It can be found under the battery by the WiMax tag, or on your box under the WiMax barcode. It should be 12 digits long, with no colons in it. If it were supposed to be "00:16:08:00:24:05" it would look like 001608002405 on the box. Write that address down with a colon between every two characters to get it in the right format.
Next, boot your phone into fastboot mode. If you don't know how to do this, hold down volume and press power to boot into the bootloader. After it brings up the menu where "FASTBOOT" is highlighted, press power. It should say "FASTBOOT USB" in red where it previously said "HBOOT" in green.
On your PC, open a shell. First off, lets see if you have a bad MAC, run
Code:
fastboot oem wimaxrmac
It should return something like
Code:
INFOcmd_wimaxrmac
INFODev MAC = *Your MAC address will be here*
OKAY
If it doesn't match the code you wrote down, then you have a bad MAC. If it does match the code you wrote, then skip to step 2.
To fix it, you need to run:
Code:
fastboot oem wimaxwmac *Address you wrote down here*
Like if you wanted it to be "00:16:08:00:24:05" then you would run:
Code:
fastboot oem wimaxwmac 00:16:08:00:24:05
It should return something like:
Code:
INFOcmd_wimaxwmac
IFNOWrite OK! MAC = *Address you entered here*
OKAY
Then just run
Code:
fastboot reboot
To reboot back into Android with your correct MAC address.
STEP 2: Flash the images again
Now push those files to your SD card & reboot into recovery.
Once you're in recovery, flash the "evo.2.05.00.06.10.zip" file. Reboot from the menu like it tells you. Once you're in Android, update your Profile & update your PRL.
Now reboot into recovery again, this time flash the "evo.wimax.25641_r01.zip" file. Reboot again from the menu, and guess what. Once again, update your Profile & PRL. Reboot one more time for good measure, and you should have working 4G. I haven't been able to confirm 4G myself, but others have reported it working with my method. My logcat no longer shows any 4G errors and neither does the kernel log, plus all the data now matches how it was before my update, so that leads me to believe it's working.
I wrecked my MAC with the update and fixed it like this, but I haven't had a chance to try out 4G yet since I won't be going into the city where I'll have coverage until Saturday.
Please post here if it works for you or if it isn't clear then just post & I'll try and clear it up.
Regards,
Jesse C.
EDIT: As a few posters had trouble, it came to my attention that you MUST have run Toast's root part 2 image to have access to fastboot oem commands.
EDIT 2: Now full 4G fix.

Thank you so much!
Sent from my PC36100 using XDA App

On it.....!!!!

It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.

Hot damn!!!! It works!!!

Neotelos_com said:
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Click to expand...
Click to collapse
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure

Geniusdog254 said:
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Click to expand...
Click to collapse
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).

Well i changes the mac....i dont know if 4G is working on it.....

ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.

( waiting for device )
*nevermind*
Sleep..needed badly

Travyevo said:
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
Click to expand...
Click to collapse
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.

asrebel said:
*nevermind*
Sleep..needed badly
Click to expand...
Click to collapse
are you in fastboot?

Neotelos_com said:
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Click to expand...
Click to collapse
I saw the same thing. I ended up with the one i posted in the OP but it seems they all start with the 00:16:08 characters.
I don't think its safe to post the after MAC address, sicne it's unique to every device. It won't hurt anything, but I'd rather keep mine private

Neotelos_com said:
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
Click to expand...
Click to collapse
ADB appeared to install when i connected it. I'll take a look.
Thanks

my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?

Anyone 4G back working using this method?

rocolema said:
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Click to expand...
Click to collapse
Yes. It should work for everyone. Do you have the newest fastboot?
david279 said:
Anyone 4G back working using this method?
Click to expand...
Click to collapse
I thought you said you had it working? Do you not have 4G or did it not fix the 4G errors

It fixed my MAC address. I have no 4G to test to see if thats working.

This is an interesting method.
I have restored my MAC via a different route, but I believe if I were to flash an offical wimax right now, I would lose my MAC again. What I have done requires modification to the wimax.img file.
Does this persist through reboots? If it does, this would likely be the best answer to the problem of the bad mac addresses.

david279 said:
It fixed my MAC address. I have no 4G to test to see if thats working.
Click to expand...
Click to collapse
Ah okay. I'm in the same boat

adb and fastboot for PowerPC Macs

I managed to successfully compile the adb and fastboot binaries for PowerPC by hacking the Android SDK a little bit. If you use a PowerPC Mac and would like to use it for debugging/etc Android device, you may find these interesting. (The apps were compiled under Leopard, I have no clue if they will also run on Tiger or not)
Word of warning: I don't take any responsibility if any of these apps kill your phone or the neighbors. You have been warned.
Known bugs: serial numbers are shown incorrectly in both apps, also you should run them from iTerm as they messed up the standard Terminal.app for me once.
Tested and working features (on a PowerBook 12" 1.5Ghz and an iBook G4):
adb:
shell
logcat
reboot
bugreport
push
pull
fastboot:
reboot
reboot-bootloader
flash (radio|hboot)
erase (system|boot)
acp:
Didn't test this one, I never used it, but seems like working.
Since I don't have any other machine ATM, I couldn't test the flash function yet, I'm planning to do that soon. Anybody curious enough to test, please reply with your results, so I can update the list. As always, donations are welcome

Just tested on my ibook g4!
It works fine! Thank You very much!
EDIT:
I used it to flash the new bootloader (1.33.013d) and the new radio (2.22.28.25_S) via fastboot.
Commands tested:
fastboot flash radio RADIO-2.22.28.25.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
fastboot erase system -w
fastboot erase boot
fastboot reboot

Glad to hear that, I'll update the first post in a few minutes. Can you confirm the bug with the serial numbers or was it working for you?

Z0l said:
Glad to hear that, I'll update the first post in a few minutes. Can you confirm the bug with the serial numbers or was it working for you?
Click to expand...
Click to collapse
The serial number isn't shown but appear "####"
iBook:android_ppc michele$ ./adb devices
List of devices attached
#### device
iBook:android_ppc michele$
Click to expand...
Click to collapse

@Z0l, could you post a patch for the source?
I tried briefly to do exactly what you've managed to do, but no point in reinventing the wheel

Actually there is no patch What you should do is to checkout the froyo sdk with repo (this is important, because gingerbread requires java6, which is a bit problematic on ppc), copy the build/core/combo/HOST_darwin-x86.mk to HOST_darwin-ppc.mk, then issue the "make adb" and "make fastboot" from the top of the source. I think I received some warnings, but at the end the binaries were at out/host/darwin-ppc/bin. So, the actual commands are:
repo init -u git://git.android-x86.org/manifest.git -b froyo
repo sync
cp build/core/combo/HOST_darwin-x86.mk build/core/combo/HOST_darwin-ppc.mk
make adb
make fastboot
Click to expand...
Click to collapse
Hope that helps. Also, make sure you do the compile on a case-sensitive filesystem (I created a case-sensitive dmg for that)

Does this still work with Gingerbread and ICS devices like the Nexus S and the Galaxy Nexus?
Thanks for answering in advance.
land.apfel

I'd say yes because I see no reason for them not to work. Although both adb and fastboot received updates, the fundamentals are the same.

OK, so I'll try them but I won't be able to use the backup feature, will I?
Sent from my Galaxy Nexus using XDA

land.apfel said:
OK, so I'll try them but I won't be able to use the backup feature, will I?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Could you elaborate a bit what you mean under backup? All the adb and fastboot commands worked when I tested them.

With backup I mean "$ ./adb backup".
Sent from my Galaxy Nexus using XDA

These binaries were compiled long before ICS existed (adb backup is available since ICS), so I don't think it'll work. You can try compiling a new version yourself, unfortunately I no longer have access to a PPC dev environment.

That's why I've asked.
Unfortunately I'm too dumb to compile it by myself
Sent from my Galaxy Nexus using XDA

iBook G3
Hi there,
Sorry to bump such an old topic! But I think I have a (very?????) special case. Is it possible to compile the newer ICS Binaries..... for iBook G3 on 10.4.11?
I tried running these and I got the dreaded "Incompatible CPU subtype" so I assume they're for G4 and up. Is there a way this could be changed?

blackthund3r said:
Hi there,
Sorry to bump such an old topic! But I think I have a (very?????) special case. Is it possible to compile the newer ICS Binaries..... for iBook G3 on 10.4.11?
I tried running these and I got the dreaded "Incompatible CPU subtype" so I assume they're for G4 and up. Is there a way this could be changed?
Click to expand...
Click to collapse
Sorry for the late reply, you cannot compile anything newer than GB on powerpc. Even GB needed the above trick, but since ICS requires a Java that never existed for powerpc, I think its impossible.
Sent from my Galaxy Nexus using xda app-developers app

Z0l said:
Sorry for the late reply, you cannot compile anything newer than GB on powerpc. Even GB needed the above trick, but since ICS requires a Java that never existed for powerpc, I think its impossible.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Haha ok fair enough the hardware is kinda old anyway. ;p
It's because when parents remove the Windows laptop I only have my iBook or athlon server left xD

[Q] What attribute about a custom ROM would prohibit connection to adb?

The dalvik bug console refuses connection with only this certain ROM in my sig. "Connection refused by the remote host". I have a backup of my last CoreDroid flash, and it connects as expected (I have it restored to the handset now, and am watching the log scroll away on the console). I installed adb and the dalvik console back when I was stock to use for screen shots. I have never had any issue with it. I have installed all the drivers that I believe are required, and have connected to adb with 3 other ROM's with absolutely no issue. So I have to believe this is nothing I have done.
So the question is, what attribute vs. a specific ROM would cause connection refusal to adb? Thank you.

meiguoguizi said:
The dalvik bug console refuses connection with only this certain ROM in my sig. "Connection refused by the remote host". I have a backup of my last CoreDroid flash, and it connects as expected (I have it restored to the handset now, and am watching the log scroll away on the console). I installed adb and the dalvik console back when I was stock to use for screen shots. I have never had any issue with it. I have installed all the drivers that I believe are required, and have connected to adb with 3 other ROM's with absolutely no issue. So I have to believe this is nothing I have done.
So the question is, what attribute vs. a specific ROM would cause connection refusal to adb? Thank you.
Click to expand...
Click to collapse
Make sure debugging is turned on

zelendel said:
Make sure debugging is turned on
Click to expand...
Click to collapse
Yes debugging is confirmed on. I have never had a problem in two months using adb. In this case it is a difference between two ROM's. I can restore CoreDroid v7 and connect as expected. On the ROM in my sig I cannot. I have restored them back to back and connection problem is only with this ROM.
I did find this thread on XDA where someone had a similar issue:
http://forum.xda-developers.com/showthread.php?t=647991&page=3
The fixed for this thread was to un-install and re-install HTC Sync.
Originally Posted by ccapasso
I have win 7 64 and here is what worked for me:
1. Uninstall HTC Driver (this will likely give you an error, you can ignore it)
2. Uninstall HTC Sync
3. Download and install PdaNet
4. Follow the directions when installing PdaNet
The end.
This worked for me. I just wish I found this thread earlier (didn't seem quite as easy to find as I would've thought). Thank you. Thank you. Thank you.
I'm going to try this later. I don't fully understand that while I have the latest drivers for adb, one ROM will connect and one will not...that is sort of what I am looking for, a more technical explanation as to why this would be so. Thanks.

The adb daemon (adbd) is run from the init.rc script. Perhaps it was left out of your ROM (I don't know which one because I have sigs turned off in my profile). This is part of the boot.img so if your using a different kernel, it may have issues with finding the adbd program.

Gene Poole said:
The adb daemon (adbd) is run from the init.rc script. Perhaps it was left out of your ROM (I don't know which one because I have sigs turned off in my profile). This is part of the boot.img so if your using a different kernel, it may have issues with finding the adbd program.
Click to expand...
Click to collapse
Thanks Gene Poole! This is exactly the type of information I was looking for. Another user that has this version of ROM confirmed the same issue on this ROM's thread. So the devs will know about it anyways. They have a place to post bugs on their website, but I kind of want to exhaust options before posting there. Here are my device stats:
[DEVICE] HTC Inspire "4G"
[NETWORK] AT&T 3.5G
[HOME LOCATION] Portland, OR USA
[ROM] Virtuous Unity v1.25.0
[RADIO] 12.39a.60.19U_26.06.06.30_M
[KERNEL] Unity V1
Unity V1 is the kernel that is packaged with the ROM. I could try Unity V2 as a kernel option. I will try this first, and if it doesn't work, try the method in the other thread of wiping and re-installing HTC sync and PdaNet. I'm a noob, but HTC sync has also been finicky with my Sense ROM setups as usually the only major functionality issue. Thanks again! You are always very helpful with your posts.

[Fixed]
Un-installing and re=installing the entire Android-sdk rectified the issues for this ROM. Why other ROM's would connect and Virtuous wouldn't with the previous install is unknown.