Related
Hello everybody,
I came from a nrg on a leo512.
I have installed MAGLDR 1.11 in order to use Android in my NAND.
But I've some random reboot from my device and most of them are when I'm standby mode when I woke up the morning the phone asks me for the pin code...
It's strange when I boot I saw in first for 1-2 sec NRG bootscreen before MAGLDR...
That's why I'm wondering If you think my HD2 NAND is clean ?
Should I make a task29 ? I heard that tools earses all the data...
All your helps are welcome !
Regards
ditto
I have this problem also..
Norwegian HD2..
I have tried quite a few radios.. plowing through all the available radios as we speak.. if i get a reboot i flash a new radio in hope of figuring out the problem.. the weird thing is i dont get this while using WP7... i get reboots in all other OS.. a quick fix for the SIM lock annoyance is to disable PIN code but does not fix the problem itself.. anyone have any thoughts on what this may be?
Sammy88 said:
It's strange when I boot I saw in first for 1-2 sec NRG bootscreen before MAGLDR...
Click to expand...
Click to collapse
This is normal.
The custom ROM you were using has flashed a custom boot screen. As MAGLDR is installed AFTER this in the chain (Boot1->Magldr->Radio & NAND), it does not alter the screen. You can actually install a custom boot screen to replace this. Check Here for some.
As for the reboots, check the sticky link in my sig. There is a FAQ in there which may offer some help.
Also try post 2 of THIS
looks promising
Cptrucker said:
I have this problem also..
Norwegian HD2..
I have tried quite a few radios.. plowing through all the available radios as we speak.. if i get a reboot i flash a new radio in hope of figuring out the problem.. the weird thing is i dont get this while using WP7... i get reboots in all other OS.. a quick fix for the SIM lock annoyance is to disable PIN code but does not fix the problem itself.. anyone have any thoughts on what this may be?
Click to expand...
Click to collapse
Update: Ended up on 2.11.50.20 and its been 20 hours since i flashed the radio.. still no reboot... looks promising, ill update if the situation changes...
Update: 2.11.50.20 was no success, 2.15.50.04 seems to be the best radio in my case.. about 60 hours between reboots has been quite consistent
lately.. i wonder what causes this. ideas and\or sollutions are recieved with gratitude. Disabled the SIM lock so its nothing to worry about but it stil gives me headache.
Although the posts above me may be right, it seems that after I disabled over clocking on my hd2, the issue was no longer present.
As always, remember what your mommy taught you; it's proper to say "please and thank you".
The solution to this problem, can be found HERE.
Esaj2 said:
The solution to this problem, can be found HERE.
Click to expand...
Click to collapse
I tried this solution, but it didn't resolve anything. I'm using mdj's cyanogen mod 2.6 with the latest radio and magdlr 1.13. I' m not using set CPU anymore. I was using it to underclock the phone and I was still getting restarts. The phone's temperature did not seem excessive either. This is a great phone but these restarts are making it almost useless. I'm at a lost here.
viscious said:
I tried this solution, but it didn't resolve anything. I'm using mdj's cyanogen mod 2.6 with the latest radio and magdlr 1.13. I' m not using set CPU anymore. I was using it to underclock the phone and I was still getting restarts. The phone's temperature did not seem excessive either. This is a great phone but these restarts are making it almost useless. I'm at a lost here.
Click to expand...
Click to collapse
Like I said, it works for some of us. I haven't had any rebooting issues, after I turned of the automatic network selection. Some Norwegians fixed this issue, by turning of the 3G. You could try removing the sim-card and leaving the phone at sleep mode for few hours, in order to see, if your phone is still suffering from the random reboots. If so, the problem is somewhere else and I can't help you with it, because I haven't had such issues.
I resloved the issue by sending the phone back to HTC and having the mainboard replaced. Now the phone is working exactly as it should.
Sent from my HTC HD2 using XDA Premium App
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse
Please mention your RADIO, HSPL and the last Android Rom in which this happened!
If your phone is booting, it's not bricked. Did you try another SD card? Have you tried doing a low level format on your SD card? If it were me I'd Format the SD card with an adapter on my PC, low level. Then I would put it back in the phone then run Task29. Then flash MAGLDR 1.1. Then Flash the CMY 1.4n Desire HD Nand build in the HD2 Nand Android Development forum. It's the most stable Nand build up there right now.
I would use the 2.15 radio that comes with the newest Tmobile ROM. You might have to download the 3.14 ROM from Tmobile and flash it first to get the Radio in there. Then Task29 after that. MAGLDR, Then the NAND build. Make sure you find the Task29.exe that doesn't have a radio paired with it. it's on this site somewhere.
lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse
hd2 running MIUI freezing up too
I'm a complete noob here so bare with me. I'm currently experiencing the same probs as lewy255 with the hd2 freezing up. It happens every now and then when I'm accessing certain apps. When the hd2 does freeze up, i have to take the battery out, wait, then boot up again. Once it tries to boot up it freezes on magldr, then i got to take out the battery again, wait, then power it on again. It seemed to happen when i first rooted my hd2. The first ROM i flashed after rooting was typhoon CM7. Currently have:
HSPL 2.08
radio 2.15.50.14
MIUI version: 1.5.27
I hope this isnt a hardware issue cause i bought this phone from one of my friends and he didn't have the receipt. Please advise on what i can do to fix this freezing issue.
Thanks
Sounds like cpu overheat freeze. When you were playing music and charging it the first time it froze, was the phone and/or battery hot?
It's very possible that it got too hot once, and now the cpu its self gets too hot much easier now that it has already happened once.
Sent from my HTC HD2 using XDA App
Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App
germotlp said:
Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.
T-Macgnolia said:
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.
Click to expand...
Click to collapse
t-mac
I tried installing setCPU and adjusted the temperature setting so if got too hot then the speed of the phone would be reduced, but still no luck.
What if i unrooted the phone and put everything back to stock? I think that way i will know for sure that its a hardware issue. I dont know much about phones but your probably right. I'll try running task29 and reinstall everything and see if that works, if not then i will un-root and put everything back to stock and test.
Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.
Kailkti said:
Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.
Click to expand...
Click to collapse
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App
i have same problem with miui roms. I think this problem is about Miui Roms. Miui developers must solve this issue, there is no way..
When i try other Roms, there is no problem like this issue..
germotlp said:
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
in my opinion and its just my opinion, but you should flash a winmo 6.5 build than boot android from sd its safer because theres no need to worry about battery dying in magldr. and if theres a nand rom you want to try out i suggest using port a droid. im using now with the new nexus 2.8 with a 1gb data.img and it runs great plus i have 3 other builds on there also.
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
I believe you're answering yourself. If you wiped everything and flashed different ROMs, but problem persisted - it means that your phone is most likely faulty.
k15goose said:
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
Click to expand...
Click to collapse
The question is, what other roms have you tried? I seem to get the same problems on sense 3.5 roms which is why i am not using them currently. If this is happening on a clean install of cm7 or miui as well as sense then you may genuinely have a problem.
Things to try: full wipe system/data/cache/dalvik/sdcard
reboot recovery after wipe to start clean. verify md5sum of the rom you are flashing to eliminate possibility of error. dont install any of your own apps for 1 to 2 days and then if you still have the problem then you may want to unroot and try to get a warranty exchange if at all possible. Good Luck!
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
k15goose said:
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
Click to expand...
Click to collapse
Well that's good to hear that it isn't happening on all roms. I usually fix the market problems by doing a data wipe and then force close it. Usually will start being able to download after a fc. To check the md5sum on a file download mand5 free from the market and check the file that way.
Sent from my HTC Glacier using xda premium
hey guys, I have a big problem with my hd2...
yesterday appeared me the "1e fatal hit" message on magldr...
so, I tried to boot from sd....fatal hit
enter recovery....fatal hit
task29, magldr, cwm........fatal hit!!! damn!
I tried to restore the device with sd installation of wm, but it stucks on htc green logo...
reunlocked hspl, task29, magldr.....fatal hit...
restored and tried to install wp7, fatal hit
tried installing clk but it wouldn't boot cwm...
removed battery for hours, i looked for some fixes in this forum, did everything but I have the same problem...I'm going insane guys!!
someone think that is an overheating problem, or battery problem....sim, sd...
have I got to bring my hd2 to the customer service center? sorry for bad english...
thanks in advance for your help
Hi,,, I have the same problem I have tried everything... some help please
Hi try to read
http://forum.xda-developers.com/showthread.php?t=1060004
It's is possible an hardware error
giolokj said:
Hi try to read
http://forum.xda-developers.com/showthread.php?t=1060004
It's is possible an hardware error
Click to expand...
Click to collapse
well, I don't think so....today I tried the "freezer trick"....10 minutes in the freezer to make the phone cold, I have read that there are some issues with overheating, but rom wouldn't boot....stuck at htc bootscreen....
in my case there is no hardware issue, I think...I gift it to my friend that told me he's going to full wipe the nand (I don't know how), and I'm waiting now...
throcker said:
hey guys, I have a big problem with my hd2...
yesterday appeared me the "1e fatal hit" message on magldr...
so, I tried to boot from sd....fatal hit
enter recovery....fatal hit
task29, magldr, cwm........fatal hit!!! damn!
I tried to restore the device with sd installation of wm, but it stucks on htc green logo...
reunlocked hspl, task29, magldr.....fatal hit...
restored and tried to install wp7, fatal hit
tried installing clk but it wouldn't boot cwm...
removed battery for hours, i looked for some fixes in this forum, did everything but I have the same problem...I'm going insane guys!!
someone think that is an overheating problem, or battery problem....sim, sd...
have I got to bring my hd2 to the customer service center? sorry for bad english...
thanks in advance for your help
Click to expand...
Click to collapse
Hi throcker, maybe you could share some events before your phone went to fatal hit? At least maybe someone like me would know what will be the signs to look out for so that we'll be prepared to backup our information. It would be much appreciated. E.g Maybe you've flashed for the 15th time or 50th time....or the phone started to reboot often than usual....
hairuleff81 said:
Hi throcker, maybe you could share some events before your phone went to fatal hit? At least maybe someone like me would know what will be the signs to look out for so that we'll be prepared to backup our information. It would be much appreciated. E.g Maybe you've flashed for the 15th time or 50th time....or the phone started to reboot often than usual....
Click to expand...
Click to collapse
yeah, I flashed about.....30 times roms, but I don't think that's the problem....I'm sure that someone flashed at least 200 times without issues...
I was running stock miui...clock 254/1190...that day I played fpse for 3 hours, plugged in charger...yeah I cranked the processor and used the phone intensely, but don't think that this may be the cause...
well, I had the phone in my pocket, took that and saw "1e fatal hit 1"....
than I did everything you can read at fist post, task 29, flash, reflash, ecc ecc.....
I have to say that my battery has no more long life....
guys, putting your phones in a freezer won't help
retsam88 said:
guys, putting your phones in a freezer won't help
Click to expand...
Click to collapse
HAHAHAHAH well, I read that a guy with overheating issues had to put his hd2 in the freezer for boot...and it worked just putting it! XD...and next the service replaced his motherboard...come on is funny, I just tried...
but....let's get serious...my friend told me that I have problems with my internal memory, and it can't boot roms...it's strange, magldr works, and also the native recovery....I don't know if I can believe him...
tomorrow or next I will bring my phone to the customer service...I'm tired to try all the day....
no way, I'm replacing the motherboard....
I don't know what is the cause...so, guys who got this error...if the fridge trick wont help (lol) keep prepared to replace and renew your phone...
I get the exact same error!! Damn fatal hit!! I want to add that for me the first time I flashed the ROM it worked perfectly fine. I used it for about a day and then in the afternoon sometime it rebooted and got stuck on the HTC logo..Im going to try and reflash magldr and rom. Hopefully that works
throcker said:
no way, I'm replacing the motherboard....
I don't know what is the cause...so, guys who got this error...if the fridge trick wont help (lol) keep prepared to replace and renew your phone...
Click to expand...
Click to collapse
Just tried the fridge trick.. left it in there for 20 minutes and runs the first 5 minutes.. but when the phone heated up it crashed again..
So i think my problem moght be the overheating.. can i fix something like this myself or shkuld i throw the lovely hd2 away? (Liked it as a back up phone)
onlymaik said:
Just tried the fridge trick.. left it in there for 20 minutes and runs the first 5 minutes.. but when the phone heated up it crashed again..
So i think my problem moght be the overheating.. can i fix something like this myself or shkuld i throw the lovely hd2 away? (Liked it as a back up phone)
Click to expand...
Click to collapse
I just sold it for spare parts....no luck I miss it! can't help
onlymaik said:
Just tried the fridge trick.. left it in there for 20 minutes and runs the first 5 minutes.. but when the phone heated up it crashed again..
So i think my problem moght be the overheating.. can i fix something like this myself or shkuld i throw the lovely hd2 away? (Liked it as a back up phone)
Click to expand...
Click to collapse
You need to disassemble the motherboard and put it in a oven at 180ºC for 12 minutes. .It may seem scary but it will work. . Trust me. . Only the motherboard. .
Sent from my GT-I9300 using xda premium