I apologize in advance if this subject is posted elsewhere. Please kindly point me to the thread...
I'm a noob and just bought a viewsonic G-tablet.
I've been searching xda for a day now, and I cannot find a how-to guide on how to make the "adhoc wifi hack" to work on the stock ROM.
I've found this:
http://forum.xda-developers.com/showthread.php?t=754961
But I can't find a definitive answer on how to "flash this in recovery mode" specifically on the G-tab.
I'm assuming to proceed to installing ClockworkMod from (http://forum.xda-developers.com/showthread.php?t=865245)
and then flashing the "adhoc-signed zip file" from there.
I realize ClockworkMod is used to flash ROM's, so I'm wondering if this "adhoc patch" file can be flashed the same way without affecting the stock ROM.
Please let me know if this is the correct path to go down.
Thanks for your help in advance.
what is that
There is an easier solution. Search for the stock enhancement pack in the development forum. You will have to flash the file in CWM or with standard recovery. Instructions are in the post.
Enjoy your AdHoc goodnes.
Okay, I answered my own question, but now have more problems to deal with.
I installed the "adhoc signed zipped" file with CWM. I created a new folder in the gtab root and put the "adhoc signed zipped" file in there. In CWM's menu, there is a selection to install zip/flash from an internal folder.
okay, got adhoc to work. When scanning for networks, the adhoc networks show up with the * as expected. I connected successfully to my wm6.1 phone with wmwifirouter.
However, the gtab cannot load up websites. I do see spurts of data on the phone being passed, but it seems to be spurts and it stops. Browser on gtab say check connection.
So I'm thinking that this has something to do with the adhoc hack on the stock rom. I'm going to bite the bullet and try a non-stock ROM to see if this will resolve the problem.
@jasco: I cannot find the stock enhancement pack in searching... I might need to search harder.
Flashed this to my Gtab to test it out. Completely broke my wifi. No longer will see any wifi or adhoc networks. I had to reflash.
I don't have a phone that I can tether to, but my son does, and I just got this working w his phone.
What I did was:
- unzipped the file from that thread above, and got the wpa_supplicant file from the system/bin dir inside the unzipped dir
- turned off wifi
- used z4root to get temporary root and root explorer to make /system R/W
- used terminal to copy the new wpa_supplicant file to /system/bin
- changed permissions of /system/bin/wpa_supplicant to rwxr-xr-x
- turned wifi on
I was then able to see his SSID, and connect using WEP.
Jim
I would like to try this with my tablet and I am having a hard time understanding these instructions. can you please make a detailed set of instructions with more steps? If you would do this I am sure there would be a lot of people that would be truly grateful, I being one of them.
Thanks,
Waspvl1
All depends....
What if you don't have an Android phone?
I use WM 6.5 phone (in my case HD2) to tether to my G-tab.
Using program WMWiFiRouter. G-tab picks it up as another regular router.
Never had a problem and most important for me, don't have to go through all of the trouble configuring AdHoc.
JMO.
here is an easier method a version of the adhoc from froyo modified to support adhoc.. i was using it on my galaxy s.. now using it on the gtab works fine..
1. you need to be rooted.
2. use rootexplorer
3. turn off wifi
4. back up the existing file in /system/bin to somewhre on your sd or sd2 card.
5. using root explorer copy this file over the one in /system/bin
make sure to put /system in read/write mode (top of root explorer when in that directory) (also need to unzip it first)
I just updated my rooted tether on my droid x and now it works. Gtab sees my adhok without the zip.
yelrx8 said:
Okay, I answered my own question, but now have more problems to deal with.
I installed the "adhoc signed zipped" file with CWM. I created a new folder in the gtab root and put the "adhoc signed zipped" file in there. In CWM's menu, there is a selection to install zip/flash from an internal folder.
okay, got adhoc to work. When scanning for networks, the adhoc networks show up with the * as expected. I connected successfully to my wm6.1 phone with wmwifirouter.
However, the gtab cannot load up websites. I do see spurts of data on the phone being passed, but it seems to be spurts and it stops. Browser on gtab say check connection.
So I'm thinking that this has something to do with the adhoc hack on the stock rom. I'm going to bite the bullet and try a non-stock ROM to see if this will resolve the problem.
@jasco: I cannot find the stock enhancement pack in searching... I might need to search harder.
Click to expand...
Click to collapse
Have exactly the same problem. Been looking for a solution for quite a while. Can't understand why this should be so difficult.
I went another route, but with the same problem.
I thought the "ad-hoc signed zipped" file install from CWM as I've described about was the issue, so I went back to the stock 3389 ROM with the tnt enhancement pack.
Exact same issue, the ad-hoc connection with WMwifirouter is connected, but no internet data will pass on the connection.
Tethering without root?
I'm definitely a noob to all this, although I have had an android phone for about 6 months now. I haven't found any roms to flash to my samsung transform so I haven't gotten root on it yet. Is there a way to tether to my g-tab (Vegan 7) with out gaining root to my phone? By the way, I really like the new rom.
I'm running a wireless tether app on my rooted Droid X and can connect my gTab to it without any updates or hacks or anything else. I'm running stock VEGAn 5.1.1 without any other tweaks.
I'll flash back to VEGAn 5.1.1 and see if tethering works with out having to hack my phone.
rosscopicoterry said:
I'll flash back to VEGAn 5.1.1 and see if tethering works with out having to hack my phone.
Click to expand...
Click to collapse
FWIW, I'm running this ROM and just tried it. It connected fine to my iPhone w/MyWi. No hacking required.
No adhoc transfers with Vegan-Tab Ginger RC1
I've flashed this ROM 5 times now and ran some tests each time. I can connect to my WMWifirouter adhoc network, get an IP, but there is nothing going through...
My understanding is that this rom already has a hacked supplicant. What's my next step? Should I bother trying with the provided wpasupladhoc.6.1.zip above? Thanks in advance.
I cannot figure this thing out for the life of me. Has anyone gone the route of trying to use blutooth to connect from their android phone to the g-tab? I can get it to pair but not connect. G-tab may have to go back if I can't figure this out.
1.2-4349 Ad Hoc tether
lgkahn said:
here is an easier method a version of the adhoc from froyo modified to support adhoc.. i was using it on my galaxy s.. now using it on the gtab works fine..
1. you need to be rooted.
2. use rootexplorer
3. turn off wifi
4. back up the existing file in /system/bin to somewhre on your sd or sd2 card.
5. using root explorer copy this file over the one in /system/bin
make sure to put /system in read/write mode (top of root explorer when in that directory) (also need to unzip it first)
Click to expand...
Click to collapse
Tried it on 1.2-4349 and it appears to work just fine. Immediately detected ad hoc tether on my original Droid running gingerbread.
Does the phone need to be rooted? Or are you putting these files on the g tab?
Hi all, I'm sorry if I posted this in the wrong place.
I have an Archos 32 and I have an ad-hoc wireless network at my home. I've been trying to get my Archos 32 to connect to it and the only way that I have done so is through UrukDroid 1.0. UrukDroid however won't allow me to run some applications such as Camera and WeatherBug that I really would like to be able to run (they just crash). So I downloaded the GPL Source Code from Archos and made the changes to the wpa_supplicant source code via the patch that is found online. I've followed the guide on CNXSoft (can't post the link) for compiling the entire source on Ubuntu 10.10 (although I'm running 11.04). I have successfully created a zImage and a cramfs file, as well as a squashfs file. What do I do now? Are there any more steps that I need to do as far as installing it on my device? I've searched high and low and can't find anything so I figured I would post here. If someone could help me I'd appreciate it.
Lol I can't believe this is such a hard question that nobody knows how to answer it.
Anyway, I got it sorted, sorta. With wifi on the device turned off, I deleted the wpa_supplicant.conf from /data/misc/wifi, and changed the WifiAdhoc value to 1 in /data/misc/wifi/tiwlan.ini, then pushed it over, as well as a patched wpa_supplicant file via ADB over to the device. Now I can connect to my adhoc network on 2.3.26, and still have WeatherBug and the Camera and all the other apps that crashed on UrukDroid. The only drawback is that the wpa_supplicant file gets replaced with the original one everytime I reboot the device. Not sure how to avoid that. So everytime I reboot the device I have to copy the patched wpa_supplicant file again. But other than that it works great.
Anyway thanks for reading.
Long story short, I tinkered to much and was completely stupid and forgot to make a back up of my original wpa_supplicant file when I was attempting to get ad-hoc to work correctly. Now for the life of me I can not get the wifi on the device to even turn on. I have tried multiple wpa_supplicant files that claim they were supposed to be compatible with android 4.0.4. I have succesfully rooted the device (obviously had to be rooted to replace the file I lost) All in all this really isn't a horrible device for the price and really want to get the wifi on the device working again.
Does anyone have a stock wpa_supplicant file for android 4.0.4 that will work with my device, or does anyone have any helpful tips?
I would greatly appreciate anyones help. I could care less about ad-hoc now and just want my wifi to work. lol
Oh and yes I did set the correct permissions on the files I have attempted use in root explorer.
nkemm2 said:
Long story short, I tinkered to much and was completely stupid and forgot to make a back up of my original wpa_supplicant file when I was attempting to get ad-hoc to work correctly. Now for the life of me I can not get the wifi on the device to even turn on. I have tried multiple wpa_supplicant files that claim they were supposed to be compatible with android 4.0.4. I have succesfully rooted the device (obviously had to be rooted to replace the file I lost) All in all this really isn't a horrible device for the price and really want to get the wifi on the device working again.
Does anyone have a stock wpa_supplicant file for android 4.0.4 that will work with my device, or does anyone have any helpful tips?
I would greatly appreciate anyones help. I could care less about ad-hoc now and just want my wifi to work. lol
Oh and yes I did set the correct permissions on the files I have attempted use in root explorer.
Click to expand...
Click to collapse
Just for clarification purposes I have the device they are referring to in this thread: http://forum.xda-developers.com/showthread.php?t=1954572
Beyond a working wpa supplicant file I guess another option for my device would be flashing a rom onto it but I haven't been able to find any solid information on this. I'm assuming time will tell, eventually someone will figure something out with this device.
Hello,
I have a Dell Venue 8 that is not able to save/remember wifi passwords after a device reboot. I've tried looking into the built.prop file for ro.securestorage.support=true and this line does not exist in that file. I've also read about google backups being potentially the cause, and I've disabled this but the issue remains.
Turning off/on wifi, the wifi is able to immediately reconnect. But the only problem is when the device itself reboots. I've tried looking all over for some sort of "Save" feature when connecting to the wifi network. It does not appear anywhere.
Has anyone else experienced this? Any help is appreciated.
Bump. Can anyone help?
Do you have root? If so, you could see if the networks are being stored in the file:
/data/misc/wifi/wpa_supplicant.conf
If they are, there's no reason they should disappear, I would think, unless as you mentioned, some Google backup process is overwriting it.
xBIGREDDx said:
Do you have root? If so, you could see if the networks are being stored in the file:
/data/misc/wifi/wpa_supplicant.conf
If they are, there's no reason they should disappear, I would think, unless as you mentioned, some Google backup process is overwriting it.
Click to expand...
Click to collapse
No, I do not have root. I am not able to find this file when connecting the tablet via usb to my computer either.
I recommend rooting your device, it took me maybe 10 minutes at most. Backup your data just in case! I didn't loose any files when I rooted, I followed this guide. After you root, download a file explorer and go to /data/misc/wifi and backup then delete wpa_supplicant.conf and do the same with the dhcp folder in /data/misc. I was having the same issues until I did that.
I know this is an old thread, but I just want to let you know my Venue 8 had the same problem and I was able to resolve it by doing a factory reset in the built-in recovery mode.
I would like to patch wpa_supplicant on my Beelink W95 that is susceptible to the KRACK WPA2 WiFi exploit.
I tested the W95 with vanhoefm/krackattacks-scripts (look on github, can't post links) and it failed the first test. I would like to patch wpa_supplicant so I can proceed with the other tests.. Except I'm not sure how to do this.
I've compiled programs for Linux and I've used Android studio. I'm really not sure how to cross compile from Linux to android and I don't think I need the full blown Android studio experience.
Are there any good guides to compiling just individual command line programs. I know I'd have to get the source, then do .configure then make, what I'd like some clarity on is if I need specific source from the device manufacturer or can I just use vanilla android code. Further, what options does make take, and basically what do I need to know so I can just compile wpa_supplicant with the patches I need to apply.
Thank you
Progress...
I decided that the first step should be to compile a generic wpa_supplicant and not worry about patches or security updates or anything like that. In order to do that, I had to compile openssl and libnl libraries. I went through a lot of versions of all three because I would always run into some problem or another. After a lot of trial and error (and some learning) I managed to successfully compile wpa_supplicant for the W95 box.
Yet I'm stuck. I can run wpa_supplicant from adb shell but I have not been able to successfully associate with an access point. I figured this might be some sort of conflict with Network or WiFi manager and two wpa_supplicants running at the same time. I wanted to successfully associate before I continued on to try and replace the wpa_supplicant on the Android box with my compiled version. My problem here was that I could not figure out how to enable wlan0 without network manager. In any case I got desperate and punted. I went ahead and tried to replace the original wpa_supplicant with the one that I compiled. Now everything's a mess.
Now that I think about it, I could probably enable the ssv6051 wifi driver module and bring up wlan0 with ifconfig or ip but did I know that back then? No.
Since I did already try and replace wpa_supplicant with my compilation I figured all bets were off. In any case, I could always copy back the original wpa_supplicant right? Well, not exactly. At this time, neither one works and I'm racking my brains just trying to get things back to square one. I get a vague error about not being able to start HAL. I read some about HAL and a possible culprit, selinux (although this is unlikely due to the w95 box being in Permissive mode by default) but I still am not anywhere closer to fixing my wifi. The button moves on temporarily, the driver modules load, but the HAL error occurs and it does not list any wifi networks.
I think I messed up when I edited one of the wpa_supplicant.conf files. Or it could have something to do with the wifi vendor. I don't know, but I'm close to getting this working. Then I can patch wpa_supplicant and it will no longer be vulnerable to the KRACK attack. At the very least I can continue the other tests.
Thank you for reading. Your input is appreciated.