Hello everyone -
The other day, I came home from work and noticed that my HTC One (M7) lost mobile data / connectivity for no reason. I thought it was just a fluke, so I restarted the phone.
From that point on, I noticed it wasn't a normal issue. I kept getting a com.htcdialer error / not responding and the phone would restart all the time. Now I'm stuck in a continuous reboot - sometimes w/ the error & sometimes without.
The weird part is that sometimes I'll get my mobile connectivity back and the phone will work. Sometimes it will work for a few hours, sometimes for a few seconds, other times not at all.
I've tried wiping the cache partition, factory resetting a few times, and even getting a new SIM Card. Nothing works. Is this a hardware issue? FYI this is a refurbed M7 that I got as a replacement from AT&T for my previously, defective One.
Unfortunately, I can't get the phone info. When I run getvar all I get <waiting for device> in the CMD prompt. Turned off fastboot, turned usb debug on, still doing it.
dgolpashin said:
Hello everyone -
The other day, I came home from work and noticed that my HTC One (M7) lost mobile data / connectivity for no reason. I thought it was just a fluke, so I restarted the phone.
From that point on, I noticed it wasn't a normal issue. I kept getting a com.htcdialer error / not responding and the phone would restart all the time. Now I'm stuck in a continuous reboot - sometimes w/ the error & sometimes without.
The weird part is that sometimes I'll get my mobile connectivity back and the phone will work. Sometimes it will work for a few hours, sometimes for a few seconds, other times not at all.
I've tried wiping the cache partition, factory resetting a few times, and even getting a new SIM Card. Nothing works. Is this a hardware issue? FYI this is a refurbed M7 that I got as a replacement from AT&T for my previously, defective One.
Unfortunately, I can't get the phone info. When I run getvar all I get <waiting for device> in the CMD prompt. Turned off fastboot, turned usb debug on, still doing it.
Click to expand...
Click to collapse
it could be a hardware issue ..
to post your fastboot getvar all you do it from the bootloader with fastboot USB showing on the screen
to get to the bootloader / power off / hold volume down + power / then go to fastboot with the usb attached to the PC
clsA said:
it could be a hardware issue ..
to post your fastboot getvar all you do it from the bootloader with fastboot USB showing on the screen
to get to the bootloader / power off / hold volume down + power / then go to fastboot with the usb attached to the PC
Click to expand...
Click to collapse
That's exactly what I did, and I just get <waiting for device>. Maybe I'll try it at home instead of at work.
If it's a hardware issue, could you guess as to what it would be? Perhaps the SIM reader? Mobo?
Related
My N1 is on stock Froyo 2.2
I was playing RoboDefence and i got popup that battery is below 15%. I ignored the warning and completed the game. Plugged in the wall charger (N1 showed charging 11%) and slept off.
Next morning when i woke up i find that the track ball is blinking, tried to switch on the phone, nothing happens. Finally i remove the battery and replace it and still nothing happens.
Searched the web and came to know that its known problem, tried a work around and was finally able to boot it up and phone is working fine.
Next day i was on a 14 hour flight, forgot to switch off the phone. When i reached at destination i noticed that the battery is in red and immediately switched off the phone.
Reached hotel and plugged in the wall charger. Now whenever i boot my phone it goes into "FastBoot" menu. I tried clearing the cache, recovering, etc. But nothing happens.
Any suggestions are most welcome before i send my phone back to HTC.
Trackball stuck down?
Rusty! said:
Trackball stuck down?
Click to expand...
Click to collapse
Don't quite get your comment. Please help me understand if i need to do something.
Thanks.
To get into fastboot, you hold down the trackball and power on.
If the trackball had become stuck down, it would always boot into fastboot. Try cleaning it with something?
Thanks for the clarification. I will try that immediately.
I cleaned the track ball using wet towel. Powered up the phone and i get the same behavior i.e. phone comes into fastboot menu.
Shouldn't have used water, I had this same problem I got my trackball to wet when I was cleaning it with alcohol and it would only boot to fastboot you can reboot via fastboot and it will turn on into safe mode. My phone dried out in like two days I ran a logcat n it was showing I was pressing it when I wasn't hope this helps you out
Sent from my Nexus One using XDA App
Maybe your getting the screen that says fastboot. In that case...your volume down button is probably stuck.
That screen will have the options FASTBOOT - RECOVERY - CLEAR STORAGE - SIMLOCK. If that's the screen you see...your volume button is stuck.
SiNJiN76 said:
Maybe your getting the screen that says fastboot. In that case...your volume down button is probably stuck.
That screen will have the options FASTBOOT - RECOVERY - CLEAR STORAGE - SIMLOCK. If that's the screen you see...your volume button is stuck.
Click to expand...
Click to collapse
I think my volume down button is not struck, since when i go into fast boot menu i can select recovery, clear storage, etc using my volume up/ down buttons.
If it is struck then the selection should continuously move from top to down and repeat.
Called up HTC customer care. They want me to send the phone for repair. Will send it to them and keep the thread alive with updates.
I sent my phone to HTC and choose the option of repairing it. I received a phone this morning and i found that it is a different phone (Missing engraving and different IMEI number).
New one is working fine with no problems. However i didn't get any message from HTC that they are sending a new phone, etc.
Overall i am happy now that i am back on N1.
My M7 has been going quite well until it ran completely flat two days ago, and now is completely unresponsive when off charger, or boot loops when on charge or connected to the computer. When plugged in, I can get it into Hboot for a few seconds, but the buttons are very unresponsive. I can just manage to select Recovery before the screen goes black and it loops again. When connected to the computer, I get the device connected sound, but am not seeing anything pop up in my Device Manager.
It's running ARHD 70-something (can't remember exactly which), with TWRP installed. No problems with the ROM or recovery before.
Tried the bright light / buttons, going to try sticking it in the fridge tonight. Any other suggestions? Thanks a lot!
otarinz said:
My M7 has been going quite well until it ran completely flat two days ago, and now is completely unresponsive when off charger, or boot loops when on charge or connected to the computer. When plugged in, I can get it into Hboot for a few seconds, but the buttons are very unresponsive. I can just manage to select Recovery before the screen goes black and it loops again. When connected to the computer, I get the device connected sound, but am not seeing anything pop up in my Device Manager.
It's running ARHD 70-something (can't remember exactly which), with TWRP installed. No problems with the ROM or recovery before.
Tried the bright light / buttons, going to try sticking it in the fridge tonight. Any other suggestions? Thanks a lot!
Click to expand...
Click to collapse
does the phone charge when it's off ?
can you boot to fastboot oem rebootRUU ?
Thanks for the reply!
I have no charging LED at all, I just plug it in and after a few minutes it boots up by itself into the boot loop. If I take it off charger, it's completely dead.
Tried sending fastboot oem rebootRUU, but I can't actually get it into fastboot. I just get into hboot for a few seconds, and my power button won't select fastboot. Command line says "waiting for device". Maybe it's a power issue.
otarinz said:
Thanks for the reply!
I have no charging LED at all, I just plug it in and after a few minutes it boots up by itself into the boot loop. If I take it off charger, it's completely dead.
Tried sending fastboot oem rebootRUU, but I can't actually get it into fastboot. I just get into hboot for a few seconds, and my power button won't select fastboot. Command line says "waiting for device". Maybe it's a power issue.
Click to expand...
Click to collapse
not good at all .. i think your motherboard died
Ouch, wonder if it's worth getting fixed or if I should just pick up something else.
otarinz said:
Ouch, wonder if it's worth getting fixed or if I should just pick up something else.
Click to expand...
Click to collapse
I guess that all depends on if you have any warranty left
used / refurbished One's go for $200 - 250 on eBay
same problem
i have the same issue om my one m7,
phone dead n battery is empty, then i plug the charger, no LED indicator on, cant go to recovery, just boot loop.
i think the problem is on the battery, so i will try to replace it, i ll report the result after new battery is placed.
hi joe_zeel. Did changing the battery solve your problem?
report, after change the battery, problem not solved, phone keep bootlooping, sorry guys.
still searching how to fix it, hope find it
joe_zeel said:
report, after change the battery, problem not solved, phone keep bootlooping, sorry guys.
still searching how to fix it, hope find it
Click to expand...
Click to collapse
i got the same problem as yours maybe its board
My HTC Desire 500 had a broken battery (it was swollen up) and the phone wouldn't stay on for more than a few minutes without having it plugged in, but it worked as long as it was plugged in. Now that I changed the battery it stays on without having to plug it in but it won't get past the logo screen when I turn it on. I kept restarting it, I did a factory reset, I let it sit like that for an hour and it still wouldn't get past the logo screen. Sometimes (1/10 chance) when I boot it from HBOOT in RECOVERY it gets past the logo screen but the WI-FI doesn't work and errors keep popping up. I also tried it with the old battery to see if it would work like it did before but it doesn't, it gets stuck at the logo screen.
For the past few days I've been trying to root it and reflash the ROM but I am unable root it because when I get to the part where I have to type the command fastboot oem get_identifier_token it doesn't return anything it just says "Waiting for device". I've looked this up on google and it seems to be a driver problem, I've installed and unistalled all the possible drivers over and over, tried it on both my laptop and my desktop (both Windows 10) but the desktop/laptop still doesn't recognize the phone when it is in fastboot usb mode (It did recognize it when I managed to boot into the Android OS though, as I could get photos from it). Any advice would be greatly appreciated.
I received the phone 'Used, like new' today, wrestled with straight talk, troubleshot my issue of an empty cell signal thingy (on the status bar) and finally came across a forum for motorola phones with a quick fix for this... If I reboot into fastboot, select 'BP tools' the phone reboots and back to android, I have cell service! UNTIL the next power cycle.
This is weird... is there a remedy? Should i return/exchange the phone? Would TWRP resolve this? (I'm totally stock)
Thanks guys!
Is the bootloader unlocked?
Tried factory reset?
It seems the carrier id is deleted......
Just Reboot
Just restart your phone or keep pressed the power for 20 sec it will automatically reboot in normal mode
Ahhh, you're right! Is there another way to push a carrier id to it? I can hard reset again..... But I just finished installing my apps and restoring backups : / .
The bootloader is locked.
#same
Did you ever figure out how to get it out of whatever mode this is? It just alternates every restart of there being being nothing listed under Baseband on the FB screen, my notification light staying on, and no service to working perfectly normal. On a XT1965-T.
Hi all .. I have a phone but nothing appears on the screen and when I connect the phone to the charger shows the sign of the charger until the green sign appears, which means full battery .. What do these things show? Is the screen damaged or motherboard problem ? Please Help
Try holding the power button down for 10 seconds or more, and see if there is any change. Also try power+vol up (which normally boots to bootloader) and hold for 10 seconds or more.
Jnoubileb said:
when I connect the phone to the charger shows the sign of the charger
Click to expand...
Click to collapse
You mean the charging animation on the screen, or just the LED charge light?
If it's showing the charge animation, your screen is okay. And at least have a working bootloader, as well.
redpoint73 said:
Try holding the power button down for 10 seconds or more, and see if there is any change. Also try power+vol up (which normally boots to bootloader) and hold for 10 seconds or more.
You mean the charging animation on the screen, or just the LED charge light?
If it's showing the charge animation, your screen is okay. And at least have a working bootloader, as well.
Click to expand...
Click to collapse
thanks for your replying >>
i mean the led charge light ..also when i connect my phone to laptop , all files on memory appear
Jnoubileb said:
thanks for your replying >>
i mean the led charge light ..also when i connect my phone to laptop , all files on memory appear
Click to expand...
Click to collapse
I gave another suggestion about holding the power/vol buttons. I have no idea if you tried, and if so, whether there was any change.
Reading the files on internal storage to me, means the phone is booted to OS. So I agree that it appears the phone is on, but screen is either not working, or somehow darkened all the way.
What is the history of this device, and did anything happen before the current condition? Did it just happen spontaneously, or did you drop it or try to open it to fix anything? Try to install anything? Is the phone modified at all (TWRP, root, etc.) or basically still stock? Even if it happened spontaneously, did it happen when you were using it (and if so, what were you doing exactly)? Or just picked it up and it was this way?
I try to press power button 10 sec and more and power+ vol+ nothing happened on screen just vibrate ....the problem for my phone appear without any open to phone
Jnoubileb said:
I try to press power button 10 sec and more and power+ vol+ nothing happened on screen just vibrate ....the problem for my phone appear without any open to phone
Click to expand...
Click to collapse
Do you have debugging turned on? Know how to use adb?
i think is on before the problem appear
Jnoubileb said:
i think is on before the problem appear
Click to expand...
Click to collapse
Then connect the phone to a computer, type:
adb devices
And see if your phone's ID is returned, or if there is an error or just hangs "Waiting for device".
If it returns your phone's ID, then the phone is booted to OS (or alternately, booted to custom recovery will also allow adb connection). So to me, this means the phone is on, but the screen is not working (not displaying anything) like you suggested. adb won't connect if the phone is not on (and booted to OS).
redpoint73 said:
Then connect the phone to a computer, type:
adb devices
And see if your phone's ID is returned, or if there is an error or just hangs "Waiting for device".
If it returns your phone's ID, then the phone is booted to OS (or alternately, booted to custom recovery will also allow adb connection). So to me, this means the phone is on, but the screen is not working (not displaying anything) like you suggested. adb won't connect if the phone is not on (and booted to OS).
Click to expand...
Click to collapse
the phone now on mtp mode
C:\WINDOWS\system32>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
3a55e345 unauthorized
So it looks like adb is connecting. I think it is saying "unauthorized" since the phone's screen is trying to prompt you to authorize adb commands (which you obviously can't see or respond to). But it is obtaining the device's ID code. Which by the way, is unique to your device. So I would advise to remove it from your previous post. Don't know if it is dangerous for other folks to have this, but better safe than sorry. Simply telling us that an ID code was returned, would have been sufficient.
Moral of the story, I am thinking the phone is booted to OS, just the screen is not displaying anything. Screen may be broken, as you somewhat were guessing from your top post. I suppose there is a possibility it may be some software fault. You can try to eliminate this as the cause, by possibly booting to bootloader, which should allow fastboot access, then flash a stock recovery image. Although it may be tricky without seeing the display. Since if you need to see the display, or select anything during the process (don't recall if you do or not), you are out of luck.
Although I tend to think this is a hardware issue. Screen may be malfunctioning. Or it may be as simple as a loose connector.