Originally Posted by Th3_uN1Qu3

I fixed one for a friend using the same method for fixing failed laptop GPUs - took the shield off the CPU side, applied flux and heated with a hot air station set at 375 deg C for 3 minutes. Airflow was set to 4 liters/minute, and the nozzle was never held closer than 1cm from the board. It's the same settings that i've found to work great with laptops.

Phone is now working solid, played over 1 hour of Angry Birds and it didn't reboot, prior to reflowing it wouldn't even last 2 minutes in any game. Looks like another victim of lead-free solder.

I also applied thermal paste on the CPU, so when i put the shield back on it now acts as a heatsink as well. We'll see how long it lasts (typical reflow lifetimes are a few months to an year, depending how hot the device runs), but for now it is working great.

Is there a layman's method for this fix?

I was thinking of removing the main board completely, taking off all the plastic stickers, and putting it in a 350' toaster oven for 5 minues.
Maybe use a small contraption to apply pressure directly above and below the chip, in a way that won't warp the PCB?

I've already tried putting a grain of stock white thermal paste on the Qualcomm chip, under the RF shield, but the phone still reboots if it reaches 34'C, after ~5 min of playing PvZ.

I started to have reboots a few weeks ago.
After trying several things, changed ROM, changed SD, reload MTD0, changed voltages.
I figured it had something to do with the radio part.
I tried a newer RIL package (HTC-RIL 2.2.0131HM) but this made no difference.
Then I installed RILInfos_1.1 and I saw after a reboot this error.
[ro.ril.last.radio.fatal]: [IST0 (mdsptask.c:00476) (1)]
Searching on this error it seens to be caused by an old SIM card and the network having enabled 3G/4G.

Then I remembered that the network name changed from "Vodafone NL" to "3G Vodafone NL" a few weeks ago.
So I went out for a new SIM and no more reboots!
I was told that I had an old SIM card.

The RIL package and info app can be found in this thread: http://forum.xda-developers.com/showthread.php?t=902752

Some rom does that sometime it not really a big deal unless it does boot loop

Sent from my HTC Desire HD using xda premium

Originally Posted by Th3_uN1Qu3

I fixed one for a friend using the same method for fixing failed laptop GPUs - took the shield off the CPU side, applied flux and heated with a hot air station set at 375 deg C for 3 minutes. Airflow was set to 4 liters/minute, and the nozzle was never held closer than 1cm from the board. It's the same settings that i've found to work great with laptops.

That should be the same as putting your gfx card into the oven at 200 something degress.

Somebody sold me a desire with this defect and I guess I cant RMA it.
The CPU is in the bottom of the phone and I have to unscrew the star screws first?

Originally Posted by sony66

Then I remembered that the network name changed from "Vodafone NL" to "3G Vodafone NL" a few weeks ago.
So I went out for a new SIM and no more reboots!
I was told that I had an old SIM card.

I ordered a new sim and that changed nothing, if I direct a 120mm pc fan at the back of the phone it doesnt reboot while downloading data.

Its the same effect as this

Originally Posted by leerees

However, I found out if I hang the phone out the window it will not reboot at all. It's about 6 degrees outside here in the UK so the cold weather stops the phone from overheating.

@raha0007
You should try to get debug output to see what the cause is.
But it looks like a badly soldered MB, and the only thing you can try is to reflow the board, preferably only the chip causing the reboots. (using a hot air soldering gun and chip shields).

TJ has done some interresting RE on the radio which can be found here
http://tjworld.net/wiki/Android/HTC/.../RadioAnalysis

I wonder if the command AT+SIMTYPE gives different values for the old and the new SIM.
dunno if this can be implemented in RILInfos

Originally Posted by sony66

I started to have reboots a few weeks ago.
After trying several things, changed ROM, changed SD, reload MTD0, changed voltages.
Searching on this error it seens to be caused by an old SIM card and the network having enabled 3G/4G.
So I went out for a new SIM and no more reboots!

A few days later my phone started to freeze and refused to boot.
I went to the shop and they have sent my phone to HTC because the hardware was faulty...

I now have a new Desire, did the full stuff and it is running very stable now.
I have the same SD (Samsung 32GB class 10) and SIM
2GB ext4 partition.

I am now experimenting with newer kernels from droidzone but most of them are not very stable. I am not sure if he build a custom kernel for this runny ROM. But I installed kmods_sf_020212_105420.zip to have all the kernel modules.

Only problem I now have is that the compas needs calibration after every restart of a compass app.

I am very happy with this ROM now! tnx!

Sorry for not replying, i have to look for the option to get email notifications about PMs on this forum.

I have found (the hard way, obviously), that there can be two causes for the reboots.

One is the mainboard, where it reboots randomly or only when stressed. This is fixable, you may not even need to reflow, just install a ROM that supports undervolting and tweak the voltages as far down as you can.

