Develop Bugs

Unlocking Is easy

I have had this watch for about an hour now... ANNNND the bootloader is unlocked...
easy steps below
Note For Clarification: you CANNOT do this over Bluetooth.
Enable ADB and connect to computer.
reboot into fastboot using: adb reboot-bootloader
then issue command: Fastboot Oem Unlock
accept the prompt on the watch.
then reboot the watch...
Piece of cake.
Now... about that boot logo...

Yeah its like a nexus in that regard. And no I don't have the watch yet but have ordered it today.

I would unlock mine but there's no reason to yet. I always unlock my Nexus devices first thing yet with the watch I would like to keep it stock for now.

No reason to unlock, until someone creates twrp, and root.

suzook said:
No reason to unlock, until someone creates twrp, and root.
Click to expand...
Click to collapse
I agree, a factory reset on it only takes 2-3 minutes so its not like a phone where it takes forever to set up again.

ApoKyla said:
I have had this watch for about an hour now... ANNNND the bootloader is unlocked...
easy steps below
Enable ADB and connect to computer.
reboot into fastboot using: adb reboot-bootloader
then issue command: Fastboot Oem Unlock
accept the prompt on the watch.
then reboot the watch...
Piece of cake.
Now... about that boot logo...
Click to expand...
Click to collapse
Hello, may iam to stupid, but i cant force a reboot.
i connect phone via USB to PC, then Bluetooth to the watch, enabled ADB,...and i can see the watch but when i want reboot, only the phone reboots not the watch.
i see this...
C:\ADB>adb devices
List of devices attached
FA2CJW201138 device (PHONE)
localhost:4444 device (WATCH)
regards
UPDATE:
Whit this i can reboot the Watch into FASTBOOT MENU.
C:\ADB>adb -s localhost:4444 reboot-bootloader
but how can i unlock it now?? (after rebooting, there is no connection to the Phone)

Carlossianz0815 said:
Hello, may iam to stupid, but i cant force a reboot.
i connect phone via USB to PC, then Bluetooth to the watch, enabled ADB,...and i can see the watch but when i want reboot, only the phone reboots not the watch.
i see this...
C:\ADB>adb devices
List of devices attached
FA2CJW201138 device (PHONE)
localhost:4444 device (WATCH)
regards
UPDATE:
Whit this i can reboot the Watch into FASTBOOT MENU.
C:\ADB>adb -s localhost:4444 reboot-bootloader
but how can i unlock it now?? (after rebooting, there is no connection to the Phone)
Click to expand...
Click to collapse
Have not done it, but fastboot takes the -s parameter as well. So I would try:
fastboot -s localhost:4444 oem unlock

brizey said:
Have not done it, but fastboot takes the -s parameter as well. So I would try:
fastboot -s localhost:4444 oem unlock
Click to expand...
Click to collapse
Hi,
no, the fastboot command does not work,it stops with the message < waiting for device >

Cannont get USB drivers to work
I tried bith google USB drivers and ClockWorkMod universal ADB drivers and cannot get my Huawei to properly connect. I tried two separate computers with the same result. Each time the USB drivers seem to install but the watch shows up under other with exclamation point. My objective is to side load watch face apks to see what I can accomplish with running this watch under iOS.
ADB debugging is on and I also tried also turning on Bluetooth debugging. Intersetingly Bluetooth debugging does kick in.
I'm a novice at BT debugging and any attempt to communicate with the watch following on-line guidance did not work.
Any suggestions/help would be appreciated.
---------- Post added at 05:19 PM ---------- Previous post was at 05:18 PM ----------
I tried both google USB drivers and ClockWorkMod universal ADB drivers and cannot get my Huawei to properly connect. I tried two separate computers with the same result. Each time the USB drivers seem to install but the watch shows up under other with exclamation point. My objective is to side load watch face apks to see what I can accomplish with running this watch under iOS.
ADB debugging is on and I also tried also turning on Bluetooth debugging. Intersetingly Bluetooth debugging does kick in.
I'm a novice at BT debugging and any attempt to communicate with the watch following on-line guidance did not work.
Any suggestions/help would be appreciated.

