Database Users

I think my Dream is toasted... OR My experience with the "blue light"

Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.

Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?

lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...

The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...

I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.

BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...

I wonder if it found one of those radios and did something with it?

For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.

hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.

lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.

Why does my phone shutoff?

Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.

If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD

patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.

Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.

Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant

I can't seem to find Damagedtrev 2.01
So I can't test it.

Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.

Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.

Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?

Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.

Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.

reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation

kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.

That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.

patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221

Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.

Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?

I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd

[Q] What does it mean when HD2 hangs on startup?

I am not sure if this has to do with using Android or not, but sometimes my HD2 decides to reboot itself unexpectedly, on WM as well as on Android and I can't really find what's causing it.
But what happens is, after switching itself off, it switches itself on again and hangs on the HTC logo, sometimes with or without the following info:
R 2.10.50.28_2
G 15.40.50.07U
D 1.66.76641
I am using stock ROM that came with it, i assumed it will be stable by itself but it reboots itself randomly sometimes just like on Android.
Does it have to do with the Radio version (i changed it from 2.07.xx). I tried 2.12.xx before and had same problems.
I should note that the only way for it to run again is to remove the battery for a while and then put it back. If i remove it and put it back briefly it will still hang.
Anyone is familiar with this strange behavior?
Thanks

ME too
I have the EXACT same problem. It only started for me after using android. now whenever i run Android it will unexpectedly reboot and sometimes hang like yours. It also does it in WM though not as often. I was able to notice it might have something to do with data connections bc if i run android but only use wifi it seems to be fine. I tried changing Radios WM ROMs and Android builds i even hardspled my phone again but nothing solved it. The problem needs to be talked about more. it got so bad for me I bought a Desire and gave up on my HD2 for the moment. Keep this thread up.

sounds like i have to follow
I hope not!
I notice if i do heavy download on wm or android i get it. But it could be that the phone is too hot? But it's not alarmingly hot tbh.
I hope more people can shed light on this.
Thanks for your input.

Yeah this is what seems to happen to me too, i start a downlogsd it gets a bit warm then freezes or reboots and gets stuck. However it doesnt even have to be a large download for me, a simple cab file or youtube video sometimes. And as far as heat, this never used to be a problem and i know for a fact my phone used to heat up way more before without a problem.

Maybe the qualcomm chipset go in "safe mode"..i remember that for first start tickle the orange led and after the device freeze or restart..maybe your device overheat. Try to touch cover's device or install a battery status monitor software. If you have changed radio, return on the original status. In case the restart happen always, make a backup using Pimbackup, and do an Hard Reset. For first try to use the telephone without the memory card and test the stabilty. If is all ok, you have to provide to format your SD card in Fat32. Try also to change the HSPL with the original SPL.

What happened to this thread? Suddenly 3 recent posts have disappeared?

