My OPO is currently in a bootloop and I want to factory reset it, however it seems like my device is unrecognized no matter what. I keep get an MTP USB device failed to install. I have tried running adb devices and it does not show up under there as well.
I made a previous thread that caused the bootloop problem here:
http://forum.xda-developers.com/oneplus-one/help/paranoid-android-5-1-bootloop-t3104618
Thanks in advanced!
Please don't create duplicate threads regarding the same issue. Use the existing thread for help with your problem.
Thread closed.
Related
Hello!
I have an HTC m7, and am using Windows 7 to interface with it. Long story short, I have twrp on it, but no working operating system. For a moment yesterday, it appeared successfully in the results of /adb devices, though when I tried to push a new rom to the internal storage on the phone using adb sideload, it failed (made it to 100% but then said failed, and when I tried to install the created .zip file, it failed as well). Since that attempt, I have been unable to see my phone as an ADB device again - I've reinstalled HTC drivers, tried various usb cables, and gone through many iterations of /adb devices (blank) /adb kill-server. After failing to find a solution elsewhere on these forums or elsewhere, I come to you.
I'd love to know if there's anything that could cause the phone to disappear after it had been previously connected, and if there's some further steps I could take to get it to work!
Thanks for your help,
Devin
Hi there!
I suggest you try returning to stock, since you're having troubles with adb. Tho, it must be a driver issue, or cable, or USB port. Usually it ends up being the cable in cases similar to yours.
Anyway, if you have no luck, try returning to stock....here's a great guide,
>*HTC One*>*One General*>*[GUIDE] How to Return to 100% Stock
Of course you will need to install recovery and root again after.
Any questions on this can be asked in the guide thread.
Good luck!!
I already install the CyanogemMod 12 on my nexus 4, it already installed for a past few weeks. And then some problems occur. The problem is when i connect my nexus 4 to PC via USB, it doesn't detected by my pc. It just detected as Other Devices -> 'Unknown Device'. I already try to change the port usb but it still give me same error. And then i try to go to Setting -> Storage -> USB computer connection, but it doesn't do anything. It just going back to storage. Usually after we click USB computer connection, it will go to some option like camera and mtp, but mine doesn't do anything. and i try to use ADB connect with developers debug mode and IP/TCP. it works, i can do 'adb reboot bootloader' but after that when i try to use 'fastboot oem unlock' it just 'waiting for device'. and when i use PdaNet, it can't detect my nexus 4. I hope some of you guys know about this problem and know the solution too.
Note : my nexus 4 just have some problem with soft keys (which i believe is hardware problem). I don't know if this is has some impact with my problem up there. and sorry for my bad english.
Hi
Thanks for writing to us at XDA Assist. I can see that you've already posted the same topic in the CM12 thread here. Please refer to the XDA Forum Rules for information regarding the creation of duplicate posts. I'm going to let the people in the CM12 thread help you, as that's the most suitable place. Good luck!
Thread closed.
I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance. (its my first thread in the forum, i hope to post it on the right section, i posted it here because i need the assistance of the developers i guess)
Hello,
Welcome to XDA.
The XDA Assist forum isn't what you think it is. We merely assist by helping to point users with issues in the right direction for their issue.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/xperia-s/help?nocache=1&z=2025285740382969
The experts there may be able to help.
Register an XDA account to post and reply in the forums.
So Im running into a weird issue that I've never before experienced. I have an SM-T320 tablet and it currently has no OS installed. It was wiped via TWRP. After wipe completed, by tablet restarted abruptly and, ever since, has not gone past the splash screen. I tried entering recovery mode again many times and each time it failed.
My light at the end of the tunnel is download mode, which I've managed to enter. My tablet is currently in download mode, and ODIN sees it (I've attached a couple pictures). I managed to even follow this thread and my tablet restarts when ODIN finished but, again, does not go past the splash screen.
When I query all attached devices with `adb devices` command, it doesnt display it.
Any advice would be much appreciated.. I dont know what's going on. I've installed a variety of different drivers of different versions from a variety of different sources. Results are the same -- ODIN sees device, ADB doesnt.
Here are the images
wertywhy said:
So Im running into a weird issue that I've never before experienced. I have an SM-T320 tablet.......
Click to expand...
Click to collapse
I don't have this device but, I believe that one or both of the following threads should be helpful for what you are looking to do that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3673338
https://forum.xda-developers.com/showthread.php?t=3303851
https://forum.xda-developers.com/showthread.php?t=3040594
One or more of them may be a bit dated but, the information should still apply...
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, I believe that one or both of the following threads should be helpful for what you are looking to do that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3673338
https://forum.xda-developers.com/showthread.php?t=3303851
https://forum.xda-developers.com/showthread.php?t=3040594
One or more of them may be a bit dated but, the information should still apply...
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
All three links don't help me because ADB does not list my device, which is the core problem. If I could just get ADB to recognize my device, I can run an `adb reboot recovery` and solve my problem that way.. but alas I can't get ADB to see my tablet. This is so odd to me.. it cannot be a driver issue because ODIN sees my device.
Solved my issue by flashing firmware on device.
my problem is the opposite , My amazon fire hd 7 9th gen is recognized in adb as devices, but it is not recognized in odin I tried both use mtp (windows 10 driver), and the kindle fire stock driver, but still not detected in odin and still recognized somehow in adb. some help would be nice
Samsung Odin is a very lightweight and easy-to-use Stock ROM flashing tool for the Samsung Galaxy line of devices including Samsung smartphones and tablet devices.
Dan TBA said:
my problem is the opposite , My amazon fire hd 7 9th gen is recognized in adb as devices, but it is not recognized in odin I tried both use mtp (windows 10 driver), and the kindle fire stock driver, but still not detected in odin and still recognized somehow in adb. some help would be nice
Click to expand...
Click to collapse
you can't use odin for other devices except samsung.
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!