Hi all,
I have been testing the wonderful ROMs for Inspire 4G, for example
AoCP: http://forum.xda-developers.com/showthread.php?t=2334107
moProject42: http://forum.xda-developers.com/showthread.php?t=2354076
I have 2 issues that I'd like to resolve. I would have posted in those threads, but I'm not allowed as a new user to this forum.
1. In both cases, after updating to the 4.2.2 ROM, I have not been able to shell in from my Win7 32bit laptop using ADB, as the device shows up as offline.
[Sat Sep 14 13:09:13 ~] $ adb devices
List of devices attached
HT19GT202387 offline
On the phone, my laptop's RSA Key was shown, and I accepted it, but it never seems to come online.
I have tried all the usual methods to try to fix this:
- upgraded my SDK and Google USB drivers for 4.2.2
- turn ADB debugging off/on on the device
- pull out/plug in the device
- Delete and reinstall the USB drivers on the laptop
2. After turning on Portable WiFi Hotspot, my 3G connection dies, so any devices that successfully connect to the hotspot are unable to browse the web.
Also, the device itself can no longer use 3G until I turn off the hotspot, and reboot the phone.
Any ideas? Thanks in advance.
Related
I'm running "Megatron" 1.0.4 on my Transformer. However this was occurring with the predecessor CM9 build (before the author renamed to it "Megatron"). I had switched from the Stock asus rom to CM9 a while ago, I was running the 3/29 build of CM9 (as mentioned above), which turned into Megatron.
I use adb to push and pull files to/from my tablet, as i find MTP to be utterly useless. I also use adb for shell access and other things when i'm tinkering with Android.
adb was working perfectly, On the 3/29 build of CM9. I was quite happy with 3/29, which is why i ran it for the entire month of april, without updating to "Megatron". However, one day, adb suddently stopped detecting my device. Restarting the adb server doesnt help, i've tried doing things like wiping cache on my device, nothing helps. I updated to Megatron 1.0.4 to see if that would help (thinking it was a software thing), with no data wipe, the tablet is again working perfectly except for the adb issue.
When i connect my tablet to my pc over its USB cable, the notification area disaplsys that usb debugging is enabled, but i still can't detect it with adb.
So, how can i continue to troubleshoot this? Is there some sort of debugging log i can view? Or enable some verbose mode?
Any suggestions would be great. Thanks!
Just did a full wipe, still, adb is unable to see my device.
Some extra info.
My PC is Linux, Fedora 16.
adb version:
$ adb version
Android Debug Bridge version 1.0.26
I havent updated it in a bit, but as stated earlier, neither it, nor the tablet's config changed when this stopped working.
Hi, I'm running Cyanogenmod 10.1.3 on my S3, the adb binary is up-to-date.
I'm trying to connect my S3 and my S4 or my S3 and my S Plus together via an OTG cable and usb debugging but it doesnt work.
The device gets listed but as "offline". Usually you get an prompt to accept the RSA key and you're done - that works if I connect any device to my PC - but if I want to connect any 2 devices together I just get an offline device and I have no idea why there is NO prompt at all.
Does anyone have an idea? Is therw any workaround?
Basically I just want to connect 2 devices (target >= 4.2.2) together via an otg host cable and adb.
Cheers
chris331022 said:
Hi, I'm running Cyanogenmod 10.1.3 on my S3, the adb binary is up-to-date.
I'm trying to connect my S3 and my S4 or my S3 and my S Plus together via an OTG cable and usb debugging but it doesnt work.
The device gets listed but as "offline". Usually you get an prompt to accept the RSA key and you're done - that works if I connect any device to my PC - but if I want to connect any 2 devices together I just get an offline device and I have no idea why there is NO prompt at all.
Does anyone have an idea? Is therw any workaround?
Basically I just want to connect 2 devices (target >= 4.2.2) together via an otg host cable and adb.
Cheers
Click to expand...
Click to collapse
Push
Push again - I'm also interested in that.
P.P.Push
Push
Sent from my GT-I9300 using XDA Premium 4 mobile app
..and again. :fingers-crossed:
Push
No one? Push..
Push
Adb on phone...
Well, I've been trying to get it though...have a SGW with kitkat rom and a SGT3 10.1 LTE on 4.2.2. Understand that the device need RSA auth to get it online. But the thing is, how to get it pop when we connect though phone. Updating the ADB on PC would help. So far, it works on kali linux (Serch for p2p-adb setup on kali linux tutorial [noob-friendly] by Jacker31). If we can get the adb updated on p2padb phone version...it might works.
If you connect via usb, then use adb tcpip 5555 you can connect over wifi until you reboot/disconnect (at which point you have to reconnect to usb again).
Is there a way of connecting over wifi without needing that initial connection? I'm used to slimroms where you only need to connect to usb once ever (for security reasons).
I've tried some of the `no root` apps but they don't work.
Please leave the development section free for development threads
Questions belong in the Q&A section
Thread moved
I'm late to this thread, but luckily, as of non-rooted Android 11 and up, adb works over wi-fi (without USB) on non-rooted Android phones via Developer options Wireless debugging switches.
Well guys, from the title you will think that its a regular windows drivers problem, but its not that straight. My Moto G is not even detecting to my laptop having windows 10 system (no yellow exclamation mark in device manager, not even an error message atleast) But at the same time my friends Moto G and Moto E is connecting in seconds and able to see that in device manager, also able to access files from mobile storage.
First time in my life I am feeling clueless even after trying every option to fix it.
First the basic system information for you:
Laptop: Dell Inspiron 1545 , Windows 10 OS Pro version (not K and KN version )
Drivers installed: Motorola device manager, Google SDK pack is also installed with its ADB driver.
About phone:
Moto G XT1033 16GB model[/COLOR]
OS: non rooted stock Lollipop 5.1 OS, Developer options enabled-USB debugging enabled
Now things I've already tried to fix this:
With Windows 10:
1) Downloaded Motorola device drivers from mototola website for Moto G. Installed, checked for update drivers. Thoroughly gone through Device manager and checked there but no sign of device at all.
2) NO problem with data cable because it can transfer data and not just a charging cable. confirmed and verified.
3) Checked USB ports for loose contacts at both sides of wire. Connected in every port for hope. No such problem.
4) Even after my Windows 10 is a Pro version I still tried to install Media Feature Pack as suggested by Microsoft site in case to overcome this problem but no luck.
5) Whenever I tried to run Motorola device manager, it just checks for new device software and goes off saying no updates.
Now even you can tell that there is no issue with windows system.
With Moto G:
1) Checked USB debugging, stay awake options In developer options.
2) Tried changing MTP option to PTP and reverse in setting - storage menu.
3) Checked every setting menu from android settings and apps to make sure no one is preventing this device from connecting.
4) Tried reseting mobile with to factory.
5) Pen drive is connecting to mobile via USB OTG and data transfer is working to and fro.
Important:
1) I can transfer my mobile files to PC by wireless method using apps, but I want to root my device. For that I have to connect it to PC to unlock the boot loader.
2) Before 2 months with the same system and windows 10, this moto g was connecting to PC and I was able to transfer files. But for now its not connecting at all.
Sorry for the long post but help me guys !!! What can you suggest me here if I am missing something ?
Thanks in advance.:good:
Things you could try:
- Use a Linux OS (live CD/USB) and run lsusb to see if anything shows up
- Put the phone into bootloader mode (fastboot) and see if the PC detects any USB device
If both of the above fail, the USB port in your phone may be defective.
_that said:
Things you could try:
- Use a Linux OS (live CD/USB) and run lsusb to see if anything shows up
- Put the phone into bootloader mode (fastboot) and see if the PC detects any USB device
If both of the above fail, the USB port in your phone may be defective.
Click to expand...
Click to collapse
Thanks for the quick reply. I tried to connect mobile in fastboot mode and now its saying [device descriptor request failed] in device manager. I am trying further and will also check linux os option that you suggested.
Tried both of your workarounds
When connected in fastboot mode it is showing [device descriptor request failed] in device manager.
Searched about it a lot and tried different solutions suggested for it..but its still not connecting properly.
2) checked with live cd and using command lsusb but no luck there ..
Now I'm really thinking that it's a USB port problem/hardware problem of mobile..but how that port is working fine for charging ??
Plzz suggest me any other methods of fix thus problem or is there any other way rather than connecting mobile to pc for unlocking Motorola devices bootloader ???
After a couple of hours trying to fix this problem with my XT1039, I solved it with this windows update: https://www.microsoft.com/en-us/download/confirmation.aspx?id=49919 .
All over the internet ppl say that Media Feature Pack for N and KN versions of Windows 10 should be installed but all the mirrors and 1st results goes to the PREVIOUS version which didn't solve my problem. With this latest version, everything is working now.
Hi,
I cannot connect to my Pixel 3 via adb any more. I last tried when I installed the system a year or so ago, and was able to. I am using a linux machine, and have tried the following:
- Two different computers
- Two different linux distros
- Many, many (new, high-quality) USB cables, both USB-C and USB-A/B
- Developer mode enabled
- USB debugging enabled, authorizations revoked and re-enabled
- Setting default USB configuration to File Transfer/USB tethering/MIDI/PTP/No data transfer
- Airplane mode
- Connecting over a USB-2.0 hub
- Booting the device to recovery mode, enabling adb
Regardless, I have the same outcome. The phone charges but no other recognition of being plugged in is made. That is, the computer cannot see the phone in 'adb devices', 'lsusb' or 'dmesg'. The phone doesn't see the computer either, in that it doesn't bring up the USB notification.
Any thoughts would be much appreciated. I am running lineageos 18.1, and the reason I wanted to connect via adb is to upgrade to 19.1.
Thanks in advance!
furrymonster said:
Hi,
I cannot connect to my Pixel 3 via adb any more. I last tried when I installed the system a year or so ago, and was able to. I am using a linux machine, and have tried the following:
- Two different computers
- Two different linux distros
- Many, many (new, high-quality) USB cables, both USB-C and USB-A/B
- Developer mode enabled
- USB debugging enabled, authorizations revoked and re-enabled
- Setting default USB configuration to File Transfer/USB tethering/MIDI/PTP/No data transfer
- Airplane mode
- Connecting over a USB-2.0 hub
- Booting the device to recovery mode, enabling adb
Regardless, I have the same outcome. The phone charges but no other recognition of being plugged in is made. That is, the computer cannot see the phone in 'adb devices', 'lsusb' or 'dmesg'. The phone doesn't see the computer either, in that it doesn't bring up the USB notification.
Any thoughts would be much appreciated. I am running lineageos 18.1, and the reason I wanted to connect via adb is to upgrade to 19.1.
Thanks in advance!
Click to expand...
Click to collapse
What version of platform-tools (adb) are you running?
I installed LineageOS 18.1 on my Pixel 3 back in April of this year.
I grabbed the latest platform-tools (33.0.1) for Linux at the time and I am able to connect, transfer files, etc. with no issues.
Below is the version I have installed on my Linux desktop . Hope this helps.
$adb --version
Android Debug Bridge version 1.0.41
Version 33.0.1-8253317
Installed as ~/bin/platform-tools-r33.0.1/adb