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)

Desire S Orange UK downgrading woes

Hi all,
New to the developer scene in terms of android phones so this current situation is causing a head scratch.
I think the problem lies because i've i tried flashing the x.x.401.x version when my phones branded software is x.x.61.x and i can't seem to find a RUU for it (20+ forum pages later). I've unlocked the HBOOT using HTCDev and i've managed to get clockworkmod on it under the recovery but the phone is still S-On and while I keep installing SU-3.0 through clockworkmod I still don't think I have root access according to ROM manager.
Any custom ROM I try to install (CyanogenMod, MIUI english fan version, MIUI official version) successfully installs on clockworkmod but just hangs on the HTC logo upon reboot and has been left for hours to make sure. I'm guessing this is down to actually having root or not?
As i've said I can't find the downgraded software version but the Europe RUU has the same radio as my phone, I am guessing that the branded software version is more important than matching radio's?
If anyone can help i'll be greatly appreciated because i'm starting to tear my hair out
Seany
EDIT: there is a x.x.61.x RUU for orange UK online somewhere but the radio is not the same (Radio_20.28b.30.0805U _38.03.02.11_M_release, as opposed to mine: 20.4801.30.0822U_3822.10.08.04_M) i'm guessing it would be a bad idea to flash until I get confirmation as I have no idea what would happen.
EDIT EDIT: That RUU is for an older version of gingerbread (V2.3.3 compared to V2.3.5 on mine) and HTC Sense V2.1 of which mine is V3.0

Then you should keep reading. Not sure what you getting at with the RUU stuff.
As for the custom ROM,.......
You need to flash the boot.img of the ROM you are trying to flash. Look into it.
fastboot flash boot boot.img

From what I've researched the RUU was needed in order to downgrade the bootloader from 2.00.0002 to 0.98.0000 in order to use the Revolutionary io in order to S-Off.
As for the custom ROM I've flashed the boot and now I've got bootloop for the cyanogenmod ROM, going to try the MIUI and see what happens. It's like it isn't installing the files but I can flash the boot
EDIT: MIUI also in bootloop, I'm thinking it has something to do with the flashing of the ROM using clockworkmod because it seems like it has no progression from the boot file.

Thankyou so much foX2delta, it was a boot.img issue and to do with flashing the boot, problem resolved

[Q] Recently rooted Inspire 4g

Hey all. Recently used AAHK (yes, I know now) to root this phone. Bootloader reports the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
.eMMC-boot
Question: In order to flash ROMS while "S-ON" I need to extract and separately flash boot.img included in ROMs after flashing ROM? If so, can boot.img be flashed from sdcard, or just via PC using adb?
Question: Can I get "S-OFF" after the fact, thus eliminating additional boot.img flashing.
This is my second Inspire/DHD. With my first, AAHK worked fine and I think I was "S-OFF" when rooted. I know I was able to flash ROMs to my hearts content (w/o ever flashing boot.img), until I bricked it (after flashing quite a few ROMS, figured procedure was same for last one I grabbed; silly me for not reading install instructions. Recovery help post for that issue forthcoming)
TIA

IC1NYC said:
Hey all. Recently used AAHK (yes, I know now) to root this phone. Bootloader reports the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
.eMMC-boot
Question: In order to flash ROMS while "S-ON" I need to extract and separately flash boot.img included in ROMs after flashing ROM? If so, can boot.img be flashed from sdcard, or just via PC using adb?
Question: Can I get "S-OFF" after the fact, thus eliminating additional boot.img flashing.
This is my second Inspire/DHD. With my first, AAHK worked fine and I think I was "S-OFF" when rooted. I know I was able to flash ROMs to my hearts content (w/o ever flashing boot.img), until I bricked it (after flashing quite a few ROMS, figured procedure was same for last one I grabbed; silly me for not reading install instructions. Recovery help post for that issue forthcoming)
TIA
Click to expand...
Click to collapse
IF your bootloader says S-ON you can unlock it and flash a custom recovery. Then, yes you need to flash the boot.img of the rom each time you flash a rom in fastboot.
For further help use the guide on my signature...you also have an script to unlock, flash recovery and root.

Thanks for the response.
I just ran the tool that is no longer supported again and all is well.
As for the original, mucked-up unit, using adb I am able to get to bootloader, recovery and can flash, but phone never boots. Tried appropriate PD98IMG on root of SD; tried applying same file as "update.zip and tried straight custom ROM. Right now stuck at CM10's animated boot screen. Guess I have to do some more skim....uh...reading.

IC1NYC said:
Thanks for the response.
I just ran the tool that is no longer supported again and all is well.
As for the original, mucked-up unit, using adb I am able to get to bootloader, recovery and can flash, but phone never boots. Tried appropriate PD98IMG on root of SD; tried applying same file as "update.zip and tried straight custom ROM. Right now stuck at CM10's animated boot screen. Guess I have to do some more skim....uh...reading.
Click to expand...
Click to collapse
Is it S-On?

