Database Info

Bricked phone or is there a fix?

Hello, the past couple of days my phone suddenly shut off by itself at random times of the day. I didn't think much of it because I figured it was just acting up like it sometimes does..Anyways my real problem is ever since last night(when it shut off by itself) it wont load HTC Sense when the OS loads. I'm currently running the Energy Raphael ROM 21905 with Sense 2.5. I have tried almost everything..The easiest way out I thought was to just update to the latest Energy ROM, however I can't because without Sense loaded my computer is unable to make a connection with the phone, leaving me screwed. Unless there is another way?

Nevermind. I didnt know you could load into the SPL and update it that way. So all should be good now

Well,well.
If the OS isn't running for any reason,just enter the bootloader(tri-color screen) and connect the phone afterwards. If one is able to enter bootloader,it is not bricked and it is alive,so one can do at the time something with that.
Just for noobs.

TomasNM said:
Well,well.
If the OS isn't running for any reason,just enter the bootloader(tri-color screen) and connect the phone afterwards. If one is able to enter bootloader,it is not bricked and it is alive,so one can do at the time something with that.
Just for noobs.
Click to expand...
Click to collapse
my telephone is also willing to go into bootloader, but i keep getting the 262 error while updating my rom. So that means my telephone isn't bricked yet? what are the possibilities to fix my telephone?

Well,don't know actually,what happens with wrong version flashed.
However let's talk in your thread about it...

Phone keeps rebooting

Just installed new rom on phone.
Keeps rebooting every couple of minutes. Now I am not sure if it happened before I installed rom or not as I just went straight ahead and installed it as I have just received a replacement handset from a broken screen.
Any help?

Sense rom? Aosp rom? Rom name? Root? No root? More info man...
*Swaypovano sa Desire S BRE*

Saga3D v3.0 (Desire S official Sense 3.0) - [2.3.5] OTA 2.10.401.5
That rom. Installed the new hboot and orig stock kernal

Assume you have rebooted into recovery and wiped data, cache and dalvik cache, then tried to reboot?

Yes, I have done that a couple of times. I left it on connected with cable overnight and it doesnt seem to have rebooted. Seems to point to a battery problem??
It does boot properly. But after a minute it just restarts.
Edit. A bit more testing and it doesnt reboot when using a game or app. As soon as it closes to main screen it seems to just reboot as the screen goes into standby.
Edit 2. I have changed setting to stop screen turning off and its not done a reboot for the whole 10 minutes.
Does anyone think its a warranty claim? Or any more things to try?

Warranty claim seems a bit drastic, I'd try installing the rom again, or try a different rom, Endymion is sense 3.5 and stable... I was toying with it today, or pre rooted stock or even cm7 which at least you know is also rock solid
Sent from my HTC Desire S using xda premium

Just tried cm7 and it does the exact same.
Edit.... tried 4 different roms now. Going to go to stock with s-on and test. Then back to the shop again
Edit 2. Just use RUU on it and it is the same. Looks like I need to return it yet again.

Any more tips before I take it back in?

I had the same problem after 2.3.5 update. Went back to old version and it's fine now.

Assuming that you are not OC or UV then continue, else adjust to stock settings and re-try.
I recall a couple of others having a similar problem that was caused by either
a) loose battery connection, resolved by placing a piece of folded paper on top of battery to ensure it sat solidly in the slot.
b) dodgy battery, suggest that you contact HTC support, explain that phone keeps rebooting you suspect battery and request that they post you a new battery - don't post old battery back until you are sure its the battery at fault.

Interesting Evo Design 4G dilemna created by my noobness

