Develop Bugs

[Q] "Main version is older"-Rom 2.15.118.1 -How to beat it ?

It is an brand Desire, I rooted, I loaded custom rom (worked fine), but the ROM manager screwed up something. I guess, it reflashed the bootloader (or recovery?), but failed.
Now the desire cannot boot. It stucked at the screen, with logo.
The bootloader says :
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.10.05.23
If I try to go to RECOVERY the screen goes white, and nothing happens.
If I put the PB99IMG.zip to SD card, the HBOOT finds it, but says, "Main version is older"
Is any way to reFlash the rom ?
What to do ?

have your tried installing a RUU then restarting all over again?

Yep, I tried, in USB_HBoot and USB_FastBoot mode (only available for me) but I`v got error (152 or 170).
Should I use some specific version RUU ?

U should read all NEwbie Threads more carefully again and again ! If u do this nothing can go wrong !U have to easily reflash the recovery! Just use Google!

xtcislove said:
U should read all NEwbie Threads more carefully again and again ! If u do this nothing can go wrong !U have to easily reflash the recovery! Just use Google!
Click to expand...
Click to collapse
From that I read, to make reflash the recovery You need a loaded sytem.
This is what I do not have
xtcislove said:
Just use Google!
Click to expand...
Click to collapse
Or I'm wrong... - Then please help me

Have you tried
fastboot flash recovery "recovery file name".img
Click to expand...
Click to collapse
while in bootloader mode?
*note* you will have to download the android sdk, copy the recovery image into the tools folder, start cmd in tools folder and then type that command in.

Yes, I know sdk - already tried - I get protection error, not flashed.

h3llb3nd4 said:
Have you tried
while in bootloader mode?
*note* you will have to download the android sdk, copy the recovery image into the tools folder, start cmd in tools folder and then type that command in.
Click to expand...
Click to collapse
He has S-on. That will not work.
I think you need to try and find a rom which contains your HBOOT and try and flash that.
Sent from my Amiga 500 using Workbench

Right my bad
anyway, have you tried other PB99IMG.zips ?
find more here
http://shipped-roms.com/download.ph...00.28U_4.06.00.02_2_release_126175_signed.exe

http://forum.xda-developers.com/showthread.php?t=768256

excogitation said:
http://forum.xda-developers.com/showthread.php?t=768256
Click to expand...
Click to collapse
As I wrote before: "I am not able to fully load the sytem"

For me it sounds like recovery did not successfully flash from unrevoked - but how can I unscrew this ?!?
Now, I launched successfully RUU under USB_Fastboot !
But I tried a number of stock images-roms (with GoldCard - my phone is brand one) and each time I get error :
140:BOOTLOADER VERSION ERROR - on Desire screen : "Main Version is older"
My rom version: 2.15.118.1
What can be done ??? How to beat it ?

Sorry for the previous inappropriate answer.
So if you can still boot to hboot just install the drivers from here
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
assumed you're running Windows and then root using:
http://unrevoked.com/#desire
After that you can install basically whatever you want (don't install stuff not matching your phone though) from the recovery
menu.
Good luck

excogitation said:
Sorry for the previous inappropriate answer.
So if you can still boot to hboot just install the drivers from here
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
assumed you're running Windows and then root using:
http://unrevoked.com/#desire
After that you can install basically whatever you want (don't install stuff not matching your phone though) from the recovery
menu.
Good luck
Click to expand...
Click to collapse
Unfortunately I am not able to use Recovery option :
As I wrote:
"If I try to go to RECOVERY I see logo for 2 sec., after screen goes black and nothing happens (The compters sees the Android USB Devices-My HTC)."
Any other ideas ?????

You've been told what to do on Androidforums so I'd suggest following that

You mean this :
You have a bit of a problem then. You could try a branded update with a higher release number (e.g. Three's froyo), and then downgrade that.
But I can not find update with higher rel. than 2.15.118.1

pawel_kd said:
Unfortunately I am not able to use Recovery option :
As I wrote:
"If I try to go to RECOVERY I see logo for 2 sec., after screen goes black and nothing happens (The compters sees the Android USB Devices-My HTC)."
Any other ideas ?????
Click to expand...
Click to collapse
Hi! I'm a new member and this is my first post !!!
When the screen goes black, did you try to hold the volume up button when pressing the power button. May be ...
pawel_kd said:
For me it sounds like recovery did not successfully flash from unrevoked - but how can I unscrew this ?!?
Click to expand...
Click to collapse
I think the same happened to me when i tried to unlock my Desire. I juste had te redo it until it worked.

I made a little progress - I have access to recovery, then I press VolUp+Power there is op screen:
E:/Can`t open /cache/recovery/command
I tried fake-recovery but its impossible to flash-error - flash aborted.
Can I do something now and maybe and solve my problem?

