Database Info

Desire S in one real mess...

Hi all, well i was playing with my Desire S trying to install the generic wwe rom on it since it is brands, and ended up messing up the phone real badly.
Well i used the good old way of creating a gold card and then flash the RUU. The first time went well, i flashed the generic 1.28.401.1 rom on it, retaining the 0002 boot it had.
Then i went to flash the 2.10 wwe RUU and this time things went bad. For some reason the gold card powers were not evoked and it gave me "CID error" but, the all mighty 2.00.0002 hboot was flashed on the phone before it gave the error. So i had to downgrade the bootloader and i used this great guide as a help but once again things went wrong.
I flashed a pre rooted RUU 2.10 rom using 4EXT recovery as the guide tells to do but, i have no wi-fi and usb connection on the rom. This means i got no way to connect the phone to a pc to change the misc_version file and don't even have wi-fi. So i end up asking for any help here as the phone is left in a very bad situation that i can't see the way out...

Try to reflash same ROM again.
Sent from my Desire S

I believe you should have named your thread "I really messed up my Desire S", as the current title is sort of misleading ;-).

In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.

Rapier said:
In your place I'll try flashing an older ROM, even your initial one and start over. If you still have acces to 4EXT recovery you just have to take out your sdcard, put it on a pc and copy the rom that way (since USB not working). Or you can try to activate USB drive within 4EXT recovery, maybe it'll work.
If you don't have 4EXT recovery, you can try flashing recovery.img (from 4EXT zip file) or a rom by renaming them as PG88IMG.zip and place them on the card (via PC). If you boot to bootloader and try to flash them using the flash procedure for radio, it might work like this.
Sorry if I am saying a stupid thing but this is what I'll try if I had these issues.
Click to expand...
Click to collapse
Well the initial ROM i had on the phone was a branded Vodafone PT and i can't find that ROM anywhere and for some reason goldcards are not working after the bootloader was flashed by the RUU.
I still have the 4EXT recovery and usb works in it. Flashing a ROM via the PG88IMG only works if the RUU has the right CID as the phone is branded, now i don't know if flashing a rooted ROM using that procedure will work. The other thing i may try is flashing an older rooted ROM, like the 1.28.401.1 and see if the wi-fi and usb works.

Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.

smash_07 said:
Well what i can say is that the phone is completely cursed and i can't find a way out of this.
I tried to flash an older rooted ROM, 1.48 and the same thing happened, no wi-fi and usb connection.
I tried to flash custom ROMs then. Even worse, the phone doesn't boot, gets stuck on the htc logo. I tried more ROMS and the same happens.
Flashing official RUU will not work due to the CID error. All i end up is that i can't put the phone to work, simple as that. The only chance i think is to send the phone to HTC and tell them that a screwed the system and want them to flash it all again. I don't know how much that will cost but it seems to be the only way out.
Click to expand...
Click to collapse
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.

Skanob said:
Return it if you still have warranty. If not, read on:
1. Check you HBOOT if it got updated to the new one.
2. If it is updated, I suggest to flash the pre-root 2.10.5 ROM. Then see if it is going to work.
3. If it does, downgrade from there if you still want to.
Click to expand...
Click to collapse
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?

smash_07 said:
Yes it has warranty but im sure it will not be covered since i was the one who messed up the phone system.
Another thing i can do, but this is not a certain option, is to wait and see if alpharev can find a way to S-OFF the new hboot with revolutionary and then open a way to flash the RUUs again and older bootloaders.
But i am more looking to sending it to HTC. Does anyone have an idea how much does it cost to reflash the system on the phone?
Click to expand...
Click to collapse
It would really help if you have given your bootloader details.\
Things you still can do:
1. If hboot is updated to 2.00.0002, then you need to unlock it, flash custom recovery via fastboot, flash custom rom, usable phone.
2. If hboot is S-OFF, same as 1 but skip unlocking. Again, usable phone.
Also, there are a lot of ways for you to change your hboot once you are S-OFF. Use search.

You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium

I my case, that was may of this year, I send my desire (not s) back because of bootproblems, and they reflashed it for free. This was in the Netherlands so don't know how easygoing they are in Portugal, but it's worth a shot I guess.

