Stuck at htc logo - G2 and Desire Z General

So I have had my g2 since Friday and have been loving until today I have had no problems with it except the hinge but like everyone says that's how its suppose to be, but today my voice search wasn't working for some reason so I decided to turn off my phone, and turn it back on but when I turned it on it was stuck at the htc logo and never loaded, so I did it again same thing so I went into fastboot and rebooted the phone from there and it finally loaded but I tested it out again and it gets seems to get stuck on the logo a lot and loaded a few times, does anyone else get this problem? Should I return it for a new one?
Sent from my T-Mobile G2 using XDA App

tdtylert said:
So I have had my g2 since Friday and have been loving until today I have had no problems with it except the hinge but like everyone says that's how its suppose to be, but today my voice search wasn't working for some reason so I decided to turn off my phone, and turn it back on but when I turned it on it was stuck at the htc logo and never loaded, so I did it again same thing so I went into fastboot and rebooted the phone from there and it finally loaded but I tested it out again and it gets seems to get stuck on the logo a lot and loaded a few times, does anyone else get this problem? Should I return it for a new one?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Happened to me as well, a full restore and wipe did the trick and I have not had the problem since
Sent from my T-Mobile G2 using XDA App

Related

Screen going blank

Sometimes the screen goes blank and is compleyely unresponsive, I have to pull the battery to get it to work again. Is this a common problem? I haven't seen much of this on these forums.
Sent from my T-Mobile G2 using XDA App
Happened to me this morning. Actively using phone then... nothing. Blank screen, no response to the power button. I also had to pull the battery to get it working again.
First time I've seen this in seven days of having the phone.
Ya'll overclocked?
Sent from my T-Mobile G2 using XDA App
Happen once but it was fue to a video on a web page and it froze the broswer then I got a phone call. And the screen just stayed black.
But like me said it only was that one time
Sent from my T-Mobile G2 using XDA App
Had it happen to me twice today, kind of annoying and not overclocked.
Sent from a Visionary temp rooted G2
I haven't overclocked it yet. I'm kinda waiting for perm root before I start tinkering with that. This has happened to me twice so far.
Sent from my T-Mobile G2 using XDA App
Not overclocked either.
Sent from my T-Mobile G2 using XDA App
Came here to see if anyone else was having this problem.
It has happened to me about 3 times over the past couple weeks. Unresponsive, blank screen (powered off?), have to pull the battery before it will restart.
Stock G2
r the people with these daily problem temp rooted? Also maybe its ur apk you u have installed? Nut never know, I heard there is a few problems with first batch g2 just like all elec. things
Sent from my T-Mobile G2 using XDA App
Happened to me today as well. I wasn't running rooted at the time, and the TMo forums have people reporting this problem as well.
Unfortunately, at the time this happened, I didn't think to throw 'adb logcat' at it to see if the phone had stopped responding all together or it was some kind of hardware issue.
hmm weird, I was having a lot of issues when I OC to 1.42ghz, black screen, phone freezes, having to pull battery each time.. very annoying, so i just went back to 800mhz and it runs amazing
This has happen to me numerous times before i forced the ota update and i only got the problem once after the update I seem to get it most when i press the power button to turn the screen on it let me slide to unlock it but i shows a black screen and i can only see the notification bar at the top and it is totally unresponsive for a good 10 seconds untilli keep pushing the home button and eventually the black screen goes away for me
and i was oc to 1ghz before ota but not yet oc bak yet so it leads me to believe that the oc was not the issue because i got the same black screen with out being oc
After the update all the glitches went away. It has been running like a champ since.
Sent from my T-Mobile G2 using XDA App
when my screen goes blank I hold down the power button till Power Off Prompt comes up then hit back. It always fixes my blank screen
Are any of you using NoLED... Because I had that problem, and when I un-installed it, the problem went away

After perma root phone won't shut down completely.

After getting perma root and installing Bacon bits 0.3, when I want to turn my phone off completely it instead just boots back up into the recovery. Does anyone else have this problem or have any ideas how to resolve it?
Sent from my T-Mobile G2 using XDA App
I have no idea, but noticed it too...
Sent from my T-Mobile G2 using XDA App
I am apparently having this problem as well now. I never noticed it before and even after a battery pull my phone seems to boot back into recovery. Any help with this problem would be greatly appreciated. Thanks in advance!
One thing to note is that you need to make sure that you don't have it plugged in and charging. It's known to boot on its own when you do that. I'm not sure if that is a bugged feature or not, but I also have Bacon Bits installed and can shut down fine.
Although, my phone stays on all the time.
Sent from my T-Mobile G2 using XDA App
Ok just tried to turn off my phone with it unplugged and it did not turn on to recovery. So kind of a boo bug for now but I am sure that it will get worked out.
Heh... I'm guessing you all have Clockwork Recovery installed? That's the problem. At least, when I switched to the test keys recovery, it wouldn't constantly start back up with any power regardless of how I shut down.
hmm..i have baconbits installed and dont have this problem. ill look into it

Back button just became erratic!!! Help!

