Hello,
I recently had my HD2 setup with MAGLDR 1.11 and a stock DHD ROM, however this froze constantly and seemed to get worse over time, as well as all together failing to boot sometimes.
So I updated MAGLDR to 1.13 found a nice rom "Typhoon CM7" I believe, downloaded the radio it sugested and flashed it, downloaded CWM and flashed it, and then flashed the ROM from SD using CWM.
Sadly however this has not fixed my freezes/failures to boot, im starting to think it might be hardware related.
So what I am asking is does somebody have a ROM that is working really well for them that they could sugest to me?
Thanks,
Alex.
everyone has different opinions, do you want a version with or without sense?
personally i like sense so am using imilkas ram hd version ,its fast and very stable
Well i usually tend to go for ROMs without sense, but i am pretty impartial to it.
alexhope21 said:
Well i usually tend to go for ROMs without sense, but i am pretty impartial to it.
Click to expand...
Click to collapse
Which ROMs have you tried already, and what was wrong with them?
I have tried one of the many DHD stock ROMs and Typhoon CM7, as well as Raphroid and Ultradroid.
I frequently get a freeze at "GO GO GO" in MAGLDR 1.13, and then once the ROM does eventually succeed to boot, it often locks up.
Some ROMs seemed to do better then others overall however, Typhoon CM7, successfully booted most frequently.
In all cases I have used recommended radio's.
However the greatest hassle has been flashing them as I can only get CWM to boot 1 out of 20 times after multiple reflashings, it often gives me an error stating "FATALHIT 1".
Does everyone get behaviour like this?
Hmm.
That's Weird I Have Tried Lots of these roms and they all seem stable and fast on my hd2
crabtreebrandon29 said:
That's Weird I Have Tried Lots of these roms and they all seem stable and fast on my hd2
Click to expand...
Click to collapse
Could you please give me some specific information of what version of MAGLDR, CWM you were using, as well as a link to the Radio and ROM?
Im starting to think my hardware might be bunged.
Thanks,
Alex.
i am too having a lot of problems when booting up from maglrd. It freezes or gets hit fatal error. Do anyone know a good stable rom that doesn't freeze when booting up,and has great battery life?
thi713 said:
i am too having a lot of problems when booting up from maglrd. It freezes or gets hit fatal error. Do anyone know a good stable rom that doesn't freeze when booting up,and has great battery life?
Click to expand...
Click to collapse
All of them. End of story. This is due to user error. Not build related
alexhope21 said:
I have tried one of the many DHD stock ROMs and Typhoon CM7, as well as Raphroid and Ultradroid.
I frequently get a freeze at "GO GO GO" in MAGLDR 1.13, and then once the ROM does eventually succeed to boot, it often locks up.
Some ROMs seemed to do better then others overall however, Typhoon CM7, successfully booted most frequently.
In all cases I have used recommended radio's.
However the greatest hassle has been flashing them as I can only get CWM to boot 1 out of 20 times after multiple reflashings, it often gives me an error stating "FATALHIT 1".
Does everyone get behaviour like this?
Click to expand...
Click to collapse
i assume you are changing the CWR partition each time you change from a dhd rom to a non sense/GB rom ?
Richy99 said:
i assume you are changing the CWR partition each time you change from a dhd rom to a non sense/GB rom ?
Click to expand...
Click to collapse
Yeah, Im starting to think my hardware is damaged, I used to use the SD RAM rom that Dark Forces released, and I guess it did not benifit my device, as it would frequently get quite hot after 20min of straight use.
How does this ROM run with the 2.15.50.14 radio?
If it is also laggy and has bugs, then I think your phone might be broken.
For me all roms using SD-EXT are laggy as hell and i personally stopped testing those roms as I'm already used to the smoothness of Gingerbread... I'm searching almost everyday though these topics to find somebody who says "This is a really smooth Sense rom!". But never seen a comment like that.
Related
Hi
I am having trouble with my t-mobile htc hd2, I have gotten hspl and MAGLDR111 on it. I have tried a couple of nand and some hang on the android boot up screen, while others like Stock Leo_Desire nand gets the black screen right after i saw the unlock screen. The only nand that works for me is the NexusHD2-Froyo_V1.9a_NAND. I have also tried clockworkmod recovery but the same thing happened; either hang on android boot up screen or black screen after i see the unlock screen. Hope someone can provide me with some help.
The NexusHD2 Froyo nand works great, its just drains quite a lot of battery from the phone; have to charge at least once a day. I want also wanted to fix this problem because I want to try different nand.
I dont remember what my previous version was because i thought it was the WM version issue so I updated.
This was the WM Version that I had installed.
RUU_Leo_1_5_TMOUS_3.14.531.1_Radio_Signed_15.42.50.11U_2.15.50.14_2_Ship
thanks.
BTW, I have tried a couple of other stock wm 6.5 roms but the same thing happened.
Same problem
I am having the same problem as you, except i havent tried NexusHD2-Froyo V1.9a NAND. Im going to try it now to see if it works.
That one worked for me woot!
chai619 said:
That one worked for me woot!
Click to expand...
Click to collapse
that's good, just waiting to see if anyone encountered this problem or solved this problem.
BTW, I have tried a couple of other stock wm 6.5 roms but the same thing happened.
Yea its annoying only one is working, i checked everywhere on the forums and the stock nand build said it just doesnt work on some. But if one of them works without a problem then tytung did it right. I went back to using the SD card i might go back to nand in the future.
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.
Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.
webmanya said:
Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.
Click to expand...
Click to collapse
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers
silverwind said:
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers
Click to expand...
Click to collapse
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.
webmanya said:
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.
Click to expand...
Click to collapse
In fact, I still can use Imilka's, Rafdroid and few other Nandroid ROM
But, I dont want to make it worse knowing that there is some badblock(because I want to sell it)
So, I am back with Winmo and SD Android. It is much safer for me
Cheers
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
joostnl said:
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
Click to expand...
Click to collapse
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Buy her an iphone, then she can't pull the battery! :-D
Sent from my HD2 using XDA App
malybru said:
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Click to expand...
Click to collapse
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
lol, hahaha
joostnl said:
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Click to expand...
Click to collapse
ive seen a few posts where people have struggled with getting past boot logo, think it was fine after using a different partition in recovery but as your device is for the sd build am not quite sure how that works as Ive never had sd android or if having sd requires clockwork mod recovery? if so try different partition as i said earlier if not hang on till someone has the answer
johnerz said:
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
Click to expand...
Click to collapse
haha great answer, my girlfriend doesn't touch my hd2 or she gets alot more than a double dose with the tazer method, HD2 is not the solution for a women... you take the hd2 of her and buy her a iphone surly they are women material.
Ignore Post
Problems almost always occur after a few weeks or months of use for me, just reflash the ROM, and you'll good to go.
removing the battery is not recommended, it can corrupt files on the sd-card. Try to boot without sd-card and see if it helps. If your ROM does boot, it means the SD card is corrupted, you can try to backup the SD card and restore it after completely wiping the sd-card.
If your rom doesn't boot, than it meant there's something else going on, maybe corrupted flash, so reflash and try again. This will delete all your data, so be careful
if your girlfriend is not an daily flasher also might i suggest using a daf build. All the configuration is done for you. if you are using a sd build from magldr than make sure you change the name of the build than edit the startup txt like this "rel_path=whatever you name the build(example: "rel_path=MIUIROM nand_boot=1") the 1 for magldr 0 for windows 6.5. the reason for me saying this is all android builds create a folder android when they boot up with all your info like data and cache is in there. So its best to separate the two just in case you want to boot up more than two builds from sd.
Same here.
could be a bad block in your NAND memory. you can check this with cLK and fastboot.
see this post: http://forum.xda-developers.com/showpost.php?p=13600733&postcount=9
i checked mine and there was a bad block in the userdata. i think that is wy my phone was freezing.
now i have flashed cLK and untill now its working great!
Hi Guys, hoping somebody can help me here... I used to use an older ROM on my HTC HD2 (NAND) that worked fine, but wanted to reflash my phone and give it to my old man as I've just got a HTC EVO 3d.
Anyway, I've flashed a couple of new ROMS (Energy 10.3.2011) and HD2_CoreDroid...
They flash ok (Im using clockworkmod), but I seem to be getting some strange artifacts on the screen from time to time. Mostly around the buttons... I would describe them as horizontal lines across the buttons, and they seem to change (ie, looks like they are animated).
So, it might be something I'm doing wrong with the setup prior to flashing the rom (I get the same problem in both roms, and copilot doesn't work - ie, loads, but nothing happens).
Anyway, this is what I am doing.
Task29 via HTC Tools
Go to Recovery:
- Wipe data/factory reset
- Wipe cache partition
- Advanced -> Wipe dalvik cache
What I am not sure about is the HTC Tools MAGLDR re-partition details.
I tried:
Cache Size (left hand side) 5MB
Cache Size (right hand side) 5MB
Custom: Repartition - 180MB
What I don't understand is what size partition I should create on the SD card... I've tried 1024MB (I have a sandisk 16GB card).
I'm using MAGLDR 1.13, Clockworkmod v3.0.0.5
baseband version: 15.39.50.07U_2.10.50.26
Kernal: 2.6.32.15_HierOS_test_notbtfix (is this correct)
Just to clarify, the phone comes from Australia and was under win6.1 Telstra.
I'm happy to see if I can take a video and post that up it if helps (to show the screen jaggies).
Could I be using the wrong ROM and need to upgrade that? Maybe my screen is just stuffed ! (although it was fine before I started to put a new rom on it!)
Any help really appreciated.
These are graphic glitches that you will experience with Gingerbread Sense 3.0-3.5 roms. There is a file that you can flash to get rid of them usually at the price of performance. What the file does is it disables the hardware acceleration of the phone and tends to slow it down some. No harm is done if you leave it alone it just gets annoying to some people. Some roms seem to be worse than others. The rom in my signature is a Froyo Rom with Sense 2.0 and you don't get the gitches. It works great. Hope that helps explain it.
Egrier said:
These are graphic glitches that you will experience with Gingerbread Sense 3.0-3.5 roms. There is a file that you can flash to get rid of them usually at the price of performance. What the file does is it disables the hardware acceleration of the phone and tends to slow it down some. No harm is done if you leave it alone it just gets annoying to some people. Some roms seem to be worse than others. The rom in my signature is a Froyo Rom with Sense 2.0 and you don't get the gitches. It works great. Hope that helps explain it.
Click to expand...
Click to collapse
Thanks mate... Yeah, have been reading quite a bit, but didn't notice this in any of the posts on the roms.... maybe it's been discussed for ages and I've mised it
I'll check out your rom...
jnrdavo said:
Thanks mate... Yeah, have been reading quite a bit, but didn't notice this in any of the posts on the roms.... maybe it's been discussed for ages and I've mised it
I'll check out your rom...
Click to expand...
Click to collapse
It has.... most Sense3 Cookers state it... and those who don't are a bunch of liers.
Also... with all due respect to him, Haldric's Glitches fix is not a fix. It's a work around.
The only TRUE fix for the glitches, is the Desire 2.6.35 kernel... but that brings other problems.