Nexus One powers up only one time in ten hours - Nexus One Q&A, Help & Troubleshooting

Hi all,
I got a totally silly problem. I have propably broken Nexus One with strange symptoms. I dont know anything about the flash-history of this device. It was sold as defect.
I received it yesterday. Put the battery in, hold power button, seems to boot up, the colored X appeared. Then nothing happend, it freezed. Then I did everything to boot up again, to get in Bootloader etc. I tried to charge, the LED didnt light up. Tried another (mine) battery, nothing, no charge process, no boot up. It stuck. I put an old Froyo PASSIMG.ZIP (PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed.zip) on sdcard, so it will install on the next/first working fastboot try. But, no chance so far, it didn't boot.
Then I removed the battery, put it on a table. Today in the morning, after about ten hours, I put the battery back in, hold VolDown and pushed the power button. It boots in Bootloader - wtf? - BlackRose is installed. It tried to install the Image put on sdcard before. It got stuck with propably 10% of checking.
After two hours I removed the battery and it didn't boot up again - I will try it in the late evening again.
The device has 8 months of warranty left, and I'll send it to HTC, but before that I want to remove the BlackRose'd Bootloader. So on next fastboot-bootup, hopefully it comes up with it again, I want to flash back the stock HBOOT (d6096cac5e9f.signed-hboot-0.35.0017.zip). Propably this will remove all problems I have, but I don't think so.
Now I want to get sure if you would go the same way or if you have an idea what is causing this freaking behavior.
Thanks so far!

Related

[Q] Strange Reboot Loop, searched forum Not Addressed

Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD

[Q] HELP!! Stuck in LG boot logo!!!

Please help! My rooted LG Revolution won't turn on. When I unplugged it from the charger this morning I powered it off. when I went to power it back up all it does is flash the LG logo and do a little vibrate like it is force closing! I have 2 days left before I can no longer return it. I did several battery pulls also with no luck. thanks in advance!
tchabalie said:
Please help! My rooted LG Revolution won't turn on. When I unplugged it from the charger this morning I powered it off. when I went to power it back up all it does is flash the LG logo and do a little vibrate like it is force closing! I have 2 days left before I can no longer return it. I did several battery pulls also with no luck. thanks in advance!
Click to expand...
Click to collapse
Did you install Clockwork on it, or just rooted?
If you only rooted it, try performing a factory reset.
This can be accomplished by holding volume down and power until you see the screen change to "Clear data and factory reset?".
Press power to confirm.
You will lose your data, but your phone should return to normal.
Just rooted, no clockwork. I will give it a try! thanks!
Tried your suggestion...just keeps flashing and vibrating. Any other suggestions?
Did you ever see the factory reset screen?
No I didn't. just the LG logo flashing and the force close vibrate. the only way I can get it to stop is to take the battery out and put it back in. Then when I hold the voume down and the power button it just starts doing it all over again.
tchabalie said:
No I didn't. just the LG logo flashing and the force close vibrate. the only way I can get it to stop is to take the battery out and put it back in. Then when I hold the voume down and the power button it just starts doing it all over again.
Click to expand...
Click to collapse
make sure you are holding it long enough. You have to continue to hold the power and vol button for sometime before you get the recovery screen.
As rooting will generally not brick a phone (it is the recovery mod that generally bricks), if you cannot get it, take it back tell them you woke up and it was on the charger like this. They should exchange it with out issue. (Do not mention that you rooted the phone)
It sounds to me like your phone is defective, it happens.
Another option is here: http://forum.xda-developers.com/showthread.php?t=1120062 .
I can walk you through it on IRC tonight if you're on around 12PM Pacific Time...
If not, there are guides for using LGNPST on the internet.
Good luck!
Thanks! Held the buttons down for a full 3 minutes and nothing. Is that long enough? Read through the other info you posted and boy does that look scary! LOL! I will try tomorrow when I have more time. Or maybe I should just return it since I have only had it for 12 days
try pulling the battery and holding the power key for about 30 seconds. my original droid use to do this from time to time and it always worked for me.
Thanks. Tried but it did not work. Ended up just returning it and getting a new one. Now I can start over! LOL Just came from the Samsung Fascinate and was pretty proficient in flashing roms and kernels. But I have to admit that I am a little confused with the process on the Revolution.
Not sure boot problem is related to root
I've had repeated problems with not being able to boot my Revolution. This has happened consistently no matter which ROM I've used. I've factory reset and tried Decrap and Revolt both. I can reboot my phone fine, but if I ever turn it off overnight, I go back to a blank screen in the morning.
It seems a number of non-root users have this problem.
https://www.youtube.com/watch?v=IOGM__SQB6Y
I'm not sure if having a low battery contributes to the problem, but I do know that Clockwork works better with a full battery.
This morning is the first time, however, that I have this exact problem. For a few times this morning I was able to get to clockwork and restore different ROMs, but always to the same blank loop during boot. Now not even able to get to Clockwork or Factory Reset. I'm headed in to Verizon to try for a replacement. I'll let you know if they make any noises about rooting.
Getting back into Clockwork
Update: I ended up getting back to Clockwork. Can't say exactly what did it, but what seemed to work was:
1. Charging the battery fully overnight
2. Removing the battery and holding the power button down for 30 seconds
3. Leaving the battery out for some time, about an hour I guess
4. With the battery still removed, plugging the phone in and allowing the bottom lights to flash about 10 times
5. Replacing the battery, holding down the power button and volume down.
After a full day of not being able to get into Clockwork, I was able to get in and do a factory reset.
Returning Rooted Phone to Verizon
FYI, I returned a rooted, stuck in boot loop phone to Verizon yesterday. In the store they arranged the return and did not ask about or look for rooting in any way.
They did try a factory reset, which was not working in any case, so no signs of Clockwork.
Same problem, different results.
I have a ROOTED LG Revo, but the first one I owned had the same problem. That one was NOT rooted, so must just be an LG thing. First phone had stock android 2.2, and this one has STOCK 2.3.4 ( after OTA ), and is just rooted with simple memory management and font tools. I WAS able to Hard Factory Reset, but the same problem still existed after reset. ADB cannot even recognize the handset. Boots with animation, stops halfway through, reboots into blank screen and freezes. RETARDED!!! This will be the second handset being sent back in as little as a month. I bought the REVO the DAY it came out, and loved it. But now I don't. No love left. I'm getting the Droid Razr!
timus5 said:
I have a ROOTED LG Revo, but the first one I owned had the same problem. That one was NOT rooted, so must just be an LG thing. First phone had stock android 2.2, and this one has STOCK 2.3.4 ( after OTA ), and is just rooted with simple memory management and font tools. I WAS able to Hard Factory Reset, but the same problem still existed after reset. ADB cannot even recognize the handset. Boots with animation, stops halfway through, reboots into blank screen and freezes. RETARDED!!! This will be the second handset being sent back in as little as a month. I bought the REVO the DAY it came out, and loved it. But now I don't. No love left. I'm getting the Droid Razr!
Click to expand...
Click to collapse
Please don't necro threads....

