Help With ADT-1 - Google Chromecast

Hi,
I am trying to enable casting with 3rd party apps on my adt-1. However, first I have to figure out how to connect it with adb. I lost the developer cable, and have been trying to debug wirelessly. Developer mode is enabled, and usb debugging is enabled.
I have tried rebooting the device into fastboot, and just normally start it, but nothing works.
I have tried "adb connect 10.1.1.67:4321" and "adb connect 10.1.1.67", but they always say unable to connect.
Is there somewhere I can buy a dev cable, or just get wireless debugging working?

RedyTedy said:
Hi,
I am trying to enable casting with 3rd party apps on my adt-1. However, first I have to figure out how to connect it with adb. I lost the developer cable, and have been trying to debug wirelessly. Developer mode is enabled, and usb debugging is enabled.
I have tried rebooting the device into fastboot, and just normally start it, but nothing works.
I have tried "adb connect 10.1.1.67:4321" and "adb connect 10.1.1.67", but they always say unable to connect.
Is there somewhere I can buy a dev cable, or just get wireless debugging working?
Click to expand...
Click to collapse
Google disabled ADB over wifi in the latest update.. If you re-enable it like with terminal emulator and USB keyboard you should be ok. I'll try to post how-to later. I think its in the build.prop

If anyone is still working with this device (I plan to attempt to build LOS 15.1 soon), I just got mine without a developer cable. I'm not sure what command death2all110 is referring to in a terminal but what I did was transfer over a chinese root apk, root it with a USB mouse (sideways) and install TWRP with dd. Note mine came bootloader unlocked, I don't know if they all come that way or if the previous owner did.
(Extra sidenote: Developer cable/charing port appears to be EC U6 but I haven't tested the pinout.)

fyi, they were bootloader unlocked from the factory. pin-out for the connector has been found. check out the adt-1 dev community on g+ for more detail.

I also lost my developer cable and bricked the device recently. The EC U6 cable is nir working, as there is no external power and dosent power on. Anyway anyone can help?.

Related

Usb debugging not detected by pc

Yesterday i got new z1 after replacement.
previously i had rooted, unlocked bootloader and much more in my phone.
but now with the new phone i m always getting msg to connect with USB debugging even when the usb debugging is ON.
i m unable to root my phone.
plz help me with this
vshainky08 said:
Yesterday i got new z1 after replacement.
previously i had rooted, unlocked bootloader and much more in my phone.
but now with the new phone i m always getting msg to connect with USB debugging even when the usb debugging is ON.
i m unable to root my phone.
plz help me with this
Click to expand...
Click to collapse
Hey..
Could you please elaborate your issue a bit? Have you enabled USB debugging? What happens when you run adb devices on your computer?
Untouchab1e said:
Hey..
Could you please elaborate your issue a bit? Have you enabled USB debugging? What happens when you run adb devices on your computer?
Click to expand...
Click to collapse
yup i have enabled the usb debugging. when when i use any thing related to it i get this message - please connect Device with enabled USB-Debugging to your computer
Revoke usb debugging authorisation in developer options
gregbradley said:
Revoke usb debugging authorisation in developer options
Click to expand...
Click to collapse
nothing happens..
actually in previous phone, when turned on debugging for first time it asks something which is not appearing in this phone. i tried flashing 4.2.2 stock and tried again. I got the same result. i reverted back to stock 4.4.4 and still facing the problem
no one to help me :'(
Check any antivirus is not blocking anything
Please run a command window from adb and run this
Code:
adb devices
Make sure you do not have any other adb devices running (Bluestacks etc)
Try a differetnt PC to check if its the phone or PC

USB Debugging Issues

I am on the stock, rooted rom. I just got the OTA. But I need to flash reflash the stock recovery since I am rooted and on TWRP. But I can't seem to get USB debugging to work. I've tried rebooting both my PC and my phone, different ports, tried enabling and disable USB debugging in developer options, even tried resetting to default settings. But adb devices still shows blank on my PC. Any idea what is the issue? I usually got a pop up to show that ADB is being requested and I will have to agree to it but I cant seem to get that popup now.
sacredsoul said:
I am on the stock, rooted rom. I just got the OTA. But I need to flash reflash the stock recovery since I am rooted and on TWRP. But I can't seem to get USB debugging to work. I've tried rebooting both my PC and my phone, different ports, tried enabling and disable USB debugging in developer options, even tried resetting to default settings. But adb devices still shows blank on my PC. Any idea what is the issue? I usually got a pop up to show that ADB is being requested and I will have to agree to it but I cant seem to get that popup now.
Click to expand...
Click to collapse
I had similar problem before. Try this, with no Connection to PC, revoke usb debug authorisations, and restored default in deverloper option, setbupn USB debug again then connect to PC . if that don't work , try rebooting pc
Sent from my SM-T819 using Tapatalk

adb unauthorized, attempting to debloat

no matter what I do, my xz1c remains unauthorized whenever I attempt to connect via adb. I've scoured the internet and tried everything. has anyone had this issue with their xz1c and resolved it? I'd like to debloat my phone, but cannot because I cannot fully use adb. any ideas?
bleggy said:
no matter what I do, my xz1c remains unauthorized whenever I attempt to connect via adb. I've scoured the internet and tried everything. has anyone had this issue with their xz1c and resolved it? I'd like to debloat my phone, but cannot because I cannot fully use adb. any ideas?
Click to expand...
Click to collapse
enable developer options - enable usb debug
1. Turn off usb debugging and developer options
2. Restart your phone
3. Turn on developer options and usb debugging
4. Plug in usb cable
5. Watch your phone screen carefully for an authorization dialog - and accept this. If you skip it, or cancel it by accident then you need repeat above steps.
6. ADB is now authorized.
I tried exactly this. Still "unauthorized".
Maybe current update of Android 9 blocks it.
Dean F said:
1. Turn off usb debugging and developer options
2. Restart your phone
3. Turn on developer options and usb debugging
4. Plug in usb cable
5. Watch your phone screen carefully for an authorization dialog - and accept this. If you skip it, or cancel it by accident then you need repeat above steps.
6. ADB is now authorized.
Click to expand...
Click to collapse

USB transfer & communication completely broken,

Hi,
Using Lineage beckham jleebl 20191007, unlocked and working previously.
Charging over USB works fine.
USB debugging enabled.
Default USB configuration set to file transfer
HTML:
adb devices
results in "List of devices attached" & no devices
HTML:
fastboot devices
returns nothing
Above commands tried OS and bootloader, same results.
Cannot connect to transfer files, or adb push.
I have gone over many of the proposed solutions for file transfer not appearing as an option, none have worked. I took the phone to an repair shop, they cleaned the USB port, but essentially said, "lol, you're phone's broke". Said there was no obvious hardware issue.
Trying to boot into recovery mode just dumps me back into the bootloader. Can't push boot TWRP as fastboot can't communicate with device.
Any help would be SOOOO appreciated. Not being able to update the OS is causing many problems.
Thanks!!
hexagface said:
Hi,
Using Lineage beckham jleebl 20191007, unlocked and working previously.
Charging over USB works fine.
USB debugging enabled.
Default USB configuration set to file transfer
adb devices
results in "List of devices attached" & no devices
fastboot devices
returns nothing
Above commands tried OS and bootloader, same results.
Cannot connect to transfer files, or adb push.
I have gone over many of the proposed solutions for file transfer not appearing as an option, none have worked. I took the phone to an repair shop, they cleaned the USB port, but essentially said, "lol, you're phone's broke". Said there was no obvious hardware issue.
Trying to boot into recovery mode just dumps me back into the bootloader. Can't push boot TWRP as fastboot can't communicate with device.
Any help would be SOOOO appreciated. Not being able to update the OS is causing many problems.
Thanks!!
Click to expand...
Click to collapse
Wait, you took your phone to a repair shop, they told you it's busted,. So you are here looking for a magician, to whammy your phone? When you find one, please ask for lotto numbers, and forward them to me.
Check that you are using data capable usb cable, some cheap cables are only charge capable.
Otherwise, light a candle.
just 4 causes: 1.- moto drivers and Usb debugg ,2.- usb PC, 3.- Usb phone or 4.- usb cable. The option 4.- need repair.

Question no fastboot connection

I have had the Mi 11 since today, I wanted to unlock the boot loader, but my PC doesn't recognize it.
looked for adb drivers and downloaded them, did not work.
I turned on USB debugging.
can someone give me a tip or with which driver it would work?
Zimty86 said:
I have had the Mi 11 since today, I wanted to unlock the boot loader, but my PC doesn't recognize it.
looked for adb drivers and downloaded them, did not work.
I turned on USB debugging.
can someone give me a tip or with which driver it would work?
Click to expand...
Click to collapse
I had the same problem after sending a new device in exchange for my defective one. It was not recognized at all on the USB port. In Fastboot mode only in sideload mode. I just did a factory reset. The device was then displayed as unauthorized in ADB mode, but Fastboot mode is sufficient to unlock the bootloader It was then displayed correctly there. However, the waiting time has increased to over 500 hours. The first device lasted 260 hours. No matter. Now it's in the drawer until August.

Categories

Resources