Related
Any help would be greatly appreciated.
I have a launch day Nexus One running CM5.0.5.3, the OC/UV kernel, and the EPE54B radio.
It has all been running great until today. I took it out of my pocket and it was warm (not hot) to the touch. I noticed the screen was blank but the buttons along the bottom were illuminated. I tried resetting it (power+volume down+trackball) and that didn't do anything, so I pulled the battery. When I rebooted it, it seemed to take a longer than usual time at the initial boot screen, and then went to the animated screen. It stayed on the animated screen for quite a while and then froze. It's stuck on the X mid-formation.
I then booted into the bootloader (which reacts like normal) and went into recovery. I re-flashed CM5.0.5.3, no effect. I wiped cache and system and re-flashed. Nothing. I did it again, and it finally booted up but I could only select things with the scrollball. The volume rocker worked fine, but the touchscreen is completely non responsive.
If I let it sit at the boot screen for a while it will go black eventually and time out.
I'm at a loss. I'm in the process of downloading a stock ROM and am going to flash it next. Anyone have any suggestions? My bootloader is (obviously) unlocked, so I'm worried about warranty work
Update: Just got it to boot (with the stock ROM) and I've got a warning screen saying:
Sorry!
Process system is not
responding.
[Force close] [Wait]
Any ideas?
Reflash CM 5.0.5.3 and then post back
Ok, re-downloading now.
Just flash in recovery?
Flashed in recovery (after wiping)
The phone stays on the stationary initial boot screen (four bars) for about a minute and a half and then goes to the animated cyan X. It stays there booting for probably two minutes before stopping mid-animation. If you let it sit there for a while the screen will time-out, which you can bring back with the power button. Sometimes when you hit the volume rocker you can hear the beep beep but nothing shows on the screen.
What the hell is wrong with my phone?
After an obscenely long time I got it to boot up.
Touchscreen is not responding, trackball is not responding, I have a question mark on the battery indicator, and no service.
I can't unlock the screen because of the non-functioning touchscreen. Live wallpaper is running great, it makes the sound when USB debugging is connected, it just won't react to any input.
I can, however, establish an ADB connection. It shows up on the device list and a remount succeeded.
Would reflashing the radio be of any benefit?
Dang the touch screen is unresponsive? I'm not an expert, but i'll try to give you some ideas.
I had some trouble once and I used settings-privacy then erased everything from within the OS. Then I reported to the screen just before going into recover and hit clear storage. Then went into recovery and wiped everything that I could. After that, flash the Rom that you want.
I've done a full wipe to no avail.
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Scaaaary!! But hey, it happens. I would also try wiping for EXT on the SD card if you have been using apps2sd.....May not hurt, mights well try everything.....
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
liam.lah said:
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Click to expand...
Click to collapse
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
mortzz said:
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
Click to expand...
Click to collapse
Many people have posted that they got a replacement even with an unlocked bootloader. One guy I heard said they charged him $55.
Either way, you can probably get a replacement.
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.
Hi All,
While on a business trip last week, my Tilt 2 (at the time, running the April 14 Energy ROM), my phone--for lack of a better word--crashed on me.
Everything had been working fine, I was sitting there with my phone connected to my laptop via a USB cable, and out of the blue, for no apparent reason, my phone re-booted, and never came back up. It would get to the splash screen, start loading the OS, reboot mid-stream, and get stuck in a loop. Weirder still, if I pulled the battery, let the phone sit, then put the battery back in, hitting the power button did nothing--even with the phone plugged in to power. On top of that, even if the phone was off, after a few minutes, it would power itself back on randomly, and get stuck in the re-boot loop. Very weird.
So, when I got home, before heading to the AT&T store and asking for a replacement, I thought I'd try to restore the phone myself.
At first, I pulled the battery, then stuck it back in, and sat there holding the volume down button, waiting to put the phone into bootloader mode. That worked, but even in bootloader mode, it would randomly re-boot. So, I started the process again, and immediately plugged the phone into my computer while in bootloader mode and ran the Task 29 tool. That completed properly.
At this point, I popped in another battery I had laying around and just let the phone charge for a few hours. Then, for the heck of it, I re-ran the HardSPL tool. Re-Flashed to the .91 radio (it was already on the phone), and then flashed to the latest Energy ROM.
Since then, my phone has been better than ever. Seems faster, battery life is better (Went three days without having to charge it), no dropped calls, and no weirdness with the latest ROM (that I've found so far).
Does it pay to REALLY start fresh from time to time, and re-flash everything on the phone?
Thanks for any input.
I have no idea, but hopefully the WinMo experts will see this and have an idea, so here's a bump for you. Most of my computer expertise revolves around Unix, Linux, and a bit of Windows, not so much these phones.
I do know that task 29 is awesome, though. It seems like DBAN for your phone...
DBAN=Darik's Boot and Nuke. Look it up.
I don't know what happened with your phone, sounds like something broke in the area of booting.
I don't think you should need to re-flash HardSPL radios just for the sake of it, but I'd strongly recommend task29 every time you flash a new ROM.
bricked my TP2
My TP2 seems to have a similar problem which I haven't been able to fix it just yet. The bootloader reboot loop is too short to succesfully run task 29 and flashing it using the microSD gets stuck around 40%
during bootloader mode there's an unreadable errormessage since it's on the same line as some of the usual information.
any thoughts/suggestions would be very welcome since i can't afford to send it to the factory.
cheers.
By the way my phone is a HTC Pure, that was security and sim unlocked, at the time it went down was running the latest Energy.TOPAZ.29022.Sense2.5.Cookie.2.0.GTX.Jul.04.7z ROM. With no recent updates or installs.
Ok my phone was in my pocket for the morning and when I pulled it out it was dead and wouldn't turn back on. Plugged it in to charge and once charged it will only boot to the white screen with the little red numbers in the bottom. It takes very little time to get to this point and once here it is unresponsive to any buttons pushed. I can leave it like this and it will just get hot and wear down the battery, I have only left it like this for ten minutes, just to see if it would come out of this stage.
After searching and reading all the brick / won't boot posts I could. I tried to hard reset, which works and I can get to the bootloader screen(striped screen). Then re flashed to the newest hard spl and have flashed three different versions of Energy, currently trying MaxSense. But nothing has gotten it past the boot screen. All flashes were done with the USB through my computer and the SIM and SD cards have not been in it.
I just don't get how it bricked in my pocket, it had worked fine for a month on the same Energy ROM with no issues and I had not downloaded or installed anything new recently.
Just miss my phone now, any help would be greatly appreciated.
Did I post this in the wrong area? 3 days 50 or so views and nothing, this sucks!
I take it this is the wrong area for this post as it has gotten a few views, but no responses. I should probably move it and see if that helps.
This sucks and I am disappointed, I'm done with this post, I give up!!!
I have a paperweight for a phone and I hope no one else has this issue, because no one on here can help.
Have checked as many threads and post as possible - And I think I have royally screwed up. Problem is My HTC Google Nexus One will only vibrate continuously until either the battery or power is pulled. I did root the phone, and installed Clockwork Mod recovery making a full back up of the factory image. This was as far as I got in my quest to upgrade the OS to something more modern.
The phone worked for a day and a half after rooting, and worked fine after installing ROM Manager. But i kept getting prompted to upgrade from 2.1 Eclair to 2.3.6 Gingerbread. So I tried to run that upgrade and it failed with a triangle with exclamation mark. I rebooted and thought nothing of it. Later I installed Snapchat, and an hour after that the phone wouldn't respond to accessing 'settings' or any other system folder. So I had to pull battery. Tried to reboot and it stalled at the starting animation and that was the last action I saw from both the screen or otherwise.
So although I read there is a risk to rooting your phone, I figured it went smoothly as the phone functioned well for a day and a half.
Anyone have any thoughts on this? I read if you can't get to any of the 3 boot screens then you're bricked. I just can't understand how it happened so easily?