bananagranola said:
Is it S-On?
Click to expand...
Click to collapse
Both units are S-OFF.

Issue resolved with effed-up unit. I flashed latest CM nightly, then flashed boot.img from that release, and (as Kelly Bundy would say) vy-o-la, working phone.
Initially found with my previous attempts at flashing (w/o flashing boot img) that phone stayed on ROMs boot spalsh. Also, found at times that phone would boot straight into recovery, but with blank screen. Only way to tell phone was powered was by the illuminated keys (Home, Menu, etc). And with no VOL- key, only way to move and select items was by using the Menu key, with screen blanking out after each key press.
BTW, how I initially effed-up this unit was by flashing http://forum.xda-developers.com/showthread.php?t=2204384 without reading install instructions. I'd just flashed the zip same as I've been doing with previous ROMs I've tried. :silly: :

IC1NYC said:
Issue resolved with effed-up unit. I flashed latest CM nightly, then flashed boot.img from that release, and (as Kelly Bundy would say) vy-o-la, working phone.
Click to expand...
Click to collapse
If it's S-Off, you shouldn't need to flash the boot.img.

bananagranola said:
If it's S-Off, you shouldn't need to flash the boot.img.
Click to expand...
Click to collapse
It is s-off; was when initially rooted way back when AAHK was still active and still is. However, after multiple attempts at recovery flashing ROMs, this last time I flashed boot.img as well and it booted correctly. Note that ROMs I tried were stock, rooted stock and most recently CM7 and CM10 based.

IC1NYC said:
It is s-off; was when initially rooted way back when AAHK was still active and still is. However, after multiple attempts at recovery flashing ROMs, this last time I flashed boot.img as well and it booted correctly. Note that ROMs I tried were stock, rooted stock and most recently CM7 and CM10 based.
Click to expand...
Click to collapse
That's bizarre...

[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

[Q] Desire S bricked by not downgrading Hboot?

Hi all!
First of all: I know. I am a dumbass for not doing a backup. (and several other things)
Second: Thank you for your time! I really appreciate it- thats why I tried for two days to solve the problem by searching the internet for guides to restore my phone and not stealing your time.
If you just want to help me - skip the first part ("The story"). I just had to write it down, because I am that desperate and hopeless...
The story
Beside my Nexus 5 I wanted a spare phone to go outdoors and have a nice small phone - other than the huuuuuuge Nexus.
My last phones were the HTC Sensation, a Desire GSM and the Wildfire. So I decided to get a Desire S and do what I did to all my phones and tablets yet: root it.
Because I had the dumb idea that rooting a couple of phones makes me an expert I skipped the "reading guides"-part and jumped right to the "beeing an idiot"-part and downloaded the Revoked-tool.
After I got the TWRP-recovery I also skipped the "making a backup"-part and that is where my disaster began....
The problem
I tried to root my phone, but I did not reverse the Hboot. So now my phone IS NOT s-off, but I've got a working recovery installed and I can get into Fastboot and the Bootloader.
But because my partitions are wiped I can neither boot normally nore can I install a custom recovery (because of the "s-on").
My phone has got an O2-branding, so I can't install the normal Android 4.0 RUU. Neither works the O2 RUU. I suppose, because it still is the Android 2.4 - Version ( the name of the file is "RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178935_signed.exe") and it does not work with my phone....
Is there any chance to get a working Desire S again?
Thabks for your time....

u have stock recover. and u have (i suppose) an unlocked bootloader.
have u tried flashing the recovery through fastboot command ?
fastboot flash recovery recovery.img
download TWRP or 4EXT touch zip file - then unpack it and copy the recovery.img inside it to fastboot or android-tools folder
open cmd there (preferably with admin rights)
and run that command.
if it is able to flash a custom recovery, then u can try to flash a rom.
u might need to check if u have a sony or hitachi screen panel though (but that should have been before u tried rooting, i think)

Hi rht_sg,
thanks for your answer!
Right. My Bootloader is unlocked.
The problem is the "S-ON" I think.
I've got a recory installed, but I can not intall any custom ROM because of the "S-ON"-Mode.
Here the important things I have foregotten in my first post:
In FASTBOOT my phone says:
"
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
eMMC-boot
"
...and my recovery is TWRP v2.4.0.0

You can install a custom rom without being s-off, but you have to flash the boot.img (from the rom) manually in fastboot after installing the rom in recovery (fastboot flash boot boot.img).
I would recommend updating your recovery to either twrp 2.7 (from the thread in this forum) or the latest 4ext touch. One reason being that older recoveries fail when trying to flash kit-kat roms (error 7).
To update your recovery while still s-on, use fastboot (fastboot flash recovery recovery.img)

Thanks!
That solved it. - Now I could install a custom ROM again.
Now I follow your advice to flash the latest recovery.