Hi guys, today i wanted to unlock the bootloader and flashing twrp in my Honor 8 but i got stuck pretty soon...
First of all my PC didn't recognize the device when i plugged it in the USB port but i discovered that i had to enable the "Google Mode" via the menu that shows up if you dial *#*#2846579#*#* in the dialer. It worked!
I enabled the debug, allowed my PC and finally i unlocked the bootloader. As you may know this formmatted the device. When i booted it up again i wanted to do the same thing but the "Google Mode" didn't work this time, and now i can't do nothing. I can enable USB debug in the settings but it does not show up the window "Allow for this computer". Also i can't browse my files from windows. It uses the connection just for charging and there is no notification where i can set the mode to MTP or anything else.
Do you have any suggestions? I already tried different computers and different USB ports.
PS. I also tried that useless software which is Hisuite but guess what, it says "Device is not connected"
Related
Hi,
I have a hobby to develop phone application.
I have no problem with connecting my HTC phone to my laptop for "USB Debugging connection" but my Verizon Samsung Galaxy s3 SCH-I535 could not get the "USB Debugging mode".
I DID CHECK the "USB Debugging mode in the system menu" however, my development environment could not get the debug mode.
Actually, when I plug in the USB with Galaxy s3, it shows the folder of the phone as usb data storage but not for debugging connection
Is there any way to get debug mode on my phone? Do I need to return this phone and wait for developer version of phone when Samsung launch in the developer site?
Thank you
I had the same issue where the galaxy only wanted to identity itself as a mtp or a camera device even though the usb debugging was enabled. adb devices command return nothing aswell. Found somewhere on stack overflow that installing the samsung kies suite would install the debug driver needed for adb to pick it up and it worked for me in my case, so hopefully that'll solve your issue as well.
I had that problem too, and I found it to be a driver issue. Grab the USB drivers from http://forum.xda-developers.com/showthread.php?t=1756885 (links direct to Samsung's site) and Win7 should detect everything.
I am having the same exact issues on my Sprint S3. I have installed all the drivers. Turned on USB debugging, and nothing! I am about fed up with this. I can transfer music over to the SD card without issue. When i try to put on anything other then media it tells me my device has stopped working or was unplugged. If i wasn't past my 14 days I'd return this thing and go back my Evo.
Title should say USB my fat fingers ! phone is completely stock no attempts to root. Enabled developer options fine. toggle the USB debugging switch. Get the Allow USB debugging? pop up. Click ok. Don't get any kind of debugging enabled notification. Restore default settings button is shown at the bottom of screen - i ignore this. Hit home or settings menu then go back to Developer options and the USB debugging switch is toggled off again. I tried restarting, developer options has stayed visible in settings but still can't get USB debugging to stick. PLEASE any suggestions what i'm missing?? Thanks
I also have the same problem with my mate 9. Allow usb debugging setting automatically toggles off as soon as I leave the settings menu.
Hi boys..
reasonable for this behaviour are the developer mode switches 1.) "Allow ADB debugging in charge only mode" and 2.) "Always prompt when connecting to USB"!!!
If switch 1.) is not set to "on", and switch 2.) is not set to "off", the switch "debugging allowed" would be cancelled every time you leave this menu!
So it does, what it have to do! Cancelling debug mode if phone would be connected to any other device without transferring data (if only charged). Easy, or not?
(see signature 1+2!)
hi man
i have a problem
my phone is huawei p40 pro
how to fix usb c port of the phone not function only charging , no fastboot ,no mtp ,no usb debugging ,no hdb
this is what i did
at the first usb c works fine
untill i did downgraded from version 11.0.0.190(c185R3) to version EMUI 11.0.0.153(c185R3)
i used hisuite proxy method and i got firmwares from https://www.firmfinder.ml/
after phone bootup 11.0.0.153 firmware , it seems usb c port disabled and just charging works
even i couldn't toggle usb debugging and change usb mode to MTP
after that i again downgraded to 10.1.0.114(c185R3) and nothing change . still usb c disabled
so i couldn't connect my phone to usb , and even i couldn't use usb otg
so i decided to use my phone itself's online update. i run updating first to 10.1.0.183 and nothing changed
again updated with itself's online update. update to 11.0.0.153 and still nothing changed
finaly the last firmware update. i updated with itself's online update to 11.0.0.195 . and see usb c work , even usb otg , and usb debugging and MTP , all works perfect
can you explain what happend on my phone and why usb don't work when i use hisuite proxy method ?
i did it again and again , all same results
It seems that the official update with the phone itself ( without pc ) is the only way to solve the problem
today some one tells me another way ,
can anyone test this way?
firlando said:
Hi there,
Huawei July Patch 2021 close all posibility to downgrade the FIRMWARE, it can be done with Hisuite Proxy but you have to choose the correct FIRMWARE and suitable to your Phone region. Once it done you can fix the "DISABLE USB" by doing OTA update to latest FIRMWARE to make it works.
When you choose the wrong cust/preload/mainFW your phone will be locked with that current FIRMWARE with "DISABLE USB" forever, you can solve this by searching the correct FIRMWARE and flash it using NMCARD the FIRMWARE should be a Higher than your Current FIRMWARE INSTALLED. after all done you can get OTA update and do OTA Update to latest FIRMWARE to make USB WORK.
Please be NOTED : Testpoin Not Working with latest July 2021 Firmware Patch so Huawei Block any downgrade posibility
I found 2 Brand USB Thumbdrive which is work with "DISABLE USB" you can do such Dload or restore Lzplay to instal GMS before update with OTA UPDATE. Here I attached the USB Thumb Drive.
Click to expand...
Click to collapse
Phone doesnt recognise usb.
Please i need help fast. Im going away tomorrow and i need my phone. I had gms successfully installed earlier today, but i accidentally deleted something and it stopped working, so i factory reset multiple times, even upgraded to emui 11 but...
forum.xda-developers.com
I recently rooted my s8+. Now when I connect it to my PC (or even my wife's PC), I get the following on my phone, "Attention: the connected device is unable to access data on this device. Please disconnect the USB cable and try again". I'm using the USB cable that came with my phone and the issue is happeing on 2 different PC's. I have USB debugging checked and set to MTP.
in settings, Switch on Developers options in configuratien. Then there is a USB modus setting. Set it to Charging rather then MTP Transfer.
try another USB cable and update the drivers in device manager.
jidamo said:
in settings, Switch on Developers options in configuratien. Then there is a USB modus setting. Set it to Charging rather then MTP Transfer.
try another USB cable and update the drivers in device manager.
Click to expand...
Click to collapse
Ok, I've tried your suggestions but the problem still persists. What's worse, I unrooted the phone and did a factory reset and it STILL is unable to access the data on the device.
Trying to unlock bootloader, upon opening command prompt via minimal adb fastboot, after entering "fastboot flashing unlock" instead of completeing the process, I'm getting a "waiting for any device" message instead.
I'm unsure if this newly discovered usb 3.1 port on my pc is even the right port for this usbc cable, as I've never used it before now.
Windows recognizes it as MTP usb , but I can't access anything, it's empty when I open it. So I don't know if it's the wrong port, and maybe I actually need to buy a USB to usbc cable from Google (tried the one that came with my V30, got same message) or if it's something else I'm missing.
breacherman said:
Trying to unlock bootloader, upon opening command prompt via minimal adb fastboot, after entering "fastboot flashing unlock" instead of completeing the process, I'm getting a "waiting for any device" message instead.
I'm unsure if this newly discovered usb 3.1 port on my pc is even the right port for this usbc cable, as I've never used it before now.
Windows recognizes it as MTP usb , but I can't access anything, it's empty when I open it. So I don't know if it's the wrong port, and maybe I actually need to buy a USB to usbc cable from Google (tried the one that came with my V30, got same message) or if it's something else I'm missi
Click to expand...
Click to collapse
just go to device manager in your windows pc where u see unknown device then you have to search for the driver of your phone and just manually select driver for your device i just faced same issue but after that it preety works but it can persists with other phone connection
[email protected] said:
just go to device manager in your windows pc where u see unknown device then you have to search for the driver of your phone and just manually select driver for your device i just faced same issue but after that it preety works but it can persists with other phone connection
Click to expand...
Click to collapse
hey thanks, that worked. Considering I've only had 3 rooted phones in the last maybe 8 years, I tend to forget those prerequisites
Hey guys,
I am Currently attempting to unlock the bootloader on my Pixel 6a, but when I attempt to connect via fastboot in the bootloader my PC shows nothing connected? I can push commands through ADB while the device is booted and have full functionality, but as soon as I reboot the device into the bootloader I lose connection to my PC. OEM Unlocking is enabled in the settings and I have toyed with updating it to the latest update and factory resetting the device. It shows correctly in device manager as 'Pixel 6a' while USB Debugging is disabled and as 'android composite ADB interface' while it is enabled.
To clarify as I am sure many have seen this issue before I do not believe it do be a driver issue as the device will not show up at all in device manager, not even showing with the incorrect driver (No ding to indicate a device has been connected). I have tried using 2 different USB C -> A cables in all slots of two entirely seperate PC's (Both running Windows 10). When I enter fastboot with OEM Unlocking disabled it acts no different to when it is enabled.
I appreciate any help or insight any of you folks can give me.
Device is currently running Android 13 Build number TQ2A.230505.002 if you need anymore info please let me know.
The OEM Unlocking toggle does not affect whether USB function works. It is only a "safety" that allows unlocking the bootloader.
Have you ensured you've installed the correct drivers? Google USB Drivers
I have spent a long time looking at drivers, but I have no device to install the drivers to as the connection drops out once I eneter the bootloader. I have used Zadig in the past to install the correct drivers for devices but when I reconnect the device while I have it open it cannot even detect a new device being connected to the PC. (Also no audible tone which would be heard even with incorrect drivers) I actually only recently used Zadig to install the correct WinUSB drivers for my S10e in which I connected it to my PC in download mode (Queue audible ding) and used Zadig to overwrite the incorrect driver with the correct one. It's almost as if the device will not communicate while it is in Bootloader mode?
I assume you have checked with the 'fastboot devices' command to see if your device is connected when in fastboot mode?