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
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
I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.
Hi,
I am in Belgium, my phone is unbranded, I bought it in around may, and everything was working fine.
I do have 1.29 that I upgraded OTA, the problem is the device loves to restart itself.
I thought it might be just the sim card not sitting well, i take it out, out of the blue, not very often, will restart itself.
sometimes, it even gives a message, something like, if you don't do anything the device will restart itself in 5 seconds or something like, or sometimes, just restarts.
the most annoying problem is , when I turn on the camera app, in 5 seconds, even if you don't move the camera will initiate a freeze and restart.
if you re quick enough to go to gallery, for some reason, and when u get back to camera, it is fine, until you decide to restart the phone.
One reason I bought this phone is its camera, right, and when you need it, it is not there.
To make sure, I went ahead and did a factory reset, guess what, nothing has changed.
I turned of geolocation, gps etc, nothing is helping.wifi is off.
i turned on airplane mode, it doesn't help.
I never rooted it or anything.
It seems to happen more frequently if the battery is around orange level.
I sent error report like 50 times to htc, perhaps, i thought it might take their attention.
Can you guys suggest something about it???
ozdemirhan said:
Hi,
I am in Belgium, my phone is unbranded, I bought it in around may, and everything was working fine.
I do have 1.29 that I upgraded OTA, the problem is the device loves to restart itself.
I thought it might be just the sim card not sitting well, i take it out, out of the blue, not very often, will restart itself.
sometimes, it even gives a message, something like, if you don't do anything the device will restart itself in 5 seconds or something like, or sometimes, just restarts.
the most annoying problem is , when I turn on the camera app, in 5 seconds, even if you don't move the camera will initiate a freeze and restart.
if you re quick enough to go to gallery, for some reason, and when u get back to camera, it is fine, until you decide to restart the phone.
One reason I bought this phone is its camera, right, and when you need it, it is not there.
To make sure, I went ahead and did a factory reset, guess what, nothing has changed.
I turned of geolocation, gps etc, nothing is helping.wifi is off.
i turned on airplane mode, it doesn't help.
I never rooted it or anything.
It seems to happen more frequently if the battery is around orange level.
I sent error report like 50 times to htc, perhaps, i thought it might take their attention.
Can you guys suggest something about it???
Click to expand...
Click to collapse
Perhaps, you guys want to keep this, because, I have this problem solved with todays OTA update to 4.0.4 by htc.
Hi there,
I'm having a problem with my smartphone and i felt like this is the #1 place to ask for guidance on android issues over the interwebz.
I have a low-budget Samsung Galaxy Y GT-S5360.
It's running what it came with, Android 2.3.6 / Gingerbread.XXLK3.
30 minutes after having it, i foolishly decided i need more internal memory and rooted the device, in order to remove the useless apps on it.
It was a total slaughter. I think i even pwnd Samsung Apps app.
Anyway, device worked well for months after the bloody carnage, but recently backfired right into my face with random shutdowns.
I have no proper idea on the reasoning of these shutdowns but i've collected some data on the subject, here they are;
- It randomly shuts down almost every day. Just 3-5 times a day if it's on a good mood. Over 10-12 if it feels down.
- Device never shuts down while being charged or connected through USB.
- Device usually shuts down after i used power button to lock the screen.
- It's not being locked on black screen, it definitelly shuts down, not properly tho. (no small time vibrating)
- I feel like front sensors (which turns off the screen during calls) might be causing this, because lately it's shutting down whilst calls on my face. I even managed to shut it down by wiping the mentioned sensors with my thumb.
- Sometimes it can be shut down by brute force. I mean putting it down to table a little bit harder than average.
- My SDCard is problematic, it gets unmounted and says its damaged but i tend to ignore it and just reply with "sssh everything is gonna be alright" (format and reuse)
- I have only a handful of apps which contains bank & password apps etc. Nothing serious going on with my services.
PLEASE HELP ME OUT IF YOU RECOGNIZE THE SEMPTOMS.
What should i do? A custom rom? New battery?
Thanks in advance.
Bonus information;
I've never seen it shutdown with my own eyes.
It usually happens when its' screen is blacked out, when i put it in my pocket or table.
Or when i try to make a call and put it against my head.
So whatever is happening, it happens while the screen is blacked out.
It neves turned off while listening to music either.
straud said:
Bonus information;
I've never seen it shutdown with my own eyes.
It usually happens when its' screen is blacked out, when i put it in my pocket or table.
Or when i try to make a call and put it against my head.
So whatever is happening, it happens while the screen is blacked out.
It neves turned off while listening to music either.
Click to expand...
Click to collapse
might be you should go to recovery mode and do a data factory rest and also might need to clear the cache partition.
try it..
prafull07 said:
might be you should go to recovery mode and do a data factory rest and also might need to clear the cache partition.
try it..
Click to expand...
Click to collapse
Ah yes, i did that. Sorry that i forgot to mentioned it.
I've factory reseted it and while i was there i got curious and did the cache-clearing too.
But the problem persists.
straud said:
Ah yes, i did that. Sorry that i forgot to mentioned it.
I've factory reseted it and while i was there i got curious and did the cache-clearing too.
But the problem persists.
Click to expand...
Click to collapse
I think you should try flashing your stock rom with the help of Odin.
Hi everyone, few days ago i got some problems with my phone.
When i am doing smth, for example chatting in whatsapp(it can be any app, even the menu) , the screen may freeze from 5 to 20 sec. After it, the device may become locked or not. Also, after it, device may reboot. Or just shutdown.
I already tried :
1 wipes (full via phone menu and recovery)
2 formatting flash via custom recovery
3 flashing 5.1 via odin
4 emergency restore via Smart Switch
But the problem is still here.
Is this a hardware problem, or should i try smth else?
Thanx for advice
I'm starting to wonder about hardware issues myself.
I'm getting the feeling that Samsung wound the processor too tight on these phones.
Once I get rooted again,I'm planning a proc' downclock to 2.3/2.4 Ghz.
I'm not totally sure,but if these proc's control the RAM directly,that might help with stabilty issues.
Just to confirm; you did a factory restore and also flashed the stock 5.1.1 for your model and region with Odin 3.10.7?
Sent from my SM-N915G using Tapatalk
yes, exactly. Not sure with odin version, but everything was fine.
Yesterday also tried River rom with Mickey Kernel. First few hours phone worked normally, but was a little bit slow (it is normal for this kernel). But then the problem returned, i got some (2 or 3 ) reboots and lots of freezes.
weird. I started gettig these issues a couple of weeks ago too. Did as you did, Odin, Smart Switch, TWRP. Nothing. On RiverRom it seems to be more stable than on the official Rom. Which is crazy. Searched through all the logs, only idea i got left is keeping in under android logcat on my computer until it crashes.
Also phone won't restart if I want to do that. Not from menu, not from TWRP. It will just not do it. It shuts down and no matter how much I press the power button.... nothing. Hve to take out the battery, wait 30 seconds, plug it back in, and it will start.
Any advices on what logs should be looking at would be much appreciated.
kalin12351 said:
weird. I started gettig these issues a couple of weeks ago too. Did as you did, Odin, Smart Switch, TWRP. Nothing. On RiverRom it seems to be more stable than on the official Rom. Which is crazy. Searched through all the logs, only idea i got left is keeping in under android logcat on my computer until it crashes.
Also phone won't restart if I want to do that. Not from menu, not from TWRP. It will just not do it. It shuts down and no matter how much I press the power button.... nothing. Hve to take out the battery, wait 30 seconds, plug it back in, and it will start.
Any advices on what logs should be looking at would be much appreciated.
Click to expand...
Click to collapse
I just tried to restart my, it booted normally.
Maybe its overheating or smth like this? It will be difficult to demonstrate this problem in service centre
honestly i don't think it's overheating. For me the behavior is a bit weirder, as said, as the phone won't restart, unless removing the battery and waiting for a minute or two before plugging it back in. Every. Single. Time. Not even rebooting from recovery.
I use now riverrom with the emotion kernel (they launched this year a new version of the kernel) and it seems to be better. Weirdly enough, the system gets slower when i turn on GPS (although i have next to nothing appls installed), and the apps that say they stopped responding are the boring ones. System UI, Google Play, etc. Also downloading the kernel auditor from the guys at emotion and enabling logcat seems to help too.
An error i seem to get constantly now is google play services error.
Bluetooth also seems to be an issue, i also have a android watch and it gets kinda weird behavior.