[Q] OTG Disabled recovery & phone salvation - One (M7) Q&A, Help & Troubleshooting

Hi there.
I recently (2 days ago) ran into issues with my 17 months old Htc One M7. The issue was something a bit different and unusual: First thing was that charging stopped working somewhere between the charge itselt. I noticed that I got reports that "Charging is disabled in USB host mode", even without any cable inserted into micro USB connector. Next thing that was really annoying was that the screen suddenly got orientation changes available even for calls and desktop, including on-the-head rotation (180°), basically it could go in any of the 4 orientations. The most anoying thing however was, the speaker was automatically turned on when call started.
At that time, I still had installed app Dayframe, which supports to run at Car mode, so all I noticed along with the upper issues was the prompt to "Choose which app you want to use to run" dialog every now and then.
After removing Dayframe, stock app started automatically, so I finally knew what was it - it was the CAR MODE!!! -.-
So, this explained a bit where the issue could be, and unfortunatelly, I can confirm that it's my worst fear: the usb connector has gone bad!
Since kernel doesn't support usb charging in otg mode, I couldn't charge my phone anymore - unless it was turned off. So wsaid, It detects otg / car mode randomly - mot of the time, so I ahave quite a big issue hereh
The big problem though is that I have had my phone rooted last year, using TWRP recovery (still have S-ON and stock rom 4.3, all I've done was gain root access in order to run some apps that needed it. Never tweaked the ROM itself...) . Now, since TWRP supports OTG mode, I can't connect my phone to the computer in any way, as, again, the usb connection is dropped as soon as I get into recovery.
One more issue at the moment is that I did the wipe all command, and haven't noticed that I marked "system" as well, so I currently don't have any OS installed at all^^.
Anyway, 3 big questions at the moment are:
1) Is there any way to get TWRP recovery or any other recovery with OTG disabled, so that I could connect it to the computer in order to proceed with unrooting before I send it for repair? I'm willing to donate/pay to someone to mod the TWRP(or any other) and recompile it for me, if that's an option...
2) Is it even possible to install another recovery from the current one, since I can't do ADB...?
Note: I still can get files onto the phone right now (ironic: thanks to the OTG) via my microUSB stick, so I can read zips. The question is, if the install is even possible at all...?
3) Is there any other way / what's your suggestion to do in my case???
I did check the usb connector from the outside and cleared it with a needle and compression, and don't see any corrosion, so have no idea how/why this happened....
Any help is more than appreciated!!

Put TWRP or other recovery img file in internal memory flash it with flash image gui app root needed

yatindroid said:
Put TWRP img file in internal memory flash it with flash image gui app root needed
Click to expand...
Click to collapse
Sorry, but your post makes no sense. First: I already gave TWRP. Second: I don't have OS installed anymore. Third: How would your suggestion help with my case? I'm afraid you misunderstood my problem... :/

cucolino said:
Hi there.
I recently (2 days ago) ran into issues with my 17 months old Htc One M7. The issue was something a bit different and unusual: First thing was that charging stopped working somewhere between the charge itselt. I noticed that I got reports that "Charging is disabled in USB host mode", even without any cable inserted into micro USB connector. Next thing that was really annoying was that the screen suddenly got orientation changes available even for calls and desktop, including on-the-head rotation (180°), basically it could go in any of the 4 orientations. The most anoying thing however was, the speaker was automatically turned on when call started.
At that time, I still had installed app Dayframe, which supports to run at Car mode, so all I noticed along with the upper issues was the prompt to "Choose which app you want to use to run" dialog every now and then.
After removing Dayframe, stock app started automatically, so I finally knew what was it - it was the CAR MODE!!! -.-
So, this explained a bit where the issue could be, and unfortunatelly, I can confirm that it's my worst fear: the usb connector has gone bad!
Since kernel doesn't support usb charging in otg mode, I couldn't charge my phone anymore - unless it was turned off. So wsaid, It detects otg / car mode randomly - mot of the time, so I ahave quite a big issue hereh
The big problem though is that I have had my phone rooted last year, using TWRP recovery (still have S-ON and stock rom 4.3, all I've done was gain root access in order to run some apps that needed it. Never tweaked the ROM itself...) . Now, since TWRP supports OTG mode, I can't connect my phone to the computer in any way, as, again, the usb connection is dropped as soon as I get into recovery.
One more issue at the moment is that I did the wipe all command, and haven't noticed that I marked "system" as well, so I currently don't have any OS installed at all^^.
Anyway, 3 big questions at the moment are:
1) Is there any way to get TWRP recovery or any other recovery with OTG disabled, so that I could connect it to the computer in order to proceed with unrooting before I send it for repair? I'm willing to donate/pay to someone to mod the TWRP(or any other) and recompile it for me, if that's an option...
2) Is it even possible to install another recovery from the current one, since I can't do ADB...?
Note: I still can get files onto the phone right now (ironic: thanks to the OTG) via my microUSB stick, so I can read zips. The question is, if the install is even possible at all...?
3) Is there any other way / what's your suggestion to do in my case???
I did check the usb connector from the outside and cleared it with a needle and compression, and don't see any corrosion, so have no idea how/why this happened....
Any help is more than appreciated!!
Click to expand...
Click to collapse
quite a long post, but I justy have a couple of questions for you, first of all, which version of twrp are you using ?
when your phone is in the bootloader and plugged into the computer, does it say fastbootUSB on the screen or something like fastboot host, are you still able to issue fastboot commands ?
when the phone is in recovery and you plug into the computer, check device manager, see if you can see the phone in their anywhere, ive noticed a lot of people loosing the device in recovery lately, me for one, if it says one with a yellow exclamation mark in device manager then you need to force the driver.

Seanie280672 said:
quite a long post, but I justy have a couple of questions for you, first of all, which version of twrp are you using ?
when your phone is in the bootloader and plugged into the computer, does it say fastbootUSB on the screen or something like fastboot host, are you still able to issue fastboot commands ?
when the phone is in recovery and you plug into the computer, check device manager, see if you can see the phone in their anywhere, ive noticed a lot of people loosing the device in recovery lately, me for one, if it says one with a yellow exclamation mark in device manager then you need to force the driver.
Click to expand...
Click to collapse
Thank you for your reply. Yeah, I have this thing for writting too much :/
I'm using twrp 2.6.3.0 if I read the version correctly.
When the phone is in the bootloader and plugged into the computer, it says nothing. Same as if I pull the cable out. The computer doesn't even recognize it. Sometimes I can hear the sound of new device connected, but only for a second or so., and this only happens during entering the recovery, not in the bootloader...
With ADB or Fastboot tool, I get no devices connected anytime I try to list them....
Unfortunatelly for me, here it's not the driver issue itself. It used to work with no issues - note that I have the same PC as I used for rooting it in the first place...

cucolino said:
Thank you for your reply. Yeah, I have this thing for writting too much :/
I'm using twrp 2.6.3.0 if I read the version correctly.
When the phone is in the bootloader and plugged into the computer, it says nothing. Same as if I pull the cable out. The computer doesn't even recognize it. Sometimes I can hear the sound of new device connected, but only for a second or so., and this only happens during entering the recovery, not in the bootloader...
With ADB or Fastboot tool, I get no devices connected anytime I try to list them....
Unfortunatelly for me, here it's not the driver issue itself. It used to work with no issues - note that I have the same PC as I used for rooting it in the first place...
Click to expand...
Click to collapse
but then you say the USB otg cable is working from within recovery ?
your recovery is a bit too old for flashing a rom, you really need 2.6.3.3, have you tried a different cable ?
I have seen this issue before, it was an option in a kernel that someone selected by mistake but for a different device, a HTC One SV, just going back 2 years so I cant remember the cure, however as you say your device is seeing the OTG cable and still charging even though it requires you to power off to do it, id say the USB port is fine, you could try flashing a custom rom which will replace the kernel on their now.

