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?
I have been searching all morning for the answer to my issue, but evidently I am not using the correct words in my search. Either that or I am the first person to need to do this:
In an effort to try to get Netflix working on my Gtab running Vegan 5.1.1, I have been trying differing edits of the build.prop file. Since Netflix is working on my original version Droid, I have been using it as a model. All to no avail. So, last evening, fully aware that I might brick the gtab and willing to pay the price of a reflash if necessary, I copied the entire build.prop file from my Droid to my gtab and rebooted. Sure enough, won't boot.
I have backups of the original working build.prop but cannot access it by connecting my gtab to my pc through usb. I can access the files on the sdcard but cannot figure out how to get into the system folder so that I can replace the offending file with a good one. I thought that nvflash might be my friend, but after reading everything I can find on that tool it seems that it will just reflash to stock.
I can reflash my Vegan install, and may have to do so....but is it possible to just access the files in the system folder? If so, all I would have to do is to delete the current build.prop file and rename my backup file back to build.prop.
Anyone know how I can do this?
Joe
You can us ADB to push (or pull) files as well as accessing the command line on your gTab. ADB is a development tool, and is part of the Android development kit. You need to install the driver that comes with it, but first you need to edit the .INF file with a couple lines referencing the gTab. You can find additional information about ADB in other posts.
If recovery is working ok then you could reflash your ROM or craft a custom update to replace build.prop.
You could also nvflash just the system partition if you have an image for your ROM.
Lots of options.
Edit: Just looked at the Vegan 5.1.1 supplement update and it has a build.prop file in it. Reinstalling it would likely get you running again as long as you haven't made any other significant changes to the system files. It might revert a few system applications to older versions.
If you have adb set up and working, restoring your backed up build.prop would be trivial job. Let us know if you have adb working and then we can give you the commands you need to use.
As of right now, I do not have adb setup and working. Well, that's not quite true....I did set it up quite some time ago and used it on my Droid. Guess I need to reconfigure it for the gtab and then proceed from there?
Joe
Well, I resolved my issue by reflashing the VegaN rom, all is good now.
Joe
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.
Help, (PLEASE) I just "re-rooted) my Archos 101it tablet....I missed the setup screen where you fill out all the information on who you are (the developer)...now when I power it on, it gives me the Archos logo, then developers logo (angstrom) but then goes to very itsy bitsy lettering :
The angstrom distribution archos-gen-8
Angstrom 2009.X-stable archos-gen-8 tty1
archos-gen8 log in:
It does not respond to the touch screen. I am just sick inside...I had this tablet since mid-2011 and never did anything much with it, then after a download from Amazon, I started getting this popup saying that certain things could not open...lots of people had this error message, thus the reason for googling to this forum. I thank ANYONE in advance who can help me out...any way to get back to the screen to put in my user information and log in passcodes??? Jeanie
ps...then the new op version (android for Archos) that the person who wrote the tutorial on how to re-root is no longer available. (scream) I will need to know how to download the new op if I ever find it 8-(
I also had the same problem!!: After applying sde versions and trying numerous times to re-download firmware, I finally got my aos back!!! Seems I downloaded the newest version using Chrome and it wasn't copying right, so I followed another forum's advice and used Internet Explorer...it worked!!! Now after a week, I now have a "Like New) Archos 101it. What a learning experience!!!
P.S. I don't really know if it was Chrome or IE, seems I kept downloading different versions of the aos files with the same name...thus it was renaming them
firmware_archos_android_gen8. (2)aos
firmware_archos_android_gen8. (3)aos
well, before I copied the file over to the 101it drive, I took out the (2) or (3), then it worked!!!!
Try to delete SDE, reformat device and flash it again. Use chrulri's method to root it.
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.