good morning sorry my English a few days ago I received a phone blu r1 hd which the owner factory reset the same turn on the logo comes to the welcome screen after moving to next remains on the screen "a moment" and from there my pc only recognizes as R1 as a disk or multimedia drive does not install the mtk 6735 preloader drivers and in the flastool it gives me the following error: BROM ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) BROM ERROR.
I also managed to enter the Factory mode menu when I connect the USB cable to install 5 drivers:
1-usb composite device
2-USB storage device
3-Android composite ADB interface
4-Mediatek usb vcom (android) (com17)
5- R1 hd file-cd gadget usb device
then in this mode I enter the cmd console and type adb and recognize it as an unauthorized device.
Did you enable usb debugging in the developer options? That's usually why it says unauthorized.
Is your bootloader unlocked ?
Related
Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel
SOLVED...sort of...
I used a workaround. I used a Windows 7 computer and there it worked perfect.
roel1976 said:
Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel
Click to expand...
Click to collapse
hi, i had same USB problem, windows7 worked for this old phone
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
davidw.roggenkamp said:
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
Click to expand...
Click to collapse
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
waiflih said:
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
Click to expand...
Click to collapse
I installed and used ADB into Linux Mint 20; but it ended with the same result.
davidw.roggenkamp said:
I installed and used ADB into Linux Mint 20; but it ended with the same result.
Click to expand...
Click to collapse
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
reg66 said:
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
Click to expand...
Click to collapse
Tried this with the same result.
https://adbdriver.com/downloads/
Plug your phone on side port and reboot to fastboot then use this app to fix fastboot mode
If you already plugged the USB cable to the side port and still not able to use fastboot, it is probably a Windows problem. The Android fastboot exe is not properly signed so you need to disable Windows' driver signature check before installing the ADB/Fastboot drivers.
I cannot post link but search for "android fastboot driver disable driver signature enforcement". Disable the signature check then install the fastboot drivers.
Here is the quick run-down of the steps.
1. In command console and in Admin mode, run this command and then restart => bcdedit /set testsigning on
2. Install adb and fastboot stuff
3. After successful install, in command console and in Admin mode, run this command and then restart => bcdedit /set testsigning off
For ADB/Fastboot driver, i use the one by "fawazahmed0" here in XDA. The title of the thread is [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows.
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
davidw.roggenkamp said:
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
Click to expand...
Click to collapse
Are you sure your using the side port ?
Created a new topic, disregard
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
TheeWolf said:
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
Hii. you go to device manager. find your phone in unknown device. Update the driver using i have a disk option. Then try again. it will work.
Disable windows 10 Driver signature and install Fastboot USB drivers again.
Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.
Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.
Sathelp said:
Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.
Click to expand...
Click to collapse
I'm able to detect device in "ADB Devices" when phone is booted into android OS, even the MiFlashTool also detects the device when phone in booted into OS.
But after i type ADB reboot bootloader, phone restarts into FASTBOOT, i can see RED "FASTBOOT" logo in phone screen but it doesn't get detected.
How come phone gets detected in ADB when Phone is booted into OS MIUI13 but not in FASTBOOT.
I'm on windows 11 .
I changed the cable also with a new Xiaomi cable purchased recently, still the same result.
You can never see a result to detect mi 11 ultra through ADB devices. Rest assured your device is already detected and ready to use. Even though can not see device address.
I had the same case. Make sure all the necessary drivers are installed.
At first mine was also not detected in fastboot. When I first ran MI Flash Tool, it automatically installed some drivers. And I also manually installed USB driver of MI 11 Ultra.
After that MI Flash detected my phone in fastboot.
A small suggestion from me: Use "Xiaomi ADB Fastboot Tools" for flashing. MI Flash was giving me, timeout error and my device got into fastboot loop. After flashing with "Xiaomi ADB Fastboot Tools" all went well.
hello, I also had this problem and to solve it I used the driver of Mi unlock which is at the level of the parameters and launch it in fastboot then connect it to the pc and the drivers must be installed
I had a similar problem with my Mi 10. Found via ADB but wouldn't show in fastboot. Tge way I solved it was to boot into TWRP recovery (assuming you have it) and then go to their reboot menu and choose fastboot from there. It will then put you into their version of fastboot and your computer should recognise the phone in fastboot mode.
I hope this helps
jaggub4u said:
Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.
Click to expand...
Click to collapse
Adb and Fastboot is not the same thing!
If you're phone is detected in ADB, it means you have install the Adb Driver ( which more than probably is Google Driver or Xiaomi driver for ADB ).
In order for you phone to be in Fastboot do the following:
- Reboot to Fastboot and connect your phone to PC with original Xiaomi cable from the box
- Go to Device Manager > Other Devices > Android Device ( you will see a yellow sign, which means you don't have the Fastboot Driver )
- Download XiaomiMi11 Ultra Bootloader Driver.zip, unzip it
- Click on the Android Device with yellow sign > Update driver > Browse my computer for drivers > Select the Xiaomi Bootloader Folder
It will install the driver.
From here you're good to go!
hi folks I am trying to unlock the bootloader on a Motorola E4 plus running 7.1.1 but I'm having a lot of trouble. Firstly when I boot the device into bootloader mode by pressing and holding the power and volume down buttons and plug it into my windows 10 pc it says 'transfer mode: cable not connected'. I have tried different cables and usb ports but the issue persists. Moreover, when I try to get the unlock data using the 'fastboot oem get_unlock_data' command it says '(remote: 'unknown command')'. Oddly however adb works and the phone is shown when I type 'fastboot devices'.
So far I've tried:
using my mac
factory resetting the phone
wiping the system cache
ensuring security is set to none on the phone
different usb cables
different usb ports
installing the android SDK and running the cmd window from it
minimal adb and fast boot
platform tools based adb
restarting the computer
installing motorola's own drivers
ensuring oem unlocking and usb debigging are turned on in developer options
ensuring the MTP driver is installed and updating the driver in device manager
restarting the phone
I would be grateful for any help anybody could please offer. Thanks all!