Every time I reset or turn on my fone after shutting down, it will stuck at the logo boot up. It wasn't like that when I first bought the fone. Now it's getting worse and worse since the issue happens so frequently.
I have to take out the battery and put it back, then wait for about 3 to 5 mn before I turn the phone on.Then it would boot up as usual.
Is there anyone facing the same issue as I am? Any suggestion guys?
Are you experiencing excessive heat when this occurs? Also, can you give more info such as: does this happen only after recent charging or does it ever happen when the phone has been turned off for a long time? Was there any recent apps you installed or ROM changes when this started happening? Was there any potential damage done to the phone -dropped it, got it wet, or microwaved
When you say frequently, does that mean every time you restart? every other time? every five times?
Lastly, do you have any other issues/symptoms other than freezing at startup? Does the phone ever freeze during normal use?
i'd suggest you do a hard reset of your phone (hold down both vol up and vol down keys while powering on/resetting). that should fix the problem. if the problem still persists, it's probably some hardware faults.
Me too
My HD2 just started doing this too. It was fine for 7 weeks I have owned it. However, as described in this by OP, when doing soft reset would it would also get stuck on bootup logo. I'd have to remove the battery for a few minutes before it would bootup.
However, my HD2 also crashes and upon reboot then get stuck on bootup logo. It appears to crashes randomly eg not with any particular program or action.
I figured it was software issue so did hard reset. This worked fine. After hard reset the only software I loaded were Total Commander and Cookie Editor.
After Cookie Editor install I did soft reset and it got stuck on bootup logo. : (
So I did another hard reset but it hung up again upon reboot on bootup logo.
This appears to be a hardware issue. But has anyone else had same issue?
T-Mobile HD2
Stock ROM
Purchased July 6 2010 from Expansys
yes i am experiencing the same problem and i have uploded a video on youtube showing this! Yes my phone heats up when this happens..
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Stormrider75 said:
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Click to expand...
Click to collapse
It will retain whatever rom you are using
Htc Hd2 vodafone UK
HD2 issue
After some more searching it appears this is not uncommon for HD2. Its not clear to me if it is specific to T-Mobile HD2 or HD2 in general.
It appears to be a hardware issue. Although that is not 100% clear either. I find it hard to distinguish what some people report as 'freezing' which i believe is different to the issue described in this post which is 'hanging up' or 'getting stuck' on boot up screen - in my case it is the T-Mobile 'stick together' pink and white screen/logo.
(The 'freezing' issue that i believe is different to this 'getting stuck on bootup logo' issue appeared to have been resolved iwth new T-Mobile ROM - and I never experienced it on my HD2).
The resolution for getting stuck on bootup screen issue described here appears to have been to exchange HD2 (although some people exchanged up to 6 times and keep getting same issue!)
I think it is important to note that my HD2 performed fine for 7 weeks with lots of soft resets, hard resets, and lots of software installs (though no ROM reflashing) but within last week or so, start crashing randomly, then upon reboot get stuck on bootup screen/logo. This also became more frequent as time progressed. After doing hard reboot, the issue is now acute, eg it gets stuck on every reboot, and crashes more often.
This leads me to think some hardware has failed or degraded and is getting worse, maybe a connection/soldering etc?
However, is there any possibility that a ROM could 'degrade'? Can a ROM have a setting that is modifiable? (I know it is 'read only memory' but is it really?)
Anyways, love to hear from others on this issue.
Same problem here. Bought my HD2 in june. Cooked my own rom with Chucky's kitchen. Flashed different radios, hard resets, task 29 etc. Absolutely no problem. Worked fine for several weeks. But sometime it begun to freeze, auto resets, stuck at boot logo. It was getting worse. Even flashing stock rom it hungs at boot logo.
Now my HD2 is out for repair. Now waiting for returning. Hope they will change the motherboard.
several people have had their motherboards replaced and that has seemed to fix it for them. You'll probably have to fight with htc or your carrier, but should be able to get it replaced.
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
HD2 is an odd one
Thanks for replies. I really don't want to send it in .. but it will probably be the only way to resolve the issue. It will cost me courier there and back, and $20 'triage' fee .. total cost to me will be ~$100 just to have them look at it. Price of doing business I guess.
Anyways, I realized that one of my issues was that it was crashing when syncing. A little digging reveals that HTC Sense does something to all contacts when syncing first time putting a bit of html in contact notes field (weird but it is true .. its their way of reminding you bought an HTC phone?) So once I got it up and running, I disabled Sense and syncing went fine, no crashing.
(Btw, Sense also appears to do something with SMS msgs too so if you have lots it crashes on due to this reason too).
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Still, important point is that it was ok for 7 weeks, and then started crashing, more and more, even after hard reset, though some of issues may have been due to Sense (which is reported by many users).
It is still not a 'normal' thing for a $700 consumer device to have such erratic behaviour. So, given others have exchanged crashing handsets for new handset that has no issues points to underlying hardware issues as suggested above eg motherboard.
As comparison I also have HTC Diamond 2 which has been rock solid for 2 years of continuous use even with lots of software install, tweaking, reg hacks, etc.
Stormrider75 said:
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
Click to expand...
Click to collapse
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
genoki said:
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
Click to expand...
Click to collapse
Thanks. Btw I read before we can actually 'disable' Sense.
How do we do that?
Sense - go to Today
Go to Start - Settings
- iI you see the black HTC Settings (has 'Personalize' on top of items) then go to Menu and select 'All Settings' (this will show Windows Mobile's Settings. HTC Sense 'Settings' doesn't everything Windows Mobile Settings has or shows it differently)
- Select 'Today'
- Select the 'Items' tab in Today
- Check 'Windows Default' and click OK in top right.
This will 'swap' out HTC Sense 'today' with Windows Mobile standard Today screen and voila you will have 'disabled' HTC Sense and you are back to using Microsoft's Windows Mobile 6.5 version of Sense (not anywhere near as useful or neat-o to look at but hey they are pretty happy with it )
genoki said:
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Click to expand...
Click to collapse
Just by disabling Sense is not going to make it work. I had this problem with my HD2 also and without using Sense it seemed to be working (there were fewer crashes), but only for few days. My HD2 was getting worse day by day - it was not crashing only if it was not touched (it was crashing just cycling between Sense tabs or by initiating a call).
At repair center they told me (after three weeks of waiting) that the motherboard must to be changed.
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
I have my HD2 back. Took me 2 weeks, the repair center changed the motherboard and got an new IMEI.
Now all is working, no more stuck at bootlogo.
But i'm on stock rom (1.66) with 2.07 radio. No way to run Android with this radio. Hmm...
axman79 said:
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
Click to expand...
Click to collapse
I'm afraid as well to flash any custom rom now. For Android i need to HSPL and flash a 2.08 radio or greater to use it. But i'm stick on stock rom for sure.
I want to know as well if it possible to damage it by flashing customs roms ?
As i stated earlier, i flashed plenty of roms, doing task 29 etc., in the end stuck on bootlogo.
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Yah, disabling Sense hasn't stopped my HD2 from crashing eith. Without using Sense it crashed several times while using Opera and more than a few times while syncing over the past three days. Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
genoki said:
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Click to expand...
Click to collapse
Was flashing stock rom with stock SPL, was at the shop where i bought it and they send it. I told them it stucks at bootlogo. Repair center changed motherboard without any question. Cost me nothing.
genoki said:
Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
Click to expand...
Click to collapse
Ja ja, same here.
genoki said:
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Click to expand...
Click to collapse
Yes you will, but dont forget to flash back stock rom regarding SPL !
genoki said:
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
Click to expand...
Click to collapse
I want to know as well !
hey guys. I am so glad I found this post! I have exact same issues ith my HD2, it's driving me nuts.
I kept sort of log and described my problems in this post: http://forum.xda-developers.com/showthread.php?t=712729
I think I have to send my HD2 for replacement or repair.
Can you please tell me how can I get my phone fixed/replaced?
I got the US T-Mobile version, but I don't have account in T-Mobile. Can I deal directly with HTC? Where do I have to call to get RMA number etc.
I would greatly appreciate your help!
KML
This is the deal:
I bought my wife and I Vibrants back in February and from the minute I got it I started looking into updating from eclair.
I was following the info on xda after researching about rooting phones, so I rooted my phone using the Superonclick method. Just before getting ready to flash custom roms, I read that froyo was available through kies. So I did that. It worked well enough for me, so I updated my wife's phone as well and hers works beautifully. I also changed the home launcher to LauncherPro. love it.
Mine however has been going on the fritz. I'm in the middle of using an app or I'm doing nothing at but turning on my phone and the screen will be all black with nothing but the notification bar showing.
The media scanner is constantly running.
No gsm is detected.
I keeps vibrating after touching the screen.
No amount of turning it on and off gets it past that state.
It just randomly decided to start working on its own.
Any Ideas?
Should I unRoot my phone. I don't want to,
I'm still researching changing the bootanimation, (waiting for a Portal 2 theme, also researching how to do it myself).
SOS guys.
sorry if tldr.
I would suggest restoring your phone back to stock Via Odin, and starting fresh. The problem you most likely had is that you updated to Froyo through Kie's while your phone was rooted.
Or, at the very least do a factory reset on your phone.
But if you need to go the Odin route, just search the forum, can't miss it.
oh wow, I didn't know that was an issue updating while rooted. I must have missed something while reading (so many threads -_-).
Guess I have some more light reading to do...
thanks.
Did a little research, should I unroot my phone first before factory reset? or is there a method that will take care of removing the root?
Hello folks of XDA,
I came here because I have not heard any response on the MIUI forums and UI guess is because the community over there is not as big.
Anywayas, I flashed 1.8.5 MIUI, and I suddenly could not see the screen after I dialed a phone number. Then I also noticed that I could not see the answer screen when someone called me.
Everything else worked like a charm, so I thought to myself, well, maybe I have not been back on JFD for a while, so I went ahead and restored the phone back to stock, follow even the MIUI procedure for the massive JFD restore, and it does not matter.... Any Rom from stock to MIUI or CM7.1 all give me the same problem or an app force close, of phone freeze. I can hear the person on the other side if I call, but there is no human way I can answer the phone.
I believe the phone.apk might be the problem, but after trying to do all kinds of factory reset and format, I am still in the same place.
So my first question is, is there a way to fully format the phone and put it with stock apps. Like out of the box? using CWM gives you the option to format the mount points, but I am afraid to format everything and then have a true bricked phone.
Any comments suggestions, questions, please let me know. I been working on this for 2 days now with no avail.
Bump. I have no phone, so it is very frustrating
So I called tech support and see if they had any idea of what could it be. in the end I am back on stock, so what more harm can I do to it right? Well the tech said something that really leave me thinking. He said that the proximity sensor could be damaged. Now that makes a lot of sense, in the end the phone is already somewhat old and I have had my mishaps dropping it from time to time, but luckly no scuffs on it. What do you guys think?
This though is gonna mean that I have to go get me a new phone today ....
Soo I have a Galaxy S II I9100. And it was great until something happened. Lord knows what happened to it. But I was running the latest version of Sensation ROM (1.6) smoothly. Then yesterday all of the sudden my phone kinda stops working more or less. The screen became unresponsive at times, the screen would activate on its own and then I would not be able to use it. After taking the battery out and restarting it things were OK for about 5 minutes.
Then after trying to open any sort of applications the Voice Command app would start and I wouldn't be able to exit out of it. After mashing the home button I could get out of it and then trying to open anything would result in a black screen (status bar active at top). So I figured maybe something went wrong with the software. I happened to have an update .zip of Sensation from 1.5 to 1.6, so I reflashed. This did not really help out. Even plugging in the USB cable was a 50/50 chance, Windows would tell me that the device is seemingly defective and sometimes it would work. But then trying to open USB Mass Storage was a big headache as well.
So I let it sit the night and then this morning I used Odin to flash a stock kernel. This seemed to help out somewhat, it made the system more stable and usable for a little bit. In the meantime I went to the so called "Samsung Cell Phone Service Center" in my city which turned out to be some repair shop for iPhones (go figure). After elaborately explaining my problems they said "must be a software issue". Which it is't. Anyways in the meantime I called Samsung America for direction, after talking to 3 different CS reps they referred me to call Samsung UK because that's where the phone was manufactured.
After that I did a factory reset and that made the issues even worse.
So I'm at a cross roads. I am probably going to be putting a call into Samsung UK tomorrow to try and figure something out.
Do a FULL wipe in CWM and then flash a stock rom. See if that helps. If not, then it's a hardware problem.
I had done that and then flashed a stock ROM which removed CWM, root, and the Sensation ROM. While that seemed to have helped, it would still randomly reboot (fewer than now) and the same issues persisted but less frequently. In the SGS2 stock recovery mode I did factory reset and wiped all data and cache and the problems are back and more frequent. I did take the phone to the beach but it was in a bag wrapped in a shirt..
could that have somehow caused this issue with the hardware?
I'm thinking that this is a hardware issue.
Yes, I think it is. One thing that comes to mind, did your modem change when flashing different roms? If not try a different modem. Otherwise it's really a hardware problem.
So sometime in the last week or 2, my I9300 started randomly freezing up and/or shutting off by itself.
it's usually a while after booting - i'll come to unlock it, and the LED will be showing Blue. Clicking any of the buttons doesn't do anything, nor does waiting a while.
Holding down the power button for a few seconds boot/reboots the phone though, and it works normally when it starts back up again - although after a while it will die again.
Sometimes it runs for hours, sometimes just minutes.
Occasionally, it will freeze up while i'm actually using it - the screen stays on, frozen in place, but the touchscreen and buttons won't do anything (although oddly, multiple clicks of the home button make the colours invert?).
Anyway, i thought this soundsed a bit like this 'Sudden Death' bug, but how do I know? I installed and ran the eMMC check app and it says:
Phone Model: Samsung GT-I9300
eMMC chip: Type VTu00M, Date 05/2012, CID 15010056545530304df1f900755f5f5f, FwRev oxf1
SGS3 Sudden Death? YES. Insane chip.
My question is - what does this mean? Do i have the problem and just need to make sure i run a kernel with the fix, or is the phone now broken and needs replacing/fixing?
If it does need fixing, do i need to revert it to stock ROM and run triangleaway or anything before i send it in, or is it fine how it is?
It's currently running crDroid 11.1 XXELLC, and it was at the time i started noticing the problem. I'm using Siyah 1.8.9, although i was using an earlier version before (can't remember what).
Same problem here... i don´t know what to do... today i make a lot of things to attempt to restore all but everything fail... i decided to talk with samsung and send the phone to repair, in a few days I hope to come to pick up the phone, I have to say that I had to pay 24 € for the shipping and after playing wait month or month and a half. is frustrating but hopefully come good repair.
One read the SDS thread . Two if you think you have the problem or a problem follow the how to revert to stock post and take to a service centre .
Freeze is more likely rom and or kernel .
???????
although oddly, multiple clicks of the home button make the colours invert AS IT SHOULD .
jje
thanks - have read the SDS thread and the stuff people were talking about there didn't really sound like what's happening for me, which is why i posted this thread.
I also thought that it sounded like the ROM or kernel, which is why I have now tried Siyah, tank, and boeffla kernel latest versions, as well as the foxhound, android revolution, and darky roms.
none have made a difference so far
I'm just looking for some ideas on what to do next - should i try reverting back to an Old rom/kernel, should i try a non-sammy based one, is it possible that my SD card is somehow causing the problem?
i didn't know that the multi-click thing inverted the colours - why does it though? it doesn't seem like something i'd want a shortcut to.
Wipe phone flash stock rom .
jje
Fixed it by moving from ELLA modem & wiping.
This thread is your solution : http://forum.xda-developers.com/showthread.php?t=2091045
so i wiped again and installed the MA2 modem - this made the freezing problem even worse so i wiped again and installed the ELKC modem.
this was on Monday and I hadn't had a single freeze until this morning, when it's frozen 4 times in the space of a few hours.
so i guess i'm flashing back to the factory image...
Lear95 said:
Fixed it by moving from ELLA modem & wiping.
Click to expand...
Click to collapse