Develop Bugs

htc desire doubt about installing rom

hello. im buying a desire tomorrow and i have some doubts.
can you give a link with some guide to install some new rom into desire?my previous phone was a samsung i8910 and almost every week i was instaling cooked roms but in android the process seems a lot different. i've seen some cool roms but i dont want to screw up the phone. i'm running windows 7 64bits. hope that's not an issue. thanks in advance

Follow this instruction to root and flash custom roms:
http://android.modaco.com/content/ht...-1-21-support/
In the beginning of that process you need to make a gold card, instruction can be found here
http://android.modaco.com/content/ge...ng-a-goldcard/
After everything is done, you should be able to flash whatever (compatible) rom you want. My recommendation is this
http://android.modaco.com/content/ht...nline-kitchen/

However, you must take note that there's some random USB bricking going on when flashing roms now.
You might want to have a look at this thread here.
Personally, I feel that flashing with Linux is more stable than using Windows.
I started rooting with Windows 7 and some problem occur halfway through the process.
I rebooted my pc to Ubuntu and continue the rooting process and everything went well.

I did everything on my desktop with 64-bit Windows 7 without any problem.

problems after installing custom rom on htc dsire
*
Hi there I’m even scared to write…
Newbie Noobie here. Greetings!
Got myself a birthday present a few days ago – HTC Desire.
If it helps, here are the details:
======
Firmware version: 2.2
i rooted my phone and then followed the steps to install custom rom
Anyway, here’s my problem (there were posts about it before as well).
Once I reach point 5 in Step 2 [i.e. Turn off your phone & turn it back on holding POWER + VOL DOWN then use vol up/down to scroll down to ‘Recovery‘ and power to select.] after I click ‘Recovery’ my screen either stays white with the green HTC logo or just goes black – in either case, that’s it… nothing happens and no buttons work.
The first time it happened I almost got a heart attack (well, which noobie didn’t?) because I thought I’d just bricked my baby… Right now it is still the only way for me to do ANYthing after getting the black screen…
Any suggestions/help will be more than welcome! Thanks in advance!!!
(And sorry for the long post… I always need long intros and all the details listed to make myself as clear as possible)
Please do help me
i am nearly crying while typing it
email me the response
cheers
Raj

rajverma3135 said:
*
Hi there I’m even scared to write…
Newbie Noobie here. Greetings!
Got myself a birthday present a few days ago – HTC Desire.
If it helps, here are the details:
======
Firmware version: 2.2
i rooted my phone and then followed the steps to install custom rom
Anyway, here’s my problem (there were posts about it before as well).
Once I reach point 5 in Step 2 [i.e. Turn off your phone & turn it back on holding POWER + VOL DOWN then use vol up/down to scroll down to ‘Recovery‘ and power to select.] after I click ‘Recovery’ my screen either stays white with the green HTC logo or just goes black – in either case, that’s it… nothing happens and no buttons work.
The first time it happened I almost got a heart attack (well, which noobie didn’t?) because I thought I’d just bricked my baby… Right now it is still the only way for me to do ANYthing after getting the black screen…
Any suggestions/help will be more than welcome! Thanks in advance!!!
(And sorry for the long post… I always need long intros and all the details listed to make myself as clear as possible)
Please do help me
i am nearly crying while typing it
email me the response
cheers
Raj
Click to expand...
Click to collapse
phone info pls
what did you use to root your phone? unrevoked?
you probably have a bad recovery flash, redownload unrevoked and start over again.
(were you able to access recovery before?)
btw it would help if you opened a new thread instead of hijacking this one
regarding to OP
* you must not forget to install all neccessary drivers
i. download & install htc sync
ii. download android phone driver
* I'm using win7 x64 and rooted my phone with no problems (pretty fresh install though...)
* you wouldn't need a goldcard if your phone is not branded by your carrier.
hope this helps

[Q] Bricked. Why did this happen?

