[myTouch 3G, Magic General] pasimetes:
So here goes my story (I just hope someone will have enough patience to read all this :D I have underlined the important bits, if you're not in the mood of reading all this stuff, but could help anyway)..

Bought an used HTC Magic (Vodafone branded) from eBay UK for £175 in absolutely mint condition, no signs, scratches, no nothing. Came unlocked from carrier and with full original package. And

everything went perfect for about two weeks

..

Then, for no obvious reasons (wasn't dropped, was not exposed to water or something like that - there was done absolutely nothing that could possibly harm the phone physically), phone

started doing strange things randomly

.. And in about 3 days after it started, those things started occurring so frequently, that they made the phone absolutely unusable.

First of all, phone specs (original), before I started rooting/modding/etc:

The OS was 100% stock 1.6 Android, recovery image was also stock, which made me to believe that

phone wasn't rooted/modded ever before

.

So.. about the problem:

Action:

Turning ON the phone,

doesn't matter in which mode

(normal (POWER), recovery (HOME+POWER) or fastboot (BACK+POWER), possible endings (occur randomly):

Blue LED of death

: Screen does not react, no backlight, no vibration (which occurs when boot process starts), blue LED illuminates, nothing else happens. The only way to make it stop - disconnect the battery.

Sub-normal

: Backlight turns on, vibrates as normal, but the carrier logo (Vodafone (same as green myTouch screen in MT3G)) is not displayed, as it should be. Randomly, about 3 out of 5 times - after some time OS booting animation appears and the phone boots up, but sometimes not, always stays in this frozen-back-lit screen state.

Boots as normal.

Action:

Using the phone:

Touchsreen stops working randomly, but everything else works: I can select things with trackball, do everything, except my touch input isn't registered. To fix this, I have to push POWER button to put it into sleep and wake it up again, then touch input starts working again. (Not software issue, happens with Cyanogen 5, 6 as well as stock 1.5 and 1.6)

Phone freezes randomly, then after about 1-3 minutes reboots automatically, but reboots in one of two modes (see above for explanations):

Blue LED of death.

Sub-normal.

Sometimes works absolutely with no problems, but this has become very rare in the past few days.

Action:

Waking the phone up from sleep state:

Hardware keys illuminate, screen does not react at all. Pushing the POWER button again would cause absolutely random things:

Sometimes, the screen turns on, while the key illumination turns off, but everything works as normal, even those keys;

Sometimes, just turns off the illumination on keys and the other time using POWER/MENU button - screen wakes-up just as it should;

Sometimes, after a few more unsuccessful tries to wake the screen, everything freezes and hardware key illumination starts doing a laser show: flashes rapidly and randomly, then stops and phones reboots.

Wakes-up as normal.

To cure this -

tried everything from the software side

: tried both, stock and custom ROMs, different SPLs, different recovery IMGs, everything - none of this helped.

Tried reaching for support from my local HTC dealer, they refused to fix the phone by warranty, but took it for a paid repair. The repair quote was about £260 (more than the phone itself, which I bought used from eBay) so I refused.

They said that the

motherboard of the phone needs to be replaced

, but didn't say why. I have my own reasons to believe that the board doesn't need to be replaced and could still be repaired in the worst case.

First of all,

they didn't open the phone at all

: "VOID" warranty sticker was intact and in same position (as I made some photos of the phone to compare it before and after the service :P ). Secondly, I gave them phone with non-stock SPL, so they could think that the mainboard was swapped or something, causing all this stuff.

HTC international instructed me to ship the phone back to UK

for a warranty-covered service, so that's what I'm doing next, but before that I thought maybe someone had already faced this problem and knows the cause or even a fix for the problem.

Thanks in advance.