I really need help...

[Guest flying_machine]

... Hi all, first post here.

Think I might have fried my gpu.. if thats possible?

I unlocked bootloader, installed clockwork mod and instantly began flashing different roms to see which one i liked.

Shortly after noticed that on all of the roms, opening a game or trying to play a video resulted in the device instantly freezing and rebooting itself. Before hand the device was functioning perfectly.

I can replicate the problem with any game and any video. Have tried using superwipe since and reinstalling stock HTC android, no luck.

I have tried forcing gpu rendering in developer settings, again no luck.

Is there anything else I can try? I feel like it could be a hardware problem a.k.a. the gpu?

The phone works absolutely perfectly other than when I try to open a game or a video.

I have a 30 day fault return policy that I'm only a week into, so if I unroot my phone and reset it back to stock completely (and the problem still persists) do you think I could get away with returning it?

Do you have any advice guys? Any other ideas?

Edited May 15, 2012 by flying_machine

[Guest loskristianos]

Were you flashing the boot.img in fastboot along with each ROM that you tried, or just the ROM on its own in recovery?

The issues you're having sound very much like the problems experienced by those who've forgotten to flash the boot.img of their ROM (or flashed the wrong one).

[Guest flying_machine]

hello Kristianos, thank you for replying.

No, I just flashed the rom in recovery.

Now i'm beginning to worry that this is the cause of the problem; not flashing the boot.img.

Do you think it could be resolved by restarting the whole process along with flashing the boot.img as supposed to?

Do I just flash the boot image through recovery? Where can i find a boot.img?

[Guest loskristianos]

Yes, I strongly suspect it will resolve your problem.

The boot.img contains the kernel (and more); because HTC haven't given us full S-OFF, recovery can't write to the boot partition. This means when you flash a ROM in recovery it doesn't replace your stock kernel with the one that should be in your new ROM which, generally, means it won't work. To get around this you have to flash the boot.img that goes with your ROM from your computer using fastboot (similar to the process you used to unlock your One X in the first place when you used fastboot to flash an unlock token).

You'll generally find the boot.img inside the ROM zip, although depending on the ROM the developer may also offer it as a separate download. The fact that you mention trying several different ROMs makes me think you've paid at least a passing visit to XDA, in which case the ROM(s) you tried should have had instructions in the post you downloaded them from regarding flashing the boot.img (as well as multiple posts explaining the process), but if not here's as a quick overview (assuming you've still got the fastboot executable/binary on your PC from when you unlocked, and a copy of the boot.img from the ROM you're installing):

1) copy boot.img into the same folder as the fastboot binary

2) turn your phone on in fastboot mode (turn it off, hold vol-down and power on and it should boot into bootloader; select 'fastboot' from the menu if it doesn't automatically load into fastboot mode)

3) connect the phone to the PC via USB (the text on the phone should now say "fastboot USB")

4) on your PC open a command prompt and navigte to the folder containing your boot.img and the fastboot binary

5) run the following command: fastboot flash boot boot.img

6) run the following command: fastboot erase cache

7) from the menu on the phone select 'hboot', then 'recovery'. The phone will reboot into recovery, then just flash the ROM as normal.

That should be it. You'll need to do this each time you install a new ROM, and also if you're restoring a nandroid backup (copy the boot.img from your backup folder and follow the same procedure).

[Guest flying_machine]

Kristianos, thank you so much for a very clear and precise answer.

Also, thank you for your quick help - I have now fixed the problem.. it was because I never flashed the boot.img and now I understand why its needed and how to do it in the future.

I am so grateful, panic over. thanks again.

Edited May 15, 2012 by flying_machine

[Guest bcool15]

LOL^^ and congrats on the fix....

i ordered mine and waiting impatiently

even paid overnight

now killing time by browsing threads gathering info ..

as i have nothing else to do