lowveld said:
You are able to install custom roms, but the phone doesn't boot? And the 1.47 pre rooted boots but no WiFi?
You unlocked the phone with HTC.dev.
Steps:
- pick a custom Rom, any Rom
- extract boot.img from that Rom
- flash the Rom in recovery
- do not reboot
- flash boot.img using fastboot command from your computer (search around for instructions)
- reboot and enjoy
The problem is your phone is still s-on, and blocking the kernel from being written during normal flash. You end up with old kernel and new un-matching modules and libs.
I could be wrong though...
Cheers
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Well i can say that this has worked. I flashed the boot.img form the CM7 rom and it worked perfectly, it booted CM7 rom and have wi-fi and usb connection. Now the only thing left is to be able to flash official RUUs passing tne CID error which for some reason the Goldcards are not bypassing.
But many thanks for your help
(ou como se poderia dizer, obrigado pela ajuda)

[SOLVED] Hangs on bootscreen after RUU

Downgrading hboot with this guide ... OK
Used revolutionary ... OK
Use RUU to install RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_382 ... OK
Rebooting ... HANGS
Now i can't enter recovery mode any more. When i try i get a red triangle with an exclamation mark (like this). So i can't boot, but i can't flash a new rom either. The bootloader still says "revolutionary" and S-off.
I have tried booting a couple of times. The phone won't boot even after 2 hours.
Any way to flash a new (custom) rom?

Why did you downgrade only to upgrade later down the line when you're saying you want to install a custom ROM.
If you have your heart set on flashing that RUU do this;
The problem you are having is because you're still on the rev hboot. Flash eng hboot 0.98.2000 (use fastboot) then try the RUU again.
The recovery you are seeing is the stock one.
I'm unsure if flashing a recovery like cwm right now will allow you to flash roms like normal. I assume it will though.
Do some more reading cause you need it.

The phone didn't had the right language (Dutch) so i wanted to flash a new rom.
Before i could flash the rom i needed to downgrade because of the wrong hboot version.
I have downloaded Eng S-off from here. I can boot into fastboot and run that batch?

Problem solved.
Flashed Clockworkmod through fastboot. After that recovery worked again.
I flashed a custom rom this time. That one worked, so i'll stick with that.

[Q] Can't get past CWM.. HELP!?

OK.. here is the deal: HTC One S, T-MO, flashed recovery (TWRP), NO ROM would work in the WiFi dept. I tried flashing the radio and no matter what I couldnt get it to flash the 1.5 or 1.84 radio. TWRP would take forever and say it was complete, but the radio version still said 1.04 (or something) in hboot.
Also, I tried going back to a Stock Tmo RUU and it would ALWAYS fail at the signature part of the install EVEN THOUGH I relocked my bootloader.
SO- I unlocked my bootloader, I flashed CWM. Works like a charm.. or so it seems. I flashed the radio and it will only boot into CWM. I can flash a ROM but it still only boots into CWM. I cant even get into fastboot. This sucks.
Ideas anyone?

What happens if you do adb reboot bootloader from your computer while the phone is in CWM?

