Related
I've compiled a fastboot binary for windows from the git source, using cygwin.
I had actually compiled it a couple of weeks ago, but I never could get it to work. I was looking into it again tonight and discovered that windows had installed the USB Mass Storage driver for the phone in SPL mode, instead of the android driver. So after updating it to the android driver, it worked! woot
Instructions:
(note: you have to check the USB device in Computer Manager when the phone is in fastboot mode. The computer sees the phone in fastboot mode as a different device than the phone in normal mode)
Download the file and extract it in the same folder as adb. (if you don't have adb yet, it's included in the android SDK for windows. go download it!)
Take out the usb cable and boot up your phone into the SPL (back + power). You have to have the dev bootloader for this to work (white background with 3 skateboarding androids).
Plug in the usb cable, and make sure the display on the phone changes from "Serial0" to "FASTBOOT". If it doesn't, try pressing the back button.
If it asks you to install drivers, then go ahead and use the same usb drivers that you used to get adb working. You can skip the rest of the instructions. Fastboot should be working for you now.
If it doesn't ask you to install a driver, you need to figure out if the correct driver is loaded already.
Right click on My Computer, and click Manage, then go to the device manager
If you see an "ADB Interface" category at/near the top, with "HTC Dream" under it, then you're good to go. Fastboot should be working for you.
If you don't see an "ADB Interface" category, then it's likely that windows loaded the USB Mass Storage driver for it automatically. In the device manager, go down to "Universal Serial Bus Controllers", and see if you have at least one "USB Mass Storage device". If you have multiple ones, you'll need to go through each to find the correct one.
To find the correct one, right click on the USB Mass Storage device and click Properties. Go to the Details tab. In the combo box at the top that says "Device Instance Id", bring up the pull down and choose "Compatible Ids". If that is the correct device, then you will see 3 entries:
USB\Class_ff&SubClass_42&Prot_03
USB\Class_ff&SubClass_42
USB\Class_ff
Once you find the correct device, go to the driver tab, and click "Update Driver". Choose "No, not this time", then "Install from a list or specific location", then "Don't search, I will choose the driver to install", and then choose the same usb driver that you used to get adb to work.
After that's done, you should be good to go. Open a command prompt and type fastboot devices and it should list the phone.
This is a great Christmas Present lol !!!!! Thanks again JesusFreke !!!!!
JesusFreke said:
I've compiled a fastboot binary for windows from the git source, using cygwin.
Click to expand...
Click to collapse
Just four minutes shy of delivering on Christmas day too I kid, I kid. Great work. This will be quite nice for those of us still working primarily in Windows. b
Really Good!!!!!!!
Thanks JF, not for the files, I already had them compiled but because I found out why they weren't working...
USB MassStorage driver was as well on! LOL Its the simple things sometimes.
That's fantastic thanks JF. Now since we got fastboot in windows how does that change the process for having our custom boot image. I could not for the life of me get fastboot to recognize my device in ubuntu no matter what I did.
pablizzo said:
That's fantastic thanks JF. Now since we got fastboot in windows how does that change the process for having our custom boot image. I could not for the life of me get fastboot to recognize my device in ubuntu no matter what I did.
Click to expand...
Click to collapse
Let me take a shot in the dark and say that it would allow you to do the "fastboot flash splash1 image.rgb565" part from windows instead of ubuntu?
Don't forget about koush's .NET application to convert an image to the correct format: http://forum.xda-developers.com/showthread.php?t=462489
Thank you JesusFreke!
Way faster than booting Ubuntu under Sun's VirtualBox
Pardon my ignorance, but all that I can see with search about fastboot is it allows us to flash cupcake and new splash screens.
Can someone enlighten me as to what exactly this is? Does it simply bypass key signatures or error checks? Being that I don't turn my phone on and off a lot, a custom splash is really not necessary and being that cupcake is severely limited, don't want to even toy with that until it has more work in it.
Thanks in advance!!!
anyone try this on vista 64 yet?
Damn, someone needs to hire you or something. You've got talent!
Ha, thanks. But it's not like I wrote it or anything. The windows code is all there. I just figured out how to get it to compile in cygwin. (and figured out the driver thing, of course)
Valicore said:
Damn, someone needs to hire you or something. You've got talent!
Click to expand...
Click to collapse
JesusFreke and Stericson need to partner up and start a company for Android apps.
I think your givin me too much credit....JF could handle the app shop all by himself, he's just that good
Stericson
THANKs alot i didnt feel i installing ubuntu on my laptop. once again thankss
hi，can i use this tool flash the cupcake to my G1？the driver is good，fastboot is good work，but when i use the command that FLASHALL，its told the products specified and android-products-out must be setted。i dont know whats that means~
"Waiting for device" with Fastboot
Edit: Got it working, thanks.
I've had issues with fastboot depending on which USB cable I used (I have different kinds with different shielding)... I assume my "cheap" cables didn't have enough shielding and corruption happened when trying to communicate... also noticed that this happened as well while using a USB hub... I now have a good cable connected to the BACK port of my PC... I used the back port because front ports have extensions running from the motherboard through the inside of the case that were making interference as well... hope this helps!
what the heck is fastboot?
Sorry, JF. What exactly is this?
texasaggie1 said:
Sorry, JF. What exactly is this?
Click to expand...
Click to collapse
http://www.gotontheinter.net/content/fastboot-cheat-sheet
[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire
The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk
Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S
USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.
It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S
I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance
Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help
jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
windows 8 have a issue with ville fastboot... please make you sure you have a fix
zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic
..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...
Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!
Thank you very much bro. HTC One V good working.
Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Crowd-sourced solutions.
Windows 8 Diagnosis
Yorus said:
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
Setting up ADB and Fastboot commands to work from ANY path (credit to original author in quote).
Chromium_ said:
Setup, Preparation and Prerequisites
ADB and Fastboot Installation
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 here (Thanks @El Daddy)
Extract the zip and place the android-sdk-windows folder on the root of your hard drive. (the path should be like this: C:\android-sdk-windows)
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the 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
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 not, repeat the step above.
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
(OR WHATEVER PLATFORM-TOOLS DIRECTORY YOU PICKED)
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). 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.
Click to expand...
Click to collapse
The importance of being careful with your command choices.
MkVsTheWorld said:
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Click to expand...
Click to collapse
Fixing MTP device not showing up after installing ADB drivers.
dbareis said:
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Click to expand...
Click to collapse
Whyzor said:
You should also mention what worked for me in post #16 (& confirmed by a few others in other threads). That is to toggle Settings - Storage - USB Connection type from Camera to Mass storage & also the debugging mode on & off.
Click to expand...
Click to collapse
Ashcunak said:
Op might wanna tack this onto the bottom of the main post as a last resort for folks to "start over" and be sure they have no old drivers installed.
http://www.nirsoft.net/utils/usb_devices_view.html
i had to use this program (right click run as admin if permissions are set) to remove EVERY single android related driver in order to get mine working.. turns out i had so many old ones in my system and some i couldn't remove from the device manager, the buttons wouldn't become click able..
Click to expand...
Click to collapse
CrazyIvan said:
I've tried everything and cannot get the authorization prompt to pop up on my Nexus5 so when I run adb devices the phone shows up as "unauthorized". Any suggestions? This is with updated sdk and USB drivers. Device manager shows phone as "Android Phone->Android Composite ADB Interface" and "Portable Device->Nexus 5". Tried toggling between MTP/PTP, USB Debugging on/off, stopping and starting the adb server (latest version 1.0.31).
Thanks in advance!
EDIT: Finally got the ba$tard! Run this for some adb debug logging:
adb kill-server
set ADB_TRACE=all
adb nodaemon server
Go and look back at the output from the start for any errors. In my case it couldn't mkdir in c:\users\administrator, which for me doesn't exist. I changed the Windows environment variable "ANDROID_SDK_HOME" to point to "C:\users\<my account dir>", closed the DOS window, re-ran the commands and I got prompted for the permission on my phone. Yee ha! Now I can fire up hello world with the SDK on my phone. Praise be to Google search for turning up this thread that told me about the debug logging.
Click to expand...
Click to collapse
SonicAngel said:
I just rooted my N5 (using the guide on this forum so I had no other drivers other than Google's SDK) and after unlocking my bootloader windows did not recognize my phone so I couldn't go further. Upon checking device manager I saw something called "AOSP on Hammerhead", a quick online search found a lot of very complicated answers (uninstall all drivers, restart, install adb drivers was one example).
Instead of all that I just right clicked "AOSP on Hammerhead", chose Update Driver, manually choose driver, went to "Android bootloader", chose the default driver from "Google inc" manually and that for some reason worked.
I figured this might help someone since the other solutions I found really were very long.
Click to expand...
Click to collapse
Questions? Ask below!
MaxRabbit said:
Reserved.
Questions? Ask below!
Click to expand...
Click to collapse
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
KTT16 said:
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
Click to expand...
Click to collapse
You're welcome! What shows up in your Device Manager now?
MaxRabbit said:
You're welcome! What shows up in your Device Manager now?
Click to expand...
Click to collapse
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
KTT16 said:
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
Click to expand...
Click to collapse
What step exactly did you take that fixed it?
MaxRabbit said:
What step exactly did you take that fixed it?
Click to expand...
Click to collapse
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). 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.
KTT16 said:
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). 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.
Click to expand...
Click to collapse
Ahh, your problem with my instructions then were that you weren't running ADB from inside the platform-tools folder
Definitely! I seriously got frustrated for a second and forgot how to read!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Not showing up as removable storage
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
MaxRabbit said:
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
Click to expand...
Click to collapse
It shows up as a 'Portable Device' -> 'Portable Media Player' (I was thinking it was a 'Device with Removable Storage').
I have full access to the internal file folders here at work.
Here's a suggestion for something to add to the OP.
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Sent from my Nexus 5 using Tapatalk
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
I have the same problem and done the same exact things u did. any help?
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
aluxzen said:
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
Click to expand...
Click to collapse
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Whyzor said:
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
That... Thankyou for that info.
I was able to get ADB to work but was not able to get the device to popup as a storage device. That fixed it. Thanks!
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/show...&postcount=937".
Click to expand...
Click to collapse
Thanks, that link was really helpful! I struggled with the correct detection before (seems I had some old drivers for my last phone on that windows installation...)
Whyzor said:
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
Thank you for sharing your solution.
enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks
hahaha1659 said:
enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks
Click to expand...
Click to collapse
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk
Droidriven said:
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.
hahaha1659 said:
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.
Click to expand...
Click to collapse
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.
hahaha1659 said:
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.
Click to expand...
Click to collapse
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.
hahaha1659 said:
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.
Click to expand...
Click to collapse
It was created by a member of this forum, you should be able to find a safe version here somewhere.
Sent from my LGL84VL using Tapatalk
Update: after a break for a couple of days, this appears to work again. But probably not for long -- so better try it if and while it's still up ;-)
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test my luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).
turistu said:
I was able to do just that (and unlock the bootloader on my phone) some two months ago (in February 2023).
I did by using this perl script of mine to simulate the https requests performed by the deep testing app.
My phone was a Realme 9 5G (RMX3474), the EU/GDPR variant.
A dry run with bogus serial num and imei strongly suggests that they haven't "fixed" it yet and it may still work.
I also suspect that it may work with other Realme phones not supported by the deep testing app.
But I don't have any spare phone (and I will not test by luck by locking it back ;-)), so I'll be grateful if anyone with a locked Realme phone would give it a try (the deep testing app would still ask you for confirmation, you don't have to unlock your phone if you don't want to).
Click to expand...
Click to collapse
Thank You!
It realy works!
Thanks,
Worked for me with Android 13/RealMe UI 4.0.
Now to magisk...
After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)
Is there a way to use this script on realme 9 pro 5g eu rmx3472?
Edit: It works perfectly and i was also able to change my region to ru.
mister_slowhand said:
After unlocking the phone, I'm looking for the boot.img.
I can find firmware update package for UI3.0, but none seems available for 4.0.
Could someone point me to it ? (either boot.img or ofp package)
Click to expand...
Click to collapse
Try https://rms01.realme.net/sw/RMX3472GDPR_NN.X.NN_YYYYMMDDHHMM0000.zip,
(replacing the N, Y, etc with the actual version of the firmware).
Also the variants with .7z instead of .zip.
hatbo said:
Thank You!
It realy works!
Click to expand...
Click to collapse
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob
RobertoSt25 said:
Hey lads,
Could you post me here some steps how to install and unlock bootloader using that script PERL ?
I'd really appreciate it. Cheers.
Thanks. Rob
Click to expand...
Click to collapse
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.
I love you Turistu, thank you for the guide!
I've had the problem, that the device wasn't getting recognized in fastboot mode.
That is because the OnePlus Fastboot USB Drivers are NOT SIGNED!
You have to restart Windows with advanced startup settings, and deactivate driver signing. So that Windows trusts unsigned drivers.
Then you can restart Windows in that mode, settings -> windows update -> advanced options -> reset options -> advanced restart. Go to advanced boot -> deactivate usb driver signing (option 7), start the pc with that option.
AND THEN you can boot your device into fastboot mode, go into your drivers and if it's still coming up as unrecognized, right click it and update it's drivers manually with the oneplus drivers.
Then it should work for you, too. Gave me lots of Headaches.
I have attached the Oneplus drivers i've used for fastboot and a patched boot.img with magisk 26.1 from RMX3311_11.C.10_EU_202303171905.
You did a great job! Thank you!
PS. Dacă ești român, ești foarte tare frate!
turistu said:
As already mentioned at the end of that github page, you can use the "Strawberry Perl" distro to run that perl script on Windows.
1) First install strawberry perl
2) download the deeptesting-junk.pl script
3) start the "perl command prompt" (it should be the first result when you type "perl" in window's search box)
4) inside the command prompt change to the directory where you had downloaded the script
5) run the commands and follow the instructions from the github page. Take care to replace the dummy HHH and DDD with your actual serial number and IMEI ;-).
If you have problems with those instructions (e.g. the deeptesting app still does not work, despite the script getting a successful result to the "ckeckApproveResult" command), please mention exactly what happened.
Click to expand...
Click to collapse
Hello there,
I tried your method, I did everything step by step and it actually worked and it did unlock the bootloader.
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Now I really do not know what to do -.-
Any advice would help.
Thanks Rob
RobertoSt25 said:
However after yelow sign saying the "device is unlocked" went black screen, rebooted and again fastboot mode.
Click to expand...
Click to collapse
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?
turistu said:
If the top of the screen has "START" in green letters, then just press the power button.
BTW, what phone model do you have?
Click to expand...
Click to collapse
yes top of the screeen is START green, but when I pressed power just keeps rebooting into fastboot.
RMX 3474 REALME 9 5G
Thanks