Whenever I unplug headphones (or any 3.5mm cable) from my Hero, it reboots shortly afterward. Sometimes it also happens upon plugging in the headphones, and sometimes it gets stuck in a boot loop (green HTC logo) until they are unplugged.
I thought maybe this was an issue with HTC's 2.1 ROM, but the issue persisted under CM 6.1 and aospMod 0.9.9.2.
Has anyone else had this issue? Anyone have an idea of how to fix it? It's probably a hardware issue, but I'm 30 days past my warranty, so no chance of getting a swap.
jasonmaloney said:
Whenever I unplug headphones (or any 3.5mm cable) from my Hero, it reboots shortly afterward. Sometimes it also happens upon plugging in the headphones, and sometimes it gets stuck in a boot loop (green HTC logo) until they are unplugged.
I thought maybe this was an issue with HTC's 2.1 ROM, but the issue persisted under CM 6.1 and aospMod 0.9.9.2.
Has anyone else had this issue? Anyone have an idea of how to fix it? It's probably a hardware issue, but I'm 30 days past my warranty, so no chance of getting a swap.
Click to expand...
Click to collapse
How long has this been going on?
Not sure, I just got the phone back. Bought it just over a year ago for someone, but they gave it back recently when they got a new phone.
I'm currently running aospMod 0.9.9.2 with Collin_ph battery tweak, but like I said, the problem happens with the RUU as well.
jasonmaloney said:
Not sure, I just got the phone back. Bought it just over a year ago for someone, but they gave it back recently when they got a new phone.
I'm currently running aospMod 0.9.9.2 with Collin_ph battery tweak, but like I said, the problem happens with the RUU as well.
Click to expand...
Click to collapse
Sounds like they broke it. If you have insurance, send it in. Or don't use the jack... Try a different ROM, maybe the one you got was a corrupt file
Related
Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!
We are going to need some more information to better assist you.
1) What Build are you using
2) Are you running Apps2SD
3) How much space do you have left on your internal storage?
Sure, thanks
Jf 1.5
Radio: 26I
No A2SD
31MB free
Nothing crazy.
I wipe every time I flash.
I've tried factory resetting too.
I try to keep the system clean.
he3 said:
Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!
Click to expand...
Click to collapse
Something like this happened to me about a month or more ago. It was everytime I try and use my phone when I was charging it, it would reboot. After a few days it would just do it at random. I just called tmobile and they just sent me a new one out.
the same thing is happening to me. my phone randomly crashes/reboots and i was starting to think it is the Haykuro build im using. is there any way to test the hardware? is there something like that in an app?
help
Are you using ahome or someting like that cause those programs cause problem with 1.5 uninstall all your theme apps if you have any
No, no themes.
Called t-mob, since I've had the device (sans insurance) less than a year, they are sending new hardware without a battery to replace mine. I decided to add insurance to the new hardware just incase. Thanks for the input! Glad I called!
Now to virginize the phone... heh
I have the same problem. There's a lot of this going around. It sure seems like a coincidence that it started with Cupcake for most all of us.
This has been something that has been happening since the RC33 load it...
Now I got the stupid random reboot problem. This is a warranty replacement and my first one never did this. I guess I gotta get another warranty replacement. Anyone find a definitive cause for this yet?
almost 100% sure you have a hardware problem
savethechicken said:
This has been something that has been happening since the RC33 load it...
Click to expand...
Click to collapse
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol
rikupw said:
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol
Click to expand...
Click to collapse
RC33 was the OTA was in March I believe maybe Feb. This didn't happen as much on RC30 and then RC33 came out and this started to happened more often. Obviously it is not the ROM doing it as not everyone has the problem but something seemed to trigger it on some devices.
alapapa said:
almost 100% sure you have a hardware problem
Click to expand...
Click to collapse
Going to have to agree. This is starting to seem like a Hardware problem, considering all the feedback we are being given.
I have the same exact problem.
It's definitely a hardware issue.
I was thinking it was because my extended battery pack is a little loose or some loose wiring. It happens when the phone is bumped a little. Like putting it on a table too roughly or flipping the screen up too quickly or it shaking in my pocket. Probably going to replace it.
I have this same problem...i had it originally with RC33 then it went away with the cupcake update and I recently root and install cynogen's build and its back to screw up my day
i don't think its a hardware thing ...at least in my case doesn't make sense to be gone for a month and then come right back after rooting
I also experience random reboot issue. Usually when the phone hang first then next thing you know, it is rebooting. Sometimes the phone will be just sitting there and it will reboot by itself. I always thought it is the ROM issue, never suspect hardware. I am running an old version of Dudes v1.3a build.
For me too
I am getting too many reboots too, just got a replacement phones(previous one did this too), same with this phone, first i thought it was Hardware but now it think its the roms. On hero it rebooted 3 times while booting the first time, on cyanogen it rebooted in a couple of hours, just dont know what the problem is, maybe abusing the phone
I got a replacement phone and still have reboots issue on it when booting, playing music etc.
charnsingh_online said:
I got a replacement phone and still have reboots issue on it when booting, playing music etc.
Click to expand...
Click to collapse
Makes me wonder on the apps your using in the background or settings you have up, or even the ROM. Do you have any extra info whats up before it reboots? Does it choke out due to low memory maybe?
So I was hoping that anyone here could shed some light on an issue that one of my friends who just bought a Nexus is having. His N1 is bone stock, and is an AT&T model. Every once in a while, completely out of the blue, the screen will turn black and restart, but then enter an infinite boot loop, where the only solution is to remove the power adapter and battery.
In trying to pinpoint the problem, we have noticed:
-It really only tends to happen when the device is plugged in.
-It's not related to the battery, charger, or microSD (since we tried mine to no avail)
-It's probably not kernel, ROM, or radio related (we let it do the OTA 2.2 update, and the crashes were still present)
I don't understand why it only happens when the phone is plugged in. The phone isn't hot to the touch, so I doubt that the battery is over heating.
Any help will be greatly appreciated. Thanks!
PS. I tried searching, but the only mention of boot loops I could find were on custom ROMs and Kernels...
Exact Same problem and Phone here!!!
Just got it today too! Please any suggestions would be nice! Want to root this phone but to afraid there is a hardware issue!
My friend ended up calling HTC and they asked him to return it, which he did, for a full refund. Ironically, he ended up getting a Samsung Galaxy S (ATT Captivate variety). Nexus one, although less powerful, is more sleek in my book...
I've got almost the exact same problem on an AT&T N1 running Froyo FRF91, the two differences I have are that the phone does feel hot to the touch, and that it never happened on 2.1. If anybody has some info on this it would be greatly appreciated, but I will be calling HTC/Google in the next few days to see if we can resolve this problem.
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
jpav80 said:
Hey guys,
I had a very similar problem with my phone rebooting while charging especially on the Car Dock. I ended up doing an exchange with Google/HTC and received another unit. This one now has no problems with rebooting. I suggest calling and getting your units replaced. My guess is there was a bad batch that have hardware issues.
Jay
Click to expand...
Click to collapse
What can I do if it is unlocked? Any chance they still help you out? Or just forget it?
I don't think it would hurt to just give them a call. I have read some forums where people have sent unlocked phones in for repair and then got them back fixed and re-locked. It is worth a shot instead of having a faulty phone. I did the exchange option and it did take me a while to get my replacement phone, but that was due to HTC moving their repair facility according to the tech. The techs that I have talked to have been helpful. If I thought a tech was no good I just hang up and try again with a different person.
Jay
I have been having pretty much the exact same issues.
I have an AT&T unlocked/rooted N1.
Random reboots frequently when the phone is charging via plug or USB for seemingly no reason. I thought it may have been an app, or combination of apps, so I tried a combination of different steps to try and find a solution.
Wiped data/cache
Wiped data/cache & fix apk permissions (Amon Ra 1.7.0.1)
Wiped data/cache and flashed the current ROM I was using again
Wiped data/cache and flashed different ROMs (both 2.1 and 2.2 w/proper radio) including MCR r16-21, PhoenRom, LeoFroYo, Cyanogen 5/6 RC1 and even tried intersectRaven's Kernel's
Reformated the SDCard both via gparted from Ubuntu live cd and Amon Ra's recovery 1.7.0.1
Swapped out the SDCard thinking possibly a bad block
And finally re-flashed back to shipping stock 2.1 and stock recovery w/successful OTA 2.2 install
All steps I was able to get my N1 to randomly reboot plugged in or not. I even had it sitting on my desk at work unused for 30-40 min (running CM RC1) and it rebooted with no user input what-so-ever. It happens more often while plugged in but was not limited to charging state.
All that said, I finally called support, took about 30 min total to arrange a replacement. This included a factory reset while on the phone with the tech and I was able to get the phone to reboot within a few minutes of first boot.
Take it for what it is worth, but I am positive that this is a hardware issue in my case. Just hope my replacement goes without penalty (unlocked and all) and that my new N1 doesn't have the same issues.
My original N1 had a display problem, so I sent it in and HTC replaced it. I got the replacement back today.. and it's rebooting at random. I updated to Froyo FRF91 (it was running some 2.1 version), and I wasn't paying close attention. I think it might have rebooted mid flash, and is now sitting at the boot logo, and was there for ~10 minutes.
Eventually I pulled the battery, and now I can't even get into recovery to try to re-flash. It just hangs on the Nexus logo.
What should I do?
Edit: On the phone with Google support, forwarding me to HTC for another replacement.
Edit 2: It seems my phone can boot, but only when it has no SIM. It still seems to randomly reboot. Is it possible my radio is messed up? It seems to reboot when I try to do anything that involves the cell radio. Any hope for repairing this myself?
Bump for edit 2. Still looking for help.
I had the same exact thing happen to me. Since the replacement phone didn't work (hard reset, stock) either HTC told me it might be the battery, and it would take two weeks to get one. I ordered one next day and the same exact thing happens. I'm sending back the replacement phone now, in order to get another "replacement". Crazy.
my n1 having rebooting loop problem when i use it continuosly for 5-6mins or performing some task.in airplane mode i can use it for 30-40mins but then restarts and keeps restarting until i give it 3-4min rest before starting it again.probably this happen after 2.3.3 ota updat.
Wipe data (factory reset) and try again.
If it doesn't work - use "unroot/restore" guide in Wiki, PASSIMG with FRG33 image, test it.
If still reboots - use the warranty, something's wrong with your HW.
You can also look at the logcat to see, what is the problem that causes the reboot. Looks like something's overheating.
i am Having the same problem, i have unlocked bootloader and installed the latest cyanogen rom hoping the rebooting problem would be fixed but no luck ,,the rebooting or the overheating what ever causing it persist.
i don't know what else to try??!!!
i really like the phone and don't feel like buying a new one yet. nothing on the market right now convinced me to ditch my n1.
i am just sad that the hardware life span of of the n1 is 1 year only.
yah thats is overheating causing it.because when it becomes hot it goes into restarting loop until i cool it down.still dont know exact problem though.
Jack_R1 said:
Wipe data (factory reset) and try again.
If it doesn't work - use "unroot/restore" guide in Wiki, PASSIMG with FRG33 image, test it.
If still reboots - use the warranty, something's wrong with your HW.
You can also look at the logcat to see, what is the problem that causes the reboot. Looks like something's overheating.
Click to expand...
Click to collapse
Isnt the warranty void after you've unlocked the bootloader?
kled54 said:
i am Having the same problem, i have unlocked bootloader and installed the latest cyanogen rom hoping the rebooting problem would be fixed but no luck ,,the rebooting or the overheating what ever causing it persist.
i don't know what else to try??!!!
i really like the phone and don't feel like buying a new one yet. nothing on the market right now convinced me to ditch my n1.
i am just sad that the hardware life span of of the n1 is 1 year only.
Click to expand...
Click to collapse
I had that problem when my CPU speed was over 1000. Maybe this'll help?
illuminarias said:
Isnt the warranty void after you've unlocked the bootloader?
I had that problem when my CPU speed was over 1000. Maybe this'll help?
Click to expand...
Click to collapse
I don't think it's the cpu because since 2 days ago the phone started rebooting while charging without me working on it. so now i have to turn it off before plugging the charger, or it will hang on the x for hours.
i guess it's time for me to look for a new phone..too bad, i really like the n1.
yes nothing wrong withcpu its hardware problem.i also cant recharge it while on.
i keep it in fridge then it work fine.after little heat up it goes into loop again.
I've also had the rebooting loop when I had a bad battery fwiw. Changing the battery to a new one solved the problem.
I was having the same problem when it's charging (and I use the N1 a bit) and when I use the 3G data (surfing the web, installing apps from the market, etc.)!
And it's the 3rd time that I've sent my N1 to the Tech Repair!!!
Never repaired the first 2! I hope this time will be ok... I'm waiting for my Nexus 1 to come again with me...
This seems like a big N1 defect.
I called HTC today. Out of warranty repair in the USA is 55$ to 283$ plus shipping.
Could have bought a Nexus S for the 500$ I'm spending on repairs + devices.
*************
Update 5/5/2011
HTC fixed mine even though I unlocked the bootloader. No charge. Free overnight in both directions.
this is making me so much angry.although my n1 is in canada warranty but i am now in pakistan so dont what to do?even we dont know about the exact problem.is it board or something small problem?
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.