Hi all,
I am have bricked my device, its in fastboot mode but wont do anything anymore.
Ive tried literally everything possible, ive read numerous manuals, seen tons of video tutorials but nothing works.
The main issue I am facing now is that MSMDownloader tool does not recognize my phone because of an Driver issue.
However, whatever I am doing I cant get the correct driver to function on my Windows 10 machine.
Whatever I do, it either does not recognize the device, or shows it as Kedacom USB Device / Android Bootloader Interface.
I have manually removed the drivers from the device manager as well as removing them manually with pnputils, it does remove the driver and then shows it as Android Device.
If i then scan the folders (whole windows is in testing mode like many manuals tell me to) it just wont install the driver and if i do that manually using pnputils it changes nothing.
The only moment it changes is when I connect to the internet and search for a driver and the old samer driver will be installed.
I have tried the OnePlus driver installer, I have tried the All In One tool, I tried the Qualcomm QDLoader HS USB Driver, I tried it totally disconnected, i rechecked if i was running cmd and the msmdownload tool as administrator, i have rebooted and updated my pc, rebooted and tried again.
I am pretty sure its an driver issue, but apparently whatever I do i cant seem to be able to fix it, and another way of fixing this phone is probably not gonna work as whatever I do with the volume, power buttons, how many times i reboot i just keep getting the same Fastboot/Download screen.
Does anyone have any other idea, am i missing something? I really have no idea. I have followed several manuals step by step, googled and found people with similar issues tried those solutions, i am now busy for like over 12 hours and am really getting the idea that i cant fix it
This can be closed, I have used the info from this thread:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
It helped me revive my phone without having to deal with the USB issues and MSMDownloader.
schorrie said:
This can be closed, I have used the info from this thread:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
It helped me revive my phone without having to deal with the USB issues and MSMDownloader.
Click to expand...
Click to collapse
THREAD CLOSED on request of OP!
Related
Purchased a gtablet, all went smooth after I installed the TNT Rom, but found some sound issues, and found out that seemed to plague a lot of other people, so decided to try another ROM - can't even recall which one now. But now where I'm stuck at is if I hold down vol up and power, I get "Recovery key detected Booting recovery kernel image" and it sits there forever. Even if I take out the microsd card, I get the same screen. A normal power attempt sits forever at the Viewsonic "birds" screen. I've tried just about every rom, none take . I'm pretty sure I had the clockwork recoverymod installed, but now I can't even get into that.
I tried volume down + power, (ATP mode?) but none of the drivers I've found are for Windows 7 64 bit, so I can't access the tablet in that mode because the lack of drivers.
Any suggestions on what to do from here?
Thanks!
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
http://forum.xda-developers.com/showpost.php?p=9302497&postcount=5
Bottom of instructions section -- a few users have written posts on nvflash for windows.
LGCubana said:
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
Click to expand...
Click to collapse
Hi,
Thanks for the link.. I think I've seen that - I don't see a APX driver missing in Device Manager - there is a ADB Interface, however when I let that install drivers, it says the Device cannot start - Code 10.
I may have another computer I can boot up and try
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
butchconner said:
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
Click to expand...
Click to collapse
It did work on my old POS XP Laptop I knew that thing was useful for something!
Thanks again.. Never thought I'd be so happy to see "TapnTap" again. And now I'm up and running on the Vegan rom
Hello everyone and well I have to say I am at my wits end over here.
I have literally just spent hours trying to find the solution without luck. So any help will be greatly appreciated.
I am completely new to android as well and this only makes things much more worse.
I have a Proscan PLT-7035 a cheap tablet by all means and my son accidentally locked the screen under too many password attempts.
I have been trying to factory restore it only to learn this Chinese hardware apparently was not shipped with a recovery option.
This means I cannot put it under USB debugging and I cannot disable mount the mass storage device. So when I connect it to my computer I am able to access all the files but that is it. Honestly it is the biggest 4G usb stick I have ever owned.
Anyway I have tried multiple guides to root and what not as well as I tried multiple button combinations to no avail. It also seems I am able to enter recovery mode by clicking the power button + volume down after shutting the device.
You can hear the sounds in windows of a device being connected and disconnected. There was also an uninstalled driver when i checked Device manager. This is how I was ultimately able to install the drivers as per this guide
It now shows under Android Device as Android Composite ADB Interface.
Now I have tried using Rockchip Batch Tool but It also gets stuck on <Layer 3-3> Test Device Start.
I have tried ICS Root Unlocker and I get error :device not found.
I try adb devices and no devices are listed.
My device is clearly not being detected and I do not know if this is due to driver incompatibility or due to the fact I cannot set the device to USB debugging.
I already disabled driver signature enforcement I'm on Win8Enterprise N x64.
Now someone here was kind enough to upload these and I have absolutely no idea. How to install them or have them run.
So you all can see I've been almost everywhere and in all honesty I have no idea what to do next.
Any lleads will be Godsend. Thanks in advance.
Please let me know if this is in the wrong category. Thanks
It is showing my device in "adb devices" when it is turned on, but it is not there when it is in fastboot mode, i cant flash any img, it stucks, i have done everything, unlocked bootloader, everything. But fastboot doesnt see my device, i have done a bit of research and i realised that it is showing SAMSUNG drivers under my ASUS device tab in that device manager, i have seen this problem in another topic and they said they have uninstalled those samsung drivers trough control panel and it worked for them, but i tried that and installed google drivers from google SDK, ASUS drivers that came with aus sync, both at once, then 1 of them and neither worked and i have tried like 95581546 things, reinstalling, uninstalling,restarting pc, disabling antivirus, and i cant get adb to see my device in fastboot. And in hdwwiz, when i am installing drivers manually it shows me Samsung drivers in Asus group and i dont know how to remove them from there. Or any ideas how i can get it to work?
Thanks
(sorry for grammar nazi and for this topic in wrong section, but i cant make new threads under "Development" because this is my first post)
For me, it was a wiring problem. I hadn't got the original wire plugged, but a second one bought in ebay. Then I used the original one, and problem solved. I hope it is your problem.
Tajmoti said:
It is showing my device in "adb devices" when it is turned on, but it is not there when it is in fastboot mode, i cant flash any img, it stucks, i have done everything, unlocked bootloader, everything. But fastboot doesnt see my device, i have done a bit of research and i realised that it is showing SAMSUNG drivers under my ASUS device tab in that device manager, i have seen this problem in another topic and they said they have uninstalled those samsung drivers trough control panel and it worked for them, but i tried that and installed google drivers from google SDK, ASUS drivers that came with aus sync, both at once, then 1 of them and neither worked and i have tried like 95581546 things, reinstalling, uninstalling,restarting pc, disabling antivirus, and i cant get adb to see my device in fastboot. And in hdwwiz, when i am installing drivers manually it shows me Samsung drivers in Asus group and i dont know how to remove them from there. Or any ideas how i can get it to work?
Thanks
(sorry for grammar nazi and for this topic in wrong section, but i cant make new threads under "Development" because this is my first post)
Click to expand...
Click to collapse
Try using the Universal Naked Drivers instead.
http://forum.xda-developers.com/showthread.php?t=2139767
Tajmoti said:
It is showing my device in "adb devices" when it is turned on, but it is not there when it is in fastboot mode, i cant flash any img, it stucks, i have done everything, unlocked bootloader, everything. But fastboot doesnt see my device, i have done a bit of research and i realised that it is showing SAMSUNG drivers under my ASUS device tab in that device manager, i have seen this problem in another topic and they said they have uninstalled those samsung drivers trough control panel and it worked for them, but i tried that and installed google drivers from google SDK, ASUS drivers that came with aus sync, both at once, then 1 of them and neither worked and i have tried like 95581546 things, reinstalling, uninstalling,restarting pc, disabling antivirus, and i cant get adb to see my device in fastboot. And in hdwwiz, when i am installing drivers manually it shows me Samsung drivers in Asus group and i dont know how to remove them from there. Or any ideas how i can get it to work?
Thanks
(sorry for grammar nazi and for this topic in wrong section, but i cant make new threads under "Development" because this is my first post)
Click to expand...
Click to collapse
Have you tried a different USB port on your PC? I know when I first started customizing my tablet I had problems using the front ports on my PC. It wouldn't recognize my tablet in fastboot, but when I plugged into one of the back ports directly on the motherboard it worked great.
Ehh
I have reinstalled drivers few times and plugged it to back of the PC and it works! It is still not showing my tablet in adb devices (now i am not sure if it should show it there in fastboot) but the img transfer has finished and everything is fine, thanks for all help!
Solved
Tajmoti said:
I have reinstalled drivers few times and plugged it to back of the PC and it works! It is still not showing my tablet in adb devices (now i am not sure if it should show it there in fastboot) but the img transfer has finished and everything is fine, thanks for all help!
Click to expand...
Click to collapse
@Tajmoti can you add solved to the thread name...
lj50036 said:
@Tajmoti can you add solved to the thread name...
Click to expand...
Click to collapse
I dont know how LOL
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
donk165 said:
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
Click to expand...
Click to collapse
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Mr hOaX said:
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Click to expand...
Click to collapse
Fair enough, well i'm thinking I may move back to CM11S if things don't work out on Blisspop. If I turn off USB debugging and then switch to camera (PTP) mode and then back to MTP mode, my phone then connects fine. I wanted it to connect so I could copy my Titanium backup files off the phone and onto the PC. In the end, my mate told me about Airdroid and I managed to download them through that as a ZIP file. For some reason, the titanium backup folder isn't visible from your computer, I tried copying it to the DCIM folder and it just gave me a 1kb file. I also tried a new folder called backups and it was empty when I looked on my PC, but the files were visible when using Airdroid and also when I used a file browser on my phone.
Weird stuff!
Just wanted to bump this and see if anyone has a solution or even just an explanation.
Whenever I plug my OPO into my PC (with the original cable), the device, A0001 is found but is shown in Device Manager with an exclamation point. If I then right click on it and chose uninstall, and then reconnect the phone, it will connect and work fine for MTP/PTP modes. If I put USB debugging on, the MTP doesn't always work after. But no matter what, if I shutdown my PC, and then come to connect the phone the next day etc, I have to do the uninstall of the driver then reconnect for MTP to work. Pretty frustrating!
Anyone know why the phone isn't remembered by my PC correctly? I'm on Windows 7 x64 if that means anything.
I'm moving back to stock ROM soon so I'll see then if its something to do with the unlocked bootloader or using a custom ROM. I'll report back if I have any luck
Bumping this again, its still the same on 6.0. I don't fancy moving back to stock ROM, I like CM over Cyanogen OS, but this problem is really frustrating. Every single time I connect the phone to the PC, it will come up as A0001 but with an exclamation mark next to it in Device Manager, if I right click and uninstall the driver, then reconnect the phone, it works fine then. But if I restart my PC, it does the same thing where it cant find the right driver for the phone.
Is there anything I can try to fix this?
I followed this tutorial. Qualcomm drivers worked briefly for detecting my device initially. I unplugged, opened up the MSM tool and went to plug the phone back in to begin the process, no luck. Now when I check device drivers it shows this error (Device Descriptor Request Failed). Does anyone have any experience with how to fix, its driving me nuts.
lukebukowiec said:
I followed this tutorial. Qualcomm drivers worked briefly for detecting my device initially. I unplugged, opened up the MSM tool and went to plug the phone back in to begin the process, no luck. Now when I check device drivers it shows this error (Device Descriptor Request Failed). Does anyone have any experience with how to fix, its driving me nuts.
Click to expand...
Click to collapse
Keep at it.
I spent two days unbricking a 7T when it happened. Take 2/3 tutorials and see that every condition is met. Don't forget to look for the proper Qualcomm pilots, you might need to update them manually. (If I didn't know any better I'd say that your problem here)
The drivers you're looking for are named QDLoader something.
I know it should work because I did it on the One plus 9 if my memory serves me right, you just need to follow through and make sure that you also have the right MSM tool.
Pay attention to small details like the phone might be crashing on the start you should restart accordingly, or maybe you're not pressing the right volume button (was it up + power? I don't remember) and see what your computer sees plugged in.
Use more than one USB cable just in case but seems unlikely.
I followed this procedure since the one you referenced the google docs link would never download for me: https://www.droidwin.com/unbrick-oneplus-9-pro-msm-download-tool/
I had to use the alternate method to get to EDL mode in that tutorial since the normal one did not work. I also had to uncheck the box that said something about SHA256 before it would say Waiting.