Today I tried to return to MIUI from Windows 10 Mobile and it went wrong. I found a guide that said, that I should choose "Mass Storage" in UEFI menu, then wait until the device shows up in Explorer, and then flash fastboot image using MiFlash. But MiFlash failed to do this, so my device is completely bricked right now. Holding any button combination does nothing, Windows can still detect that something is connected via USB, but it shows the message "The last USB device you connected to this computer malfunctioned and Windows does not recognize it". Even notification LED doesn't turning on, when I try to charge the phone. When I tried to check this phone on Linux PC, using "lsusb" command(just wanted to check if it's even connecting), it stuck without any output to terminal. So, right now, I'm completely clueless, what shall I do next.
Related
. .
. .
I know, silly response, but is your phone is USB debugging, and after you connect it via usb, do you manually mount the device from the notification menu?
Good Luck.
Redfoot
. .
If you're using Windows 7, Windows may not be assigning a drive letter to the phone when you plug it in.
Is if this helps.
I had this similar problem today... I fixed it by uninstalling Kies/Drivers, re-installing drivers from the Samsung website, unplugging the Captivate, restarting it into Download Mode (Power + Volume Up & Down), and plugging back in the Captivate. Windows 7 said "Installing new drivers" (which it installed the USB ADB drivers), but said the device "could not start". I unplugged the phone, took out the battery, rebooted the phone, and plugged the phone back in. Windows 7 said again it was installing the drivers, this time with success. Yay!
. .
I think you can flash using Odin One click. just try to reinstall samsung drivers anyway. or use the repair driver utility on kies. then try odin. don't give up :T
So I wiped my phone, went to flash the unofficial kitkat CM rom, and found out I had the wrong recovery version. No biggie, I thought, I'll just reflash my backup ROM. Well, it wasn't where I left it, so now I'm stuck without a ROM to flash. That was okay, though, I could just push one via adb. Then my computer gave me the "USB device not recognized" thing, and so I've tried reinstalling drivers, cleaning the registry, rebooting many times, and all to no avail. I'm lost! Wise ones of XDA, what can I do?
Bump. I really could use some help, I use my phone for work and school and it's a paperweight in it's current state.
I'm guessing you have no access to an sdcard? Looks like you need to use Odin to go back to stock then reroot and unlock. Try uninstalling the drivers then boot your S3 into download mode (hold volume down, home, and power) follow the on-screen prompt, then plug your S3 into the computer to force install new drivers. Now, unplug and pull the battery and try flashing stock, and root/unlock. Try another port, keep the computer plugged into the wall, and also make sure you're using the Samsung USB cable.
SlimSnoopOS said:
I'm guessing you have no access to an sdcard? Looks like you need to use Odin to go back to stock then reroot and unlock. Try uninstalling the drivers then boot your S3 into download mode (hold volume down, home, and power) follow the on-screen prompt, then plug your S3 into the computer to force install new drivers. Now, unplug and pull the battery and try flashing stock, and root/unlock. Try another port, keep the computer plugged into the wall, and also make sure you're using the Samsung USB cable.
Click to expand...
Click to collapse
No sd card. My computer shows the same "USB device not recognized" message while the phone is in either download mode or recovery, and while using my samsung usb cable and a new one I bought yesterday evening. I've deleted every driver for it, tried every port, and it's the same thing every time. EXCEPT, for some reason, when I plug it into my USB 3.0 ports, it shows up in device manager under "other devices- unknown device", but when it's plugged into my USB 2.0 port, it shows up under "USB controllers- unknown USB device (invalid device descriptor)".
Danno131313 said:
No sd card. My computer shows the same "USB device not recognized" message while the phone is in either download mode or recovery, and while using my samsung usb cable and a new one I bought yesterday evening. I've deleted every driver for it, tried every port, and it's the same thing every time. EXCEPT, for some reason, when I plug it into my USB 3.0 ports, it shows up in device manager under "other devices- unknown device", but when it's plugged into my USB 2.0 port, it shows up under "USB controllers- unknown USB device (invalid device descriptor)".
Click to expand...
Click to collapse
If its not connecting to your main computer, try another computer. Honestly though, I think you need to purchase a cheap sdcard (format it to Fat32) and put a rom on there. Cuz you can still access download mode and also recovery correct? Maybe by then, there will be a few more replies or some idea that will get you in the right direction.
SlimSnoopOS said:
If its not connecting to your main computer, try another computer. Honestly though, I think you need to purchase a cheap sdcard (format it to Fat32) and put a rom on there. Cuz you can still access download mode and also recovery correct? Maybe by then, there will be a few more replies or some idea that will get you in the right direction.
Click to expand...
Click to collapse
I just have my laptop. I've bought an sd card now, but I don't have a reader. When I fix this I'll put a backup on there I think I'm just going to reinstall windows and get a fresh start. Then maybe I'll be able to ADB sideload a rom.
I had similar problem
After I screwed up my device, this was the way I got the right recovery installed in order to flash 4.4
I cant post links in posts yet, I'll pm you the link.
Hey all.
I'm real sorry if this is out there somewhere--which I'm sure it is.
I had no luck using the search feature.
My PC (win 8.1) will not recognize the phone when connected in fastboot mode. I have the drivers installed and will work/connect when powered on. In fastboot it DOES show that the USB is obviously connected but, again, PC doesn't pick it up or says there was a "problem" with this device....
I am trying to the the TWRP recovery installed.
In addition, why is it when stock "recovery" is selected is shows the android with the statement "no command" and does nothing?!
Thanks for any and all help and/or links
I'm hoping someone can help me out here. I've rooted phones before and didn't have any trouble previously. I just bought a used Pixel 3 on eBay with the plan to root using Magisk. The only problem is I can't get the device to be recognized at all on my PC. I've tried all the usual things like different USB ports, different cables, cleaning out the port, etc. I have the latest drivers installed and I have a Pixel XL that is recognized by my PC immediately so I know I have the correct drivers installed. Pixel 3 does not show up in Device Manager at all. I have USB debugging enabled on the device, but it never prompts me to Allow USB debugging when I connect the Pixel 3 to my PC.
Now, here's the weird part. I know the cable is working fine because I use the same cable and plug it into my Mac. The Pixel 3 is recognized immediately and I'm prompted to enable USB debugging. ADB then works just fine on my Mac. 'adb devices' shows my phone. But I then try to use 'adb reboot bootloader' and my phone reboots to the bootloader as it should. At this point my phone says it's in FastBoot Mode, but the device isn't recognized using 'sudo fastboot devices' and if I try 'sudo fastboot flashing unlock' it just sits there saying 'waiting for any device'. I've also tried putting it into FastBoot mode manually by using the Power and Volume Down key, but run into the same issue with it not being recognized while in FastBoot mode.
Could the previous owner have done something to the bootloader to cause the device to not be recognized in FastBoot mode? And is there any way to fix it? Why would the phone be recognized on my Mac without issue, but using the same cable and multiple different ports on my PC, it never gets recognized?
Any help would be very much appreciated here as I'm at a loss as to what I can do and fear I just spent money on an expensive paperweight.
I tested the cable I'm using with my Pixel XL and it's immediately recognized by my PC and the notification for USB debugging shows on the phone, so I know the cable is working out. No device ever shows in the device manager when I have my Pixel 3 connected though. I've even uninstalled the drivers while my Pixel XL is connected to hopefully put Windows into a driverless state hoping my Pixel 3 would then show up as an unrecognized device, but no device. I can't get it to show up at all in Windows for some reason and it's not recognized while in fastboot mode on my Mac. Fastboot mode information all seems to match what a Pixel 3 should look like as well, so I don't think the previous owner installed the wrong software causing device id mismatch. Anyone have any other suggestions for what I can try?
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