Database Info

Continuous soft resets...

Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!

boot command from mtty reads:
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0xAB80, total sector=0x10740
Storage start block=707, total block=1053
Total Bad Block in CE: 0
Erase physical block from 995 to 2032
formatstorage Bad block found: 1045
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++

Try this
Try flashing this ROM and see what happens.
http://www.4shared.com/file/3857459...ULAR_WWE_157_-_Originaly_Shipped_ATT_ROM.html
What does your bootloader screen show?

Please Help!
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!

Threads merged.

Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Some people go to far ahead before figuring out the real issue. Don't **** yourself.
Hold down your power, camera, and insert your stylus then tell us what your bootloader screen displays.

Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
ok post was moved from another thread. sorry. It appears that you do have hardspl installed.

Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
and your bootloader screen will not change because it does not display the rom version. You have hardspl installed what more do you want?
Did you believe your bootloader screen would change after you flashed a rom?
Damn!!!

Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Dude it has been five months since you flashed a rom why bother getting all neurotic and worried For a common situation? I complained to mods because they closed your thread now I look like a douche bag. Thanks.

I had the same problem (continuous reboot) as before, see this thread:
http://forum.xda-developers.com/showthread.php?t=383678
but the problem that I had is because of bad blocks, post your info 8 and maybe I can help

ok, I got the phone to startup, eventually it stopped trying to soft reset. I hit the power button and it turned on. Now, I run jumpspl and it doesn't ever bring up the USB connection, so I can't change the bootloader back to oem. any suggestions?

I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.

Metzex08 said:
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
Click to expand...
Click to collapse
If your sending it for warranty replacement via AT&T just put it in the microwave for 2 seconds....problem solved.

Cannot flash rom! Weird 'loading ...' screen

Hi,
I bought a HTC Touch Pro today from ebay, all working fine and everything. So I go to flash to the latest energyrom, using this guide:
http://lievenvw.wordpress.com/2008/...c-diamond-or-htc-touch-pro-with-a-custom-rom/
It starts, then has an error saying it was unable to flash and i should check my devidce etc. I look at my phone and it has a whit background and it just says 'Loading ...'. I had to take out the battery to get it back on again.
Everything is fine, my phone works, but I don't think I can flash anymore.
I then read this guide:
http://lievenvw.wordpress.com/2008/...c-diamond-or-htc-touch-pro-with-a-custom-rom/
When i got to this step:
Enter bootloader mode on your phone:
While the device is booting up or with the device turned on, press and hold the volume down button along with the power button, then press the reset button with the stylus tip, then release the volume down and power buttons when bootloader tricolour screen appears.
Everything was fine the tricolour appeared and the text, then suddenly it went back to 'Loading ...'
I really want to flash my phone, and i'm worried I won't be able to know. Ive tried hard reset, but it didn't do anything. Is there anything else I can do?
I've left the loading screen for 20 minutes, i don't think it's doing anything...
If anyone could help me that would be amazing.
Cheers
EDIT:
I just tried flashing with the default firmware, as guided here:
http://forum.xda-developers.com/showthread.php?t=410150
The phone fades to black, and doesn't show anything at all, and then i get ERROR [260] CONNECTION, and tells me to check if it's plugged in etc.
Very strange, i'm really worried I won't be able to fix this..

I had this issue
I had this issue with a Fuze that I had about a week ago.
It comes with a newer version of bootloader.
All you have to do is remove the Sim card and SD Card before you flash. That made the black fading go away and flashing succeeded.
Start by installing Hard SPL first. Once that is in they you can start flashing the rom.

How about reading and posting in the noob flashing thread? Do you know what hard spl, gsm, and cdma are? If not, you're either wasting your time and/or your phone.

Well I am clearly an idiot, thankyou both for you posts, phone is now successfully flashed!

Htc Touch Pro -RAPH100 serious problem

Hi there,
I need help to know whats going on with my HTC Touch Pro.
After more than 1 year of use, the phone started yesterday giving this message:
RAPH100
SPL-5.05-0000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
PCBID 0x80
RID 0x0
This happens with the screen splitted in 4 colours.
Before giving this message I can read very quickly a system message saying "No image file!"
The phone JUST shows this message, I can't do ANYTHING on it. I have tried to make an hard reset, but nothing - only shows this message.
What can I do to fix this?
thanks,
Alex

