Develop Bugs

[REQ] Dropbear ssh client

Ive asked in Themes and Apps to no avail so please dont jump on this for possibly being in the wrong forum.
Im looking for a binary of dropbear but i cant seem to find one that will work with our phone.
The situation.
At work they block everything, so i figure since i can adb into my phone, and since it has its own internet connection, i can use a cli ssh client to run around the internet doing the things i need to do from my shell.
can anyone please compile it or post it? ive looked for a couple of days.
much obliged.

Have you already tried QuickSSHd on Market?
Also this guy claims to have got it working:
Gentooer said:
Got it working!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I basically built it with qemu by following the tips and using the patch found here: http://jblomer.web.cern.ch/jblomer/android.htm
I'm not too familiar with all the different kinds of authentication, so this my be very insecure, but it works for me. These are the steps I followed after building dropbear:
1. Transfer dropbear and dropbearkey to a rw partition where they can be executed.
2. Generate a private rsa key with "dropbearkey -t rsa -f my_rsa_key"
3. Run "dropbear -A -N root -U 0 -G 0 -C <desired password> -r <path to my_rsa_key> -p 22"
4. ssh into your phone using the password entered in previous step. You should now have a full root terminal!
Here are the files (If anyone can provide better hosting that would be great):
http://www.speedyshare.com/190562592.html
Click to expand...
Click to collapse
That quote was from this thread.

If you have enough access to get ADB running on your work PC, why not just put PuTTY on there as well?

[Q] LOOP_SET_FD failed: Device or resource busy

First of, jump down to the red dotted line for what i need help with, the text above just explains root method, phone and programs i have installed.
Thanks for taking the time.
I have been searching and reading up on every problem I've had so far in the install, i have come to a dead end and i need to get pushed a step further, i need help.
I am installing BT5 ARM on my Note 2 N7100.
Whatever the reason, i grew up with BT and i have my reasons why i want it on my phone (if i wanted to crack someone i would have just used my BT on USB, i have a lot of different things like this mostly for nostalgia)
I have a Note 2 N7100 with android 4.1.2
I rooted my phone using METHOD 2 in this thread (Odin307)
http://forum.xda-developers.com/showthread.php?t=2143479
I have SuperSU BusyBox and AndroidVNC
All installed and working as they should.
----------------------------------------------​
Backtrack version downloaded:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now it gets wierd.
On Terminal Emulator i grant SU and go into the BT5 folder and boot the "bootbt" file.
"ioctl LOOP_SET_FD failed: Device or resource busy"
I am not a linux expert, I am what you will call an experienced n00b :good:
I was up LATE last night and i figured out something i cant remember now.
It was something about if my device had "loop 1-2-3-4 etc" enabled?
AND that i might need an modified "bootbt" file ?
I am so stuck and I have been staring in the eyes of this problem for so long i have gone blind.
Help me see.
Thank you.

I have the same problem on my samsung s5

good to know
you need custom kernel, as stock doesn't support it

Adaway hosts file problem, rooted with CF-Auto-Root

Just received my T-Mobile Galaxy Note 3 SM-N900T yesterday and it's gorgeous! I used CF-Auto-Root to get root in under 30 seconds as advertised! I installed F-Droid and then Adaway, which is my ad blocker of choice, but it has a problem writing the hosts file. I was wondering if this has something to do with not having access to a particular partition? It's not really a huge ordeal and I know the device is brand new but I thought I would throw this out there just in case anyone else had noticed the issue or has a solution. Thanks in advance.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ad-free is working on my phone
[I put the pic of speedtest so you can see there's no ad's
Sent from my SM-N900T using Tapatalk 4

Make sure Busybox is up to date. If you installed it, rebooted, and it still doesn't work, try enabling USB debugging, and try again. That worked for me in the past when I had issues with it not working right.

bobbyphoenix said:
Make sure Busybox is up to date. If you installed it, rebooted, and it still doesn't work, try enabling USB debugging, and try again. That worked for me in the past when I had issues with it not working right.
Click to expand...
Click to collapse
To update my own results. I couldn't get it to work normally. I had to change the host destination in settings to /data/data/hosts, and then let the app create a symlink. Now it works great.
Sent from a Galaxy Note 3 far, far away....

[Q] Cannot resolve hosts in Terminal

I can't seem to find a solution for this, but Internet access from within the Android shell was working for a few days, but now it just won't.
Ping google.com gives an unkown host error.
nslookup google.com is the same.
nslookup google.com 8.8.8.8 Does work, spits out 7 lines of DNS... stuff.
I tried looking for /etc/resolv.conf but there's not one there. Internet access outside the shell works fine.
Is there a fix for this? I'm running stock GB27 completely untouched other than root and Agat's kernel.

gorei23 said:
I can't seem to find a solution for this, but Internet access from within the Android shell was working for a few days, but now it just won't.
Ping google.com gives an unkown host error.
nslookup google.com is the same.
nslookup google.com 8.8.8.8 Does work, spits out 7 lines of DNS... stuff.
I tried looking for /etc/resolv.conf but there's not one there. Internet access outside the shell works fine.
Is there a fix for this? I'm running stock GB27 completely untouched other than root and Agat's kernel.
Click to expand...
Click to collapse
You can create a resolv.conf if there isn't one, though I don't know if that would fix your problem. Also I notice the you wrote nslookup, shouldn't it be dnslookup?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
You can create a resolv.conf if there isn't one, though I don't know if that would fix your problem. Also I notice the you wrote nslookup, shouldn't it be dnslookup?
Click to expand...
Click to collapse
Sorry, typo.
What's the syntax for the resolv.conf?

Reset dpi using adb and Swiftkey is messed up now

I have been resetting my dpi for years without issue. Now that I am systemless rooted on the 5X, I had to use adb to change dpi. Before I always used a file editor. So for some reason, resetting in adb gets me the Swiftkey keyboard in my pic. Nothing I do seems to fix it. Tried reinstalling Swiftkey, but it comes out the same. Google keyboard is not affected, nor is anything else. Also, if i change dpi using a file editor then Swiftkey works as it should. Anybody know what is happening here?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You have to change it in the build.prop too, as far as I know. Unless there is some sort of hook to override build.prop using systemless root...?
Swiftkey flat out does not support the adb only method.
Googling "swiftkey dpi" will bring up the relevant results.

PhoenixTank said:
You have to change it in the build.prop too, as far as I know. Unless there is some sort of hook to override build.prop using systemless root...?
Swiftkey flat out does not support the adb only method.
Googling "swiftkey dpi" will bring up the relevant results.
Click to expand...
Click to collapse
Bummer. The adb method did change the build.prop(I checked), but I did not know this was a known issue with Swiftkey/adb. Thanks for the heads up.

jackdubl said:
Bummer. The adb method did change the build.prop(I checked), but I did not know this was a known issue with Swiftkey/adb. Thanks for the heads up.
Click to expand...
Click to collapse
Sounds like you have it set up correctly, but just in case, checking output with the command here might help:
https://www.reddit.com/r/nexus6/com...i_to_493_swiftkey_is_now_freaking_out/cnc198j
FWIW, I have not tried changing on my 5X but have on my Shield K1 and ran into this.