Ok so I bricked my Evo yesterday. The goal of this thread is to find out possible reasons why it bricked so I can avoid any future incidents. What I was doing was simply flashing a new rom. I had reflashed my clockwork from version 3.0 to version 2.5 which worked fine. I was able to flash between a couple of roms using it. I did this because of the issue with not being able to flash certain zip files with the new recovery. So I downloaded Warm Z RLS 1; the 2-23-11 version. So I flashed the zip the process went as normal. The installation completed normally. Then, I flashed the radio file. That also installed successfully as expected. Then, I backed out and went to "reboot system now." When I clicked that It went to a black screen showing a picture of an open box with an arrow coming out of it pointing to the little android guy outside the box. So, after trying to hit the power button to turn it off and return to the bootloader, it remained at that screen. Next, I removed the battery to restart it that way. Where it finally rested in peace. The phone would not even attempt to boot up nor attempt to enter the bootloader. The charger light wouldn't even turn on when plugged in. It was as bricked as can be.
Now here is my question. Does anybody have any theories as to why this happened? I want to remain a "rooter" when I get my next Evo. I want to know what went wrong so I can avoid bricking another phone.
Thank you in advance to those who can offer any advice or help. Also, sorry in advance if I'm posting a repetitive topic.
P.S. Sprint is replacing my phone for FREE. I didn't mention anything about rooting. Without asking questions, the sprint rep simply said that they would order a replacement, which will arrive in a couple of days.

errie806 said:
Ok so I bricked my Evo yesterday. The goal of this thread is to find out possible reasons why it bricked so I can avoid any future incidents. What I was doing was simply flashing a new rom. I had reflashed my clockwork from version 3.0 to version 2.5 which worked fine. I was able to flash between a couple of roms using it. I did this because of the issue with not being able to flash certain zip files with the new recovery. So I downloaded Warm Z RLS 1; the 2-23-11 version. So I flashed the zip the process went as normal. The installation completed normally. Then, I flashed the radio file. That also installed successfully as expected. Then, I backed out and went to "reboot system now." When I clicked that It went to a black screen showing a picture of an open box with an arrow coming out of it pointing to the little android guy outside the box. So, after trying to hit the power button to turn it off and return to the bootloader, it remained at that screen. Next, I removed the battery to restart it that way. Where it finally rested in peace. The phone would not even attempt to boot up nor attempt to enter the bootloader. The charger light wouldn't even turn on when plugged in. It was as bricked as can be.
Now here is my question. Does anybody have any theories as to why this happened? I want to remain a "rooter" when I get my next Evo. I want to know what went wrong so I can avoid bricking another phone.
Thank you in advance to those who can offer any advice or help. Also, sorry in advance if I'm posting a repetitive topic.
P.S. Sprint is replacing my phone for FREE. I didn't mention anything about rooting. Without asking questions, the sprint rep simply said that they would order a replacement, which will arrive in a couple of days.
Click to expand...
Click to collapse
Yes, I can tell you why that happened. It's because you pulled the battery during the Radio Flash!!! (almost a guaranteed brick by doing that...) After you flash the radio update in recovery, it brings you back to the recovery screen, and you have to hit reboot. Upon rebooting, the radio flash completes (that is the black screen with the box and the arrow....) That part can take from 20 seconds to 10 minutes, and you have to be patient. If you disturb the phone (battery pull) during that process, you'll brick it. That is one of the only ways to surefire brick an Evo. So, to prevent it from happening again, all you need to do is be sure that if/when you ever flash a radio update, that you follow all of the instructions, and never, ever pull the battery during a radio flash. You need to remember that when you flash a different radio, it reboots and then does the important stuff, while showing you that screen with an arrow and a box, or an arrow and a phone. Once that part completes, it takes you back to the recovery screen, and then at that point you select reboot, and it'll boot normally into the OS.

Oh, I see. Thanks a lot. I had never seen that screen before. I had flashed radio update before but I didn't see that screen. I thought it froze. I feel like an idiot. But, I learned a lesson. Thanks again! Can't wait to get my replacement evo to start rooting/flashing again.

errie806 said:
Oh, I see. Thanks a lot. I had never seen that screen before. I had flashed radio update before but I didn't see that screen. I thought it froze. I feel like an idiot. But, I learned a lesson. Thanks again! Can't wait to get my replacement evo to start rooting/flashing again.
Click to expand...
Click to collapse
Yea, we all make mistakes. That is definitely one that you'll learn from though! And sometime's that screen, when the radio is flashing, varies a bit. I know when I flash a radio, it's a screen with a picture of an Evo that has a circle around it with an arrow facing down. I believe it is the hboot version or the recovery (amon ra or clockwork) that determines what that screen will be. Either way, that is what to expect during a radio flash. It has happened to many people, where they flash a radio, and get to that screen that they've never seen before, and then think that something's wrong so pull the battery. You're not the first, for sure. Anyways, good luck on getting your new Evo. Take it easy.

