yashsingh1/xdaforums huggingface dataset:
[EVO 4G Themes and Apps] scottspa74:
If someone kinda sorta flashed the wired tether fix zip (by Davidlightle) twice, -one for one ROM, and one already was set and working on my everyday ROM that I just nanded back to- that shouldn't hurt anything, right?
[EVO 4G Themes and Apps] davidlightle:
I think I get what you're asking, but I may be wrong. On that note, I don't think there is any issue with what you're saying/asking.
[EVO 4G Themes and Apps] scottspa74:
Hahahaha, yeah. Thanks for tryin to make sense of my boozy gibberish

I know I wasn't clear. I'll take a sober stab at it:

My everyday Rom is a stock root Evo ROM with netarchy kernel 4.1.9, and I had already flashed the wired tether fix and had tether working flawlessly.

Then I flashed Fresh ROM. Tether wouldn't work. So flashed the tether fix zip you made (would a flashed fix zip stick between nandroids, does anything stick between nandroids? Meaning, if I flash something on a ROM I'm playing with, then nand back to my everyday ROM, will somethin I flashed or changed carry over when I nand back? This illustrates my fundamental ignorance of Android)

Anyhow, in Freshs ROM, I flashed the fix, cuz tether wasn't working, then I so played with the libnativetasks thru root explorer, still nogo.

So , I flashed the fix on my everyday ROM, AND on fresh ROM. Is that like flashing it twice (if so, is that bad?) Or are two separate ROMs (each with a nand backup made of it) completely isolated from each other, or do some changes stick and carry over between nand backups/restores ? Thank you much for shedding some light on this for me. Hopefully I am clearer this time.

My coworker just got an incredible, and I'm searching to find if anyone got this working on incredible. Thank you for everything.
[EVO 4G Themes and Apps] scottspa74:
Man, I cannot get this working on Fresh ROM no matter what. I don't know what I'm missing.

Force Close immediately every time.

I tried it with Freshs native kernel. I just flashed netarchys 4.1.9 kernel (which is what I use on my everyday stock ROM) still force close on fresh. I flashed the wired tether fix zip. NoGo. I used root explorer to rename .bak to the libnativetask.so in dada/data/android tether/lib. Still force close immediately.

I don't know what I've missed. I do like fresh ROM, and tethering was the main reason I went root. I wish I could figure it out for this ROM. If anybody knows what I'm missing, it'd be much appreciated. Thanks in advance, and much thanks to Davidlightle and Josh_H.

Scott
[EVO 4G Themes and Apps] davidlightle:
Okay, I'll try to give a quick summary that I hope helps. A ROM is basically (not always?) a "full install" of your system partition (system being system apps and system functionality, etc.; data partition is where your market-installed apps go; sdcard is a separate mount, to treat it like a "drive" on the phone).

So, if that's not clear, I'll try to explain a tiny bit further (trying to not make it confusing). With your "good" ROM, when you flashed Fresh over it, that should've been a clean slate, "new install" basically. So you would actually need to do the [my] tether fix again actually. In addition, with Fresh, since they incorporate Wifi Tether for root users, they include the libnativetask.so; but since they don't create anything on the data partition (where installed apps normally go after initially setup [like stock or custom ROM installed]), they put it in that /system/lib folder. This is to make Wifi tether work. If you install Wired tether, it comes with its own (as would Wifi tether if you reinstall it); so then it's ambiguous which one to use (even though they're the same). This is why it's a bad approach really with how it is handled (not sure where the blame falls). So the best idea here is to remove Fresh's installation of Wifi tether, remove /system/lib/libnativetask.so and then install Wifi tether and Wired tether from the market/google code. This way they have everything they need like normal.

Okay, that wasn't as short a description as I meant to give. In short, ROM installs are fairly "clean" and so you need to apply things to them again (if it applied to the "system" partition -- my Wired tether fix does). You may have to, too, if it applied to the data partition and you had to do a "factory reset". A nandroid will save your system and data partitions, so when you restore a nandroid backup, you won't need to reapply the fix then, though, if you'd done it before.

So, for your specific case, when you flash Fresh, you can try renaming the /system/lib/libnativetask.so to /system/lib/libnativetask.so.bak, maybe restart to be safe, and then try installing Wired tether. My preferred approach, though, would be as I mentioned above (remove Wifi tether and the /system/lib/libnativetask.so, reboot, install Wifi and Wired tether). And then apply my fix for the ip symlink/binary and give it a shot.