My capacitive back button is going crazy!!! I figured it was just the rom or a program running in the background. So I rebooted into recovery and it happened then too!!! Definitely a hardware issue. I didn't drop the phone and I wiped the screen clean. So I'm not sure what the problem is. Is there any way I can disable the back button completely and remap it to the Search button? I never use the Search button, so this would work for me. Please help!
I have had this happen to me, it would randomly act up. After two weeks or so, it just stopped happening.
I have seen reports on forums that some people have tightened the screws on the back of the phone and had luck with that fixing the problem.
Sorry I can't be more helpful.
Yeah happened to me too when I first rooted it, found out it wasn't the root that did it but an application that I put on there that was not compatible with the phone.
I had the same problem too -- I posted this a few days ago on another thread dealing with this problem. I'm not sure why it's happening but it many people think it's a software incompatibility issue. I did five hard resets and the problem went away. Most people who tried the hard resets only did it once, and the problem persists. It'll even persist in recovery. I think you need to do enough hard resets until the problem disappears. Mine now is glitch-free -- good luck.
http://forum.xda-developers.com/showthread.php?t=952535&highlight=back+button+issue&page=2
Nexus S
Rooted Stock 2.3.1
T-mobile unlocked
Try installing the stock 2.3.4 just for trial. The new update fixed all my issues with the back button
Sent from my Nexus S using XDA App
I had this happened on a recently purchased nexus s. It was on 2.3 stock, and the back button just went crazy, the screen would flicker on and off, and no matter how many factory resets I performed, the problem was still there. I eventually returned it and the new nexus s has been problem free.
SphericalPuma said:
I had this happened on a recently purchased nexus s. It was on 2.3 stock, and the back button just went crazy, the screen would flicker on and off, and no matter how many factory resets I performed, the problem was still there. I eventually returned it and the new nexus s has been problem free.
Click to expand...
Click to collapse
Your new nexus s are using latest version or not?
I have this issue sometimes too. Mine doesn't go crazy though, it just becomes unresponsive and dark. I have to wait a couple of seconds and then it comes back. Kinda of like the phone freezing while the damn button come back.
Running Nexus S4G 2.3.4

My G2 gets stuck in a sort of boot loop sometimes...

If I try and reboot the phone instantly it turns on, gets to the lock screen, and after anywhere from 4-10 seconds, it turns off and suddenly I'm looking at the LG then AT&T boot splash again. If I hold the power button to force power off and let it sit, off, for a minute or two then turn it back on it works just fine.
I think it has something to do with the rooting process. I never got the original chinese superuser app removed and the new superuser app working properly and had to re root it a couple of times, then eventually gave up and left both of them on the phone and didn't try to remove the chinese one.
I'm not sure what to do since I can't just boot into rom manager and flash a stock rom over mine like I would have to fix problems with any of my older android phones.
Are there special steps I might have missed when trying to remove the chinese superuser app? Maybe I did something out of order by accident? I followed the thread on G2 => General to the letter...
EDIT: I also have a few apps frozen in Titanium Backup, but I don't think any of them could cause this. This is the list of frozen apps:
-Featured Apps
-File Manager
-LG Backup
-LG Keyboard
-LG Keyboard Black Theme
-LG Keyboard Lovely Theme
-LG Keyboard Natural Theme
-Music 4.2.9
-Music 4.1.13
-POLARIS Office 5
I think it almost definitely has to do with the root issues I had earlier.
Is this guide the only way to return to bone stock firmware on AT&T? I tried following it a few days back but I don't think I ever got my phone into recovery mode.
This happened to mine when I went into the service menu and made changes to the thermal settings. After forcing it off and waiting about 10 minutes, it booted up fine.
Sent from my LG-D800 using Tapatalk 2
Thanks! Which settings and what is the default? I went in and changed the things I thought I changed originally when u did that but I'm not totally sure if I changed them back to what they're supposed to be.
Sent from my LG-D800 using xda app-developers app
zxrax said:
Thanks! Which settings and what is the default? I went in and changed the things I thought I changed originally when u did that but I'm not totally sure if I changed them back to what they're supposed to be.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
The default for High Temperature Property and Thermal Daemon Mitigation is OFF. I got gunshy and turned them back to OFF and haven't fooled with it since.
Sent from my iPad using Tapatalk - now Free

S4 i9505 stuck on Samsung Logo

This has started to happen (from what I've noticed.) I replaced an LCD on an S4. Worked fine no problems, tested and turned it off and prepared it for sale. I turn all my phones on for the photo and noticed it would hang on the Samsung logo and wouldn't boot into recovery only download.
I thought it needed restoring via Odin and would freeze at "Get PIT for Mapping..." I thought great, the eMMC randomly died on me. Then, I tried to turn it on the next day and it worked, updated & left it turned on until the battery was low and turned it off.
Now, it's doing the same again.
I highly doubt anybody on here will know as it looks like people focus on iPhones but does anybody have a clue why this might be happening?
Thanks
Urban Designs said:
This has started to happen (from what I've noticed.) I replaced an LCD on an S4. Worked fine no problems, tested and turned it off and prepared it for sale. I turn all my phones on for the photo and noticed it would hang on the Samsung logo and wouldn't boot into recovery only download.
I thought it needed restoring via Odin and would freeze at "Get PIT for Mapping..." I thought great, the eMMC randomly died on me. Then, I tried to turn it on the next day and it worked, updated & left it turned on until the battery was low and turned it off.
Now, it's doing the same again.
I highly doubt anybody on here will know as it looks like people focus on iPhones but does anybody have a clue why this might be happening?
Thanks
Click to expand...
Click to collapse
Maybe you can wait in 15 minute. it happens today make a upgrade firmware to Lollipop, The logo Samsung stuck in 15 minute. and later work well.
Abcastillo said:
Maybe you can wait in 15 minute. it happens today make a upgrade firmware to Lollipop, The logo Samsung stuck in 15 minute. and later work well.
Click to expand...
Click to collapse
It's already on Lollipop, fully updated
Reboot to recovery and wipe cache,it should work?
If not,then unmount cache[emoji57]
Sent from my GT-I9505 using Tapatalk

Resources