Related
Hi there,
Rooted my phone yesterday, downgraded from HBoot 2.00 to 1.13 using Nonverbose's script and then used Revolutionary to get S-OFF and then finally flashed Virtuous Quattro RC3 as well as the latest Tiamat kernel.
Works fine, just the phone won't charge if it's switched on. I have to power off for it to charge at all.
I know it's not a ROM problem, because I've tried both Quattro and IceColdSandwich, and neither will charge, and I'm quite sure it's not the cable, as it obviously works when powered off. I have also tried two other cables and one wall charger.
I've tried reflashing the kernel, doing Davlik cache wipes etc. Also checked the battery for bent pins, and it seems fine.
Is there any diagnostic check I can run to see if the battery is faulty etc? Or something I forgot while rooting/flashing?
Thanks in advance,
Larry
larryorsomething said:
Hi there,
Rooted my phone yesterday, downgraded from HBoot 2.00 to 1.13 using Nonverbose's script and then used Revolutionary to get S-OFF and then finally flashed Virtuous Quattro RC3 as well as the latest Tiamat kernel.
Works fine, just the phone won't charge if it's switched on. I have to power off for it to charge at all.
I know it's not a ROM problem, because I've tried both Quattro and IceColdSandwich, and neither will charge, and I'm quite sure it's not the cable, as it obviously works when powered off. I have also tried two other cables and one wall charger.
I've tried reflashing the kernel, doing Davlik cache wipes etc. Also checked the battery for bent pins, and it seems fine.
Is there any diagnostic check I can run to see if the battery is faulty etc? Or something I forgot while rooting/flashing?
Thanks in advance,
Larry
Click to expand...
Click to collapse
Ics roms are always bit laggy atm. Quattro isn't made to use with tiamat. Icecoldsandwich 7 dont needs tiamat cause the stock kernel ist better optimized for it. Try a stock sense, miui or cm7 rom. If this doesn't suit too i think your usb port is in yhe ansroid heaven.
Sent from my HTC Incredible S using xda premium
Silversniper said:
Ics roms are always bit laggy atm. Quattro isn't made to use with tiamat. Icecoldsandwich 7 dont needs tiamat cause the stock kernel ist better optimized for it. Try a stock sense, miui or cm7 rom. If this doesn't suit too i think your usb port is in yhe ansroid heaven.
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
Okay, I'm going to install CM 7.2 RC1 today. When I flash the ROM, do I have to flash another kernel or will Tiamat get lost automatically? Where can I find a download for the stock kernel?
Thanks!
Stock kernel will be included within the rom anyway. So don't worry.
Sent from my Incredible S using xda premium
You can transfer files while connected via USB?
I installed CM 7.2 by loading it onto the MicroSD card via a cardreader, because I couldn't get my phone to mount storage on my PC (I kept getting the 'device malfunctioned' message). I can't find the setting to enable disk drive mode, or battery info, can anyone help with this?
Actually, I've got it on now, and I just saw it go from 'Charging (9%)' to 'Charging (8%)', the same as the other roms.
I guess it's the microUSB port?
larryorsomething said:
I installed CM 7.2 by loading it onto the MicroSD card via a cardreader, because I couldn't get my phone to mount storage on my PC (I kept getting the 'device malfunctioned' message). I can't find the setting to enable disk drive mode, or battery info, can anyone help with this?
Actually, I've got it on now, and I just saw it go from 'Charging (9%)' to 'Charging (8%)', the same as the other roms.
I guess it's the microUSB port?
Click to expand...
Click to collapse
Do you use your device while charging? Sometimes is the Usb Output lower than the used power. Have you disabled wifi/data/wlan and do on while charging? You have to press in the notification bar on the Usb. Notifications and select usb drive
Sent from my HTC Incredible S using xda premium
By way of some miracle, USB mass storage and debugging are working now. Should I try to unroot to get back to S-ON for warranty, assuming it's the microUSB port?
Oh, and I just saw it go from Charging 11% to 12%, so I guess it's charging. I'm afraid to touch it though, guessing the port's really fragile.
larryorsomething said:
By way of some miracle, USB mass storage and debugging are working now. Should I try to unroot to get back to S-ON for warranty, assuming it's the microUSB port?
Oh, and I just saw it go from Charging 11% to 12%, so I guess it's charging. I'm afraid to touch it though, guessing the port's really fragile.
Click to expand...
Click to collapse
If you unlocked it via Htcdev idk if you revert the warranty back because they safed the Toked from you device. If you riitrd ir without any token or so, i would revert it
Sent from my HTC Incredible S using xda premium
I didn't use htcdev, just Revolutionary? (not sure if they do the same thing, sorry)
larryorsomething said:
I didn't use htcdev, just Revolutionary? (not sure if they do the same thing, sorry)
Click to expand...
Click to collapse
They don't
You can get it Back to S On
Sent from my HTC Incredible S using xda premium
Uhh so I'm trying to follow this guide to get back to S-ON, but it requires ADB and USB debugging. After flashing the stock rom back on, I can't seem to get debugging to work again. The USB icon is in the status bar so I know it's charging, but there should be a notification for debugging mode, right?
I'm assuming it's not possible to put the files on the microSD card and then flash the HBOOT on the device itself? (maybe I should post about this in the guide's thread)
EDIT: I should also note that despite being able to set it to disk drive mode, I'm still getting the 'device malfunctioned' message on my PC, so I can't directly transfer files to the SD. I guess that's why debugging isn't working.
larryorsomething said:
Uhh so I'm trying to follow this guide to get back to S-ON, but it requires ADB and USB debugging. After flashing the stock rom back on, I can't seem to get debugging to work again. The USB icon is in the status bar so I know it's charging, but there should be a notification for debugging mode, right?
I'm assuming it's not possible to put the files on the microSD card and then flash the HBOOT on the device itself? (maybe I should post about this in the guide's thread)
EDIT: I should also note that despite being able to set it to disk drive mode, I'm still getting the 'device malfunctioned' message on my PC, so I can't directly transfer files to the SD. I guess that's why debugging isn't working.
Click to expand...
Click to collapse
Have you ever installed HTC Sync or the HTC USB drivers on your PC? Those are the key to getting adb and fastboot working.
tpbklake said:
Have you ever installed HTC Sync or the HTC USB drivers on your PC? Those are the key to getting adb and fastboot working.
Click to expand...
Click to collapse
Yes, I have HTC Sync installed. I also installed the ADB/fastboot files from here, just to be sure. I don't think that would be the problem anyway, since not even Windows is recognizing it.
larryorsomething said:
Yes, I have HTC Sync installed. I also installed the ADB/fastboot files from here, just to be sure. I don't think that would be the problem anyway, since not even Windows is recognizing it.
Click to expand...
Click to collapse
Have you tried another sdcard? This might be a corrupt misc.img. When you used my script, did you have any issues with gold card creation, or have you messed with the Cid in any other way? The script should have made a backup of your original misc partition so it shouldn't be too hard to flash it back, but first you should try flashing another rom, tpbklakes stock rooted rom would be a good one to try unless you have a stock nandroid on your sdcard.
Btw, what recovery are you using? Please include version number.
Nonverbose said:
Have you tried another sdcard? This might be a corrupt misc.img. When you used my script, did you have any issues with gold card creation, or have you messed with the Cid in any other way? The script should have made a backup of your original misc partition so it shouldn't be too hard to flash it back, but first you should try flashing another rom, tpbklakes stock rooted rom would be a good one to try unless you have a stock nandroid on your sdcard.
Btw, what recovery are you using? Please include version number.
Click to expand...
Click to collapse
Sorry, I flashed the stock ROM right before you posted this. I just tried putting in another SD card and it's getting the same error. I'm sure it's the USB port at this port, seeing how I have to position the cable to get it to charge at all, and it's getting harder and harder to position. I'm just hoping for a way to flash the HBOOT on the device at this point.
I think I was using Recovery 5.0.3.0? I installed it from ClockworkMod's Rom Manager. And I didn't mess with the Cid at all, or have problems with the goldcard creation.
larryorsomething said:
Sorry, I flashed the stock ROM right before you posted this. I just tried putting in another SD card and it's getting the same error. I'm sure it's the USB port at this port, seeing how I have to position the cable to get it to charge at all, and it's getting harder and harder to position. I'm just hoping for a way to flash the HBOOT on the device at this point.
I think I was using Recovery 5.0.3.0? I installed it from ClockworkMod's Rom Manager. And I didn't mess with the Cid at all, or have problems with the goldcard creation.
Click to expand...
Click to collapse
Ah well yeah, if you have to physically manipulate the USB cord to get it to charge then its a hardware issue. Warranty will take care of that.
So you're back to s-on, no issues?
Nonverbose said:
Ah well yeah, if you have to physically manipulate the USB cord to get it to charge then its a hardware issue. Warranty will take care of that.
So you're back to s-on, no issues?
Click to expand...
Click to collapse
Well, not yet! I have stock rom working fine, but when I load up the bootloader, it still says Revolutionary, S-OFF. So I'm trying to get it to say FASTBOOT USB while bending the cable around and round etc. It's only flashing to USB a couple of times, and then it says USB Device not recognized on my PC, so I guess it won't work anyway if I get the cable in properly.
larryorsomething said:
Well, not yet! I have stock rom working fine, but when I load up the bootloader, it still says Revolutionary, S-OFF. So I'm trying to get it to say FASTBOOT USB while bending the cable around and round etc. It's only flashing to USB a couple of times, and then it says USB Device not recognized on my PC, so I guess it won't work anyway if I get the cable in properly.
Click to expand...
Click to collapse
To use Fastboot USB mode, the phone should be in Charge Mode, Not Disk Drive mode.
tpbklake said:
To use Fastboot USB mode, the phone should be in Charge Mode, Not Disk Drive mode.
Click to expand...
Click to collapse
I'm having trouble even getting the option to change that now, but shouldn't I be in the bootloader if I want to be using fastboot?
Also, I should probably specify that this is the stock ROM I flashed:
http://www.filefactory.com/file/c0a...5AU_3805.04.03.12_M_release_185029_signed.exe
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
I have the sprint htc one m7, I have been connecting it to my PC widows 7 64bit for the past year without any issues. I have the proper drivers installed on the pc. Now when I plug in via usb I get an immediate error message= on the pc it says DEVICE DRIVER SOFTWARE NOT SUCCESSFULLY INSTALLED, on the phone it says USB HOST CABLE IS PLUGGED IN UNABLE TO CHARGE.
I think the problem is with the phone because I have tried two computers different usb ports and cables and get the same. I also tried my wife’s phone and it works as it should. She has the same phone only difference is mine is rooted (stock4.4.2) and hers is not rooted.
I have tried uninstalling the drivers and reinstalling and get the same thing.
This is really bugging me because I don’t know what changed on my phone to cause this.
Please Please help if you can. I have searched for the solution without any luck
THANKS
Doug
Quick note=Under the driver software was not successfully installed message on my pc it says MTP USB DEVICE then has a red X with DEVICE UNPLUGGED next to it?
It is however able to see the phone when i put it in Fastboot= Fastbootusb.
What the heck is going on???
another note= after plugging it into the computer and getting the errors, when i plug it in to the wall charger it will not charge. Unless i reboot it then it will charge.
Anybody got an idea?
dug13 said:
I have the sprint htc one m7, I have been connecting it to my PC widows 7 64bit for the past year without any issues. I have the proper drivers installed on the pc. Now when I plug in via usb I get an immediate error message= on the pc it says DEVICE DRIVER SOFTWARE NOT SUCCESSFULLY INSTALLED, on the phone it says USB HOST CABLE IS PLUGGED IN UNABLE TO CHARGE.
I think the problem is with the phone because I have tried two computers different usb ports and cables and get the same. I also tried my wife’s phone and it works as it should. She has the same phone only difference is mine is rooted (stock4.4.2) and hers is not rooted.
I have tried uninstalling the drivers and reinstalling and get the same thing.
This is really bugging me because I don’t know what changed on my phone to cause this.
Please Please help if you can. I have searched for the solution without any luck
THANKS
Doug
Quick note=Under the driver software was not successfully installed message on my pc it says MTP USB DEVICE then has a red X with DEVICE UNPLUGGED next to it?
It is however able to see the phone when i put it in Fastboot= Fastbootusb.
What the heck is going on???
another note= after plugging it into the computer and getting the errors, when i plug it in to the wall charger it will not charge. Unless i reboot it then it will charge.
Anybody got an idea?
Click to expand...
Click to collapse
This is probably the most drastic method to fix it but the most likely way to fix it. Flash a RUU it reverts EVERYTHING to stock and deletes everything you had in the phone.
Since the computer recongizes it in fastboot RUU will work. Make a backup and if you are S-On then you have to relock bootloader first
Thanks for the reply, i thought about RUU and will probably have to attempt it. Im just not sure if its a software or a hardware issue? Everything else on the phone seems to be working fine. It just will not show up on any computer, i have tried 3 different computers and even installed HTC sync software on one and I still get the same error message.
Does this sound like a software issue or a hardware?
What do you think?
dug13 said:
Thanks for the reply, i thought about RUU and will probably have to attempt it. Im just not sure if its a software or a hardware issue? Everything else on the phone seems to be working fine. It just will not show up on any computer, i have tried 3 different computers and even installed HTC sync software on one and I still get the same error message.
Does this sound like a software issue or a hardware?
Click to expand...
Click to collapse
What do you think?
dug13 said:
What do you think?
Click to expand...
Click to collapse
sounds like a software problem since if it was hardware it wouldnt show up in fastboot either.
PLEASE HElp RUU failed to fix???????
ok as stated in the OP my HTC one wont connect to my pc. The only time is connected was in fastboot, so i did an RUU to attempt to fix the problem. After a successful RUU I still have the same problem= usb debugging is on i plug it in, it says installing drivers. Then I get the red X and the error message says =HTC MTP DEVICE IS UNPLUGGED & HTC MTP DEVICE FAILED.
I know everything else is working because my wife's phone connects no problem- so its not the usb port or cable my setting are the same.
ANYBODY GOT A SOLUTION?
PLEASE HELP- TIA
DOUG
dug13 said:
ok as stated in the OP my HTC one wont connect to my pc. The only time is connected was in fastboot, so i did an RUU to attempt to fix the problem. After a successful RUU I still have the same problem= usb debugging is on i plug it in, it says installing drivers. Then I get the red X and the error message says =HTC MTP DEVICE IS UNPLUGGED & HTC MTP DEVICE FAILED.
I know everything else is working because my wife's phone connects no problem- so its not the usb port or cable my setting are the same.
ANYBODY GOT A SOLUTION?
PLEASE HELP- TIA
DOUG
Click to expand...
Click to collapse
try talking to htc offical live chat
dont mention anything about being s-off or being rooted though they wont help you then.
as long as you are ruu you should have everything stock
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
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.