I'm trying to help a friend recover the data from his oneplus A5010. The touch screen is not responding so I can't enable anything. (file transfer... OTG... Are off).
I read in the forum that it is possible to switch usb debugging on. Using custom default.prop file and then sideload it from the recovery.
But for that I would need a help for a developer and some basic instructions on how to flash the custom file.
I checked maybe it is possible to install CWM or TWRP. But from what i can tell i can't install then without the debugging option
Other solutions are also welcome.
Do you have an OTG cable? If so, you can try plugging in an external mouse and use that to select menu items.
---------- Post added at 03:45 PM ---------- Previous post was at 03:44 PM ----------
Rethinking my previous post, I don't think that will work, as the OTG isn't natively active (thanks OnePlus). Is the screen entirely non-responsive?
Tried using OTG but it doesn't work. Mouse and keyboard are not responding
Probably the option is disabled
And touch screen is completely dead
Related
Hey guys,
So I'm attempting to root the nexus. I was following the instructions and put it into bootloader mode. I accidentally hit the power button while it said start at the top of the screen and it restarted. Now every time I power off and try to enter bootloarder mode it wont display the android guy. How can I bring that back up?
thanks,
Mike
try adb reboot-bootloader?
opticaldh said:
try adb reboot-bootloader?
Click to expand...
Click to collapse
my phone also isnt getting recognized by my computer now as well
hkdflip2 said:
my phone also isnt getting recognized by my computer now as well
Click to expand...
Click to collapse
try adb devices. If nothing shows up, then I think you should reinstall your driver. I used the Nexus Root Toolkit to install the driver.
After you uninstall the driver and plug in your device again, if Windows keeps installing autimatically the driver, then you should disable the Automatic Driver Update (or something named like that). I used to stuck with this Driver Update for 2 days. After I disable it, uninstall driver, then install again through Device Manager. Everything is OK now.
Cross check if USB debugging is enabled before connecting via adb. I have never used that Start option so don't know what it does apart from booting your phone.
---------- Post added at 04:23 AM ---------- Previous post was at 04:19 AM ----------
I reproduced the actions that got you the bug (selected Start from boot loader screen). But my boot loader still shows up.
Try adb bootloader
sent from my nexus 4; cat on lap, beer in hand
So i figured out most of it, im following the instructions from http://www.youtube.com/watch?v=g88PPZyvfDI however i get to the part about 11 1/2 minutes in where my phone should be rebooting once i put usb debugging on however i put it on and my phone doesn't restart and the nexus toolkit just says waiting for usb debugging to be enabled. Any suggestions
I used the OTA update and it went (as far as I can tell) without any problems. I tried to install TWRP, but when I use Wug's toolkit, or N-Cry, they cannot detect the phone in ADB. I tried removing and re-installing the drivers, but no luck. It worked fine before the update to 4.3, but obviously something has changed.
It will see the phone if I'm in fastboot, just not when the phone is up and running normally. Is this normal with the 4.3 update (I know not being able to get root at the moment is)?
Have you enabled USB debugging?
Sent using xda-developers app
chromium96 said:
Have you enabled USB debugging?
Click to expand...
Click to collapse
Yes, sorry, should have mentioned that...it is.
I tried un-checking the USB debugging box and re-checking it, un-plugging and pluggin the USB back in, rebooted computer and phone several times as well.
Did you update adb and fastboot as well?
Try updating your sdk or at least the platform-tools
I just updated the drivers using Wug's toolkit, is did that update adb and fastboot at the same time?
I'll try and update sdk and see if that helps.
I just tried installing Wug's toolkit on another computer running W7 (previous one on XP), and it seems to work great now It did ask me about alowing the RSK (I think), but then it seems to work fine. I was also able to use N-cry and get root back
Now I have to figure out how to install TWRP. I tried Wug's, but it didn't stick, when i try to boot into recovery it just give the android on his back with a red exclamation mark.
Same problem here. Followed the steps in the toolkit to install drivers, and the test always fails. The phone is seen by windows as a nexus 4, and no adb device nowhere to be seen.
I'm on Windows 8 BTW.
---------- Post added at 07:03 PM ---------- Previous post was at 06:49 PM ----------
Additionnal information : when i connect the phone, it appears as "Google Nexus ADB Interface" in the device manager. I seriously don't get it.
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
Another : while messing aroung with the toolkit, i ended up on a tutorial about how to activate USB debug on my phone.
USB Debug is activated, but there is this step : 4.) You will see a prompt with your computer fingerprints [...]
I never get prompted for anything, would be on my computer or on the phone. Am i missing anything ?
---------- Post added at 07:25 PM ---------- Previous post was at 07:08 PM ----------
Alright sorry for spamming but finally found a solution : the phone has to be connected to the computer in camera mode -_-
1. Windows 7 Pro
2. I plugged in device and it is looking for an APX driver?
3. Tried hard reset and device does not vibrate
I have searched and googled. Unable to find suggestions that helped.
Does it vibrate when you turn it on?
poslato sa elmag radija
---------- Post added at 07:01 AM ---------- Previous post was at 06:59 AM ----------
Maybe you cld try to download some of blackthunders tools and install drivers. Then try to reboot via a500 manager.
poslato sa elmag radija
no vibrations
I downloaded some USB drivers from Acer website and now I have "Acer USB Boot-recovery driver" listed in Device manager.
I'm guessing that is good?
Hello!
My problem
My problem is that when I connect my Mako to my PC, it repeatedly connects, disconnect and reconnects every 2-3 seconds. The hardware icon flashes in the taskbar and I hear the connect/disconnect sound played. This is a very weird behavior I have never seen in any other device. It also means that any ADB operations are rendered impossible because the connection is severed constantly.
My phone
Stock Mako
Also tried after having installed CM12
My computer
Windows 10 (dev preview)
What have I tried?
The problem only appears when the phone is powered on fully or in recovery mode. In bootloader mode, it is stable (but here, obviously, I have no ADB connection). This lead me to believe it was a problem with my ADB drivers, so I tried the following:
Different USB ports on the computer
Reinstalling Google's ADB drivers
Installing custom ADB drivers
Removing all ADB drivers (this prevents the phone from connecting to ADB entirely)
Troubleshooting using http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396 and other guides
Additional question
I could technically do without ADB, but the reason I want it is so that I can clear my phone and install ROMs cleanly with sideloading (without having to boot into the phone, download the zip and then reboot). I'm quite new to flashing -- is it usually a bad idea to boot the phone and download the zip and then install? Am I right in saying it would be better to sideload or push the zip onto the device after a complete format? Or is that just an incorrect thing to assume.
I will be trying with a new USB cable in the next few days, hopefully that should solve it.
Doggie52 said:
I will be trying with a new USB cable in the next few days, hopefully that should solve it.
Click to expand...
Click to collapse
What happens when you fastboot devices in the bootloader?
For sure try a new cable, if it does not help, you are likely facing a hardware failure like in the following post:
http://forum.xda-developers.com/nexus-4/help/nexus-4-computer-t3048983
---------- Post added at 08:53 AM ---------- Previous post was at 08:39 AM ----------
and here
http://forum.xda-developers.com/google-nexus-5/help/usb-fastboot-adb-driver-issue-t3055262/page2
joegestes said:
What happens when you fastboot devices in the bootloader?
For sure try a new cable, if it does not help, you are likely facing a hardware failure like in the following post:
http://forum.xda-developers.com/nexus-4/help/nexus-4-computer-t3048983
---------- Post added at 08:53 AM ---------- Previous post was at 08:39 AM ----------
and here
http://forum.xda-developers.com/google-nexus-5/help/usb-fastboot-adb-driver-issue-t3055262/page2
Click to expand...
Click to collapse
Fastboot works fine -- when in the bootloader, my phone appears to be working just as normal. The connection is stable and fastboot can detect the device and flash to it as well.
I will try the cable and report back. Thank you for the tip!
Kind of late but if you are still experiencing the problem, try using USB 3.0 or 2.0 because I experience the problem too when I use the dedicated charging port on my laptop.
sent from Le Nexus 4
It turned out to be the cable that I had which was not good! I bought a stock Nokia cable, actually, which worked flawlessly (and charges at 820mA!!).
Good to know you've rectify the problem
from Le Nexus 4
Doggie52 said:
It turned out to be the cable that I had which was not good! I bought a stock Nokia cable, actually, which worked flawlessly (and charges at 820mA!!).
Click to expand...
Click to collapse
Excellent :good:
So I recently booted my Oneplus 5 into fastboot, just because.
And for some reason my device name is QC Reference Phone.... what the heck!
Has the factory QC phone somehow ended up being packed up and shipped out to me?
Can anyone else check their device and see if it says anything similar.
Got a pic?
I have same thing
Same for me.
same here and cant get fastboot working also can flash twrp
Same here and it is also strange that I can't connect with my windows.
- the cmd: Fastboot devices
doesn't return the serial number.
---------- Post added at 03:10 PM ---------- Previous post was at 03:00 PM ----------
hounter17 said:
same here and cant get fastboot working also can flash twrp
Click to expand...
Click to collapse
Did you already got an solution for your fastboot?
hmm wierd mine said the same
i can boot into fastboot
so i have allready unlocked oem an rooted
Unable to connect OnePlus 5 to windows 10, Fastboot reads phone as QC Reference Phone
I am having the same issue. Oneplus 5 is not being recognized as a valid USB device in windows 10.
In fast boot the device shows as a QC REFERENCE PHONE.
Please Help.....do i need a replacement ?
hounter17 said:
same here and cant get fastboot working also can flash twrp
Click to expand...
Click to collapse
didt u enable debug an oem in developer before u enter fastboot
Jonnyn93 said:
So I recently booted my Oneplus 5 into fastboot, just because.
And for some reason my device name is QC Reference Phone.... what the heck!
Has the factory QC phone somehow ended up being packed up and shipped out to me?
Can anyone else check their device and see if it says anything similar.
Click to expand...
Click to collapse
I am having the exact same issue...
Got the same problem. After some reboots and USB Debugging on/off the device was shown as a drive in Windows. Then there was a driver in this Drive. Installed. Problem solved. My Phone is shown as QC Reference Phone but Everything working great yet. (Fastboot, Sideload, USB Debugging, File Transfer)
When i connect my phone with te pc I hear te tone from recognizing or making contact ,but there is no drive visible as a folder in explorer. Ofcourse In die all settings in the developer options.
I'm missing the right driver. But I tried several.
Oneplus 5 showing up as Qualcomm HS-USB Diagnostics 900E
I got my OP5 today in the mail and the phone itself is working fine.
Although when connected to PC(Windows 10 64bit) it says "USB device not recognized". - Have already tried to set USB to MTP in developer Options.
And the device connected Reads "Qualcomm HS-USB Diagnostics 900E", did i receive a bricked Phone from the company ?
PLEASE HELP.
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Spider1996 said:
Got the same problem. After some reboots and USB Debugging on/off the device was shown as a drive in Windows. Then there was a driver in this Drive. Installed. Problem solved. My Phone is shown as QC Reference Phone but Everything working great yet. (Fastboot, Sideload, USB Debugging, File Transfer)
Click to expand...
Click to collapse
@Spider1996 :
This is my issue, any thoughts on that.
I got my OP5 today in the mail and the phone itself is working fine.
Although when connected to PC(Windows 10 64bit) it says "USB device not recognized". - Have already tried to set USB to MTP in developer Options.
And the device connected Reads "Qualcomm HS-USB Diagnostics 900E", did i receive a bricked Phone from the company ?
PLEASE HELP.
This was my Problem too. The normal USB Drivers from other devices are not working. Try to delete the driver in the device Manager from Windows and replug (with usb Debugging enabled and disabled) until a new drive is shown in Windows. After that install one of the .exe from this Drive. This helped me
---------- Post added at 04:45 PM ---------- Previous post was at 04:34 PM ----------
There are the Drivers from my Device Folder (Windows, Mac and Linux)
https://www.dropbox.com/s/nc7mgnj1k8kli92/OP5 Drivers.rar?dl=0
Try to use them for your OP5 in the device manager.
I think your device is not bricked/corrupted whatever
-fluffy- said:
didt u enable debug an oem in developer before u enter fastboot
Click to expand...
Click to collapse
yes i did it
I have the same thing. QC reference phone, no BL version or baseband version shown in fastboot mode. I also could not flash TWRP. I could fastboot reboot and see the device's serial # in fastboot but it wouldnt report the target size and errored out saying the file was too big for the target or something along those lines. I updated my ADB and fastboot EXEs just in case. What ended up working was switching USB ports on my laptop, despite the fact I use that one all the time and it was still recognized by fastboot. Hope this helps.
hibby50 said:
I have the same thing. QC reference phone, no BL version or baseband version shown in fastboot mode. I also could not flash TWRP. I could fastboot reboot and see the device's serial # in fastboot but it wouldnt report the target size and errored out saying the file was too big for the target or something along those lines. I updated my ADB and fastboot EXEs just in case. What ended up working was switching USB ports on my laptop, despite the fact I use that one all the time and it was still recognized by fastboot. Hope this helps.
Click to expand...
Click to collapse
just the same happend to me, so u finally flash the recovery and root or nay??
y try all the usb ports and nothing...
hounter17 said:
just the same happend to me, so u finally flash the recovery and root or nay??
y try all the usb ports and nothing...
Click to expand...
Click to collapse
I got the recovery to flash yes. It took me a while. It didn't stick because I didn't delete that file you have to delete but it flashed and booted into TWRP eventually.
hibby50 said:
I got the recovery to flash yes. It took me a while. It didn't stick because I didn't delete that file you have to delete but it flashed and booted into TWRP eventually.
Click to expand...
Click to collapse
so the only solution is to try in different usb plugs till it goes on someone?
wich file i must delete?
pritamk88 said:
I am having the exact same issue...
Click to expand...
Click to collapse
So maybe it isn't an issue, I'm not sure.
Oneplus replied "QC means qualcomm". So does this mean the phone is based off of a qualcomm reference board, and they just slapped it into a oneplus shell....