Seanie280672 said:
but then you say the USB otg cable is working from within recovery ?
your recovery is a bit too old for flashing a rom, you really need 2.6.3.3, have you tried a different cable ?
I have seen this issue before, it was an option in a kernel that someone selected by mistake but for a different device, a HTC One SV, just going back 2 years so I cant remember the cure, however as you say your device is seeing the OTG cable and still charging even though it requires you to power off to do it, id say the USB port is fine, you could try flashing a custom rom which will replace the kernel on their now.
Click to expand...
Click to collapse
Yes. I can see the OTG partition in the recovery present...
Tried a few cables, even took a brand new one out of the packet. It's not the cable issue...
But I can't understand how would I "select an option" in the kernel. Note, that I had stock ROM 4.3 with Sense 5.5, only root access gained, and have this firmware for over a year on now. Not a single app was installed/uninstalled within the last month, nor updated (I do all updates manually, and mostly don't except if I need them...), and this started to happen all of a sudden, out of nowhere.
I've read that someone had this issue (Found only one single thread about similar issue on some other forum, with no further info provided, but the guy described the exact same issues that I have), and that after taking it to the Sprint service, his warranty was revoked as they found corrosion on the usb connector...
Also, if I move a little bit up/down/left/right the cable, every 100 try I did lose the sign of the OTG host present in the system, but as soon as I released it, or took the cable back out, the message reappeared in the notification dialog...
Also, from what I know about OTG, I don't really see if you could be correct with the "usb port is fine" based on the fact that it does see OTG and charge. Note that the only difference between having otg and not having otg is linking the fifth (5th) pin to the ground.
By that, the system detects it as OTG host port instead of regular USB port, and switches charging off (as it redirects the current draw from inputing to outputing into the otg device, my guess is this is to avoid possible drawbacks and to control the actual current that the phone is outputing - otherwise you could damage the battery,...? ), , as well as turns the data pins to read OTG device instead present the phone itself as the device.
From that perspective, I believe that if the usb port is defective in such a way that it triggers the OTG, the charging will work only in powered off mode (as it does), and when powered on disable it as it "sees" otg device...
Do you have different info about OTG and disagree at any point with me? (I'd actually be glad to hear you do, if you do... )
The fact is that currently I can't do anything with the PC, as I can't see the phone at all. So, if my recovery is too old to flash rom, can I reflash new recovery from the current one, or do I explicitly need fastboot / adb for doing so?

cucolino said:
Yes. I can see the OTG partition in the recovery present...
Tried a few cables, even took a brand new one out of the packet. It's not the cable issue...
But I can't understand how would I "select an option" in the kernel. Note, that I had stock ROM 4.3 with Sense 5.5, only root access gained, and have this firmware for over a year on now. Not a single app was installed/uninstalled within the last month, nor updated (I do all updates manually, and mostly don't except if I need them...), and this started to happen all of a sudden, out of nowhere.
I've read that someone had this issue (Found only one single thread about similar issue on some other forum, with no further info provided, but the guy described the exact same issues that I have), and that after taking it to the Sprint service, his warranty was revoked as they found corrosion on the usb connector...
Also, if I move a little bit up/down/left/right the cable, every 100 try I did lose the sign of the OTG host present in the system, but as soon as I released it, or took the cable back out, the message reappeared in the notification dialog...
Also, from what I know about OTG, I don't really see if you could be correct with the "usb port is fine" based on the fact that it does see OTG and charge. Note that the only difference between having otg and not having otg is linking the fifth (5th) pin to the ground.
By that, the system detects it as OTG host port instead of regular USB port, and switches charging off (as it redirects the current draw from inputing to outputing into the otg device, my guess is this is to avoid possible drawbacks and to control the actual current that the phone is outputing - otherwise you could damage the battery,...? ), , as well as turns the data pins to read OTG device instead present the phone itself as the device.
From that perspective, I believe that if the usb port is defective in such a way that it triggers the OTG, the charging will work only in powered off mode (as it does), and when powered on disable it as it "sees" otg device...
Do you have different info about OTG and disagree at any point with me? (I'd actually be glad to hear you do, if you do... )
The fact is that currently I can't do anything with the PC, as I can't see the phone at all. So, if my recovery is too old to flash rom, can I reflash new recovery from the current one, or do I explicitly need fastboot / adb for doing so?
Click to expand...
Click to collapse
Is your phone Sprint ? 2.6.3.0 was very popular on Sprint.
their are still old roms you can flash with that recovery look for insertcoin-m7-5.0-3 it will work on Sprint

cucolino said:
Yes. I can see the OTG partition in the recovery present...
Tried a few cables, even took a brand new one out of the packet. It's not the cable issue...
But I can't understand how would I "select an option" in the kernel. Note, that I had stock ROM 4.3 with Sense 5.5, only root access gained, and have this firmware for over a year on now. Not a single app was installed/uninstalled within the last month, nor updated (I do all updates manually, and mostly don't except if I need them...), and this started to happen all of a sudden, out of nowhere.
I've read that someone had this issue (Found only one single thread about similar issue on some other forum, with no further info provided, but the guy described the exact same issues that I have), and that after taking it to the Sprint service, his warranty was revoked as they found corrosion on the usb connector...
Also, if I move a little bit up/down/left/right the cable, every 100 try I did lose the sign of the OTG host present in the system, but as soon as I released it, or took the cable back out, the message reappeared in the notification dialog...
Also, from what I know about OTG, I don't really see if you could be correct with the "usb port is fine" based on the fact that it does see OTG and charge. Note that the only difference between having otg and not having otg is linking the fifth (5th) pin to the ground.
By that, the system detects it as OTG host port instead of regular USB port, and switches charging off (as it redirects the current draw from inputing to outputing into the otg device, my guess is this is to avoid possible drawbacks and to control the actual current that the phone is outputing - otherwise you could damage the battery,...? ), , as well as turns the data pins to read OTG device instead present the phone itself as the device.
From that perspective, I believe that if the usb port is defective in such a way that it triggers the OTG, the charging will work only in powered off mode (as it does), and when powered on disable it as it "sees" otg device...
Do you have different info about OTG and disagree at any point with me? (I'd actually be glad to hear you do, if you do... )
The fact is that currently I can't do anything with the PC, as I can't see the phone at all. So, if my recovery is too old to flash rom, can I reflash new recovery from the current one, or do I explicitly need fastboot / adb for doing so?
Click to expand...
Click to collapse
you could of flashed a new recovery if you still had a rom on your phone, all I can suggest is that you try and flash an old'ish rom now from your OTG and current recovery.
The reason I think it was the kernel is because of all the strange orientation changes you were getting and the USB host problems, maybe an app messed it up or its just got corrupt or something, the rom has gotta be worth a try.

clsA said:
Is your phone Sprint ? 2.6.3.0 was very popular on Sprint.
their are still old roms you can flash with that recovery look for insertcoin-m7-5.0-3 it will work on Sprint
Click to expand...
Click to collapse
No. Its Unlocked, if Im not mistaken. (Bought in Central EU, no carrier locked, not Google Play edition,.... ?)
I should go and find an old rom somewhere, I'm sure its there on the net. But what do I gain with it anyway? If its kernel issue for sure, does the rom flash (stock one) reinstall the kernel as well..?
Seanie280672 said:
you could of flashed a new recovery if you still had a rom on your phone, all I can suggest is that you try and flash an old'ish rom now from your OTG and current recovery.
The reason I think it was the kernel is because of all the strange orientation changes you were getting and the USB host problems, maybe an app messed it up or its just got corrupt or something, the rom has gotta be worth a try.
Click to expand...
Click to collapse
Still though, if I don't get the usb connection back, I guess theres no way to remove the flags and put it back on S-On for repairas, is it...?
Well, I assumed that the orientation "issues" were enabled since the Car dock mode supports that. Was I wrong on this one..?
Note: Only 2 apps on my phone had SU access. File browser (ES file manager), and MyBackupPro. So only these two were actually able to mess with the kernel, if I'm not mistaken..?

cucolino said:
No. Its Unlocked, if Im not mistaken. (Bought in Central EU, no carrier locked, not Google Play edition,.... ?)
I should go and find an old rom somewhere, I'm sure its there on the net. But what do I gain with it anyway? If its kernel issue for sure, does the rom flash (stock one) reinstall the kernel as well..?
Still though, if I don't get the usb connection back, I guess theres no way to remove the flags and put it back on S-On for repairas, is it...?
Well, I assumed that the orientation "issues" were enabled since the Car dock mode supports that. Was I wrong on this one..?
Note: Only 2 apps on my phone had SU access. File browser (ES file manager), and MyBackupPro. So only these two were actually able to mess with the kernel, if I'm not mistaken..?
Click to expand...
Click to collapse
yes the Rom will fix the kernel
whats the top line in your bootloader M7_U / M7_UL / M7wls
your old roms are here >> http://insertcoin-roms.org/category/devices/one_m7/one_sense5/page/3/

clsA said:
yes the Rom will fix the kernel
whats the top line in your bootloader M7_U / M7_UL / M7wls
Click to expand...
Click to collapse
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMC-boot 2048MB
Oct 17 2013, 23:06:14.0 (Interesting date... and its always the same time.. -> I rooted the phone in Nov 2013, if I remember correctly...)

cucolino said:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMC-boot 2048MB
Oct 17 2013, 23:06:14.0 (Interesting date... and its always the same time.. -> I rooted the phone in Nov 2013, if I remember correctly...)
Click to expand...
Click to collapse
the roms in the link i posted will work fine on your phone IC 5.x = OS 3.x.401

clsA said:
the roms in the link i posted will work fine on your phone IC 5.x = OS 3.x.401
Click to expand...
Click to collapse
Thank you for that.
Downloaded, tried to install... seems like I have a bit of a more serious problem. Can't get to read the OTG drive anymore. Still shows as that some device is mounted, but the USB is not being recognized (tried 2 different, one directly OTG stick, and one via OTG cable..).
Looks like I'm totally f***ed.... :S

cucolino said:
Thank you for that.
Downloaded, tried to install... seems like I have a bit of a more serious problem. Can't get to read the OTG drive anymore. Still shows as that some device is mounted, but the USB is not being recognized (tried 2 different, one directly OTG stick, and one via OTG cable..).
Looks like I'm totally f***ed.... :S
Click to expand...
Click to collapse
Just a quick question, you said your phone was 17 months old, do you still have a warranty? I thought HTC's warranty was only valid for 1 year...

alray said:
Just a quick question, you said your phone was 17 months old, do you still have a warranty? I thought HTC's warranty was only valid for 1 year...
Click to expand...
Click to collapse
yep. theoreticallyninstill do. including the battery (since its integrated).
i dont know for foreign countries, at us, its 2 year...
Right now I have nothing to lose so i´ll give it a shot with our old twice-succeeded technique: 230V directly on the input to fry the board and usee have no idea why he woke up with a dead phone^^

cucolino said:
Sorry, but your post makes no sense. First: I already gave TWRP. Second: I don't have OS installed anymore. Third: How would your suggestion help with my case? I'm afraid you misunderstood my problem... :/
Click to expand...
Click to collapse
sorry Yes I misunderstood your problem
I attached a zip extract it you will find meta-inf + recovery.img (dummy file ) replace recovery file with whatever recovery you wanna flash with name recovery.img zip it flash it

Related

[SOLVED] No USB sync, only charge O2X

Ok Guys, I started this thread because last weekend I had an interesting issue with my O2X. From one day to another, whenever I connected my phone to the computer it only charged, I had no USB connection. I’m not yet quite sure why it happened, the last thing I did to my phone was install CM10 nightly of 31 October 2012, and then I changed the default baseband I had (725) to the one GetRil was telling me to install (LGP990AT-00-V20l-EUR-XX-OCT-20-2011 0_CP) (this baseband didn’t fixed the strange noises of in call) two days after that I got the no USB bug, at first I thought it was software related, then after lots of reading and trying different cables and computers I thought it was hardware related, but then I saw an interesting chance of fixing it, and it did in my case
Credit goes to Kohos, I manage to have USB fixed temporary thanks to his post on modaco.com
I’M NOT TELLING THAT CM10 CAUSE THIS BUG, IT JUST HAPPENED TO ME WHILE USING THIS ROM
Specs
Phone: Optimus 2x (p990H made in south Korea)
Rom: CM10 Oct 31 2012 (when got the bug) now CM7 nightly 15 July 2012
Kernel: Symbiosis 2.6.32.59 v1.2
Carrier: Telcel
Country: México
Ril: 0725 (V10d, Europe)
BB: 1035.21_20110725
CWM: 5.0.2.0 (no touch version)
To solve this issue you need to have a stock ROM that can be flashed by CWM. Can be the rom, or a backup of the stock rom (If you don’t have one send me a PM), I didn’t tried stock-based ROM so those may or may not work; I’m not sure but rather use an original stock ROM. You also need to be able to enter CWM recovery, and have LGE drivers up to date.
For this method I used a stock nandroid backup.
I’ll describe step by step all I did to solve this issue so you can give it a shot:
1. If you have a flashable stock rom you may skip this step and go to step 3, if what you have is a nand backup you need to make your partitions back from EXT4 to EXT3 (this is the format that stock rom uses) so need to download the tool R2 found on the first post here:
http://forum.xda-developers.com/showthread.php?t=1021549
put it on your external SD card along with the backup of the stock rom
2. Reboot to enter CWM recovery and install the tool R2 (NOTE: this will erase all information of the internal memory)
3. Install or flash your stock rom or backup (In case you're using my backup, keep in mind, my file IS NOT a flashable rom, it is a backup, so trying to use the option "flash zip from external sd card" WON'T work, what you need to do is unzip the file and put it on sdcard/clockworkmod/bakcup, then on the recovery, you have to use the option "restore from external sd card", that way it should work, keep in mind that if you change the name of the file it will give md5 error for the name won't match the backup's md5)
4. Reboot and start the phone, once it is all loaded, on the phone app dial: 1809#*990# this will take you to the service (hidden) menu (If it doesn’t take you automatically to the service menu (without clicking dial) you’ll need another ROM or backup)
5. In this menu you’ll need to scroll to the option: Module Test > USB Mode Selection, in there make sure the option LG Android USB is selected
6. Then go back to the root of the hidden menu, and go to Port settings, there you’ll see several options, the ones we’re interested in are: AP USB, CP USB, AP UART, CP UART, the default should be AP USB, you can start playing with those options. (While doing this, you might want to play with your computer device manager scanning for hardware changes, that might help detecting the USB)
The recommendation is to select CP UART, wait, if your problem is not hardware related, it should popup a message of new unknown device, or LGE Platfrom Android USB device. If your USB show some life signal, then you’re almost done, if not, keep playing with the four options until you see some life signal.
What I did was select CP UART, click Ok, wait, AP UART, click OK, wait, CP USB, click OK, wait, AP USB, click OK, I waited here about 1 min, and then on the computer device manager I scanned for hardware changes, and suddenly my computer started installing all drivers again, this last option is the one that must keep selected even with reboot of the phone.
7. Once you get all done, reboot the phone and connect it to USB to see if it is recognized again, if not, repeat steps 4 to 6
8. Ok, If everything went fine, you should now have USB connection, now I would recommend you flash your Stock Rom, so everything that might cause this bug gets fixed (if you don’t do this, you might get the bug back eventually). To do so you might need to turn off your phone and plug it to your computer while clicking PWR and VOl- at the same time, if your computer doesn’t recognize your phone, use the device manager and scan for hardware changes, this should reinstall the driver needed to make this happen.
9. Finally I restored my last nandroid backup through cwm
I did this on Monday, and two days later I had no USB connection again, I repeated this steps and I had USB detection once more, today it happended again, and repeated the steps so I’m pretty sure this fix should work every time.
NOTE: This is a temporary fix, I've been trying to identify why the bug keeps comming back
Hope this help you all get over this serious bug :laugh:
Updates
This is my last froyo teclel stock backup
http://www.4shared.com/zip/AEVLSE34/2007-02-01000516.html
http://dl.dropbox.com/u/7867872/2007-02-01.00.05.16.zip
Disclaimer: Even though I'm sure it will work, try it at you own risk, I'm not responsable for any bad behavior or damage that could happen to your phone
UPDATE:
Ok, guys I told you I would make some test to make sure the bug won't come back or identify the problem, what I've found so far is that the problem might be caused by the wall charger (but might not the the only reason), If I'm not wrong, the LG stock charger has output of 5.2V - 650mA DC and I've been using a motorola charger (5.1V - 850mA DC output).
Four days ago I started charging my phone only with my computer (usb port has output of 5V - 500mA) and I've had no trouble at all, the bug hadn't come back, today I charged my phone with the wall charger and the bug immediately came back, so for now that's my theory, the wall charger, stock or not, might fail and deliver more current that the O2X need so it mess the phone, I'm going to make fix on my charger to prove my theory, (I have no money for a new charger xD, but I'm studying electronics) if it fix it, I'll let you know, but you can try and charge your O2X with your computer for a day or two to help me prove my theory or prove me wrong
UPDATE:
It's been some time since I last posted here, I've been busy with my finals, but have had some time to make some tests to my phone. On my last update I told you that I had a theory about the bug, well, so far I can tell you that the wall charger indeed have something to do with the bug, but its not the cause of it, I've been using my wall charger letting my phone connected all-night long and the bug seems to happen again, but letting my phone connected to the PC for a while allows the USB sync and debugging again, so I'm not sure why it happens, I'm about to finish my finals so I'll try to make some tests once I'm done, hope this giude help you
UPDATE:
Well, as I was testing my theory, I go back to zero, this is because, my phone, doesn't have the bug anymore, so I have no chance to keep testing solutions for it, the conclusion I got with this is that the wall charger doesn't create the bug, maybe it triggers it, but not always nor on every device because, I haven't sopped using the same wall charger and the bug haven't returned, the last thing I did was, use my computer to charge my phone for three days, always letting it charge to 100% (unless I have to move from the computer) and the bug didn't happened, then, on a rush I had to use the wall charger, the bug appeared instantly, and then keep charging it with the same charger, two days after that, the bug dissappeared, I made no rom change, nor baseband, nor ril, nor anything, just like that it disappeared, so, I have no way to keep testing, if it ever comes back, I'll make some tests again, but for now, I have nothing to work with, hope this thread help you to get over this bug, at least, for a while, I'll be reading this thread in case you have some trouble with the instructions or so, cheers
UPDATE:
Ok, so I deleted long ago the last backup you told me was not working, and since I went to CM10 from Pengus I haven't had the no USB bug, so, one person asked me for the backup, I just made a new one, (this one is 204 MB on zip, read step 3) and uploaded it to 4Shared and Dropbox, so, remember to read and follow the instructions as they are, hope this time you can restore this backup, and one more thing, this backup was made just after installing it on the phone, so it doesn't have even a gmail account, you have to put yours and update market if you need something from there, ps. dont mind the date of the name of the file, it is innacurate, cheers
I don't have any stock ROM backup that I can flash via CWM, can I use this instead?
http://forum.xda-developers.com/showthread.php?t=1617458
To be honest I don't see a big difference to my post you probably found while searching except that your version is waaaaay more to read.
kohos said:
when dialing the above mentioned 1809#*990# in the Port menu, switching from default AP USB to AP/CP UART gave me life signs.
After switching to AP UART I linked the Unknown device driver to lgusbdiag.inf located in C:/ProgramFiles(x86)/LG United Mobile Driver.
Suddenly it started installing it and is now recognized as: LGE Platform Android USB Device.
Once disconnected I lose USB again, I'm able to recreate the first steps though even in default AP USB mode by now.
Click to expand...
Click to collapse
But that aside I hope you realize that this is not a solving fix at all. All it does is giving people who got a fresh device the chance to flash a custom recovery. That's all. It won't work with any CM ROM and even Stock based ROMs.
Unless you have an early Froyo version flashed you will also have no ADB and it won't be recognized during the NVFlash process rendering it pretty much useless.
Having seen dozens of people having this particular problem where all the super obvious stuff like other cables, other pcs, other drivers etc. did not work, sending it to repair was the only fix I heard of solving this problem to date.
Of course I'm very curious on how you are going to identify the problem. Good luck.
kohos said:
To be honest I don't see a big difference to my post you probably found while searching except that your version is waaaaay more to read.
But that aside I hope you realize that this is not a solving fix at all. All it does is giving people who got a fresh device the chance to flash a custom recovery. That's all. It won't work with any CM ROM and even Stock based ROMs.
Unless you have an early Froyo version flashed you will also have no ADB and it won't be recognized during the NVFlash process rendering it pretty much useless.
Having seen dozens of people having this particular problem where all the super obvious stuff like other cables, other pcs, other drivers etc. did not work, sending it to repair was the only fix I heard of solving this problem to date.
Of course I'm very curious on how you are going to identify the problem. Good luck.
Click to expand...
Click to collapse
I'm extremely sorry, there's one think I missed, give you credit (fixing that right away), I actually found your post on modaco.com, and tried to access to the hidden menu from CM7 with no success, fortunately, I do have an early froyo backup that can be flashed through CWM, the only thing is that is the Telcel stock rom (I don't know if this can work with other O2X devices, I think there should not be problem at all)
About ADB, it work in full with the latest drivers installed and scanning for hardware changes on the computer device manager, It even work entering the S/W update service on the phone (to install a stock rom)
I know that many people have had this issue, I spent a lot of time reading forums and stuff about it, the only post that actually helped me, was yours, so, credit is yours, I did this post to show people what I excactly did (that's why is a lot to read, but I wanted to make it as easy as possible to follow up)
To identify the problem is a long and slow task, so, I'll be making some tests and let you know what I found, right now I have no much time, 'cuz I'm about to start my final exams, so I'll be busy, but as soon as I finish I'll be more dedicated to it, I'll be making hardware and software tests but can't promise anything yet
vanmarek said:
I don't have any stock ROM backup that I can flash via CWM, can I use this instead?
http://forum.xda-developers.com/showthread.php?t=1617458
Click to expand...
Click to collapse
I tried to use that ROM, but couldn't manage to download it (I think it was removed, if you want to give it a shot try to find another flashable stock rom or backup, if not, give me some hours to clean my bakcup and upload it somewhere to let you use it, (it is mexico's telcel stock rom, but it should work)
Well Thanks ocr66 for this wonderfull news. I have the issue with usb connection from long time and i will give a try to your fix. You can post a stock rom here or a link to a rom that works??? In order to instal this fix i could lose the root??? Thank you 4 all!
vladutz9 said:
Well Thanks ocr66 for this wonderfull news. I have the issue with usb connection from long time and i will give a try to your fix. You can post a stock rom here or a link to a rom that works??? In order to instal this fix i could lose the root??? Thank you 4 all!
Click to expand...
Click to collapse
It all depends on what you install, if you manage to install stock rom through CWM or another recovery, yes you will loose root, but will have usb connection so you can root again, later today I'll upload my own froyo stock backup (it's mexican stock for telcel carrier, i think it should work out of méxico, maybe could cause network trouble on other countries, but its just a posibility, the important thing is that you be able to access the hidden menu), this backup I'll upload can be installed through cwm and its already rooted, so its like installing any custom rom, you'll keep your recovery and root
Remember, this is a temporary fix yet 'cuz I still get the bug comming back, maybe its because I am restoring my last working cwm backup, the only thing I haven't tried is clean all, install stock, root, install custom rom, and download again everything, maybe the bug is caused by something on that last cwm backup
I'll let you know as soon as I upload my bakcup
cheers
Well thank you! How i have this issue from one year i learned to live with her, but i could not live without root. So if i will instal a stock rom without root i will be unable to correct the usb connection i will get stuck with stock rom and no root. Will be the end of my phone. In am interesed to gain the usb connection for change the bb, i supose i can be something wrong with my bb 1035.21_20110725 and gingerbread. You can check to change the bb to see if you get again losing usb connection. Cheers and thank you 4 all.
got this after CM10 install
I've only had my phone for 1 day from new and already got this problem.
Rooted with superoneclick
Installed CWM v5.x
Installed CM10 Nightly Nov 13th
Now no USB mode, only charging.
baseband: v10e
RIL: CM10 1106
EDIT UPDATE: Well its working for me again now, I think in my case it was because I was using Linux and CM10.
By going to Settings/Storage then pressing menu button and selecting 'USB computer connection' I was able to change the 'Connect as' option from MTP to Mass storage and it now works.
@tiktok1 Lucky you!!!
@ocr66 Any news about this bug???
vladutz9 said:
@tiktok1 Lucky you!!!
@ocr66 Any news about this bug???
Click to expand...
Click to collapse
Actually yes, I've managed to identify what's triggering the bug at least in my phone, so might be the same for others as well, see the second post
BTW, did you tried already the fix? did you used my stock froyo backup?, if it didn't work, I can make another and upload it
Hi. Looks like I have the same problem with USB as you. Your theory about the wall charger might be correct. Here's my situation:
So, I've got my phone two days ago, bought used, came with a general Sony Ericsson USB charger. It says it outs 850mA at 5.0V (confirmed with a multimeter). The phone is on stock Android 2.2.2, isn't rooted yet. The guy from who I got the phone says that he suffered too with this kind of problem, however he got it working after 2 weeks without the use of the hidden menu. This means, that in those 2 weeks, he might have used a PC or a laptop to charge the phone. I tried the hidden menu port settings, however the only "working" mode is AP UART, but it is not recognizable by the PC, even if I try to link the LG drivers manually. Cycling through the modes did not help. I'll try to charge the phone with my PC, and see if that dose anything.
Details of the phone:
Firmware version: 2.2.2
Baseband: 1035.21_20110218
Kernel: 2.6.32.9-dirty
Build: FRG83G
LGE Version: LGEP990-V10b
Wow. All i can say is wow! Gosh! Just dunno how grateful I am stumbling upon this thread! Kudos to you sir,you just ended my 2 month long frustration about my phone not being able to communicate to my PC. was getting ready to send the phone for service then I read this. I had flashed every GB ROM imaginable from the dev thread with no luck. I am running carburano DM 1.7 now,all I did was to go to the hidden menu,switched one port setting,wait,then voila! PC recognized my phone! Again thanks,great respect to you,and Superskill.
Hi, this is my post to thebgeneral board by accident, didnt even read there was a qanda section lol
It didn't work on my gfs phone unfortunately, notvsure what was wrong.
Maybe I should try stock Rom instead of modded, how long are you guys waiting for the phone to show up?
I downloaded a stock Rom that had been modded.
So I could be sure that I would have cwm in case anything went wrong.
Rom loaded and was able to get into the secret menu.
I will say that under USB connection type there was misspelling where it said:
LG USB adnroid
Not sure if that would affect it.
I selected that item.
Then went to port.
Selected the different options in ordered and waited about 10 seconds on each turn, then pressed find any changes in device manager unplugged and plugged the USB.
Then tried in different orders but with not luck.
Took the battery out and tried holing the vol up down the plugging in USB but to no avail.
Then pressed power and vol down.
The phone tuned on and showed LG sign then switched off.
I tried pressing check any changes as the LG sign came on but nothing.
Then tried nvflash as the LG sign came on but nvflash showed no connection.
Very weird, definitely dead but still charges, doesn't make sense.
Oh well
Ordered an atrix with work and play kit for 68 quid, has a broken digitizer which will cost 20 pound, on average, off ebay.
Thanks for the help though.
May take the 2x apart when new phone comes and see if there's any physical damage on te board.
Sent from my LG-P990 using xda app-developers app
Sent from my LG-P990 using xda app-developers app
mondc1088 said:
Wow. All i can say is wow! Gosh! Just dunno how grateful I am stumbling upon this thread! Kudos to you sir,you just ended my 2 month long frustration about my phone not being able to communicate to my PC. was getting ready to send the phone for service then I read this. I had flashed every GB ROM imaginable from the dev thread with no luck. I am running carburano DM 1.7 now,all I did was to go to the hidden menu,switched one port setting,wait,then voila! PC recognized my phone! Again thanks,great respect to you,and Superskill.
Click to expand...
Click to collapse
Lucky you! I was to in DM 1.7 but when i was in hidden menu i chosing another port, don´t want to save the settings. Anyway congrats!
No luck...
I've used my PC for charging for a week now, still no USB connectivity. I think this might be a hardware issue with me as the phone sometimes says it's charging, but it's actually in my hands with no cable attached. I managed to root the stock 2.2.2 firmware with GingerBreak and installed CM7 with RomManager with a downloaded ZIP on the SD card. Thanks for the tips anyways.
Doctor0710 said:
I've used my PC for charging for a week now, still no USB connectivity. I think this might be a hardware issue with me as the phone sometimes says it's charging, but it's actually in my hands with no cable attached. I managed to root the stock 2.2.2 firmware with GingerBreak and installed CM7 with RomManager with a downloaded ZIP on the SD card. Thanks for the tips anyways.
Click to expand...
Click to collapse
Hello, I'm sorry it took me a while to answer, I've been busy with my finals, did you tired the tutorial I posted? the hidden menu modification? I know that you let your phone charging for a while with your pc, actually, it should've worked but, maybe the problem on your phone actually is something else, 'cuz I haven't had that issue that the phone says it is charging but its not connected to the charger, my brother told me that he have had that same issue but with other phone, he changed the wall charger and that "fixed" it, but I think if you haven't tried the tutorial, give it a shot, try changing to CP UART if your phone's usb is working as it should, your computer should detect a new unknown device, if not, myabe your phone is hardware damaged, hope you can fix your phone soon
cheers
monkeyass said:
Hi, this is my post to thebgeneral board by accident, didnt even read there was a qanda section lol
It didn't work on my gfs phone unfortunately, notvsure what was wrong.
Maybe I should try stock Rom instead of modded, how long are you guys waiting for the phone to show up?
I downloaded a stock Rom that had been modded.
So I could be sure that I would have cwm in case anything went wrong.
Rom loaded and was able to get into the secret menu.
I will say that under USB connection type there was misspelling where it said:
LG USB adnroid
Not sure if that would affect it.
I selected that item.
Then went to port.
Selected the different options in ordered and waited about 10 seconds on each turn, then pressed find any changes in device manager unplugged and plugged the USB.
Then tried in different orders but with not luck.
Took the battery out and tried holing the vol up down the plugging in USB but to no avail.
Then pressed power and vol down.
The phone tuned on and showed LG sign then switched off.
I tried pressing check any changes as the LG sign came on but nothing.
Then tried nvflash as the LG sign came on but nvflash showed no connection.
Very weird, definitely dead but still charges, doesn't make sense.
Oh well
Ordered an atrix with work and play kit for 68 quid, has a broken digitizer which will cost 20 pound, on average, off ebay.
Thanks for the help though.
May take the 2x apart when new phone comes and see if there's any physical damage on te board.
Sent from my LG-P990 using xda app-developers app
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
What I did on my phone is exactly what I posted, if your computer haven't detected your phone on CP UART I doubt rebooting will make a change, anyways the most important thing to see if your usb is damaged or not is to try on the hidden menu the option CP UART it almost instantly detect the device, but, not everytime, I once waited there 20 min, so, give it a shot if you want, the stock rom I posted (on second post) is Mexico's Telcel stock rom, rooted, it doesn't delete your cwm recovery nor root, you can give it a try if you want, but read the instructions 'cuz you have to restore the ext3 format of your phone's partition to make it work (it stays on boot loop if you don't restore ext3 format), if the backup doesn't work, let me know to upload a new backup, hope you can fix it
cheers
vladutz9 said:
Lucky you! I was to in DM 1.7 but when i was in hidden menu i chosing another port, don´t want to save the settings. Anyway congrats!
Click to expand...
Click to collapse
Hey did you managed to fix the problem yet? did you tried the bakcup I uploaded? it's Mexico's telcel stock rom, rooted, its made by cwm so it doens't delete your cwm recovery, give it a try if the backup doesn't work, let me know to make a new one and upload it ok?
cheers

Phone in USB Host Mode

Hello!,
I got my phone into a weird situation, every time I try to connect to my PC, it's saying "Phone is in USB host mode", the PC tries to recognizes and nothing happens, after that the phone won't charge and stays like that until I rebooted, I can charge it with the original charger after this.
My device:
HTC One AT&T 32GB
ROM: ARHD 41.0
I also tried this method with no results: http://forum.xda-developers.com/showthread.php?t=2481211
Anyone with this situation too?
lumogox said:
Hello!,
I got my phone into a weird situation, every time I try to connect to my PC, it's saying "Phone is in USB host mode", the PC tries to recognizes and nothing happens, after that the phone won't charge and stays like that until I rebooted, I can charge it with the original charger after this.
My device:
HTC One AT&T 32GB
ROM: ARHD 41.0
I also tried this method with no results: http://forum.xda-developers.com/showthread.php?t=2481211
Anyone with this situation too?
Click to expand...
Click to collapse
You mean it's showing up as QHSUSB_DLOAD in Device Manager?
Unfortunately that would indicate a hard brick, no fix, as far as I am aware of.
Welcome to the group of unfortunate people.
I guess the best option would be to send it back for warranty repairs, mine is the same and I'm 99.99% sure it has to do with the charging port.
Unfortunately for me I'm out of the US so warranty shipping is not an option at the moment.
There are other threads about this problem, but so far the only ones I heard that solved this problem was by repair or replace.
You mean it's showing up as QHSUSB_DLOAD in Device Manager?
Unfortunately that would indicate a hard brick, no fix, as far as I am aware of.
Click to expand...
Click to collapse
No, it's not bricked it works ok but only charges through wall charger and if you plug it up to a pc it gets into "USB Host Mode" and then you have to reboot to be able to charge from the wall charger.
My HTC showed the same message. Saying it can not charge into host mode.
HTC only charges powered off.
ferincr said:
Welcome to the group of unfortunate people.
I guess the best option would be to send it back for warranty repairs, mine is the same and I'm 99.99% sure it has to do with the charging port.
Unfortunately for me I'm out of the US so warranty shipping is not an option at the moment.
There are other threads about this problem, but so far the only ones I heard that solved this problem was by repair or replace.
No, it's not bricked it works ok but only charges through wall charger and if you plug it up to a pc it gets into "USB Host Mode" and then you have to reboot to be able to charge from the wall charger.
Click to expand...
Click to collapse
Indeed man, same situation here, I'm actually in Colombia, so not an option to send it, as I can't go back to factory settings without connecting it to the PC.
@nkk71 The device is fully functional, it's just not getting detected on my pc.
lumogox said:
Indeed man, same situation here, I'm actually in Colombia, so not an option to send it, as I can't go back to factory settings without connecting it to the PC.
@nkk71 The device is fully functional, it's just not getting detected on my pc.
Click to expand...
Click to collapse
What Windows version you running?
but be careful, QHSUSB_DLOAD mode is a brick... sooner or later
maybe best to get yourself an ubuntu live usb, and check adb and fastboot connections there. you can use this guide by @tobesedated to create a Live USB http://forum.xda-developers.com/showthread.php?t=2606577
maybe it's just bad/outdated windows drivers.
nkk71 said:
What Windows version you running?
but be careful, QHSUSB_DLOAD mode is a brick... sooner or later
maybe best to get yourself an ubuntu live usb, and check adb and fastboot connections there. you can use this guide by @tobesedated to create a Live USB http://forum.xda-developers.com/showthread.php?t=2606577
maybe it's just bad/outdated windows drivers.
Click to expand...
Click to collapse
I try with 3 different versions of Windows, on my jobI got Win 7, Win XP, and at home Win 8, same issue for all.
nkk71 said:
What Windows version you running?
but be careful, QHSUSB_DLOAD mode is a brick... sooner or later
maybe best to get yourself an ubuntu live usb, and check adb and fastboot connections there. you can use this guide by @tobesedated to create a Live USB http://forum.xda-developers.com/showthread.php?t=2606577
maybe it's just bad/outdated windows drivers.
Click to expand...
Click to collapse
lumogox said:
I try with 3 different versions of Windows, on my jobI got Win 7, Win XP, and at home Win 8, same issue for all.
Click to expand...
Click to collapse
Steps 8-15 of my guide show how to set up adb/fastboot in Ubuntu 32bit and to check if your device is recognized. You don't have to install Ubuntu just select to try it. I think that's what scares everyone off, is thinking they have to install the OS...It seems like a lot of work but it really isn't and compared to what you've gone through, it can't hurt....good luck
lumogox said:
I try with 3 different versions of Windows, on my jobI got Win 7, Win XP, and at home Win 8, same issue for all.
Click to expand...
Click to collapse
Win 7 and XP are pretty much OK with any drivers & hboot & firmware/rom, but what is it exactly showing you when you say "USB Host Mode"?
Have you considered uninstalling everything with HTC.... in control panel, and installing newer version: http://forum.xda-developers.com/showthread.php?t=2089508
then see if you get MTP (Media Transfer Protocol) working again.
USB Host Mode (as in Qualcomm High Speed USB Download Mode) is NOT a good sign! it's a brick about to happen.
maybe try changing the cable you are using to your PC!!!
EDIT: and make sure you're phone's USB port is not dirty or similar
nkk71 said:
Win 7 and XP are pretty much OK with any drivers & hboot & firmware/rom, but what is it exactly showing you when you say "USB Host Mode"?
Have you considered uninstalling everything with HTC.... in control panel, and installing newer version: http://forum.xda-developers.com/showthread.php?t=2089508
then see if you get MTP (Media Transfer Protocol) working again.
USB Host Mode (as in Qualcomm High Speed USB Download Mode) is NOT a good sign! it's a brick about to happen.
maybe try changing the cable you are using to your PC!!!
EDIT: and make sure you're phone's USB port is not dirty or similar
Click to expand...
Click to collapse
1. "Phone is in USB mode" appears as a notification on the phone when plugged to the computer.
2. Installed 3 different ROMs with the same result, uninstall everything, and nothing.
3. Don't know how to get back MTP.
4. Brick??
5. I try to charge it, but same thing happens.
6. Clean the port, and nothing.
lumogox said:
1. "Phone is in USB mode" appears as a notification on the phone when plugged to the computer.
2. Installed 3 different ROMs with the same result, uninstall everything, and nothing.
3. Don't know how to get back MTP.
4. Brick??
5. I try to charge it, but same thing happens.
6. Clean the port, and nothing.
Click to expand...
Click to collapse
let's take this down a notch, we dont care what your phone says, we care what shows up in Windows 7 Device Manager (or XP, maybe even Win8):
for example
I really haven't explored what steps are needed to get it back to stock, but mine connects to the pc as long as it's in bootloader so I can flash stuff like Fw but nothing that need to get into the sd card. (as far as I know).
nkk71 said:
let's take this down a notch, we dont care what your phone says, we care what shows up in Windows 7 Device Manager (or XP, maybe even Win8):
for example
Click to expand...
Click to collapse
Well, it's says nothing... doesn't appear anymore on Win 7 devices.
Try cleaning your USB ports?
Sent from my HTC One using Tapatalk
n1234d said:
Try cleaning your USB ports?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm thinking this a port issue, is damage somehow, however, I hope to find a software solution.
New Firmware
Phone that was purchased was not recognized by my computer in recovery and was locked with no S-Off and did not have a Super CID, but assuming that you have all of those things already and are developing these issues then I would try updating the firmware. For some reason, after flashing the 5.11.1540.9 firmware from http://forum.xda-developers.com/showthread.php?t=2485651 and updating to ARHD 71.1 the charging issue all has seemed to disappear. If anyone wants the full run down of how I got from my original non-functioning and unrecognized phone to where it is now I can put in details, but as far as I can tell the issue is just with the firmware if you find yourself being able to intermittently charge in different scenarios when it is off.
Loading New Firmware
Also, for some reason, computer would not recognize phone with TWRP recovery yet I could push files through adb when using CWM recovery. So what happened for me was loading up CWM and pushing the files that I needed into the data folder and flashing TWRP to then install it or rebooting the phone as normal and finding the file with something like a root file explorer. I feel like I may not be very clear with this so post if there needs to be more clarification.
it's a strange issue ,i think it is a hardware problem,happen to me and i try everything possible,without success,than i charge phone when power of and it was the only way ,but led was flashing so it was intermittent charging,i was able to charge only to 97%..i use my phone and somehow next day i was able to charge phone,but then problem occur again...and wired thing is that fastboot devices list is not empty but adb devices list is empty,so phone is not fully recognized by computer,and i forgot to say that day when i was able to charge phone,adb command worked...that day i flashed firmware recovery and rom again ,because i thought it will resolve the problem...
---------- Post added at 11:35 PM ---------- Previous post was at 11:23 PM ----------
ricehoshi said:
Phone that was purchased was not recognized by my computer in recovery and was locked with no S-Off and did not have a Super CID, but assuming that you have all of those things already and are developing these issues then I would try updating the firmware. For some reason, after flashing the 5.11.1540.9 firmware from http://forum.xda-developers.com/showthread.php?t=2485651 and updating to ARHD 71.1 the charging issue all has seemed to disappear. If anyone wants the full run down of how I got from my original non-functioning and unrecognized phone to where it is now I can put in details, but as far as I can tell the issue is just with the firmware if you find yourself being able to intermittently charge in different scenarios when it is off.
Click to expand...
Click to collapse
And do have same problem again after flashing new firmware?
The phone was a gift for my dad and it has been running fine since my last post. No charging issues and the phone does not go into host mode randomly anymore.
Well i also had the same problem...but i did factory reset on the phone and flashed it to completly stock ...and since then no problem..
Sent from my HTC One using XDA Free mobile app

[Q] HTC One not seen by computer

For some months my HTC One has not been seen by my PC.
I also cannot use my OTG cable.
I have tried reinstalling the HTC drivers,
Connecting to different PCs
searching for a solution
but I can't access the HTC One, use fastboot, etc.
I have a workround for adding or working on files by using wireless connection in MyPhoneExplorer.
I cannot get S-OFF or (I think) replace the Radio, and I suspect the problem may lie there, unless it is a hardware problem, in which case I'll live with it. I did install a 3G only App which caused a few problems, but I can't relate the problem directly to that, as I did not notice at that time.
In case the Radio change would help, can anyone direct me a way to
a) replace radio without S-OFF, OR
b) get S-OFF without fastboot, connection to PC etc.
c) advise another approach
Thanks in advance
Alex
HTC One M7, international
Viper One 5.7
ElementalX 13.0
What is your hboot version and what OS are you running on your PC?
ukmaps4us said:
For some months my HTC One has not been seen by my PC.
I also cannot use my OTG cable.
I have tried reinstalling the HTC drivers,
Connecting to different PCs
searching for a solution
but I can't access the HTC One, use fastboot, etc.
I have a workround for adding or working on files by using wireless connection in MyPhoneExplorer.
I cannot get S-OFF or (I think) replace the Radio, and I suspect the problem may lie there, unless it is a hardware problem, in which case I'll live with it. I did install a 3G only App which caused a few problems, but I can't relate the problem directly to that, as I did not notice at that time.
In case the Radio change would help, can anyone direct me a way to
a) replace radio without S-OFF, OR
b) get S-OFF without fastboot, connection to PC etc.
c) advise another approach
Thanks in advance
Alex
HTC One M7, international
Viper One 5.7
ElementalX 13.0
Click to expand...
Click to collapse
I assume it still charges, so usb is at least partially working. Interesting that OTG doesn't work any longer, would seem to point to usb on device rather than PC. There are several threads regarding folks cleaning usb connector, have you tried?
What is your hboot version and what OS are you running on your PC?
Click to expand...
Click to collapse
hboot 1.44 0000
Only have Windows 7 machines.
I assume it still charges, so usb is at least partially working. Interesting that OTG doesn't work any longer, would seem to point to usb on device rather than PC. There are several threads regarding folks cleaning usb connector, have you tried?
Click to expand...
Click to collapse
I've looked with a magnifier and blown into it, but nothing apparent seen. Tried multiple USB connectors.
It does charge correctly. The USB notification does sometimes stay on even when not charging though, forgot about that.
hboot 1.44 can be done with rum runner. I still use hansoon's toolkit to bad its not here anymore. I would recommend running RUU it should fix your issue's.S-OFF first and theres no need to relock bootloader when s-off to run RUU. Have you tried wiping data in recovery????? S-off cannot be done with a pc nor can radios be flashed. your problem most likely is tied to the system since no pc recognizes it.Also try changing recoveries.
hboot 1.44 can be done with rum runner. I still use hansoon's toolkit to bad its not here anymore. I would recommend running RUU it should fix your issue's.S-OFF first and theres no need to relock bootloader when s-off to run RUU. Have you tried wiping data in recovery????? S-off cannot be done with a pc nor can radios be flashed. your problem most likely is tied to the system since no pc recognizes it.Also try changing recoveries.
Click to expand...
Click to collapse
I think Rumrunner and run RUU needs fastboot working.
I've done several wipes and reset to factory..
The USB controller in Device manager shows nothing in Universal Serial Bus Controllers but an old Samsung Android phone shows Samung Android USB composite device. On another computer it shows up on Other Devices.
I assume mine should show HTC device when the USB notification is on but it doesn't, so the phone knows about the USB but a pc doesn't. Weird?
I have tried 3 recoveries recently that didn't get the phone recognised, but as I'm on Viper I'll stick with TWRP for now, as the last recovery didn't want to go away.
Mine only shows as android device until I 2x click it. Then I see my HTC drivers. Hope you get it fixed.
Sent from my unknown using Tapatalk
Unplug your device from PC.
Uninstall HTC Sync Manager.
Install HTC Sync Manager.
Plug your phone into PC.
Unplug your device from PC.
Uninstall HTC Sync Manager.
Install HTC Sync Manager.
Plug your phone into PC.
Click to expand...
Click to collapse
I have tried this several times, on more than one PC. Doesn't seem to be the answer.
I can update on one item. I have been trying to find out what software I installed which might have caused it or made it worse. When I installed Stickmount, a helper for OTG, and then uninstalled it I found that my device again recognises the OTG cable on the notification bar, but the power light on the stick or adapter does not power up, and I can't see files.
This might have pointed to a failed power connection on the USB connector, although charging indicates and works ok?
The power and ground must connect, and also the host signal. Perhaps one of the 2 data connectors is faulty on the micro USB connector, which might explain everything?
Same problem here. Did you solve it ?
I had a sense 7 custom rom than i flashed CM 12.1 and that problem still continues

