Database Info

[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.

[DRIVERS] Latest HTC Drivers [4.2.0.001]

Latest HTC Drivers
Latest HTC Drivers extracted from HTC Sync v3.3.21 and HTC Sync Manager v2.0.61.0
Latest Driver Version (HTC Sync): 4.0.1.001
Latest Driver Version (HTC Sync Manager): 4.2.0.001
BMP Drivers are the same for both sets of drivers.
For those who don't want to have to download 120 some MB of bloatware called HTC Sync
Instructions:
Determine if your system is 32-bit or 64-bit
Download the BMP Driver for your OS type (x86 version if on 32-bit, x64 if on 64-bit)
Download the newest HTCDrivers file (choose either the "EXE" or "MSI" driver file, but not both)
Disable any antivirus program(s) present
Run both files downloaded above (the BMP.msi and the HTCDriver file)
Re-enable your antivirus program(s)
Click to expand...
Click to collapse
Links
ALL DRIVER FILES: www.mediafire.com/?o10b16j5b3r3o
OEM SETUP FILES: www.mediafire.com/?1rwmleoe17akd
Updated on 6.6.13
HTCDriver_4.2.0.001.exe
SyncManager_2.0.61.0.exe
Updated on 4.23.13
HTCDriver_4.1.0.001.msi
HTCDriver_4.1.0.001.exe
HTCPluginChecker.exe
HTCSync_3.3.21.exe
SyncManager_2.0.53.0.exe
SyncManager_2.0.53.0_STRIPPED.exe
Updated on 4.02.13
RemoveOldHTCDriver3.exe (packaged in HTC Sync Manager v2.0.41.0)
Removed duplicate x86 BMP Driver
Updated instructions with link to determine if on 32-bit or 64-bit
Updated on 3.31.13
HTCDriver_4.0.1.002.exe
HTCDriver_4.0.1.002.msi
IPTInstaller_4.0.8.msi
Updated on 3.6.13
HTC_BMP_USB_Driver_x86_1.0.5375.msi
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTCDriver_4.0.1.001.exe
HTCDriver_4.0.1.001.msi
Updated on 11.28.12
HTC BMP USB Driver_x86.msi DELETED: Turned out to be the same 1.0.5375 as above. Download from link above.
HTCDriver_3.0.0.023.msi
Click to expand...
Click to collapse
------------
MD5 CHECKSUMS
Sometimes downloading from the internet can yield a corrupt download. To prevent this, make sure you always check the md5 checksum (also known as "md5sum") of the file. This method verifies the digital integrity of the file by verifying its digital signature with the MD5 algorithm.
After you download each file, make sure to check that the md5sum matches what is given.
Code:
[LIST]
[*]25912deacc5d55528e223ec7b99705cc [B]*HTCDriver_3.0.0.023.msi[/B]
[*]220c41f3b03f42190899db8cb081b5c6 [B]*HTCDriver_4.0.1.001.exe[/B]
[*]a578d837343fe2542ecf405a630d46a0 [B]*HTCDriver_4.0.1.001.msi[/B]
[*]8223ec1c2aa71503b431a0daabb23154 [B]*HTCDriver_4.0.1.002.exe[/B]
[*]4dfbd4ae8662124d06e0a04db2065069 [B]*HTCDriver_4.0.1.002.msi[/B]
[*]bf24b0adc2f792ee4180ca545e4b60a0 [B]*HTC_BMP_USB_Driver_x32_1.0.5375.msi[/B]
[*]7b461095d56f9a6814d8f3e14cac0859 [B]*HTC_BMP_USB_Driver_x64_1.0.5375.msi[/B]
[*]96e6d181192a995214493a6828e4287d [B]*IPTInstaller_4.0.8.msi[/B]
[*]92bd34ec7787e631231c68aba392b6e7 [B]*RemoveOldHTCDriver3.exe[/B]
[*]f281d8994ab9f1315828ac2226a9bb75 [B]*HTCDriver_4.1.0.001.exe[/B]
[*]ed6d5fc5cc7dcca653f7a0beab01035d [B]*HTCDriver_4.1.0.001.msi[/B]
[*]96589c02be46fd7b85160d5b15f4c88a [B]*HTCPluginChecker.exe[/B]
[*]36ba2c8627ba18c6540bfa25be3b67fc [B]*HTCSync_3.3.21.exe[/B]
[*]a356e5c828c7cb3869dc67058e5bbc2c [B]*SyncManager_2.0.53.0.exe[/B]
[*]da1e40e478725d3e829243e84043d21f [B]*SyncManager_2.0.53.0_STRIPPED.exe[/B]
[/LIST]
Click to expand...
Click to collapse
How to check the md5sum of a file:
Windows:
For windows you need to download the md5sum binary. I recommend the one from my dev-host.
After that, copy the file you're trying to verify to the directory where where you downloaded the "md5sum.exe"
Once that is finished, do SHIFT+RIGHT CLICK (inside the folder window) and choose "Open command window here"
{
"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"
}
Then type the following ("fileNameHere" must include the extension):
Code:
md5sum fileNameHere
That will output a hash, which you can compare to the ones above.
Linux: No need to download anything, md5sum binaries are included in all distros, as far as I know.
Open a terminal and type the following ("fileNameHere" must include the extension):
Code:
$ cd path/to/download/folder
$ md5sum fileNameHere
Two important notes:
This method can be used with any files you download, as long as the download site (or the dev themself) provides the correct md5sum.
If any of the digits do not match exactly, you need to download the file again.

Updated OP with md5sum how-to and checksums.

Wow really cool, I have always hated installing htc sync Thank you a thousand times!!!

No problem :good:

What about the Universal Naked Driver thread?
Are these drivers in any way more up-to-date or in other ways better than those? Or additional?
I currently use that driver package and am setup quite well with it. But i think i still had to set up HTCSync to get the MTP drivers. Not sure anymore lol.

MSI files don't seem to install. Getting error messages on ALL. Error 2732 Directory Manager not initialised.
edit: disregard, just temporarily disabled UAC settings and it worked.

Sneakyghost said:
What about the Universal Naked Driver thread?
Are these drivers in any way more up-to-date or in other ways better than those? Or additional?
I currently use that driver package and am setup quite well with it. But i think i still had to set up HTCSync to get the MTP drivers. Not sure anymore lol.
Click to expand...
Click to collapse
I believe that the universal naked drivers would work just as well, but for ADB only
For the purposes of transferring files using either MTP or UMS, you need the HTC drivers
EDIT: If you look at the thread, the drivers were last updated Nov. of 2012, so I would say that these are more up to speed than those

Thanks for this! Worked like a charm Bud! Glad I stumbled into this very nice not to deal with HTC Sync :good:

AW: [DRIVERS] Latest HTC Drivers [v4.0.1.002]
CNexus said:
I believe that the universal naked drivers would work just as well, but for ADB only
For the purposes of transferring files using either MTP or UMS, you need the HTC drivers
EDIT: If you look at the thread, the drivers were last updated Nov. of 2012, so I would say that these are more up to speed than those
Click to expand...
Click to collapse
Ok cool thanks I had that feeling that the universal drivers are ADB only but want sure anymore. Then I thank you for this nice extraction. Very handy.
Sent from Viper 2.2

Re: [DRIVERS] Latest HTC Drivers [v4.0.1.002]
Sneakyghost said:
Ok cool thanks I had that feeling that the universal drivers are ADB only but want sure anymore. Then I thank you for this nice extraction. Very handy.
Sent from Viper 2.2
Click to expand...
Click to collapse
No problem :thumbup:

Got an idea, the MD5 verification you posted sounds awefully complicated. Why don't you just recommend windows and/or mac users to install HashTab? Its a Windows Shell extension that produces a new tab on the properties dialogue for each file and lets you compare hashes by just c/p any hash you want from one file property into another.
It's free and totally cool. You find it here: http://www.implbits.com/hashtab.aspx
[EDIT]
I am having issues identifying which driver packages i have to install on my windows 7 x64. I just went through all of them (apart the obvious x86 bmp package). I noticed that i had to create a uniqueID folder in \TEMP with another uniqueID subfolder and place one of the MSI packages in there and rename it to what the MSI wanted to have, in order to make that package work.
I assume, the HTC Sync or the Sync Manager would usually unpack those files to that folder and name them accordingly (in fact, i think you extracted them from there the same way i would extract a RUU lol) and then you renamed those packages to include the version numbering? Unfortunately those drivers aren't easy that way for noobs. I wonder if they can be re-packaged with some easy install automator program so that in the end you could offer like a HTC Sync package without the HTC Sync crap in it?

Sneakyghost said:
Got an idea, the MD5 verification you posted sounds awefully complicated. Why don't you just recommend windows and/or mac users to install HashTab? Its a Windows Shell extension that produces a new tab on the properties dialogue for each file and lets you compare hashes by just c/p any hash you want from one file property into another.
It's free and totally cool. You find it here: http://www.implbits.com/hashtab.aspx
[EDIT]
I am having issues identifying which driver packages i have to install on my windows 7 x64. I just went through all of them (apart the obvious x86 bmp package). I noticed that i had to create a uniqueID folder in \TEMP with another uniqueID subfolder and place one of the MSI packages in there and rename it to what the MSI wanted to have, in order to make that package work.
I assume, the HTC Sync or the Sync Manager would usually unpack those files to that folder and name them accordingly (in fact, i think you extracted them from there the same way i would extract a RUU lol) and then you renamed those packages to include the version numbering? Unfortunately those drivers aren't easy that way for noobs. I wonder if they can be re-packaged with some easy install automator program so that in the end you could offer like a HTC Sync package without the HTC Sync crap in it?
Click to expand...
Click to collapse
What windows suite do you have? Before I even started uploading extracted drivers, I tested all of the installations (run from my desktop) on my Windows 7 ultimate x64 laptop, precisely because I suspected it might somehow be blocked. And all (including the msi's) installed with no problem. I've even reinstalled the latest ones (downloading from my own mediafire) after I had to reinstall windows 7 on my laptop. Also, which msi did you have problems installing?

What you need to install is detailed in the OP: the BMP x64 driver, and the HTCDriverXXX.exe (or HTCDriverXXX.msi)

thank you mister, works great for me under win 7 x64 / win 8 x64.

Awesome, thanks for the feedback that it works on Win8, will add to OP. Couldn't test it myself because I have no machines running 8. But thanks :good:

Bump

CNexus said:
Bump
Click to expand...
Click to collapse
hehe, good idea. Thanks.

CNexus said:
What windows suite do you have? Before I even started uploading extracted drivers, I tested all of the installations (run from my desktop) on my Windows 7 ultimate x64 laptop, precisely because I suspected it might somehow be blocked. And all (including the msi's) installed with no problem. I've even reinstalled the latest ones (downloading from my own mediafire) after I had to reinstall windows 7 on my laptop. Also, which msi did you have problems installing?
Click to expand...
Click to collapse
Running Windows 7x64 Ultimate.
Dunno bro probably just some mess on my machine then.
Think if your machine took it alright with the same OS it'll probably be some screw-up on mine.
mobile post

Sneakyghost said:
Running Windows 7x64 Ultimate.
Dunno bro probably just some mess on my machine then.
Think if your machine took it alright with the same OS it'll probably be some screw-up on mine.
mobile post
Click to expand...
Click to collapse
Ok, did you run the MSI version of the drivers? If you did, try the exe version.

I can't remember, will check tomorrow.
mobile post

[ Logcat or it didn't happen! ] How To Logcat (updated 9/6/13 - added 4.3 reqmnts)

Ok, so there's a lot of new people in the Blaze forums here on XDA, and that's great! That means we got more people buying a Blaze, which means more popularity, which hopefully means more support.
However, that also means the forums are getting choked up with "X isn't working, how do I fix?" on things that aren't known issues, and certainly are not the norm.
The first thing everybody should do BEFORE flashing a new ROM is to read all posts made by the OP, usually the top 2 or 3. Those contain critical information, directions, known bugs, fixes, downloads, etc.
Once you flash, if you run into a problem, what should you do? Ask about it in the dev forum?
{
"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"
}
Read the ENTIRE post. The whole thing, from page one to the last. If the post is more than 20 pages long and you've spent less than 35 minutes reading it, then FAIL.
Once you've read the entire forum post from front to back and you're 100% sure this hasn't been covered, then should you ask about it?
Not necessarily.
Logcats. Logcats are important. Logcats are Android's method of telling developers
instead of it being a functioning operating system.
Logcatting is easy. Its fun. It makes you feel important when you give the devs something to go off of instead of "duh, it aint workin', bossman!"
So here's how to logcat:
FIRST! You must have the latest version of ADB on your computer. The only surefire way to get ADB that hasn't been compromised or altered in a malicious way is to download it directly with the Android SDK >>>HERE<<<
For the minimalist, you can get ADB and Fastboot only. See @Romman0's post #6
There are installers for Windows, Linux, and OS X.
Prerequisites
You must have the Android SDK and/or ADB on your computer already set up
You must have your phone's drivers installed on your computer
Your phone must be able to boot past the loading screen
You must connect your phone to your computer with the supplied manufacturers USB data/charging cable
How to logcat: Linux, Windows, and OS X
WARNING! With Android 4.3 (CM 10.2 and 10.2-based ROMs), ADB version 1.0.31 is REQUIRED. You can find out your adb version by running:
Code:
~/.android/sdk/platform-tools$ adb version
C:/Android/SDK/platform-tools>adb version
You may also need to fully boot into Android and and accept Debugging from that computer (you will have to check the box marked always accept, or always trust, or something along those lines) and restart your phone to start the logcat
(Pictures coming soon guys, I'm tired lol)
Open up a terminal (Linux or OS X) or a command prompt (Windows).
Navigate to where the Android SDK is installed on. I always install at:
Code:
Linux: [email protected]: ~$: cd ~/.android/sdk/platform-tools
Windows: C:/Windows/System32> cd C:/Android/SDK/platform-tools
OS X: I dont know where, never done it on Android, but I will soon for the sake of this guide
Your location may be different!
type the following command to make sure ADB recognizes your device is connected. If it's not, Google "ADB wont connect to my device"
Code:
Linux: ~/.android/sdk/platform-tools$ adb devices
Windows: C:/Android/SDK/platform-tools>adb devices
If it is connected, power off your phone completely and type the following command:
Code:
Linux: ~/.android/sdk/platform-tools$ adb logcat > {name of logcat here}.log
Windows: C:/Android/SDK/platform-tools>adb logcat > {name of logcat here}.log
I normally name my logcats with a naming convention, example:
logcat-ROM-version-device-date_time_timezone_of_log.log
example:
CM10.1-20130729-UNOFFICIAL-t769-09AUG2013-2033EST.log
This way, when looking at my logcats, I know:
[LIST]
[*]The Rom
[*]The Build Number
[*]The Device
[*]The date and time the logcat was captured
[/LIST]
your terminal/command prompt will say "Waiting for device to connect...". THIS MESSAGE WILL NOT CHANGE! Just trust that the log cat is will start as soon as the adb service on the phone initiates.
Power on your phone as normal
Try to make the problem appear again
When you've catted as much log as you think you need, hit CTRL + C on Linux or Windows (It's probably CMD + C on OS X, as I said, I've never done this on Mac (yet), but I know how they like to be aggravatingly different so that when I'm using Synergy to share a Mouse and Keyboard between Linux, Windows, and OS X, I keep hitting the wrong keystrokes because I re-grew accustomed to whatever OS i'm using as the primary at the moment). Now hit dir.
Upload your logcat for developer review
Now, I know for a fact that Samsung USB Drivers and ADB communicate perfectly well with the Blaze using the following operating systems. I have tested them personally.
Ubuntu 12.04 x64
Ubuntu 12.10 x64
Ubuntu 13.04 x64
Fedora 17 x64
Fedora 18 x64
Fedora 19 x64
Windows 7 x64
Windows 8 x64
Windows 8.1 Developer Preview x64
I will test out OS X 10.8.4 tomorrow and make sure it works for certain-like
That's it. Any questions, comments, gripes, or complaints? Write your congressman!

Reserved: Because I Can!

I am so happy you did this.
Edit: You should ask a mod to pin this. This is really useful and should be on the top when needed.

Thank you so much for this. I've never been completely sure how to get a logcat, and always felt kind of worthless because of this. Thanks again!
Sent from a Paranoid Blaze

Very nice!
While Windows-specific, beyond this the next best reference I've found was this - just a nice link for sdk/logcat info.
Again, great job on getting this around. Stuff like this should be standard sticky/first post stuff for just about any forum

Here is a modified minimalist version of adb, if anybody wants it.......
http://forum.xda-developers.com/showthread.php?t=2317790

Pin request sent to a mod. here's hoping!
On an additional note, I dont exactly like how it looks and I've never been good with BBcode formatting... is HTML allowed on XDA???
---EDIT---
And we're pinned! Thanks, Naddict

I've read that terminal emulator can do a logcat as well, is that true? Is it the same as doing a logcat through this method?
Sent from a Paranoid Blaze

njstein said:
I've read that terminal emulator can do a logcat as well, is that true? Is it the same as doing a logcat through this method?
Sent from a Paranoid Blaze
Click to expand...
Click to collapse
yes, if running from terminal emulator:
Code:
logcat > /sdcard/logcat.log
That will place the logcat on the root of your SD Card.

jparnell8839 said:
yes, if running from terminal emulator:
Code:
adb logcat > /sdcard/logcat.log
That will place the logcat on the root of your SD Card.
Click to expand...
Click to collapse
Just thought I'd mention the adb shouldn't be there if running from terminal emulator

dwitherell said:
Just thought I'd mention the adb shouldn't be there if running from terminal emulator
Click to expand...
Click to collapse
thanks... dont know what I was thinking :silly:
BTW...
POST # 500!!!!

Okay, call me dumb if you want to but I have a question. As I do not have a manufacturers USB cord, I cannot use this method. However, I'm tired of being useless, can I use CatLog from the Play Store?
It appears to have the ability to record logs, but I honestly have no clue if it's the same thing.

FroBreadCreamJellyPie said:
Okay, call me dumb if you want to but I have a question. As I do not have a manufacturers USB cord, I cannot use this method. However, I'm tired of being useless, can I use CatLog from the Play Store?
It appears to have the ability to record logs, but I honestly have no clue if it's the same thing.
Click to expand...
Click to collapse
Yes. But adb is needed to debug booting issues. Catlog will work fine capturing logs for bugs on working roms.

Romman0 said:
Yes. But adb is needed to debug booting issues. Catlog will work fine capturing logs for bugs on working roms.
Click to expand...
Click to collapse
Awesome, thank you.

FroBreadCreamJellyPie said:
Okay, call me dumb if you want to but I have a question. As I do not have a manufacturers USB cord, I cannot use this method. However, I'm tired of being useless, can I use CatLog from the Play Store?
It appears to have the ability to record logs, but I honestly have no clue if it's the same thing.
Click to expand...
Click to collapse
a manufacturers cord is recommended because it's known and proven to work as is, however, I can tell you that I have yet to run across a MicroUSB cable that didn't work for strictly adb purposes, and I've only seen very few that wouldn't charge my phone.

jparnell8839 said:
a manufacturers cord is recommended because it's known and proven to work as is, however, I can tell you that I have yet to run across a MicroUSB cable that didn't work for strictly adb purposes, and I've only seen very few that wouldn't charge my phone.
Click to expand...
Click to collapse
Then in that case, I'm doing something terribly wrong, lol thanks anyways

Lol
Gửi từ GT-S5360 của tôi bằng cách sử dụng Tapatalk 2

Kali Linux (Chroot) on Galaxy S4 i9505/i9500 [Tutorial]

{
"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"
}
How to Install:
1. Download Linux Deploy from PlayStore
2. Open it and go to settings
3. Selection Distribution: Kali and leave everything else as default, except Disk Image Size, which you should use 7128mb instead of Automatic.
3a. Normally it automatically finds your resolution, but you can change it on this page. (One of the last items.)
4. Then select Install
4a. [IMPORTANT] Be sure to be connected to a Wi-Fi network, otherwise 1.4GB will be downloaded from your Mobile Network.
4b. The downloading time is quite long, and you can't lose connection through that, otherwise the .img will be corrupted.
5. Once you see <<< end: installation on the app, download your favorite VNC client and set-up the following configurations:
IP/Host: localhost or 127.0.0.1
Port: 5900
Password: changeme
Click to expand...
Click to collapse
6. You will notice that there's no tools avaliable, open LXTerminal (From the dropup icon of Kali) then type:
sudo apt-get update
Click to expand...
Click to collapse
and
sudo apt-get upgrade
Click to expand...
Click to collapse
Those are minor commands, to really install the tools see next step
7. Type
sudo apt-get install kali-linux -yq
Click to expand...
Click to collapse
And wait for the full installation to complete, after it's sucesfully done it's good to go!
Q&A:
Which VNC Client you recommend?
I personally like Touchpad mouse settings and a full-screen view, the best free app that does the work for me is bVNC Free.
PostgreSQL gave me an error on the end of installation, is that supposed to happen?
YES, to fix PostegreSQL on Kali Linux ARM you have to whitelist on your network. You can do that by simply typing:
sudo usermod -a -G aid_inet postgres
Click to expand...
Click to collapse
IceWeasel (Internet Browser) is not opening! What's wrong?
For some reason when you first install it, the browser is misconfigured. To solve that type:
sudo apt-get install iceweasel
Click to expand...
Click to collapse
Happy Hacking!

Thanks so much for this!!!
Kali Linux is one of the best pentesting Linux distro.
But, I've get one error triying to install Kali
When I try to install, in the part that sais "making new disk image" the App fails. I try it changing the directory install... but not working.
Thanks in advance!!!
EDIT:
I think the errors was produced by:
First, because I hadn't 7 GB of free space
Second, the filesystem of my external sdcard (fat32) can't support files bigger tan 4 GB.
Triying again!!!

i got the same issue on my Galaxy S4 let me know if u ever find a fix

Works brilliantly. For people having problems on install. You need the following.
1. A phone not running android 4.3
2. Root
3. Busybox
Sent from my GT-I9505 using xda app-developers app

In the last attempt, I lost all my data in the external sdcard.
I don't know what happend exactly, probably I change some option without being aware, and that is the result.
Backup your data before install this!!!!

GruberEXN said:
...
3. Selection Distribution: Kali and leave everything else as default, except Disk Image Size, which you should use 7128mb instead of Automatic.
...
Click to expand...
Click to collapse
Can anything lower than 7128 MB work? I don't have that amount of space free and anything else I try fails to make the image.

::

whats the use of this ?

If you don't know what this is you don't need it
Sent from my GT-I9505 using XDA Premium HD app

so with the s 4 hardware what is possible can it go in to mon mode and does it support packet injection

simkhovich said:
so with the s 4 hardware what is possible can it go in to mon mode and does it support packet injection
Click to expand...
Click to collapse
That's all I want to know before I Flash it
__________________________________
Sent from my M919 w/ Dualboot

Obagleyfreer said:
If you don't know what this is you don't need it
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Wow so you know it already when you first heard of it?
You came also from that point.
Why not help?
Sent from my GT-I9500

gdonanthony said:
whats the use of this ?
Click to expand...
Click to collapse
It's a pentest distribution, made for security profissionals or hobbyists who wants to have all hackers tools at hand for penetration testing at servers.
simkhovich said:
so with the s 4 hardware what is possible can it go in to mon mode and does it support packet injection
Click to expand...
Click to collapse
No, since it's a Chroot installation. It's in a jail, you can't use any connection outside from it apart the internet connection (3g/wifi/2g, etc).
ktetreault14 said:
That's all I want to know before I Flash it
__________________________________
Sent from my M919 w/ Dualboot
Click to expand...
Click to collapse
Sorry, there's no use then.
marc_ecko28 said:
Wow so you know it already when you first heard of it?
You came also from that point.
Why not help?
Sent from my GT-I9500
Click to expand...
Click to collapse
Sorry for the delay.

GruberEXN said:
How to Install:
1. Download Linux Deploy from PlayStore
2. Open it and go to settings
3. Selection Distribution: Kali and leave everything else as default, except Disk Image Size, which you should use 7128mb instead of Automatic.
3a. Normally it automatically finds your resolution, but you can change it on this page. (One of the last items.)
4. Then select Install
4a. [IMPORTANT] Be sure to be connected to a Wi-Fi network, otherwise 1.4GB will be downloaded from your Mobile Network.
4b. The downloading time is quite long, and you can't lose connection through that, otherwise the .img will be corrupted.
5. Once you see <<< end: installation on the app, download your favorite VNC client and set-up the following configurations:
6. You will notice that there's no tools avaliable, open LXTerminal (From the dropup icon of Kali) then type:
and
Those are minor commands, to really install the tools see next step
7. Type
And wait for the full installation to complete, after it's sucesfully done it's good to go!
Q&A:
Which VNC Client you recommend?
I personally like Touchpad mouse settings and a full-screen view, the best free app that does the work for me is bVNC Free.
PostgreSQL gave me an error on the end of installation, is that supposed to happen?
YES, to fix PostegreSQL on Kali Linux ARM you have to whitelist on your network. You can do that by simply typing:
IceWeasel (Internet Browser) is not opening! What's wrong?
For some reason when you first install it, the browser is misconfigured. To solve that type:
Happy Hacking!
Click to expand...
Click to collapse
I go into settings but I cant find distribution. some help please
Sent from my SGH-M919 using xda app-developers app

xda23 said:
I go into settings but I cant find distribution. some help please
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
This should be very simple, but anyway, I uploaded a short video showing how to select it.
It's pretty straightforward, really.
And please, don't quote the whole main post. (and edit this, please.)

There's a lot more to penetration testing then just wifi hacking.

hololight said:
There's a lot more to penetration testing then just wifi hacking.
Click to expand...
Click to collapse
You're actually right, but most of people don't get the whole idea of a penetrating testing operational system.
Can't blame them tho, server security don't interest most of them.

Hi. i have completed the installation everything is done and ready to start, but when I click the start button, it show done for the directories and other stuff, but when it comes down to SSH :22 and VNC :5900 it fails. I cannot connect it to the vnc or ssh.

Mount usb?
Sorry for my english.
I have installed kali successfully, but I need to mount a Tp-link WN722N or similar and I do not know how. Is this possible?
I would be very happy.

I'm having the same problem as tidu12 I've downloaded the distro successfully and I've downloaded the bvnc free, I enter in all the info given (127.0.0.1) port: 5900, and the password "changeme" it gives me this error "connection failed, connection to VNC server failed with reason:failed to connect to /127.0.0.1 (port 5900): connection failed: ECONNREFUSED (Connection refused)" I've also tried to enter in "localhost" for the host instead of the IP address and it gives me the same error.
Thanks in advance!!!

[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