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.
Related
I have a 6 or 7 month old Kaiser branded by AT&T. I got seperated from it late last week, so it ran it battery down till failure. When I went to recharge the phone, it started attempting to boot, staying at the AT&T globe screen and then appearing to boot again, (black screen and momentary vibrate.) With a bit of searching I found the suggestion of boot to loading screen and leave it there to charge. After 6 hours, the battery has a measured voltage of 4.17V so that should be enough, but the phone continues the booting loop.
I tried hard resetting with the two keys and stylus. The phone acted like a normal hard reset with the questions, but when it tried to boot, it continued the reboot loop.
My question, do you think I should attempt to reload the stock AT&T ROM?
I'm new at this so there's a large learning curve. If you guys think this is a low probably solution, then I'll sent it back / buy another one and save the long learning curve. I use this for business so I could spead the learning curve time writing software I get paid for writing.
Thanks,
Bernie
your phone got damaged from battery drain? is that possible?
i think your phone has another problem... i really dont think the battery drain was the reason...
can you go to bootloader if so try flashing new ROM (you will loose data) but again you said you have performed hard reset (partial HR) so your phone is clean!
if you want send your phone back - yes you need to get stocked ROM and stocked SPL back
BernieHunt said:
I have a 6 or 7 month old Kaiser branded by AT&T. I got seperated from it late last week, so it ran it battery down till failure. When I went to recharge the phone, it started attempting to boot, staying at the AT&T globe screen and then appearing to boot again, (black screen and momentary vibrate.) With a bit of searching I found the suggestion of boot to loading screen and leave it there to charge. After 6 hours, the battery has a measured voltage of 4.17V so that should be enough, but the phone continues the booting loop.
I tried hard resetting with the two keys and stylus. The phone acted like a normal hard reset with the questions, but when it tried to boot, it continued the reboot loop.
My question, do you think I should attempt to reload the stock AT&T ROM?
I'm new at this so there's a large learning curve. If you guys think this is a low probably solution, then I'll sent it back / buy another one and save the long learning curve. I use this for business so I could spead the learning curve time writing software I get paid for writing.
Thanks,
Bernie
Click to expand...
Click to collapse
If you already have Hard-SPL installed and it is a version capable, you may try to put the Rom with a Radio onto the Micro-SD card and re-flash the phone that way. I had an issue where i got a boot loop and it turned out that flashing the radio fixed the issue. I hope you at least had a current backup prior to the hard reset because as of now, there is no way to retrieve it
No worries on the backup, it's backed up daily and I only use it as a data carrier. The only drag of the reset is the time of reloading apps.
I agree it may be more than just software issue due to dead battery, but I have to try everything I can. I've back on my old Moto smart phone and it's just not the same, hahahaha.
Now back to studying Kaiser ROMs and how to.
Bernie
As a follow up for anyone who runs across this in the future. I flashed the original AT&T rom and the problem still exists. I spoke to tech support yesterday and they are mailing out a new/reman replacement. So the problem appears to be terminal.
Thanks guys for trying to help.
Bernie
I recently upgraded to the Cyanogen test 5 on my black G1. About a week ago, the screen started fading and blanking out. I restarted the phone and the touch screen was no longer responding. I did a full wipe with no change, then reflashed a different rom, still with no change. I reflashed the dreamimg which sort of reset it back to factory oe rom, but it's still not responding to touch input.
Any suggestion on what I should do?
Thanks!
see my thread here, currently active, same problem, working on it for a week!
http://forum.xda-developers.com/showthread.php?t=684711
Probably a dead touchscreen is the problem. tmo tech said to do a factory reset, and if that didn't fix it it was probably hardware. Luckily I have insurance, which apparently extends the factory service indefinitely, so as soon as I can get back to stock they'll cover it.
1. if you are under warranty, please help me figure out how you get back to stock, because it ain't working for me.
2. if you aren't, I guess you buy a new phone.
3. If you wanted to hustle tmo, you could just add the insurance, use it for a month or so without a touchscreen (not all that inconvenient with no screen lock, especially if you can use androidscreencast, droid explorer, adb and fastboot), after you've had the insurance for a while you could then call tech support and see. I'm not sure if that will work or not, I've had insurance since I've had the phone, maybe that's why the do warranty replacements, Just a thought.
If you have a hard time figuring out how to do some things without a touchscreen, let me know, I've been figuring out workarounds the hard way!
*edit, wait, you got the dreaimg.nbh to reflash? With what spl/radio/recovery combo installed? Because I can't get the nbh to flash!
I had amonra recovery, dangerspl and I believe the 26i radio, though I had recently been switching back and forth between that and the latest(22?).
I doubt the phone's still under warranty(I bought it second hand) as well.
Thanks for the response
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
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.
Hello,
Tried to look up some answers to my problem, however I'm not sure exactly what is wrong which makes any troubleshooting rather difficult.
I bought a new ADP1 a few months ago. I haven't had much time to play around with the phone, have just been using it stock and haven't even added any applications. There has been no physical damage to this phone, no drops etc.
Yesterday the phone locked up when I was using the browser and would not function. When I would try and reboot it, it would lock up at the first android screen and would fail to start up. I ended up doing a hard reset to factory defaults and the phone finally booted. After setting everything up again the phone seemed to be working fine.
A few hours later it locked up again while using the browser. This time no reboot/safe mode/factory reset would get it to boot. I can't even get to recovery mode or even get the phone to attempt to boot up. The screen remains black and the phone will not power on. It won't even charge when I plug it into the charger.
Not sure how to proceed here and I can't seem to find any information in regards to RMA, it is still in warranty.
Any help would be greatly appreciated.
Take out the battery for hour or so put it back in and try again.. but this sounds like my issue What happen to Me is my mobo was crapping out and eventually just died on me
Sent from my Nexus One using XDA App
Yeah, the mobo going to **** was my original thought.
I already tried taking out the battery last night for about 3 hours, it still didn't work.
Guess I'm going to have to look into an RMA, I hear they are a pain in the ass. The phone is still within it's 1 year.
Yea I would get that done quick
Sent from my Nexus One