Patience is the key with all things root. Not every dev reminds you that you have to wait a while for things so it's easy to forget it. On the Samsung Fascinate, development can be a fragmented mess so most devs explain everything l.e.t.t.e.r.b.y.l.e.t.t.e.r. I rooted my girlfriend's phone and they always remind you that reboot/reflashes can take up to 20 minutes so when my Evo did that on a recent flash I knew I just had to leave it alone.

Great to know info. Thanks for bringing this out for us newbs to know.

Yeah as said above those radio flashes can be a learning process. Seemed like a few people did exactly as you when flashing radio's on Myn's RLS 5. Even after people were warned in the thread it still happened. I put my phone down and sat on the throne a while. Felt better to drop bricks, than turn my phone into one. patience is a virtue.

Yep, whenever I do any flashing I just set it down next to me and try to keep myself busy with other stuff so I don't get impatient.
BTW, what did you tell then Sprint store had happened to your phone, just that it wouldn't turn on?

[Q] OMG! Accidentally Formatted system data!

Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.

I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot

I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...

Does your phone still go to clockwork when you go to recovery?

Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!

Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.

SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.

Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.

shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...

So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?

COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!

[Q] [HELP] Desire messed up after alpharev

Hi there,
I had a very nice trip with my rooted desire with a miui rom on it for now maybe, 1 year smthg.
Recently, i bought a new µSD and wanted to prepare it for my phone ; i downloaded rom manager, and tried the "partition SD" functionality, which told me that i would have to update my clockworkmod, which i tried with the "update recovery" in it, which failed.
After a while, i found that i forgot to S-OFF my phone, and that was the reason why i couldn't update the recovery. So i decided to S-OFF. Unfortunately, my phone didn't went to the last step, and stayed stuck at the boot screen until its battery died, maybe an hour after.
I began a long journey trying to figure out if my phone was bricked or not, since i wasn't able to boot it up ; only the hboot was responding. I tried MANY ways, MANY posts, i tried to flash with a nand backup without success ('access denied'), i tried to flash just the recovery (same or 'signature failed'). I tried to put a PB99IMG.zip file from alpharev into my phone without any success...
BUT. I succeed in recovering my phone with putting a stock PB99IMG.zip from shipped-roms and it boots up very well on a crappy sense rom.
From that, i tried hard to root it again since i want to try again to S-OFF it, and after that, return back to my beloved miui rom. I'm stuck because of a mysterious problem into my phone. It looks like it doesn't like the third step which (i guess) requires a boot script. So nothing happens to it, it freezes to the bootscreen, while unrevoked says "waiting for reboot..." endlessly.
I succeeded once (only) in passing this step, but then unrevoked said to me something like : "Internal error: failed to unlock NAND flash?" which seems crazy since i'm in a 0.93 HBOOT (since the RUU reset). I hadn't any Superuser app nor signs of rooting ("su" command failed in terminal).
For now, i'm trying to root it via the Visionary app, but i don't think it will work.
If anyone has any suggestion in making things better, i'll be pleased to hear !
PS : I'm writing this post because i feel it could be full of useful infos for anyone else stuck with a "bricked" phone.

use this guide to S-OFF, install custom recovery and root.
read all the instructions, several times.
oh and rom manager is often not recommended for this phone as it can often cause usb bricks. once s-off you can flash different recoveries via fastboot or android flasher.
use gparted or 4EXT recovery to partition your sd card.

Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !

ynk said:
Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !
Click to expand...
Click to collapse
don't just go flashing RUU's randomly, you may get amoled/slcd incompatibility for instance, which is what this might be.
try reading the troubleshooting guide, you can probably save your phone.
read carefully before you do anything in future...this situation could probably have been avoided

Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.

ynk said:
Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.
Click to expand...
Click to collapse
that problem sounds different as that was posted ages ago, and they weren't messing around with rooting and RUUs...
i don't think you should 'wait and pray, try another battery, or let it dead'
can you get to recovery/bootloader/fastboot at all? please post more details. if you can then it's probably not bricked.
i'm unsure of whether you've actually tried anything in the troubleshooting guide. try [2] advanced boot problems, S-ON. create a goldcard and try the WWE RUU
if none of it makes sense ask directly in that thread
and if you get the RUU to boot, don't use unrevoked...follow my 1st reply...

