I have owned my HTC One m7 (AT&T flavored) for several months now and I love the phone but there is this one recurring issue that I have had since i bought it. It randomly ejects the SIM card then it will randomly put it back in. Most of the time it seems to do it while I'm not looking at it, screen turned off, in my pocket. It will, however, pop up the error while I'm on it but that is uncommon. As for the actual error, well sometimes it pops up the error to say it was removed then immediately afterwards reinsert it. Sometimes several of the messages will pop up either over time or almost instantly. And while sometimes its only a couple of the messages other times I can see 40+ of these. Sometimes it will remove the card then not put it back in for hours. I have had it remove it and then put it back after only a few minutes or I have had last for literally hours. Sometime rebooting will make it realize that is SIM is in the phone but other times, I'm talking rarely' it won't and I will have to reboot a few times before it will come back. Mebbe I just have to wait for the phone to put the SIM back. As for frequency, totally random, some months I have zero issues, other times it will act up and it makes my phone all but unusable. I mean everything about this issue it totally random and ethereal.
I have tried getting a new SIM card, that seemed to help it for a while but it came back. And I have tried several different ROMS both jellybean and kitkat. I think they have all been cm11 based except for the stock ones that I have tried. And again it was happened even on the original ROM, recovery and everything.
After talking with a guy at AT&T about this issue he told me that its not uncommon on these phones. That he had seen it alot after the upgrade to KitKat, I saw it before kitkat. And from trying to Google around and find anyone with a similar issue, I'm not so sure its so common.
Can anyone shed some light on this issue? Does anyone know how to fix it? Its driving me up a wall and it seems to like happening in the worst of times, when I really need my phone to work.
(For the record, the SIM tray is not popping open or anything, its very firmly in the phone, it seems to be software)
Currently I have it running C-ROM v6.4 with TWRP 2.7.0.1a.
Could my HBoot thing it way out of date and that be causing it?
HBOOT - 1.44.0000
RADIO - 4a.17.3250.20
OpenDSP-v31.120.274.0617
(this is entering new territory for me, idk what any of that is, I think you can flash the HBOOT thing if you are s-off but idk what that is either)
Umdoobby said:
Could my HBoot thing it way out of date and that be causing it?
HBOOT - 1.44.0000
RADIO - 4a.17.3250.20
OpenDSP-v31.120.274.0617
(this is entering new territory for me, idk what any of that is, I think you can flash the HBOOT thing if you are s-off but idk what that is either)
Click to expand...
Click to collapse
HTC was replacing the sim card tray on some early models
and some were able to use a piece or tape on the back of the sim to make it a little thicker. It really has nothing to do with the hboot version. The hboot you have indicates you have never updated the phone. Updating to a 3.xx.502.x software would give you a huge improvement in the touch screen driver.
if can be done pretty easy with a RUU (rom update utility) you can download the 3.xx RUU from HTC here >> http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
be aware that that file will totally erase you phone and all settings / apps / pictures / music will be lost. Backup your sdcard to the pc before you began. Also sync your phone to htc backup and / or Google before and after the RUU.
I can attest to the tape on the back of the SIM method.
clsA said:
HTC was replacing the sim card tray on some early models
and some were able to use a piece or tape on the back of the sim to make it a little thicker. It really has nothing to do with the hboot version. The hboot you have indicates you have never updated the phone. Updating to a 3.xx.502.x software would give you a huge improvement in the touch screen driver.
if can be done pretty easy with a RUU (rom update utility) you can download the 3.xx RUU from HTC here >> http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
be aware that that file will totally erase you phone and all settings / apps / pictures / music will be lost. Backup your sdcard to the pc before you began. Also sync your phone to htc backup and / or Google before and after the RUU.
Click to expand...
Click to collapse
Alright I laminated the top of the SIM card with a single piece of scotch tape, that sound about right?
Now I have updated my phone just not through HTC. Its been on custom ROMs after about a month of owning the phone and I try to stay with the most up to date version of android. You you recommend that I update that? Should I go to the version that you mentioned or find a more up to date version. What about the radio or any of the other firmwares, should i even bother those?
Umdoobby said:
Alright I laminated the top of the SIM card with a single piece of scotch tape, that sound about right?
Now I have updated my phone just not through HTC. Its been on custom ROMs after about a month of owning the phone and I try to stay with the most up to date version of android. You you recommend that I update that? Should I go to the version that you mentioned or find a more up to date version. What about the radio or any of the other firmwares, should i even bother those?
Click to expand...
Click to collapse
just the update to the 3.xx RUU would be better than where you are now. If you want to go further you need to consider getting s-off first on a hboot lower than 1.57
Related
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Mine reboot when it overheats during charging. There are several overheating threads u should check out.
Sent from my Nexus One
Just be honest
houmi1 said:
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Click to expand...
Click to collapse
From what I hear, if your honest and tell google that you unlocked your bootloader they will still repair your device, I don't know about replacing it if it can't be repaired. But before you go that route try troubleshooting. Make sure you have the correct radio, not all roms come with the correct radio. Non-compatible kernals can become a issue to, if you flashed a custom kernal. I get the bootloop problem if I flash a rom without wiping, which I never do, except when the instructions say no wipe required, and then I get the bootloop issue. So try a full wipe, data, dalvik & cache, ext, and then reflash your rom.
I had random reboots up the wazoo. My phone was unlocked/rooted/running FRF93. I downgraded to other versions of Froyo and even went back to 2.1/CM and it was still rebooting.
Turns out that HTC actually puts it through a reasonable testing procedure to determine if it was in fact the user that damaged the phone. So even if it is unlocked/rooted and the phone passes the test, you will get your repair free of charge just like me. I'm currently waiting for them to ship my phone back.
Although I have heard horror stories from HTC, so I really think it depends on the moon cycle...
Like a poster above said, BE HONEST. Let them know the truth that it's rooted/unlocked but currently running a standard ROM. If they give you the standard "if it's rooted, you're going to have to pay", tell them that you're heard of their testing procedure to determine if it's the user's fault. Go to a supervisor if you have to.
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
houmi1 said:
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
Click to expand...
Click to collapse
Any updates? I have a similar issue
Yeah I basically think it's heat related and unrelated to the firmware, RAM, etc.... I had the phone at a very cool place and it works perfectly, and when I started using it, as it got hot, it started rebooting, and I noticed the back of the phone was very hot.
So I think nxt was right #2 in this thread.
Houman
The above observation would seem to make sense. My phone would reboot while trying to watch youtube videos sometimes, but ALWAYS within a few minutes of using it on the mains...
I have since had it sent back to HTC to have the phone repaired. I had rooted my phone just to get 2.2 however as it was a genuine hardware issue they replaced the main board and now not only does the phone not reboot anymore, the issues I had with no 3G (only Edge) have disappeared too. Happy
BANE
Hi
So I got my phone back from htc, they basically fixed it and even locked the bootloader so all is well
Just FYI
Houman
So, I bricked my Hero about a year ago, and I now have a shiny Evo V 4G after going through an Optimus S. Anyway, I've kind of missed the little Hero, which has been sitting in my drawer for about a year now. Can anyone help me unbrick it?
What happened was that the phone decided to randomly turn itself off (happened once in a while on CM7), and I didn't mind it until I tried to turn it on later at home. Didn't boot (just hung at the ROM's bootanimation- not the HTC logo), so I tried to go into recovery, only to find out that recovery was mysteriously wiped. Panicked a bit here. I then downloaded the RUU, only to find that it failed every time I tried it, quoting some error I tracked down to a mismatched carrier (I was on iWireless from Kroger, cheap, I know). At this point, I was cursing myself, wishing I had S-OFF'd. (didn't make that mistake with my Evo V! xD)
Anyway, does anyone have ideas on how to revive it? Current stats from bootloader-
HERO XC SHIP S-ON
HBOOT-1.47.0000 (HERO200000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.23
Try this. Stick it on the root of your msdcard. Might have to pull the card out of the phone and use an adapter to fit a sdcard slot on your computer. Make sure it is the only Hercimg.zip file on card.
Once on card and back in phone, Vol down and Power. Vol rocker to Hboot and let it read the file. Push track ball to get to run. Should work with S-on. Let me know if you have any luck.
Mac
Edit: The file I have is for Sprint. Not sure if it will work for iWireless. Might have the same mismatch error. Not sure if you can edit the build prop if that will change anything if it does not work.
The HTC Hero is one of the most bullet proof Android phones ever made. It's really hard to brick it. Usually when someone has made it unusable within their range of understanding, thinking it is bricked, there's a ground-up approach that can recover it, like what Macanage has recommended. HERCIMG is your friend, and may indeed recover your phone.
It's astounding as to what strides developers have made with porting later Android OS versions to the old Hero, and not only reducing the bloat but streamlining the rest (like partition rebalancing) to give the OS more room to operate in. I'm still using mine and I'm thrilled with how well it works at this point, running LiGux.
My HTC One decided to kill itself yesterday by vibrating out of control during a run. In the process, it burned up some stuff. The back camera doesnt work, my screen wont come on during phone calls, and my screen flickers any time it has to do something with my sim card.
I have the Unlocked 32gb US Edition bought straight from HTC. (PN07120)
I want to send it back to them, but I can't find the RUU for my phone to restore back to stock.
I turned my phone into a google edition and now I need to get it back to true sense 5.
Any help and I'd be so thankful!
That model number probably corresponds to an AT&T HTC One. You most likely need the Cingular RUU. Could you check your phone's CID before you run the RUU? It should be CWS__001(if it is indeed the AT&T model).
You can find most RUUs here: http://forum.xda-developers.com/showthread.php?t=2207874
lilcoleslaw said:
My HTC One decided to kill itself yesterday by vibrating out of control during a run. In the process, it burned up some stuff. The back camera doesnt work, my screen wont come on during phone calls, and my screen flickers any time it has to do something with my sim card.
I have the Unlocked 32gb US Edition bought straight from HTC. (PN07120)
I want to send it back to them, but I can't find the RUU for my phone to restore back to stock.
I turned my phone into a google edition and now I need to get it back to true sense 5.
Any help and I'd be so thankful!
Click to expand...
Click to collapse
I have the same problem
also I have the same model (PN07120) UNLOCKED
I can not find the file RUU
could you fix it?
I have problem with the camera showing a lot of noise and flashes pink and want to take it to warranty
I just got my One a week ago today, and rooted it the first day as well. From last Wednesday to earlier today, I've had no issues at all with it; suddenly, audio is not working at all, either through the headphone jack or speakers. I thought it might be a ROM issue, so I reflashed the ROM clean (PACMan 4.2.2), and it still didn't work. I flashed 2 other ROMs, SlimBean and a Sense 4.2.2 based one, and the audio still doesn't work at all. I've done nothing that could've damaged it; I don't overclock, it's never gotten wet, nothing. Has anyone else had this issue, and know a fix, or do I have to return it to stock and turn it back into Sprint?
Also, another note- earlier today it was getting really hot for no reason- I wasn't running anything that would do that, no OC like I said. I Googled, and many people said it was a common occurrence due to the aluminum body dispelling heat from the internals. It went away after 20 minutes or so, so I figured it wasn't an issue. Could that have done some damage? Thank you for any help in this, I'm really worried since I just got the phone and it's already having issues. I've loved it otherwise so far, and owned 3 other HTC phones, and nothing like this has happened before, so I hope it's just a one time thing.
I don't have the audio issue with any rom I flashed, maybe your device is damaged. You can return it for a new one.
I also have the heat problem...
sent from my m7spr using tapatalk 4
I've been backing up my stuff to get it ready to take back. I hear the blue model's coming to Sprint on the 10th, maybe I can hold out a few more days and pick up one of those
Update- I've been trying all morning to restore to stock, and I'm getting worried now.
I went by this thread http://forum.xda-developers.com/showthread.php?t=2250904 to use that RUU to return to stock. I am trying to relock my bootloader in fastboot, and I get the error "[Err] Command Error!" each time I try. To use the RUU, I need to have a locked bootloader, but I can't get a locked bootloader because of that error. What might be wrong here? I am using the stock USB cable with a USB 2.0 port, Windows 7 32 bit.
Alright, it turns out that was due to a stupid error on my part. I have got my bootloader relocked, but now when I try to flash the RUU, I get the 171 USB Connection error. It'll get stuck on the black HTC screen at that point. What could possibly be wrong now?!?! If anyone has any tips, I can provide as much further information as you may need.
I will try to be as complete as I can here, let me know if I forgot to mention anything.
I have a two month old Sprint HTC One running software version 1.31.651.2. I installed TWRP 2.6.3.0 and rooted the phone about 1 month ago. About a week ago I used revone 0.2.1 to get S_OFF and to remove the “tampered” banner. Otherwise the phone is pretty much stock. I was hoping to install a custom ROM eventually, but I have not got around to it yet.
Now here are the problems I have been having. On Saturday I plugged an OTG cable into the phone with a flash drive attached. The drive just had some random files on it, nothing phone specific. After seeing that it mounted the drive okay I unplugged it (admittedly without “properly ejecting” it.) Now I don't believe that I used the phone for the next 20 minutes or so. The next time I grabbed the phone, it had apparently turned off. The power button would not turn it on, and if I held the button down the soft buttons would flash, but not turn on. After panicking for a while I eventually got the phone back on by holding the power button down for a good 2 minutes (soft buttons flashing the whole time). After that everything seemed fine for the next 24 hours.
On Sunday I was participating in a half marathon, I had Winamp and Run Keeper running on the phone. Just as I was about to cross the finish line I stopped Run Keeper and quickly tried to switch to the camera, but the home button didn't seem responsive. I know several toasts popped up during this time, I didn't read them, I just assumed that it was Run Keeper complaining that I did not have a Internet connection (which I didn't). Then the phone just reset. It came back on by itself and has been fine since.
Now I am not sure what to do. I don't dare flash a custom ROM when there could be hardware issue. Should I attempt to return everything to stock in case I need to have the phone serviced? Do I just let it go “as is” and see what happens? I don't suppose this is a known bug?
I am willing to listen to any suggestions.
a22e said:
I will try to be as complete as I can here, let me know if I forgot to mention anything.
I have a two month old Sprint HTC One running software version 1.31.651.2. I installed TWRP 2.6.3.0 and rooted the phone about 1 month ago. About a week ago I used revone 0.2.1 to get S_OFF and to remove the “tampered” banner. Otherwise the phone is pretty much stock. I was hoping to install a custom ROM eventually, but I have not got around to it yet.
Now here are the problems I have been having. On Saturday I plugged an OTG cable into the phone with a flash drive attached. The drive just had some random files on it, nothing phone specific. After seeing that it mounted the drive okay I unplugged it (admittedly without “properly ejecting” it.) Now I don't believe that I used the phone for the next 20 minutes or so. The next time I grabbed the phone, it had apparently turned off. The power button would not turn it on, and if I held the button down the soft buttons would flash, but not turn on. After panicking for a while I eventually got the phone back on by holding the power button down for a good 2 minutes (soft buttons flashing the whole time). After that everything seemed fine for the next 24 hours.
On Sunday I was participating in a half marathon, I had Winamp and Run Keeper running on the phone. Just as I was about to cross the finish line I stopped Run Keeper and quickly tried to switch to the camera, but the home button didn't seem responsive. I know several toasts popped up during this time, I didn't read them, I just assumed that it was Run Keeper complaining that I did not have a Internet connection (which I didn't). Then the phone just reset. It came back on by itself and has been fine since.
Now I am not sure what to do. I don't dare flash a custom ROM when there could be hardware issue. Should I attempt to return everything to stock in case I need to have the phone serviced? Do I just let it go “as is” and see what happens? I don't suppose this is a known bug?
I am willing to listen to any suggestions.
Click to expand...
Click to collapse
I think if it were me, being as you are already S-OFF, I would find a 1.29 RUU then update to 1.31 then to 4.3. Don't install custom recovery or root or anything and see if it still gives you problems. If you are still having issues after that it's a hardware problem. If it's hardware, then go take it in to have them look at it.
-Apollo- said:
I think if it were me, being as you are already S-OFF, I would find a 1.29 RUU then update to 1.31 then to 4.3. Don't install custom recovery or root or anything and see if it still gives you problems. If you are still having issues after that it's a hardware problem. If it's hardware, then go take it in to have them look at it.
Click to expand...
Click to collapse
I have similar issues as you do and I've attempted flashing all various firmware for sprint htc one (thinking it was the cause), but no success. I've tried all custom roms (both international sprint supported and sprint only) and still same results. I'm had long experience in flash so I'm not new to the scene. I have not yet done the RUU 1.29.651.10 yet but will eventually, once I have the time to do this and test if hardware is the real issue. If someone test before I do I hope he post to let us know. FYI, I'm S-OFF, Hboot 1.44, Elegencia Rom 4.3 sense 5.5., and latest firmware and radio from sprint.
Does the soft buttons flashing when holding the power button mean anything? Is this a known behavior in any context?
a22e said:
Does the soft buttons flashing when holding the power button mean anything? Is this a known behavior in any context?
Click to expand...
Click to collapse
Yes when holding power button soft buttons flashing, but not sure what your leading into...
By the way, ,I've flashed Elegencia nightly revision 42 (4.3 with sense 5.0) and so far has not power down or rebooted. Something leads me to believe that this is not a hardware issue, but software. I'm just glad I don't have to give up my phone with hboot 1.44 and S-Off just yet...