The other is the radio board (the board at the top with all the flex cables), when you get a continuous reboot loop no matter what you do, and it only works in fastboot or bootloader. I bought a Desire with the second issue, unfortunately it was locked and S-ON, so the only thing i could flash on it was the RUU (since i was unable to get it to boot fully, i couldn't root or S-OFF it). All mainboard voltages checked out okay, and i reflowed every large chip to no avail, it just did the same thing.

When i attempted to flash the RUU on it, i told me "Failed-PU" at Radio, and then i had a brick. I tested 2 other mainboards with it (known good) and no go, not even the charge LED lights up. I've been out of town for the past 3 weeks, i'll buy a new radio board for it and come back with updates.

Tonight i have one in with minor reboot issues, reboots only when stressed, or just out of the blue. Pulling the battery and re-inserting it always makes it come back for a while. Will undervolt it and see how it goes.

Edit: Seems like this one isn't as minor as it seemed at first sight either. Worked for a bit outside, almost immediately rebooted inside, and now i can't get it to stay on even if it's kept cool. Just like it happened with the one i bought...

This one was S-ON too. I managed to S-OFF with Revolutionary under Linux. It didn't work in Windows, it just sat at waiting for device (just like on mine). At least i won't be bricking this one completely. Flashed CyanogenMod recovery, but can only get in it like once in 10 tries, and any option just hangs so it's useless. I can sit in hboot or fastboot all i want, but anything else reboot loops or gets stuck at the HTC logo. Interesting bit: fastboot oem reboot ALWAYS hangs or reboots after it gets past hboot, a normal boot sometimes succeeds...

Tried to flash an official RUU via fastboot:

fastboot oem rebootRUU
fastboot flash zip rom.zip

Flashed okay, it's still alive, still S-OFF, but still rebooting too. I'll call it a night and leave it alone. Now i'm sorry i didn't bring mine with me, i could have swapped boards and see where that would get me.

Aaaand update.

I left it for ~10 minutes in the fridge and it booted up fine... Today i was able to install an undervolted ROM and tweak it. So far, so good, but restarting it is still a bad idea... I have found that once booted, it'll run in conditions in which it'll bootloop permanently if you attempted to power it on. And it doesn't seem to depend (only) on temperature, but rather on absolute power consumption at a given point. Because when it bootloops, it'll keep bootlooping regardless of how cold you make it. Until you pull the battery, put it back in, and allow it to sit for a few minutes, no go. I assume it uses more power during boot than in standby, so that seems to support my theory.

I'm starting to suspect a power problem. A bad CPU or a corrupted NAND wouldn't complete a full flashing process... There's a single chip powering all the goodies on the mainboard, and if that hiccups, bam. Actually what undervolting does is control this very chip - at least the section feeding the CPU Vcore. Which lowers the consumption and... you get the idea.

Oh, and the camera autofocus seems to have crapped out due to condensation (all that moving the phone in and out of the fridge), but that may fix itself eventually.

Edit: Yup, autofocus fixed itself. Still having the same issues tho. So as a conclusion, my prime suspect would be the power management IC, TPS65023. Not the CPU, not the RAM, not the NAND, since there's no way in hell a phone with bad logic hardware would be able to flash a full ROM and still work afterwards. I don't feel like dropping 10 euros for one of those ICs tho, since this is not my phone anyway. To be continued.

As a personal conclusion, when you get your first bootloop, pull the battery, keep the phone off until you get to a computer, and undervolt immediately. You may get away with just that. So far only 1 of 3 did...

Overheat and reboot - common "early version" Desire problem.
So if it's bothers you (if you use app2sd, google maps,, browser, games - it's really annoying) - take it to service.
(replace motherboard will cost you about 100-150$ (almost like new desire on ebay), if it's not on warranty).

PS Yep, it's defect, but usually it takes time to fight with service for free replace).

htc desire rebbots its own...

---

i also have htc desire with same problem, only 1 solution u can do about this problem, when ever u turn off your phon turn off it in airplane mood, and don't use mobile data on it, my phone works fine with these cautions

Originally Posted by isaw

I'm getting the reboots now.

Last nite I was watching some youtube before bed when the battery warning come up that I'm 14% low. Fair enough, so I plug it in.

Within about 2 seconds it reboots. This has happened before, sucks but ok, i'll deal with it.

However it reboots, then restarts... gets to the HTC screen, little chime, reboot. WTF!? Same again and again, etc. I'm stuck.

I take out the battery, give a few minutes, try again. Same thing. F##k!. So I do a hard reset - maybe it was an app?

This time it gets to the screen where I start entering my google details, crash! reboot, loop, reboot, loop. etc.

I leave it alone for 40 mins turned off on charge. Try again, ok. I'm back to a defaultly wiped Desire. It's stable so far, but damn - what the hell was that about?? I just called up HTC and told them the details and they want me to stick with it for 24 hours to see what happens. This doesn't seem right at all. Maybe I'm getting an overheating issue as well.

Interestingly it loaded up with a live wallpaper I had since turned off - almost as tho it was using some old default config. Had GPS and Wifi on. really, really annoying.