Related
Hi all.
I have seen this in another kind of devices but haven't found thread related about Kindle Fire (1st gen).
A little introduction:
- My kindle was in CM10 and I noticed it started to be detected as Unknown Device in Windows, so
- I used TWRP to flash 6.3.1 stock ROM BUT forgot to wipe before flashing and rebooting. In that moment my situation was an endless loop wih the Kindle being rebooted after 15 seconds aproximately.
- I modified a cable to make it "factory cable" but even in fastboot (plain kindle fire logo) the Unknown Device was there.
- After many tries I managed to make a Reset to factory defaults in Android in the 15 seconds
- Currently the kindle is in stock ROM but still is not correctly detected.
Of course, I have re-installed the drivers in my computer and even tried in a fresh windows installation with no previous drivers without luck. Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
So, if some of you have any idea to try, please tell me. I have the factory cable and the back cover of the kindle removed... ready for anything!
Thank you for your time!
soukron said:
Hi all.
Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
Click to expand...
Click to collapse
This is the part I mentioned before about dmesg messages:
Code:
[ 234.956030] usb 2-5: >new full-speed USB device number 4 using ohci_hcd
[ 235.136035] usb 2-5: >device descriptor read/64, error -62
[ 235.420038] usb 2-5: >device descriptor read/64, error -62
[ 235.700026] usb 2-5: >new full-speed USB device number 5 using ohci_hcd
[ 235.880055] usb 2-5: >device descriptor read/64, error -62
[ 236.164040] usb 2-5: >device descriptor read/64, error -62
[ 236.444025] usb 2-5: >new full-speed USB device number 6 using ohci_hcd
[ 236.852030] usb 2-5: >device not accepting address 6, error -62
[ 237.028025] usb 2-5: >new full-speed USB device number 7 using ohci_hcd
[ 237.436025] usb 2-5: >device not accepting address 7, error -62
[ 237.436037] hub 2-0:1.0: >unable to enumerate USB device on port 5
And there's no reference in lsusb:
Code:
[email protected]:~$ lsusb
Bus 001 Device 004: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive
Bus 001 Device 005: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 002 Device 002: ID 04ca:0022 Lite-On Technology Corp.
Bus 002 Device 003: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/10p, 12M
|__ Port 3: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 4: Dev 3, If 0, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 1, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 2, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 3, Class=HID, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/10p, 480M
|__ Port 9: Dev 5, If 0, Class=>ifc, Driver=rtl8187, 480M
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
soupmagnet said:
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
Click to expand...
Click to collapse
I'm trying to follow this thread http://forum.xda-developers.com/showthread.php?t=1636883 but I don't know how to check if the "short trick" is well performed or not. Is there anything I should notice? At this moment if I make the short trick and plug in the usb connector, nothing seems to be working in the kindle but dmesg is continuously showing errors like previous ones.
Regards,
Are you using Firekit? What command?
"That's a special kind of stupid. The kind that makes me laugh"
I'm still in the step of the process when I make the short trick, plug the usb and the kindle should be detected. Should I try the usbboot commands even when there's no kindle entry in lsusb output?
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
Click to expand...
Click to collapse
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
soukron said:
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
Click to expand...
Click to collapse
Are you using a 32bit or 64bit machine? If you have SoupKit installed, option 2 should have installed 32bit libs, but sometimes it fails...mostly due to Ubuntu servers and them trying to make 32bit libs obsolete. If you're running a 64bit machine, try installing 32bit libs again and see if you get any errors.
Code:
sudo apt-get install ia32-libs
Also since you have SoupKit installed, run it and select option 4 to launch the Firekit. There's really no difference in using Firekit and manually entering the commands for Rekindle but it makes things a little easier. Select "usb_install_fff_twrp". The important thing to know about the "usb_fix_parts..." and "usb_install..." commands in Firekit is that they both use "fastboot boot ..." instead of "fastboot flash ..." to install TWRP and FFF. Meaning, if you reboot or shut the device down before actually installing a bootloader, the device won't turn back on and you'll have to do the shorting trick again.
That being said, from the moment you make the short, you only have about 2 seconds to plug the device in and have Linux detect it before the CPU resets and you have to start all over again.
Hold the power button for 10-15 seconds to make sure the CPU is off before attempting the short.
Launch Firekit and select "usb_install_fff_twrp". When the command is run, you will get the "Waiting for OMAP4 device..." prompt. Let it wait.
To do the shorting trick...
Something I have found to be most useful in this situation is to use a sharp pair of tweezers or safety pin to make the short.
Keep the device flat on a desk or table with the USB connection pointed away from you. Use one hand to hold the short, one hand to plug the device in, and use your body against the other end of the device as leverage as you plug it in.
Using a safety pin, stick the sharp end of the safety pin into the short point and press it in a little to keep it from sliding off when you plug the device in. Squeeze the other end of the safety pin or tweezers to make contact with the metal frame and immediately plug the device in while holding the short.
If the tweezers slip or make contact with the frame before you are ready, hold the power button for 10-15 seconds to make sure the device is completely shut down and try again.
You should see something going on in the terminal to let you know it's working...let it finish.
It might take a few attempts to get the timing right but persistence (and practice) is key...don't give up.
Follow these instructions and I'm positive you'll get it working again. Good luck.
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
soukron said:
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
Click to expand...
Click to collapse
When the OMAP4 device is detected, you will see something similar to this in the terminal:
http://forum.xda-developers.com/attachment.php?attachmentid=1262650&d=1345043823
That will temporarily install the bootloader, which is likely the cause of Linux not being able to detect it in the first place. When you see the yellow triangle on your Kindle, you'll know the Firekit worked. But you still have to permanently install the bootloader via fastboot (or TWRP if accessible) before you reboot the device.
Will it work to get Linux to detect it? Most likely, but there's no way to know for sure until you get a new bootloader installed.
On second thought...
I just realized you may not even have to do that in the first place. Lucky you? If your device is working properly as you said, boot into Android and open up the Terminal Emulator. Make sure the u-boot.bin is on your sdcard and enter the following:
Code:
su
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
reboot
See if that works.
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
soukron said:
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
Click to expand...
Click to collapse
Nope...you need root access to use the 'dd' command.
soupmagnet said:
Nope...you need root access to use the 'dd' command.
Click to expand...
Click to collapse
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
soukron said:
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
Click to expand...
Click to collapse
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds..
Sent from my GT-I8350 using Board Express
prahladvarda said:
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds.
Click to expand...
Click to collapse
Unfortunately, it won't work in this situation.
Hi I have rooted my Samsung Galaxy Tab 3 8" 3g (SM 311) and I am in the need to install the AX88772 USB to 10/100 Fast Ethernet (in my job they allow only ethernet cable connection and not wifi).
I do not have the knowlege to complile the kernel or do whatever it needs.
Is there a way to install it as I do in a pc or mac or the recompile is nessesary?
Any help will be appriciated.
Thanks in advance
Did you have success with installing the adapter so far ?
Hello,
my Axis LAN adapter (0b95:772b) is beeing recognized by stock android in tab 3 10 automatically = eth0 device is created after plug-in, however there seems no client app trying to configure it (like dhclient for DHCP etc.). have anyone experience how to, ideally automatic, use and configure it?
thanks
I've seen reports of the VK815 being rooted and would like to root mine. Is there someone who has a VK815 and has rooted it who is willing to share how they accomplished it?
I have 'adb' available and working, the developer mode enabled, and can talk to the phone. Trying to attain superuser from the 'adb shell' doesn't work because the 'su binary' is missing. 'adb reboot recovery' gives the ''dead android' and the 'power/volume -' key combination results in a normal boot.
Thanks,
Jim
I rooted my vk815 with one click root from the g3 section. Not sure yet how to post links I'm new to xda...
---------- Post added at 12:56 AM ---------- Previous post was at 12:49 AM ----------
http://forum.xda-developers.com/showthread.php?t=3056951
That looks like a solution for those who have Windows PC's connected to their tablets. I'm a linux only and should have put that in my original post.
I guess I could look at the script and see if there's any clues inside it.
Thanks,
Jim
There is a python script for using the send command with the files. On my phone and at work, so difficult for me to look up, but I'm sure googling send command LG python will turn it up (probably under g3 or g4 forums...)
danaff37 said:
There is a python script for using the send command with the files. On my phone and at work, so difficult for me to look up, but I'm sure googling send command LG python will turn it up (probably under g3 or g4 forums...)
Click to expand...
Click to collapse
I've seen it and given it a try. The writer and everyone else in the thread look like they aren't working with a VK815. The VK815 doesn't trigger loading of the 'serial' module. I don't have one on my system so that looks like a problem. I keep getting this error message:
[email protected]:/root# qcdlcomm.py /dev/ttyUSB0
Traceback (most recent call last):
File "/home/jim/Desktop/qcdlcomm.py", line 13, in <module>
import serial
ImportError: No module named serial
For anyone who's interested; the python script is here about a quarter of the way down the page. hxxp://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772/page46 (Change the x's to t's)
Jim
Seems like the kernel can't figure out what chip is handling the serial I/O for the tablet so it only loads 'usbserial_generic'. That module can't change any of the comm parameters. The error messages now want a more specific module loaded before running the python script.
[1655862.790132] usb 1-9: new high-speed USB device number 9 using ehci-pci
[1655862.905356] usb 1-9: New USB device found, idVendor=1004, idProduct=6293
[1655862.905359] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1655862.905361] usb 1-9: Product: LGE Android Phone
[1655862.905363] usb 1-9: Manufacturer: LG Electronics Inc.
[1655862.905365] usb 1-9: SerialNumber: VK815275a2846
[1655862.905753] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655862.905755] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655862.905757] usbserial_generic 1-9:1.0: generic converter detected
[1655862.905816] usb 1-9: generic converter now attached to ttyUSB0
[1655862.946215] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
[1655862.946343] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[1655862.946356] usbserial_generic 1-9:1.0: device disconnected
[1655863.049404] usb 1-9: reset high-speed USB device number 9 using ehci-pci
[1655863.164195] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655863.164201] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655863.164203] usbserial_generic 1-9:1.0: generic converter detected
[1655863.164288] usb 1-9: generic converter now attached to ttyUSB0
[1655863.164329] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
Jim
jowski said:
Seems like the kernel can't figure out what chip is handling the serial I/O for the tablet so it only loads 'usbserial_generic'. That module can't change any of the comm parameters. The error messages now want a more specific module loaded before running the python script.
[1655862.790132] usb 1-9: new high-speed USB device number 9 using ehci-pci
[1655862.905356] usb 1-9: New USB device found, idVendor=1004, idProduct=6293
[1655862.905359] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1655862.905361] usb 1-9: Product: LGE Android Phone
[1655862.905363] usb 1-9: Manufacturer: LG Electronics Inc.
[1655862.905365] usb 1-9: SerialNumber: VK815275a2846
[1655862.905753] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655862.905755] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655862.905757] usbserial_generic 1-9:1.0: generic converter detected
[1655862.905816] usb 1-9: generic converter now attached to ttyUSB0
[1655862.946215] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
[1655862.946343] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[1655862.946356] usbserial_generic 1-9:1.0: device disconnected
[1655863.049404] usb 1-9: reset high-speed USB device number 9 using ehci-pci
[1655863.164195] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655863.164201] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655863.164203] usbserial_generic 1-9:1.0: generic converter detected
[1655863.164288] usb 1-9: generic converter now attached to ttyUSB0
[1655863.164329] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
Jim
Click to expand...
Click to collapse
I doubt there are drivers for linux for a g4 in Linux, and I know people used the script for that. You are doing this in download mode? I can't remember since it's been a while for me setting it up, but does the Android sdk install the generic android USB drivers in Linux?
danaff37 said:
I doubt there are drivers for linux for a g4 in Linux, and I know people used the script for that. You are doing this in download mode? I can't remember since it's been a while for me setting it up, but does the Android sdk install the generic android USB drivers in Linux?
Click to expand...
Click to collapse
The kernel modules handle what drivers would do in Windows.
I'm in the download mode and if I boot normally instead of into download; I can talk to the tablet with adb. I'm thinking that maybe if I comment out the serial port settings code, the script might work. I'll try that later.
Jim
jowski said:
The kernel modules handle what drivers would do in Windows.
I'm in the download mode and if I boot normally instead of into download; I can talk to the tablet with adb. I'm thinking that maybe if I comment out the serial port settings code, the script might work. I'll try that later.
Jim
Click to expand...
Click to collapse
I just know in the past for fast boot mode on other devices, I had to run the Android sdk tools and add some udev rules. But I can't remember if the sdk tools was simply for executables, or for modules/drivers
danaff37 said:
I just know in the past for fast boot mode on other devices, I had to run the Android sdk tools and add some udev rules. But I can't remember if the sdk tools was simply for executables, or for modules/drivers
Click to expand...
Click to collapse
When I can talk to the tablet; adb works but fastboot doesn't. 'adb reboot recovery' gives the dead android. This is turning into a real adventure.
There has to be something after 'modprobe usbserial' to load a specific module on the PC so it can talk to the VK815. Would the Windows ddl's give a clue?
Jim
Well, I'll be go to ....
Commenting the block of code that sets the serial port settings worked! I went into the download mode with the key press (power off, volume +, connect the usb cable, wait for Firmware Update screen, release volume +) and ran the script and was talking to the tablet. Looks like the next step is to load the goodies first and then try the manual commands to install root.
Whatcha think gang? I'm thinking we're almost there and how cool is that!!!
Jim
edit: [email protected]:/# ./qcdlcomm.py /dev/ttyUSB0
Traceback (most recent call last):
File "qcdlcomm.py", line 47, in <module>
port=sys.argv[-1]
File "/usr/lib64/python2.7/site-packages/serial/serialutil.py", line 282, in __init__
self.open()
File "/usr/lib64/python2.7/site-packages/serial/serialposix.py", line 296, in open
self._reconfigurePort()
File "/usr/lib64/python2.7/site-packages/serial/serialposix.py", line 325, in _reconfigurePort
raise SerialException("Could not configure port: %s" % msg)
serial.serialutil.SerialException: Could not configure port: (25, 'Inappropriate ioctl for device')
Any ideas??? I changed the 'ser' block to
ser = serial.Serial(
port=sys.argv[-1]
)
I'm back to thinking it's a module that needs to be loaded.
Previous post errors were due to 'cdc_acm' being reloaded and me not checking that before running the script. Fixed that and reloaded usbserial. Now the errors are:
[email protected]:# qcdlcomm.py /dev/ttyUSB0
Special commands: ENTER, LEAVE, exit
# ENTER
Traceback (most recent call last):
File "/home/jim/Desktop/qcdlcomm.py", line 100, in <module>
cmd(input)
File "/home/jim/Desktop/qcdlcomm.py", line 87, in cmd
rawcmd(commands[input])
File "/home/jim/Desktop/qcdlcomm.py", line 63, in rawcmd
ser.write(input)
File "/usr/lib64/python2.7/site-packages/serial/serialposix.py", line 490, in write
if not self._isOpen: raise portNotOpenError
serial.serialutil.SerialException: Attempting to use a port that is not open
So much for talking to the tablet.
Jim
I tried usb_modeswitch and got something that may be encouraging. I'll post the command and output so someone who knows a bit about usb_modeswitch can shed some light.
[email protected]:/home/jim/Desktop# usb_modeswitch -p 0x6293 -v 0x1004 -M a1
Look for default devices ...
product ID matched
Found devices in default mode (1)
Access device 067 on bus 001
Get the current device configuration ...
OK, got current device configuration (1)
Use interface number 0
Use endpoints 0x01 (out) and 0x81 (in)
Not a storage device, skip SCSI inquiry
USB description data (for identification)
-------------------------
Manufacturer: LG Electronics Inc.
Product: LGE Android Phone
Serial No.: VK815275a2846
-------------------------
Looking for active driver ...
OK, driver detached
Set up interface 0
Use endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
Sending the message returned error -1. Try to continue
Reset response endpoint 0x81
Reset message endpoint 0x01
Could not reset endpoint (probably harmless): -99
-> Run lsusb to note any changes. Bye!
There are other messages that can be sent as part of the command. I'm wondering if this is how we can gain access to the device using linux.
Jim
Tried the windows method from an XP machine. Keep getting a "Device cannot start. (Code 10)" error. Tried uninstalling and reinstalling the LG drivers along with the VZW drivers. Also tried using only the VZW drivers. Same results. The device manager says the DIAG port is COM16 but Send_Command.exe can't open port 16.
Anyone had success rooting from XP or do I need to try Windows 7?
Jim
jowski said:
Tried the windows method from an XP machine. Keep getting a "Device cannot start. (Code 10)" error. Tried uninstalling and reinstalling the LG drivers along with the VZW drivers. Also tried using only the VZW drivers. Same results. The device manager says the DIAG port is COM16 but Send_Command.exe can't open port 16.
Anyone had success rooting from XP or do I need to try Windows 7?
Jim
Click to expand...
Click to collapse
I tried XP but the device drivers wouldn't install. 7 worked great for me tho. But I'm not real good with Windows possibly some others would know better??
So my tablet today prompted me to update to 11A. But since it's rooted, so it didn't go thru. Does anyone know what we can do with that info? Like to keep root and update?
I gave up on finding a linux solution and did it with WinDoze 8. A root canal has to be less painful. At least it's rooted now.
I'm holding off on the update until after I get a few apps loaded that require root access. I wish there was a way to turn off the updates and nags.
Jim
I think the linux answer to talking to the VK815 involves the BCM2079x on the tablet. Could that mean the linux box trying to load a serial driver would need to do something like 'modprobe bcm2079x'? If so, where to we find the config for it in the kernel .config?
Jim
I know this is an old thread, but maybe someone can send me in the right direction. My non-rooted VK815 updated to 6.0 and ruined the battery life. So, I'd like to root it. I can only find threads on rooting the previous version - has anyone rooted the 6.0 version?
Hi all
I run a gentoo linux box and I have adb 'USB debugging' enabled on 1+5T.
When I plug in the cable I can choose
- Charge only <- choosen automatically
- Transfer files (MTP)
- Transfer photos (PTP)
- Use device as MIDI
But nevertheless I see an ISO mounted with files
- AndroidFileTransfer(OSX).dmg
- adb_config_Linux_OSX.sh
- OnePlus_USB_Drivers_Setup.exe
- OnePlus_setup.exe
If I choose MIDI the directory is unmounted and I can use adb.
But this choice is not remembered, ...
So it sounds a bit odd:
- why would anything mount if Charge only is chosen as default?
- why is there no choice to just ADB?
Also 'Wireless ADB debugging' does not connect (when enabled, that is) to port 5555
unable to connect to 192.168.168.151:5555
And indeed no ports are open on device when scanned with nmap from linux box.
Does this ring a bell? Is there a way to save USB adb as default and make Wireless ADB work?
Other than that : great device I am very happy and impressed.
ABD should work no matter what option you choose. (Assuming USB debugging is enabled)
Are you rooted? Wireless ADB needs root.
Heisenberg420 said:
ABD should work no matter what option you choose. (Assuming USB debugging is enabled)
Are you rooted? Wireless ADB needs root.
Click to expand...
Click to collapse
I would think so. But what should be is not always.
Dior DNA said:
I would think so. But what should be is not always.
Click to expand...
Click to collapse
Wise words.
IDK what to tell ya. I'm able to access ADB no matter what option is selected and I'm able to see port 5555 open with nmap (adb wireless, no cable). Maybe a firewall is interfering?
Heisenberg420 said:
Wise words.
IDK what to tell ya. I'm able to access ADB no matter what option is selected and I'm able to see port 5555 open with nmap (adb wireless, no cable). Maybe a firewall is interfering?
Click to expand...
Click to collapse
Hi I am able to do so from Ubuntu as well. Not so from gentoo even if I delete udev entries.
My point is, why is there, under any circumstances, a mount if charge only is configured.
Can linux host overrule phone setting?
Cable Used: anker powerline+ (https://www.amazon.com/Anker-Powerline-Durability-Samsung-Nintendo/dp/B01GN0M6NE)
When copying the same file from a my labtop using linux i can copy in about 2mins (3gb movie)
On Windows 7 that file will take more than 5 usually 8 (windows dialog box says 12)
Ive reinstalled intel usb3 drivers, set my xhci to smart auto, handoff enabled
Android drivers as well as adb are installed
Using USB Device Tree Viewer i can see that it is connected to a usb 3.0 HUB and:
Device Bus Speed : 0x03 (SuperSpeed)
Meaning it should have usb 3.0 speeds.
What am i doing wrong here?