It reboots, the screen flickers for a millisecond or so (I am sure its probably trying to load hboot and gives some type of error so fast that I can't see) and then it goes to CWM. I am thinking about flashing it back to team win recovery...

mbolden said:
OK.. here is the deal: HTC One S, T-MO, flashed recovery (TWRP), NO ROM would work in the WiFi dept. I tried flashing the radio and no matter what I couldnt get it to flash the 1.5 or 1.84 radio. TWRP would take forever and say it was complete, but the radio version still said 1.04 (or something) in hboot.
Also, I tried going back to a Stock Tmo RUU and it would ALWAYS fail at the signature part of the install EVEN THOUGH I relocked my bootloader.
SO- I unlocked my bootloader, I flashed CWM. Works like a charm.. or so it seems. I flashed the radio and it will only boot into CWM. I can flash a ROM but it still only boots into CWM. I cant even get into fastboot. This sucks.
Ideas anyone?
Click to expand...
Click to collapse
mbolden said:
It reboots, the screen flickers for a millisecond or so (I am sure its probably trying to load hboot and gives some type of error so fast that I can't see) and then it goes to CWM. I am thinking about flashing it back to team win recovery...
Click to expand...
Click to collapse
Try flashing the boot.img thats compatible with your ROM. As for going back to stock try this http://forum.xda-developers.com/showthread.php?t=1927939 If you're on Hboot 1.14 then the T-Mo RUU's wont work for you. I had that problem.

antny said:
Try flashing the boot.img thats compatible with your ROM. As for going back to stock try this http://forum.xda-developers.com/showthread.php?t=1927939 If you're on Hboot 1.14 then the T-Mo RUU's wont work for you. I had that problem.
Click to expand...
Click to collapse
OK.. I thought about that.. but my question is: How can I flash a boot.img if I cant get into fastboot? I installed the trickdroid ROM and I have the boot.img from the zip. I DID try to go back to stock (when I could still access everything pretty easily), but It got stuck on the signature part of the RUU. I went back to trickdroid and all was well sans the WiFi not working.
Can I flash a boot.img via ADB since that is the only thing really working right now?
Thanks
-M

If you still need help...
I'm sure you guys have figured this out by now, but I Solved a problem very similar to this one in my Thread. I was able to return to Stock while still being Rooted.

[Q] Cant't get a stable ROM

Hi Guys.
I have a Problem with my HTC One S (ville).
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT 2-15.000
RADIO 1.11.50.05.28
After using the "unofficial" HTC Stock Rom 4.1 with root (Which works sometimes and sometimes not, dont ask me why...), i decided to upgrade.
First I tried Liberty Rom, but after installing my phone was in endless start loop.
So i tried CM (every Version i could find), but after flashing it hang at the HTC Start screen (The One with the Red text).
Then I Tried Viper One S. This was the only one i could start. It runs perfect, except the random reboots. Sometimes every 2 min, sometimes no reboot in one day.
I tried it with TWRP 2.6 and 2.7 and CWM and erverytime the same results: no running OS or a "rebooting-party-OS".
I installed everything with an USB drive connected to the phone via cable.
I tried to get HBOOT 2.16, didnt work.
I tried flashing via ADB, doesnt work. My Computer (win 7) doesnt find the devices.
I tried S-Off, but doesnt work because of ADB-Problem...
I read almost every thread here, but nothing helped...
The Backup of my HTC stock, doesn work. When I restore it, it starts and i have a black screen with only the notification bar and nothing works.
Going back to the orignial RUU's doesnt work. Trying to flash the zip gives me an error, and when i start the .exe the program doesnt find my phone.
So i decided to ask you guys, cause you know everything

peter13337 said:
Hi Guys.
I have a Problem with my HTC One S (ville).
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT 2-15.000
RADIO 1.11.50.05.28
After using the "unofficial" HTC Stock Rom 4.1 with root (Which works sometimes and sometimes not, dont ask me why...), i decided to upgrade.
First I tried Liberty Rom, but after installing my phone was in endless start loop.
So i tried CM (every Version i could find), but after flashing it hang at the HTC Start screen (The One with the Red text).
Then I Tried Viper One S. This was the only one i could start. It runs perfect, except the random reboots. Sometimes every 2 min, sometimes no reboot in one day.
I tried it with TWRP 2.6 and 2.7 and CWM and erverytime the same results: no running OS or a "rebooting-party-OS".
I installed everything with an USB drive connected to the phone via cable.
I tried to get HBOOT 2.16, didnt work.
I tried flashing via ADB, doesnt work. My Computer (win 7) doesnt find the devices.
I tried S-Off, but doesnt work because of ADB-Problem...
I read almost every thread here, but nothing helped...
The Backup of my HTC stock, doesn work. When I restore it, it starts and i have a black screen with only the notification bar and nothing works.
Going back to the orignial RUU's doesnt work. Trying to flash the zip gives me an error, and when i start the .exe the program doesnt find my phone.
So i decided to ask you guys, cause you know everything
Click to expand...
Click to collapse
By any chance, AFTER you flashed any of the above ROMs, have you also flashed boot.img of that ROM (kernel) separately from fastboot? Based on what you say, you have no working ADB so I could guess fastboot isn't working either, but I want confirmation. According to the symptoms, it looks like you have not flashed/have the proper kernel for the ROM...
Sent from nowhere over the air...

Rapier said:
By any chance, AFTER you flashed any of the above ROMs, have you also flashed boot.img of that ROM (kernel) separately from fastboot? Based on what you say, you have no working ADB so I could guess fastboot isn't working either, but I want confirmation. According to the symptoms, it looks like you have not flashed/have the proper kernel for the ROM...
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hey.
No I just flashed the installing .zip of the ROMs. Should I do that and yes, how does it go ?
When i connect my phone via USB with my PC (in Bootloader) it says fsatboot USB and i installed with that way TWRP and CWM Recovery...

peter13337 said:
Hey.
No I just flashed the installing .zip of the ROMs. Should I do that and yes, how does it go ?
When i connect my phone via USB with my PC (in Bootloader) it says fsatboot USB and i installed with that way TWRP and CWM Recovery...
Click to expand...
Click to collapse
It seems that even you read every thread, you missed some important things. First remember: if you're S-On, you MUST flash EVERY time after a ROM flash the corresponding kernel. Or else ROM won't boot. There are threads in which this is discussed but I'll summarize the steps:
1. Open (on your PC) the ROM zip and find inside the file called boot.img. Usually you'll find it in /system. If there are ROMs made for both 2.15 and 2.16 hboot (I know only one that's Liberty Max), it could be that the file is located in a /boot folder in the zip and the file name contains 2.15 or 2.16 to know for which hboot it is...for you it is the one having 2.15 in the name.
2. Copy the ROM zip onto your phone, enter recovery and flash it. I won't detail this step since you should know how to do it but I'll draw your attention upon one thing....BE SURE you have the correct recovery for the ROM you want to flash. That is, for most (or all) 2.15 ROMs you could flash the latest official TWRP 2.7.1.0 from HERE and for 2.16 ROMs you should flash the recovery recommended in that particular ROM thread
3. Having the boot.img file ready and copied on your PC in the location of ADB and fastboot (usualy where Android SDK is installed, in the platform-tools folder), first check that fastboot is working. To do that, after you flashed the ROM, reboot in fastboot mode (bootloader) from recovery and having phone connected on USB as you said before, open a command prompt in the ADB folder and issue the command: fastboot devices. You should get a result containing the S/N of your device...if you get an empty response, that means fastboot doesn't recognize your device. I am almost sure that it does tho, since you said you flashed this way the recovery (you couldn't do it otherwise)
4. Having fastboot working and boot.img in the same folder, issue the following command: fastboot flash boot boot.img
5. Reboot the device, the ROM should boot up and work