USB not working as expected under custom ROMs

Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Marco2G said:
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Click to expand...
Click to collapse
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
danarama said:
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
Click to expand...
Click to collapse
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Marco2G said:
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Click to expand...
Click to collapse
Haha, no worries. Sometimes it is hard to see the wood for the trees.

No USB recognition at all, HELP.!

Hi, firts of all sorry for my english.
My sister give to me a BLU R1 HD 2GB RAM/16 ROM, it come without Amazon ads (so i think its OEM version). Its running BLU_R001UU_V21_GENERIC.
She told me that one day just not was recognized by PC to transfer files,photos, music. I make a wipe from recovery and still the problem no USB detection at all just charging, no sounds like new USB device was conected, no device on Device Manager.( i do this on diferents PC Windows 10, Windows 8, and Linux Elementary OS , Deeping OS)
I enable Developer Options and change MTP/PTP/Only Charge option and nothing happened; I opened the device to check the pins on the USB connector and check continuity and all seem like be perfect.
I thing that may be when was update to the last software something happen and lost USB recoginition, I want to Root the device and change Recovery but i see that the steps need connect the R1 HD to PC and make some things throw ADB console.
My question is: can i downgrade the original rom from SDcard in the actual Recovery.. to try recover the USB functions. or may be its something wrong on any internal chip that no make the USB conection.
Ty.
mykrov said:
Hi, firts of all sorry for my english.
My sister give to me a BLU R1 HD 2GB RAM/16 ROM, it come without Amazon ads (so i think its OEM version). Its running BLU_R001UU_V21_GENERIC.
She told me that one day just not was recognized by PC to transfer files,photos, music. I make a wipe from recovery and still the problem no USB detection at all just charging, no sounds like new USB device was conected, no device on Device Manager.( i do this on diferents PC Windows 10, Windows 8, and Linux Elementary OS , Deeping OS)
I enable Developer Options and change MTP/PTP/Only Charge option and nothing happened; I opened the device to check the pins on the USB connector and check continuity and all seem like be perfect.
I thing that may be when was update to the last software something happen and lost USB recoginition, I want to Root the device and change Recovery but i see that the steps need connect the R1 HD to PC and make some things throw ADB console.
My question is: can i downgrade the original rom from SDcard in the actual Recovery.. to try recover the USB functions. or may be its something wrong on any internal chip that no make the USB conection.
Ty.
Click to expand...
Click to collapse
I have not seen any other reports of usb dying after OtA update. You say you tried with different PC, what about using different usb cable?
But more bad news for your plans. If you have official v21 update, then you are not rootable anyway.
mrmazak said:
I have not seen any other reports of usb dying after OtA update. You say you tried with different PC, what about using different usb cable?
But more bad news for your plans. If you have official v21 update, then you are not rootable anyway.
Click to expand...
Click to collapse
I tried with diferents usb cables, and nothing happened.
mykrov said:
I tried with diferents usb cables, and nothing happened.
Click to expand...
Click to collapse
Do you know if any of them are sync cables??
codyalan said:
Do you know if any of them are sync cables??
Click to expand...
Click to collapse
They are USB cables that i use on others phones (lg 4x HD and Honor 6X) and work fine with those phones but not on my R1Hd
mykrov said:
Hi, firts of all sorry for my english.
My sister give to me a BLU R1 HD 2GB RAM/16 ROM, it come without Amazon ads (so i think its OEM version). Its running BLU_R001UU_V21_GENERIC.
She told me that one day just not was recognized by PC to transfer files,photos, music. I make a wipe from recovery and still the problem no USB detection at all just charging, no sounds like new USB device was conected, no device on Device Manager.( i do this on diferents PC Windows 10, Windows 8, and Linux Elementary OS , Deeping OS)
I enable Developer Options and change MTP/PTP/Only Charge option and nothing happened; I opened the device to check the pins on the USB connector and check continuity and all seem like be perfect.
I thing that may be when was update to the last software something happen and lost USB recoginition, I want to Root the device and change Recovery but i see that the steps need connect the R1 HD to PC and make some things throw ADB console.
My question is: can i downgrade the original rom from SDcard in the actual Recovery.. to try recover the USB functions. or may be its something wrong on any internal chip that no make the USB conection.
Ty.
Click to expand...
Click to collapse
I have the exact same issue... and it happened just after an OTA Update. After that it showed it was charging only when the phone was shut down.
No USB recognition whatsoever. PC/Mac. Tried several cables.... All USB modes... Factory Reset... Nothing made it work.
I contacted BLU with the issue. As soon as I have an answer (If ever) I will let you know.
If any of you know anything about this please share it here.
Oddly enough, After a cache wipe and factory reset, I have no ads on the lock screen. The app is running on the background but nothing shows up.
elcarmi said:
I have the exact same issue... and it happened just after an OTA Update. After that it showed it was charging only when the phone was shut down.
No USB recognition whatsoever. PC/Mac. Tried several cables.... All USB modes... Factory Reset... Nothing made it work.
I contacted BLU with the issue. As soon as I have an answer (If ever) I will let you know.
If any of you know anything about this please share it here.
Oddly enough, After a cache wipe and factory reset, I have no ads on the lock screen. The app is running on the background but nothing shows up.
Click to expand...
Click to collapse
I think if we can downgrade to a official rom under the actual recovery maybe that fix the USB. But all methods are under USB connection to PC.
mykrov said:
I think if we can downgrade to a official rom under the actual recovery maybe that fix the USB. But all methods are under USB connection to PC.
Click to expand...
Click to collapse
As far as I know downgrading is not possible without making the phone unusable. If by any chance that is possible maybe an update from an SD Card can work.

Categories

Resources