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.
Related
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?
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
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?
Hello!
I had purple tint on my old HTC One, so I sent it for repairs under warranty and I got a completely new unit. It was working for a day, but today it couldn't connect to the network. At first I thought it was a HW issue, but I realized that Dialer was crashing with a message: "com.htc.htcdialer is not responding.". That made me think it was a software problem, so I tried doing a factory reset in HBOOT, but now htcdialer is still crashing, and I can't even go through initial setup, it just keeps rebooting when I try to unlock it for the first time. Is there any other way to flash a ROM, without being able to boot the phone?
Everything is completely stock, bootloader is locked and phone is not rooted. I updated it to the latest available version, 4.4.2 with Sense 5.5, I'm unsure what version it exactly is. I would like to keep it stock for at least a couple of days in case there is a hardware failure and I have to send it back to service, but I can do anything if it's necessary.
Thank you very much.
HBOOT image, if it is of any help: http://i.imgur.com/3XKC6Br.jpg?1
Since its completely stock and you just got the phone, I wouldnt bother going through and installing a custom rom, its too much of a hassle and if it ends up being a hardware problem its an even bigger issue.
I'd contact HTC again and see if they can do anything about it, or just send it back again under warranty. Flashing a custom rom in your situation isnt worth it imo.
Bhavpreet said:
Since its completely stock and you just got the phone, I wouldnt bother going through and installing a custom rom, its too much of a hassle and if it ends up being a hardware problem its an even bigger issue.
I'd contact HTC again and see if they can do anything about it, or just send it back again under warranty. Flashing a custom rom in your situation isnt worth it imo.
Click to expand...
Click to collapse
That's exactly what I've been thinking.
I was actually able to get it to go through initial setup between reboots and I was able to install a RUU, a the same thing is happening again, so I'm pretty sure it's HW related. And it still isn't getting any signal. It's a bit of a problem because I have to bring it to a store 150km away, but I'll have to do it :crying:
[email protected] said:
That's exactly what I've been thinking.
I was actually able to get it to go through initial setup between reboots and I was able to install a RUU, a the same thing is happening again, so I'm pretty sure it's HW related. It's a bit of a problem because I have to bring it to a store 150km away, but I'll have to do it :crying:
Click to expand...
Click to collapse
Ahh that sucks. Call them and make some excuse about how you cant come to the store and see if you can ship it to them.
Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?
placebored said:
Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?
Click to expand...
Click to collapse
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it
clsA said:
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it
Click to expand...
Click to collapse
Thanks clsA. I'm surprised by that since in my experience a broken motherboard results in a much more substantial and obvious failure, but I guess the point is moot if I can't get into recovery to try anything else.
There isn't much of a market for new motherboards, and my experience with eBay sellers for oem components on this device makes me think trying to replace it there would be a fool's errand. I guess I could buy a used M7, but on the other hand the damn thing has basically been nothing but problems. The defective camera turned to garbage in under a year and one drop killed it? Unless anyone has another suggestion, I guess it's time to cut my losses on this thing. I may feel a sentimental attachment because I've nursed it along so much, but damn... a phone is a phone and this one has been a LOT more problematic than any other one I've had.
Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!
placebored said:
Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!
Click to expand...
Click to collapse
That's great, I'm glad you were able to fix it