soo it doesnt boot up all the way to Windows Mobile screen? if so, then flash a ROM a STOCK Rom from the HTC Site, all though idk how to do that since i havent been in that situation before, but just connect ur device to the computer

XERO_Racer said:
soo it doesnt boot up all the way to Windows Mobile screen? if so, then flash a ROM a STOCK Rom from the HTC Site, all though idk how to do that since i havent been in that situation before, but just connect ur device to the computer
Click to expand...
Click to collapse
I there,
I have downloaded this file from htc.com site:
_HTC Touch Pro_RUU_Raphael_HTC_PTG_5.05.410.1_Radio_Signed_Raphael_52.58.25.30_1.11.25.01_Ship
Somehow the laptop was able to recognize usb connection to HTC and it seems it was installed. BUT in practice, everything stayed the same - only that screen appear, and nothing else.
Any other suggestions?
thanks

Try flashing from MicroSD. I think there's a summary of how to do this in one of the stickies in the Rom Development subforum. Sounds like your rom got corrupted or something is trigger that screen.. That screen you mention is the bootloader screen. It's access by holding down the Volume Down rocker as you power on the device.

SDreamer said:
Try flashing from MicroSD. I think there's a summary of how to do this in one of the stickies in the Rom Development subforum. Sounds like your rom got corrupted or something is trigger that screen.. That screen you mention is the bootloader screen. It's access by holding down the Volume Down rocker as you power on the device.
Click to expand...
Click to collapse
tried to FLASH HARDSPL but was not successful.
Can this be a hardware problem?
is there a way of reinstall the windows mobile, besides doing an hard reset?
Even i can flash the ROM , but the screen is always the same with the 4 colours.
more clues?

in your case, doing a hard reset seems to be the least of your worries. you can install the stock roms w/o hardspl so you should give that a shot first. through usb and through sd card if usb doesn't work.
from what you've said, you could flash the stock ROM but when you start up your phone, it brings you back to bootloader?
also, when you attempted to flash hardspl, what error did you get?

fatpandas said:
in your case, doing a hard reset seems to be the least of your worries. you can install the stock roms w/o hardspl so you should give that a shot first. through usb and through sd card if usb doesn't work.
from what you've said, you could flash the stock ROM but when you start up your phone, it brings you back to bootloader?
also, when you attempted to flash hardspl, what error did you get?
Click to expand...
Click to collapse
Hi there,
When I try to install hardspl the progression bar does not goes forward, it stays in the 0% - this by USB - I did not try it in the SDcard, but I think it should be the same...
I can flash the ROM with USB, but after the install is complete it brings me back the same 4 colours screen with that error I have mentioned first.
The funny is the cellphone just started this from day to night. Did not fell on the floor, I didn't installed anything... strange.
Can this be an hardware problem?

It seems like your Volume Down button got stuck - therefore you cannot pass bootloader screen.

pilgrim011 said:
It seems like your Volume Down button got stuck - therefore you cannot pass bootloader screen.
Click to expand...
Click to collapse
How can I fix this?

Even if the Vol Down button was stuck, she wouldn't get the "No Image File" message... it would just go into bootloader mode and say, "Serial".
I had this problem when I first got my Fuze and was playing with new roms. The solution would be to flash a new rom on there and be careful.
Connect the phone through USB and turn on the phone while holding Volume Down
Tri-Color screen should read "USB" at the bottom.
Load up the official firmware upgrader and click through the screens.
Wait for it to fully load.
If you are having problems with the official firmware, perhaps you have a bad download and need to redownload it.

Honestly, I think you should take it in (or send it in) for service. I'd quit screwing with it. You've got the stock rom and spl on there, and it's stuck in bootloader for some mysterious reason. You're ok. But if somehow you flash any non-stock firmware on there, and you end up still stuck in bootloader, you may have passed the point of no return, warranty-wise. Bummer that it happened, and it could well be a stuck volume down button, but I wouldn't try flashing as the solution.