I still use the old pdanet drivers...they seem to work with everything.

Hi Guys,
still can not work whit the watch after rebooting, may i missunderstand somthing.
Thats the way i do:
From PC to Phone via USB DEBUGING, from PHONE to WATCH via BLUETOOTH DEBUING!
but after reboot into bootloader, i can not talk to the watch anymore, so how can i put the files on the watch???
thanks for help!!!

Carlossianz0815 said:
Hi Guys,
still can not work whit the watch after rebooting, may i missunderstand somthing.
Thats the way i do:
From PC to Phone via USB DEBUGING, from PHONE to WATCH via BLUETOOTH DEBUING!
but after reboot into bootloader, i can not talk to the watch anymore, so how can i put the files on the watch???
thanks for help!!!
Click to expand...
Click to collapse
Enable ADB on the watch (settings/about/tap build# 10 times then developer options, ADB enable)
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
reboot into fastboot using: adb reboot-bootloader
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Sent from my SM-N920T using XDA mobile app

Thanks for replay,
last night i got it, via Bluetooth.
Thanks all, now i have the new kernel and recovery.
I think the new kernel works faster and need less power then the orig one.
best Regards

Thank you !

az93civic said:
Enable ADB on the watch (settings/about/tap build# 10 times then developer options, ADB enable)
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
reboot into fastboot using: adb reboot-bootloader
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Sent from my SM-N920T using XDA mobile app
Click to expand...
Click to collapse
I have the same problem. Once it boots into bootloader on the watch, cmd prompt on the pc becomes unresponsive and i cannot type anything else in. Were you able to fix yours
---------- Post added at 03:27 AM ---------- Previous post was at 03:04 AM ----------
wookie_666 said:
I have the same problem. Once it boots into bootloader on the watch, cmd prompt on the pc becomes unresponsive and i cannot type anything else in. Were you able to fix yours
Click to expand...
Click to collapse
just realised i should probably be using the magnetic charger, because when i reboots it looses bluetooth connection
ill try when i get home

az93civic said:
...
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Click to expand...
Click to collapse
What does "issue command: fastboot oem unlock" mean exactly? There is a little red action name which I can cycle between "Reboot", "Shutdown", "Reboot-bootloader" and "Reboot-recovery", none of which seem remotely correct. I went into "Reboot-recovery" to see whether there was further stuff in there, but nothing seems relevant.

Trejkaz said:
What does "issue command: fastboot oem unlock" mean exactly? There is a little red action name which I can cycle between "Reboot", "Shutdown", "Reboot-bootloader" and "Reboot-recovery", none of which seem remotely correct. I went into "Reboot-recovery" to see whether there was further stuff in there, but nothing seems relevant.
Click to expand...
Click to collapse
So what this means is you need to have ADB and fastboot setup on your computer. From there, you will need to go into developer settings on the watch and enable ADB debugging. Then once you have that enabled, go to where you set up ADB on your computer and type in those commands provided.
P.S. If you're sitting there not sure what ADB means and how to set it up, you NEED to do more research before trying anything like this.

dbroer91884 said:
So what this means is you need to have ADB and fastboot setup on your computer. From there, you will need to go into developer settings on the watch and enable ADB debugging. Then once you have that enabled, go to where you set up ADB on your computer and type in those commands provided.
P.S. If you're sitting there not sure what ADB means and how to set it up, you NEED to do more research before trying anything like this.
Click to expand...
Click to collapse
Actually, it has been a bit of a ride.
I knew of adb already from my watch face development so I had initially wondered whether fastboot was a subcommand of that. I didn't expect it to be another command in the SDK at all for some reason. But yep, it's in the same place as adb, and it works, and now everything flashed fine. I don't know why I didn't search my computer for a file with that name, since that would have located it.
Un-hiding the development options is mentioned on the wear developer site so that was fairly easy to set up. The only hard part was that they gave a text-only explanation, but this watch came set to Chinese, so it was a bit fun to figure out which button to press to "confirm" a dialog. I recognised the first option as the "no" and the second option turns out to have been the "yes", but there are more options below that I still don't know what they are, lol.

suzook said:
No reason to unlock, until someone creates twrp, and root.
Click to expand...
Click to collapse
Custom recovery already available by skin 1980. Take a look here. Custom kernel with custom twrp.
http://forum.xda-developers.com/showthread.php?t=3219596
I was thinking to upload a custom rom for Huawei watch “slim system.img, deodexed, root and more " But I need someone to try it first. I am still waiting for my watch. I will upload if anyone is interested.
Sent from my Nexus 6P using Tapatalk 2

janjan said:
Custom recovery already available by skin 1980. Take a look here. Custom kernel with custom twrp.
http://forum.xda-developers.com/showthread.php?t=3219596
I was thinking to upload a custom rom for Huawei watch “slim system.img, deodexed, root and more " But I need someone to try it first. I am still waiting for my watch. I will upload if anyone is interested.
Sent from my Nexus 6P using Tapatalk 2
Click to expand...
Click to collapse
You are quoting me from 4 mos ago? LMFAO!

Strange behavior after update to Nougat.

My phone is full stock. Bootloader blocked, S-On, no root. After that bloody update i cant charge my phone normally. To charge it i must turn it off (not restart - full power down) plug charger - wait few second for battery symbol. Then turn phone on. And it will charge in normal time. I can live with that, but it irritating as my mother in law.
Second problem is much worse. None of my PC/Laptops see my M9. I trying bunch of USB cables (working perfect with other stuff) but not with M9.
I was try root my phone (kingoroot/towelroot/supersu 2.77/8/9) - no effect.
I can`t unlock bootloader, coz ADB dont see my phone.
I try ADB wifi - but it still device connectet to PC via cable in first step.
I preform more then 5 factory reset. Nothing has changed.
Sure - i can connect via AirDroid and still have acces to anything i need...
The question is:
What can i do to unlock bootloader/flash android 6.0 except waiting for official fix.
Sorry for bad eng and thanks for reading.

Enable developer options and then look for "oem unlocking" and just a bit down from there "usb debugging".
You also need look for an up to date rooting tutorial for nougat and a tutorial to return back to 6.0. You have to do a lot of reading BEFORE you start.
Beamed in by telepathy.

shivadow said:
Enable developer options and then look for "oem unlocking" and just a bit down from there "usb debugging".
You also need look for an up to date rooting tutorial for nougat and a tutorial to return back to 6.0. You have to do a lot of reading BEFORE you start.
Beamed in by telepathy.
Click to expand...
Click to collapse
Enable dev ops and turn on usb debbuging/oem unlocking was one of the first step.
Every single rootong option need cable conection - so i cant use it. And in that point we back to the begining...

Danjou667 said:
My phone is full stock. Bootloader blocked, S-On, no root. After that bloody update i cant charge my phone normally. To charge it i must turn it off (not restart - full power down) plug charger - wait few second for battery symbol. Then turn phone on. And it will charge in normal time. I can live with that, but it irritating as my mother in law.
Second problem is much worse. None of my PC/Laptops see my M9. I trying bunch of USB cables (working perfect with other stuff) but not with M9.
I was try root my phone (kingoroot/towelroot/supersu 2.77/8/9) - no effect.
I can`t unlock bootloader, coz ADB dont see my phone.
I try ADB wifi - but it still device connectet to PC via cable in first step.
I preform more then 5 factory reset. Nothing has changed.
Sure - i can connect via AirDroid and still have acces to anything i need...
The question is:
What can i do to unlock bootloader/flash android 6.0 except waiting for official fix.
Sorry for bad eng and thanks for reading.
Click to expand...
Click to collapse
If u do not hear the "connected" sound in windows when plugged in, u may have a faulty USB connection.
Try blowing some air into it or GENTLY clean it.
Good luck!

Fain11 said:
If u do not hear the "connected" sound in windows when plugged in, u may have a faulty USB connection.
Try blowing some air into it or GENTLY clean it.
Good luck!
Click to expand...
Click to collapse
I try all (4) cables/all 10 usb port on all of my computers. I don`t see dirt in port phone/pc.
i just turn on speakers. Yea i hear "plong". But my PC dont see my phone. And adb dont see it either.

Danjou667 said:
I try all (4) cables/all 10 usb port on all of my computers. I don`t see dirt in port phone/pc.
i just turn on speakers. Yea i hear "plong". But my PC dont see my phone. And adb dont see it either.
Click to expand...
Click to collapse
Try re-installing HTC drivers.
See here the latest:
https://androidmtk.com/download-htc-usb-drivers

lastest drivers already in use. But i made small step forward. ADB see my phone. But i stuck @waiting for device... (child crying bbs)

Definitely sounds like a driver problem. Maybe try running a live Linux disc and run adb from that?

philicibine said:
Definitely sounds like a driver problem. Maybe try running a live Linux disc and run adb from that?
Click to expand...
Click to collapse
Perkeleen vittupää! bloody driver. I download drivers from http://droididea.com/download-android-usb-drivers-for-pc-samsung-lg-motorola-sony-oppo-and-others/ adb see my phone on every one goddamn port on all of my comps.
Linux u say... ok maybe it will help but what distro of linux?

Ubuntu is good if your new to it.

philicibine said:
Ubuntu is good if your new to it.
Click to expand...
Click to collapse
Ubuntu hate my GTX 970... Atm linux mint is my second os. And... suprise... linux don`t see my htc either. i install MTP, ADB and android tools - nothing change. Except one thing. adb devices command return 0 devices... I need to learn a lot of new things.

You have enabled USB debugging right? In developer options on the phone?

sure thing. Unlock bootloader in programing options enabled too. Ha! mint see my htc when i type lsusb. So another small step forward. Now i only must figure out why adb dont see my phone.

Can you get into fastboot? If fastboot devices sees your phone you can flash a ROM with that.

fastboot devices - no perrmision im lurking for solution for this atm

sudo fastboot devices

philicibine said:
sudo fastboot devices
Click to expand...
Click to collapse
yeah that one help a little. Now i see "HT535YJ0****"
http://askubuntu.com/questions/705537/no-permissions-fastboot-fastboot-and-adb-not-working - this is solution it think. But i don`t know yet how to use it. I can get my idVendor from lsusb Bus 003 Device 004: ID 0bb4:0ff0 HTC (High Tech Computer Corp.) Now i have few minutes to read about udev. After that i know im newbie and first things first - basics.
At this moment i stuck here
$ sudo sh -c "echo '# Megafon SP-A20i' >> /etc/udev/rules.d/51-android.rules"
$ sudo sh -c "echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="8087", MODE="0666", GROUP="plugdev"' >> /etc/udev/rules.d/51-android.rules"
$ sudo service udev restart
udev stop/waiting
udev start/running, process 1821
$

Don't worry about udev if your phone is already detected.
You need to find the firmware for your phone and a stock ROM.zip that matches it.
First use
Code:
sudo fastboot flash firmware.zip
And then
Code:
sudo fastboot flash ROM.zip
Hopefully you will be sorted then.
---------- Post added at 10:05 PM ---------- Previous post was at 09:59 PM ----------
Just read back to what your trying to do in your first post.
You can do this to unlock your bootloader
Code:
sudo fastboot oem unlock
Then you can flash twrp, and then any ROM you need.

philicibine said:
Then you can flash twrp, and then any ROM you need.
Click to expand...
Click to collapse
Nope. It can`t be so easy. "< waiting for device >". When i try do it on windows i see the same txt.
Command "get oem token identifier" give the same result. And as u know i need this token to unlock bootloader via htc developer center.

But you said when you did sudo fastboot devices this happened?
Danjou667 said:
Now i see "HT535YJ0****"
Click to expand...
Click to collapse
That's what happens when your device is ready to flash and detected.
Surely if you precede every command to unlock with sudo you should be fine? No more waiting for device.

USB debugging

Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance

Hmmm..
edshawn911 said:
Hello everyone, I really need help bad!! I just got my honor 7x and was trying to unlock my bootloader. I have followed directions for how to do this. The problem is that although I can see phone and files on laptop. For some reason the phone doesn't show as connected. I have tried adb commands as well as multi tool. Every way I try it doesn't work. I have unlocked bootloaders on other phone before. No matter what driver I have downloaded I still have yellow caution. Sighn in device manager ager. I have searched and searched for solution with no resolve. If it matters it is the model that a
Ends with the number 24. Thanks in advance
Click to expand...
Click to collapse
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?

RaiderWill said:
Hello..
Original Cable ?
What Version Of Windows ?
Drivers Installed ?
ADB Debugging Switched On ?
When You Type "ADB / FASTBOOT DEVICES" Seeing A Series Of Letters & Numbers ?
Click to expand...
Click to collapse
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.

edshawn911 said:
original as well as tried other cable.
windows 8
installed whatever drivers i could find. nothing said 7x .
i have allow adb debugging in charge only mode checked. i
when i type fastboot command as well as adb devices it doesn't find anything.
Click to expand...
Click to collapse
Ok... Since I have no intention to root until Huawei pushes the Oreo and Facial Recognition updates, I have kept USB Debugging "OFF" and set Select USB Configuration to: Media Transfer Protocol (MTP)
Then, I attempted to do what you are trying to do... and it worked perfectly..
So.. Do This:
Step 1 Click on your windows icon and in the search bar type "CMD"
Step 2 Set USB Configuration to MTP.
Step 3 Again I had Debugging off.. you can try it with it on if you like.. either way turn off your device.
Step 4 Hold down the Vol-Down button while plugging your device into your USB cable connected to your computer.
Step 5 This will turn on your device and put you in Fastboot Mode.
Step 6 Now go to your ADB Command Line and type "fastboot devices"
You'll see it.....

adb not working

Any help with ADB? tried everything adb kill-server and then adb start-server... change back and forth file transfer... turn on and off usb debug...
The think is tablet is connected can see phone memory and sd card and transfer files, but never see the fingerprint window asking me to allow usb debug

wallyhenderson said:
Any help with ADB? tried everything adb kill-server and then adb start-server... change back and forth file transfer... turn on and off usb debug...
The think is tablet is connected can see phone memory and sd card and transfer files, but never see the fingerprint window asking me to allow usb debug
Click to expand...
Click to collapse
Have you enabled USB debugging in Developer Options?

waterdaan said:
... turn on and off usb debug...
Click to expand...
Click to collapse
as i have said... many times

wallyhenderson said:
as i have said... many times
Click to expand...
Click to collapse
Sorry I missed the
... turn on and off usb debug...
Anyway, the problem is not the Tab S4, your adb server isn't starting
it should look something like
Code:
adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
yours says adb server is out of date

waterdaan said:
Have you enabled USB debugging in Developer Options?
Click to expand...
Click to collapse
waterdaan said:
Sorry I missed the
... turn on and off usb debug...
Anyway, the problem is not the Tab S4, your adb server isn't starting
it should look something like
Code:
adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
yours says adb server is out of date
Click to expand...
Click to collapse
but when i plug the usb cable it does not show the fingerprint message to accept usb debug... that should be because adb on pc?

wallyhenderson said:
but when i plug the usb cable it does not show the fingerprint message to accept usb debug... that should be because adb on pc?
Click to expand...
Click to collapse
You've probably chosen always trust this computer
You could revoke USB debugging authorizations in Developer Options
---------- Post added at 16:03 ---------- Previous post was at 15:59 ----------
@wallyhenderson
I would download the adb from this link and try to use that
https://wiki.lineageos.org/adb_fastboot_guide.html

waterdaan said:
You've probably chosen always trust this computer
You could revoke USB debugging authorizations in Developer Options
---------- Post added at 16:03 ---------- Previous post was at 15:59 ----------
@wallyhenderson
I would download the adb from this link and try to use that
https://wiki.lineageos.org/adb_fastboot_guide.html
Click to expand...
Click to collapse
its crazy... revoked authorizations and same... it does not ask for the fingerprint... downloaded your adb and same...

wallyhenderson said:
its crazy... revoked authorizations and same... it does not ask for the fingerprint... downloaded your adb and same...
Click to expand...
Click to collapse
Strange....
Just to check if adb is working,
Type only adb and hit enter
That should give you a help screen
If you do 'adb devices' and the adb server isn't running, it will start the adb service
Example without device connected to the computer
Code:
adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
Have you added adb as an Environment Variable in Windows?
Maybe in a previous install?
Check if it works with your phone in stead of the tablet

How To Guide [FAQ] ADB use issues for OnePlus 11

1. ADB doesn't see/detect your phone
- Make sure you're using the latest version of ADB. Download links are posted here.
- The phone is finicky in terms of USB cables. Try the one which came with the phone or a brand new good one.
2. You get a permission error trying to run adb grant com.developer.app android.permission.PERMISSION commands, e.g.
Code:
adb -d shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
Exception occurred while executing 'grant':
java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
at android.app.ContextImpl.enforce(ContextImpl.java:2253)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:2281)
at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermissionInternal(PermissionManagerServiceImpl.java:1364)
at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermission(PermissionManagerServiceImpl.java:1346)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:553)
at android.permission.PermissionManager.grantRuntimePermission(PermissionManager.java:597)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2591)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:302)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6351)
at android.os.Binder.shellCommand(Binder.java:1073)
at android.os.Binder.onTransact(Binder.java:901)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4313)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6335)
at android.os.Binder.execTransactInternal(Binder.java:1331)
at android.os.Binder.execTransact(Binder.java:1268)
What you need to do is:
Go to development settings and enable "Disable Permission Monitoring". You'll have to reboot your device afterwards.
3. BetterBatteryStats complains about a lack of access to PrivateAPI
Run this:
Code:
adb -d shell settings put global hidden_api_policy 1
Unfortunately it enables Hidden APIs globally for all apps which could be considered a security risk, so after using BBS you could revert it by:
Code:
adb -d shell settings delete global hidden_api_policy

I still cannot connect with ADB after updating drivers, ADB and using the factory cable.

biggiesmalls657 said:
I still cannot connect with ADB after updating drivers, ADB and using the factory cable.
Click to expand...
Click to collapse
Try rebooting. If it still doesn't help, try to change USB mode: e.g. switch from charging to "File transfer".

birdie said:
Try rebooting. If it still doesn't help, try to change USB mode: e.g. switch from charging to "File transfer".
Click to expand...
Click to collapse
Yes I tried that multiple times and every time I do it says USB malfunction like Windows can't understand it

biggiesmalls657 said:
Yes I tried that multiple times and every time I do it says USB malfunction like Windows can't understand it
Click to expand...
Click to collapse
Share a pic of device manager when device is connected.

biggiesmalls657 said:
Yes I tried that multiple times and every time I do it says USB malfunction like Windows can't understand it
Click to expand...
Click to collapse
That usually indicates you've got a bad cable or/and broken usb port on either of devices (your PC/smartphone).

birdie said:
That usually indicates you've got a bad cable or/and broken usb port on either of devices (your PC/smartphone).
Click to expand...
Click to collapse
Well it does it on all ports on my PC, I've used multiple cables

biggiesmalls657 said:
Well it does it on all ports on my PC, I've used multiple cables
Click to expand...
Click to collapse
Try a different PC, if it's still happening your phone USB port could be faulty.

birdie said:
Try a different PC, if it's still happening your phone USB port could be faulty.
Click to expand...
Click to collapse
I couldn't even get wireless ADB to work but it used to work on my Pixel