Database Develop

Nexus One stuck in bootloader

Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.

Reflash the stock ROM and see if that helps.

mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\

Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?

Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?

Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?

So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?

Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.

Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!

Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying

i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot

Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.

so is this because on invisibleshield? cuz i just ordered mine today!!

I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.

I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.

Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.

[Q] G1 keeps restarting

my g1 keeps on restarting after i downgraded my phone to rc29 so i can root it. this never happen to me before. if i have my charger plugged into my phone, when the phone loads and passes the g1 screen onto the android screen, it'll automatically reboot itself. if my charger isnt connected. it wont reboot, it'll just turn off. i have 2 g1s and both battery are working perfectly. what am i doing wrong? i can enter to recovery mode and fast boot without any problem. DREAMIMG is installed correctly also. a little help will be great! thanks in advance

I've just ran into this myself. I am running Biffmod 2.0, went into UI settings, changed LED notification for missed call, it rebooted, changed it back, still rebooting, rebooting itself ever since. Put it on charge as I have to go out. Picked it up, missed call. Rebooting. Went into Menu to look at LED settings, still rebooting.
:/

Give up. GAME OVER.
Well, not so dramatic. Short answer for me = Hard reset. Not much on there anyway. Done too much reflashing for that.

Scorpia said:
Give up. GAME OVER.
Well, not so dramatic. Short answer for me = Hard reset. Not much on there anyway. Done too much reflashing for that.
Click to expand...
Click to collapse
all i know that it's not bricked. there has to be a way to fix it.

WEIRD! i got it working now. took the phone apart to the main board and put it back on slowly. and WOILA! it worked lol

Not booting (into anything)

My phones battery died over the weekend, I got it charged back up, the phone was acting real sluggish so I restarted it, came back a few hours later and noticed it was still on the white HTC screen, I watched it for a few minutes and noticed it would sit on this screen for about a minute, then go dark, then back to the HTC screen and we go round and round.
I tried hboot, all the options do this. Fastboot, recovery even factory restore all trigger this infinite loop...
What has happened? How can I fix this?
Note that it was a stock phone, no mods, no custom ROMs or anything else. It was OTA updated to ICS about a week ago, and has been fine since then.

echodreamz said:
My phones battery died over the weekend, I got it charged back up, the phone was acting real sluggish so I restarted it, came back a few hours later and noticed it was still on the white HTC screen, I watched it for a few minutes and noticed it would sit on this screen for about a minute, then go dark, then back to the HTC screen and we go round and round.
I tried hboot, all the options do this. Fastboot, recovery even factory restore all trigger this infinite loop...
What has happened? How can I fix this?
Note that it was a stock phone, no mods, no custom ROMs or anything else. It was OTA updated to ICS about a week ago, and has been fine since then.
Click to expand...
Click to collapse
So can you get to the bootloader and send fastboot commands?

Sorry I am not a modder or anything like that, do you mean select the "fastboot" option?
I tried running fastboot reboot from my PC while it was plugged in and my phone was in the hboot area, and it just says "waiting for device" and never does anything.
If I select "fastboot" from the hboot menu the phone restarts, a bar goes up the side of the HTC screen then about 30 or so seconds later it goes black and repeats process.

Ah, yes I can. I figured it out, plug into USB, select fastboot, then it goes to USB. I was able to reboot the phone.
EDIT: Tried running the update from HTC's website, took it about 5 - 10 minutes or so. It completed without issues, however the phone is still doing this infinite rebooting cycle...

You mean the RUU? And for ICS? That is supposed to be the ultimate method to unbrick and return to stock. Sounds like the OTA messed something up. When you say go dark you mean the screen goes of then it comes back to the HTC screen? This is probably obvious but have you tried a battery pull? Taking out aim card anything is worth a shot.
Sent from my HTC PH39100 using xda premium

Yes the RUU update from HTC's website. The phone started this morning without issues. Then after a restart it starts the whole cycle over again.

[Q] [HELP!]

I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.

GreenMunky said:
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
Click to expand...
Click to collapse
If a factory reset does not fix the issue, all I can suggest is find the thread "Return to Stock" and follow the instructions to flash the entire stock SBF for your carrier. This should fix any corrupted files, if present. Either option WILL erase everything, so backup anything you need first.
Good Luck

Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?

KJ said:
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
Click to expand...
Click to collapse
Nope, phone had been off the charger only a few hours, still had 85% or so. I actually tried plugging the phone in while it was booting up to see if an extra jolt of juice would somehow help it to fully boot up... made no difference. After 6-8 failed boot attempts, it finally booted up and has been running fine since... although I have yet to try to manually reboot it.

Well, if it acts up anymore...I'd consider a full wipe and return to stock. Same android version you're on now of course.
Otherwise...probably a fluke. ?

Recovering from the dead

So, I was clean flashing Titan Prime back into my XT1064 after testing CM12.
Everything went well, same apps, same configurations as always, no major changes.
I was about to reboot the phone when it did it by itself.
The boot screen (you know, the white one that burns your eyes) showed up, then it went away, and then oh surprise!, it came back again.
So the phone was in this bootloop within the boot screen.
I tried to enter to the Bootloader and the key presses (Power + Volume Down) did not work.
Every time I would try that, the phone screen would stay off for as long those keys were pressed down, and then, Bootloop.
After many tries I was about to let the phone stay in the bootloop until I find a solution here on XDA.
But I tried one more time, and lo and behold, it went into the Bootloader.
From there everything went as normal.
Now, the question is, could I have bad sectors?, could the Bootloader be corrupted?, could I have a ghost trapped?.
Thank you for answers and/or ideas.
And if any of you happens to be in my same situation, do not give up, let it be, try many times, and it finally will work (hopefully)

Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.

Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.

Tel864 said:
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Click to expand...
Click to collapse
You do everything right, the phone gets screwed, it gets fixed, and the problem is something no one else has had so you have no freaking idea of why or what it was.
It is not my power button, the only times I use it is when I turn the screen on, and it would not be the reason because it made a difference when it was pressed.
I will try some fastboot commands to scan sectors, but I need to remember how they worked. The last time I used them it was when I had a Galaxy Note 1.
Lars124 said:
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Click to expand...
Click to collapse
As noted on the first post, I did not do anything out of the ordinary. Same apps, same configuration as always.
The good thing is that I now can say I have every app that I need, with the configurations that I need, so I almost never need to change.
Let's hope it will not happen again.