HI!!! I installed navigation is probably not a good.switch machine and the screen just glows.activates the table text:the device in unable to boot becouse either you have turned off the device incorrectly or tried to install an application from untrusted source.press send to reset yor device or press any other button to cancel.this operation will delete all yor personal data and restore the device to its factory default settings. HELP!!! what to do for me?
basically its asking for a hard reset. by pressing the send button your device will reboot with the factory settings meaning you will loose all data and your phone will be just like the same when you bought it. hope this helps
XDA-ORBIT2 fix problem???
I have tried your solution but I got the following message on my PC. I have a XDA-Orbit2
Cmd>boot
Command error !!!
Cmd>
Please can you help me with this problem?not working (none of the methods):confuse 1. Download mtty.exe
2. Disable activesync (connection settings -> uncheck "allow usb connections")
3. Connect your Polaris to PC using USB cable.
4. Open mtty, select USB port and click OK.
5. Hit ENTER twice, you should see the "Cmd>" prompt.
6. Type the command "boot", you should see something like this
disconnect your device from pc. make sure u have atleast 50% on your batter and follow this hard reset procedure
http://www.hardreset.eu/o2_xda_orbit2_hard_reset_soft_reset_en.html
I've read many threads on fixing this issue, but none of the fixes I've tried are working for me and I'm kinda at my wit's end. I'll try to lay this out as concisely as possible :
Desired outcome - I need to recover my 'Documents' folder from the SD Card. After I've done this, I can reset the device to the factory image on my own.
Device - 2012 Nexus 7 Wifi, currently running 4.4.2 after the push update (Build KOT49H), and I've installed WUGfresh's Nexus Root Toolkit 1.8 on my Win7 machine. - On the nexus, I had enabled developer mode and USB debugging. No clue, unfortunately, what the most recent MTP settings were. I assume they were set to "mount as disk drive" (if I'm thinking of the correct setting here).
This morning my Nexus began looping the four-circle loading screen (formerly the X) when I powered it on. I can boot into recovery mode and restart the bootloader/etc, but couldn't break the loading loop.
Here's something I seem to be stuck on - when using the toolkit, what screen should I be working from for which tool? For instance, should I leave the tablet at the loading screen, at the recovery mode ("no command") screen, the "input adb command" screen, etc - and for which utility? It seems the ones I should be making use of are either :
Backup Utilities -> Create Android Backup File
Backup Utilities -> Backup VirtualSD Card
Advanced Utilities -> Push/Pull Files*
*On this option, should my path be /system/sdcard/Documents ?
Here's what I think I'm failing to understand - I notice that, under advanced utilities -> list devices, if I check the radio box for "ADB Device on" at the basic bootloader screen (on the device), I get nothing, but checking the "Fastboot - Bootloader" box returns the proper serial #. The only time I get a valid entry from "ADB Device on" -> List devices is when I'm at the command prompt line of the recovery mode screen (on the device).
Thanks for the help - II have tried browsing for similar issues, but after a night of struggling with it something's still not clicking in my brain. Pardon my exasperation and good on you all for being here.
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!
Thanks to:MaxRabbit
Other solutions
Windows 8 Diagnosis
Originally Posted by Yorus
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
Hello,
here is my guide to "how to fix the File Transfer Problem" which some people have got.
FIRST:
It's just a problem with windows and not with your smartphone or custom rom.
This guide is for Windows 10, because i haven't installed another windows system anymore.. But with a few differences you should are able to follow this guide with windows 7, 8 or 8.1, too.
GUIDE:
Open a explorer windows and type "Control Panel" in it. You should be redirected to the old Windows 7 style control panel.
Click at "Hardware and Sound" and then at "Device Manager".
If your smartphone is plugged in your PC and you have chosen the File Transfer settings at the smartphones menu, in the device manager should be a unknown device with the name "MTP". (If this device doesn't be there, you should look for your phone at the other register entries and right click on it. Then choose uninstall and check the checkbox "delete drivers" (or similar..). In the device manager window click on the first entry with your PC name. After that click on "Action" in the menu and "Search for changed hardware". Then normally follow this guide.)
Right click on it and choose "update driver".
In the following window choose the second option, and then again the option at the bottom.
In this list search for the "Portable Devices" entry. Double-Click on it.
Now you should select standard MTP-device on the left side of the window (Important:Don't choose standard MTP-supported device or standard MTP-compatible device!)
On the right side you choose MTP-Device. Click on next and confirm the message of "incompatible driver warning".
Then the driver should be installed and your device should be recognised normally by the windows OS.
That's it!
Greetings,
AenimaEx
It worked, I just had to go to Portable Devices instead of Wearable Devices. For some reason the internal storage is showing up as 4 GB.
Okay, i've corrected it. Hmm.. How much storage capacity should it be? You could try to backup all files and folders from your sdcard to your PC and then format the sd card in your smartphone. Normally it should partition and format the sdcard with it's full size.
Thanks for the Guide. Works also for the old Samsung SGS4 i9505 on LineageOS 16 with Win 10.
I have done this on Windows 10/11 with the 8 Pro, 8T, and 9 Pro personally.Other members have had success with the OP5T, OP6T, OP7P, OP7T, OP8 and even a OP1 for @mawil1013 and somehow a Xiaomi Mi 9T lol
Spoiler: Backstory
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
To fix the issue, we are going to disable driver signing enforcement in Windows and then install the Unsigned OnePlus drivers.
Install the OnePlus drivers that are included with your phone.
They should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer.
I'm sure you can find the installation package somewhere online, but I don't have a good download source so I am not going to give out random links.
This will create a directory containing the USB driver. This will most likely be
C:\Program Files (x86)\OnePlus USB Drivers
In that folder there is a driver, but both when installed using the installer incuded with my phone, and a downloaded version, I ran into...
The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
To get around this we are going to disabled signed drivers on windows.
Select the “Start” button.
Type “startup”.
Select “Change advanced startup settings“.
Select “Restart now” under the “Advanced startup” area.
Once presented with the Advanced options select...
“Troubleshoot“ --> “Advanced Options“ --> “Startup Options“ --> “Restart“
After that, a menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver until you reboot, meaning we can install our unsigned OnePlus driver.
Pop open Device Manager
You can press windows + x to bring up a menu, then you can press m or select device manager for quick access
Boot your device into fastboot mode.
This should cause it to show up in device manager as "Andriod", with a yellow triangle
In device manager right click the "android" device
Then press the following options
Update driver --> Browse my computer --> Let me pick --> Have Disk
Navigate to the folder from earlier: C:\Program Files (x86)\OnePlus USB Drivers
Select OnePlus_android_winusb.inf and click okay
After that, OnePlus Android Bootloader interface should be selected. Go ahead and install it.
Congrats! Your device should start showing up in fast boot mode.
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
Make sure when you allow adb debugging in developer mode that you authorize the phone when using adb devices, otherwise you will not see fastboot when you try to use.
Thank you, that would have driven me crazy. It is crazy that it is 2020 and driver manufactures still don't sign their drivers some times.
There is no CD Drive show up....
find on internet a oneplus usb driver and installed....
then got this message trying to get the [oem get_unlock_code]
Code:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Thanks OP.
finally works...
Okay, I just figured out my mistake, but I'll leave it in case someone else stumbles across the same thing. The fix: choose your language, then choose "reboot to fastboot" and confirm that you're sure. You'll get to a screen with "Fastboot mode" in red near the top. Once there, run the get code command.
Click to expand...
Click to collapse
REFERENCE: reference link
Thanks a lot @Mbektic. This seems so much harder than it needs to be and I wouldn't have been able to unlock my bootloader without your guide. Thanks again!
Wow I didn't even realize that I had helped people until now! I am so glad I could help you guys @bigd4ve @jefffeely and @Pain-N-Panic
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
Yes, I also had to disable device driver signing, then the phone showed up in the bootloader.. You can just open an admin command prompt, type "bcdedit /set testsigning on", REBOOT, then install the proper driver. This seems to be a problem with OOS11.
The easiest method for any newbie is to install , iobit driver booster , free.
Driver Booster 10 Free: Official Free Driver Updater Tool for Windows 2023
The best free driver updater for Windows 11/10. Fully detect and update all your old drivers for graphics, USB, audio, display, network, printer, mouse, keyboard and scanner. Free check driver updates now.
www.iobit.com
Then update the android driver. The fastboot would be working fine after that.
dogmatism said:
The easiest method for any newbie is to install , iobit driver booster , free.
Driver Booster 10 Free: Official Free Driver Updater Tool for Windows 2023
The best free driver updater for Windows 11/10. Fully detect and update all your old drivers for graphics, USB, audio, display, network, printer, mouse, keyboard and scanner. Free check driver updates now.
www.iobit.com
Then update the android driver. The fastboot would be working fine after that.
Click to expand...
Click to collapse
I just cant thank as much as I have to! I couldnt find solution for months, I was using magisk module on old phone to use fastboot and it sucked. Now updated driver and works like charm. Thank you so much!
Thanks for making this thread. I couldn't believe I were having so many issues on my desktop, when I had managed to get everything right when I first got the phone(8PRO) on my laptop. I had adb & fastboot installed, then plugging in Kona w/ usb debug off allowed me to install the adb driver and then for fastboot(while in fastboot, using window's "device manager" I selected the Google usb driver I had downloaded, and finally for edl mode driver just in case (msm), I installed the qualcomm driver while in edl mode( whew). Anyway thanks,
I cannot believe I did not see this thread earlier...
Just finished solving the same problem after going nuts for a couple of hours.
It is most definitely just getting the PC to install the OnePlus drivers AND disabling the driver signing.
What a pain.
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
you've saved my sanity on oneplus5T after upgrading to Android Q 10. Thank you
I also struggled with this issue but found another solution. Once my phone was plugged in (can't remember if it was system or fastboot) I went to Windows Update and browsed the optional updates. One of the optional updates was a driver for android recovery. Installed it and it worked.
bynarie said:
Yes, I also had to disable device driver signing, then the phone showed up in the bootloader.. You can just open an admin command prompt, type "bcdedit /set testsigning on", REBOOT, then install the proper driver. This seems to be a problem with OOS11.
Click to expand...
Click to collapse
Between the OP and this post, I was finally able to get the drivers to work on my 8T (Sim Free- Carrier Unlocked) new phone from Oneplus. I spent several hours trying to determine what the issues were and then found this thread. I am successfully unlocked from the bootloader. Thank you both.
behel1t said:
I also struggled with this issue but found another solution. Once my phone was plugged in (can't remember if it was system or fastboot) I went to Windows Update and browsed the optional updates. One of the optional updates was a driver for android recovery. Installed it and it worked.
Click to expand...
Click to collapse
THANK YOU! This worked 100% for me, super easy too. Went to Windows Update, View Optional Updates, saw the Android External Device update, device showed in fastboot after installing.
THANK YOU SO MUCH!!!!! You're a legend, it works on my OnePlus 5T as well.
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
ohhh my man, you really saved my time. thanks a lot. appreciates ur help.
I recovered my account just so I could post a reply on this thread. THANK YOU MBEKTIC, you saved my skin!
I was puzzled for 3/4 hours wondering what to do. Thank you
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
Thanks for this - I know its a little after the fact but 6+ months later this post has gotten me out of a fastboot hole with a oneplus 9. Now fully rooted only for this. Thanks again.