Related
Hey can some post the .apk for iptables unzipped please so I can install it and get my wifi tethering program working please?
Thanks
Well I got iptables installed but none of the tethering programs work currently.
Anybody been able to get tethering working with haykuros builds?
As far as i can tell Wifi Tether for Root Users work but on first run it showed an error messaging saying that my g1 doesnt have root which it does and gives the choice of wether to override the error or not. The files installed quickly and it started tethering after a while.
WARNING!!!!! your phone msy freeze up when trying to stop the tether and will require removing the battery!
Wifi tether for root users doesn't work for me. The log says iptables or the kernel may need updated.
I've used WiFi Tether and it runs just fine.
http://code.google.com/p/android-wifi-tether/
I've tried an uninstall and reinstall, I still get the error in the log saying iptables can't initializa, iptables who, iptables or kernel may need updated.
What can I be doing wrong? I've only just installed the latest 4.5 today and I did do a wipe before installing.
JaboJG said:
I've tried an uninstall and reinstall, I still get the error in the log saying iptables can't initializa, iptables who, iptables or kernel may need updated.
What can I be doing wrong? I've only just installed the latest 4.5 today and I did do a wipe before installing.
Click to expand...
Click to collapse
I would remove the iptables and other files you copied over manually. Reinstall the wifitether apk and you should be gold. The wifitether apk actually installs the necessary files for you. I didn't have problems updating when I went from the 'manual tether' to this app, but I get lucky like that.
Didn't work for me. Removed the iptables, reinstalled wifi tether, numerous reboots, no joy.
Still have the same error. Wifi tether for root users was the program I tried to use before messing around with iptables. Worked fine for me with jf's roms but no joy today with haykuro 4.5.
Any suggestions?
I too have tried every tether app there is and still haven't had any luck.
Good to know I'm not the only one.
Just a thought, the apps wouldn't require busybox to be installed would they?
I've been having the same issues.
I'm having the same problem. If i fastboot and flash my nandroid backup of jf1.41 it works fine. When I updated to 4.5 it stopped working. I am running my apps off of sd. I uninstalled and downloaded it again to reinstall and i keep getting the iptable error in the log too.
thugplayer said:
I'm having the same problem. If i fastboot and flash my nandroid backup of jf1.41 it works fine. When I updated to 4.5 it stopped working. I am running my apps off of sd. I uninstalled and downloaded it again to reinstall and i keep getting the iptable error in the log too.
Click to expand...
Click to collapse
Now that I think of it, I haven't tested the wifi tether in 4.5. I remember it ran no problem with 4.9. I just relinked my sd card for apps and am rebooting. I'll test when it gets back up.
Edit1: arrg, I don't know what I'm running anymore. I guess i'm running 4.5 w/o sdcard cause i created a loop when i relinked my sdcard. Fixing and I'll get back.
I just noticed my 4.5 doesnt have superuser so i opened up droidsans tweak tools and tried to reboot with that to see if my root was working. When i hit the reboot button in droidsans nothing happens either. I am going to try the junefabrics tethering app which doesnt require root and see what happens.
I am on 4.5 and none of the tether apps I tried work. I tried tetherblu, tetherwifi, wifi-tether, anetshare and one more. They all seem to work, but no internet connection once the computer connects to it. I also get the error stated before about updating kernel. Also, I am on the apps-to-sd kernel before the camera-headphones kernel fix so this might be related.
** WOO HOO ** 300th post. I bet at least 3 of them were good posts too!
Damn I hope we can figure this out soon cause my phone is my only net connection for now!
I'm on the 4.5 with camera and audio fix build.
I'm on 4.5 with apps to SD card, and the only tethering app I could get to work was PDAnet. I couldn't get wifi tether to work (got the same error as others about iptables or kernel needs to be upgraded) and Azilink wouldn't work either. However, PDAnet worked great AND it was the easiest to install and set up.
Cool I'll give it a try. How can I download the setup program with my phone?
Does wget work in android?
Cool I can get wget to work through busybox. Could somebody post the download link for pdanet?
would have just asked in :
http://forum.xda-developers.com/showthread.php?t=1142872&page=67
but i don't have enough posts, and don't want to spam a bunch of useless "cool" posts to get my count up.
Anyways,I did every thing in that topic and have CM7 running fine on my Cell South Showcase. But, i don't seem to have root access superuser is there but seems to do nothing. i tried checking via the terminal with just a "su" command and got nothing. Tried Superoneclick (my go to rooter for awhile) and it just hangs at "looking for device" . and, Z4 seems to not work with 2.3.4 phones.
So is there any fix to this, or have i just hit some crazy bug?
I have seen some people allude to changing the kernel, but the last time i tried to upgrade/change the kernel on this phone i had to save it via odin
Don't you HAVE to be rooted in order to run cm7?
i know, it breaks all logic
i just know i cant grant superuser to anything, busybox installer says it isnt rooted, and Titanium cant do anything
thenumber5 said:
i know, it breaks all logic
i just know i cant grant superuser to anything, busybox installer says it isnt rooted, and Titanium cant do anything
Click to expand...
Click to collapse
Clear data on superuser app and/or uninstall/reinstall it.
Ah,I see.. yes, try above. If no. Maybe wipe and reflash?
ok cleared the data, did nothing
can you ever uninstall/reinstall superuser?
thenumber5 said:
ok cleared the data, did nothing
can you ever uninstall/reinstall superuser?
Click to expand...
Click to collapse
Yup just an app
Also:
i have already flashed via Odin back to stock once and did the whole CM7 flash again from a fully clean rom
ok, Flashed Superuser 3.0 beta 3
no go, says my SU binary is out of date, and the app crashes when it tries to update it
checked my bin and xbin, both have a "SU" file in them
in terminal when i CD in to both folders and try to run "SU" i get an error that looks like it is trying to relocate a library and failing to do so
Can i just download the new SU binary my self and manual drop it in to the folders?
well that didnt work, cant modify anything in the system folder so i cant delete that old "SU" and replace it with the one from the superuser 3.0 apk
LOL
well i got it to let me replace the SU in /bin but not in /xbin
so now i got some half confused phone, i can grate Superuser "superuser" but when it tries to update or do any thing the log says "gaining root access....fail"
i still dont know how i have have a CM7 phone that by it very nature is rooted that thinks it is not rooted
ok for anyone who cares, i just gave up flashed via odin back to stock and tried the MIUI port, worked great once i fangled MMS in to working again
I had a similar problem, at which point I grabbed stericson's busybox app from the market which allowed me to flash a working busybox which after a reboot or two and running the installer again fixed me up..there is an app called root checker that can give info on su, superuser.apk, and busybox installs
I am almost positive that when I used jrummys busybox installer our killed root access on my phone. I had superuser.apk but without busybox it was rather useless as no apps could get root. the fix was flashing busybox 1.19.0 and leaving it in xbin and letting the app do its thing once I had rebooted.. then I rebooted again and everything was fine! after bring rooted for so long I don't think I could function without it!
for others out there, my experience has been this: stay weary of the jrummy busybox installer...its never given me anything but problems...and honestly unless busybox is borked, or ya have a damn good reason to upgrade or downgrade my suggestion is to leave it! the potential problems that can arise (for me every time, using jrummy's version..3 times) can be a pain!
Sent from my SCH-I500 using XDA Premium App
i had the same issue but dont recall if it was CM7 that did it or not but i think it was.
i had to completely blow out the phone and start from scratch.
if i recall, CM7 uses a different version of SuperUser and it just want bonkers on me but completely blowing everything out reformatting and everything seemed to work.
If you're on CM7 already, you should be rooted. If not, try SuperOneClick (Google).
Alright I checked all the threads I thought that would pertain to my problem but no such luck so here goes,
-Rooted Samsung Droid Charge running GummyCharged 1.91
-I was following this guide http://forum.xda-developers.com/showthread.php?t=991276 and got to the part where I install busybox on my phone. Busybox was installing fine when at 4% I realized it was downloading off of 3G while I was in my basement so I turned on the phones wifi, busybox then stopped downloading completely and just froze. So I went into the task manager and force closed it, cleared the data, and cache (probably stupid of me) and tried to isntall it again. This time and everytime all Busybox says is "Error: Root Access" "Your phone must be rooted to install busybox". Busybox has SU permissions.
I dont know what to do. I just want to follow the directions on that list to install those scripts.
How can I uninstall busybox or undo what Ive done and reinstall it from scratch?
Pssssst. Hey! Hey you! Yeah, you! Check this thread.
I got my HTC One X about a week ago now for AT&T. Almost immediately, I tried rooting but ran into an odd issue.
Before rooting I had installed Apex launcher. There is an option in the settings to enable Root Helper, which previously would give an error message of something like, "This device does not have root access"
I went through the rooting procedure as detailed here on my mac. The script didn't work at first until I realized I had to switch it to Unix from DOS (Didn't look at the script before running) after I fixed it, it ran and rebooted twice and everything looked normal. Now I tried using the apex root abilities and it just froze and crashed.
So I booted up windows and tried using that to root, but the exact same thing happened. It seems to recognize my root, but not actually give any permissions.
I've tried using other root apps such as uninstallers,titanium backup, etc and all of them just freeze when trying to get elevated permissions.
Is there something wrong with my phone or the way I did the root?
Have you tried clicking on the su app? I had to upgrade mine.
Sent from my HTC One XL using XDA
Yea load up the Su app and ugrade binaries. That should fix the issue. Ive had issues like this on other phones.
You could also try running paulobrien's root method. That's what I used, and my phone's good.
jason.hamilton said:
Yea load up the Su app and ugrade binaries. That should fix the issue. Ive had issues like this on other phones.
Click to expand...
Click to collapse
I've also had a situation where the Busybox version installed on a custom ROM on my HTC Flyer tablet interfered with some apps (like Titanium). Make sure Busybox is up to date. I even had to install a different Busybox installer in order to get it to work right on my Flyer in that particular instance. I had to use the JRUMMY16 version in the market, and not the Stericson installer (which seem the most popular).
No packages were installed with the root.
I'll try using paulobrien's method later and hopefully that will work.
Hey guys and gals,
I've got a 7.7 on stock ROM rooted using the original root method the day I purchased the tablet. I've been using my tablet happily for over a month now.
Unfortunately, late last night I opened up Google Play and started updating all my apps, including Busybox by stericson. There was a new busybox version out (1.20.1) and I decided to install it using "Smart install." I'm not sure if it tried to install to /system/bin or /system/xbin but after the install I saw the app give me an error message explaining that the install was unsuccessful. Anyways, now a lot of my root-requiring apps including Titanium Backup Pro is not functioning at all. It seems that my BusyBox installation is corrupt.
I tried using BusyBox Pro by stericson to uninstall but the corrupt busybox seems to have prevented a proper uninstall, so it still lingers. I downloaded JadeEyedWolf's root.zip from his pinned "Root" post which includes SU & BusyBox thinking that installing the root.zip from CWM Recovery would over-write the corrupt busybox. After flashing I rebooted the tablet and I still got the same corrupt busybox issues.
Anyone have any suggestions?
Thanks!
Edit: The corrupt busybox causes the Wifi to show Error when I try to turn on the radio. Not that internet is vital in repairing the tablet, but I've worked around it by tethering Bluetooth internet off of my OG HTC Evo 4G. It's strange though - I can peruse websites and view the items in the Google Play Store but it will never actually download, though the "Downloading --- " bar does display.
I had the same problem, stock rom as well. If you check the reviews for Stericson's Busybox on Google Play, the two top ones a few minutes ago both mentioned the same issue.
Trying to root again and reinstalling Superuser didn't help, neither did a factory reset (manually salvaging settings and data was a pain too).
Re-flashing the original rom fixed it, following the guide at http://forum.xda-developers.com/showthread.php?t=1469635
I switched to JRummy16 Busybox installer and it seems to work.
Surprising that no one else here mentioned the problem ...
Try this fix.
To be more specific: BusyBox installer 8.0 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Installer 8.1 and above has this bug fixed.
Had the same problem with busybox and had to re-install the rom. What does this fix do?
Sent from my GT-P6800 using xda premium
Already answered, see post above.
Deleted
Sent from my GT-P6800 using xda premium
Too late for me to try it, but thanks the same
ginkage said:
To be more specific: BusyBox installer 1.20.1 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Click to expand...
Click to collapse
Thank you so much it works well now! You're a life-saver ginkage. Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Thanks again!
Thank you so much it works well now!
Click to expand...
Click to collapse
That's why we are here.
Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Click to expand...
Click to collapse
Personally I always use /system/xbin, so that some custom kernel (like CWM) could use /system/bin if it wanted to.
BTW, the BusyBox installer bug was fixed in version 8.1, and current version is 8.2, so you should update it anyway. I was wrong to mention "1.20.1" version. Post edited.
Hi guys,
First of all, I want to apologize sincerely for the bug that my application introduced in 8.0. I didn't catch the bug because my device wasn't affected by the bug.. (I always test my app myself before releasing..yet I still miss things due to devices file structure being so different.)
At any rate, the bug was that the application symlinked all applets to Busybox. Normally, this is done if you use smart install and change the settings manually. By default smart install will not overwrite applets that are not already symlinked to Busybox.
This was not a problem with Busybox 1.20.1 but was a problem with my application and how it performed the install.
Again, I am very very sorry that this has occured, as a result I am scouring the web trying to find people with the issue and help them resolve it.
If you have this problem, it can easily be fixed by reflashing your current rom. you do not have to wipe or clear any data. Once this is done, you can download my installer, version 8.1 or greater and upgrade busybox as normal.
Please let me know if you guys have any questions.
Best Regards,
Stephen - Stericson
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Deleted
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
ninpo said:
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
Click to expand...
Click to collapse
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
regius said:
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
Click to expand...
Click to collapse
A thousand thanks kind sir, I'm back in business, that was pain free
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thanks for posting this, I'm in love with my 7.7 once again.
Appreciate the response stericson. I had purchased your Pro version but even after I fixed the uninstall failed and it also did not detect superuser permissions even though SU gave a notification that Busybox Pro was granted superuser. All other root-requiring apps work. Had to refund the Pro purchase though
No problem. there seems to be an issue with the application detecting root sometimes, that's why you can still try the install.
I'm looking into this issue, it just started showing up so I am not sure what is going on.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Really appreciate this fix. On the verge of wiping out everything....
But decide to see if its busy box since its the last thing i install before all this happens....
Just to note that uninstall busybox also doesnt solve the issue...
so need to fix.
I had a lot of problems with root permissions not being granted by Superuser app. Recently I have tried SuperSu from the market and uninstalled original Superuser app (important to follow the instructions for the App! ).
My main problem was that ntfssd was not granted root permissions at startup, so I had to start it again manually. With SuperSu it is no problem. Also I use Busybox and successfully updated to the latest binary recently.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thank you so much for that, I had been driven crazy and had also gone through a factory reset to try and get my device back working, to no avail. Can I ask where you got the ash you're including here? It worked for my Samsung Galaxy Tab 7 Plus, on 3.2, but is it a generic enough file that it can be dropped on nearly all Android devices without any issues arising?
I only ask out of curiosity and understanding the system more.