Does anyone else have a problem with holding down the power button?
When I hold down the button my Nexus only registers it as pressing it and letting go and usually just turns off the screen. It's quite frustrating when I need to turn off my N1 or set airplane mode, and usually takes half a dozen tries before it actually registers as holding down the button and not just pressing it.
I fear it may be a hardware issue and I will have to return it.
I got the same issue. Not sure if it is soft- or hardware related. Also having problem with waking up. Works well with the track ball so I guess it's the hardware.
I'm really dreading having to send this back to HTC. Everything else on this device has been working normally, but I also have an unlocked bootloader. I'm reluctant to trade it in.
andythefan said:
I'm really dreading having to send this back to HTC. Everything else on this device has been working normally, but I also have an unlocked bootloader. I'm reluctant to trade it in.
Click to expand...
Click to collapse
Mine is doing the same thing.
Here's a good test.
Do a nandroid backup, and then flash back to the stock ROM. I haven't done this yet, and am planning to do so this weekend.
If you flash back to stock and the power button works normally, well there you go.
If not, it's a hardware issue.
I will say that I've been using a Desire2Nexus port ROM and it definitely happens more with this ROM than the CM-based ROMs, but that could also be due to the laggy/sluggishness of SenseUI.
I was seeing the same problem in both ROMs of recent generation though. So my gut tells me it's a hardware issue. Flashing to stock and testing it out will be a dead giveaway, though.
HTC has historically been pretty good about replacing known hardware malfunctions. I also bought SquareTrade coverage just in case, though, so I will be getting my money back one way or another.
maxawesome said:
Mine is doing the same thing.
Here's a good test.
Do a nandroid backup, and then flash back to the stock ROM. I haven't done this yet, and am planning to do so this weekend.
If you flash back to stock and the power button works normally, well there you go.
If not, it's a hardware issue.
Click to expand...
Click to collapse
I've wiped and flashed the last stable CM version. The issue persists. Also, it happens when I'm in recovery as well, so I'm afraid it may be a hardware related issue.
Can I still send this in for replacement if the bootloader is unlocked? When I be charged repairs in that regard?
Related
I've been in this rooting game since it began, and I never had a major issue.
Unfortunately now I have come across one, and I believe it may be a Hardware problem, but I'm not entirely sure.
At any rate, the other day I'm on the computer the phone is charging through the usb cable, and while im using it, the back light goes out. I think this is weird.
I lock, and unlock it and everything is back to normal, but when I slid the screen back the back light went out again.
And the home button didn't work either, I doubt this was a problem with Cyan's ROM, or a theme. I do have the new lockscreen but I never had an issue.
So from Cyan's 4.0.4 I upgrade to the experimental version and the problem persists, the back light won't turn on unless the screen is slid up/open (Also, I have no lock screen!? wtf?).
Afterwards I decide to go back to 4.0.4 and even when my phone boots up the back light wont turn on unless the phone is open/screen is slid up. So obviously it seems like a hardware issue.
Anyone else have this problem? or any thoughts about it?
I'm on Cyan's 4.0.4 - no theme
26I Radio and H's SPL.
reset your phone. hit call,menu and power at the same time. then let us know how everything works.
Funny things happen when you don't wipe, make a nandroid backup of your current setup and than wipe and flash again and see if it persits
I tried both of those suggestions but they didn't work at all.
Lame, like I said it might be a hardware problem, so I might have to just call them
igloo77055 said:
I tried both of those suggestions but they didn't work at all.
Lame, like I said it might be a hardware problem, so I might have to just call them
Click to expand...
Click to collapse
This is a hardware problem. Happened to me too. Been trying to find a solution, but the fact that it still has the same backlight problems when the phone is booting (On the T-mobile G1 screen) shows that's it's way beyond the ROM.
Mine even has the same problems on the recovery screen. Time to find a new G1. If you find a solution, lemmie know. I've been looking for one.
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
I received a Nexus One yesterday. First it worked for around 5 min, then rebooted by itself. From then on I never got into the system. If i turn it on normally, it freezes (or loops) at X logo. I have no problem reaching FASTBOOT and BOOTLOADER. But when I try to go to recovery, sometimes I can get to it, sometimes not (freezes at X also, or the screen is completely black so I need to pull out the battery).
What is causing the problem? I also tried to flash recovery image, same result. As long I'm a newbie, I know nothing about radio, spl, kernel ... flashing and dependencies between each.
Is it possible that it is a hardware issue? If not, what can I do, wipe, flash, etc...?
In desperate need of help... Tnx
I had exactly the same situation with my first N1. I called HTC and returned it as a defective device. My replacement device has been rock solid.
That being said, can you get into recovery Mode? (hold trackball down while powering on), if you can, try a factory reset and see if you can boot then.
Yea sometimes i can get to recovery mode. Usually when the battery is out for a while. I tried also with the factory reset, no success.
I write this problem here thinking there may be a solution (like flashing everithing...), but the problem is I know very little about all the stuff such as kernel, rom, radio, etc.
Any advice besides returning to HTC? Because I have no warranty.
You describe my problem exactly. It was a hardware problem and I returned my device to HTC.
It sounds like the same problem i have.
Looks something like this ?
http://www.youtube.com/watch?v=_bIfvl6Cuts
DvTonder said:
You describe my problem exactly. It was a hardware problem and I returned my device to HTC.
Click to expand...
Click to collapse
This is happening to my N1 quite often, it seems stable now and doesn't happen often. I am guessing it has defective RAM or something.
The important part of this is how long did you take to get your device back as I see you are also in Canada, this is why I am not sending it in also, I know they are pretty good about honouring the warranty after root if it is hardware but I don't want to send it in for nothing if it is not that bad.
I have started using a 950mV kernel, this seems to have helped. Try one out OP.
This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?
Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs
That is definitely not normal behaviour.
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.
any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^
I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department
I have the same problem its almost like the soft key is being held down, anyone find a fix for this?
Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.
I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.
I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.
Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492
^^^
Do not do this unless you have a i9000m. You will break your buttons.
electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...
Hi,
I have flashed the 4.1.2 EE ROM found at (http://forum.xda-developers.com/showthread.php?t=1942150) and also flashed the Perseus kernel.
Since this, however, I have found my phone randomly just decides to turn off and people end up dialling my other number to ask why I'm not picking up their calls, to which I check my phone and see it's completely dead.
What makes things stranger is that some people say my phone still rings leaving me to think maybe it stays on but there is no sound/display?
I guess this is further apparent considering to turn my phone on I have to hold the power button for a while, as if I'm powering down to then power up again.
Does anyone know why this could be or has experienced anything similar with the kernel/ROM?
I am probably going to re-flash the ROM and use the stock kernel since it's supposedly the official ROM.
If the problem persists, however, I am wondering what steps I would have to take in order to send it off to insurance for a replacement handset.
Can insurance companies void my claim if they know the phone has been tinkered with? I know this has been asked many times but specific to my handset what steps would I take to get it 'claim-ready'?
Thanks guys!
Thers nothing wrong with the rom I assure you!
Reflash it again and leave the kernel as it is and see how you go with that.
Probably an issue with the custom kernel you are using and the rom.
Sent from my GT-I9305 using Tapatalk 2