Htc one s (s4) no rom

Hi
I have a problem witch my HTC ONE S (S4). Some days ago i decided to flash ViperC2 5.2.1 (http://forum.xda-developers.com/showthread.php?t=2531065) on my device.
I unlocked bootloader and flash latest TWRP recovery. Everything was going well until flashing custom rom. After wiping partitions AROMA installer end instalation after 2-3 sec. Now my phone does not have any software.
I can't flash ruu - signature fail
I can't restore my recovery via TWRP (after rstore phone stuck on white screen with red subtitles)
I can't flash any different custom rom (installer can't start)
Please help me. How can i back my HTC to life ?
My phone is S-ON
HBOOT 2.15.0000
RADIO 1.11.50.05.28
CID HTC_032

Hello,
first off, I think you flashed the wrong version of that ROM onto your phone. You probably would have wanted this one->(http://forum.xda-developers.com/showthread.php?t=2667758). Also, can you get to the bootloader by just pressing power and volume down for a bit(20-30 seconds) and see if it loads. If so, then try to use fastboot and re-flash a recovery and adb sideload a rom that doesnt use AROMA installer.

Thanks This ROM works fine. Now i have new issue - sometimes phone loses coverage and asks for a PIN code. Does anyone know how to fix it ? Maybe i should change a radio (my phone is S-ON) ?