Related
EDIT: It seems the sqlite solution does not work at all. I am trying other ways.
See this thread: http://forum.xda-developers.com/showthread.php?t=593739
[DEL]
I've been searching for the way to get my Hero access the Internet through a proxy when connected to a WiFi network. And the only information I found useful was a HOWTO on setting up the emulator to use a proxy.
According to that HOWTO, inserting a record into table 'system' in database 'settings.db' (/data/data/com.android.providers.settings/databases/settings.db) tells the emulator the proxy information:
Code:
sqlite> insert into system values(99,'http_proxy','<ip-of-proxy>:<port-of-proxy>');
So I wonder if this works on a Hero product.
I am using a HTC Generic 2.73.405.38 ROM and I couldn't find sqlite in my phone. Following is what I have tried under android sdk in windows:
Code:
android-sdk-windows\tools> adb pull /data/data/com.android.providers.settings/databases/settings.db .
android-sdk-windows\tools> sqlite3.exe settings.db
sqlite> insert into system values(99,'http_proxy','<ip-of-proxy>:<port-of-proxy>');
sqlite> ^C
android-sdk-windows\tools> adb push settings.db /data/data/com.android.providers.settings/databases/
But after rebooting my Hero, the proxy still does not seem to work.
Can anyone help me with some clues on this? Does the settings.db not work as it did in emulator? If not, then how?
[/DEL]
Someone has managed to connect to an ad-hoc access point? I tried but I failed, also I have not heard of anyone who has achieved
Try the Connectify application to achieve the same thing.
Sent from my HTC Desire using XDA App
This transforms the pc (with windows) in AP, but i want this feature to connect Android phone to other Android phone, [with Wireless Tether] sharing the connection between two phones (really i dont need, but i like to experiment xD)
Thanks for fast reply an sorry for my english
I am also very much interested in this topic for quite a while and i have collected some information about it:
1. Ad-hoc wifi is not a desire specific issue but it affects all devices running android. There is a ticket asking to add it but its just in the state "reviewed" by now. See http://code.google.com/p/android/issues/detail?id=82
2. Some workarrounds exists but they depend on the device beeing addressed.
3. szym.net (author of barnacle wifi-tether) gives a very good explanation why ad-hoc actualy does not work with stock android:
Unfortunately, the WifiManager in stock Android ignores ad-hoc networks.
Click to expand...
Click to collapse
He offers a patch to hack wpa_supplicant which lets ad-hoc networks look like regular access points and thus make them accessable from the phone. See http://szym.net/android/adhoc-wpa-supp.html
HTH
I try your link says, and i try this other pretty way: racheado.blogspot.com/2009/12/conexion-ad-hoc-en-android-posible.html (is in spanish)
but when go to remount in "-ro" the phone resets and don't save the changes.
Also i try this way: ott.net/knowledge/htc-desire-adhoc/ but when go to execute "iwconfig" the "better terminal" or "adb shell" says "permission denied".
And yes, I have root access
ghiki said:
I try your link says, and i try this other pretty way: racheado.blogspot.com/2009/12/conexion-ad-hoc-en-android-posible.html (is in spanish)
but when go to remount in "-ro" the phone resets and don't save the changes.
Also i try this way: ott.net/knowledge/htc-desire-adhoc/ but when go to execute "iwconfig" the "better terminal" or "adb shell" says "permission denied".
And yes, I have root access
Click to expand...
Click to collapse
You can't gain Read/Write access to /System, Read-Only Access.
You can get access in Recovery Mode though.
Unfortunately the fix does not work after boot anyways, due to the /data/misc/wifi/wpa_supplicant.conf being defaulted to not show AdHoc by the original wpa_supplicant.conf in /system after a visit in WiFiManager. I suggest you modify that one instead to always remember your network and settings. Tricky, but works.
Hello to all,
I have just tried to overwrite the wpa file in data/misc/WiFi with the one patched and I changed the name but nothing works!!!
Please help!
Sent from my HTC Desire using Tapatalk
No Answers?
Help us
Found another solution.
Get hold of the iwconfig / ifconfig binaries.
Shut off WiFi first!
Code:
su
insmod /system/lib/modules/bcm4329.ko
iwconfig eth0 mode ad-hoc
and there you go. A interface you're free to do what you like with.
Got it working with my laptop by following up with
Code:
iwconfig eth0 essid [U]ad-hoc_test2[/U]
If coded, use:
Code:
iwconfig eth0 key [B][U]your passkey here[/U][/B]
Then a bunch of stuff for the IP, SubNet, GW, DNS
Code:
ifconfig eth0 [U]192.168.1.10[/U] netmask [U]255.255.255.0[/U]
route add default gw [U]192.168.1.1[/U] dev eth0
setprop net.eth0.dns1 [U]208.67.222.222[/U]
Adjust underlined with your own config.
I need help with this.
First, I should mention that I am a Noob in this, so please be patient.
I have rooted my HTC Desire with unrevoked 3.1 and do get a popup whenever an application is trying to get superuser permissions.
Also, I downloaded the Android SDK and can connect to my device by
Code:
adb devices
adb shell
su
What does not work for me is the
Code:
adb remount
command in the PC command prompt but I managed to mount the system directory rw with
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/bin
So, when I the try to
Code:
adb push iwconfig /system/bin
I get a
Code:
failed to copy 'iwconfig' to '/system/bin/iwconfig': Out of memory
What is going wrong here?
P.S.: I found also other solutions like http://szym.net/android/adhoc-wpa-supp.html but have no idea how to apply the patch and the linked solution on the same site http://www.olsr.org/?q=olsr_on_android doesn't work either for me, as the used /system/bin/wpa_cli is simply not on my phone.
I am using stock rom Android 2.2 build 2.11.832.2
OMG: why couldn't anyone mention that one needs to boot the phone into recovery to be able to put files into the system directory.
Now it works, I can run iwconfig.
I can see ad hoc networks now but can't connect.
I have the Android ADK installed and I have adb. I don't seem to have the privledges to use it though. If I try and use it normally I get
Code:
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
I can only get it to work if I start adb as the admin. Then I can use it as a normal user.
Also, I don't seem to have fastboot. Where do I get it?
On some Linux systems, starting adb as root is the easiest way to go about things. Some systems require setting up udev rules to give normal users permissions to run adb. Still others, simply changing the permissions on adb itself and putting it somewhere in the path will work. Running it as root isn't recommended, but it does work.
As for fastboot, Google have stopped pre-compiling it and distributing it with the SDK. You can either compile the emulator to get it or download a pre-compiled binary from HTC's support website.
beartard said:
On some Linux systems, starting adb as root is the easiest way to go about things. Some systems require setting up udev rules to give normal users permissions to run adb. Still others, simply changing the permissions on adb itself and putting it somewhere in the path will work. Running it as root isn't recommended, but it does work.
As for fastboot, Google have stopped pre-compiling it and distributing it with the SDK. You can either compile the emulator to get it or download a pre-compiled binary from HTC's support website.
Click to expand...
Click to collapse
Ok I guess it's just easier to start it as root. Fastboot on the other hand wont work. After I use the command
Code:
adb reboot bootloader
my phone reboots into recovery and has FASTBOOT USB on the screen. When I type
Code:
fastboot devices
it just goes to the command line again and doesn't show anything. When I try and type $ fastboot reboot I get
Code:
< waiting for device >
Any ideas why it's not working?
I'm probably sharing my ignorance here, but did you run fastboot after starting adb as root? You might have to run it as root as well. Also, try unplugging your phone and re-plugging it before running the command.
beartard said:
I'm probably sharing my ignorance here, but did you run fastboot after starting adb as root? You might have to run it as root as well. Also, try unplugging your phone and re-plugging it before running the command.
Click to expand...
Click to collapse
Ok, now I feel really dumb. I guess I didn't run fastboot as root before. I could have sworen I did. Well now it seems to all be working, as long as I am root. I wish I could do it with out having to be root.
Thanks beartard
No problem. In case you're interested in how to do it The Right Way™ here's a post I found on the Google support forums for Android. The author had a Motorola CLIQ. The vendor id for the Slide is 0bb4.
I found this info to be helpful, although there was not much explanation behind it, and in the end things still did not work for me. after a number of hours of debugging (which was kind of fun!) i finally got things working, and wanted to document it here in case others have the same issues. also documented is *how to debug* your stuff, which may be as valuable as the fix!
disclaimer:
i still dont really understand udev very well, so if someone who does can clarify my observations, that would be cool.
my environment:
ubuntu 10.04, device is a motorola cliq.
adb version 1.0.26
eclipse version 3.5.2 (galileo)
the problem:
persistent issues with adb devices returning:
List of devices attached
???????????? no permissions
rat holes i went down:
a) first, be sure that when you write your android-specific rules in /etc/udev/rules.d that you ensure that you name the file with a name that ends in .rules, or else the udev daemon wont read it.
b) Ubuntu 10.04 uses a new version of udev, so some of the documentation you find on the web is out of date.
c) The phone looks like a disk drive to the OS, which caused me some wierdness. more later.
some basics:
a) the udev infrastructure is what the OS uses to dynamically map, present, and control USB devices. you will need to tell udev what to do with your android phone when the phone is in application debug mode (that is why you need the /etc/udev/rules.d/50-android.rules file.
b) the adb (android debug bridge) is the daemon (using network sockets) that allows the IDE to talk to the device. when you run commands like 'adb devices' the command looks for a running daemon, and if one is not running it starts one and then communicates with it.
c) the "no permissions" error message indicates that the adb daemon cannot get the right permissions to access the device as the user that it is running as. normally the IDE starts the daemon as the user you are logged in as. unless the phone device appears in the udev infrastructure with the correct permissions to be accessed as the user you are logged in as, it wont work.
steps:
1) plug your phone into the usb bus on your system. does not need to be in application debug mode yet...
2) verify that you can see the phone by using 'lsusb', e.g.:
$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 044: ID 22b8:2d66 Motorola PCS
Bus 002 Device 004: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 002 Device 003: ID 10d5:0001 Uni Class Technology Co., Ltd
...
the line "ID 22b8:2d66 Motorola PCS" is my phone. the rest is other stuff on the usb busses. ignore it.
3) the 4 digit value 22b8 is the Vendor ID of my phone. yours may be different. whatever it is, this is the value you need to use in your udev rule.
4) the Bus number and Device number are useful. you can see what permissions your device is getting at any time by doing
$ ls -l /dev/bus/usb/<busnumber> where <busnumber> is the Bus number above (002 in this case).
the permissions of the device will be the permissions of the file numbered with the Device number above. in my case it was device 044, so the full file path is /dev/bus/usb/002/044
! note - this device number will change when you plug/unplug or enable/disable debug on your device.
5) you can now get *alot* of info on this device now by using 'udevadm info', but you need to use the bus and device info above (remember yours may be different and change). you can use either udev info command --query=all or --attribute-walk, e.g.:
$ udevadm info --query=all --name=/dev/bus/usb/002/044
or
$ udevadm info --attribute-walk --name=/dev/bus/usb/002/044
note that the attribute-walk walks up the bus. the first entry printed should be the lowest device on the chain, which is your phone. in my case some of the lines looked like:
looking at device '/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2.4':
KERNEL=="2-2.4"
SUBSYSTEM=="usb"
DRIVER=="usb"
ATTR{configuration}=="Motorola Config 42"
...
ATTR{idVendor}=="22b8"
...
ATTR{busnum}=="2"
ATTR{devnum}=="44"
ATTR{version}==" 2.00"
ATTR{maxchild}=="0"
ATTR{quirks}=="0x0"
ATTR{authorized}=="1"
ATTR{manufacturer}=="Motorola "
ATTR{product}=="MB200"
ATTR{serial}=="<serialnumber>"
...
where the <serialnumber> is the serial number of my phone, which will show up in the adb devices list when this all works. recognize the items that you will need for the .rules file are there.
6) now, lets write the .rules file. you have two choices. either get the permissions of the phone as it shows up changed to 0666 (rw for all users, including the world) or change the ownership to be your user. i prefer the latter. seems cleaner to me, so i will use this approach for the rest of the info.
7) find out who you are. use the id command, e.g.:
$ id
uid=1000(<your username>) gid=1000(<your group name>) groups=...
where the uid and gid for you are indicated. for now lets use both as 'juser' for the example.
8) now lets create the .rules file. the number at the beginning of the file name is the order that it will be loaded by the udev infrastructure. it may be important. all the examples showed a number of 50, but there are a bunch of things being loaded in /lib/udev/rules.d/ as well. i prefer to make my file name 99-android.rules to force it to load very late in the process. this keeps other later things from clobbering my permissions as they load.
for example, if you use the ATTR{idVendor} attribute in .rules as oppose to SYSFS{idVendor}, then when other later rules load they could over write the permissions you set in your .rules file.
9) you have to use root or sudo to create the file in /etc/udev/rules.d. create /etc/udev/rules.d/99-android.rules and put in a line like:
SUBSYSTEM=="usb", SYSFS{idVendor}=="<Vendor ID>", OWNER="<your username>" GROUP="<your group name>"
and save it.
the SYSFS{idVendor} value needs to match your device id, and the OWNER and GROUP are from step 7 above.
for this example lets use
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", OWNER="juser" GROUP="juser"
if you just want to set the permissions use:
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
10) now, when you connect the device (try the application debug mode) you should be able to see that the device appears with the correct user permissions. e.g.(using this example's bus, device, and uid/gid values):
$ ls -l /dev/bus/usb/002
crw-rw-r-- 1 root root 189, 128 2010-10-09 20:02 001
...
crw-rw-r-- 1 root root 189, 131 2010-10-09 20:02 004
crw-rw-r-- 1 juser juser 189, 173 2010-10-10 11:29 044
this is very good, 'cause now adb running as you will be able to read and write the device.
11) if you did not get here, then you have udev issues. dont bother beating on adb, the problem is in udev. your best bet is to go into /etc/udev and edit udev.conf, to change the line
udev_log="err" to udev_log="debug" to see what is going on. then you can follow what udev is doing by opening a terminal window and following /var/log/syslog with:
# tail -f /var/log/syslog
you may need to restart udev, which you can do by doing:
$ sudo /etc/init.d/udev restart
from another terminal window.
this output is very verbose, but you should look to see that your .rules file is being loaded. if not, then that is the issue to fix.
12) if all is ok, and the device has the right permissions, when you put it into application debug mode you should be able to simply start the adb server with:
$ adb devices
and see your device by serial number
List of devices attached
<serialnumber> device
13) if you have problems with adb, here are a few things to check.
a) make sure you see that adb is running, and owned by you by looking for it with ps, e.g.:
$ ps aux |grep adb
you should see a line like:
juser <pid> 0.0 0.1 28160 728 pts/4 Sl 10:18 0:01 adb fork-server server
where juser should be your user id, and <pid> is the process ID.
b) if adb is running as root, you may need to use 'sudo killall adb' to kill it off and then as your user run 'adb devices', which should start the server as you.
c) if you still have problems you can run strace on the server and it's child processes with:
$ strace -f ./tools/adb server
note that the output is very verbose, but look thru there for some kind of permissions problem. lots of 'file not founds' are ok, but as the daemon starts and tries to bind to the device, you may find a permission problem.
hope this helps. sorry to be long winded.
jerichod.
Click to expand...
Click to collapse
Been working on a couple fix ideas for this since UltraCfg is no longer working in the UCLD2 leak.
From what I can tell, UltraCfg made an entry in settings.db which can be enabled or disabled. This entry is TETHERING_ALWAYS_ON_MODE = enabled/disabled. Steps to manually do this are shown in post #2.
Also: Tethering Manager & UltraCfg were active; and WifiDirect, Wifi Sharing, and Wifi Sharing Manager are frozen.
Please let me know if any of this works and we can continue to improve this. I'm not sure how stable it is.
Known Issues & Limitations:
1. Only tested by me so far.
2. Not sure if it stable yet. I've had issues keeping wifi tethering active.
3. Any time you connect phone to PC via USB, it disables Debugging and activates Tethering.
4. USB Debugging is disabled on reboot.
5. Not an easy patch for the novice.
I used sqllite editor which is $2.99 in the market. If you dont want to pay and you can survive some terminal shell grinding, here's a free method using sqlite3. For whatever reason, it's not installed by default in our ROMs.
1. Download sqlite3.zip attached. Unzip and put it in /system/bin.
-- quickest method is to unzip. then use adb.
Code:
adb mount
adb push sqlite3 /system/bin
adb chmod 771 /system/bin/sqlite3
2. Next we are going to make a copy of our settings.db file as settings.dbx. Again, in adb.
Code:
adb shell
>su
>cd /data/data/com.android.providers.settings/databases
>cp settings.db settings.dbx
3. Dont close your terminal. Now that we have a copy, we will now edit it with sqlite3. Assuming you did a clean data wipe when you first installed the UCLD2 rom do this:
Code:
echo "insert into system (name, value) values('TETHER_ALWAYS_ON_MODE','enabled');"|sqlite3 settings.dbx
4. Now we have inserted the new tethering setting! Now we need to backup your original settings and replace it with this modified one.
Code:
mv settings.db settings.bak
mv settings.dbx settings.db
5. DONE! Now you may need to reboot.
Code:
reboot
Now, I'm not 100% sure this will work, but I never wiped my data from the UCAL4 ROMs to this new one, so my settings never changed. You will also need Tethering Manager. The one issue with having this mode on is that you will get automatically switched to usb tethering when you connect your phone to computer.
If you ever want to disable, follow steps above except use this command in step 3:
Code:
echo "update system set value = 'disabled' where name = 'TETHERING_ALWAYS_ON_MODE';"|sqlite3 /settings.dbx
I followed the steps ending in a boot loop
Did anyone successfully install debian kit on the galaxy note 10.1 (2014) ?
I tried,
sh /storage/emulated/0/debian-kit-1-6.shar
unpacks properly, but then nothing happens. A wizard is supposed to start.
I tried both 1-6.shar from Doviak, and 1-5.shar from sven-ola
I did the following. Start with unrooted device. Accept KK OTA upgrade. Now
I have SM-P600 with Android 4.4.2. Root with CF. This fails.
Flash openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar with Odin. Then boot into TWRP and
install UPDATE-SuperSU-v1.94.zip. Now some apps ask for root access and it seems to be
granted; installed sdfix, and at least one app (aplinequest) that could not write after
the KK upgrade can now write to extsdcard.
Installed Debian Kit app. All green checks, except red Xs for "Kernel modules supported"
and "Valid 'su' command found". But I know su is working. (I think there was a red X by Debian
Kit already unpacked)
Transfer debian-kit-1-6.shar to device. I follow instructions, Install connectbot. Give 'su'.
Run sh /storage/emulated/0/debian-kit-1-6.shar
Get error messages (I didnt record them), such as md5sum not found, and
a couple of other binaries not found. I give echo $PATH and then look for these binaries
in my path. They are not there. So I install BusyBox Free. Run the shar file again. I
get a list of files extracted, but then nothing happens. Now I see that debian kit wants
to use its own busybox and I didnt need to install busybox, but debian kit did not work
in any case.
I try to run /data/local/deb/autorun with sh autorun. Exits with "Unsupported CPU or architecture"
Investigate and find shell var CPU is set correctly to "armel" on first past, but when the script
runs again with exec, CPU is ''. So I hardcode CPU=armel. Then I can get a little further.
And so on and so on, hardcoding CPU in all the scripts. Trying to get the scripts to see the
correct binaries, etc. Now I have a diskimage installed, can't go forward and can't uninstall.
If anyone can shed some light....
update
Deleted everything and started over. Using adb shell. I notice
that the installer says
Included busybox failed.
and tries to use system tar, sed, etc, which it cannot find.
However, If I put #!/system/bin/sh at the top of debian-kit-1-5.shar
And run ./debian-kit-1-5.shar rather than sh ./debian-kit-1-5.shar,
then the script runs for quite a while and extracts a lot of files.
It fails eventually with
ash: id: Permission denied
In fact, from the adb shell I get
126|[email protected]:/data/local # id
uid=0(root) gid=0(root) context=u:r:init:s0
[email protected]:/data/local # ./deb/armel/busybox ash -c "id"
ash: id: Permission denied
126|[email protected]:/data/local # ./deb/armel/busybox ash -c "/system/bin/id"
ash: /system/bin/id: Permission denied
More Update
It seems that in some cases the user 'shell' has permission to do something, but 'root' does not.
One thing stopping the debian kit install process is that root running a shell located under /data cannot run any executables via
passing a string on the command line. They can run commands interactively (maybe because the command
line uses exec ?). But the user 'shell' can run executables this way. E.g. I copied /system/bin/mksh to the /data partition.
[email protected]:/ $ su
[email protected]:/ # /data/local/bin/mksh -c "id"
/data/local/bin/mksh: id: Permission denied
1|[email protected]:/ # /system/bin/mksh -c "id"
uid=0(root) gid=0(root) context=u:r:init_shell:s0
[email protected]:/ # su shell
[email protected]:/ $ /data/local/bin/mksh -c "id"
uid=2000(shell) gid=2000(shell) context=u:r:init:s0
There are a few posts scattered around other forums mentioning the same problem when trying to
install debian kit, but no responses even recognized that there was a problem.
The solution was to install an selinux permissive kernel. Then installation
went normally.
I think I can help.
injola said:
Did anyone successfully install debian kit on the galaxy note 10.1 (2014) ?
I tried,
sh /storage/emulated/0/debian-kit-1-6.shar
unpacks properly, but then nothing happens. A wizard is supposed to start.
I tried both 1-6.shar from Doviak, and 1-5.shar from sven-ola
I did the following. Start with unrooted device. Accept KK OTA upgrade. Now
I have SM-P600 with Android 4.4.2. Root with CF. This fails.
Flash openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar with Odin. Then boot into TWRP and
install UPDATE-SuperSU-v1.94.zip. Now some apps ask for root access and it seems to be
granted; installed sdfix, and at least one app (aplinequest) that could not write after
the KK upgrade can now write to extsdcard.
Installed Debian Kit app. All green checks, except red Xs for "Kernel modules supported"
and "Valid 'su' command found". But I know su is working. (I think there was a red X by Debian
Kit already unpacked)
Transfer debian-kit-1-6.shar to device. I follow instructions, Install connectbot. Give 'su'.
Run sh /storage/emulated/0/debian-kit-1-6.shar
Get error messages (I didnt record them), such as md5sum not found, and
a couple of other binaries not found. I give echo $PATH and then look for these binaries
in my path. They are not there. So I install BusyBox Free. Run the shar file again. I
get a list of files extracted, but then nothing happens. Now I see that debian kit wants
to use its own busybox and I didnt need to install busybox, but debian kit did not work
in any case.
I try to run /data/local/deb/autorun with sh autorun. Exits with "Unsupported CPU or architecture"
Investigate and find shell var CPU is set correctly to "armel" on first past, but when the script
runs again with exec, CPU is ''. So I hardcode CPU=armel. Then I can get a little further.
And so on and so on, hardcoding CPU in all the scripts. Trying to get the scripts to see the
correct binaries, etc. Now I have a diskimage installed, can't go forward and can't uninstall.
If anyone can shed some light....
Click to expand...
Click to collapse
I have the same tablet and I tried to answer you several times but when I give exact instructions they don't let my reply get to the thread for some reason. So I'll have to be less specific, sorry. Anyway. I rooted with an omnirom based setup. 412. Homemade. Once you get the debian-kit-1-6-testing.jpeg and you've unloaded it to you your root directory try:
#sh /data/local/deb/mk-debian -i
Follow the usage correctly and until your done testing leave:
-h
At the end of the script. But be sure to set it to armel and 2047 and wheezy and set the mirror to:
deb. .org/dists/wheezy/ main contrib non-free
Kali
catch all the protools and for the gpg licence use google search my username KeizerPaPa and I'll give you the gpg on my + account. Goodluck. ]
---------- Post added at 06:40 PM ---------- Previous post was at 06:28 PM ----------
KeizerPaPa said:
I have the same tablet and I tried to answer you several times but when I give exact instructions they don't let my reply get to the thread for some reason. So I'll have to be less specific, sorry. Anyway. I rooted with an omnirom based setup. 412. Homemade. Once you get the debian-kit-1-6-testing.jpeg and you've unloaded it to you your root directory try:
#sh /data/local/deb/mk-debian -i
Follow the usage correctly and until your done testing leave:
-h
At the end of the script. But be sure to set it to armel and 2047 and wheezy and set the mirror to:
deb http .org/dists/wheezy/ main contrib non-free
Kali
catch all the protools and for the gpg licence use google search my username KeizerPaPa and I'll give you the gpg on my + account. Goodluck. ]
Click to expand...
Click to collapse
Make sure you piece the above together correctly, they wouldnt let me type it all together. Thats deb http: //http
Then .kali then .org/dists....... have fun. If ya get stuck on the gpg search me and ask. KeizerPaPa
A reason why mine failed at first was because "Debian kit" is set to resolve ip addresses using "only" your Primary DNS Server (DNS 1). When I finally pinged my Primary DNS server, I found it was not functional. My Secondary DNS server (DNS 2) was functional (this also explains why my internet was slower than it should have been while browsing the internet)
I changed my Primary DNS server by
1) going into the WIFI settings
2) long-pressing on the WIFI I was connected to
3) choosing "Mofify..."
4) checking the "Show advanced..." option
5) changing from "DHCP" to "Static"
6) entering a functional DNS server (such as 8.8.4.4) for "DNS 1"
- Hyp