Hi, i want to unlock the bootloader of my old Redmi note 5, but there's a problem, when I go into fastboot mode, the Xiaomi's software can't find it, even using ADB the device is impossible to find. If I turn it on normally i can find it. Why it happens?
Hey u may give this a try as based on my understanding Xiomi devices will require u to install mi flashtool on PC as it has driver installation option. Remember some times you are required to disable driver signature verification.
I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.
plusminus_ said:
I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.
Click to expand...
Click to collapse
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
Weird.
Maybe try a different cable?
Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
U might be using an Amd based system. Usb 2.0 hub is ur solution
Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.
drnightshadow said:
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.
Click to expand...
Click to collapse
Can you tell me about this usb 3 reg patch?
Actually i am outstation and don't have my usb hub and i want to do faatboot commands
Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me
Banty448 said:
Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me
Click to expand...
Click to collapse
Read the thread and don't be troll. You didn't even read post before you post it your own. Ignorance is a bliss.
Good luck and stay safe.
Related
Hello, I finally got drivers to work while my EVO was in Diag mode, but it will not show me a com port, here is a screenshot.
I have searched all other categories and can't find anything.
It only shows up as My HTC in device manager, no more HTC DIAG
Please assist in this matter as I would love to connect with CDMA Workshop.
http(COLON)//img833[/url](DOT)imageshack(DOT)us/i/28373875(DOT)jpg/
First of all Welcome!! I fixed your image for you. Look under ports in device
manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have looked under everything and under ports is only Com1 which isnt it and printer port.
huh? I literally just installed the htc diag drivers and put the phone it diag mode (##3424#) and everything went perfectly and showed right up in device manager under ports (com 3). Took 2 mins... Not trying to brag.
try unplugging phone>rebooting computer>put phone in diag mode and connect usb
I understand that, I did that too and it worked. Then I rebooted and now it shows up as My HTC.... and no com port to choose from ((((
huh.. try right clicking and uninstalling my htc then reconnecting your phone in diag mode and running the drivers that way.
I did uninstall it, also chose delete drivers. Then I can see it show up as HTC DIAG without a driver. I choose the Driver for installation... It installs and just shows up as My HTC.
I attached the htc diag drivers I just used a little while ago. When it prompts you for the driver direct it to the win x86 folder that you unzip.
I am using Windows 7 64 Bit
enko420 said:
I am using Windows 7 64 Bit
Click to expand...
Click to collapse
ahh ok attached 64 bit then
This is the problem I was having before untill I searched and found someone that provided a VISTA 64bit version of the driver which is the only one that worked out of like 10.
The driver you provided will not install the HTC DIAG.
And if I use the Vista driver then it installs but automatically says My HTC.
--- Don't worry this is just my luck, nothing ever goes easy when I try to do stuff
Sorry man check THIS thread out & maybe THIS one too. Hope they can help you better than I was able to.
I did the manual force install, now it's showing as HTC Usb Modem #2 under Modems, it's #2 even though there isnt another listed?
but when I click properties it wont show com
enko420 said:
I did the manual force install, now it's showing as HTC Usb Modem #2 under Modems, it's #2 even though there isnt another listed?
but when I click properties it wont show com
Click to expand...
Click to collapse
looking at this picture below, what you describe sounds right. Goto step 3 on the first link i posted above.
ok cool man, thanks for the help, got CDMA workshop to connect
A quick question to you though, should I pay the $15 to have metro PCS flash my phone to where I get just talk and text or should I flash it myself? is the original flash hard? I have read some write ups on it but not to sure
hey wht llat rom are u using because im dialin the code but nothing happens or i have to do it after i installed the driver
Sent from my PC36100 using XDA Premium App
make sure you hit ##3423#
enko420 said:
make sure you hit ##3423#
Click to expand...
Click to collapse
ah **** i forgot that doesnt work on aosp roms right it has to be done on a sense rom? lol
I meant ##3424#
but as for the roms I have no Idea, I know nothing about ROMs
qubanaso said:
ah **** i forgot that doesnt work on aosp roms right it has to be done on a sense rom? lol
Click to expand...
Click to collapse
Yes aosp roms don't work it has to be sense.
And OP I'm glad you finally got out working! I was feeling like a failure for a minute there
I am having issue connecting to PC (on XP here but also issues on Vista 64 at home). No matter what I try I can't access storage to copy to/from my PC to my phone. I understand that JB now uses MTP rather than USB Storage, but having spent about three hours now trying to find a solution I have to admit I am completely stumped
Having tried many options without success, and having installed and uninstalled HTC Sync at least six times I have started again from scratch reinstalling everything I could think of which might have a bearing. I have just reinstalled the full SDK, installed Windows Media Player 11 (for MTP), reinstalled .NET 4, installed latest version of HTC Sync, but still when I connect I get an error in device manager with Other Devices>Android Phone (also get the Hardware Wizard popup which always ends up saying not installed/could not locate software even if pointed directly at the Google USB driver folder in the SDK so it's obviously not this), and in HTC Sync it always shows no device connected. Fastboot and ADB both see it (devices). If I disable USB Debugging then it is recognised as an MTP device but then the Android Phone error kicks in and Sync doesn't see it.
This is my issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...and this...
Both of these are taken with the phone connected to PC, and whilst connected I can run ADB commands!
What am I missing? This is driving me mad
Try the Universal Naked Driver.
leppie said:
Try the Universal Naked Driver.
Click to expand...
Click to collapse
Well that sounds like fun What is it?
Dunc001 said:
Well that sounds like fun What is it?
Click to expand...
Click to collapse
Haha sounds like fun.
I think its a generic sort of driver
Wilks3y said:
Haha sounds like fun.
I think its a generic sort of driver
Click to expand...
Click to collapse
Hmm, found it - it's just drivers for ADB/fastboot which I don't have an issue with. This is my issue:
...and this...
Both of these are taken with the phone connected to PC, and whilst connected I can run ADB commands!
Dunc001 said:
Hmm, found it - it's just drivers for ADB/fastboot which I don't have an issue with. This is my issue:
...and this...
Both of these are taken with the phone connected to PC, and whilst connected I can run ADB commands!
Click to expand...
Click to collapse
On the Android device in device manager right click then uninstall, tick delete drivers if the tick box is there (sometimes it isnt)
Keep doing that until it doesn't even say android device (it will keep reinstalling it) it should say unknown device or something similar. Then reinstall the htc driver software and try again
Windows buggers up like this sometimes, has several drivers for the same thing, AFAIK its a case of getting rid of all the "spares" and installing just the one driver
Hope this helps
Sent from my HTC One X using xda app-developers app
Dunc do you try on another PC?
jamm513 said:
Dunc do you try on another PC?
Click to expand...
Click to collapse
+1 if it's a driver thing then this should confirm it
Sent from my HTC One X using xda app-developers app
Hey guys, I am having a lot of trouble with my LG G3, and I'm at the point where I'm desperate for help.
As the title says, I'm trying to unroot it and install the stock firmware back onto it (currently running Lollipop 5.0.1).
I have looked at many different guides and they all have basically had me do the same thing.
Here is what I've done so far:
- Downloaded the D850 stock firmware (TOT file)
- Downloaded the dll file that came with it
- Downloaded the LG Flash tool
- Downloaded and installed the LGUnitedMobileDriver
Here is my issue:
When I plug the G3 into my laptop in download mode, the port does not show up in the device manager (as you all probably know, I need to access the port properties so I can change the COM#)... The only thing that shows up is "LGE Mobile USB Composite Device" and it's under Universal Serial Bus controllers.
Just for giggles I decided to click on preferences of the LGE Mobile USB Composite Device and the device status read:
"Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
{Unable to Load Device Driver}
%hs device driver could not be loaded.
Error Status was 0x%x"
The question:
I have heard of other people having the same issue with the port not showing up, and to fix it, they had to uninstall their drivers and re-install them. That's where my noobie-ness comes in. Exactly what drivers do I have to uninstall? Where do I find them? Are they found in the Device Manager? If so I have no idea what to look for. Am I supposed to uninstall the LGUnitedMobileDriver that I installed earlier? Because I have no idea where that installed to, and I can't find it! Sorry this is probably a dumb question but I'm stumped.
I just install new drivers over the old ones. Also make sure usb debugging is off also in device a
Manager it needs to be set to port 41
TheMadScientist420 said:
I just install new drivers over the old ones. Also make sure usb debugging is off also in device a
Manager it needs to be set to port 41
Click to expand...
Click to collapse
Yeah, I know that it has to bet set to 41. I actually have debugging on. Maybe that was the issue... Lets see what happens when I turn it off! Also, it has to be plugged into a 2.0 port on my computer right?
GuyInTheSky said:
Yeah, I know that it has to bet set to 41. I actually have debugging on. Maybe that was the issue... Lets see what happens when I turn it off! Also, it has to be plugged into a 2.0 port on my computer right?
Click to expand...
Click to collapse
Turned off debugging, tried it again, but nothing has changed. :crying:
This is all that shows
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GuyInTheSky said:
Yeah, I know that it has to bet set to 41. I actually have debugging on. Maybe that was the issue... Lets see what happens when I turn it off! Also, it has to be plugged into a 2.0 port on my computer right?
Click to expand...
Click to collapse
Yea no 3.0 somtimes u gotta fool with it diffrent usb ports back and forth. Flash tool is real picky sometimes. Sometimes it would take me close to an hour to get it to read rite. To the point i know all is rite just kept failing. Finally goes through
TheMadScientist420 said:
I just install new drivers over the old ones. Also make sure usb debugging is off also in device a
Manager it needs to be set to port 41
Click to expand...
Click to collapse
By the way, when I try installing new drivers over the old ones, it says:
"You will have to uninstall the previous version before installing this version."
And I have no idea hoe to do that.
GuyInTheSky said:
By the way, when I try installing new drivers over the old ones, it says:
"You will have to uninstall the previous version before installing this version."
And I have no idea hoe to do that.
Click to expand...
Click to collapse
Plug in the device so it shows up in device manager click on it in device man. I think left click and ule get more options like update driver or properties. Once u left click u can find the option of either update disable or uninstall. Im not near my computer or i could walk you throught it better. Rite there near where u change the com number to 41 1 or 2 sub menus before it
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
C:\Users\rikku>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
C:\Users\rikku>adb devices
List of devices attached
1c576f70 sideload
C:\Users\rikku>adb usb
error: closed
Click to expand...
Click to collapse
mkioshi said:
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
Click to expand...
Click to collapse
Changing miui roms still require the bootloader to be unlocked.
mkioshi said:
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
Click to expand...
Click to collapse
Have you tried using Ubuntu and regular adb or something?
If you can't change anything on the phone start changing the way you try to fix it with the PC.
Maybe the linux adb will force it to work or something.
Sorry no specific answer but could be worth a try. If you have the determination there is a chance to fix it.
Your absolute last option is EDL with the test point on the inside of the phone. If you can't send it back to the seller its better to have a phone with a broken seal on the back (just repair it yourself after) than a fully assembled paper weight
Dobsgw said:
Have you tried using Ubuntu and regular adb or something?
If you can't change anything on the phone start changing the way you try to fix it with the PC.
Maybe the linux adb will force it to work or something.
Sorry no specific answer but could be worth a try. If you have the determination there is a chance to fix it.
Your absolute last option is EDL with the test point on the inside of the phone. If you can't send it back to the seller its better to have a phone with a broken seal on the back (just repair it yourself after) than a fully assembled paper weight
Click to expand...
Click to collapse
I tried both xiaomiadb and normal adb, all give the same error, on Mac OS X and Windows 10. Seems to me the problem is in the phone, I dunno.... Thanks a ton tho!
mkioshi said:
I tried both xiaomiadb and normal adb, all give the same error, on Mac OS X and Windows 10. Seems to me the problem is in the phone, I dunno.... Thanks a ton tho!
Click to expand...
Click to collapse
Seriously try Linux
Dobsgw said:
Seriously try Linux
Click to expand...
Click to collapse
I installed a virtual Ubuntu machine, did the passthrough but no dice
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mkioshi said:
I installed a virtual Ubuntu machine, did the passthrough but no dice
Click to expand...
Click to collapse
good day please was this problem solved cause i have the same screen as above
i can't get the mi flash tool to detect my device no matter what i try. it always says device not connect or whatever.
- Used Diffrent cables including the official one
- Using usb 2.0 port
- Intel laptop
- using mi flash unlock tool 6.5.406.31
- adb drivers by snoop05
redfrost6 said:
i can't get the mi flash tool to detect my device no matter what i try. it always says device not connect or whatever.
- Used Diffrent cables including the official one
- Using usb 2.0 port
- Intel laptop
- using mi flash unlock tool 6.5.406.31
- adb drivers by snoop05
Click to expand...
Click to collapse
Did you do that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOSS8 said:
Did you do that?
Click to expand...
Click to collapse
When i click "check" it gives me this error
Also when i check my phone on device manager it shows android composite adb interface
I think that the drivers are not installed properly can you link me the one you used
redfrost6 said:
When i click "check" it gives me this error
Also when i check my phone on device manager it shows android composite adb interface
I think that the drivers are not installed properly can you link me the one you used
Click to expand...
Click to collapse
NOSS8 said:
View attachment 5686069
View attachment 5686073
Click to expand...
Click to collapse
I also have the same drivers but a windows 11 pc when i try to install the android_winusf.inf driver by right clicking and install then there is no response
redfrost6 said:
I also have the same drivers but a windows 11 pc when i try to install the android_winusf.inf driver by right clicking and install then there is no response
Click to expand...
Click to collapse
NOSS8 said:
View attachment 5686069
View attachment 5686073
Click to expand...
Click to collapse
Okay now i tried with the latest miunlocker then it got connected i don't know how tf that happened but yay i am so happy
although i have been given 314 hrs warning but i will wait
redfrost6 said:
Okay now i tried with the latest miunlocker then it got connected i don't know how tf that happened but yay i am so happy
although i have been given 314 hrs warning but i will wait
Click to expand...
Click to collapse
Normally 168 hours.
NOSS8 said:
Normally 168 hours.
Click to expand...
Click to collapse
Hey, do i have to put my phone into fastboot then open miunlock tool and check how many hours are remaining?
is there any sort of other way to check the time remaining ?
redfrost6 said:
Hey, do i have to put my phone into fastboot then open miunlock tool and check how many hours are remaining?
is there any sort of other way to check the time remaining ?
Click to expand...
Click to collapse
Use Mi Unlock and try to unlock it.
NOSS8 said:
Use Mi Unlock and try to unlock it.
Click to expand...
Click to collapse
Oh but i have seen some users having this interface which tool is this
redfrost6 said:
Oh but i have seen some users having this interface which tool is this
Click to expand...
Click to collapse
Still Mi unlock but can be for Mac or linux.
NOSS8 said:
Still Mi unlock but can be for Mac or linux.
Click to expand...
Click to collapse
Oh then i will just connect my phone and check it
thanks for your support