If you go back to your main ROM, you should be good to go straight after the backup, no extra work needed; if you get Fresh working after this and nandroid backup it, same thing, shouldn't need to repeat this from a backup, only if you do a new custom ROM install.

If you're still having problems, you might shoot me a PM and I'll see how I can help you better.
[EVO 4G Themes and Apps] saturatedfat:
The above post fixes the issue on the new bakedsnacks 1.7 rom as well.
[EVO 4G Themes and Apps] scottspa74:
@ Davidlightle

Your post was appreciated. after reading it, I went back to root explorer and somehow hgot it working. Thank you mass. I wish all threads had this level of support. Thanks so much man.

To clarify the fix , I used root explorer and renamed the libnativetask in sys, not data, then uninstalled, then reinstalled 1.4 . I thought I already managed that, but guess not. Fixed now. Oh, and I did reflash the fix zip.

Originally, I tried renaming the libnativetask in data/data. That didn't work for me, so I removed .bak from that, then renamed the libnativetask in system/lib. Bingo. That worked.

Davidlightle, for the millionth time, thank you. You the man.
[EVO 4G Themes and Apps] islandreamer:
Thanks David and Josh for your work!! Following your instructions, Josh's zip for the FCs and David's zip for the unable to tether. It seems to work correctly on my phone but can't fully test on my Mac. Even if I go the windows side it still uses Mac's airport utility for the built in Ethernet card. Last I read this app does not work with Mac just windows. I have to use windows machine for work sometimes so the app will come in handy. Do you know if it will support Mac sometime in the future?
[EVO 4G Themes and Apps] nucher:
Thanks Davidlightle, I have a Fresh 3.2.0.0 and couldn't get wired tether to work. I used a terminal with SU permissions(type SU in terminal) and navigated to /system/lib/libnative.so (cd /system/lib) and deleted the libnativetask.so "rm libnative.so" Rebooted and installed the wired tether 1.4 and it works. Thanks and I hope my post at least guides other noobs on how to get there EVO tethered.
[EVO 4G Themes and Apps] Josh H.:
Glad you got it working!

As far as Mac functionality, I don't see that coming anytime soon. The only reason it works on windows is because windows has the proper drivers (written by HTC if I remember correctly) for android-specific USB tethering. No such drivers exist for the Mac, so it's kind of out of the hands of the wired tether people until a proper Mac driver exists.
[EVO 4G Themes and Apps] islandreamer:
It treats it as a modem and requires a number, user name and password with a wired connection. As a wireless it just sees it as a network and connects that way. If I have to use it for long periods of time I just plug it in so I am charging through the usb and working wireless. I know with my Crackberry it was always a little quicker on a wired connection vs a wireless. THANKS for all of your hard work in really is appreciated on these forums!!!!
[EVO 4G Themes and Apps] saturatedfat:
Anyone know if there is a widget or an app that will automatically enable this when the phone is plugged in?

Thanks in advance!
[EVO 4G Themes and Apps] govno64:
This fix breaks 4g

Hey David and Josh, I applied both fixes for the Wired Tether app, and I can confirm that while the fix does work for 3g tethering, this somehow breaks the 4g abilities of the phone. I nandroided before and after to test it and, sure enough, after reverting, 4g works again.

Thanks for all your hard work and help here in the forums.
[EVO 4G Themes and Apps] akastixx:
Uninstall Wired and Wireless Tether, then......

Worked for me too. Now running Wired 1.4 on Baked Snack 1.7. THANKS.
[EVO 4G Themes and Apps] Razgriz:
Anyone else having the slow connection speed while tethering? I'm only getting about 40Kb/s max.
[EVO 4G Themes and Apps] LAYGO:
Didn't see your response until now (DEEERP!).

I still can NOT route when connected to 4G. The only two things I've changed since it last worked is the wired tether fix and tried getting updated PRI via ##3282# & MSL. I got an updated PRL (60670), but not PRI. 20 times trying that & still can't get updated PRI.

I flashed, then 12-16hrs later I tried the ##3282#, but didn't try connecting to 4G between then, so I can't be explicitly sure what might've caused it! :( I don't have 4G at home, but can get it at work only on top of the parking garage. 99% of the time, I'm not using 4G, but can't use it now if I tried! :(

