I know that OnePlus does not allow ADB over network and requires a connection under normal circumstances. I know this may sound stupid. I'm new, learning and trying to find different ways to do things. I've recently enabled my ADB via Magisk and installed Termux on my OP6T. Am I able to connect to my Amazon Fire device via Termux and WAN? Both devices will be connected to the same network. I plan to try with this later and am just researching. I've downloaded the APKs that I plan to push and want to see if I can accomplish it via my phone.
I've also noticed that Termux is in a hidden folder in the Internal Storage as I was trying to locate the folder to move the APKs there.
Sorry for wasting time, there apparently are apps that already do that more easily than utilizing this method.
Related
Developers, do NOT get EasyTether! EasyTether allows your 3G connection to be shared to your computer via the USB Cable.
HOWEVER, when you install the computer-side client of EasyTether, it saves a file that tells the computer to automatically mount the phone as a network spot when it is plugged in. This means adb won't find it (since it's not mounted as a device), and this means DDMS and "Eclipse Run on Device" won't work either. EasyTether is a great app, but developers shouldn't get it if you test apps on your device.
P.S. I learned this the hard way. It involved deleting system files and logging in as root on my Mac, as well as a few terminal commands.
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
I've been thinking about this, and if I could just set up the android version of astrill directly in the micro sd (directly set up on nooter) I could then access youtube and finish the job properly.
Do you know if it's in any way possible to do that?
I wonder if you'd be able to use Orbot to be able to gain access to Youtube...
Karibou3 said:
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
Click to expand...
Click to collapse
Read this, its all contained on my manual tutos, adb is gained just by changing uramdisk, there is one for wifi and another for usb, please, check which one you are using, then, follow this:
Here there is a list of all the tutos:
http://forum.xda-developers.com/showthread.php?t=1380400
and here the ones you should read:
Setting up adb manually on the nook touch:
Making the manual process LESS PAINFULL
Setting up root access on NST through adb and installing busybox:
Hope it helps.
For the youtube thing, just set adb correctly (when you get it right) sideload an app to use a proxy, or tor, or anything you like, and try to login on Youtube.
I'm really sorry for not responding to this
I managed to get it rooted in the few days after my post, and I didn't any email notifications of your replies (didn't check on control panel, i'm new here, please don't hurt me )
I found a chinese source for rooting (a seller on taobao.com explained it. The Chinese are quite fond of the nook because it's the only foreign e-reader you can use to read Chinese apparently, and Chinese e-readers are both more expensive than the nook AND crappy.
Anyway I painstakingly translated it and got it to work
what you tell me about the proxy is new to me though, I thought android couldn't run a proxy, that's great news not just for youtube but the zillions of website China blocks and that I could use my nook to check, I'll have a go at it when I get near a wifi network.
cheers
After reading around, I've learnt that MinimalTouch 1.1beta5 is a reliable way to root my new Nook Simple Touch. Since I intend selecting the package version in the beta5 folder, I must choose between the "START" zips: beta5-2 XUFullTouch-PART-1-START and beta5-2 XWFullTouch-PART-1-START. I gather the first zip is ADB over USB, and the second, ADB over WiFi, but have found little documentation on either, except that ADB is a method to connect your home computer to your Nook.
The above link states that all W zips install ADB wireless Uramdisk, and all U zips install ADB USB Uramdisk + ADB widget to enable wireless adb at need. Am I right that ADB over USB is the best choice because both USB and WiFi are available after rooting? If so, would anyone select the ADB over WiFi option?
Can someone please explain how and why one chooses between the two options when rooting the Nook?
On startup the ADB daemon, adbd looks at the property service.adb.tcp.port
If it is set it uses that value as the port number over TCP (presumably over WiFi) to listen for connections.
If it is not set it tries to connect over USB.
I'm not sure how these applications that switch mode work.
They probably kill the daemon and restart it.
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Renate NST said:
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Click to expand...
Click to collapse
Thanks for your help. I've taken a while to make sense of your post since all this is new to me - I rarely use a mobile phone.
I've just looked at contents of both the "START" zip files and noticed they're the same, except that the file uRamdisk in the folder boot of the WiFi option is marginally bigger. You have shown me the difference lies in the property service.adb.tcp.port in the Java source code, and that property determines whether the rooted Nook tries to connect by WiFi or USB. In other words, the two zips are identical except for ADB connection.
But my opening post, in ignorance, attempted to ask a more trivial question. I know whenever I wish to access any laptop computer from my desktop computer under Windows XP, I can connect the two using a network cable from the laptop to my wireless router/modem or, more simply, by activating WiFi on the laptop. Similarly, I am assuming I can connect the rooted Nook to my desktop either by cabling the Nook microUSB port to a USB port on my desktop, or by activating WiFi on the Nook. I expect to connect every few days. Since the USB "START" zip of MinimalTouch 1.1beta5 provides an ADB widget to enable wireless adb at need, what is the point - for the end user - of a separate WiFi only "START" zip file?
In other words, in routinely connecting my rooted Nook to the desktop computer every few days, why on earth would I or anyone benefit from having had the two "START" zip options available in MinimalTouch 1.1beta5?
I can't find instructions on how to side load apps from OS X to my Nook Simple Touch. I rooted it using these instructions. I also installed NTGAppsAttack but it took me a while before I could log into Google and get it working. Now that it's working it doesn't seem to do much since I can't search the Google Market (probably because I can't side load apps).
First, I'm trying to install the Kindle App that I got from here. I downloaded the Android tools, but when I try to run ADB, it seems that the device isn't connected:
$ ./adb install ~/Downloads/Kindle_3.3.1.1.apk
error: device not found
- waiting for device -
I thought maybe I could load the .apk file in the Finder. There isn't enough room for me to load it onto the NookManager partition (only 8 MB free) so I put it in the My Files/Documents folder of the NOOK partition. However I can't seem to find that location using the ReLaunch app. It won't let me out of the sdcard directory.
I also tried launching ADB Konnect on the device and it tells me "Root Access Denied!"
Is it possible to install apps via SSH? I can't figure out how to get SSH running.
I'd appreciate any help. Thanks.
No idea about Macs, but for USB you will have to modify ~/.android/adb_usb.ini
Nook is not a "known" Android.
Code:
0x2080
If your root uses ADB over WiFi that would work too.
I have recently tried to root the new Fire HD 10 (2017). Unfortunately i've got today a bootloop. This little guide is for Linux. The principle stays the same, so you can apply this also on Windows. Here's what i did to resolve the problem:
1. Download adb on computer (here is for linux: dl.google.com/android/repository/platform-tools-latest-linux.zip ) & unpack
2. Download the 5.5.0.0 firmware for HD10(2017) from HERE : fireos-tablet-src.s3.amazonaws.com/afKacHmumxrMp9XPdw6oykKMaw/update-kindle-40.5.9.1_user_591450020.bin
3. Rename that in update.zip and place in the same folder with adb
4. Open terminal in the same folder with adb
5. Connect your device to the computer
6. Enter recovery mode on Tablet (Power + Vol Up) & go to install update from ADB
7. Go on computer and run in the opened terminal: ./adb sideload update.zip
8. Wait till the process is finished, restart and enjoy
Exsa said:
I have recently tried to root the new Fire HD 10 (2017). Unfortunately i've got today a bootloop. This little guide is for Linux. The principle stays the same, so you can apply this also on Windows. Here's what i did to resolve the problem:
1. Download adb on computer (here is for linux: dl.google.com/android/repository/platform-tools-latest-linux.zip ) & unpack
2. Download the 5.5.0.0 firmware for HD10(2017) from HERE : fireos-tablet-src.s3.amazonaws.com/afKacHmumxrMp9XPdw6oykKMaw/update-kindle-40.5.9.1_user_591450020.bin
3. Rename that in update.zip and place in the same folder with adb
4. Open terminal in the same folder with adb
5. Connect your device to the computer
6. Enter recovery mode on Tablet (Power + Vol Up) & go to install update from ADB
7. Go on computer and run in the opened terminal: ./adb sideload update.zip
8. Wait till the process is finished, restart and enjoy
Click to expand...
Click to collapse
I attempted the same activity and ran into the same issue (using different rooting methods, even though it has been stated no root is currently available), I can also confirm reloading the OS using the stock image works.
I don't think it really matters but I didn't rename the *.bin file to a *.zip; I used the following command (on Windows):
<ADB Tools working dir>\adb.exe sideload <path to bin>\update-kindle-40.5.9.1_user_591450020.bin
On a side note, with the release of FireOS 5.6.0.0, I am trying to hold my device at 5.5.0.0 in the event that a root method is discovered. The setup wizard doesn't allow you to skip the wireless setup, after connecting to a wireless network it wants to check for "system updates" - to work around this, I used my cellular hotspot, after connecting my kindle to the hotspot, it got me passed the wireless connection screen, where it then started to check for updates. I immediately turned off the hotspot. This allowed me to get past the setup wizard and prevent system updates/checks. (I suppose someone could setup a temp access point that doesn't have a connection or route to the internet, but I haven't tested this method.)
I installed G Play, G Services, G Framework apk's and NoRootFirewall. Once I blocked all of the Amazon Apps, I connected my kindle to my regular wireless network and the device hasn't been able to download 5.6.0.0.
That being said, on a side of caution, I turn off wireless when I turn off the tablet, to ensure that NoRootFirewall is up and running before connecting to WiFi on next boot. The device was able to start a download of 5.6.0.0 once and I had to boot into recovery to clear the partial/complete download of the OTA update to 5.6.0.0.
DaKat said:
The setup wizard doesn't allow you to skip the wireless setup, after connecting to a wireless network it wants to check for "system updates" - to work around this, I used my cellular hotspot, after connecting my kindle to the hotspot, it got me passed the wireless connection screen, where it then started to check for updates. I immediately turned off the hotspot. This allowed me to get past the setup wizard and prevent system updates/checks. (I suppose someone could setup a temp access point that doesn't have a connection or route to the internet, but I haven't tested this method.)
Click to expand...
Click to collapse
I can confirm that connecting to a router with no internet access will indeed allow you to get past the wifi setup portion. I bought an HD 10 7th gen. a few weeks ago and in order to prevent any updates before I could get a firewall installed, I plugged in an old router I had lying around. Once connected to the 'dummy' router I was able to continue setup.
As for disabling wifi before rebooting - I use NoRoot DF and have granted it usage access permission and never have any issues rebooting with wifi left on. This is certainly no guarantee that it is safe and I definitely wouldn't advise doing this if you haven't granted uap to your firewall, I'm simply sharing that I have had no issues.
Hi I ran into a bootloop while trying to get Xposed Framework. I get an "error: closed" in the terminal when I try to access adb shell. I have tried kill-server and it still wont work