I stopped all the things i was doing when i had your reply, trust me !
As i said, i can't get the device to be powered on ; since, i'm not able to have any access to hboot, fastboot, nor adb. The phone does not charge when plugged to a charger neither to a computer. The led stays black, and the battery doesn't get warm (which normally does when charging).
Since the phone doesn't turn on, the guide you gave me is useless (but i learnt a lot from it, so thanks for that). The only section which *could* have been useful was the one talking about wrong RUU flashing with SLCD off ; but since my screen was working, and the symptoms are different (my phone is not recognized by the computer), this is not describing my problem definitly.
Be sure that if i can boot that phone once again, i'll follow your 1st reply and won't use unrevoked on it ever...
I'm trying now to find an other battery, to know which from the battery xor the mobo of the phone is dead. If battery, i'll just buy a new one ; if mobo, i'll buy a Desire S, since my phone reached the warranty limit, and i would have to pay to repair it...

HOX won't boot

Hello, i'm sorry that my first post on this forum is an question about my no longer working htc one x. I have been gathering information of this forum for a long time, and allways helped me, but this time i am really stuck. So in advance i thank you for all the help you already have given me
This is what happened
my first HOX had a defect sim reader, was declared DOA so i got a new one, so far so good
but after using the phone for about 2 weeks,
all apps started closing one at a time, untill the phone went black (it was still on, but nothing was working)
at first i tought i installed a bad app, so reset the phone to factory settings.
after i did that it worked for a few days untill the same phenomenon happened again.
this time i reset the settings via the power+volume button boot menu, and in android wiped the SD card.
again it worked for a few days,
untill it all started going haywire.
all the apps i installed the last time where whatssap and dropbox (no games and such)
now i rarely can get my phone to boot, or go into recovery.
when i connect it to my charger it has no red light.
if i get it to boot, i usually cant get past the sim unlock screen.
i have been thinking about returning it, or installing another rom (wich i have done before on my htc desire wich worked great)
problem is, i cant go into android to tick on the usb debug.
sorry for the long post, i'd be really happy if you could help me out in this one.
my htc is from the dutch vodafone provider.
cheers,
Schella

schella said:
Hello, i'm sorry that my first post on this forum is an question about my no longer working htc one x. I have been gathering information of this forum for a long time, and allways helped me, but this time i am really stuck. So in advance i thank you for all the help you already have given me
This is what happened
my first HOX had a defect sim reader, was declared DOA so i got a new one, so far so good
but after using the phone for about 2 weeks,
all apps started closing one at a time, untill the phone went black (it was still on, but nothing was working)
at first i tought i installed a bad app, so reset the phone to factory settings.
after i did that it worked for a few days untill the same phenomenon happened again.
this time i reset the settings via the power+volume button boot menu, and in android wiped the SD card.
again it worked for a few days,
untill it all started going haywire.
all the apps i installed the last time where whatssap and dropbox (no games and such)
now i rarely can get my phone to boot, or go into recovery.
when i connect it to my charger it has no red light.
if i get it to boot, i usually cant get past the sim unlock screen.
i have been thinking about returning it, or installing another rom (wich i have done before on my htc desire wich worked great)
problem is, i cant go into android to tick on the usb debug.
sorry for the long post, i'd be really happy if you could help me out in this one.
my htc is from the dutch vodafone provider.
cheers,
Schella
Click to expand...
Click to collapse
mmh i read about same problem with someone, here on xda, are your bootloader unlocked?
it seems to be a firmware problem, so you can try to install a ruu if it's available, and if it's not, you can try to ask for htc or vodafone to change it with another hox, or you can unlock bootloader and install a custom firmware, hoping that it will not give you the same problem! (unlocking bootloader MAY void all or part of your warranty)>>it depends only from htc... in some country they don't care, in some other, they will not repair it.

aha
glukosio said:
mmh i read about same problem with someone, here on xda, are your bootloader unlocked?
it seems to be a firmware problem, so you can try to install a ruu if it's available, and if it's not, you can try to ask for htc or vodafone to change it with another hox, or you can unlock bootloader and install a custom firmware, hoping that it will not give you the same problem! (unlocking bootloader MAY void all or part of your warranty)>>it depends only from htc... in some country they don't care, in some other, they will not repair it.
Click to expand...
Click to collapse
i believe it is alowed here, but this was exactly my dilemma.. i think i'm going to return it for it is the safest option i guess. Maybe it is an hardware failure. thanks for the reply! my bootloader is locked btw