When I load a page, it just gives me like a 404 error. Turn off 4G, immediately connects.
[EVO 4G Themes and Apps] toochevere:
I was also getting slow connection speed (about 40k) when using WiFi Tether with 3g. It appeared to be because the processor was throttled. I was using SetCPU on the conservative governor with aggressive power saving settings. When I switched it to the Performance governor and full (overclocked) speed, it went up to 1.1Mbps. I'm on BakedSnack 1.7 with the default #6 kernel.
[EVO 4G Themes and Apps] davidlightle:
Hmmm. I am still pretty sure at least one person, if not more, said they were on 4G and tethering both, so not sure what the differences are yet. I just posted an update on the issue tracker for issue 24 that I'll repeat here a bit. I'm going to try and compile a list of working and not-working users, ROMs, and kernels to try and see who needs help, what help is needed, and if there is anything in common with the ROMs and kernels that is causing any of the troubles.

I don't have 4G anywhere even close to where I am, so testing for it and fixing/working with it is going to be very difficult. For anyone who did my fix and can't use 4G and would like it back, I can work that up. The current situation for that would be "4G and no tethering, or tethering and no 4G"; I think I can get a small shell script that will allow you to flip back and forth between those two options (but still won't allow tethering and 4G to co-exist at the same time).

I'll try to set some time aside tonight to get some of that out at least.
[EVO 4G Themes and Apps] scottspa74:
Davidlightle,

I don't know if you're soliciting this info, but my 4g doesn't work either. But I don't know at what point I lost it, so I don't know how this helps you any.

After rooting, then flashing a ROM, then more, then using wired tether fix, I now see 4g broke. I always thought it was working though (cuz I didn't go thru the initial unrevoked debacle, I know it worked back then), I've only ever flashed stock rooted ROM (netarchy), and fresh ROM. Anyhow, always thought it worked cuz it will scan, obtain IP address, then say connected to Sprint. Only recently did I try to load a web page (this was after wired tether fix, then libnativetask fix for fresh), and see that I have no real connection. I never suspected it was related to wired tether, and still don't really. But you said you're gonna try to make list, and I wondered if you wanted people to chime in.

Thanks for all your work (I personally never used 4g anyway, too much battery drain)
[EVO 4G Themes and Apps] LAYGO:
If you can get me that script while at work, I can test if that's the fix. I don't have any ability to open a console directly on the phone. I'd need some guidance there, but if you're just talking about a .BAT or something, ignore! ;)

As it stands for me, I wouldn't be tethering and 4G at the same time because I don't have 4G at home. I don't have net at home, hence why I'm tethering, but my 12mb down UVerse is set to go active on the 22nd.

Couldn't the tether apps be configured to point to a local symlink that points the busy/local box that wouldn't affect the system wide access to the IP binary?
[EVO 4G Themes and Apps] BrianBusby2038:
My 4g still works fine.Running Fresh 3.1.0.1 and Netarchy 4.1.8 bfs.Wired and Wireless Tether are both working great on 3g and WiFi,my 4g coverage is pretty spotty so haven't tried to tether via 4g yet.
[EVO 4G Themes and Apps] davidlightle:
Well, here are a couple of different update.zip fixes. I'm still trying to fully understand what all is happening but I'm really stretching to try to understand things that are happening at the kernel level.

Anyway, the first zip, named SignedWiredTetherRestore.zip is the opposite of my previous fix, which will restore the original ip binary to the one that came with stock FroYo. Basically it should remove your current /system/bin/ip (which, if you ran my previous fix, would be a symlink to toolbox) and then copies in the original binary and fixes up the permissions. This is useful for those people who want to restore back from my previous fix, in order to fix 4G.

Also, I have another zip, named SignedWiredTetherFixToggle.zip that removes the current /system/bin/ip (the binary or the symlink), copies in the original ip binary but named ip.bak (/system/bin/ip.bak), creates a symlink pointing to the original ip binary, fixes the permissions, and additionally adds a simple shell script to flip the symlink between the original binary and toolbox, so that you can use 4G or wired tether.

The syntax for the script is /system/bin/tetherFix [on|off].

Let me know if you have any questions or problems and I'll do what I can.

Edit: Removed attachments; see new post.
[EVO 4G Themes and Apps] LAYGO:
Ok, I will try these a little later . . .
[EVO 4G Themes and Apps] scottspa74:
Yeah, I HATE to say it, but it turns out it WAS somehow the wired tether fix that caused 4g to not work. I never thought it was broken cuz I would turn it on and it would say 'connected', but I never went so far as to actually try to use it (only recently actually tried to load a web page, nogo, and now, I just flashed a new rom (and haven't done any wired tether fixes), and suddenly 4g is working again (on phone, but wired tether is not working ) not force close, just says 'unable to tether'. But now 4g works on my phone, which it didn't after fixes.

Not complaining, just wanted to give you feedback.

I never use 4g anyway, too much of a battery hog.

Thanks for your work.

Okay, I'm gonna try to clean up this post so it makes more sense.

A) On previous rom (fresh rom, net/kings kernel,) I had done the wired tether fix zip, and renamed libnativetask to. bak

- wired tether worked (thank you david and Josh), but 4G didn't work (on phone)

B) Just flashed new rom (Virus rom with stock kernel, alt with king kernel). Have NOT done wired tether fix zip. HAVE renamed the system/lib/libnativetask to .bak to eliminate force close.

C) I see now my 4G DOES work again (on phone, obviously). But wired tether just says 'unable to tether'

