AnimaTechnica
Senior Member
- Nov 4, 2010
- 789
- 63
- Thread starter
- #16
@rico - i was thinking the same, but thought i'd make sure
well since my wife declined the jailbreak, and she did warn me not to do it behind her back, i decided to go with plan B - that is let her use my verizon mifi and I'll try to tether using my Droid - so after a couple of hours of research, i finally got it working
basically the key is enabling adhoc on NC, rooting the droid phone, then using Wifi Tether app on the droid. Now this broadcasts in adhoc mode so i needed to prepare the NC to be able to connect to AdHoc. tried the adb method, could not get it to work and finally settled on rogerdugan's method which uses root explorer and terminal to do it
i downloaded root explorer and Better Terminal Emulator (from app planet)
Download the switch-adhoc.zip file xda-developers
and follow the instructions below (original posting at XDA here)
method below by Rogerdugans
------------
unzipped the switch-adhoc file, and open Root Explorer
Navigate with Root Explorer to /system/bin amd click on the Mount rw button.
Copied the unzipped files (4 files) into /system/bin
Launched the Better Terminal Emulator app to start a terminal session and
typed su
su
cd /system/bin
ls
'cd' to get you to the right directory
'ls' to make sure the files are there
and then in Better Terminal Emulator type
'chmod 755 /system/bin/wpa_supplicant.adhoc' then press enter
'chmod 755 /system/bin/wpa_supplicant.infrastructure' then press enter
'chmod 755 /system/bin/adhoc' then press enter
'chmod 755 /system/bin/infrastructure' then press enter
Used Root Explorer to make /system/bin ro again
For good measure rebooted the nook by typing in the terminal: reboot
After the reboot opened terminal and did
su
adhoc
------
on the Droid, run Wifi Tether app
so now in adhoc mode you should see the adhoc signal (I use wifi manager ) - shown as *AndroidTether the (*) indicates it is adhoc, connect to it
now if i want to go back to infrastructure mode, turn off wifi first, then just open the terminal again:
type 'SU' then enter
type 'infrastructure' then enter
and tried connecting - success!
well since my wife declined the jailbreak, and she did warn me not to do it behind her back, i decided to go with plan B - that is let her use my verizon mifi and I'll try to tether using my Droid - so after a couple of hours of research, i finally got it working
basically the key is enabling adhoc on NC, rooting the droid phone, then using Wifi Tether app on the droid. Now this broadcasts in adhoc mode so i needed to prepare the NC to be able to connect to AdHoc. tried the adb method, could not get it to work and finally settled on rogerdugan's method which uses root explorer and terminal to do it
i downloaded root explorer and Better Terminal Emulator (from app planet)
Download the switch-adhoc.zip file xda-developers
and follow the instructions below (original posting at XDA here)
method below by Rogerdugans
------------
unzipped the switch-adhoc file, and open Root Explorer
Navigate with Root Explorer to /system/bin amd click on the Mount rw button.
Copied the unzipped files (4 files) into /system/bin
Launched the Better Terminal Emulator app to start a terminal session and
typed su
su
cd /system/bin
ls
'cd' to get you to the right directory
'ls' to make sure the files are there
and then in Better Terminal Emulator type
'chmod 755 /system/bin/wpa_supplicant.adhoc' then press enter
'chmod 755 /system/bin/wpa_supplicant.infrastructure' then press enter
'chmod 755 /system/bin/adhoc' then press enter
'chmod 755 /system/bin/infrastructure' then press enter
Used Root Explorer to make /system/bin ro again
For good measure rebooted the nook by typing in the terminal: reboot
After the reboot opened terminal and did
su
adhoc
------
on the Droid, run Wifi Tether app
so now in adhoc mode you should see the adhoc signal (I use wifi manager ) - shown as *AndroidTether the (*) indicates it is adhoc, connect to it
now if i want to go back to infrastructure mode, turn off wifi first, then just open the terminal again:
type 'SU' then enter
type 'infrastructure' then enter
and tried connecting - success!
Last edited: