Ok fellas, the title pretty much says it all, I had a bricked Streak and was able to revive it by using the latest QDL tool. I was able to use the ZaRoot tool to root my Streak. TO get it to synchronize I downloaded and installed the latest files from Nero. Now when I connect the phone during the fastboot method, it was coming up and saying Android ADB Interface and I tried many times with that self installed driver. Then I went into device manager and changed the driver to say Android Bootloader Interface and try once again with no luck. I have used both methods of flashing, command prompt and by double clicking the .bat file in the folders. I mention again, I have used both Streakmod and Clockwork images and neither has done anything for me. I have also used 3 different computers, two of them running W7 ultimate x64 and another using W7 Home Premium 32 bit, same results....
I am at my wits end here and dunno what else to try. I have used several .img files for both Streakmod and Clockwork with same results also...
UPDATE!"!!!
Ok guys, so at my wits end like I just stated I had an OLD HP laptop with Windows XP on it (old faithful) XP and I fired it off to see what would happen. Well at first all was the same so I was pretty disappointed. Then I decided to come back to the forum and double check to see if there were any special drivers for XP, in doing so I had to disconnect the Streak's USB and reconnect an external wifi because the laptop's wifi card is bad... so I started at Clockword posts and found nothing but decide to try to flash again, well I tried to execute the .bat file and it just flashed on screen... then I tried using the command prompt window and when I typed in the first command to flash I saw "waiting for device" and realized I had forgotten to plug the Streak back in, WELLLLLLLLLLLL much to my content, when I plugged the Streak back in the laptop began to push the Clockwork image to the Streak!!! WOWWWWWWWWWW I said to myself, finally I get to move a step forward. Well, I rebooted and the first thing I did was to try a nandroid backup but throughout a funny message kept popping back up "E: can't find MISC" thus not letting the nandroid backup complete (that is the same message that kept popping up when I had bricked my Streak). SOOOOOOO, I crossed my fingers and went back and tried the same thing to flash the Streakmod and when it went through I was beside myself with enjoyment!!!! So the first thing I again did was run a nandroid backup and this time it went through without a hitch with no E: can't find MISC" message and it booted up just fine!!!
Hope this helps someone else out. I am going to uninstall all drivers and programs from the other 3 computers to try and verify that it was a driver problem.
But I hope someone can tell me what this "E:can't find MISC" message means in Clockwork....
Any and all input is appreciated...
Forgot to mention, that when I flash using the .bat file the command prompt window flashes up on my laptop screen for a brief moment but not for long enough for me to see what it says... which leads me to believe I have a driver problem, but how can that be if I am seeing "Fastboot_Mode" on the Streak???
I've had a look and not seen anyone else with this issue. I installed CM7 and everything worked fine after reboot except when I connect it to PC to debug it doesn't read the phone. It will however read phone when in external storage mode and in device manager it shows the phone and it's current USB driver. Reinstalling drivers didn't work.
So then I wiped system memory and cache and reflashed CM twice as heard that helps. Still not read by adb and this was before I backed up apps from titanium. Then spent another few hours reinstalling drivers, including the one from the Heimdall suite, continuely restarting ADB and computer. ADB still not reading it. Any ideas?
Didyou check Development to see if USB Debug is checked? By default it's checked but you may just have to uncheck it and recheck it again?
Yeah in addition to the restarting ADB and phone etc.. I also tried that a few times.
I believe you need the Nexus S drivers. But i'm not sure because I never tried it.
Thanks so much, works perfectly now!
Hi Guys and Gals, I have ran into an issue I have not experienced before. I was wiping davlik, cache and factory resetting my Droid Razr for a friend to use, as I dont use the phone anymore. I did all of the above with an extra FATAL error of accidentally wiping the system. I thought I had backed out and was rebooting the system.
I booted my phone into fastboot to use Matts utility to flash back to stock and when I connected to my computer, it began to install the driver for "Fastboot CDMA Spyder S" after a few seconds of saying installing, it shows a red x and says failed.
I uninstall and install the moto-drivers again and same thing occurs when I plug phone to computer. I have a factory cable tried it as well and still fails to install fastboot driver.
Any ideas or know what I am doing wrong.
UPDATE: I solved by uninstalling everything that had to do with anything mobile on my computer (drivers, software ect..) Although I dont think it was necessary. I then downloaded Motorola device manager and reconnected my phone and it worked. Here is the link to the latest device manager, https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
hi, i tried rumrunner but it keeps giving me a usb connection error when testing the adb. but when i use the adb commands in the sdk it shows up just fine and everything works. and my fastboot works as well. but on rumrunner when it runs fastboot first and then adb the adb doesnt recognize my device. ive uninstalled rebooted and reinstalled the drivers but nothings working. please help!!
this is the error message i get when running rumrunner, and i cant figure out why. on the left is my initial adb test, and then on the right is my rumrunner right afterwards
pRoDiGyXxGiRl said:
hi, i tried rumrunner but it keeps giving me a usb connection error when testing the adb. but when i use the adb commands in the sdk it shows up just fine and everything works. and my fastboot works as well. but on rumrunner when it runs fastboot first and then adb the adb doesnt recognize my device. ive uninstalled rebooted and reinstalled the drivers but nothings working. please help!!
this is the error message i get when running rumrunner, and i cant figure out why. on the left is my initial adb test, and then on the right is my rumrunner right afterwards
Click to expand...
Click to collapse
Check and make sure that when your phone reboots it connects to the computer properly, I had a similar issue when i was using moonshine to flash my phone, you should see that the phone is connected and listed in Explorer when you reboot. also make sure that you UNINSTALLED HTC Sync - if it fails to load the drivers, you may try quickly unplugging and replugging in the usb cable into your computer during the countdown, definitely do not do that after it has connected - doing so will result in a brick. follow this advice at your own risk. if you don't feel comfortable with it, don't try it, try another computer, it just so happens that i tried moonshine on 3 of my pc's before i finally got it to run with out hanging.
you can also try this tool kit to install the drivers separate from sync: http://forum.xda-developers.com/showthread.php?t=2219175
p1droidx said:
Check and make sure that when your phone reboots it connects to the computer properly, I had a similar issue when i was using moonshine to flash my phone, you should see that the phone is connected and listed in Explorer when you reboot. also make sure that you UNINSTALLED HTC Sync - if it fails to load the drivers, you may try quickly unplugging and replugging in the usb cable into your computer during the countdown, definitely do not do that after it has connected - doing so will result in a brick. follow this advice at your own risk. if you don't feel comfortable with it, don't try it, try another computer, it just so happens that i tried moonshine on 3 of my pc's before i finally got it to run with out hanging.
you can also try this tool kit to install the drivers separate from sync: http://forum.xda-developers.com/showthread.php?t=2219175
Click to expand...
Click to collapse
thanks!! i will try the toolkit. i never installed htc sync so i know its uninstalled lol. and i will also try the unplugging the cable. oh and i dont know if this matters or not, but my bootloader is still locked because it said for rumrunner i dont need to have it unlocked. is that correct?
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Luinwethion said:
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Click to expand...
Click to collapse
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
ante0 said:
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
Click to expand...
Click to collapse
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Luinwethion said:
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Click to expand...
Click to collapse
I ran into this also and I un-installed HiSuite, then re-installed it and after that in device manager set up drivers as seen in screen copy in attachement.
I also refer to this page for more info: https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Luinwethion said:
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
Click to expand...
Click to collapse
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
AntoRei said:
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
Click to expand...
Click to collapse
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Luinwethion said:
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Click to expand...
Click to collapse
You can use this guide with linux?
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814