SO, now I'm. Interested in trying the toggle zip you made, but don't know, do you flash it thru recovery, and then do you get some sort of toggle gui? Or does it just work in the background somehow?

I don't care that much about. 4G (obviously, since it's been broke for a month and I didn't even know ;) ), but I suppose if I had 4G 'available, and ALSO had option to toggle to tether, obviously that'd be ideal)

So, thanks for all your work (for the millionth time), and if you could tell me what to do with, and what to expect from, the toggle zip, it'd be much appreciated.

Thank you all for everything
[EVO 4G Themes and Apps] davidlightle:
No problem! Sorry that I wasn't clearer before. Both files on my last post are signed zip files that can be flashed through recovery. With the toggle, it isn't ideal for a non-technical user. Basically there is a very simple and somewhat crude Linux shell script installed as /system/bin/tetherFix that you would call with a single command line argument of either on or off. On will fix the up symlink to point at toolbox while off will flip it back to the original ip binary.

So this isn't built into the tether app as it is a simple, temporary workaround for now. One way to use it would be to use a terminal app; I have also heard of some other apps that may work well with this but I don't have experience with them (GScript is the one I hear about the most).

I'll try to grab some free time to dig into the kernel and Android source and see if I can't get a better fix in place permanently and built-in.
[EVO 4G Themes and Apps] scottspa74:
Ok. So, to see if I understand you, the toggle zip would require that before running tether, I would need to open (for example) terminal emulator on my phone (which is no biggie, I'm getting fairly accustomed to using that) and entering some command?

Am I understanding correctly? And if so, what would that command be? And lastly, if I flash zip and it effs something up, is there anyway to undo/restore?

Thanks for your reply, and thank you for taking on what must be an incredibly frustrating project due to constant EVOlution and development. I know I'd probably lose my drive.

Anyhow, thanks.
[EVO 4G Themes and Apps] davidlightle:
Yup I think you've got it now. I don't think there would be any problems due to these zips, but to be safe I would recommend making a nandroid backup beforehand (in recovery).

The command to run before tethering would be (without quotes) "/system/bin/tetherFix on". When done it would be "/system/bin/tetherFix off".

On the other half of your message, I actually really enjoy helping but yes the incredible number of variances make things challenging. Plus I'm still learning some things as I go too; my patch to wired tether was something I stumbled into and was in my comfort zone since it was a software development issue, but knowing the inner workings of the Linux kernel is a new (but mostly enjoyable) challenge.

I would love to help even more, but time has been scarce lately as my wife and I are working on our home and other normal personal commitments. But I'm still checking in and will help how I can, but complex research is slower and less frequent for the time being.

Thanks for hanging in there and giving feedback, too, as it definitely helps me improve things.
[EVO 4G Themes and Apps] scottspa74:
Not gonna quote and waste space, but @ davidlightle, thanks a ton. Will give it a whirl. I'll report back.

Thanks for your work. :-)
[EVO 4G Themes and Apps] scottspa74:
Ok, hope I can keep this concise.

On new Rom (virus ROM, super stable ROM), I did not flash the wired tether fix zip. 4G works.

Wired tether just says 'unable to tether' (fixed fc by doin the libnativetask bit thru root explorer)

I flashed the 'wired tether toggle zip', without signed tether fix first, and 4g gets broken.

I tried the commands in terminal emulator app but get the following :