[Q] stuck at "dual core" but now can't even fastboot?!

I bought one of the refurb'd bionic's a couple months ago. I've rooted and masked the wifi tether, but nothing else, no custom ROMs or anything. phone's been working great for the past seveal weeks since those changes were made, several reboots, etc. no problems until last weekend.
I randomly found my phone stuck on the "dual core" screen one morning. it must have rebooted overnight and been that way for several hours as it was quite hot. I did a battery pull and tried to turn it back on, got nothing. plug it in to the charger, nothing, no leds, nothing. several battery pulls later, still nothing. try to enter fastboot/bootloader by pressing power + volume up/done, nothing. plug it into the computer, nothing.
I'm sorta fearing its been hard bricked (though I have no idea why... i wasn't loading ROMs), except, the other day, after leaving the battery out all night, I was able to get it to turn on, it booted up to the home screen, but before it was usable, rebooted and was stuck on "dual core" again. messing with it some more, I eventually got to the bootloader screen. I wish I had siezed that moment, but i didn't. Messed with it some more yesterday, saw the 'dual core' screen again, but couldn't get it into fastboot. its very hit or miss and I can't do it consistantly, but on rare occasion, it does seem to want to come back to life.
any advice on what happened? where to go from here? and if it can get it back into fastboot? I'm hoping i can and rsdlite will recognize it and I'll try loading 902 fxz back on it, but sure could use some advice to save this phone... no insurance and it was a refurb thats been rooted, I don't think verizon will be too much help.
THanks
-Rob
Try this
Little known hidden key (actually button) sequence: press and hold both volume up & down then hold the power button ten seconds (five should work, but ten always gets it). You should boot into fastboot mode, then flash 902 using a USB cable. You do NOT need to delete data! Check the batch file and REM out or remove any line that says it will. Worst case, Motofail after that will give you access to your latest CWM backup, assuming you have one, just restore that once you have root.
What he said and also you may need to charge your battery.
Sent from my DROID BIONIC using Tapatalk 2
It could just be a dying phone, I came across an Atrix basically in the same situation. The radio in it had died, so the only way to boot the phone was to skip booting the radio, but if you hit the phone application it would crash the phone.

[Q] HD7 vibrates 7 times, gold card fails