i'd agree. since it seems like you never managed to successfully flash anything, everything should still be stock. and sometimes you get lucky and they don't care about that anyways. just send it in

Farmer Ted said:
Honestly, I think you should take it in (or send it in) for service. I'd quit screwing with it. You've got the stock rom and spl on there, and it's stuck in bootloader for some mysterious reason. You're ok. But if somehow you flash any non-stock firmware on there, and you end up still stuck in bootloader, you may have passed the point of no return, warranty-wise. Bummer that it happened, and it could well be a stuck volume down button, but I wouldn't try flashing as the solution.
Click to expand...
Click to collapse
I was just about to sent the HTC to the service today, but one last try before sending it: tried to turn it ON, and...it worked!! With the new ROM installed.
VERY STRANGE...
Well, as long as it keeps working that's fine...but I will never know what happened with my HTC these last days...
thanks for you guys help!!

player911 said:
even if the vol down button was stuck, she wouldn't get the "no image file" message... It would just go into bootloader mode and say, "serial".
I had this problem when i first got my fuze and was playing with new roms. The solution would be to flash a new rom on there and be careful.
Connect the phone through usb and turn on the phone while holding volume down
tri-color screen should read "usb" at the bottom.
Load up the official firmware upgrader and click through the screens.
Wait for it to fully load.
If you are having problems with the official firmware, perhaps you have a bad download and need to redownload it.
Click to expand...
Click to collapse
u r the best ty veryyy much.....i was having the same problem & solved with ur instruction...ty again

herhh87d7 said:
Hi there,
I need help to know whats going on with my HTC Touch Pro.
After more than 1 year of use, the phone started yesterday giving this message:
RAPH100
SPL-5.05-0000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
PCBID 0x80
RID 0x0
This happens with the screen splitted in 4 colours.
Before giving this message I can read very quickly a system message saying "No image file!"
The phone JUST shows this message, I can't do ANYTHING on it. I have tried to make an hard reset, but nothing - only shows this message.
What can I do to fix this?
thanks,
Alex
Click to expand...
Click to collapse
Make be you should change your ROM at once~

Can you Unbrick a Touch Pro 2?

Hey guys looks like a bricked my 2 week old Sprint Touch Pro 2. I can't get pass the touch pro 2 logo screen now and I'm very upset with myself. Is there a way to possible unbrick the phone. I tried to sync it with my PC no response. Also i did back it up with " Microsoft My Phone " earlier in the day and its backed up on WMDManager too. I will try to take it to sprint for warranty and see what the will do. HAPPY NEW YEAR people!!

clariceave said:
Hey guys looks like a bricked my 2 week old Sprint Touch Pro 2. I can't get pass the touch pro 2 logo screen now and I'm very upset with myself. Is there a way to possible unbrick the phone. I tried to sync it with my PC no response. Also i did back it up with " Microsoft My Phone " earlier in the day and its backed up on WMDManager too. I will try to take it to sprint for warranty and see what the will do. HAPPY NEW YEAR people!!
Click to expand...
Click to collapse
Depending on what happened, it's a yes/no situation. What did you do?
Try this:
get into bootloader mode (tri-color screen): Take out the battery for one minute. Put it back in. Getting into bootloader mode is done by holding the Volume down button while you do a press/release of the Reset button. OR hold the Volume down button while you do a press/release of the Power button.
That should get you to bootloader mode. Now, plug in your USB to the PC. Flash a CDMA ROM from there by running the .exe. If you cannot do that, transfer the .nbh file (rename it to "RHODIMG.nbh" [no quotes]) and follow these instructions.
Good luck, and happy new year!
*The majority of the CDMA ROMs can be found at PPCGeeks*

PLEASE HELP ME UNBRICK MY TOUCH PRO 2 (tmobile)
i was installing a ROM onto my TP2 but i accidentally installed a CDMA ROM instead of a GSM ROM. My phone loads past the TP2 startup screen but then stays white with the rom info on the bottom. I tried to do the bootlegger with the 4 colors on the screen but it doesnt work. Also tried a hard reset. CAN SOMEONE PLS PLS PLS HELP? thanks

