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] upgarde snaufu...

was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.

What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.

first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off

No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?

I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.

iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.

i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.

i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.

well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.

[Q] Urgent!! Need Help!! No ROM is booting :(

Hi there!
Few days back I had a problem of low internal memory. I posted the problem, got some responses, then followed cute prince's Nandroid restoring tutorial. Flashed the latest Cm9, all was working fine. Then again needed a change (I'm kinda flashaholic ), wiped / reset my phone thru TWRP recovery (whatever is the procedure) and was unable to flash any single rom onwards. Tried to flash stock rom, even tried to restore my 6 months old cwm recoveries, but nothing boots up. I also tried to flash boot.img thru fastboot and flash the rom consequently but it too didn't work.
Now, I have no rom on my explorer except getting to bootloader, fastboot, TWRP or Clockworkmod recoveries. I can't do the nandroid restore as told by cute prince, now.
So I would have to post again here in the forum for the above problem. Here, what I need is to find out about what went wrong actually and what is the solution to the problem!! I hope am not talking about bricking the phone or something.
An urgent reply is highly appreciated, please
Regards.

vikingmax said:
Hi there!
Few days back I had a problem of low internal memory. I posted the problem, got some responses, then followed cute prince's Nandroid restoring tutorial. Flashed the latest Cm9, all was working fine. Then again needed a change (I'm kinda flashaholic ), wiped / reset my phone thru TWRP recovery (whatever is the procedure) and was unable to flash any single rom onwards. Tried to flash stock rom, even tried to restore my 6 months old cwm recoveries, but nothing boots up. I also tried to flash boot.img thru fastboot and flash the rom consequently but it too didn't work.
Now, I have no rom on my explorer except getting to bootloader, fastboot, TWRP or Clockworkmod recoveries. I can't do the nandroid restore as told by cute prince, now.
So I would have to post again here in the forum for the above problem. Here, what I need is to find out about what went wrong actually and what is the solution to the problem!! I hope am not talking about bricking the phone or something.
An urgent reply is highly appreciated, please
Regards.
Click to expand...
Click to collapse
change TWRP to cwm and then flash your cwm recoveries...........search xda how to install cwm over twrp...........
Hit thanks if i help

i had the same problem too.....i was using the twrp because its touch...but i think its not as good as cwm.....install cwm and then yannou's recovery .....you can find it in index thread...yannou is best ...im using it for four months ...no problem till now....

Burnt Nand?
Come here
http://forum.xda-developers.com/showthread.php?t=2183130
Sent from my HTC Explorer A310e using xda premium

[Q] Having Issues Flashing Rage ROM

Hello, all. I am a pretty experienced flasher, and I have been running HatkaXL on my device for quite some time now. I saw where a new ROM had developed, and tried to flash it last night (with no luck). My device is S-ON (I would consider going S-OFF, I just do not understand the terminology with SuperCID and all that good stuff). Anyway, I downloaded the ROM, patch, and wiped (completely). I formatted /system, performed a factory data reset, wiped the cache and dalvik cache. I installed the ROM and patch, and tried to reboot afterwards. I went into a bootloop. I did a restore, downloaded both files again, but I put the boot.img file aside and flashed it separately (after the ROM and patch the next time). I still got a bootloop. Any suggestions?

Worked fine for me. I flashed it a few times due to trying to mod it and being unsuccessful lol.
Sent from my HTC One XL using Tapatalk 2

Method of Recovery
InflatedTitan said:
Worked fine for me. I flashed it a few times due to trying to mod it and being unsuccessful lol.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Just out of curiosity, were you using TWRP or CWM? I have been running the supported version of CWM (I have always liked it better for some reason). I think it's the cool hat and orange eye, but just wanted to see if maybe you used TWRP?!? Note: HatkaXL has been flashing flawlessly on CWM, so...just wondering.

mikenjen0524 said:
Just out of curiosity, were you using TWRP or CWM? I have been running the supported version of CWM (I have always liked it better for some reason). I think it's the cool hat and orange eye, but just wanted to see if maybe you used TWRP?!? Note: HatkaXL has been flashing flawlessly on CWM, so...just wondering.
Click to expand...
Click to collapse
I would use TWRP 2.3.3.1 or below (no issues and is compatible with all roms) If you intend to switch, after flashing a new recovery you should always fastboot erase cache.
When you say you flashed the boot.img seperately did you flash it in CWM or using fastboot? It should be done with fastboot.
SuperCID is just a changed CID to 11111111 or 22222222 from default. Default CID is different from carrier to carrier. If you have an AT&T phone and had to root/unlock bootloader, you have SuperCID.

Thanks
exad said:
I would use TWRP 2.3.3.1 or below (no issues and is compatible with all roms) If you intend to switch, after flashing a new recovery you should always fastboot erase cache.
When you say you flashed the boot.img seperately did you flash it in CWM or using fastboot? It should be done with fastboot.
SuperCID is just a changed CID to 11111111 or 22222222 from default. Default CID is different from carrier to carrier. If you have an AT&T phone and had to root/unlock bootloader, you have SuperCID.
Click to expand...
Click to collapse
I never knew about the fastboot erase cache thing (thanks). I got it just a few minutes ago. It would not go with just flashing the two files and then rebooting. I had to manually boot into bootloader, reboot my computer (to get fastboot to recognize my device), and then flashed the boot.img via adb. I don't know why it was such a bugger, but I finally got it.