Hi Guys,
I bought an HD7 from UK with a broken screen. Just installed the screen, and tried to switch on the phone for the first time. It was stuck on the HTC logo. So I pulled the battery out, and tried to reboot, but now it vibrates 7 times and does nothing more.
BTW. I made it to boot into bootloader, and it shows the attached screen.
I tried to flash a stock NoDo rom with GoldCard, but it fails at the first step, saying:
"Radio.nbh - FAILED"
I've used the GoldCard on two other HD7s in the past, so I guess the problem lies elsewhere. Now I try to download an other original O2 UK rom, and see it it makes any differen or not.
Any clue about what could cause this? And how to resolve the problem?
Any clue about this problem?
A bit of update about this. Put the phone in a bag and put it into the freezer for an hour. After I switched the phone on, and it WORKED! Loaded up the OS, checked my emails and so on, but after around 5 mins (when it warmed up) it shut itself down, rebooted and vibrated 7 times again...
So it's a heat issue.
Also noticed that if I leave the phone for a while It loads up into bootloader, does what I want, but the more I use the worse it gets. First it freezes, then won't even switch on.
Is it a CPU failiure?
VTS_Tibi said:
A bit of update about this. Put the phone in a bag and put it into the freezer for an hour. After I switched the phone on, and it WORKED! Loaded up the OS, checked my emails and so on, but after around 5 mins (when it warmed up) it shut itself down, rebooted and vibrated 7 times again...
So it's a heat issue.
Also noticed that if I leave the phone for a while It loads up into bootloader, does what I want, but the more I use the worse it gets. First it freezes, then won't even switch on.
Is it a CPU failiure?
Click to expand...
Click to collapse
Maybe it is a bad assembly, why don't you reassemble the phone, all points to that... this happened after the disassembly, right?

[Q] [HELP] Something is SERIOUSLY wrong with my Moto G(boot loop)

So. My Moto G is completely un modded, not rooted, and is exactly stock how I bought it and haven't changed any of the software. My Moto G has been getting slower in the past couple of months with everything going slower than usual. I bought my phone in February 2014.
Yesterday while I was at school, in my pocket I had my phone. I felt random vibrations in timed cycles. So I pulled out my phone and had a lol at it randomly rebooted but came back to the home screen. As I started to use it just to send a couple of messages it rebooted again but this time after the reboot animations they just went on and on, what I've found out to be called a boot loop.
So I went home did some research and figured I would have to factory reset. I couldn't get into the phone therefore I had to do it externally. I got the the menu thing ( I think it's called fast boot menu ) and I wanted to select newer bootup or power up just to see if that would possibly stop the boot loop. I selected it and got into my phone, into setting and factory erased my phone.
Well I factory erased my phone and re installed the apps I on,y essentially use or NEED such a social media, within this time there was no unusual activity. Shortly after my phone randomly rebooted ( after downloading the apps ) and turned off, and then went in to the former boot loop! I was furious!
Well here I am, left it overnight for charge and it's been looping for 10 hours. I tried going back into the fast boot menu, the first time I got into it this morning I selected recovery in hope to reset it, however the screen said no command with the android and the exclamation point. The second time I got into the menu I tried 'Factory' and it just rebooted and back into the cycle.
At one point I did get into my phone however shortly after that guess what happened, it turned off and rebooted. And back into the vicious cycle.
I am led to believe it's the power button that's causing the problem ( correct me if I am wrong ) as when I did manage to get I to the phone I did try pressing the power button to investigate this and on some occasions in did lock the phone but in several others it displayed the power off popup and then turned off shortly after indicating that I was holding the button down which I definitely wasn't doing.
So where would I go from this? Do I call Motorola, try flashing a stock ROM ( it's completely stock ATM , I don't know how to do this so if I have to do this can you please explain briefly ) or try going back into the fast boot and go into recovery and try and get rid of no command ( if I can, and how ? ).
Please any help would be very appreciated!
Thanks in advance.
PS you don't think it's the back cover that's doing it because it took that off last night '
kevlarpatel said:
Do I call Motorola, try flashing a stock ROM
Click to expand...
Click to collapse
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.
doppelhelix said:
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.
Click to expand...
Click to collapse
Hi, I had a look online and came across a forum post saying it was a jammed or sticky power button and the poster stated to hit the power button side of the phone on a desk a couple times and it will go back to normal. I'm glad to say it did work after I hit it a couple times, as fast as ever now due to the reset!
I was wondering if I call Motorola would they give me a free new moto g out of it, as I see it as an opportunity to do so, or will they just prompt me to send it so they can repair it under warranty? Is it worth calling ?

Categories

Resources