Disabling usb tether fix

rm failed for /system/bin/ip Read-only file system

link failed File exists

2 questions ;

1) do I need to flash the tether fix zip for the toggle zip to work

2) does the text that came back mean my file system is read-only? Is that whew the command of 'mnt -0 dev block blah blah blah ' or whatever it is comes into play? i.e., is there some command I need to make my system read/write with terminal emulator?

Thanks a million (and thanks for putting up with my niggling questions )

Scott
[EVO 4G Themes and Apps] davidlightle:
Ahhh, yes, I probably should've added that into the script as well. I'll fix that here in a bit, silly mistake. I must have already had my system read-write when I tested.

So yes, you'll need to make your /system partition read-write, which on the Evo is usually the command "mount -o remount,rw /dev/block/mtdblock4 /system", before doing my script.

Sorry for all the headaches and hoop jumping.
[EVO 4G Themes and Apps] scottspa74:
Ahhh, no worries at all. I'm sorry, for all my 'special needs' help. All I've got to say is 'thank you', and of course more questions ;)

A few quick, easy questions:

Should I need to flash the signed tether fix zip BEFORE the toggle zip, or does toggle zip contain the previous 'fix" ?

Is that command you wrote, is it all one line?

If you're gonna fix the toggle zip, should I just wait for that? Or is it ok to flash the current toggle, then flash the next one right over it?

Thanks for all your patience.

Scott
[EVO 4G Themes and Apps] davidlightle:
Keeping the thread alive! ;)

You shouldn't need to do the previous signed tether fix of mine with this.

Not sure if you mean the mount command or the actual tetherFix, but each is a one-liner. Until I get the improved, super-duper fix, here's what you would need to do:

Before tethering:

(in a command shell, like terminal emulator, without quotes:)

"mount -o remount,rw /dev/block/mtdblock4 /system" [enter key, and then]

"/system/bin/tetherFix on" [enter key, and then]

"mount -o remount,ro /dev/block/mtdblock4 /system" [enter key]

After tethering/before 4G:

(in a command shell, like terminal emulator, without quotes:)

"mount -o remount,rw /dev/block/mtdblock4 /system" [enter key, and then]

"/system/bin/tetherFix off" [enter key, and then]

"mount -o remount,ro /dev/block/mtdblock4 /system" [enter key]

Well, I may pull down the old version and put up a new, corrected version. I probably should have an "undo" update.zip as well, for those who want to remove the changes if unwanted or for once I get a more long-term fix in place. So much to do!

Anytime!

Edit: Wow, I was not thinking clearly when I typed the commands. I've fixed them now; the process is to make your system read-write, use the toggle, then set it back to read-only.
[EVO 4G Themes and Apps] davidlightle:
Well, here are -- yet again -- a few more flashable, signed zip files. One, SignedWiredTetherFixToggle2.0.zip, is an updated v2.0 to my tether fix toggle, to be called from a terminal. This is separate from/in addition to the toggle of Wired Tether, and is just a temporary, short-term workaround for Evo users who lose 4G due to the change of the ip binary to a symlink to toolbox.

The second, SignedUndoWiredTetherFixToggle.zip, is to revert my toggle patch. Tread with care, but I think things are sound. This should remove the shell script, the ip symlink, the ip.bak, and restore the original ip binary with it's proper name.

The third, SignedWiredTetherRestore.zip, is the Tether Restore from my previous posting, but signed as I said; I realized just now that I said both were signed, yet I accidentally uploaded the unsigned versions. This should be used if my non-toggle WiredTetherFix was applied and you desire to go back to stock in this regard.

Being signed, these should work with Amon Ra as well as Clockwork Mod recoveries. As with any change, I would recommend making a nandroid backup prior.

With this v2.0 toggle, the current state and process should be as follows:

Wired Tether and 4G are somewhat mutually exclusive still (one or the other but not both at the same time); some people report working 4G with wired tethering, but I'm trying to isolate and identify how to make this stable and reliable.

Prior to using wired tether, execute the following command in a terminal (without quotes):

"/system/bin/tetherFix on"

This may disable 4G while the fix is active. After running the command, you should be able to use the Wired Tether application as expected.

After finished with wired tether, execute the following command in a terminal (without quotes):

"/system/bin/tetherFix off"

This should re-enable 4G but most likely will kill Wired Tethering, so please have it disabled prior to this.

Edit: Removed tether toggle for now.