Database Info

[Solution]Windows 8 - ADB/fastboot driver problem solved!!

Hello!!​
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that as well, it is, after all, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed. Again (-_-") ) (Note: These are the Sammy OEM drivers.)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check out Beatsleigher & M4gkman's Universal Android Toolkit, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
So, apparently, if you're using Windows 8 and/or USB 3.0 ports, Windows installs its crappy drivers, so you should check out this link, posted by the awesome @tommy_riley and try it out for yourselves! Don't forget to drop him a 'Thanks'!
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers <- Courtesy of @tommy_riley!
Wow. Over 40.000 clicks and downloads. I'm amazed at you guys!
It doesn't cost anything or hurt to hit that 'Thanks' button... Please be sure to hit it, it helps me out and also shows me what sort of content you want to see from me.
Do you like the effort I put into this? Then consider donating, by adding towards a new PC: http://www.gofundme.com/NewPC
With a new PC, I can create more one-click solutions and stuff and things!

Updates & other info!! (Reserved)
If you have a problem, I'll do it over TeamViewer, if you wish
Ok, here is some news, for you!
Well, according to some people, who have used this tutorial, Microsoft has done something new to their device driver signing.
I did not have note of this, as I was using Ubuntu most of the time and the laptop I was using broke, several weeks ago (It's gonna take me ages to get a new one, with which I can finally finish my ROM cooking..)
And Senior Member "purpler" has posted a link, which teaches you to turn device driver signing off, in the new bootloader, which Windows 8 is using/will be using, so; let's give him loads of thanks, for this!
here is his answer:
purpler said:
confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options
Click to expand...
Click to collapse
Many thanks to you, purpler!
Please, if you notice anymore changes, which interferes with this method, please let me know, how to solve the problem!
Every helpfull answer, with new solutions will be posted in this thread and thanked many times!
EDIT: If you don't want to donate, but still want to thank me, then use these links, instead of the links, in the tutorial.
Mod edit: No adfly links allowed.
4lex96 said:
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards
Click to expand...
Click to collapse
Senior member 4alex96 has experienced some problems, while using USB® 3.0 ports.
If you are also experiencing these problems, or you have found a solution to this, be sure to post in this thread or write to me via PM and I'll be sure to quote and write this, so others also get to know and are able to get the most out of there Androids!
Creating a new tool!
Hey guys, I'm going to be creating a new tool or two, which will allow you to install ADB and Fastboot directly to the system root and which will install the Google drivers to your C:\ drive.
These tools will be available for a small donation, and they will save you a lot of work, i.e. you will never have to type in "path=<Whereever the ADB files are>" but you can just debug on
If you want to have the program, hit the "Donate to Me" button on the left of this post and donate a small amount. Then in the donation, write me a message, saying what it's for and give me your XDA username and I'll PM you the download link.
(Minimum of 5€)
tommy_riley said:
For Windows 8, I was having an issue getting my phone to be recognized in bootloader mode on an ASUS laptop that only had USB 3.0 drivers, I followed the procedures at the below URL (luckily I had an INTEL chipset) and once I replaced my native Windows USB 3.0 drivers with the Intel USB 3.0 drivers, I was able to work around a lot of issues:
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
(I cant post HTTP links yet, but you should be able to plug the above into a browser to find the instructions...)
hope this helps!
Click to expand...
Click to collapse
You get that, guys? Go check out that website, and try it out for yourselves!

Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing

thisiswar951 said:
Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing
Click to expand...
Click to collapse
Ok, cool. I haven't been on my laptop, for a few days, so I wouldn't know, if MS has released any updates, yet...
I was thinking: WTF is he talking about? It's worked by so many people :O...
xD
LG familyguy59

confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options

Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!

hshen45 said:
Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!
Click to expand...
Click to collapse
You'll have to wait a moment, the system has to look for all the needed files, in the exe, and then needs to try to execute. If it then doesn't work, I'll upload an updated version, but as this seems to be working pretty much fine, I'll hesitate, not that the updated verison causes problems.
Anyways, I was running Win8 64x and it worked fine, just let the computer do it's work and it will work sooner or later, if nothing happens, even after waiting for 5-10 minutes, then try running it with administrative rights (Run as administrator).. Let me know if it works!

Doesn't work for me because I cant even see my S3 in the device manager.

leeznon said:
Doesn't work for me because I cant even see my S3 in the device manager.
Click to expand...
Click to collapse
Then try a different computer Doesn't mean that your S III is kaputt, does it?
If it then doesn't work, you've probably got dirt in the socket, or something else, like that.
And if you don't have dirt in the socket, then I don't know, whats wrong, but it'll definitely go over warranty

I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:

dalien26 said:
I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:
Click to expand...
Click to collapse
That's what the link in the first post is for. And you still need to follow the steps in the tutorial, otherwise it won't work properly.
I know the tutorial looks complex, but it isn't. You just need to read properly
LG familyguy59/Beatsleigher
EDIT: It's spelled "click"

help me to connect android in win 8
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.

netbook said:
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.
Click to expand...
Click to collapse
OK, I will be back, tomorrow. I'm currently at a friend's, so I will be back tomorrow. Send me an e-mail, when you're back, and I'll help you, right away!
LG familyguy59/Beatsleigher

familyguy59 said:
Hello!!​
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that aswell, it is, afterall, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed) (Thanks so much for 5k+ downloads!!)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
Thanks a ton for 6k+ views/downloads!! The thanks are also very much appreciated!!
9K+ views!!
15K+ views!!!
Click to expand...
Click to collapse
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!

llsiddhantll said:
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!
Click to expand...
Click to collapse
I'm always glad to help, dude
LG familyguy59/Beatsleigher

heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.

shaolinx said:
heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.
Click to expand...
Click to collapse
We're already aware of that (see post #2) but still thanks for briefing everyone again.
LG familyguy59/Beatsleigher
Cyanogenmodded very skankily via XDA app. Skanky, indeed

Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!

4lex96 said:
Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!
Click to expand...
Click to collapse
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher

familyguy59 said:
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards

[Tutorial] How to install Android SDK/ADB tool & HTC's drivers [BEGINNER FRIENDLY]

[Tutorial] How to install Android SDK/ADB tool & HTC's drivers [BEGINNER FRIENDLY]
[SIZE="+1"]-- Android SDK/ADB tool Tutorial --[/SIZE]​
I decided to create this Beginner Friendly tutorial on how to install SDK tool mainly because recent phones such as the i.e. HTC One X / One X+ are requiring many basic usage of adb command line, and lots of members are having difficulities to have basics adb command to work because their SDK tool is not correctly installed. I won't show you how to make usage of it, there is plenty of How-to's for that purpose all around xda and on the Web.
This is all safe to install on your Windows based computer, and if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device. From now on, I or anyone else on the Internet can not be held responsible if something really bad is happening to you because you didn't read and followed any given instructions letters by letters and you ended with a screwed, pricey and valuable paperweight device. That being said, let's get started.​
Let's GO!
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
This is it, I hope this tutorial was helpful, if you have some sort of problems let me know, I will try to help you at the best of my knowledge. Have fun hacking your Android!!

Lucky Thirteen said:
...if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device.
Click to expand...
Click to collapse
Excellent tutorial... but I disagree with this line. No process is bulletproof and there is no way a tutorial can account for all the variables with Windows.
Which explains why I am now asking for help!
This is my third Android phone and fifth Android device. I've rooted all five and installed multiple ROMs and for the most part have not had too many problems.
I'm currently running Elegancia 5.3.0 on my AT&T One X+ and have a few issues that I'm tired of dealing with. I decided to flash the RUU to go back to stock and also to update to hboot 1.4 which is required for the Blackout ROM I was thinking about trying. The RUU cannot find my phone unless I connect while in the bootloader. Even then though, the RUU flash still fails. Since it cannot see my phone while it's running, I decided to check if ADB can see it. Nope. No luck at all. I have connected with ADB to my device many, many times... but it has been close to a year since the last time I did. I removed all HTC drivers and Sync from Add/Remove Programs, deleted my old version of the SDK and Java and followed your tutorial step-by-step.
My phone still shows up in Device Manager under PORTABLE DEVICES and I can't seem to make it connect any other way.
Please tell me you have a suggestion to help me fix this. I've tried using every combination of search terms I can think of and have had no luck for the past 36 hours.

Finally fixed my ADB problem using these steps in case anyone else runs into it.

This worked great for me after two days of trying to get my phone to connect. I had to uninstall everything related to java, android, and htc, and the link for the htc drivers was dead so I just reinstalled sync manager, but it all works now, much thanks. All this effort was just so I could put my music on the phone, and so that I could do a full backup to my pc without rooting.

[GUIDE] Set up Android SDK (ADB) for Windows 8 / 8.1 / [ADB][Bootloader][Fastboot]

Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Java is needed to Run SDK Manager - Install JAVA​
The Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.​
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\sdk\platform-tools
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified

Reserve if needed

Thanks! Good stuff.. I just installed Windows 8 and totally forgot that I had to reinstall this... ( which originally took me 8 hours to figure out the first time! Lol ) this will definitely help future HTC people out...

Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0

x70xchallengerx said:
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
Click to expand...
Click to collapse
USB 3.0 gets a bad rep. I do a lot of my adb with a USB 3.0 with few issues
Sent from my HTC6525LVW using Tapatalk

OP Updated
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks

x70xchallengerx said:
Thanks for the guide but will this work with USB 3.0? I have an Asus G750JW with 4x usb 3.0 ports and no usb 2.0
Click to expand...
Click to collapse
wtoj34 said:
USB 3.0 gets a bad rep. I do a lot of my adb with a USB 3.0 with few issues
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I am aware that USB 3.0 does cause issues with adb, mostly the longer running ones it hangs sometimes, I don't have an answer for that right now, I am running with 2.0 still and I have zero issues.
This is something that I came across that seemed to resolve a lot of adb issues
USB 3.0 Help with ADB
also
XDA Thread I found that in

cant launch sdk manager
After installing abd on Windows8.1 64 is there a trick to launch so that i can add and update?
Fixed issue. New pc and forgot to install java...?
bdorr1105 said:
Android SDK - Powerful tool and easy to set up for use with your HTC One M8
​
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
Part 2. Verifying ADB is set up properly and Working
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
Click to expand...
Click to collapse

davidmatt34 said:
After installing abd on Windows8.1 64 is there a trick to launch so that i can add and update?
Fixed issue. New pc and forgot to install java...?
Click to expand...
Click to collapse
Thanks for sharing that, I added that as note in the OP...Glad you are setup and good to go

I feel like such an idiot, but I want to be sure I'm getting the latest HTC Sync... I follow the link in the OP and it takes me to support.. I Google and the same thing happens.. They move it over at HTC?
I found it here... http://www.htc.com/us/support/software/htc-sync-manager.aspx
And this worked flawlessly!! I was always afraid of going back to Windows 8.1 because of ADB/Fastboot being broken.. so far so good!! Side loading soon!!

jbarcus81 said:
I feel like such an idiot, but I want to be sure I'm getting the latest HTC Sync... I follow the link in the OP and it takes me to support.. I Google and the same thing happens.. They move it over at HTC?
I found it here... http://www.htc.com/us/support/software/htc-sync-manager.aspx
And this worked flawlessly!! I was always afraid of going back to Windows 8.1 because of ADB/Fastboot being broken.. so far so good!! Side loading soon!!
Click to expand...
Click to collapse
Glad everything is working, the link in my OP went to the same exact HTC Sync Manager yours did, pull yours you posted and mine side by side its the same, not sure what happened, either way glad you are up and running

bdorr1105 said:
Glad everything is working, the link in my OP went to the same exact HTC Sync Manager yours did, pull yours you posted and mine side by side its the same, not sure what happened, either way glad you are up and running
Click to expand...
Click to collapse
Yeah.. the link just wasn't working at the time.. weird..

jbarcus81 said:
Yeah.. the link just wasn't working at the time.. weird..
Click to expand...
Click to collapse
Thanks for the update
Sent from my HTC6525LVW using Tapatalk

Also make sure you don't have drivers installed for another phone.. ADB couldn't find my M8 until I uninstalled my lg spectrums drivers on Win 8.1
Sent from my HTC6525LVW using XDA Free mobile app

Nice job.. Thanks for this. My first W8.1 machine.

Guys can someone help ,,
everything is installed and still getting the following error :
C:\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH44FWM09049 device
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
< waiting for device >
i've been trying to fix this for the past 4 hours but no luck ,, anyone ??

I$ device in fastboot mode?

nvmd

without changing environment variable we can even hold shift+right click the folder containing the adb and open command window from the menu isn't it?

technochatter said:
without changing environment variable we can even hold shift+right click the folder containing the adb and open command window from the menu isn't it?
Click to expand...
Click to collapse
Yes.

Nexus 5 WiFi problem...acting strange....turning ON / OFF and Power ON/ OFF

Gentlemen/ Ladies,
I am NOT a developer, in fact I need a little help here, and searching all over internet, I bet you guys are probably the last resort of true assistance to my problem.
I am a proud Nexus 5 (Hammerhead) phone user, yes, still Nexus 5 because it is such a good reliable phone.
But started the day before, the WiFi is turning itself OFF, and although I tried turning it ON, it just keep searching and searching (where the screen usually display all WiFi networks around, it just shows a energy-bar running from left to right, while bottom is pretty much blank except saying turning ON wifi).
The phone then shutting down itself, OR I have to turn the phone OFF, wait to power ON again, sometimes WiFi works , sometimes it does not, or turn if OFF itself after a few minutes. when it's back ON, it works normally for a short time, then OFF again....
All other functions of the phone are flawless, blue tooth, my t-mobile LTE, have no problems.
At this stage, I can’t tell, it is a software and hardware error.
Did’nt drop on the floor, no water damages, no crack on screen, I have been use it nicely. I noticed the battery drinks fast, and I worried that this problem is the result of bad battery/ shutting down due to empty battery, so yesterday I finally replaced the battery with a brand new one.
I checked my charter internet modem, and wireless router, all seems to be ok, as my other PC and laptop both using hard cable and wireless, other cell phone also use the same WiFi at home, they all function OK.
I ran malwarebytes and panda anti-virus on the Nexus 5, no virus.
I tried suggestions from youtube:
-turn the airplane mode ON/OFF
-turn t mobile, bluetooth ON/OFF
-reset network connection, ( that only brings my t mobile ON)
-Developer mode ON, select legacy DHCP,
As you notice, it’s a Nexus, it still runs on Android 6.01 version, not the latest. And I really do not want to “manufacturer re-set” back to original setting, just too much work, not to mention, a reality that I may not able to get updates from Android as the version is old, which really put me in a more difficult position. I am financially tight now and hoping to continue to use this Nexus 5 for another year before I can afford a new phone.
I also noticed from the website here, there is a "FirstEver" Andriod 8.1 for nexus 5 hammerhead available, Will it solve my WiFi problem/ error? Also, it will be nice for my Nexus 5, right? My phone is still running on Android 6 !
Any suggestions, please. Thank you all !

Hello, unfortunately this was very common on the nexus 5. It is a hardware issue. It has something to do with the WiFi chip that's on the motherboard.
It happened to me and funny enough I'm responding to you on that same Nexus 5.
My solution was to buy a used (damaged external) Nexus with functioning internals; CPU, motherboard, BT, WiFi etc etc and then swap out the damage motherboard with the used one. You would have to either flash/reset an OS on the replacement motherboard to "clean" it up.
There's a few tutorials here on XDA on how to disassemble the the back and battery removal. Do a quick search on Google with the addition of "XDA" on the end of the search criteria. The search bar here on XDA is terrible.
Good luck.

Mojar7070 said:
Hello, unfortunately this was very common on the nexus 5. It is a hardware issue. It has something to do with the WiFi chip that's on the motherboard.
It happened to me and funny enough I'm responding to you on that same Nexus 5.
My solution was to buy a used (damaged external) Nexus with functioning internals; CPU, motherboard, BT, WiFi etc etc and then swap out the damage motherboard with the used one. You would have to either flash/reset an OS on the replacement motherboard to "clean" it up.
There's a few tutorials here on XDA on how to disassemble the the back and battery removal. Do a quick search on Google with the addition of "XDA" on the end of the search criteria. The search bar here on XDA is terrible.
Good luck.
Click to expand...
Click to collapse
@Mojar7070,
Thanks for yr reply.
My situation is WiFi sometimes works, sometimes it does'nt. That's why it is difficult for me to determine IF it is a hardware/software issue. Do you think by replacing the pair antenna will work?
https://www.ebay.com/itm/1-Pair-Wir...-LG-Google-Nexus-5-D820-D821-USA/252497470238
I hear what you said, it just that it is difficult to determine the used one truly does not have other hardware error inside, until it's too late, more importantly, I am not someone who is really good in repairing hardware.
Can you share with me how do I go by backing-up the whole Android OS + all data onto my computer? Especially the Android OS....
Million thanks,

Hello, I don't think the wire itself is the issue. You can try, I'm just not sure.
Do you have custom recoveryOr at least have have the boot bootloader unlocked on your phone??
Having TWRP recovery simplifies everything as far as backing up information on the phone.
Your options for downloading from your phone is limited since WiFi is broke. Do you have some data room to upload information to Google backup?? That may be your only option, especially if you're not on a custom recovery.

Mojar7070 said:
Hello, I don't think the wire itself is the issue. You can try, I'm just not sure.
Do you have custom recoveryOr at least have have the boot bootloader unlocked on your phone??
Having TWRP recovery simplifies everything as far as backing up information on the phone.
Your options for downloading from your phone is limited since WiFi is broke. Do you have some data room to upload information to Google backup?? That may be your only option, especially if you're not on a custom recovery.
Click to expand...
Click to collapse
Hello,
Thanks for yr replies.
At this stage, I don't a custom recovery/ boot-loader/ TWRP, BUT see this link below especially step 4 and 5 are exactly what you are saying?! :
https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#comment-113
If I go get the Android 8 thru them now, it seems to me step 4 & 5 cover what you just mentioned !?
But the thing is, from logical thinking, I should be backing up FIRST, in case if anything don't work out ! Right ?? I know Windows PC, not anroid phones/ OS !!
You are right ON, unless I want to pay more $ for data thru T-mobile LTE for this backup....
When I connect the phone to my PC thru USB, seems to me all things are presented. Can I just copy/ paste onto a folder I create on my PC, but I take it that's NOT bootable ? Or should then put it onto a USB flash drive to make it bootable?
Thank you,

STDupont said:
Hello,
Thanks for yr replies.
At this stage, I don't a custom recovery/ boot-loader/ TWRP, BUT see this link below especially step 4 and 5 are exactly what you are saying?! :
https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#comment-113
If I go get the Android 8 thru them now, it seems to me step 4 & 5 cover what you just mentioned !?
But the thing is, from logical thinking, I should be backing up FIRST, in case if anything don't work out ! Right ?? I know Windows PC, not anroid phones/ OS !!
You are right ON, unless I want to pay more $ for data thru T-mobile LTE for this backup....
When I connect the phone to my PC thru USB, seems to me all things are presented. Can I just copy/ paste onto a folder I create on my PC, but I take it that's NOT bootable ? Or should then put it onto a USB flash drive to make it bootable?
Thank you,
Click to expand...
Click to collapse
Hello,
Yes, steps 4 and 5 from that site is what I'm referring to. Like I've mentioned before search here on XDA for actually guides and tutorials.
Installing TWRP recovery is the very first step in "fully" backing up your device. Data, OS, user preference and all apps. Plugging into a PC and moving personal folders and files is just that. Transferring files and folders. Now, you can definitely do that and have your personal data on the PC but if you plan to install the 8.1 Android OS anyways you'll need TWRP recovery. So why not "kill two birds with one stone."
You are correct, simply transferring files/folders will not translate to a bootable medium. Having a TWRP backup will do just that. It will act like a "bootable" file whenever you need to roll back to a previous state.
Once you search a guide/tutorial, you'll find that the whole process is done through a PC. So you'll be fine. But please read through the guides first and get familiar with the process before typing any commands in.
Good luck.

Mojar7070 said:
Hello,
Yes, steps 4 and 5 from that site is what I'm referring to. Like I've mentioned before search here on XDA for actually guides and tutorials.
Installing TWRP recovery is the very first step in "fully" backing up your device. Data, OS, user preference and all apps. Plugging into a PC and moving personal folders and files is just that. Transferring files and folders. Now, you can definitely do that and have your personal data on the PC but if you plan to install the 8.1 Android OS anyways you'll need TWRP recovery. So why not "kill two birds with one stone."
You are correct, simply transferring files/folders will not translate to a bootable medium. Having a TWRP backup will do just that. It will act like a "bootable" file whenever you need to roll back to a previous state.
Once you search a guide/tutorial, you'll find that the whole process is done through a PC. So you'll be fine. But please read through the guides first and get familiar with the process before typing any commands in.
Good luck.
Click to expand...
Click to collapse
Hello,
Thank you for yr confirmation, I was not sure, but you strengthen my thought.
Would you please pinpoint to me just where exactly I can read the "guide/ tutorial" section that applies in my situation? This website is so big, I almost "lost in ocean" here....
I will first backup my Nexus 5 today, and waiting for yr "guide/ tutorial" section, mostly like do the installation android 8.1 either Monday night or tuesday night. I notice the guy at FirstEver already produced his custom Android 9.0 version, but it is too new for me, I am thinking he is still perfecting his version, just a thought !
Have you tried the new 9.0 Android yet?
Thank you,

Mojar7070 said:
Hello,
Yes, steps 4 and 5 from that site is what I'm referring to. Like I've mentioned before search here on XDA for actually guides and tutorials.
Installing TWRP recovery is the very first step in "fully" backing up your device. Data, OS, user preference and all apps. Plugging into a PC and moving personal folders and files is just that. Transferring files and folders. Now, you can definitely do that and have your personal data on the PC but if you plan to install the 8.1 Android OS anyways you'll need TWRP recovery. So why not "kill two birds with one stone."
You are correct, simply transferring files/folders will not translate to a bootable medium. Having a TWRP backup will do just that. It will act like a "bootable" file whenever you need to roll back to a previous state.
Once you search a guide/tutorial, you'll find that the whole process is done through a PC. So you'll be fine. But please read through the guides first and get familiar with the process before typing any commands in.
Good luck.
Click to expand...
Click to collapse
Hello Mojar7070,
I ran into some difficulties as I am trying to back-up, seeking guidance:
On Step4 of the FirstEver pages-https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#
When I typed adb root bootloader, on my DOS black screen of my computer, it says:
"adb" is not recognized as in internal or external command operable program or batch file.
Earlier, as I was doing the ADB , step 9 and step 10 did not pop up, but it did say completed in blue little screen, I did that 3 times, same thing, following their instruction as below:
https://androidmtk.com/download-best-android-adb-driver
Any suggestions ? Thank you,

STDupont said:
Hello Mojar7070,
I ran into some difficulties as I am trying to back-up, seeking guidance:
On Step4 of the FirstEver pages-https://www.firstever.eu/first-ever-android-8-1-for-nexus-5/#
When I typed adb root bootloader, on my DOS black screen of my computer, it says:
"adb" is not recognized as in internal or external command operable program or batch file.
Earlier, as I was doing the ADB , step 9 and step 10 did not pop up, but it did say completed in blue little screen, I did that 3 times, same thing, following their instruction as below:
https://androidmtk.com/download-best-android-adb-driver
Any suggestions ? Thank you,
Click to expand...
Click to collapse
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
https://forum.xda-developers.com/google-nexus-5/general/how-to-nexus-5-one-beginners-guide-t2510966
Hello,
Try out 1 or both of the links above. That should get you started in the right direction.
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
Mojar7070 said:
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
https://forum.xda-developers.com/google-nexus-5/general/how-to-nexus-5-one-beginners-guide-t2510966
Hello,
Try out 1 or both of the links above. That should get you started in the right direction.
Click to expand...
Click to collapse
https://forum.xda-developers.com/go...ol-tool-one-driversunlocktwrpfactory-t3358707
Try this one as well. It's an all in one root tool.
Good luck.

Mojar7070 said:
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
https://forum.xda-developers.com/google-nexus-5/general/how-to-nexus-5-one-beginners-guide-t2510966
Hello,
Try out 1 or both of the links above. That should get you started in the right direction.
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
https://forum.xda-developers.com/go...ol-tool-one-driversunlocktwrpfactory-t3358707
Try this one as well. It's an all in one root tool.
Good luck.
Click to expand...
Click to collapse
Hello Mojar7070,
From the first link you gave me, I ran into more difficulties....( the instruction of that link is no where near the actual scene I ran into....see below 1-5 )
I clicked the download link for Android SDK, my plan was first to get the ADB working.
I got the Android Studio thing that's about over 1GB,
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
#2-5 are no where like that at all. See the photo below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After the download installation, i got the first photo, double click to install, took more than hour and half, finally says cannot be done, see photo #2, also during installtion, see Java error.
What did i do wrong??

STDupont said:
Hello Mojar7070,
From the first link you gave me, I ran into more difficulties....( the instruction of that link is no where near the actual scene I ran into....see below 1-5 )
I clicked the download link for Android SDK, my plan was first to get the ADB working.
I got the Android Studio thing that's about over 1GB,
From the link-ADB and Fastboot Installation
1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
2. Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....
#2-5 are no where like that at all. See the photo below:
After the download installation, i got the first photo, double click to install, took more than hour and half, finally says cannot be done, see photo #2, also during installtion, see Java error.
What did i do wrong??
Click to expand...
Click to collapse
Hello,
I think you should try the last link. The all in one tool. I know it took me a few times to figure out how to correlate the instructions to what is on the PC screen. The all in one tool simplifies everything.
You can YouTube the tutorials as well get a step by step process.
Good luck.

Hello,
Seems to me that All-In-1 tool can do many things.
But in my situation now, i first need to get the ADB works otherwise I cannot move forward getting back-up, does that "install driver" will get the adb works? If not, which function should I select?
Thanks,

Mojar7070 said:
Hello,
I think you should try the last link. The all in one tool. I know it took me a few times to figure out how to correlate the instructions to what is on the PC screen. The all in one tool simplifies everything.
You can YouTube the tutorials as well get a step by step process.
Good luck.
Click to expand...
Click to collapse
Hello Mojar7070,
Just now, i tried SDK thing again, noticed that JAVA error, i went ahead the got the latest JAVA April 2019 version, this time, the SDK went ok without any error this time.
My question is: when I go back to DOS, to type the cmd command(s) according the FirstEver's instruction #4/ 5, how do I use the SDK thing to solve the " adb is not recognized as an internal or external command operable program or batch file" error ??
Thank you,

STDupont said:
Hello Mojar7070,
Just now, i tried SDK thing again, noticed that JAVA error, i went ahead the got the latest JAVA April 2019 version, this time, the SDK went ok without any error this time.
My question is: when I go back to DOS, to type the cmd command(s) according the FirstEver's instruction #4/ 5, how do I use the SDK thing to solve the " adb is not recognized as an internal or external command operable program or batch file" error ??
Thank you,
Click to expand...
Click to collapse
Gentelmen/ Ladies,
I truly need some help here !
FYI, I did not try the last link, as it seems more complicated and does not looks like it can solve my situation.
I am stuck, first link: downloaded and installation the thing SDK, tried typing the command in DOS, same thing. It is very very frustrated when the instruction(s) are no where near the actual thing from what I see....
Anyone here located near downtown Los Angeles ? Thank you...

[GUIDE] Odin on Linux [VirtualBox]

Odin 3 running inside VirtualBox on PureOS, a Debian-based Linux distribution:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found a way to get Odin running on Linux! It uses a virtual machine (VM), but it works better than heimdall for newer devices, and is much better than dual booting Windows just to use Odin. Used it to flash Lineage OS 20 to my Samsung Galaxy A52 4G multiple times. Here are the steps I used to install and use Odin on Linux.
I highly recommend reading through the steps once before following them, especially the "Things to know" and "Solutions to common problems" sections.
Install VirtualBox:
Download VirtualBox for your distribution from virtualbox.org,
Right click on the downloaded file,
Click "Open With",
Click on "Software Install" or something similar,
Install according to onscreen instructions,
NOTE: if you don't have an app like "Software Install", you can either install the downloaded file manually - How to install .deb, How to install a .rpm; or try to install VirtualBox with a package manager such as apt, synaptic, etc. However, VirtualBox may not be included with your distribution and it probably will not be the newest version. In either case, skip the above four steps.
Download the VirtualBox Extension Pack from virtualbox.org,
Right click on the ".vbox-extpack" file you just downloaded,
Click "Open With", and select VirtualBox,
Follow the onscreen instructions to install it.
Create a Windows VM:
Download the correct version (32-bit or 64-bit) of Windows 10 from microsoft.com,
NOTE: If Microsoft gives you an error like: "We are unable to complete your request at this time. Some users, entities and locations are banned from using this service..." when you are using a VPN, then just start the download on a normal network, pause the download, switch to your VPN, and then continue - It worked for me!
Run VirtualBox,
Click "New",
Type "Windows 10" in the "Name" entry,
Select the Windows ISO image you downloaded earlier,
Click "Next",
Enter a username and password, and change the host-name to "Windows",
NOTE: You will need to remember your password, because even though you don't have to enter it every time, you will be required to change it every month, which requires your current password.
Click "Next",
Set the "Base Memory" to 1GB (1024MB) for 32-bit, or 2GB (2048MB) for 64-bit,
Leave the "Processors" at 1,
Click "Next",
Select "Create a Virtual Hard Disk Now",
Set the "Disk Size" to whatever meets your requirements (Just remember that Windows needs 20GB, Samsung firmware needs ~17 GB (You can store it on a USB drive though), and that the virtual drive does take up space on your computer),
Click "Next",
Verify everything is as you expected,
Click "Finish",
Windows should now boot up and start installing itself, once it is done it will do multiple things, and finally boot to the desktop.
Install Odin on the Windows VM:
(The steps in this section are to be done on the VM)
(To make this section easier, open this webpage on the VM)
Download the newest Samsung drivers from developer.samsung.com,
Open the "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" file you downloaded,
Follow the onscreen directions to install the USB drivers,
Download Odin from androidfilehost.com,
Extract "Odin_3.13.1.zip",
Run "Odin3 v3.13.1" found in the newly extracted "Odin_3.13.1" folder,
Odin should run fine, BUT DON'T USE IT FOR YOUR PHONE YET, for now just close it.
Get USB working with the Windows VM:
In the terminal, run the following (this unloads the "cdc_acm" module, which can be re-added by running "insmod cdc_acm"):
Bash:
sudo rmmod cdc_acm
With the Windows VM powered off, run VirtualBox,
Click "Settings",
Click "USB",
"Enable USB Controller" should be auto-checked, but manually choose either the 2.0 or 3.0 controller (if one isn't already selected), according to your computer's USB ports,
Close VirtualBox,
In the terminal, run the following:
Bash:
sudo usermod -a -G vboxusers $USER
Log out and log back in (of your computer),
Run VirtualBox,
Click "Settings",
Click "USB",
Plug your phone into your computer while in download mode,
Click on the icon of a USB cable with a plus sign,
Your phone should show up as something like "Samsung SM6150 [021B]",
Click on the box next to where your phone is listed,
Your phone should now show up under "USB Device Filters",
Click "OK",
Unplug your phone,
Exit download mode.
Using Odin on the Windows VM:
Run VirtualBox,
Select "Windows 10",
Click "Start",
(The following steps are to be done on the Windows virtual machine),
Right click on the "Odin3v3.13.1" app you downloaded,
Select "Run as Administrator",
Odin should now recognize your device if you plug it in (be aware that your device will not show up if it's not in the mode it was in when you added it to the USB filters).
Things to know:
To turn the VM off, click on the Windows logo in the bottom right, and then click on the power icon.
To turn the VM on, run VirtualBox, Select the "Windows 10" VM, and click "Start".
VirtualBox uses something called "USB filters" to decide whether the host OS (Linux), or the Windows VM get access to specific devices when they are plugged in, for information on how this works, look here. NOTE: If the VM is off, everything you plug in will open on the host OS, regardless of filters.
If you have files you want to move from your Linux computer to your Windows virtual machine, you can use a thumb drive, to do so add the drive to your USB filters (see above), make sure the VM is off, move the files you want to transfer from the Linux host onto the drive, eject the drive, unplug it, power on the VM, plug the drive back in, Windows should then see the drive, so move the files from the drive to the VM.
Solutions to common problems:
If Odin is unable to see your device after following this tutorial try to unplug as many USB devices as you can from your computer (except your phone) and restart Odin.
If you encounter a "Kernel driver not installed" error when installing VirtualBox, look here.
If Odin gets stuck on "SetupConnection" during a flash, follow these steps.
If you have any problems and/or questions, let me know.
Hope this helps!

@ethical_haquer I wil give it a try next time I find a device I wouldn't mind loosing.
Which Linux are you using?
Will the VM survive a reboot?
I use Windows on my dual boot PCs just audio stuff and for flashing TWRP or stock firmwares.

bmwdroid said:
@ethical_haquer I wil give it a try next time I find a device I wouldn't mind loosing.
Which Linux are you using?
Will the VM survive a reboot?
I use Windows on my dual boot PCs just audio stuff and for flashing TWRP or stock firmwares.
Click to expand...
Click to collapse
I'm using PureOS, it's based off Debian, but VirtualBox runs on many different flavors of Linux. The VM runs fine, shutting it down with "shutdown /s " shuts it down safely.

ethical_haquer said:
I'm using PureOS, it's based off Debian, but VirtualBox runs on many different flavors of Linux. The VM runs fine, shutting it down with "shutdown /s " shuts it down safely.
Click to expand...
Click to collapse
I wanted to know if I have to redo the VM installation procedure every time after a Linux shutdown or if the VM survives?

bmwdroid said:
I wanted to know if I have to redo the VM installation procedure every time after a Linux shutdown or if the VM survives?
Click to expand...
Click to collapse
No, the virtual machine is stored on it's own virtual disk on the drive. I have shut down my computer many times, and the VM still runs fine.

bmwdroid said:
@ethical_haquer I wil give it a try next time I find a device I wouldn't mind loosing.
Which Linux are you using?
Will the VM survive a reboot?
I use Windows on my dual boot PCs just audio stuff and for flashing TWRP or stock firmwares.
Click to expand...
Click to collapse
Let me know how it goes when you do it.

Thanks @ethical_haquer , I'm ready to try the method, but I'm asking why do you recommand only 1 cpu ? Is it really a problem to set more ?

Pierro29 said:
Thanks @ethical_haquer , I'm ready to try the method, but I'm asking why do you recommand only 1 cpu ? Is it really a problem to set more ?
Click to expand...
Click to collapse
You can use more than one CPU if you'd like, see here, but sometimes people have problems setting it up, and you don't really need more than one CPU if you're just using the VM for flashing. That's why I didn't include it in this tutorial. If you want more than one CPU to be used, feel free to though. Let me know if you encounter any issues when following the directions.

ethical_haquer said:
Let me know how it goes when you do it.
Click to expand...
Click to collapse
I will but didn't have the necessity yet.
Realized although that I may have to get another key from somewhere.

bmwdroid said:
Realized although that I may have to get another key from somewhere.
Click to expand...
Click to collapse
What key?

ethical_haquer said:
What key?
Click to expand...
Click to collapse
the activation key.
Don't have one as I installed 8.1 as OEM on the notebook and then upgraded to 11 without needing one.
The 8.1 key isn't printed on the back but just worked.

bmwdroid said:
the activation key.
Don't have one as I installed 8.1 as OEM on the notebook and then upgraded to 11 without needing one.
The 8.1 key isn't printed on the back but just worked.
Click to expand...
Click to collapse
Activation is mandatory for this method ?
Another question, Odin V3.14.4 is better? or is it safer to stay with V3.13.1 ?
Thanks

Pierro29 said:
Activation is mandatory for this method ?
Click to expand...
Click to collapse
No, I think @bmwdroid is talking about something with his phone.

ethical_haquer said:
No, I think @bmwdroid is talking about something with his phone.
Click to expand...
Click to collapse
I meant the Windows key

bmwdroid said:
I meant the Windows key
Click to expand...
Click to collapse
What Windows key? I can head over to the Windows website I linked to and download it without any key.

bmwdroid said:
the activation key.
Don't have one as I installed 8.1 as OEM on the notebook and then upgraded to 11 without needing one.
The 8.1 key isn't printed on the back but just worked.
Click to expand...
Click to collapse
You can use a KMS activator. Free and easy

ethical_haquer said:
What Windows key? I can head over to the Windows website I linked to and download it without any key.
Click to expand...
Click to collapse
I know and did but thought I need one for installing it on the VM.
At least that's what I understood from reading this:
<will begin the Windows install process just as you might see when installing natively on a PC>

bmwdroid said:
I know and did but thought I need one for installing it on the VM.
At least that's what I understood from reading this:
<will begin the Windows install process just as you might see when installing natively on a PC>
Click to expand...
Click to collapse
I just looked through the instructions you linked to, and I didn't see anything talking about activation keys. This isn't the exact same as installing it on a PC, as we are downloading an ISO image in this guide. I know you don't need a key because I followed this guide myself after I created it to make sure I didn't forget anything.

ethical_haquer said:
I just looked through the instructions you linked to, and I didn't see anything talking about activation keys. This isn't the exact same as installing it on a PC, as we are downloading an ISO image in this guide. I know you don't need a key because I followed this guide myself after I created it to make sure I didn't forget anything.
Click to expand...
Click to collapse
You do not need a product key to use Windows 10. I think you can skip the product key prompt.

ethical_haquer said:
I found a way to get Odin running on Linux! It uses a virtual machine (VM), but it works better than heimdall for newer devices, and is much better than dual booting Windows just to use Odin. Used it to flash Lineage OS 20 to my Samsung Galaxy A52 4G multiple times. Here are the steps I used to install and use Odin on Linux.
I highly recommend reading through the steps once before following them, especially the "Things to know" section.
Install VirtualBox:
Download VirtualBox for your distribution from virtualbox.org,
Right click on the downloaded file,
Click "Open With",
Click on "Software Install", or something similar,
Install according to onscreen instructions,
# Note: if you don't have an app like "Software Install", you can skip the above steps and try to install VirtualBox with a package manager such as apt, synaptic, ect. However, VirtualBox may not be included with your distribution and it probably will not be the newest version.
Download the VirtualBox Extension Pack from virtualbox.org,
Right click on the ".vbox-extpack" file you just downloaded,
Click "Open With", and select VirtualBox,
Follow the onscreen instructions to install it.
Create a Windows VM:
Download the correct version (32-bit or 64-bit) of Windows 10 from microsoft.com,
Run VirtualBox,
Click "New",
Type "Windows 10" in the "Name" entry,
Select the Windows ISO image you downloaded earlier,
Click "Next",
Enter a username and password, and change hostname to "Windows",
Click "Next",
Set the "Base Memory" to 1GB (1024MB) for 32-bit, or 2GB (2048MB) for 64-bit,
Leave the "Processors" at 1,
Click "Next",
Select "Create a Virtual Hard Disk Now",
Set the "Disk Size" to 20GB,
Click "Next",
Verify everything is as you expected,
Click "Finish",
Windows should now boot up and start installing itself, once it is done it will do multiple things, and finally boot to the desktop.
Install Odin on the Windows VM:
(The steps in this section are to be done on the VM)
(To make this section easier, open this webpage on the VM)
Download the newest Samsung drivers from developer.samsung.com,
Open the "SAMSUNG_USB_Driver_for_Mobile_Phones.exe" file you downloaded,
Follow the onscreen directions to install the USB drivers,
Download Odin from androidfilehost.com,
Extract "Odin_3.13.1.zip",
Run "Odin3 v3.13.1" found in the newly extracted "Odin_3.13.1" folder,
Odin should run fine, BUT DON'T USE IT FOR YOUR PHONE YET, for now just close it.
Get USB working with the Windows VM:
In the terminal, run the following:
Bash:
modprobe -r cdc_acm
cd /etc/modprobe.d/
ls
In the output from "ls" there should be one file, named something like "dkms.conf" or "blacklist.conf".
In the terminal, run the following, replacing "yourfilename.conf" with the output of the "ls" command:
Bash:
sudo nano yourfilename.conf
Add the following line to the file:
Code:
blacklist cdc_acm
To safe your changes to the file, hit Ctrl+x, y, and Enter,
With the Windows VM powered off, run VirtualBox,
Click "Settings",
Click "USB",
"Enable USB Controller" should be auto-checked, but manually choose either the 2.0 or 3.0 controller (if one isn't already selected), according to your computer's USB ports,
Close VirtualBox,
In the terminal, run the following:
Bash:
sudo usermod -a -G vboxusers $USER
Log out and log back in (of your computer),
Run VirtualBox,
Click "Settings",
Click "USB",
Plug your phone into your computer while in download mode,
Click on the icon of a USB cable with a plus sign,
Your phone should show up as something like "Samsung SM6150 [021B]",
Click on the box next to where your phone is listed,
Your phone should now show up under "USB Device Filters",
Click "OK",
Unplug your phone,
Exit download mode.
Using Odin on the Windows VM:
Run VirtualBox,
Select "Windows 10",
Click "Start",
(The following steps are to be done on the Windows virtual machine),
Right click on the "Odin3v3.13.1" app you downloaded,
Select "Run as Administrator",
Odin should now recognize your device if you plug it in (be aware that your device will not show up if it's not in the mode it was in when you added it to the USB filters).
Things to know:
To turn the VM off, type "shutdown /s" in the PowerShell.
To turn the VM on, run VirtualBox, Select the "Windows 10" VM, and click "Start".
VirtualBox uses something called "USB filters" to decide whether the host OS (Linux), or the Windows VM get access to specific devices when they are plugged in, for information on how this works, look here.
If Odin gets stuck on "SetupConnection" during a flash, follow these steps.
If you have files you want to move from your Linux computer to your Windows virtual machine, you can use a thumb drive, to do so add the drive to your USB filters (see above), make sure the VM is off, move the files you want to transfer to the drive from the Linux host, eject the drive, unplug it, power on the VM, plug the drive back in, Windows should then see the drive, so move the files from the drive to the VM.
If you have any problems and/or questions, let me know.
Hope this helps!
Click to expand...
Click to collapse
Hello fellow Linux user,
Might I suggest another similar method: QEMU and Libvirt (VirtManager). The only difference is it's lighter and more configurable than Virtualbox. USB passthrough is much simpler to setup in my experience and setup isn't terribly hard. I seem to have an issue with VBOX drivers, so this became my workaround for anything VM related.
You can install using the following commands:
DEBIAN:
sudo apt update && sudo apt install qemu virt-manager
ARCH:
sudo pacman -Syu qemu-full virt-manager
FEDORA:
sudo dnf update && sudo dnf install qemu qt-virt-manager
GENTOO:
sudo emerge --ask --verbose app-emulation/qemu virt-manager
Best regards,
D'Tor Aelek of Romulus