So, I give up
I`m sending the phone to an authorized service.
We'll see - warranty success or not (
Thanx 2ever1 for time and help

Give it another try, may be...
Sorry mate! Didn't read your answer till now. Did you try other RUUs. There's a bunch of them in that URL: shipped roms (it is somewhere in the forum juste search it) for Bravo.
For me, to upgrade from the stock "Eclair", i used this one "RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed" and it worked just fine (before that i upgraded via stock zip to froyo but the unrevoked didn't work). Then i re used the unrevoked3 and it worked in third attempt.
I guess, there was a problem in the way the phone handels the transfer of data (USB dosen't act quick enough to send the right amount of data). So the first time when my phone bouted up, it couldn't get all data from the unrevoket script at the right speed so it continued booting with the old version of recovery prog without routing.
After it worked, i upgraded my radio to the "32.48.00.32U_5.11.05.14" via recovery and zip (found somewhere in the forum) and it was ok.
At least give it another try. It's all yours.

AlphaRav soft-failed - no restore files

"precedure soft-failed. we were unable to flash HBOOT blabla reminder: your phone is NOT bricked. restart the procedure and try again. you may need to restore your most recent nandroid backup from restore.."
omg.. i dont know what to do! im totally desperate Q_Q cannot restore something or maybe i'm to dumb to do?! or maybe i only dont know how it works... i cannot use my mobile, can't start it 'cauze it always starts this alpharav thing. i only want to get it s-off and get another rom, but know i only want my old mobile back now, working, with no problms and so on. i've read the forum/internet but i didn't find hints can help me or i understand. i'm not a pro! please, dont ask me then why i wanna do that! -.- a friend of mine did it with his samsung and it was ready rootet in some minutes.. why must it be so difficult with desire???
if its of interest:
bravo pvt4 S-ON! (grrr)
hboot-0.93.0001
microp-051d
touch panel-synt0101
radio-5.11.05.27
please tell me anything which let my mobile works less or more like before this sh**! and do it for a noob if i wont get is s-off please give me a link to an update.zip file!! i cannot restore anything. it has alwasy MISC faults... i could cry.. my head hurts -.-
P.S: if anybody could explain it in german it would be soooo nice o_o but english is also fine, better then nothing

http://forum.xda-developers.com/showthread.php?t=696189

Well do as descriped???
enter recovery(vol down+power and chose recovery using volume buttons and power) From the recovery you can restore the nandroid you were told to make before running alpharev.
Also does it still show s-on in the bootloader? and the alpharev thing you are talking about that it alway start up in, is that the screen with the joker? Because that means it got to flash something.
edit: and if you didn't do a nandroid backup, you can just flash a new rom and run alpharev again...

Which rom are you using, and is it rooted stock?
I couldn't get alpharev to recognise my device till I wiped everything and flashed oxygen rom. You can always change it once you have s-off as mortenmhp says.

hi guys,
rubyspida said:
it has alwasy MISC faults...
Click to expand...
Click to collapse
from my own i am afraid that there'nt any nandbckp and the unrevoked is not fully functionnal. don't know if uou still go into recovery.
when power on keep volume down and you should normally get into recovery.
if it work do as morten says.
need answer to thos questions

thank you for your answers so far!
well, i thought i did anything like descript... if i try recovery something it always tells me: checking MD5 sums, MD5 mismatch! E:CAN'T mount CACHE:recovery/log E:CAN'T find MISC
i'm still S-ON if i press vol down and the power button, so i cant install new zips/roms and if i start the phone the alpharev SLPBOOT 2.0 starts - nothing with a joker. i cant start my phone normally to start flashing again and as i told i cannot do any restore stuff. i tried to install leedroid 2.4 a2sd: assert failed: write_raw_image ("/tmp/boot.img", "boot"), E:ERROR in /sdcard/Leedroid.. (status 7) Installation aborted.
if i had knew it would be soooo complicated i wouldnt do it..
well, and if i get an RUU ROM from http://forum.xda-developers.com/showthread.php?t=695667 (but which one? i guess i have GSM, there a lot of roms o.o) it will work as it does before?
EDIT: ok, i downloaded this RUU RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release as zip... but i cannot install it: fomratting system: E:CAN'T format system, E:Failure at line 6.. installation aborted. everything is about this E: and MISC thing. what is it? how can i fix it?

k, i think i managed it and installed a RUU via PB99IMG.zip methode. i wont never thouch my phone's software again! stupid s-off.. ^^ i'm so glad that it works now.. thank you all for your help

[Q] HTC G2 stuck on boot screen! Help!

My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
ClockworkMod Recovery v3.0.2.4
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
Thanks
-Kagen

notKagen said:
My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
Thanks
-Kagen
Click to expand...
Click to collapse
How did u get it bricked?

xudsa II USERT said:
How did u get it bricked?
Click to expand...
Click to collapse
A friend rooted it over a year ago.
Everything worked fine, so we flashed a ROM. (don't remember which one)
That worked fine, then few days later things on the phone started to fail. Slowly more and more things failed. Then I was forced to reboot the phone.
When I rebooted It stuck on boot screen. now I get those logs in recovered that I originally posted.

To say the worse, it sounds like a corrupted file system acutally . You can get to HBOOT screen right? (Vol + Power On)

xudsa II USERT said:
To say the worse, it sounds like a corrupted file system acutally . You can get to HBOOT screen right? (Vol + Power On)
Click to expand...
Click to collapse
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.

notKagen said:
Yes, I can get there very easily.
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
Click to expand...
Click to collapse

EDITED: GAVE EXPLAINATION
notKagen said:
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
Click to expand...
Click to collapse
Erm.. I'm not too sure, it could be just maybe a small error fixable by 'replacing', but then again it could be a physical damage (bad sectors, but those are usually very very rare).
If your bootloader does function fine, it could be the former (though not being able to mount in recovery sounds like a bad sector). It is possible that you can load a rom through ur sd card and restore it through the bootloader. (I'm still learning that part). Be very very very careful! You can actually make your phone not work! Do a lot of research, and don't rush! Hopefully someone with much more experience can help from here on.
I'll explain here: if your phone does not boot, usually it could mean that some files cannot be read or are missing, so the phone will not boot android. The fact that the recovery states that it cannot mount the filesystem could mean that there is a possibility that your memory filesystem may be corrupted. But, since it can boot the bootloader without problems, there is a high possibility that the problem lies in the recovery files being problematic themselves. In that case, you can load a original rom (BE VERY CAREFUL BEFORE YOU DO SO, I ASKED HERE, so this could be a jumping board for you.). A mention, u must be careful, loading a full ROM includes loading the bootloader as well, so it may cause your phone to not even load the bootloader.
I really think someone with better experience should help from here on, i dont want to brick your phone :/

xudsa II USERT said:
EDITED: GAVE EXPLAINATION
Erm.. I'm not too sure, it could be just maybe a small error fixable by 'replacing', but then again it could be a physical damage (bad sectors, but those are usually very very rare).
If your bootloader does function fine, it could be the former (though not being able to mount in recovery sounds like a bad sector). It is possible that you can load a rom through ur sd card and restore it through the bootloader. (I'm still learning that part). Be very very very careful! You can actually make your phone not work! Do a lot of research, and don't rush! Hopefully someone with much more experience can help from here on.
I'll explain here: if your phone does not boot, usually it could mean that some files cannot be read or are missing, so the phone will not boot android. The fact that the recovery states that it cannot mount the filesystem could mean that there is a possibility that your memory filesystem may be corrupted. But, since it can boot the bootloader without problems, there is a high possibility that the problem lies in the recovery files being problematic themselves. In that case, you can load a original rom (BE VERY CAREFUL BEFORE YOU DO SO, I ASKED HERE, so this could be a jumping board for you.). A mention, u must be careful, loading a full ROM includes loading the bootloader as well, so it may cause your phone to not even load the bootloader.
I really think someone with better experience should help from here on, i dont want to brick your phone :/
Click to expand...
Click to collapse
Alright man, I'll follow the link but I don't know if this will help you. Some things when I am in HBOOT and I hit them they do nothing. Just freeze the phone. I don't know if that changes things.

notKagen said:
Alright man, I'll follow the link but I don't know if this will help you. Some things when I am in HBOOT and I hit them they do nothing. Just freeze the phone. I don't know if that changes things.
Click to expand...
Click to collapse
Okay, I tried what you said but no success. My ClockworkMod seems to not be mounting. Because of the Errors I posted previously in my first post. So this way I can't flash anything from recovery because it will just stay on that screen with the top hat and the orange circle with the arrow. Nothing happens. If I tap the power button, it just goes back to the menu.
Should I be updating clockwork somehow?
Is there another way to flash?
Could there be a problem with my SD's? (i've tried on 2 different ones)
Do you have any ideas?

This is an educated guess, but you might want to try flashing the stock firmware back onto the phone and trying again, and ensure the MD5s match. You could even follow the instructions in the wiki to give CyanogenMod ROM a try; that's what I'm using now and is the more widely developed and recognizable ROM that I know of.
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)

Firstly, don't select stuff with power button in clockwork, use the camera or trackpad.
Secondly, those errors may indicate a bad emmc, which is a hardware defect, and cannot be fixed. More info here
You can either go for a warranty replacement, or you can boot cm7.1 from your sdcard, using Catherall's instructions
-Nipqer

EdWaRdW818 said:
This is an educated guess, but you might want to try flashing the stock firmware back onto the phone and trying again, and ensure the MD5s match. You could even follow the instructions in the wiki to give CyanogenMod ROM a try; that's what I'm using now and is the more widely developed and recognizable ROM that I know of.
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)
Click to expand...
Click to collapse
Sure, I can try that. Is there a step by step....don't really know what im doing.

Almost 100% you have a bad emmc, there is no fix for this, nipqer sent you a guide to run an os off your sdcard and this may be your only 'fix'
You can try and flash a new recovery via fastboot and a rom as well. But my best guess is your sol, try to warranty it if possible, run os off sd, or sell it for parts and get a new one
Sent from my HTC Vision using xda premium

demkantor said:
Almost 100% you have a bad emmc, there is no fix for this, nipqer sent you a guide to run an os off your sdcard and this may be your only 'fix'
You can try and flash a new recovery via fastboot and a rom as well. But my best guess is your sol, try to warranty it if possible, run os off sd, or sell it for parts and get a new one
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Alrighty! Thanks for your help!

reflash a new ROM
notKagen said:
My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
Thanks
-Kagen
Click to expand...
Click to collapse
Dude This happened to me too first if you downgraded to froyo and if you kept a nandroid backup of it restore to the froyo nandroid backup BE SURE THE NANDROID BAKUP OF THE FROYO VERSION IS A ROOTED ONE OR ELSE YOU'LL BRICK YOUR PHONE OR SCREW UP THE ROOT!! then after that flash another ROM using fastboot in bootloader mode
okay heres what to do
1.Open A CMD window in windows
2.Navigate to the folder where you have fastboot for example cd...
cd...
cd /
C:\Android SDK\Platform Tools
then you should also have ADB at the same folder together with Fastboot
then plug your phone while it fastboot mode in Bootloader
it should say "FASTBOOT USB"
3.Then verify that your computer recognizes your Phone by typing "fastboot devices" without (" ")
4.put the ROM.zip on the same folder where you have Fastboot and ADB
5. type in fastboot clear cache (I don't know the exact command but you need to clear cache)
6. AFTER CLEARING CACHE TYPE IN "fastboot flash zip ROM.zip (REPLACE "ROM" with the right ROM name it ahould be like ICS.zip or whatever your gonna flash
7. just let it do its job
8.Celebrate if it worked =))
PM me if you need more help
SOMEONE PLEASE CORRECT ME IF I DID SOMETHING WRONG
-goodluck

Help help help !

i was using my nexus with vicious JB and it randomly froze. i did a battery pull and all i would get is up to the google logo and then it wourd restart. did a batt pull. wiiped and formated everything. then decided to get off JB as i its been buggy for me. i flashed aokp, trinity 1500mhz 512mhz kernel. then i got the trinity logo, halfway through aokp, then freeze and reboot. kept doing this. i wiped everything a million more times but this keeps happening. i tried to go back to stock but the image-imm76k or something like that file had boot.sig could not be found, and same thing for the other fiels. i redownload the file and same thing. soemone please help !

follow the guide in my sig. it was made by efrant.
it will take you back to stock.

i keep gettin failed when it tries to write system.img

what does fastboot say is the reason it failed?

FAILED (remote: write fail)

Dri94 said:
i keep gettin failed when it tries to write system.img
Click to expand...
Click to collapse
Did you unlock your bootloader?
Sent from my Galaxy Nexus using Tapatalk 2

yea and it says
"Lock State - Unlocked" in red words

Hmmm. Maybe change USB ports, and maybe your USB cable.

^its not that

[solved]
7zip > winRar when extracting files

!Updated -Realy need some help "rooting" my desire

Hello to all!
I am completely new to flashing phones, and cant get it to work on my Desire (Europe/Norway).
The case is, that i replaced the glass (not the digitizer) on my phone, and when i went to turn it on, it only stuck on the HTC logo and vibrated a few times, it never came past the HTC logo.
So, i tried reading a bit, and i tried "rooting" my phone, witch did not go well, i guess i did the whole prosess wrong.
I have tried making a goldcard, but that did not work, and i have tried installing a new rom (RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed) but that just got stuck and gave me and error that it was the wrong ROM.
Now, when i try turning on my phone, the screen is black with a white HTC logo, and white warning signs in every corner..
When i press power+volume, this is the information i get:
Bravo PVT1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
Touch panel-synw0101
Radio-5.11.05.27
Aug 10 2008 17:52:18
RUU
So, as you can see my "fastboot" menu and options are gone.. But my device gets discovered on my pc when i plug in the USB.
Can anyone please tell me what to do step by step, in the right order? (Like you are explaining to your mom what to do)
Would realy realy appreciate it.
Thanks!

Your phone is stuck in RUU mode. Try running the 2.3 RUU.

Thank you sir, for your response.
On the page you link to me, i cant seem to find the agree button, just plain text and nothing else. Is there anyway you can download it and upload it to megaupload?
Thanks

k1mzor said:
Thank you sir, for your response.
On the page you link to me, i cant seem to find the agree button, just plain text and nothing else. Is there anyway you can download it and upload it to megaupload?
Thanks
Click to expand...
Click to collapse
Ah you're right. I've got it downloaded on my PC, so I'm currently uploading it for you.
Edit: here it is: http://www.androidfilehost.com/?fid=23329332407586107

Hello again!
I have now tried the RUU you gave me.
At first, it "froze" at 26% when sending radio, and the phone vibrated a few times.
I den shut it down, and restartet the process. It then came to about 80% and gave me the error 152: Please get the correct ROM update...
When i disconected the cable from my computer, it says;
RUU
Parsing... [downloaded ZIP]
[1] RADIO_V2 - FAIL-PU
[2] SPLASH1 - OK
[3] RECOVERY - OK
[4] RADIO_CUST - OK
[5] BOOTLOADER - OK
[6] USERDATA - OK
[7] SYSTEM - OK
[8] BOOT - OK
Partition update fail!
Update fail!
Keep in mind, i have done nothing else to the phone, exept formated the SD card in FAT32.

k1mzor said:
Hello again!
I have now tried the RUU you gave me.
At first, it "froze" at 26% when sending radio, and the phone vibrated a few times.
I den shut it down, and restartet the process. It then cam to 80% and gave me the error 152: Please get the correct ROM update...
When i disconected the cable from my computer, it says;
RUU
Parsin... [downloaded ZIP]
[1] RADIO_V2 - FAIL-PU
[2] SPLASH1 - OK
[3] RECOVERY - OK
[4] RADIO_CUST - OK
[5] BOOTLOADER - OK
[6] USERDATA - OK
[7] SYSTEM - OK
[8] BOOT - OK
Partition update fail!
Update fail!
Keep in mind, i have done nothing else to the phone, expect formated the SD card in FAT32.
Click to expand...
Click to collapse
Sorry to tell you, but it looks like you have a radio brick. This type of brick doesnt really have any solution. See here for more info on why this is the case.

So there is basicly nothing that can be done? A new board from ebay?
With your 2.3 update, my rom is 2.29.405.14 and 2.3 is image version 3.14.405.1

I dont need to root this phone, i just need it to work. And is it so, that rooting it is a litle more work than to just put in the original image? I mean, i have read so mutch about S-OFF, goldcard etc, that i am unsure. Is this rooting? And what i'm trying to do (Format SD card, download a image and press next) is recovery? Maybe i ned the image that is already on my phone? ( 2.29.405.14)

k1mzor said:
I dont need to root this phone, i just need it to work. And is it so, that rooting it is a litle more work than to just put in the original image? I mean, i have read so mutch about S-OFF, goldcard etc, that i am unsure. Is this rooting? And what i'm trying to do (Format SD card, download a image and press next) is recovery? Maybe i ned the image that is already on my phone? ( 2.29.405.14)
Click to expand...
Click to collapse
I think you might have mistaken but if you need more help but try pressing power button with volume down and see what it gets into first?

A little update!
I have been reading a lot on this page, and i came across a few posts that suggested putting the phone in the freezer.
So, i put the phone in the freezer for about an hour, i copied PB99IMG downgrade from Alpharev to my SD card, and turned my phone on.
I then had the bootloader options.
But, the phone never asked me to update the zip or anything, green text with checking ... came up a few times.
So, after that i pressed bootloader, and i installed the RUU_HTC Desire Android 2.3 Upgrade (Gingerbread) with sucess!
The phone then restartet with white screen and green htc logo. It restarted a few times, uintil it started to vibrate.
I went in to bootloader again and pressed recovery, it completed the process and the phone started up like normal.
But when i was about to unlock the screen the phone turned off, so i installed the RUU one more time, and it kept restarting when it was done..
What did i do wrong? And what can i do now to get it too work?

Tried moving the rom from the RUU_HTC Desire Android 2.3 Upgrade (Gingerbread) ROM in to the SD card while renaming it to PB99IMG and running it from the bootloader. When it had completed it said:
Main Version is older (i think)
Update failed!
Restart?
But it does complete with no error if i connect the phone to my computer and run the .exe?
Sigh...

I have found the problem and the solution..
This is a phone that only works in the freezer.. Need to get one hell of a freezer now.

This got me thinking and some time on google, looks like this is a common problem.
But, i never had this problem before my screen got damaged, and i replaced it. And the phone never feels warm when it restarts, it is actually cold.
So, maybe there is a faulty sensor in the phone causing it to think that it is overheating. Anyone know anything about this? If i can find the sensor, maybe i could just.. Remove it?

Is 2.2 the original android version on this phone? Maybe the 2.3.3 causes the overheat, so i was thinking on downgrading to 2.2
Where can i find the original 2.2 .exe?

Will the RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe work with my 0.93.0001 HBOOT?

2.3.3 doesn't 'cause' it to overheat...
You can try to flash any compatible RUU you want, it is highly unlikely you'll properly fix a radio brick which is a hardware issue

Radio Brick? How can it have a radio brick when the phone is working? But only in the freezer tho.
I wondered because i never had this problem on the phone before i changed the screen.

k1mzor said:
[1] RADIO_V2 - FAIL-PU
Click to expand...
Click to collapse
- This bit means radio brick
- You can only get it to work in a freezer
There's not much more evidence you need to show that unfortunately you have a hardware issue...