Related
Ok so I'm having trouble getting my xoom rooted. At this point I have unlocked the bootloader and need to flash the new img. Going through the instructions it says after opening command for the SDK tools folder to type "adb reboot bootloader" and i get the error saying no device found. No idea why its doing that, my computer can see my xoom.
I will say this, since the adb.exe was put into platform tools instead of tools I did move it over along with its dll files, not sure if that might have done it.
Any help is appreciated.
Ok so feel a little stupid now, got that taken care of but still cant flash the img. Just sits on "waiting for device" and neither do anything.
I have been searching everywhere online for the past 3 days and have seen hundreds of posts on the subject but nothing has helped. I plug in my Kindle Fire, use KFU, use "Install TWRP...", but I get a "device not found" (ADB Status: offline, Boot Status: Unknown).
I've updated the drivers using install_drivers.bat. I've installed them manually. I've restarted my computer and kindle numerous times. The last thing I have tried is updating the adb, but I'm getting an "access denied" error for the adb_usb.ini. I've looked at the permissions and I have permission to edit it.
I'm seriously at my wit's end here since everything I've tried that people say works hasn't worked for me. Does anyone know how to fix this?
Does your device boot up?
Do you mean turn on? Yes. My computer recognizes it. I can transfer files back and forth.
Just to update: I was able to get the kindle fire utility to show adb status online. I didn't do the update adb, so I just put the "0x1949" in the adb_usb file that says
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
It recognizes it, but when I do "Install TWRP", it goes through some code, and on my kindle just says "Root enabled" with and "exit" button to press.
In KFU, after it says "Activating Burritoroot" and "elevating the shell", I get
"adbd cannot run as root in production builds" then
"mount: operation is not permitted" a couple of times
"failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system"
"unable to chmod" that file above
"mount: operation not permitted" a couple of times
It then says "root activated". "The kindle is successfully running in root mode"
<idme> invalid permission
reboot: operation not permitted
The kindle has been told to reboot in Fastboot Mode.
<waiting for device>
What does all of that mean?
Do you have 6.2.2? If you have 6.2.2 everything that happens is normal because it isn't supported yet.. You have to root with burrito root 2 and manually install the recovery.
Yeah, I have 6.2.2. When you say root with Burritoroot 2 and manually install, what do you mean? In my searching, I haven't come across this. Is there a tutorial somewhere. Also, is there a way to return to earlier versions to just use TWRP?
Check the burrito root 2 thread (first post) and the recovery thread for the exact steps you have to follow. By manually I mean that you have to type all the commands your self. There isn't a script yet that can do it for you.
Thanks. I'll try that and see if it works.
It worked for me
or patch run.bat of kfu:
http://forum.xda-developers.com/showthread.php?p=21602553#post21602553
b63 said:
or patch run.bat of kfu:
http://forum.xda-developers.com/showthread.php?p=21602553#post21602553
Click to expand...
Click to collapse
this will brick you if you try and get into fastboot mode, i'm now bricked
the_kwa said:
this will brick you if you try and get into fastboot mode, i'm now bricked
Click to expand...
Click to collapse
many people have done it and it seems to be working
but it is still kfu - means the op of kfu is still valid:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
Okay, I have root (used root checker app to make sure), but KFU still doesn't work. I get the same error. I actually think I may have had root all along. I'm still getting the:
<waiting for device> and that the adb cannot run as root in production builds
I now understand (after reading for a little longer) that Kindle Fire Utility simply doesn't work with 6.2.2 to install TWRP unless you update the run.bat file. While I'm okay with doing some of those commands, it seems that too many people have been bricked by that route. Is there any other way to install TWRP, or do I just have to wait for KFU to be updated? And does anyone have an idea of how long that will take?
you can do it manually
try to follow this post:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
Thanks for the reply, but right after posting, I found an updated version of KFU for 6.2.2.
Here's a link to where I downloaded it from:
http://pastebin.com/PV9FQYry
It worked perfectly for me. I now have TWRP installed and my system backed up using Kindle Fire Utility for 6.2.2. If anyone else is having these problems, this works (at least for me).
good ...
please mark the subject of the topic (edit first post) with [Solved]
Hi, I have the 6.2.2 OS, but I still get the 'Offline ADB Status' even after using the KFU for that version
Any hints?
maxximop said:
Hi, I have the 6.2.2 OS, but I still get the 'Offline ADB Status' even after using the KFU for that version
Any hints?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
YouthTeam said:
Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
Click to expand...
Click to collapse
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
also check for developer->usb debugging notify...
Anarkista7 said:
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
Click to expand...
Click to collapse
I was having the same problem. I also had a box that said 'USB debugging notify' checked and didn't notice the device asking for permission to run adb right after I did the kill-server and start-server. As soon as I hit 'ok' the unauthorized problem went away.
Thanks to all on the thread.
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
problem
I am having a similar problem as well. My old Samsung Galaxy S is stuck on bootloop. Home button is dead so I cannot acces download mode/recovery mode manually and in adb device is unfortunately unauthorized
Any way to go around this ?
unauthorized device, unable to adb anything
[email protected]:~$ adb reboot bootloader
error: device unauthorized. Please check the confirmation dialog on your device.
[email protected]:~$
[email protected]:~$ adb devices
List of devices attached
FA2BDS501095 unauthorized
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
Same Problem! Phone stuck on Samsung logo
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
are that problem was solved?
how?
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
No RSA key dialoge either
I have seen some RSA key apps but they are for creating keys. How can I get the dialoge to come up. I have a HTC One M8 831c ROOTED twrp recovery BadSeeds Stock Rooted ROM SuperSU PRO updated. Its on a Harman Kardon Edition which seems to be a little off from the other versions.
emko7 said:
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
Click to expand...
Click to collapse
I have the same exact problem as you. Have you found a solution?
same problem
I have root
have deleted critical system files via titanium backup
i have USB debugging enabled
have revoked authorizations
i have systemui error which loops every time I boot
no home button functionality
no actual phone application any longer
no drop-down notification available, however banner notifications do present themselves only to disappear out of reach above the screen edge.
I have done everything the previous poster mentioned, and my problem is virtually identical to theirs.
Due to these particular circumstances, I am unable to receive the RSA prompt menu and authorize ADB.
I have root access but cannot enter ADB into root mode due to unauthorized device errors.
i am unable to do anything with shell functions as well
my phone is practically disabled at this point, to do anything useful is a daunting task of escaping and passing by the looping systemui error in order to slip into subsequent menus/functions.
The only solution I have found is to rebuild the boot.img file such that it excludes the RSA protocol or over-rides it.
factory restore does not remount vendor partition files no luck restoring from SD or cache.
I am sure I could rebuild the file but I would be pushing my boundaries, something I don't have particular time for at this moment. Being too busy with academics that currently dont encompass coding, I have no time to study on this one...
I will be happy to do my due diligence whatever the case may be, however...I need some answers. My phone is out of commission.
Same problem, did u get the solution?
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
Please help me. I rooted my phone with the procedure given at:
wiki.cyanogenmod.org/w/Install_CM_for_nicki
Now , after doing
fastboot flash boot boot.img
fastboot reboot
i did -> wipe data/factory reset.
after that when i tried -> adb sideload <my cm12.1 package name>.zip
i am getting this msg.
error: device unauthorized. Please check the confirmation dialog on your device.
when i typed -> adb devices
i got my device unauthorised.
Please help me, i am desperate.
for some reason I dont get the adb authorize box on my watch anymore (to adb reboot bootloader) its says "error: device unauthorized. Please check the confirmation dialog on your device." but there is no way to enable the authorisation anymore.
I also face this problem with pop 2 4.5 5042d; unauthorized and phone in bootloop with no fastboot
No OS installed so not able to Allow USB debugging.
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
---------- Post added at 10:03 AM ---------- Previous post was at 09:10 AM ----------
Im_Rohit said:
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
Click to expand...
Click to collapse
I used OTG instead of internal storage and it works.
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
same problem--- any idea to solve my problem???
thanks
abhi26 said:
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
Click to expand...
Click to collapse
Your phone might be bricked. Did you recently try to root it?
bit late to the party, but this worked for me
I had RSA ADB fingerprint issues, worked for ages then stopped working, went through every forum post and nothing worked, then found this post.... stackoverflow.com/questions/31638582/android-adb-devices-unauthorized[/url]
opening a cmd prompt in this location C:\Users\<your user name>\AppData\Local\Android\sdk\platform-tools and running adb from here and it worked straight from the off.
i've spent 2 nights working on this, so if it helps anyone
my screen broke and picture is completely ****ed and useless.
is it possible to enable USB debugging without using the touch screen? i want to mirror the phone to a laptop and pull my work hour sheet
Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!
techgeard said:
Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!
Click to expand...
Click to collapse
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?
dgadelha said:
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?
Click to expand...
Click to collapse
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.
techgeard said:
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.
Click to expand...
Click to collapse
In that case, follow the "Last resort" part of this guide http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
It will reinstall your fastboot when the USB icon appears
dgadelha said:
In that case, follow the "Last resort" part of this guide
It will reinstall your fastboot when the USB icon appears
Click to expand...
Click to collapse
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.
UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.
techgeard said:
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.
Click to expand...
Click to collapse
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
techgeard said:
UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.
Click to expand...
Click to collapse
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!
dgadelha said:
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!
Click to expand...
Click to collapse
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Code:
start
sending dner
writeoutpipe dner
writeoutpipe 0
write----> dner
windriver Error: 0x20000015, Timeour expired
LogError
Error Code:1 - Connection Error
Failed to start Dldr state matchine, aborting...
void CloverviewPlusDownloader::do_abort()
Abott
FAIL
.....
techgeard said:
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Click to expand...
Click to collapse
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.
dgadelha said:
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.
Click to expand...
Click to collapse
Iam using Win7x64. The same with the guy posting in the link.
TG.
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
hackmythinq said:
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
LMSA has a pin reset, you could try that.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
hackmythinq said:
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
[email protected]!$h said:
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
Click to expand...
Click to collapse
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it? In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
hackmythinq said:
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it?
Click to expand...
Click to collapse
Yes, it could be bluestacks. It's adb connection runs in the background.
In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
Click to expand...
Click to collapse
adb doesn't have any GUI and cmd flashing for a second is general behaviour when you run adb.exe. You should always run it from command prompt like you did before.
try installing Moto drivers : https://support.motorola.com/in/en/drivers
if already installed better try different port/cable/pc