Related
i'm using a htc wizard with the tnt 5.0 rom, it's been running amazingly fast and smooth, i love it but all of the sudden in the past week, i can't really figure out why but, i reset(soft) my phone once and it sat there forever on the wm6 splash, so i pulled the battery for a few seconds, and reinserted and turned it on, it came on fine, the clock/calender is set to some random time and random day/month of 2006, and if i set the clock to correct date/time/year the hourglass type thing shows up and stays there for a while, i press end and it goes away, but the phone runs super slow, so i soft reset and then it sits there, at wm6 splash and never finished booting up even after 20 minutes, so i pull battery, and repeat, minus chanigng the clock and if i leave the date/time to 2006, it works fine, does this make any sense to anyone? how can i fix this possibly ?
Please make your text readable....
Have you tried to reflash your phone?
it makes vague sense but you need to work on your grammar a little
Reflash your phone, make sure you followed all the steps. Thats all i can recommend until you put more info in a reply
I'm going to try re-flashing it, but as far as working on my grammar, I don't see how anyone would have any problems understanding what I typed. lol. Unless of course english isn't your first language ?
Maybe the problem is so abnormal there isn't much more info I can include to make any more sense. I described exactly what the problems were.
sintax said:
but as far as working on my grammar, I don't see how anyone would have any problems understanding what I typed. lol. Unless of course english isn't your first language ?
Click to expand...
Click to collapse
Surely you Jest. There wasn't a single Period (.) in your entire first post. Apparently you realized and corrected that error in your second post. But to claim that there was nothing wrong with it was wrong.
Flash with an official ROM, that should take care of the issue
yeah it happened to me once or twice. I just reset the date.
No grammar problems. Very understandable for one single, long run-on sentence. Really this isn't Language Arts. I had NO PROBLEM understanding you.
I'd do a HARD reset before I resorted to reflashing.
Maybe you should pay a SINTAX for your lack of SYNTAX hehe
I understood because I encountered the same problem. Except I encountered it because my phone was CPU-scaled at a time I didn't know how and I had a heavy start-up program running.
So far the only solution was that I reflash to official ROM, then back to cooked ROM. And now every time I reboot my device, I'm mindful of the 3rd boot loading time.
Therefore I just believe that you have to be mindful about the stuff that's on your phone and see what contributes to a slow or non-responsive boot time. Our phone's are computers, and therefore computer's never last.
I can't understand for the life of me why some of are flaming this guy for making a run on sentence... Last time I checked this wasn't 12th grade english class, it was a forum for a bunch of WM fanatatics to gather together and create great things.... I mean come on...
And to reply to the first post, I could understand you 100% for the record.
I think you need to hard-reset your phone. Just hold the comm manager and voice button while resetting with your stylus and press the send key when it prompts you to. Simple enough.
sintax said:
i'm using a htc wizard with the tnt 5.0 rom, it's been running amazingly fast and smooth, i love it but all of the sudden in the past week, i can't really figure out why but, i reset(soft) my phone once and it sat there forever on the wm6 splash, so i pulled the battery for a few seconds, and reinserted and turned it on, it came on fine, the clock/calender is set to some random time and random day/month of 2006, and if i set the clock to correct date/time/year the hourglass type thing shows up and stays there for a while, i press end and it goes away, but the phone runs super slow, so i soft reset and then it sits there, at wm6 splash and never finished booting up even after 20 minutes, so i pull battery, and repeat, minus chanigng the clock and if i leave the date/time to 2006, it works fine, does this make any sense to anyone? how can i fix this possibly ?
Click to expand...
Click to collapse
eject your storage card before resetting, and put it back after your device started up completely...this will not always help, but it did work for me
Okay. I have had this same problem at least once on three different devs' WM roms. It happened first with VJ's WM6 3.2, then again on 3.4, then again on 3.7. Then it happened once with Nitro's WM6. Now, just last night, it happened again on GnatGoSplat's WM6.1s.
I have no idea what causes it. I can't replicate the problem. I just notice it after it happens.
I'll get to where I'm going and take my phone out of the holster, switch it from Vibrate to Normal, and set it down. Then I'll either receive a call or message, or else I'll pick up the phone to send one, and notice that it's still on Vibrate. Oops, must've forgotten to put it on Normal. So I switch it to Normal. It says "Normal" for about a second, but the Vibrate icon stays put, and then it switches from "Normal" to "Vibrate" by itself.
When this happens, I can't figure out how to get it back into Normal mode. Soft reset, hard reset, pull-the-battery. Nothing. The only thing I can do is re-flash the ROM.
But here's where it gets interesting. After all this happens, when I plug the phone into the computer via USB (WinXP), ActiveSync starts up, connects, and then pops up a dialog box that says ActiveSync cannot synchronize with the device. The AS window still shows it as being "Connected" but not "Synchronized". I can explore, copy, move, whatever. I can even reflash the OS. Which I do.
And then all is well.
Until it happens again.
Kicker: When it happened to Nitro's WM6, it was the same day Gnat released his 6.1, so I flashed that instead. And when he updated it and fixed a few things, I flashed that one. And I used it 24-7 without even a soft reset from the day it was released until approximately a week ago, when I installed moalesipufos' 6.1Pro RC4, just to test it out. It lasted all of an hour until I decided I just couldn't figure out the interface and wanted my GGS6.1s back. So I reflashed Gnat's ROM onto the phone.
A week later I get this.
So that was a long and (probably) boring description of my problem, but as it is so random and confusing, I wanted to make it as clear as possible in the hopes that someone, anyone, would read it and have some clue what the problem is - including whether it's user error or an ID=10T error.
So. Anything?
Thanks a ton!
Hi guys....,
Can anyone help me with my problem....
Installed a Desire HD ROM on my HD2 last January....
Everything is doing great, love the ROM..., until one day it freezes, I remove the battery cover to reset my device, while booting, an error occurred displaying 1E FATAL HIT 1 in MAGLDR.... (damn!).... remove my battery again and it keeps on resetting and resetting, until it enters MAGLDR (1.11) and displaying the error again. Since then it freezes, maybe on a day basis, maybe 5 freezes and rebooting, tsk.... In some instances whenever I'm watching movies, or playing games, it freezes and makes a weird noise especially when it uses the speaker, the noise is just like a static electricity... and it is hot, the device and the battery....
After that I thought, maybe may ROM is corrupt, or the MAGLDR, or the radio I installed (2.15.....), so I reinstalled everything, try a different ROM, update my MAGLDR to 1.13 and even do the Task 29, but my problem stills occurs, still displaying 1E FATAL HIT 1 and still freezes...
Can someone help me, is it still a software malfunction or hardware, I hope not.
Thanks guys.
that doesnt sound good and imho is hardware related. Just a thought though, have you tried a different sd card?
Nope haven't tried a new sd card..... even if my sd card is not inserted, it got the same problem....
when you reflashed everyback back to square one so to speak, did you flash back to stock winmo rom and if so did the issue still persist?
been busy for awhile....
yup I flashed back to stock winmo rom, and it does persist, same error even if i'm in winmo, I guess same error, it doesn't display sa 1E Fatal Hit 1 because winmo doesn't have MAGLDR, but it hangs... Tsk....
Time to visit a repair centre i think, soz dude.
OMG... Maybe that's the last resort... Thank you sir....
del
I had 1E fatal HIT and its problem on you hardwere temperature I had Windows Mobile 6.5 and had a same problem. So intall Android OS and you will have minimal errors on this fatal HIT problem.
m_cruz_jr said:
Hi guys....,
Can anyone help me with my problem....
Installed a Desire HD ROM on my HD2 last January....
Everything is doing great, love the ROM..., until one day it freezes, I remove the battery cover to reset my device, while booting, an error occurred displaying 1E FATAL HIT 1 in MAGLDR.... (damn!).... remove my battery again and it keeps on resetting and resetting, until it enters MAGLDR (1.11) and displaying the error again. Since then it freezes, maybe on a day basis, maybe 5 freezes and rebooting, tsk.... In some instances whenever I'm watching movies, or playing games, it freezes and makes a weird noise especially when it uses the speaker, the noise is just like a static electricity... and it is hot, the device and the battery....
After that I thought, maybe may ROM is corrupt, or the MAGLDR, or the radio I installed (2.15.....), so I reinstalled everything, try a different ROM, update my MAGLDR to 1.13 and even do the Task 29, but my problem stills occurs, still displaying 1E FATAL HIT 1 and still freezes...
Can someone help me, is it still a software malfunction or hardware, I hope not.
Thanks guys.
Click to expand...
Click to collapse
Did you try hard boot?
1e fatal hit 1
well guys get ready when you look into this its going to piss you off but the heat has desadered your contact you know that buzz you get just before reset the last ditch effort to stay operable going to pull my phone apart tonight and see if hardware can be repaired peace out
ok here you go have to completely wipe sd card with easus partition manager will take some time at first will act like nothing is going on after one min. remove bat then reboot and hold up and down toggle to reset the should come back ok worked for me
Ok, so i had this exact problem yesterday. Same issue, same screen. This is what i did, it doesnt mean it might work for you but i bet it should. Although in my case the phone will just freeze after some time using it since its really a hardware failure. But at least youll be able to flash it. First i recharged the battery overnight with an external battery charger(Mine is a china cheap charger so i guess any of those will do the job. Then i put the HD2 without the battery of course inside the freezer(since the problem is overheating and this has been done forever since integrated circuits existed(everyone knows the cooler your machine the faster it works). Wrap it with some plastic so that it will not grab any water inside the phone obviuosly. Leave it there for a while. Then take it out put the battery in and try to flash it. Youll see that it will flash without any errors. The problem is that if your phone is as messed up as mine was the problem will persist after some time using it. It will freeze and will get stock. So i think theres not much we can do about it! But if you want to at least flash it succesfully you can do that.
you could try a new phone.
Well, we are talking about the problem with his phone. But yeah anyone can try that option with succes. And to give some kind of update, my HD2 was left for a while cooling off. Now its working like theres nothing wrong with it. I cant talk about the future but it has been working like a charm for about two hours now.
It fixed with me
It fixed with me
I Have same same error, finally last boot when he stick in that error appear in the screen, i pressed the soft reset button in the back, Works and booted normally
I recently forced the updates to get to Mango using the http://www.wpcentral.com/force-mango-update-early-through-zune-software method. I'm on step 8 of 10 on the Mango installation and it appears to have frozen. The small gray bar appears to be at 100 percent but it still depicts the do not disconnect from computer screen. I'm wondering if anyone else has encountered this problem and what I should do. Thanks.
It's possible it just froze and a restart would work.
EDIT: Well I waited for the little gray status bar to get as far as it will go. ie: let it sit there for an hour or two to make sure everything was set. The Zune software said something about a failed update or whatever so I disconnected it. Anyways took two restarts and bam I have Mango working perfectly fine on my phone. Sat a little while on the new Windows Phone logo page.
I have a HTC 7 Trophy and I managed to update succesfully, but I'm dissapointed that there's no difference from the leaked one. No IM integration from yahoo, no skype. Very little customisation
chioreanul said:
I have a HTC 7 Trophy and I managed to update succesfully, but I'm dissapointed that there's no difference from the leaked one. No IM integration from yahoo, no skype. Very little customisation
Click to expand...
Click to collapse
That was 100% unhlepful.
I have the same problem as you. I cancelled the update and disconnected my phone but now my phone will not boot properly. It vibrates 7 times and stays on the HTC start up screen.
Can anyone help us?
using an omni a 7 here, been stuck on step 6 of the process "rebooting your handset" for about an hour now. Handset rebooted a couple of times as I expected before this step but just hangs on this screen. Loading bar stick ticking on and the do nt disconnect screen on the handset but that's it.
hightower1 said:
using an omni a 7 here, been stuck on step 6 of the process "rebooting your handset" for about an hour now. Handset rebooted a couple of times as I expected before this step but just hangs on this screen. Loading bar stick ticking on and the do nt disconnect screen on the handset but that's it.
Click to expand...
Click to collapse
My Omnia did the same. Just unplug the USB cable from your phone, and then plug it back in again. Worked for me!!!
this is just from my experience.
I did have freeze the first time I updated to mango beta few weeks back on part where I had to restarted the phone. I disconnected the usb, and seemed everything was good.
but I connected the phone again, try to look for new update, and zune gave me error. the only way I fixed is by restoring to previous NODO build.
the 2 things I would make sure I have before doing any updates for wp7:
1. battery power is > 50%
2. I would make sure that screen time out is set to NEVER
since then, I never had issue with updates
I hope this helps
Edited because I found the 'fix' or work about. Everything is fine.
So I bought the S6, new, never been opened, sealed etc, let it charge the proceeded to turn it on. Then comes the welcome bit and startup, this is where it went tits up. Apparently everything stopped responding, google maps stopped responding, voice commands stopped responding, etc. Thought nothing of it, skipped through everything, got into home screen and then "Touchwiz has stopped responding". So naturally I though oh dear. Oh, it also started restarting on it's own randomly as well, I tried booting in safe mode, disabling things, that didn't work, sometimes it would even get in a bootloop, loop 3 times and then start.
I tried updating it, didn't work, tried flashing it with "G920FXXU3QOLD_G920FH3G3QOJ1_G920FXXU3QOJB_HOME", problems still persist. It's currently on 5.1.1, it wont update in settings, just starts downloading more than 1.2gb's of downloads then says "Software update has stopped responding".
Tried samsungs live chat, was awful, they didn't present any useful information.
I'm wondering if it's just 5.1.1 being awful, because when I boot to the system recovery menu thing where it has the blue screen with android logo, then has yellow exclamation mark, that doesn't reboot on it's own at all. Never reboots in download mode either. Phone is not rooted, knox hasn't been tripped or anything, so I'm left clueless. What do I do? Bought this phone, what, 4 days ago ish. Came here yesterday. My question is, if I flash it with idk, a 6.0.1 update in odin or something, will that fix the problems?
Hi,
It seems to me that you have a defective device, you can either try reflashing the stock firmware and then factory resetting, I believe that it really is a software issue, but as it's brand new (as you stated), you can return it to the store and get another one.
There are quite a few guides to flashing stock firmware back, hope you can do it .
All the best,
~Lord
Sent from my SM-G920I using Tapatalk