Hi,
My girlfriends tablet HTC Flyer has craked screen, and touchscreen is not working. Tried to plug in the OTG solution, but its not working at all.
Whenever I plug the usb to PC, it shows that device is not recognized. I have already installed ADB, but command ADB Devices does not give any results. So i can't go any further that way. But maybe there is other solution that you know? Tried lot of things already, and I'm slowly running out of ideas what to do. Whenever I plug the usb when in recovery mode (Power and volume down) there is text saying HBOOT USB PLUG, after couple minutes it changes to normal HBOOT.
Related
Hi all... i got my V for a month and now it is not charging anymore. neither from the ac adapter nor my computer usb..and my computer couldnt detect my phone is plug to the USB port....just nothing pops out. The debugging mode status icon, and the storage icon is not shown on my phone.
basically... i tried everything i found on Google...
reboot my phone, pop out the battery, change cable[from other optimus V], changed battery, different ports on my computer, different computer, different AC adapter, different SD card, format my SD card, factory reset, and the last thing i tried is to rooted my phone and flash with a I.H.O CM7.1 ROM.
no hope at all; however, when i plugged to the usb port or the ac adapter, then i take out the battery.. the phone does power up and say required battery....
so, if anyone had this problem before and solved it.. please help me out. between, i cant return the phone anymore.. it is over a month.
forgot to mention... it is the second time this charging issue happened. the first time, it fixed itself after i plugged into the PC, windows recognized it, and installed the drivers. [well, i already installed the driver before this happened, because i was doing some coding and debugging]
this time.... windows is doing nothing, no message pop out, no new driver found.. just nothing. and my phone doesn't shows the debugging icon on the status bar even thought i ticked the debugged mode On, and connected to the usb.
sorry for my bad grammar =[
maybe see if your pc recognizes it while rebooted into recovery.
you could also try removing all the lg and Android drivers in device manager (select show hidden devices to get at them) and then plugging the phone into the pc again.
or use a Ubuntu "live cd" to check the connectability... micro$oftware is uppity, my kid's windoze computer doesn't like my v, although it used to see it fine.
I've also read that toggling debugging, disconnecting and reconnecting the cable, then toggling usb debugging again can help.
also, froyo roms are supposed to go to a charge mode when turned off but still plugged in.
I tried to make the internal memory swap adb method found on the forum, but the command adb devices stuck. I tried to restart and nothing, I removed the power cord and still not finished, I removed the USB cable and so died. I put the power cord back but never lit, illuminates only when connecting the USB cable, I managed to get into recovery mode, I managed to install firmware restarted and the screen remained black. the idea is that it is powered only by the USB port, which led me to do? has anyone happened to that? Thank you!
I have been running on Cooks I777UCMD8 rom for about 2 months now and have had multiple powering issues. Have tried all the basic trouble shooting, not sure if its the Rom causing the issues or the AJK noswap Kernel, but nothing has been tweaked, running as is. The booting issue is when connecting a USB cable while the phone is powered off, if you try to turn the phone on while the USB cable is still attached you get a POWER RESET OR UNKNOWN UPLOAD MODE error message, only way to avoid it is to remove the usb cable and hold power button then it powers up normally.
now the problem with the USB cable, and i feel these two are possibly related, my phone no longer recognizes when its attached to a computer usb hub, it charges, but dose not enter into mass storage mode, nor does the computer recognize that the phone is attached, i have tried on multiple computers with same results, and yes all drivers are downloaded on computers. Further information; Before this problem began accruing, I would get error messages after attaching the phone to a pc VIA usb cable saying ( ONE OF THE USB DEVICES ATTACHED TO THIS COMPUTER HAVE MALFUNCTIONED, AND WINDOWS DOES NOT RECOGNIZE IT ) also, after plugging in the usb cable and windows attempted to download the drivers this error also appeared ( DEVICE SOFTWARE WAS NOT SUCCESSFULLY INSTALLED, CONSULT WITH YOUR DEVICE MANUFACTURER FOR ASSISTANCE ) it later resolved itself for a short time ( couple days ) but now when i connect the phone, nothing happens... i'm hoping somebody has had similar USB problems after flashing a new rom and knows whats going on.
additional information:
- i have two Galaxy S2 phones both running cooks-i777ucmd8 rom and both phones have had the exact same issues.
- previous problems also include boot looping, and frozen lock screen upon powering up the phone. has not happen in a while.
I just got the phone today. i unlocked it with the ASUS-provided tool. No problems. I enabled developer mode and USB debugging, no problem. I can see the device when I connect it to my PC and type "ADB Devices". No problem there.
My problem is when I enter FASTBOOT mode (vol-up + power). If I connect the phone to my PC and type "fastboot devices" it comes up blank.
I tried multiple versions of ADB/Fastboot, and multiple cables and ports on multiple computers. The ROG phone just isn't recognized by fastboot (My old Pixel XL is recognized by Fastboot on the same PC).
Does anybody know why the ROG Phone isn't being picked up by fastboot when adb works fine on the same machine?
[UPDATE 1]: I also updated my USB driver and the device is in Device Manager as ASUS ADB Android Device when plugged in as USB debugging. When in Fastboot mode, the device does not show up in Device Manager at all.
It might not return anything but maybe it could execute commands. I think you want to flash TWRP am i correct?. If so try to run the commands and see if it executes them. I am also facing the same issue but i haven't unlocked my bootloader yet and i have no plans to do it yet.
Update: It seems my laptop doesn't detect my phone in fastboot mode also. If you go to the device manger window nothing changes when you connect your device to the computer/laptop. Could this has to do with me not unlocking the bootloader yet.
This is not the case with my Nexus 6p, when i am in the bootloader mode my laptop detects it fine and it shows a bootloader interface driver in the device manger window. which is obviously not the case for the ROG phone.
By the way when my Asus is on and connected it detects it by its name "ASUS_Z01QD" and not "ASUS ADB Android Device".
Thanks for the reply. Seems we're more or less in the same boat. I guess I'll hang tight until someone smarter than I am posts a step by step rooting guide. Till then, no Fastboot and no TWRP, it seems.
I was able to get fastboot to detect. I plugged the cable into the side USB slot, not the bottom.
When I plug it into the bottom, my device is not detected either.
I am using a USB-A to micro-USB cable with a micro-USB to USB-C adapter.
When I get home, I'll check if the USB-C cable that came with the device works with fastboot when plugged into the side slot.
I contacted ASUS support, and they said to use the USB-C port on the side of the phone. Don't I feel dumb. The only thing I didn't try.
This happens on my rog 3 too.. debug detects on my bottom side. But it only charges on my side port.. any help pls?
So i got it to work. It was my cable problem lol.. all good now and im back to my lovable Android 10!
OK so i was also stucked and nothing seems to be work i put the cable at the side port but same no detection i tried change cable nothing works...
simple is put cable on side and restart bootloader **** this is real works ... lol hit
gimme a like if it works for u too
I was having the same issue. Was thinking I was going to have to start troubleshooting with different cables and computers but just changing to the side port actually worked. Wouldn't have thought of that on my own. I made an account here just to say thank you to this multi year old thread lol.
I seem to have gotten my N200 in a state where it will not power on. No screen display, no vibrations, and unresponsive to volume and power buttons (standalone or combination). It's a DE2118, T-Mobile variant, network locked and not rooted.
Here are the conditions leading up to it:
The phone was plugged in to my PC via USB, (through a USB hub).
My Sim/SD tray was ejected.
I had been using an ADB shell to disable-user some apps and check out some various PM commands.
I did not terminate the ADB shell before powering down from the phone.
Once powered off, I held the volume up+volume down+power buttons to attempt to check out the recovery mode. I've never entered recovery mode before on this device.
The USB cable was still plugged in and I could hear the USB new device sounds on my PC a few times while I did this but didn't think anything of it.
Nothing ever appeared on the screen and pushing any of the buttons seem to provide no response.
Battery usage was at least 80%, if not closer to 90% before this happened.
It almost seems like the device is powered on and running as there feels like there's some very slight warmth on the back panel, near the center just under the camera area but I might just be imagining the warmth.
I'm aware that it needs to be network unlocked before it can be rooted as per other threads and I have not tried any root methods.
I still have my ADB shell dialog up but there really isn't much interesting in it besides a lot of the command help dialog.
What are my options?
Note: I recently installed the Jan 6th android 11 security update maybe a day before.
Edit: For anyone looking at this later, the phone came back after a complete battery drain and partial recharge and I was able to replicate the bricked state performing the same thing, usb debugging on, plugged in to usb hub on pc, shut down phone, then holding all 3 buttons down for a while.
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
mthous01 said:
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
Click to expand...
Click to collapse
I'm using Windows 7 mainly.
It shows up in device manager when I plug in the USB but with error code 28, unknown driver.
In Win7, "adb devices" lists a blank line for devices.
In Linux, "adb devices" lists a blank line for devices.
In Linux, "fastboot devices" has no output at all.
If your phone is showed in device manager you should be able to give him his life back...had the same situation long time ago with my oppo find 7..
Try this, and see if it'll recognize you for MSM download.
mthous01 said:
Try this, and see if it'll recognize you for MSM download.
Click to expand...
Click to collapse
Will give it a try. Going to be a few hours to DL the file as I'm on an extremely slow connection atm.
Well, I think that made it worse. Couldn't get the Qualcomm CAB drivers working on Windows 7, but got it through Windows Update. The MSM tool went through the process fully but afterward I unplugged the device and tried to boot, still no response, nothing on screen, no vibration. Now when I plug my device back in to the USB, I have an endless new usb device noise and windows says "Unknown Device". Device manager refreshes constantly while its plugged in. Looking back I should have probably tried ADB first before running the MSM tool.
After almost 24 hours of being unplugged, I tried plugging it in again and it finally had some signs of life with the low battery warning and then TMobile splash screen+vibration+sound after about 5 minutes. Still waiting on it to charge up for now. Probably just needed to be power cycled in the end instead of attempting to flash anything. I sure do miss the days of removable batteries.
Mtrlns said:
Probably just needed to be power cycled in the end instead of attempting to flash anything.
Click to expand...
Click to collapse
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
lzgmc said:
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
Click to expand...
Click to collapse
I had tried that yesterday to no avail. Was very strange. Everything seems to be working as normal now, though factory reset from running the MSM tool. I'm wondering if I'd be able to duplicate the issue again.
Could not replicate with USB debugging off and plugged directly in to my PC's USB port, but turning on USB debugging and plugging in to my USB hub, shutting down the phone, and then power cycling with all three buttons brought the same bricked state.
Don't know for sure if the USB port matters but while bricked plugging in to the USB hub always gives a USB device error sound. Going directly on PC it connects fine as a new device (as QUSB_BULK without drivers or Qualcomm HS USB QDLoader 9008 with drivers). ADB/Fastboot commands from PC's command line don't seem to do anything.
I did notice the fastboot menu show up on screen for a second when power cycling this time and I don't recall it appearing the first time. I think i may have had "advanced reboot" turned on the first time, while it was off this time.
Powercycling actually reset it this time.
Possible solution
It would seem that you can force MSM to write both a and b slots, which might fix your issue. Might be worth a shot
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
Just had the same problem. Holding all buttons for 30 seconds worked.
if you bricked it and you have tmobile variant you can restore it weather you have a locked or unlocked bootloader.
you have to get your phone in EDL mode, once in EDL mode you will see the "QUSB_BULK_CID" in device manager. you will then need to install qualcomm drivers (if done manually you will have to endable windows test mode, if you use the qualcomm USB driver installer then it will do it for you and you will be in test mode upon next windows reboot.) Reboot windows in TEST MODE. NOTE: i said WINDOWS TEST MODE... Once in windows test mode the driver should function and look normal in device manager. From there just open the MSM tool for your version of Nord N200 and flash and wait about 3-5 minutes. Reboot the phone and you are back in Oxygen OS.
Tips and extra Files needed below:
for the tmobile NORD N200 MSM tool
Index of /list/Unbrick_Tools/OnePlus_Nord_N200
The installer for the QUALCOM USB drivers can be found here at this website (ONLY use the QUALCOMM drivers from here, do not use any other file as it is for a different phone):
droidwin.com/unbrick-oneplus-7-pro/
once done unbricking and restoring your phone you can then exit windows test mode by running
bcdedit -set TESTSIGNING OFF
at the windows command prompt as ADMINISTRATOR.