foxxyroxy5 said:
i was installing a ROM onto my TP2 but i accidentally installed a CDMA ROM instead of a GSM ROM. My phone loads past the TP2 startup screen but then stays white with the rom info on the bottom. I tried to do the bootlegger with the 4 colors on the screen but it doesnt work. Also tried a hard reset. CAN SOMEONE PLS PLS PLS HELP? thanks
Click to expand...
Click to collapse
Well, this forum is for CDMA TP2s, but I'll help.
So you took out the battery for at least one minute? Then you put it back in. Get into bootloader mode (T-Mobile version: phone is off, hold the Volume Down button while you press/release the Power Button. Keep holding the Volume Down button until the colorful screen shows up).
When you're in bootloader, plug in your TP2 to your PC. Now run the .exe of a GSM ROM and follow the steps, as if your phone is synced to the PC. (aka flash as you would usually do).
To flash via the Storage Card: On your PC, go to Start > My Computer > Removable Disk drive (something like that; make sure this is your phone's Storage Card). Drag the .nbh of a GSM ROM there. Rename the .nbh "RHODIMG.nbh" (no quotes). Unplug your Phone. Take out the battery again for one minute. Now, go back into bootloader (hold Volume Down button and press/release Power button [keep holding the Volume Down button]). Follow the steps to flash the phone.
Good luck.

RE:LEASE HELP ME UNBRICK MY TOUCH PRO 2 (tmobile)
Thank you very much for helping me with my TP2 problem! You were my last resort and i was going to give up. It works perfectly fine! I really really appreciate it! THANK YOU AGAIN

Should work
foxxyroxy5 said:
i was installing a ROM onto my TP2 but i accidentally installed a CDMA ROM instead of a GSM ROM. My phone loads past the TP2 startup screen but then stays white with the rom info on the bottom. I tried to do the bootlegger with the 4 colors on the screen but it doesnt work. Also tried a hard reset. CAN SOMEONE PLS PLS PLS HELP? thanks
Click to expand...
Click to collapse
You did exactly the reverse of what I did, and the instructions already given are how I resolved it: put it in bootloader and flash a compatible ROM. I flashed a stock ROM just to be sure, but that's probably not needed.

foxxyroxy5 said:
Thank you very much for helping me with my TP2 problem! You were my last resort and i was going to give up. It works perfectly fine! I really really appreciate it! THANK YOU AGAIN
Click to expand...
Click to collapse
No problem. Enjoy your unbricked TP2 this new year!

Bricked my Sprint Touch Pro 2
i downloaded a hotfix for internal gps from htc website for Sprint touch pro 2. after i tried to install it the phone went off and now it won't even power on or go to boot loader.. any suggestions on how i can fix this i was using Mighty Rom 6.5 with htc sense 2.1

[email protected] said:
i downloaded a hotfix for internal gps from htc website for Sprint touch pro 2. after i tried to install it the phone went off and now it won't even power on or go to boot loader.. any suggestions on how i can fix this i was using Mighty Rom 6.5 with htc sense 2.1
Click to expand...
Click to collapse
See if you can do a hard-reset right now. While phone is off (which it is), press and hold Talk/Send, End, and Power button at the same time. Wait for a screen to pop-up. Follow steps to hard reset. That will bring it back to factory defaults.
If it doesn't work, maybe you could post your question on PPCGeeks, where a lot of CDMA people go. They might be able to help you.

Can you Unbrick a Touch Pro 2
Hi to all,
I'm a new here and a little desperate . I flashed my rom by using a raphael update instead of Rhodium. My phone got bricked. My phone is a Sprint HTC touch pro 2.
At the moment, it will not boot, when I plug it to my computer and it was looking for qualcomm cdma MSM drivers.
I tried sof and hardware reset including the boot loader. Nothing works. I also tried using different RUUs. Nothing works. I hope somebody can help me.

Fixed the problem...bought an android...ha,ha...

smileyzst said:
The same exact thing happened to my tp2.Accidently flashed touch pro(RAPHEL)rom and now nothing!!It won't power on or anything,can someone help me too...Is my phone bricked???? Help please!!!
Click to expand...
Click to collapse
Well if you can power it on, and go to bootloader, then your phone is just fine. Just flash a Rhodium ROM.
I suggest take battery out, and put it back in after few seconds, to see if it powers on. If not, leave it in the charger, and see if it powers on.

After installing the HardSPL, I decided to flash my US Cellular CDMA phone with a GSM rom and of course it bricked it. The phone would only boot to bootloader, so I was going to have it repaired for $70. But if I was willing to flash my device, then I'm sure as willing to look for a DIY solution somewhere. Goodthing I searched this forum, because the answers where right here!
Just format your microSD to FAT32, install an extracted stock ROM kit to the root of the SD insuring you rename the .nbh to RHODMIG.nbh and place the other extracted files on the SD as well. Place the microSD in your HTC Touch Pro2 and boot to bootloader. You may have to take steps to get to the bootloader, mine booted to bootloader automatically anyway at that point. Follow onscreen instructions, and your Touch will be as good as new!

thanks a million for helping me unbrick my tp2
wow man thanks a million, i followed the instru and it worked but was slow so i did task 29 and flashed the rom i wanted and it works great, i really appreciate your help on this

How did you get to the bootloader menu. I am using CDMA HTC Pro 2 by Sprint. Thanks
goldenu said:
You did exactly the reverse of what I did, and the instructions already given are how I resolved it: put it in bootloader and flash a compatible ROM. I flashed a stock ROM just to be sure, but that's probably not needed.
Click to expand...
Click to collapse

@rocco24
Did everything go alright? If not, just post here or send me a PM.

Hi i have a different issue I accidentally flashed the wrong nv items 01192 and now its rebooting. if someone can dump their tp2 sprint 6.5 nv items please help. I am cut off from the world of cell phones at the time. I read that i also would need the radio dump which in my case is the same one on the 6.5 ruu windows version. any feed back or advice is welcome. please help guys.
Oscar

sumflipnol said:
Well, this forum is for CDMA TP2s, but I'll help.
So you took out the battery for at least one minute? Then you put it back in. Get into bootloader mode (T-Mobile version: phone is off, hold the Volume Down button while you press/release the Power Button. Keep holding the Volume Down button until the colorful screen shows up).
When you're in bootloader, plug in your TP2 to your PC. Now run the .exe of a GSM ROM and follow the steps, as if your phone is synced to the PC. (aka flash as you would usually do).
To flash via the Storage Card: On your PC, go to Start > My Computer > Removable Disk drive (something like that; make sure this is your phone's Storage Card). Drag the .nbh of a GSM ROM there. Rename the .nbh "RHODIMG.nbh" (no quotes). Unplug your Phone. Take out the battery again for one minute. Now, go back into bootloader (hold Volume Down button and press/release Power button [keep holding the Volume Down button]). Follow the steps to flash the phone.
Good luck.
Click to expand...
Click to collapse
I wonder if you can help me; i have a sprint hybrid cdma/gsm and it has black screen no lights at all but the qualcomm cpu is easily recognized by pc-have tried all known methods to get in bootloader but i get no lights at all??-have fully charged batt from another tp2=any experience w this problem?-thanks

keeps rebooting?
Hello, I'm wondering if anyone has experienced the problem I'm facing:
I have the latest Energy rom, with Android 2.3 on SD card. Android proved to be quite unstable and requires soft resets every now and then. Most of the time I would let it boot into WinMo and then run Haret again to get into Android.
Yesterday I left in running in Android all day, and in the evening I noticed the phone had died. Thinking it was just out of battery, I just plugged it in, let it charge for a few hours, then tried to boot it up. But it just kept rebooting, never getting pass the Touch Pro 2 boot screen.
Did hard resets twice, same thing. Re-flash the rom, same thing. Took out SD card, flashed again, same thing. Everything I tried, it would not get pass the initial boot screen, and just cycles the reboot again. Oh by the way, the hard resets and re-flashes are all successful with no errors.
Anyone have a solution to this? Thanks!

velo25 said:
Hello, I'm wondering if anyone has experienced the problem I'm facing:
I have the latest Energy rom, with Android 2.3 on SD card. Android proved to be quite unstable and requires soft resets every now and then. Most of the time I would let it boot into WinMo and then run Haret again to get into Android.
Yesterday I left in running in Android all day, and in the evening I noticed the phone had died. Thinking it was just out of battery, I just plugged it in, let it charge for a few hours, then tried to boot it up. But it just kept rebooting, never getting pass the Touch Pro 2 boot screen.
Did hard resets twice, same thing. Re-flash the rom, same thing. Took out SD card, flashed again, same thing. Everything I tried, it would not get pass the initial boot screen, and just cycles the reboot again. Oh by the way, the hard resets and re-flashes are all successful with no errors.
Anyone have a solution to this? Thanks!
Click to expand...
Click to collapse
Try flashing another ROM or try putting in another battery and see if the bootloop issue goes away. Kindly update the status of your post if you fixed the issue or are still having problems.

Phone reboots instead of entering recovery mode.

So I've had my htc one s for about 2 years or so now and this problem has started happening rather recently. No matter what I try, I cannot access the recovery menu.
I've tried:
1.Hardware Keys (Going into bootloader and trying the recovery from there) = no go.
2.App that would allow me to reboot to recovery = no go
3.Installing another recovery to see if that would help = no go
I've also tried the method of erasing the cache through fastboot to no avail.
I'm currently running a really outdated version of cyanogenmod (10.1 i believe) and my phone is now currently stuck at the beginning trying to boot up.
I'm not sure what else I can try. Oh and another thing. It seems like when I tried to install another recovery image, it didn't overwrite what was already there and so now I believe that my phone currently has to recovery menus.
I've already searched through the forums looking for help and while some of the threads that I found came close, none of them except for the erasing of the cache one came close to helping me figure out what was going on.
Please help.

Macrophage001 said:
So I've had my htc one s for about 2 years or so now and this problem has started happening rather recently. No matter what I try, I cannot access the recovery menu.
I've tried:
1.Hardware Keys (Going into bootloader and trying the recovery from there) = no go.
2.App that would allow me to reboot to recovery = no go
3.Installing another recovery to see if that would help = no go
I've also tried the method of erasing the cache through fastboot to no avail.
I'm currently running a really outdated version of cyanogenmod (10.1 i believe) and my phone is now currently stuck at the beginning trying to boot up.
I'm not sure what else I can try. Oh and another thing. It seems like when I tried to install another recovery image, it didn't overwrite what was already there and so now I believe that my phone currently has to recovery menus.
I've already searched through the forums looking for help and while some of the threads that I found came close, none of them except for the erasing of the cache one came close to helping me figure out what was going on.
Please help.
Click to expand...
Click to collapse
You can get into bootloader, so just relock it and run an RUU.
Then you can go through the steps of unlocking, installing a recovery and ROM again.

tivofool said:
You can get into bootloader, so just relock it and run an RUU.
Then you can go through the steps of unlocking, installing a recovery and ROM again.
Click to expand...
Click to collapse
Ah ok, I'm going to try that. The problem now is that my phone won't boot up and my volume down button doesn't work. It just stays at the portion of boot up with the cyanogenmod logo. I guess my only option now is wait until my phone dies for it to turn off since it won't stay off by simply shutting it down.

Macrophage001 said:
Ah ok, I'm going to try that. The problem now is that my phone won't boot up and my volume down button doesn't work. It just stays at the portion of boot up with the cyanogenmod logo. I guess my only option now is wait until my phone dies for it to turn off since it won't stay off by simply shutting it down.
Click to expand...
Click to collapse
If you mean your volume down is physically broken, then yikes you might be in trouble. Might have to watch a video on youtube to learn to take it apart and fix/clean the rocker contact.
If you mean it isn't working because of the boot loop, ok. If you hold power down for like 10 seconds it should reset and then you hold down volume down to get to bootloader.

tivofool said:
If you mean your volume down is physically broken, then yikes you might be in trouble. Might have to watch a video on youtube to learn to take it apart and fix/clean the rocker contact.
If you mean it isn't working because of the boot loop, ok. If you hold power down for like 10 seconds it should reset and then you hold down volume down to get to bootloader.
Click to expand...
Click to collapse
Yeah I meant it's actually physically broken. I was hoping that wouldn't be the case but it seems like I'm going to have to find out how to take my phone apart.
Thanks for the help.