[HD2 Android Q&A, Help & Troubleshooting and Genera] Cotulla:
I will post my official answer here:

(some parts of text are from private talk with davinci2007)

Possible reasons of issues:

1)Errors in HTC code (they are also people and they can make errors / buggy code)

After two years, phone become a bit different. Nobody knows at the developing stage what issues can appear after X months of usage.

2)Hardware failures. Temperature and etc. NAND chip located near CPU and I think it got all hot from it too. Often high load may be source of problems.

3)MAGLDR issue.

I am not idiot (at least I am think so :D ) and I never wanted to lost my device too.

So I make MAGLDR as safe as possible. More about it below.

4)OS issues. Issues caused by using different Operating Systems. (Android, WP7, WM65)

5)Usage issue. (Users do wrong actions with device: over clocking, removing USB cable at flashing and etc)

About MAGLDR safety:

It never modify any data on NAND before SPL and SPL. Because modifying any data there is very dangerous.

As well MAGLDR never mark any blocks as bad! Bad blocks are only marked by Radio, SPL and Operating Systems (like WP7 WM65 Android).

The next thing: CPU contains inside device called MPU (Memory Protection Unit) which designed to limit access to NAND memory.

MPU disallow to modify any data before SPL and SPL too (it was a primary problem with HSPL development however, if you still remember old good days ;) ).

So I don't see how MAGLDR can cause this issues.

Some answers:

I don't offend anybody, but it's only personal opinions of some people :)

They heard some words from me, without knowledge about other things :)

I am working with LEO almost 2 years already and seems know it as my five fingers :D

As well cLK also can cause issues. who tells that it can't?

I am not against cLK, but I don't like when somebody starts holywar.

I respect cedesmith and even helped him with some stuffs for cLK before ;)

Well, I can't read German language, but Google translate helps me a bit.

I respect those people who repair devices, it's hard job, but they have not deep knowledge about LEO.

For example they said that last 24mb used for badblock replacing, but it's not true - they are used in WM65 as EXTROM for storing Facebook files (used inside FacebookSDK.dll somehow :eek: ) and for faster WM65 boot (caching).

And some words there tells "I do not know yet exactly where the errors are possibly".

Please examples?

btw, I remember some people had Radio RSA fail errors _before_ MAGLDR release. isn't it?

we can look to forum history:

21st August 2010, 08:44 AM:

http://xdaforums.com/showthread.php?t=760906

15th May 2010, 01:53 PM

http://xdaforums.com/showthread.php?t=682047

14th January 2010, 01:48 PM

http://xdaforums.com/showthread.php?t=614630&page=2

14th January 2010, 06:09 PM

http://xdaforums.com/showthread.php?t=618084

All this threads was started before MAGLDR release. Much more other examples, you can find via Google :)

So it means that this problem not caused by MAGLDR and it's initial issue with (some?) LEO devices?

Maybe most users, who install MAGLDR, they are experienced users and they flash new stuffs everyday? it cause big load to NAND and destroys it faster.

Well, other facts: some my MAGLDR testers are using MAGLDR for year now on LEO and their devices are still alive.

My device also alive from the beginning - from HSPL development :)

My personal opinion: this issues caused by 1)wrong user actions 2)bad quality of components 3)bad design (HTC, overhot and etc)

At the end I will say the next thing:

I am interesting to improve my hobby projects and look at this problems, if somebody can provide more information.

Dumps from killed devices, ability to test something on such killed device and etc.