Database Info

[Q] Please help, no Android installed, cannot install, phone stuck on HTC logo

Long time lurker first time poster. I had a Nexus One two years ago so I was here very very often.. Since I got my Desire S a year ago, I haven't been able to flash a custom rom OR S-OFF.
Unlocked with HTCdev, rooted, HBOOT 2.00.0002 (downgrading hboot never worked either), S-ON
Last night I tried again to get onto ICS (official RUU doesn't install either). I installed 4EXT touch, flashed recovery, had my ROM (Fallout) on SD ready. Rebooted phone into new recovery to find that is was still the OLD revolutionary recovery and not 4EXT. This was 4am so I thought I'd try the usual wiping + rom flash. It went through normally and said completed although the progress bar only got about 1/3rd before jumping straight to finished. Rebooted.. stuck at white HTC logo screen.
My issues are that I cannot install HTC Sync phone drivers without phone powering up to be recognised by the PC, AND I cannot turn USB debugging on for obvious reasons
My phone is veryvery important and I'm now scared I won't be able to get it working again. Please help me.
TLDR; stuck on White HTC logo screen, no Android installed, cannot see how I can install one, help!
If anyone could shine some light on what I need to do next, I'd be very grateful.
Thanks in advance.. and afterwards

How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...

teadrinker said:
How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...
Click to expand...
Click to collapse
For the 4EXT recovery I 'flashed' it from inside the touch app thinking that was enough these days.. naively. Had just been fighting with GF at 4am and was fed up and about to go to bed and in Revolutionary recovery so I thought what the hay, I'll wipe etc in here and use this to try and flash the rom.
I did not flash the boot.img. I goofed. I understand that but now I'm just desperate for any route back to a functional device.
I never stopped installing ROMs and etc on my old Nexus One but that was a while ago and everything just seemed to work. Desire S is being a nightmare.

Decide what you want to do.
If you want to upgrade the phone to official ROM - relock your bootloader and run RUU.
If you want to use custom ROMs - flash the recovery from fastboot and don't forget to flash the kernel from fastboot too.
I won't get into any more details, searching for the right info with these pointers will get you whatever you might need.

Thank you, I'm all fixed. Simply found an old 2.3.5 ROM and flashed and booted fine. Reason I was so stuck was because I had formatted my PC since last installing phone drivers so I couldn't do much hurdur

[Q] ViperOneS rom problem

First noted this is first time installing a custom rom. Long time lurker, first time problem!
HTC One S from Bell (Canada) Rooted/unlocked. CWM for Recovery.
Installed the from Zip in CWM. Cleared everything, went and flashed with fastboot for the boot. Everything looked good. Went back into CWM and cleared cache again.
Went to boot, hanging at htc screen but has the additional red text as well.
What did I miss ?
Thanks for any help or insight into this issue.

Is your phone s-off ... If not thm install 4ext recovery n flash the rom by enabling smart flash in 4ext recovery... Search for 4ext recovery n how to flash rom with s on ull b done
If I hve helped you press the thanks button ...
sent from HTC sensation

No idea what the above poster is on about but... My engrish isnt that good.
CWM is a crappy recovery for our phones. You should use TWRP instead.
But that doesnt seem to be the issue here. The issue you are describing is exactly what happens if boot.img isnt flashed through fastboot.
So, I suggest trying to flash it again through fastboot (fastboot flash boot boot.img).
If it still doesnt work after a couple of tries, change recovery to TWRP and start over from scratch (wipe everything, flash viper, flash boot.img).

Goatshocker said:
No idea what the above poster is on about but... My engrish isnt that good.
CWM is a crappy recovery for our phones. You should use TWRP instead.
But that doesnt seem to be the issue here. The issue you are describing is exactly what happens if boot.img isnt flashed through fastboot.
So, I suggest trying to flash it again through fastboot (fastboot flash boot boot.img).
If it still doesnt work after a couple of tries, change recovery to TWRP and start over from scratch (wipe everything, flash viper, flash boot.img).
Click to expand...
Click to collapse
Thanks so much, It worked. I was starting to stress out. Re-did the flash and BAM music happened. Just sitting at the HTC One screen now. I assume that takes a couple minutes.

Yeah. We dont have 4ext recovery yet for our phones. Only an old outdated version of clockwork, and of course a good updated version of TWRP. I havent used 4ext but have heard interesting things. I hear in the new year there will be some work on bringing it to HTC One S, although I dont know if it will have any features that arent already covered in TWRP.

AKToronto said:
Yeah. We dont have 4ext recovery yet for our phones. Only an old outdated version of clockwork, and of course a good updated version of TWRP. I havent used 4ext but have heard interesting things. I hear in the new year there will be some work on bringing it to HTC One S, although I dont know if it will have any features that arent already covered in TWRP.
Click to expand...
Click to collapse
Yeah im going to be switching over to TWRP. Sounds like its allot better to work with. I know with cwm you can't even mount usb storage, so you end up pushing files on using adb.

[Q] Stuck in Bootloader and TWRP

I have an AT&T HTC One X that's rooted. I wanted to put Cyanogenmod 10 on it, but I accidently wiped the System files instead of the cache. Now it can't boot up regularly, I've tried using Rom Update Utility but it doesn't seem to work. Factory Reset doesn't seem to work either. I didn't expect this to happen because my friend just flashed his a couple of days ago. I've tried making a backup and restoring but no matter what I can't get the phone to start up normally. Unless I put it in TWRP (Team Win Recovery Project) or the HBoot/Bootloader I really can't use it for anything. Any suggestions? I would greatly appreciate it. Also when bootloader opens it says "Tampered" and under it "Unlocked" because I did root it. It didn't have "Tampered" when I first rooted it.
I don't care about Cyanogenmod 10 anymore I just want to have it working again.
Everything else about the phone is in perfect condition but what I just said is the only problem.

Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.

iElvis said:
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
Click to expand...
Click to collapse
Well, I've already flashed it to a few things and so far it hasn't changed anything. Got any links?

Did you fastboot flash boot boot.IMG ? Don't know what hboot you are on, but could be it.
Sent from my Carbon-ize Evita using xda-developers app

[Q] Can't Get Rom to Boot

I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.

utdps said:
I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.
Click to expand...
Click to collapse
Did you flash boot boot.img?

Crypto66 said:
Did you flash boot boot.img?
Click to expand...
Click to collapse
I've narrowed down the issue to the install of CleanROM failing. This may be to twrp 2.5.0.0 but as I've said, earlier versions such as 2.3.3.0 aren't responding to touch for some reason. I don't think 2.5.0.0 is my problem though. I can see it if it didn't wipe properly, but the install is failing due to I/O errors.
But yes, I have tried flashing boot.img. twrp tells me I don't have an os when I try to reboot though, so that's the issue.

Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.

Crypto66 said:
Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.
Click to expand...
Click to collapse
Fix permissions won't work without a rom installed. It fails. And from what I understand anyways, fixing permissions is mostly for apps anyways.

Problem solved. Everyone make sure to use TWRP 2.3.3.1 and only that exact version. Older has touchscreen problems and newer has install issues. Man, this stuff can be frustrating at times.

That's not exactly true. Older versions work just fine, I'm using version 2.2 and it has never failed me.
Older versions aren't working for you because you have a newer touchscreen firmware, you would need to downgrade your touchscreen firmware in order to have touch response. For the same reason, you would not be able to run aosp roms until downgrading. Just thought I'd clear that up.
Sent from my One XL using XDA Premium

[Q] Stuck going back and forth between recovery

I think I screwed the pooch. I finally took the plunge and Rooted/S-off (with Sunshine) and installed a custom recovery. Issue is, I think I had TWRP installed and then installed Philz_touch_6.43.6-m8. Now, I can't get out of a recovery boot loop. I'm not 100% sure how I managed this but now when I reboot, I'm getting the red text at the bottom stating "this build is for android development purposes only" and boots me into TWRP. If I try to fastboot flash recovery and install the Philz recovery again, it does it's business, boots into Philz and when I go to reboot Philz it reboots into TWRP. Am I hosed? Any help is greatly appreciated. I was hoping by reflashing Philz it would remove the ability to boot into TWRP. This sucks!
Thanks in advance.

I actually just think somehow I hosed the system. I was able to download a custom ROM and get out of this boot loop hell!

upnsmoke67 said:
I actually just think somehow I hosed the system. I was able to download a custom ROM and get out of this boot loop hell!
Click to expand...
Click to collapse
You probably installed twrp into the stock partition, glad you got it fixed.

upnsmoke67 said:
I actually just think somehow I hosed the system. I was able to download a custom ROM and get out of this boot loop hell!
Click to expand...
Click to collapse
I know you fix it...but did you 1st flash twrp via the terminal emulator?

Thanks for the reply guys and sorry I didn't answer sooner. I'm not 100% sure how I did it honestly. First time with an HTC coming off Samsungs.... everything is humming along beautifully and I'm digging the stuff I'm learning from here about these powerful devices. I'm a flashing fool!

upnsmoke67 said:
Thanks for the reply guys and sorry I didn't answer sooner. I'm not 100% sure how I did it honestly. First time with an HTC coming off Samsungs.... everything is humming along beautifully and I'm digging the stuff I'm learning from here about these powerful devices. I'm a flashing fool!
Click to expand...
Click to collapse
I asked bout terminal emulator because twrp has the partitions mapped wrong. So if you do that it will flash to the system one which is what sounded like you did.....I been with HTC forever just a quick tip always fastboot flash if you can as it is the safe way..never use apps or emulator to flash...

OK cool Tigerstown... many thanks for the tip!