First off, I know I just signed up. I've been creeping for the past month or so.
So here is the situation:
Summary: I have a hardware problem on a rooted/unlocked htc evo design and have to return it to stock settings to return but have lost usb connection and cannot re-establish.
Hboot:
Unlocked
S-On
1.26.0000
Software Info:
version: 2.3.4
htc sense: 3.0
software number: DesignerEvo-0.5
Longer Version:
I bump into a tech-head tweak everything buddy of mine and he says i just have to "flash the new ics" to my phone.
15 hours of banging the head against the wall later i realize im trying to unlock/root/su/flash as though i have the evo 4g not the evo DESIGN 4g which i actually have. (and which i shortly discovered has nothing customized for it) After that I was off and away-ish...
so here is what i have done (don't mock me for saying it wrong):
- Unlocked the phone via htc dev site (it won't let me post links yet)
- Flashed/Installed Custom Recovery Clockwork mod 5.0.2.7
- Flashed su-2.3.6.3
- Flashed Designer Evo 0.5 found at sdx-developers (wont let me link)
- then for kicks flashed a a vaelek rom that said it was compatible-ish for the evo design from http://forum.xda-developers.com/showthread.php?t=1399351 it didnt see usb and other issues, so...
- then came back to Designer Evo
- installed setcpu to try to improve battery life...
Everything was fine for a couple of weeks (other than no ics and crappy battery life!)...
All of a sudden at random the phone powers off with battery reading charged. It will reboot, and within minutes power off again.
It does this in stock rom and custom.
If i keep it on charge it stays on.
If i remove it after charging, it holds power for a little while, but still powers off.
I thought conflict may have been between setcpu and a power savings app i had running and had forgotten to remove. removed, seemed to be okay then same.
I decided to come back on here figure out how to flash back to factory and unroot, and plugged it into computer (windows 7) via usb. "unknown device". reinstalled drivers. same problem. opened as ubuntu 11.x, still nothing. installed drivers nothing.
I dloaded a stock PH44img.zip w/ phone and put it on root and it would load at hboot, but do nothing after. may require s-off?
This is weird, I did a factory reset from recovery and on reboot it defaulted to the vaelek custom rom, so i went back to my oldest backup.
so... as i said, I think I have a hardware problem on a rooted/unlocked htc evo design and have to return it to stock settings to return but have lost usb connection and cannot re-establish.

Hang in there Vince...somebody is bound to point you in the right direction

I guessing people were off partying this weekend and have yet to respond?

ok this is crazy.... My design 4g is nowing doing the same thing.... Google brought me to this thread... anyone know anything?

Have you tried ruu'ing back to stock or flashing a different rom thru recovery
Sent from my PG06100 using xda app-developers app

shrekdaklown said:
Have you tried ruu'ing back to stock or flashing a different rom thru recovery
Sent from my PG06100 using xda app-developers app
Click to expand...
Click to collapse
Tried several roms . No luck..
tried to ruu via boot loader... It won't take. I may need to relock the boot loader.

[Q] Radio problem with custom ROM

I'm hoping for some friendly advice - I have a Desire S which was rooted last year and I installed CM10 to try out JB. All has been working well )part from the occasional reboot) however couple of days ago the battery started draining quickly, the phone became very hot and the wifi stopped working. After various wiping of caches and rebooting I decided to try some other ROMs (Fallout Evolution V5, Miui, IceDS) and although they all installed OK I still have no wifi and now the mobile network won't work.
It worked on Fallout at first but when the wifi wasn't working I wiped and re-installed and it hasn't worked since. It does see the O2 network although the phone hd previously been unlocked to work with Vodafone, so I think I may have rolled back the radio somehow.
At this stage I'm not entirely sure if it is a software or hardware problem, and I din't know how to test the hardware.
The phone is currently as follows:
UNLOCKED
Saga PVT ship s-on RL
HBOOT -2.02.0002
Radio -3831.19.00.110
eMMC -BOOT
July 31 2012>15.41.32​
Do I need to update the radio? If so, which version should I use? And do I need to s-off the phone first?
Any other help would be appreciated.

lesmorton said:
I'm hoping for some friendly advice - I have a Desire S which was rooted last year and I installed CM10 to try out JB. All has been working well )part from the occasional reboot) however couple of days ago the battery started draining quickly, the phone became very hot and the wifi stopped working. After various wiping of caches and rebooting I decided to try some other ROMs (Fallout Evolution V5, Miui, IceDS) and although they all installed OK I still have no wifi and now the mobile network won't work.
It worked on Fallout at first but when the wifi wasn't working I wiped and re-installed and it hasn't worked since. It does see the O2 network although the phone hd previously been unlocked to work with Vodafone, so I think I may have rolled back the radio somehow.
At this stage I'm not entirely sure if it is a software or hardware problem, and I din't know how to test the hardware.
The phone is currently as follows:
UNLOCKED
Saga PVT ship s-on RL
HBOOT -2.02.0002
Radio -3831.19.00.110
eMMC -BOOT
July 31 2012>15.41.32​
Do I need to update the radio? If so, which version should I use? And do I need to s-off the phone first?
Any other help would be appreciated.
Click to expand...
Click to collapse
Did You tried installing stock rom again in your mobile

No I haven't. I assume this would re-install the correct radio?
Not sure where to get the stock ROM, or which one was shipped with the phone.
If I did get it can I flash it through recovery - I'm using 4EXT?

lesmorton said:
No I haven't. I assume this would re-install the correct radio?
Not sure where to get the stock ROM, or which one was shipped with the phone.
If I did get it can I flash it through recovery - I'm using 4EXT?
Click to expand...
Click to collapse
Boot into bootloader and run following command
fastboot get cid
Than you can know which ruu to flash. But don't forget to downgrade your misc version before fishing ruu
No ruu are flashed from PC
Sent from my HTC Desire S using xda app-developers app

OK, I have managed to get the phone back to it's stock ROM which is O2 in the UK.
I had previously unlocked the phone but it now won't accept anything other than an O2 SIM. When I scan for networks only O2 is seen. I still have the unlock code but when I put a Vodafone SIM in it doesn't prompt me for the unlock code. I'm just getting a Limited Service display.
Is there any way of forcing the unlock code prompt screen - say with keyboard numbers or via Fastboot?

lesmorton said:
OK, I have managed to get the phone back to it's stock ROM which is O2 in the UK.
I had previously unlocked the phone but it now won't accept anything other than an O2 SIM. When I scan for networks only O2 is seen. I still have the unlock code but when I put a Vodafone SIM in it doesn't prompt me for the unlock code. I'm just getting a Limited Service display.
Is there any way of forcing the unlock code prompt screen - say with keyboard numbers or via Fastboot?
Click to expand...
Click to collapse
do i understand things as they are?
do you intend to use simcards of another operator?,
well... that`s what branding stands for,
to make sure
you`ll not use any sim from different carrier...
is your phone simlocked as well,
or is it only a branded rom ?
..but why bothering to flash the phone with branded RUU,
(when there are quite a few generic ones, still floating around,..)
except, when one wants to claim a warranty..may be...

I flashed the O2 ROM as it was what was on the phone when I bought it and I was trying to get back to a radio that would work.
I have since managed to get the phone working OK with the Asda/Vodafone SIM but I am still having problems with the wifi (this is where it all started!). whenever I switch the wifi on it scans and then reports that it is unable to scan for networks, after 2-3 attempts the wifi switches itself off.
I'm still trying to find out if it is a software or hardware problem. Other than that all is working well on the Fallout v5 ROm I have flashed - although it does make the phone run hot.

lesmorton said:
I flashed the O2 ROM as it was what was on the phone when I bought it and I was trying to get back to a radio that would work.
I have since managed to get the phone working OK with the Asda/Vodafone SIM but I am still having problems with the wifi (this is where it all started!). whenever I switch the wifi on it scans and then reports that it is unable to scan for networks, after 2-3 attempts the wifi switches itself off.
I'm still trying to find out if it is a software or hardware problem. Other than that all is working well on the Fallout v5 ROm I have flashed - although it does make the phone run hot.
Click to expand...
Click to collapse
make backup (CWM)
try to find, and flash another kernel- custom,
..that may be a possible fix, for wifi issues,
as that is very often caused by,
not efficient, or completely missing drivers (0kb file size)....
...depending on the RUU version- flashed,
you might be interested in:
http://forum.xda-developers.com/showthread.php?t=1845039
otherwise, try to look for < unity > or < endymion > kernel.....
..Heat might be caused either
by battery,
or CPU - struggling with heavy flaw of graphics, (like < Google Earth >+< Browser >+<anything one prefers > )
or a nasty app ( or several ), constantly trying to consume, most of its resources...
..both quite simple to eliminate...
..and...undervolting, it helps to reduce heat - too...

asgardr said:
make backup (CWM)
try to find, and flash another kernel- custom,
..that may be a possible fix, for wifi issues,
as that is very often caused by,
not efficient, or completely missing drivers (0kb file size)....
...depending on the RUU version- flashed,
you might be interested in:
http://forum.xda-developers.com/showthread.php?t=1845039
otherwise, try to look for < unity > or < endymion > kernel.....
..Heat might be caused either
by battery,
or CPU - struggling with heavy flaw of graphics, (like < Google Earth >+< Browser >+<anything one prefers > )
or a nasty app ( or several ), constantly trying to consume, most of its resources...
..both quite simple to eliminate...
..and...undervolting, it helps to reduce heat - too...
Click to expand...
Click to collapse
I changed the ROM to IceDS v8 which seems to run cooler. I think part of the problem was with Titanium Backup running and the wifi kept searching for a network.
I am still having the wifi problem as it displays 'unable to scan for networks'. Having searched the internet extensively and tried a few different so called fixes I have come to the conclusion it is a hardware problem. When I get time I'll see if I can strip the phone and see if I can find the cause.

lesmorton said:
I changed the ROM to IceDS v8 which seems to run cooler. I think part of the problem was with Titanium Backup running and the wifi kept searching for a network.
I am still having the wifi problem as it displays 'unable to scan for networks'. Having searched the internet extensively and tried a few different so called fixes I have come to the conclusion it is a hardware problem. When I get time I'll see if I can strip the phone and see if I can find the cause.
Click to expand...
Click to collapse
Well I stripped the phone and checked what connections I could but still no wifi.
I have used the RUU to get back to stock ROM and everything is fine except the wifi not working. Does anyone know if the wifi hardware is on the PCB, and if so where it would be in the phone. As the phone is in excellent condition I am thinking of getting a cheap phone with broken screen and just cannibalising it with my phone and building one good phone. It's just knowing what part of the phone contains the wifi hardware.
Any help would be appreciated.

[Q] Reboots 30 into loading ROM

From the beginning.
Unlocked
EVITA PVT SHIP S-ON RL
HBoot 1.14.002
Radio 0.19as.32.09.11_2
OpenDSP v29.1.0.45.0622
eMMC-boot
June 11 2012, 14:36:28
Click to expand...
Click to collapse
I was running a ViperRom my camera light was staying on, I tried everything to get it to turn off. I decided it been a few month it was time to get a new ROM anyways. I tried installing Gummy Nightly's was having problem with the install read about getting a different version of TWRP so I updated to 2.6.3.0 I believe I had 2.1.0.0. Gummy still won't work, so I changed plans and want for the Viper XL Rom 4.2.0 this led to a bootloop not getting past the Viper splash screen. I thought I might as well just with one of my backup. So, i wiped and loaded a backup. This is the problem, it will load up the ROM for about 30 seconds before the icon all appear it will reboot. I've now been working on this for 2 days. I've went through each post and tried the advice each person was given, I've tried to Flash a different Rom, the Viper Rom I had when I had the Camera Light Issue, each time I get about 30 second into the Rom Load and reboot. (One of the ROMs would let me access the SDCARD0 but found a work around that.) I've let the phone sit charged for 2 hours looping. I've turn it off and let it sit charging. The next thing I'm going to try to to downgrade the TWRP. If anyone can give me some advice, something new and different to try that would be great. Thanks!
Cheers
xDrFirefly

talked to one of my buddy and said the downgrade would be pointless so, i'm trying to flash a stock rom at the moment.

When you changed to TWRP 2.6.3.0 was it the official version or the unofficial modified version?
Sent from my Evita

Recovery: Custom TWRP 2.6.3.0 w/selinux support

And what errors did it give you when trying to install Gummy?
Sent from my Evita

The install failed. I tried it multi times, and even d/l it again to see if that would make a difference. Nope.
Here is what i've done so far. I factory reset everything. Found a stock rom flashed it on. For the two hours I used it seemed to work fine. I then flashed CleanRom everytime I would open Ti Backup the phone would reboot. I flashed another ROM, was getting the signal drop snagged the Beastmode Kernel it keep failing everytime I tried to flash it. Factory Wiped EVERYTHING again. Flashed the Stock, then Flashed ViperXL (then went to bed) in the morning still had signal bars, so far had two reboots, one when I was uninstalling apps using Manage apps feature, and another time when I was in the Venom HUB app. But at the moment the phone seems to be working. The battery life is ****. In the 30 mins I've had the phone unplug i've down to 89% and all I did was delete a few apps, and move some stuff to the home screens. Hopefully it will get better with time.
Side Note: To anyone reading this. I got the AT&T HTC XL preorder. I doubt I will ever do that again. In all the years I've been flashing and messing with phone. ( My first phone I messed with was a Sidekick ) I've never had so much trouble as I had with this phone. ( HTC Tilt, Fuze and Tilt 2 never had this kinda problem ) a friend of mine whom waited a year to get the XL has never had any of the problem I've had. Just my thoughts. Thanks and I hope I won't have to be asking anymore question.
When, I have more time and such I'm going to try to flash Gummy. If I get the same error message for it or anything else I will post it here.
Cheers
-Dr FF

I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita

You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.

jacobas92 said:
You might also want to try setting a fresh install up without restoring any apps or installing any social networking apps. Those are possibly the worst for fc's, random reboots, and bad battery life. At least for me that's how it is.
Click to expand...
Click to collapse
I will try this. Sounds like a very logical plan.

timmaaa said:
I get that it failed, I asked what error you got. Your battery life on Viper will improve, just let the ROM settle in for a few days. I've had this phone since just after release and I've never had a single problem with it, not one. There are quirks that come with any device but if you do the proper research and know what you're doing you shouldn't have issues.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".

xdrfirefly said:
Timmaaa I just get annoyed how easy this phone get caught in bootloops. That is really my main complaint. I know it's trivial. -- I really don't know what caused the fail when I tried to install Gummy. I wiped and tried it a few time and I keep getting failed. I normally try twice then find something else. To quote Little Britain "Computer says no".
Click to expand...
Click to collapse
Computer always says no for a reason. You need the right recovery installed to flash KitKat ROMs, you also need to check the md5 of every ROM you download before you flash it. What I'm saying is there's no reason Gummy wouldn't install if you have done everything correctly.