Hi people
I have the GT-I9190 S4 mini running 4.2.2 [not rooted], and am trying to connect to my pc with adb for installing apps etc.
The problem is:
I have enabled debugging on the phone, and when i start adb on the pc and query devices:
Code:
List of devices attached
####### offline
Then I went and googled about this, and a site said that from 4.2 upwards, android will prompt for confirmation whether the connected pc is trustworthy.
My phone did not ask. in fact, while i try anything on adb, my phone does nothing. If i was a phone i would also ask my owner if someone is allowed to poke in my back door but whatever.
to summarise:
adb lists phone as offline, phone doesn't acknowledge adb trying to connect
I think you need to update or reinstall SDK if you are on windows.
F4k said:
I think you need to update or reinstall SDK if you are on windows.
Click to expand...
Click to collapse
i am using the standalone adb that i got here on xda
I think you need a more recent adb, there's a change from 4.2 on, you don't really need full sdk.
I just installed adb on Linux and it works. so its gladly not my device. Can you point me to a minimalistic package of adb
I always install adb on linux with apt-get.
i think i wasnt clear, when i said
i am using the standalone adb that i got here on xda
Click to expand...
Click to collapse
i was on windows, then from when i mentioned linux, i was actually on linux, so my windows issue isnt resolved
The Jinxer said:
i think i wasnt clear, when i said i was on windows, then from when i mentioned linux, i was actually on linux, so my windows issue isnt resolved
Click to expand...
Click to collapse
I don't know any other method that install SDK tools on windows.
F4k said:
I don't know any other method that install SDK tools on windows.
Click to expand...
Click to collapse
Reinstalled from old package of sdk, not anything other than platform tools and it works
me too
The Jinxer said:
Reinstalled from old package of sdk, not anything other than platform tools and it works
Click to expand...
Click to collapse
For me too.
Related
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Install HTC Sync, then reboot your computer
JvIo55iBl3r said:
I was reading some instruction from htcevohacks.com. Since i didn't decide to root or not yet, i just want to install those sdk and driver on my pc. sdk part is easy, and i installed it successfully. But adb driver part is tricky.
I followed instruction, turn on "USB debugging" in the settings, and reboot phone into recovery mode, plugged usb cable. However, the device manager of windows 7 didn't find any adb devices, then i tried refresh, still no lucky at all. what should I do to find adb device then update driver? or i have to root first b4 installing adb driver?
Click to expand...
Click to collapse
I did, actually. As a matter of fact, i do have that sync icon in my task bar
I am not sure, but i was wondering if the adb driver is necessary to be installed?
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
adseguy said:
Yeah the HTC Sync.exe will have the drivers. Check your hardware configuration to make sure it's installed right then in the folder with adb installed use the command prompt to go: adb devices -> You should see a device with numbers. then you correctly installed it
Click to expand...
Click to collapse
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
JvIo55iBl3r said:
the problem right now is the device manager cannot even find any "other device" with question mark(when i plug the phone, which is under recovery mode, by usb cable)
Click to expand...
Click to collapse
this should definitely be in the Q&A board, not the developers board.
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Exit HTC sync first on your computer so it is not running or just uninstall it. It should find it after that.
joeykrim said:
this should definitely be in the Q&A board, not the developers board.
Click to expand...
Click to collapse
Sorry about that, will do next time
joeykrim said:
since you've already installed htc sync, the drivers should already be properly installed on your system.
ive only ran win xp and vista, not familiar with win 7, but if its designed the same, having no question marks, sounds like all connected devices have drivers properly installed ...
how do you know your adb drivers aren't installed? have you tried using adb? if so, what error does adb show?
Click to expand...
Click to collapse
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
JvIo55iBl3r said:
Sorry about that, will do next time
i tried command "adb device", i got some serial number, does that mean adb driver has been successfully installed on my pc, and work properly?
Click to expand...
Click to collapse
any help? anyone?
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Hi Dave, thanks for the reply.
I definitely have USB Debugging enabled - I also am 100% sure that I have installed the hboot driver before (I did it when rooting for the first time ages ago), and can confirm this by booting into Bootloader and having "Android Bootloader Interface" appear as a known device.
Also, with the HBOOT-Driver, it lists the phone as "Android 1.0" when Unknown, whereas my situation lists "Android Phone" as the unknown device.
davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Click to expand...
Click to collapse
Same here.
Have you added the environment variable for the sdk directory? It won't work if you don't.
Also.. install .. HTC Sync.. .and try.. and again uninstall only HTC sync.. and leave the HTC driver and try
I've had issues getting it working too and haven't quite figured out the sequence to get it to work. All I remember is the Android SDK drivers don't work, you need to use the HTC ones. You don't need to uninstall HTC Sync (try re-installing it though). You might then need to run update drivers on the unknown device for it to find them.
I can confirm that it does work with HTC Sync still installed. I sometimes find ADB devices takes a few attempts or restarting ADB to actually work.
vnvman said:
Have you added the environment variable for the sdk directory? It won't work if you don't.
Click to expand...
Click to collapse
Hi vnvman.
Thanks for the reply - I have indeed, my "PATH" value is as below:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\XviD MPEG-4 Video Codec 1.2.2 64-BIT;C:\Program Files (x86)\Common Files\Teleca Shared;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools
Click to expand...
Click to collapse
However, even if I cd in CMD to the platform-tools folder and run adb from there, no luck. ADB itself works perfectly, but it just doesn't recognize my phone.
bobsie41 said:
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Click to expand...
Click to collapse
Like some others users posted here, win 7 x64 is working for me without any problems.
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
Try to reinstall android sdk completely following this guide:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Hi MatDrOiD.
Thanks for the reply, I'll give that a shot as well as try jhonybravo4u and Antcodd's ideas.
Appreciate all input. If I get it working, I'll be sure to update this post so that anyone else who might have this problem has a solution
davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
What i meant is that windows 7 seems 64bit seems to cause more problems than any other windows os. I had a windows 7 64bit computer and after days of pratting about i managed to get it working now, further down the road, and a bit more knowledgable(i think!) i have a new more powerful windows 7 64bit machine and i can't for the life of me get it working.
I know run adb from my wifes vista laptop and had no trouble whatsoever in setting this up.
If u tried "everything", u better don't ask for more ;-p
Sent from my HTC Desire using XDA Premium App
It worked for me last time, but then I formatted my drive, and now can't get it to work for the love of god. Actually I can, but I have to change the driver every time Android phone pops up in the device manager using have disk.
I'm having trouble. I'm using this tutorial
http://forum.xda-developers.com/showpost.php?p=23229558&postcount=1
(if there is a better one I'm all ears), and the first command line step, where you plug in the phone and open up the command window within the designated file path and type "adb reboot bootloader", this is what I get:
* daemon not running. starting it now on port 5037 *
*daemon started successfully *
error: device offline
Any suggestions on what i'm doing wrong? Is it a driver issue?
A few things to try in no particular order: Try a different USB port. Try a different USB cable. Try typing the command adb start-server
I am not sure if the adb AIO thing installs the newer versions of adb. If it uses outdated versions, this could potentially be a problem as well. The SDK will install the newer versions.
cupfulloflol said:
A few things to try in no particular order: Try a different USB port. Try a different USB cable. Try typing the command adb start-server
I am not sure if the adb AIO thing installs the newer versions of adb. If it uses outdated versions, this could potentially be a problem as well. The SDK will install the newer versions.
Click to expand...
Click to collapse
/Yeah I didn't use the AIO app, I used the first method of downloading it from here http://developer.android.com/sdk/index.html
I've tried different ports and the start server command with no luck either......
If you are on windows it sounds like a driver issue.
Sent from my Galaxy Nexus
Indeed, this is most likely the issue. While the Android SDK package should have installed the latest drivers try this:
Run the SDK manager and make sure you're completely up to date.
You also need Android debugging enabled to be able to use adb and fastboot if you're doing it whilst logged on to the OS.
If you still have issues, I might be able to guide you through manually installing adb and fastboot drivers
Sent from my Galaxy Nexus using Tapatalk 2
iLeopard said:
Indeed, this is most likely the issue. While the Android SDK package should have installed the latest drivers try this:
Run the SDK manager and make sure you're completely up to date.
You also need Android debugging enabled to be able to use adb and fastboot if you're doing it whilst logged on to the OS.
If you still have issues, I might be able to guide you through manually installing adb and fastboot drivers
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
That's what I'm thinking, gotta be a driver issue. I'm using windows 7, and I uninstalled all drivers and got the drivers straight from the samsung website but who knows. I'll be at work tomorrow and will be working on it again there. Is it ok if I PM you tomorrow and we can go from there? I really appreciate your help!!!!
vballrkc said:
That's what I'm thinking, gotta be a driver issue. I'm using windows 7, and I uninstalled all drivers and got the drivers straight from the samsung website but who knows. I'll be at work tomorrow and will be working on it again there. Is it ok if I PM you tomorrow and we can go from there? I really appreciate your help!!!!
Click to expand...
Click to collapse
Yes that would be fine
Sent from my Galaxy Nexus using Tapatalk 2
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Appsdroid said:
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Click to expand...
Click to collapse
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Wilks3y said:
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Click to expand...
Click to collapse
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Appsdroid said:
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Click to expand...
Click to collapse
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Wilks3y said:
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Click to expand...
Click to collapse
Nice one cheers mate will try these drivers when I get home later. I was originally using Hasoons toolkit which is what flashed the recovery and new rom but once I updated to 4.2.2 the toolkit stopped. It was coming up as device offline. I have managed to get it working by overwritting the old ADB and fastboot files with the new ones for 4.2.2. The ones the toolkit comes with is 4.1 so was erroring as it didnt know to carry out the fingerprint check.
Yes mate I have tried various methods I have accessed the android\android-sdk\platform-tools folder and run ADB from there this identifies the phone but states its not authorised. I tried using the toolkit with the new ADB and fastboot but get the same.
Im just missing the ADB prompt on my phone for usb debugging just cant for the life of me identify why im getting the copy files from usb prompt rather than the adb fingerprint prompt. Im sure its drivers so am hopeful the ones on the link will fix it. Fingers crossed
I was having issues with adb not finding my device. These drivers worked for me...
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
Nice one mate will try these ones when I get in to on way home now hopeful one of the driver links sorts out the prompt for me will update later thanks guys
Sent from my HTC One X using xda app-developers app
Cheers All removed all drivers for htc one x then downloaded the 4.2 versions from the link
http://forum.xda-developers.com/show....php?t=2217396
once reinstalled adb gave unauthorised error again but then put the prompt up on the phone. So possible the 4.2 contains the info for requesting permission as i havent changed anything other than the drivers adb and fastboot have been the same since i started. Anyway cheers all
confusion about installing driver
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
bro i download your driver but how to install it. my htc one x just start in fastboot mode. i want to unlock bootloader but without adb i am helpless
If you have Windows 7,8,8.1 just enable automatic update and let windows install correct drivers
Sent from my HTC One X using Tapatalk 2
How do I enable using ADB with my Pixel XL? When I try to do ADB commands, they come back blank. ADB devices returns nothing for example. I read some stuff that seemed to indicate I didn't have the right drivers. I tried to download a new set of drivers from Google's website, but those don't work either. Windows 10 keeps insisting that the drivers installed are better.
Can someone point me in the right direction please?
Thanks!
Eric
Ewto16 said:
How do I enable using ADB with my Pixel XL? When I try to do ADB commands, they come back blank. ADB devices returns nothing for example. I read some stuff that seemed to indicate I didn't have the right drivers. I tried to download a new set of drivers from Google's website, but those don't work either. Windows 10 keeps insisting that the drivers installed are better.
Can someone point me in the right direction please?
Thanks!
Eric
Click to expand...
Click to collapse
SDK Platform-tools r29.0.5?
If you booted into fastboot mode/bootloader
ADB doesn't work, use fastboot devices
Homeboy76 said:
SDK Platform-tools r29.0.5?
If you booted into fastboot mode/bootloader
ADB doesn't work, use fastboot devices
Click to expand...
Click to collapse
Those are the platform tools I have.
On my phone, I hold down power and volume down until the little android guy comes up. From there I hook it to my PC, via a USB cable. Next I go into the platform tools folder and start running commands from there. If I run ADB devices, nothing comes back. If I run, fastboot devices, I get my model number back.
Is that not correct? How would I run ADB commands then?
Thanks!
Ewto16 said:
Those are the platform tools I have.
On my phone, I hold down power and volume down until the little android guy comes up. From there I hook it to my PC, via a USB cable. Next I go into the platform tools folder and start running commands from there. If I run ADB devices, nothing comes back. If I run, fastboot devices, I get my model number back.
Is that not correct? How would I run ADB commands then?
Thanks!
Click to expand...
Click to collapse
What are you trying to do with adb? Adb is used in either recovery mode or once the phone had booted into the system, provided you have enabled USB debugging. Is it this that you want to know more about?
Ewto16 said:
Those are the platform tools I have.
On my phone, I hold down power and volume down until the little android guy comes up. From there I hook it to my PC, via a USB cable. Next I go into the platform tools folder and start running commands from there. If I run ADB devices, nothing comes back. If I run, fastboot devices, I get my model number back.
Is that not correct? How would I run ADB commands then?
Thanks!
Click to expand...
Click to collapse
When you power off phone, press and hold the power and volume down buttons you should see Start.
You are booting the bootloader/fastboot mode.
Then you open a Command prompt in the Platform-tools folder and type: fastboot devices
It should return the phones serial number.
Take a look at one of these guides: Android 9 (Pie) Guide or Android 10 (Q) Guide.
NZedPred said:
What are you trying to do with adb? Adb is used in either recovery mode or once the phone had booted into the system, provided you have enabled USB debugging. Is it this that you want to know more about?
Click to expand...
Click to collapse
Hi, thanks for the response. I was trying to run and do the following series of commands.
Install Magisk module: Busybox for Android NDK
Install Magisk module: MagiskHide Props Config
Reboot
adb shell
settings put global tether_dun_required 0
su props
On the last command above you may need to authorize the shell via Magisk SU.
You'll now be in an interactive script, do the following:
Enter 5, Add/edit custom props
Enter n, New custom prop
Enter net.tethering.noprovisioning
Enter true
Enter 2, post-fs-data
Enter y
Enter y to reboot
I couldn't figure out how to get adb to work. (I don't know what the heck BusyBox does either for that matter.) It sounds like I may not have had my phone in the right mode to use adb. Based on the other post, I think I was in bootloader mode. (power down and volume down). It sounds like adb doesn't work in that mode, which I didn't understand. Does any of this make any sense?
Homeboy76 said:
When you power off phone, press and hold the power and volume down buttons you should see Start.
You are booting the bootloader/fastboot mode.
Then you open a Command prompt in the Platform-tools folder and type: fastboot devices
It should return the phones serial number.
Take a look at one of these guides: Android 9 (Pie) Guide or Android 10 (Q) Guide.
Click to expand...
Click to collapse
You are correct. Doing that does return my phone's serial number. However, adb doesn't appear to work for me in that mode. Are you saying that in bootloader/fastboot mode adb doesn't work?
Thanks for the link to those guides. They are REALLY good and well written for someone who is a bit of a noob like myself. I really appreciate them. I've used them to install Magisk on my Pixel XL when it was on Android 9 quite a few times. This time, I used it to install Magisk on my Pixel XL with Android 10, but ran into issues when I couldn't edit the build.prop file to enable tethering. The adb commands I was trying to run were supposed to help with the build.prop problem.
Ewto16 said:
You are correct. Doing that does return my phone's serial number. However, adb doesn't appear to work for me in that mode. Are you saying that in bootloader/fastboot mode adb doesn't work?
Thanks for the link to those guides. They are REALLY good and well written for someone who is a bit of a noob like myself. I really appreciate them. I've used them to install Magisk on my Pixel XL when it was on Android 9 quite a few times. This time, I used it to install Magisk on my Pixel XL with Android 10, but ran into issues when I couldn't edit the build.prop file to enable tethering. The adb commands I was trying to run were supposed to help with the build.prop problem.
Click to expand...
Click to collapse
Yes!
adb does not work in bootloader you spastic, boot into your system or twrp to use it
Homeboy76 said:
Yes!
Click to expand...
Click to collapse
Ah, I see. OK. Thanks for clearing that up for me. I'll have to hook my phone up and try adb again. I'll probably just wait until I need to upgrade again. I have everything working at the moment so I kinda don't want to mess with it.
Thanks for the help!
Ewto16 said:
Ah, I see. OK. Thanks for clearing that up for me. I'll have to hook my phone up and try adb again. I'll probably just wait until I need to upgrade again. I have everything working at the moment so I kinda don't want to mess with it.
Thanks for the help!
Click to expand...
Click to collapse
Also do yourself a HUGE favor and use dual boot on your computer and install Linux Ubuntu. Then adb and fastboot and anything you want as far as Android (and all types of other things) will work without issues. I am somewhat new to Linux Ubuntu but ever since the first installation I did I fell in love with it and haven't had an issue since. If you google search Linux Ubuntu you can find their site and read all about it and dual boot if you want or wipe windows and install Linux only. I grantee you'd love Linux OS. There are MANY to choose from too, not just Ubuntu but Ubuntu is bad ass IMO. I use 18.04 LTS and I love it. Check it out some time. Its 100% free too.
Linux site: https://ubuntu.com/download
flash713 said:
Also do yourself a HUGE favor and use dual boot on your computer and install Linux Ubuntu. Then adb and fastboot and anything you want as far as Android (and all types of other things) will work without issues. I am somewhat new to Linux Ubuntu but ever since the first installation I did I fell in love with it and haven't had an issue since. If you google search Linux Ubuntu you can find their site and read all about it and dual boot if you want or wipe windows and install Linux only. I grantee you'd love Linux OS. There are MANY to choose from too, not just Ubuntu but Ubuntu is bad ass IMO. I use 18.04 LTS and I love it. Check it out some time. Its 100% free too.
Linux site: https://ubuntu.com/download
Click to expand...
Click to collapse
ubuntu is trash.
also adb/fastboot work fine on any os i dont see why there is any difference. i use macos myself and its working just fine and it works on my windows install too.
sudoxd said:
ubuntu is trash.
also adb/fastboot work fine on any os i dont see why there is any difference. i use macos myself and its working just fine and it works on my windows install too.
Click to expand...
Click to collapse
I always had some driver issue on Windows seemed like. And everything was installed perfect. Since I left windows and switched I have NOT had any issue with anything far as my phone and PC go. I may check out Mint and or some other distros soon. I've only been onboard 6-8 months now so I'm noobin it still. ;p You should see my setup. LMAO! It's not the nicest looking laptop (a few keys missing on my keyboard...) [emoji23][emoji849] But hey, it does the job I need it to,, for now anyway. LOL! I would never return to windows unless I was using Photoshop. Sure there's Gimp but I always kinda liked Photoshop better.
Sent from my [device_name] using XDA-Developers Legacy app
flash713 said:
I always had some driver issue on Windows seemed like. And everything was installed perfect. Since I left windows and switched I have NOT had any issue with anything far as my phone and PC go. I may check out Mint and or some other distros soon. I've only been onboard 6-8 months now so I'm noobin it still. ;p You should see my setup. LMAO! It's not the nicest looking laptop (a few keys missing on my keyboard...) [emoji23][emoji849] But hey, it does the job I need it to,, for now anyway. LOL! I would never return to windows unless I was using Photoshop. Sure there's Gimp but I always kinda liked Photoshop better.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
how have you been using linux for 6-8 months and you still think ****-tier distros like ubuntu and mint are still acceptable