relic said:
What happened to this thread? Suddenly 3 recent posts have disappeared?
Click to expand...
Click to collapse
Forums Restored from Backups - LOST DATA - PLEASE READ
As many of you may have heard, we underwent routine maintenance on our Database Server. Upon rebooting the Database Server, it refused to boot and all indications are that the RAID 10 (what is RAID? http://en.wikipedia.org/wiki/RAID) array failed.
We have restored the Forums from a 24 hour old backup. We know this is not ideal, but at this point, the chances of recovering the failed array are slim.
We sincerely apologize for this. In fact, this maintenance was intended to boost the redundancy of our database setup and lightening strike.
http://forum.xda-developers.com/showthread.php?t=792013
__________________
svetius
-----
User Experience Admin
xda-developers
http://forum.xda-developers.com/announcement.php?f=743

Thabks. Back to the subject, today i tried downloading on wifi a 150mb file on android and it rebooted byitself.
Then i tried to play a wmv video file on WM stock ROM and after 6 min it rebooted.
So its starting to look more and more like cpu/heat problem, anyone having these issues?

So does anyone think this might have something to do with all the overclocking in those android builds we've been using?

After 45 mins of install HD2 still hanging?
Hi, I just installed FroyoSense by darkstone
Release date: 07.AUG.2010
I don't know if this is the latest (probably not) but after 45 minutes of install the screen has in the top left hand corner tiny small text (excuse my lack of knowledge here) but no scrolling text as I expected, its now like 50 minutes, how long should it take?
Any help please would be appreciated, thanks
John

New to the HD2
So, I just bought a used HD2 a week ago. It was having similar problems in WM. I took it to a local store, and they said that is just how WM phones are. I've flashed HSPL and different radios and ROMs, installed Android, but still have trouble with freezing and rebooting on it's own no matter what I do. IT happens the same in WM or Android. Is there any way to find out if these might be due to hardware problems caused by the previous owner?

I got the same problem, when I do a lot of things on the same time on the HD2 it hangs or reboot. During de restart of the phone it hangs on the White screen with HTC on it. I have te take the battery out of it en than reboot again.
When I listen music and Internet the same time it almost always happends.
It happends on WM but also on Android, I tryed different ROM's and Radio Version's but nothing worked. Also tryed to work without SD-card, but still the same problem.
So I have no idea how to solve the problem...
I hope someone now's how to solve it...
Sorry for my bad English but I hope it's clear

FroyoStone with HTC Sense V2
Polar bear said:
Hi, I just installed FroyoSense by darkstone
Release date: 07.AUG.2010
I don't know if this is the latest (probably not) but after 45 minutes of install the screen has in the top left hand corner tiny small text (excuse my lack of knowledge here) but no scrolling text as I expected, its now like 50 minutes, how long should it take?
Any help please would be appreciated, thanks
John
Click to expand...
Click to collapse
Ok having waited for 2 hrs, I shutdown and installed FroyoStone v2, this time the tiny text appeared and faded after about 5 -10 seconds and the screen has gone blank, is this normal? No scrolling text, nothing, I going tpo re-boot and will keep you updated. Thx

If you read the previous posts you would know this thread has nothing to do with the problem youre describing. I understand the confusion of the title but pls read the thread first.

Polar bear said:
Ok having waited for 2 hrs, I shutdown and installed FroyoStone v2, this time the tiny text appeared and faded after about 5 -10 seconds and the screen has gone blank, is this normal? No scrolling text, nothing, I going tpo re-boot and will keep you updated. Thx
Click to expand...
Click to collapse
Your problem is unrelated to this thread.
So far we have more and more people having the related issue on WM and Android. We need some expert to help us pinpoint the problem.

jasperbleumink said:
I got the same problem, when I do a lot of things on the same time on the HD2 it hangs or reboot. During de restart of the phone it hangs on the White screen with HTC on it. I have te take the battery out of it en than reboot again.
When I listen music and Internet the same time it almost always happends.
It happends on WM but also on Android, I tryed different ROM's and Radio Version's but nothing worked. Also tryed to work without SD-card, but still the same problem.
So I have no idea how to solve the problem...
I hope someone now's how to solve it...
Sorry for my bad English but I hope it's clear
Click to expand...
Click to collapse
i have the same issues.
I can add also playing videos for longerthan 5-10min would make the phone reboot too weither its WM or android.

Today I was in the Store where I bought mine HTC HD2, because I was sick off it. They told me that is was a familiar problem with the HTC HD2. They also would repair it free for me. I didn't do it yet because first I have to delete my HSPL etc.
I asked them also what the would repair to solve te problem, he told me: the will do a complete bodyswap. So everything will be renewed, exept the tochscreen and front.
So I guess it is a real and serious hardware problem....

Why we dont hear people conplaining about it if its comon?
I find that very odd.

Someone could try PMing one of the devs in the forum and linking them to this thread to see if they could shed some insight or at least bring more attention to the issue.

Well I live in the Netherlands and on the Dutch HTC HD2 forum, I heard some people complaining about it. But the salesman of the store said that it is a familiar problem, so that sounds to me like a regular problem. But indeed it's weird we doesn't hear more people complaining.
Maybe the most of the people think is normal with WM, but I am really sick of it...

Just an answer to my question.

Phone freezes no matter what I try. Stumped
I have a question that seems not to be able to get answered where ever I post it. so please forgive me for posting here if this is not the correct place. I have been trying android from the beginning and I've tried everyones builds. from winmo to droid and different radios to find the right combination. The problem i keep running into is that my phone freezes up no matter what i do. I tried the letama .2 & .3. This problem even occurs in winmo even with the sd out. I may get a full day out of it with no problems then the problem returns. Right know i'm running MDJ Froyo revolution v.1.3 and winmo ozrom 5.10 wwe and radio 2.10.50.26. Also, wipe the sd clean every time i switch builds or upgrade. Haven't figured out how to do logs yet. still searching and reading to try and teach myself how to be more useful around the forums. Thanks and I appreciate all the hard work the DEVS put in. That's why i follow the rules except this time.

cwsmall said:
That's why i follow the rules except this time.
Click to expand...
Click to collapse
Obey the rules!
Naa, just kidding. But if your phone's freezing even in WinMo there's something really messed up. Did you try to make a task 29 and flash your ROM again? That might be helpful.. If not, turn your phone back to original standards (ROM, HSPL, Radio must be as given by the factory) and go to your retailor to use your guarantee if you still have.

Obey the rules!
Naa, just kidding. But if your phone's freezing even in WinMo there's something really messed up. Did you try to make a task 29 and flash your ROM again? That might be helpful.. If not, turn your phone back to original standards (ROM, HSPL, Radio must be as given by the factory) and go to your retailor to use your guarantee if you still have.
I like you sense of humor. thank you for taking the time and commenting. there has been 30+ people that have viewed this and haven't even responded. But, some can ask like where is the download link and we all now where its at. always at the beginning of the thread,but they get all kind of replies. It just makes no sense to me when someone has a legit question they can't get much help. don't really understand that. Thought we were here to help each other.I don't believe that its an issue hardware issue. i believe its more software than anything. It comes and goes. My phone was going thru a period where it would reboot all by itself with no apparent reason. Then all of a sudden it stopped it and hasn't done that for 4 to 6 weeks.

really 97 views and no insight.

you tried the stock factory rom?? It might be hardware. You will be surprised a tiny drop of water inside your phone will slowly mess up your phone through a long period of time.
Are you on tmobile? I will try to look for a stock rom for you.
BTW, what do you mean by freezing? it hiccups or you have to do a battery pull.

cwsmall said:
really 97 views and no insight.
Click to expand...
Click to collapse
btw, your title is a curious one, that is why you have many views and received little to no response. If they can't help you they won't post anything. But I will try my best to see whats going on.

if your suffering from the freezes in winmo and android then you I think that you need to forget about android for the time being and concentrate on getting a stable WM set up........
If you havent already done so then try a hard reset and see if that helps.......
try booting and running your phone with and without your sd card........
with and without your sim card........
if it still happens after the hard reset then you will need to reflash your WM rom, if you plan on using the phone mostly for android then I would opt for a basic rom like the energy reference series or one of duttys roms.....
there are many reasons why your phone might freeze and you need to spend time trying all situations to figure out what makes it freeze..........
if it still happens after the reset/reflash then we can only assume that it is a serious problem which may well require a warranty replacement.....

if your suffering from the freezes in winmo and android then you I think that you need to forget about android for the time being and concentrate on getting a stable WM set up........
I have tried all that you have suggested. The curious thing to me is that it seems to come and go. It first started with the energy rom and it's also happened with dutty's as well. if you guys know how to pull logs that devs need is possible you could give me a run down on how and then maybe i can find out if it is hardware. My phone has never been near water. i'm very careful about that. I'm using ozrom now. This is the 3rd HD2 i've had. the last one lost all touch response. I just have a feeling its software, but i just have a gut feeling on that. Thanks everyone though for your input i greatly appreciate it and keep it coming.

BTW, what do you mean by freezing? it hiccups or you have to do a battery pull.
I have to pull the battery. Then i may have to leave it out for a minute or two maybe longer then replace battery before it will load windows. it will just show the splash screen.

was this happening even when you were running the stock rom?

Have you tried to reformat your SD Card? I have two, and when I used my original card received with my HD2, TMOUSA, it would freeze. Since I reformatted and use new and old card, no problems for over a month.

was this happening even when you were running the stock rom?
YES

Have you tried to reformat your SD Card? I have two, and when I used my original card received with my HD2, TMOUSA, it would freeze. Since I reformatted and use new and old card, no problems for over a month.
yes. I have two the 16 that came with it and an 8. it happens with both. I reformat every time i switch builds.

I see that your using radio 2.10 and that caused my HD2 to freeze a lot. change your radio to 2.12 or 2.14
I use the same Android build as you but with the elegancia gtx wm rom with radio 2.14 and after upgrading the radio the freezing (SOD) stopped.

I started using the radio 2.15.50 and have had no problems whatsoever. Also unchecking auto rotate and auto britghtness helps. Sometimes redownloading and installing your Android helps if you got a bad download the first time.

Update
now runnning enery extreme from 11/5 and mdj desire hd with his newest kernel smartass and the only time it freezes in during a call. usually anywhere from 5 - 15 minutes into the call. Anyone have any insight two a possible solution?

This is what I would do:
1. Task 29
2. Flash a slim WM ROM such as the one mentioned in my signature.
3. Flash a NEW RADIO...at least 2.12 or even higher.
3a. Install NOTHING. NOTHING AT ALL. Just answer and make calls. Period.
4. Test that build for two days. If I have freezups, then my phone is bad and I would flash the stock rom and radio and return it. If it does not freezup goto 5.
5. Completely reformat my SD card to Fat32 32kb (or 64kb if you think it affects stuttering in music).
6. Since you and I are both in the US, I recommend getting an Android that has a built in TMO MMS fix such as the new MDJ build (with link to MMS fix) or the fine MooMoo build or even Bluetopia.
7. Test the basic features in Android for two days minimum and see if I get freezeups (after disabling auto-rotate and wi-fi on the Android build as well as completely shutting off all radios in WM).
8. Be glad I got this far, and slowly reinstall my apps, testing each thoroughly for freezing.

This is what I would do:
1. Task 29
2. Flash a slim WM ROM such as the one mentioned in my signature.
3. Flash a NEW RADIO...at least 2.12 or even higher.
3a. Install NOTHING. NOTHING AT ALL. Just answer and make calls. Period.
4. Test that build for two days. If I have freezups, then my phone is bad and I would flash the stock rom and radio and return it. If it does not freezup goto 5.
5. Completely reformat my SD card to Fat32 32kb (or 64kb if you think it affects stuttering in music)
Thanks for taking the time to post this i appreciate it. I have tried it all. It appears to be getting better. I have been using MDJ's kernels since he posted them with his desire hd build. I have always felt that it was software related and not hardware. It appears to me to be caused maybe by the data drops from ppp. Not sure though till i teach myself how to do that. thanks again though.

Turned out to be a hardware issue. Got my new replacement and it works flawless. Can't believe the fun I was missing. At least it was a great learning experience.
Sent from my HTC HD2 Desire using XDA App

[Q] Android won't boot up, keeps reloading the Quietly Brilliant ****

its REALLY grinding my goddamn gears and I'm ready to smash the phone against the wall. It won't boot up anymore into Android, just goes to the white HTC "Quietly Brilliant' screen and KEEPS PLAYING IT, OVER AND OVER.
It worked absolutely fine up till today. Any help? I'm sick of gadgets not working properly. Android worked fine for the past month, why now?
BUILD: cedesmith's desire hd2 ROM: OzDROID ROM RADIO: 2.15.50.14

that kind of language won't help. anyway, just do a fresh install. if you haven't done a backup then you're screwed, but it's a risk you have to face.

when was the last time you rebooted into windows and back into android
i get this even after 48 hours of use, so every day i almost backup my phone from windows mobile

jcsy said:
when was the last time you rebooted into windows and back into android
i get this even after 48 hours of use, so every day i almost backup my phone from windows mobile
Click to expand...
Click to collapse
lol, then you guys are seriously retarded or doing something completley wrong

You guys never post how you formatted your sdcard. I had this kind of problem in my "early" day(s) of Android, lol.. But reading the stickies allways help, for me the magic medicine was the panasonic sdformatter, since then android never get stuck on bootscreen...
well... smashing the hd2 against a wall would solve your problem to us too
every 48h?! thats madness... torture..

i suspect its the SD card though so probably going to get a new one, probably smaller in size 8GB..
anyways, yes that format program by panasonic doesnt change any **** i face, lol
32kb or 64kb blocks, lol

This can happen when your data.img gets corrupted. This can happen for any number of reasons, but unexpected reboots are probably the cause. I've had this myself and the only answer was to delete it and let it create a new one next restart.
I did, of course, lose everything, so I do regular backups now.
Sent from my HTC HD2 using XDA App

dan138zig said:
that kind of language won't help. anyway, just do a fresh install. if you haven't done a backup then you're screwed, but it's a risk you have to face.
Click to expand...
Click to collapse
I was in a VERY bad mood, my apologizes. I hadn't slept in about 32 hours when I posted this and this just grinded my gears.
I've done a fresh reinstall (After loosing everything) so I'll check if it fixes everything.

I've had this before, and by deleting the ".android_secure" folder on my sdcard I got it to boot. I doubt this is a wonderfix for everyone, but for me it's worked a couple times, but I do a lot of build swapping, and when I try one build then go back to a build that is now 'not booting' deleting that ".android_secure" folder has worked.