[EVO 4G Themes and Apps] davidlightle:
Hmmm, I'm not sure if this is going to be as fruitful as I'd hoped then. I'm seeing some really confusing results (yours, mine, and others').

So, there are only a handful of things being done in the application itself to get wired tethering working; I lucked into finding that having some symlinks to busybox in lieu of some binaries in /system/bin somehow allowed my wired tether to work when others didn't; I then narrowed down by process-of-elimination, to find that the ip binary was the only one needed to make it work. This ip command isn't called directly in the application, so must be involved at a lower-level when something changes around the networking. Still, there has to be a way to make it work without this (or with minor changes in the source) since stock FroYo has a way of USB tethering built-in on the Evo still.

However, I know with my testing of this toggle, that one time I had my fix turned off (using the "non-working" originally included ip binary), with wired tether enabled. I rebooted the computer, and it picked up the connection and it worked! That was very confusing. I tried to reproduce that, but had no luck. After that I started testing by restarting the phone and computer, which was a huge hassle.

I'm really baffled why the 4G is breaking; I know sometimes when disabling the wired tethering, it can leave a remnant connection (disabled and unable to be enabled at all), and this also is symptomatic that the computer won't shutdown as a result and I don't know why this happens (I had a thought, but it doesn't seem to be a fix).

Sorry, bit of a rant and ramble, but also a bit of a braindump. I'm far from an expert here, so I may be goofing things up or doing something stupid or even overlooking something simple.

I do have a "restore from toggle 2.0" update (flashable in recovery, even Amon Ra; same as "restore from toggle 1.0"), but it only does things like removing the script and fixing the symlinks and putting the original ip binary back in place where it should be. But if the script's "off" mode isn't letting 4G work again, I'm not sure that this will be a true restore either. It could be, though, as nothing should be any different then from even stock in regards to what I would've changed.

One thought that might put me slightly at more ease: have you tried rebooting the phone at all, especially after doing the tetherFix off? I know this wouldn't be ideal, but if a reboot does help in this case, then that tells me something is working, but I'm leaving something unchanged (routing table maybe? or something else?).

I really hate that this isn't the "one simple change and done" fix that I expected a couple months ago, and in fact it seems like things are slipping farther from where I want them to be instead of getting closer to final. I also hate that, since I have no 4G access, that I'm putting others into a guinea pig position; I hope I've spoken enough on making nandroid backups that nobody's system needs fully restored as a result. I will definitely help as much as I reasonably can if there are remaining problems, though "tech support" via email isn't the easiest and I can't guarantee I do the best job at explaining everything that's in my head.

Also, I know things are moving extremely slow right now and I apologize for that, too. I'm pretty strapped for time right now, plus my kernel-fu is pretty weak, as so far I'm not even finding the ballpark to be in with the native usb tethering (I've found the Wifi one, go figure), not to mention the specific source file(s) I need. I have tons of thoughts, but finding time and a solution are tricky. By no means am I giving up, though, and this isn't a complaint toward anyone, but a complete openness of where I'm at. I still hope to sit down and do some of the fixes and fun plans I have in mind. And I'll still be reading here, and I'll still be responding to scottspa74. ;)