Method 2: Permanently Fix ADB Recognition Error by Setting Environment Variables.Method 1: Temporarily Fix ADB Not Be Recognized Error in Command Prompt.In order to satisfy different people who expect to use ADB normally on computer for And roid device, two methods will be provided to fix the ADB error temporarily and permanently. Method 1: Temporarily Fix ADB Not Be Recognized Error in CMDġ. Android SDK has been downloaded and saved on your computer.Ģ. Steps to temporarily fix ADB not be recognized error C:\Users\isunshare\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\tools.C:\Users\isunshare\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools.Get the location of "platform-tools" and "tools" in Android SDK. You can follow the steps as shown in the following screenshot. Or follow the description under the screenshot. Step 1: Open command prompt on Windows computer. Step 2: Type " adb" and press Enter if it can work successfully. Set ANDROID_PLATFORM_TOOLS ="C:\Users\isunshare\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools" Step 3: Specify " ANDROID_PLATFORM_TOOLS" location with following command. Set path=%path% % ANDROID_TOOLS% % ANDROID_TOOLS% Set ANDROID_TOOLS="C:\Users\isunshare\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\tools" Step 4: Specify " ANDROID_TOOLS" location with following command. Step 6: Type " adb" now and you could see the detailed information about it. It means ADB command could be used now to control your Android device. Tips: This way only could make ADB run successfully on the same CMD window after you set the ADB path. Once you close this command prompt window, and open it again to run ADB, you would find ADB cannot be recognized again. ![]() Method 2: Permanently Fix ADB Recognition Error by Setting Environment Variablesīefore fixing ADB not recognized error, you should confirm that Android SDK has been saved on your computer and you know its location. Step 1: Right-click " Computer" and choose " Properties" on pop-up menu. Step 2: Click " Advanced system settings" on the left panel in new window. Step 3: In System Properties window, under " Advanced" tab, click " Environment Variables". Step 4: Environment Variables is open now. You can edit or delete existing variables in list, or create new environment variables. ![]() Under " User variables for isunshare", click " New" button to create a new variable for running ADB on computer. Step 5: Type Variable name and Variable value. Variable value: C:\Users\isunshare\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools.Step 6: You would see the new variable you just created in "User variables for isunshare". Step 7: Open Command Prompt and type "adb", you would see ADB detailed information. Now you have successfully fixed error "adb" not recognized as an internal or external program or batch file. You could use it to mount permissions to android device, or convert user app to system app after rooting Android device. Navigate to the installation file of the program you are trying to use and make sure the executable is present.Navigate to Control Panel, System and Security and Advanced system settings.Select the Environmental Variables button.Select Path in the System variables pane at the bottom of the new window.Select Edit and a new window will appear.Make sure ‘%SystemRoot%System32’ and ‘C:WindowsSystem32’ are present.Change the entry in the Environmental Variable window to something else and click OK. ![]() Replace the value you just changed with the original from Notepad and click OK. ![]() If you know Windows, you will know that sometimes all you need do is re-enter a value for it to be picked up again. I assume this is to link it within the Windows internal database once more but who knows. Pasting the values into Notepad saves time and preserves the correct syntax should you be disturbed while performing this task or in case you forget what it looked like. Just cut and paste each one individually and change the value in the Environmental variables to anything. Then paste the original value back and confirm. This should be enough for the original command you were trying to work again.
0 Comments
Leave a Reply. |