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)

[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.

In a really big trouble (Need help with returning to stock ROM)

So... I got excited about flashing my HTC sensation. I had done it before with ZTE blade and it wasn't that hard.
Long story short... I flashed the ROM, all went succesfully, but now I'm stuck in a bootloop. I can restart to clockwork recovery though. So I'm hoping it's still possible to get back to stock ROM. In that I need your help. I need to get information about which stock ROM to download, and how to flash it. I can't get to home screen to use USB sharing. Neither does Clockwork recovery usb sharing work.
Im stuck with putting the memory card to my other phone, putting the needed files on the memory card and then switching the memory card back to my HTC.
I've searched for hours and hours in google for help, but haven't found anything to match my situation. I have no idea what to do.
I've tried formatting system, wiping system and cache and then running CM10, bootloop. Formatted system, cache etc and flashed CM9, bootloop.
I have no idea what to do.
PLEASE HELP!

Did you flash firmware?
Sent from my HTC Sensation using xda app-developers app

Are you sure your s off? Otherwise enable smartflash within 4ext.

So my HBOOT version is 1.27.0.0
And i did the Token ID thing, wasn't that putting it to S-off?
How to check if my firmware is updated? I think I did it but I'm not sure. Tell me the things you need to know.

Laitila said:
So my HBOOT version is 1.27.0.0
And i did the Token ID thing, wasn't that putting it to S-off?
How to check if my firmware is updated? I think I did it but I'm not sure. Tell me the things you need to know.
Click to expand...
Click to collapse
If you were able to find your HBOOT version you should also be able to see whether you're s-off or s-on, copy down all the information that appears when you boot into bootloader and post it here.
You need 3.33 firmware from here. Read well before flashing.
Learnings for the future, always nandroid backup before wiping!

goatee84 said:
If you were able to find your HBOOT version you should also be able to see whether you're s-off or s-on, copy down all the information that appears when you boot into bootloader and post it here.
You need 3.33 firmware from here. Read well before flashing.
Learnings for the future, always nandroid backup before wiping!
Click to expand...
Click to collapse
Tried to flash CM10 again, still bootlooping.
Here's my info from bootloader.
Unlocked
Pyramid PVT SHIP S-ON RL
HBOOT- 1.27.0000
eMMC-boot
Jan 13 2012 17:33

Laitila said:
Tried to flash CM10 again, still bootlooping.
Here's my info from bootloader.
Unlocked
Pyramid PVT SHIP S-ON RL
HBOOT- 1.27.0000
eMMC-boot
Jan 13 2012 17:33
Click to expand...
Click to collapse
Ok so in order to flash a ROM you either need to be s-off or get 4EXT recovery and enable smart-flash.
Again, you need the correct firmware so please make sure you get what you need from the link in my first reply.

As you are S-ON and HTCDEV Unlocked, you need to flash the 4EXT Recovery, enable smartflash in the settings and flash the rom. Then you will be fine! Follow this thread: http://forum.xda-developers.com/showthread.php?t=1631861

matekaneve said:
As you are S-ON and HTCDEV Unlocked, you need to flash the 4EXT Recovery, enable smartflash in the settings and flash the rom. Then you will be fine! Follow this thread: http://forum.xda-developers.com/showthread.php?t=1631861
Click to expand...
Click to collapse
So, it seems that the phone is bricked? Is there no way to bring it back? :C
I've got S-on, no backup and my usb doesnt recognize the phone when I'm in bootloader mode. And I can't get to home screen because of bootloop. 4ex thing needs usb and so does every other thing seem to need? Am I completely ****ed?
Argh, I knew I shouldnt have touched these things :C

Laitila said:
So, it seems that the phone is bricked? Is there no way to bring it back? :C
I've got S-on, no backup and my usb doesnt recognize the phone when I'm in bootloader mode. And I can't get to home screen because of bootloop. 4ex thing needs usb and so does every other thing seem to need? Am I completely ****ed?
Argh, I knew I shouldnt have touched these things :C
Click to expand...
Click to collapse
You are far from bricked. You need to get into recovery and mount usb storage. You can probably do it in clockworkmod but I've never used it so I don't know, if you're having trouble get 4ext recovery (since you do have a way of getting stuff onto your sd as you said in your first post), and you can toggle usb storage from there.

goatee84 said:
You are far from bricked. You need to get into recovery and mount usb storage. You can probably do it in clockworkmod but I've never used it so I don't know, if you're having trouble get 4ext recovery (since you do have a way of getting stuff onto your sd as you said in your first post), and you can toggle usb storage from there.
Click to expand...
Click to collapse
I understood from the 4ext recovery that you need to get usb connection working, without it, there's pretty much nothing to do. I can only get things to my sd card with my other phone, but since i'm s-on, i can't flash it from cwm. At least that's what I've understood. I'm starting to get annoyed. I really don't have money for another phone, and I know that I was really stupid to even try flashing.
If there is a way still, I'm gonna try it, but I can't establish usb connection. When I connect my phone to usb in CWM, it says drivers couldn't be installed.

goatee84 said:
You are far from bricked. You need to get into recovery and mount usb storage. You can probably do it in clockworkmod but I've never used it so I don't know, if you're having trouble get 4ext recovery (since you do have a way of getting stuff onto your sd as you said in your first post), and you can toggle usb storage from there.
Click to expand...
Click to collapse
The thing is, I can't get an usb connection to my phone AT ALL. And I'm stuck in a bootloop and I'm S-ON without a backup. So only thing I do have is unlocked phone and i can boot to fastboot and can get to CWM recovery. Still, I've understood that it ain't enough. I need an usb connection with my phone to my PC. Which for the life of mine I can't get to work.
Any ideas are appreciated. I'm getting desperate :C

Laitila said:
I understood from the 4ext recovery that you need to get usb connection working, without it, there's pretty much nothing to do. I can only get things to my sd card with my other phone, but since i'm s-on, i can't flash it from cwm. At least that's what I've understood. I'm starting to get annoyed. I really don't have money for another phone, and I know that I was really stupid to even try flashing.
If there is a way still, I'm gonna try it, but I can't establish usb connection. When I connect my phone to usb in CWM, it says drivers couldn't be installed.
Click to expand...
Click to collapse
You can still flash 4ext via fastboot. Go to this thread and some way down the OP look for the line "there's a direct download for a version you can flash via fastboot".
Are you familiar with adb? You need to download the recovery.img using the link above and flash it via adb. Read this.

If you are in fastboot and connect your cable, does it read "fastboot USB"? You can flash 4ext from fastboot!
Did you follow the steps from the guide I linked before? You are already unlocked, install the 4ext recovery, enable "smartflash" in settings and flash the Rom you have chosen.
Sent from my HTC Sensation Z710e

Laitila said:
The thing is, I can't get an usb connection to my phone AT ALL. And I'm stuck in a bootloop and I'm S-ON without a backup. So only thing I do have is unlocked phone and i can boot to fastboot and can get to CWM recovery. Still, I've understood that it ain't enough. I need an usb connection with my phone to my PC. Which for the life of mine I can't get to work.
Any ideas are appreciated. I'm getting desperate :C
Click to expand...
Click to collapse
Ok so when you first boot into bootloader you should have:
HBOOT
<VOL UP> to previous item etc. etc.
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Then by selecting FASTBOOT you should be able to connect your usb cable and it will change to FASTBOOT USB. If not you need to be sure you have the correct drivers properly installed on your PC.

goatee84 said:
You can still flash 4ext via fastboot. Go to this thread and some way down the OP look for the line "there's a direct download for a version you can flash via fastboot".
Are you familiar with adb? You need to download the recovery.img using the link above and flash it via adb. Read this.
Click to expand...
Click to collapse
I'm getting real tired, have to go to sleep, but on a quick glance it seemed that with fastboot and adb, you need to have somekind of connection with the pc, right? You can't push commands to your phone without a connection? And I can't get to usb-debugging. I can only use CWM, and it doesn't help.
I'm starting to loose hope, but I'll try to check those threads tomorrow, maybe tomorrow I can save my phone, maybe not.
But thanks alot guys, a really REALLY friendly community. I know it ain't fun trying to help people with their problems, but I appreciate what you're trying to do

Laitila said:
I'm getting real tired, have to go to sleep, but on a quick glance it seemed that with fastboot and adb, you need to have somekind of connection with the pc, right? You can't push commands to your phone without a connection? And I can't get to usb-debugging. I can only use CWM, and it doesn't help.
I'm starting to loose hope, but I'll try to check those threads tomorrow, maybe tomorrow I can save my phone, maybe not.
But thanks alot guys, a really REALLY friendly community. I know it ain't fun trying to help people with their problems, but I appreciate what you're trying to do
Click to expand...
Click to collapse
Yep, you need to be connected to your PC via USB, with drivers installed (I used this) and FASTBOOT selected in bootloader, at which point it SHOULD say FASTBOOT USB.
At this point you can use fastboot commands to flash the recovery.img I previously linked you to, then you will have 4ext recovery and you will be able to set up smart flash to allow you to flash whilst s-on. Only once you get to that stage can you start thinking about flashing firmware and custom ROMS.
And don't lose hope, plenty of phones have been resurrected from far worse conditions. Just requires some patience and careful reading. Don't do anything until you make sure you understand what it is you're about to do.
---------- Post added at 11:48 PM ---------- Previous post was at 11:47 PM ----------
Oh and no need to say thanks....just click it

goatee84 said:
You can still flash 4ext via fastboot. Go to this thread and some way down the OP look for the line "there's a direct download for a version you can flash via fastboot".
Are you familiar with adb? You need to download the recovery.img using the link above and flash it via adb. Read this.
Click to expand...
Click to collapse
ok i downloaded the 4ext file now what!? im having the EXACT same problem. im stuck in a bootloop but im s-off on hboot 1.27.000 and upgraded firmware to 3.33 and still dont know what to do. it looks like 4ext is what to do. but like i said i downloaded the zip file now how do i flash it via fastboot...thats what i wanna know

seangeezy12 said:
ok i downloaded the 4ext file now what!? im having the EXACT same problem. im stuck in a bootloop but im s-off on hboot 1.27.000 and upgraded firmware to 3.33 and still dont know what to do. it looks like 4ext is what to do. but like i said i downloaded the zip file now how do i flash it via fastboot...thats what i wanna know
Click to expand...
Click to collapse
From fastboot, along your usb cable connected and htc drivers/adb are installed, you use the fastboot command: "fastboot flash recovery recovery.img" that's how you can push the recovery on your device. (actually you should have just clicked on the link you quoted and would have found the answer.)

matekaneve said:
From fastboot, along your usb cable connected and htc drivers/adb are installed, you use the fastboot command: "fastboot flash recovery recovery.img" that's how you can push the recovery on your device. (actually you should have just clicked on the link you quoted and would have found the answer.)
Click to expand...
Click to collapse
Helped me! Excellent help from you guys, to the other guy asking for help. Just follow the instructions given. Again, many thanks to the people that helped. You make the world a better place

How to FORMAT ALL partition?

Hi all,
My sensation has been shutting down for no reason for a long time now. No matter what ROM, what kernel, even I have changed the battery twice. It just sometimes turns off, and when I reboot (if it does) it either has very low battery or it will keep shutting down until I plug it in.
To me, it seems like there is something misleading the power level or something. I have super wiped the phone, even reformatted my SD, changed recovery and did the same, flashed thousands of roms (4.1 and 4.2)... and it still does the same.
Funny enough, it doesnt happen when I am in recovery mode (for example, after it shuts down, I reboot into recovery, spend some time there, then reboot and as soon as it boots, bam it shuts down).
This makes me think there is something in a partition that is not touched by the wiping scripts that is bugged and therefore is not fixed after flashing roms etc.
I recently manually wiped and formatted all of my Asus Transformer's partitions (even the recovery) using my PC and it works great, that fixed a problem that also was carried on from ROM to ROM. Hopefully there is a way to do the same for my sensation to give it a 100% clean start.
Thank you very much in advance!
Sent from my Transformer TF101 using Tapatalk 4 Beta

TheKaser said:
Hi all,
My sensation has been shutting down for no reason for a long time now. No matter what ROM, what kernel, even I have changed the battery twice. It just sometimes turns off, and when I reboot (if it does) it either has very low battery or it will keep shutting down until I plug it in.
To me, it seems like there is something misleading the power level or something. I have super wiped the phone, even reformatted my SD, changed recovery and did the same, flashed thousands of roms (4.1 and 4.2)... and it still does the same.
Funny enough, it doesnt happen when I am in recovery mode (for example, after it shuts down, I reboot into recovery, spend some time there, then reboot and as soon as it boots, bam it shuts down).
This makes me think there is something in a partition that is not touched by the wiping scripts that is bugged and therefore is not fixed after flashing roms etc.
I recently manually wiped and formatted all of my Asus Transformer's partitions (even the recovery) using my PC and it works great, that fixed a problem that also was carried on from ROM to ROM. Hopefully there is a way to do the same for my sensation to give it a 100% clean start.
Thank you very much in advance!
Sent from my Transformer TF101 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi,
The recovery 4EXT has a "Format all partitions except sd card" option.
Look HERE for an installation guide.
Alternatively,you could run a RUU ,which will return all your partitions to stock.
Look HERE
Have you tried the trick of jamming some card to improve the contact of your battery?
It may just be loose,and the card keeps it firmly in place.

malybru said:
Hi,
The recovery 4EXT has a "Format all partitions except sd card" option.
Look HERE for an installation guide.
Alternatively,you could run a RUU ,which will return all your partitions to stock.
Look HERE
Have you tried the trick of jamming some card to improve the contact of your battery?
It may just be loose,and the card keeps it firmly in place.
Click to expand...
Click to collapse
Hi, thank you for your reply.
I used to have 4ext and I have used many times the format all option. I recently switched to TWRP recovery to try their formatting options too. Neither solved the problem.
Also, I have two anker batteries, I have made sure they are not loose. Nevertheless, this happens even when the phone resting on the table, so I am sure that is not the issue. I have switched them wth my gf's sensation, and hers works fine and mine doesn't.
I will try the RUU option to see if going back to stock will remove any kind of bricking that may have occured after so many flashes..
do you think there is anything that is not touched by rom flashing, recovery changing, and partition formatting that may be the cause of the problem? I also updated the firmware too 3.32 I believe it was (the latest) for JB 4.2.2... I dont know what else I can flash or change or format to try to eliminate this powering-off issue...
thanks a lot once more

TheKaser said:
Hi, thank you for your reply.
I used to have 4ext and I have used many times the format all option. I recently switched to TWRP recovery to try their formatting options too. Neither solved the problem.
Also, I have two anker batteries, I have made sure they are not loose. Nevertheless, this happens even when the phone resting on the table, so I am sure that is not the issue. I have switched them wth my gf's sensation, and hers works fine and mine doesn't.
I will try the RUU option to see if going back to stock will remove any kind of bricking that may have occured after so many flashes..
do you think there is anything that is not touched by rom flashing, recovery changing, and partition formatting that may be the cause of the problem? I also updated the firmware too 3.32 I believe it was (the latest) for JB 4.2.2... I dont know what else I can flash or change or format to try to eliminate this powering-off issue...
thanks a lot once more
Click to expand...
Click to collapse
Hi,
The RUU option seems all that is left.
Backup everything before you start.
Are you supercid?

malybru said:
Hi,
The RUU option seems all that is left.
Backup everything before you start.
Are you supercid?
Click to expand...
Click to collapse
Yes, back in the day I used revolutionary, got supercid, and recently I updated the firmware to 3.33 (hboot 1.27.1100), and I am S-OFF.
my bootloader:
-Firmware 3.33 .
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-V05.6.0.2226.00.0418
eMMC-boot
Might this be caused by the radio? it's the only thing I havent changed recently.
Also, being supercid, and S-OFF, do I have to lock the bootloader and S-ON? I quickly looked at the RUU thread and that is what I understood...
thanks man!

TheKaser said:
Yes, back in the day I used revolutionary, got supercid, and recently I updated the firmware to 3.33 (hboot 1.27.1100), and I am S-OFF.
my bootloader:
-Firmware 3.33 .
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-V05.6.0.2226.00.0418
eMMC-boot
Might this be caused by the radio? it's the only thing I havent changed recently.
Also, being supercid, and S-OFF, do I have to lock the bootloader and S-ON? I quickly looked at the RUU thread and that is what I understood...
thanks man!
Click to expand...
Click to collapse
Hi,
Noooooooooooooooooooooooooooooooooo!!!!!!!!!!!!!
DO NOT GO TO HTCDEV if you are s-off.
The reason I asked is because you can flash any RUU being s-off and super cid.
Just choose a 3.33 European RUU to run.
EDIT:
Look HERE
Just use the guide to show you how to run it.

malybru said:
Hi,
Noooooooooooooooooooooooooooooooooo!!!!!!!!!!!!!
DO NOT GO TO HTCDEV if you are s-off.
The reason I asked is because you can flash any RUU being s-off and super cid.
Just choose a 3.33 European RUU to run.
EDIT:
Look HERE
Just use the guide to show you how to run it.
Click to expand...
Click to collapse
thanks man, I will run the RUU. I believe I have already done this in the past, but my memory is terrible xDD
3.2 Using RUU to restore partitions
Find your right RUU using 2 in this guide.
Flash your RUU as you normally would by double clicking the executable & following the instructions, you phone must be connected to PC via fastboot USB (in the bootloader).
If you get a Hboot Pre-update message, re-run the RUU once again with your phone connected in fastboot USB.
If the previous step fails, follow points listed under 4. Flashing RUU manually.
Reboot your device to bootloader, your bootloader should now say *Locked* or *Relocked*
Click to expand...
Click to collapse
From the tutorial on RUU in the link you provided, the last point on bootloader being locked or relocked... will I need to do revolutionary again or the other method to unlock it again? Will this be drawback flashing a new ROM?
thanks!

TheKaser said:
thanks man, I will run the RUU. I believe I have already done this in the past, but my memory is terrible xDD
From the tutorial on RUU in the link you provided, the last point on bootloader being locked or relocked... will I need to do revolutionary again or the other method to unlock it again? Will this be drawback flashing a new ROM?
thanks!
Click to expand...
Click to collapse
Hi,
Bootloader will not be affected because you are s-off.
You will not lose s=off either.
YOU WILL LOSE EVERYTHING else.
So,backup first.
You will end up with stock recovery,ROM and kernel.
You will need to re-install a custom recovery,before you install a new ROM.
See how it all works before you do anything.

malybru said:
Hi,
Bootloader will not be affected because you are s-off.
You will not lose s=off either.
YOU WILL LOSE EVERYTHING else.
So,backup first.
You will end up with stock recovery,ROM and kernel.
You will need to re-install a custom recovery,before you install a new ROM.
See how it all works before you do anything.
Click to expand...
Click to collapse
well, the RUU went fine, but now I have a locked bootloader, and can't flash a recovery via fastboot. (still S-OFF).

TheKaser said:
well, the RUU went fine, but now I have a locked bootloader, and can't flash a recovery via fastboot. (still S-OFF).
Click to expand...
Click to collapse
Hi,
Look HERE
Post 2:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Should unlock your phone again.
Run the phone for a while.
Does it still reboot?

malybru said:
Hi,
Look HERE
Post 2:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Should unlock your phone again.
Run the phone for a while.
Does it still reboot?
Click to expand...
Click to collapse
sweet, that did the trick
I flashed a dark splash screen and the cwm recovery. All went well and I could flash my 4.2.2 rom. I will restore my titanium backup apps and hope for the best. Cant tell now if the sudden turning off still happens because my phone has been plugged in all the time while I was doing this.
I will report probably tomorrow once the battery is bit used.
Sir, I must say, you are a legend. Thank you very very much for your help!!! your rock!:good: :laugh:

TheKaser said:
sweet, that did the trick
I flashed a dark splash screen and the cwm recovery. All went well and I could flash my 4.2.2 rom. I will restore my titanium backup apps and hope for the best. Cant tell now if the sudden turning off still happens because my phone has been plugged in all the time while I was doing this.
I will report probably tomorrow once the battery is bit used.
Sir, I must say, you are a legend. Thank you very very much for your help!!! your rock!:good: :laugh:
Click to expand...
Click to collapse
Hi,
Hope it all works out.

[Q&A] [s-off] moonshine s-off for ville_c2

Q&A for [s-off] moonshine s-off for ville_c2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [s-off] moonshine s-off for ville_c2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Hello everyone.
I tried using Moonshine to S-OFF my HTC One S (villec2), which didn’t quite go as intended and now I’m stuck in a boot loop.
I downloaded Moonshine from the Moonshine website, under HTC One S – S3 model (ville_c2), first download for ROM version 3.19.401.101 (I got that version number from Software information somewhere in Settings). I then made sure that the phone had Fast boot disabled under power options, turned off the screen lock, connected the phone to the desktop (running Ubuntu 14.10) via the USB cable, and did sudo ./distiller. Moonshine did its magic for a few minutes and, in the end, the phone was powered off. However, when I powered it on, it got stuck in a boot loop.
Now, to solve this, I rebooted into recovery mode (I’ve got something that says CWM-based Recovery v5.5.0.4, not quite sure where I got that) and tried restoring the backup I had previously made and/or wiping caches, none of which seemed to help.
So here’s where I am now: I can boot into bootloader just fine. The bootloader says moonshine S-OFF on top. Normal boot is stuck in a boot loop; it shows the regular splash screen for a few seconds, then a window entitled Android is upgrading… and a spinning progress thingy along with Optimizing app 1 of 24. for a second, then Starting apps. for a few more seconds, then the screen just turns off and the loop begins anew. Occasionally I can see, for a brief moment, an error message right at the end; I can’t quite discern what it says, but it is about a crash of something with gapps in its name.
During the boot loop, I can connect to the phone using ADB (and by that I mean that I can access the shell with adb shell or reboot into bootloader or recovery with adb reboot bootloader or adb reboot recovery). Oddly enough, when I try to power down, the phone doesn’t power down but reboots into recovery instead. I tried powering it down by: holding the power button for a really long time (this, however, just restarts the boot loop); FASTBOOT → POWER DOWN from the bootloader; adb reboot -p; adb shell → reboot -p.
So, what do I do now? (I apologize if I made some obvious mistake with the procedure described above, or with making this post…)
EDIT: I also forgot to mention that the Moonshine directory seems to contain a file called boot_backup.img; can it help me with anything?

i have a problem with s-on. this app solved.

thanks for s-off
Hi, i want to thank all the people involved into moonshine's s-off solution for villec2. I've run it on 64-bit Debian Wheezy. It worked perfect. Finally my One S is free .
I can't thank you on solution thread because i have not enough posts to post anywhere.
The CID for my One S was ORANGB10. It was bought in ORANGE PL.
Thanks again.

moonshine on stock ICS
Moonshine on stock ICS?
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Moonshine on stock ICS 4.0.4?

moonshine on stock ICS
Moonshine on stock ICS 4.0.4?

Aleksic82 said:
Moonshine on stock ICS 4.0.4?
Click to expand...
Click to collapse
moonshine request a jb bases rom but in runrummer dont say anything. They say runrummer run in a stock or another roM. So, checkout, try and coment!

JavierG123 said:
moonshine request a jb bases rom but in runrummer dont say anything. They say runrummer run in a stock or another roM. So, checkout, try and coment!
Click to expand...
Click to collapse
I would recommend to have a close to stock ROM for rumrunner too. I remember I've used Viper at that time for this purpose
Sent from nowhere over the air...

Rapier said:
I would recommend to have a close to stock ROM for rumrunner too. I remember I've used Viper at that time for this purpose
Sent from nowhere over the air...
Click to expand...
Click to collapse
i have 4.1.1. 3.20.518.102 CL175688 release-keys. can i use rumrunner?

moonshine on stock ICS
Hi every one, greetings from Serbia!! I have couple problems on my Htc one s ville2. 1. Can't unlock relocked bootloader, i many time try, its finish every segment ok htcdev, cmd, token, bin code, mobile phone accept, i click yes on ulock htc screen on mobile and enter power buton, restart phone, and up system, every ok, but not unlocked in bootloader, stay relocked. Phone its s-on, my phone (ICS 4.0.4)find OTA update and download, but cant install update, Verification Failed. S-on its problematic? Why i can't unlocked bootloader, i want to install twpr and flash officiall (and root) OTA update on my Htc.

Aleksic82 said:
Hi every one, greetings from Serbia!! I have couple problems on my Htc one s ville2. 1. Can't unlock relocked bootloader, i many time try, its finish every segment ok htcdev, cmd, token, bin code, mobile phone accept, i click yes on ulock htc screen on mobile and enter power buton, restart phone, and up system, every ok, but not unlocked in bootloader, stay relocked. Phone its s-on, my phone (ICS 4.0.4)find OTA update and download, but cant install update, Verification Failed. S-on its problematic? Why i can't unlocked bootloader, i want to install twpr and flash officiall (and root) OTA update on my Htc.
Click to expand...
Click to collapse
Search a RUU for your phone. maybe that work

moonshine on stock ICS
Yes i m, flash RUU and after that, i try to unlock bootloader, but i can't , many time i try... After that, in software update find last update, and downloading, every ok, but can't install, variant system version-raport. Any solution?

Aleksic82 said:
Hi every one, greetings from Serbia!! I have couple problems on my Htc one s ville2. 1. Can't unlock relocked bootloader, i many time try, its finish every segment ok htcdev, cmd, token, bin code, mobile phone accept, i click yes on ulock htc screen on mobile and enter power buton, restart phone, and up system, every ok, but not unlocked in bootloader, stay relocked. Phone its s-on, my phone (ICS 4.0.4)find OTA update and download, but cant install update, Verification Failed. S-on its problematic? Why i can't unlocked bootloader, i want to install twpr and flash officiall (and root) OTA update on my Htc.
Click to expand...
Click to collapse
Here is the thread for Ville S4 dunno anything about C2 and I won't recommend you to flash or use any procedure from here unless it's stated that works for C2. You might risk bricking your device otherwise
Sent from nowhere over the air...

Ok, i understand that. I have one question for every one, can i install ota update on s-on, s-off its need or not? I have on my htc one s ville 2 s-on, i cant unlock bootloader, always relocked, many, many times i try, one_kit_v, or easy Unlock tools or direct on htcdev, always phone acept comand end always acept on screen yes unlock press power key, but stay relocked. In app get cid from gp, says htc__044-asia wwe, but in cmd fastboot getvar cid stay 11111, im confused, many question, but no answer, i hope so its riff jtag box not only solution on my phone. Thanks anyway!

I guess having S-On for Ville C2 means same thing...that is, you must flash kernel in fastboot mode after every ROM flash.
So you could use OTA but after installing OTA you have to go to fastboot and flash the kernel from that OTA. It also means you should open the OTA zip on your PC and extract it from there to have it at hand when needed
Sent from nowhere over the air...

Rapier said:
I guess having S-On for Ville C2 means same thing...that is, you must flash kernel in fastboot mode after every ROM flash.
So you could use OTA but after installing OTA you have to go to fastboot and flash the kernel from that OTA. It also means you should open the OTA zip on your PC and extract it from there to have it at hand when needed
Sent from nowhere over the air...
Click to expand...
Click to collapse
Thanks man.
Flash kernel after RUU exe ICS update? I can't OTA install, phone its find, download but cat't, verifact- variant system version, can't install. From recovery, recovery error flash zip, cant find update, i think this problem caused s-on.

Aleksic82 said:
Ok, i understand that. I have one question for every one, can i install ota update on s-on, s-off its need or not? I have on my htc one s ville 2 s-on, i cant unlock bootloader, always relocked, many, many times i try, one_kit_v, or easy Unlock tools or direct on htcdev, always phone acept comand end always acept on screen yes unlock press power key, but stay relocked. In app get cid from gp, says htc__044-asia wwe, but in cmd fastboot getvar cid stay 11111, im confused, many question, but no answer, i hope so its riff jtag box not only solution on my phone. Thanks anyway!
Click to expand...
Click to collapse
Aleksic82 said:
Ok, i understand that. I have one question for every one, can i install ota update on s-on, s-off its need or not? I have on my htc one s ville 2 s-on, i cant unlock bootloader, always relocked, many, many times i try, one_kit_v, or easy Unlock tools or direct on htcdev, always phone acept comand end always acept on screen yes unlock press power key, but stay relocked. In app get cid from gp, says htc__044-asia wwe, but in cmd fastboot getvar cid stay 11111, im confused, many question, but no answer, i hope so its riff jtag box not only solution on my phone. Thanks anyway!
Click to expand...
Click to collapse
1-. if you want to install another RUU different at you CID you need be a S-OFF and SuperCID.
2-. if you want to install .zip rom flashed from recovery you DONT need be a S-OFF, but, after flash a rom you need flash boot.mg from fastboot.
3-.The problem with unlock boot loader its very strange, i relock and unlock boot loader a lot of time and no problems.

Hey guys
I sincerely apologize in advance if this is wrong thread to post such question in. Please be so kind to redirect me to the right thread, I just got registered
Here's my problem. Couple of days ago my phone (HTC One S, villec2, S-ON, here's the picture from bootloader http://tinypic.com/r/qo87k6/8) started behaving somewhat out of the order. Every process that was there, everything started throwing out errors with the likes of Google play has stopped working, Music has stopped working, Messages has stopped working, nothing was the same as it was before that. And nothing else like cleaning the phone with some apps from Google Play didn't help. Therefore, I decided to install myself a custom ROM
Phone was already rooted two days after I got it. It was pretty straightforward process really. That was two years ago. I needed root acess to install some app that required root acess, don't ask me which app was this because I don't remember, honestly. It also installed TWRP 2.6.0.0 and SuperSU
I downloaded ROM (this one in particular http://www.android.gs/update-htc-one-s-to-android-5-1-1-lollipop-with-resurrection-remix-5-4-4-custom-rom/), followed instructions, got into TWRP and this is when the turd hit the fan. Instructions said that I need to wipe my phone. I did just that, with one exepction - I wiped everything from my phone. Spare me saying that I'm an idiot, I've got over that fact already
Basically, TWRP said that no OS is installed. Everything was wiped out from internal SD card aswell, including my ROM file that I put on the phone. I tried with mounting USB storage, which got me into the SD card on my PC and I've put ROM file on it again. So I tried flashing the ROM with TWRP but it kept telling me that my device is not supported to install this ROM
So I was stuck in bootloader with option to flash TWRP.img file from fastboot enviroment on PC, nothing more than that
I've tried at least 4 different ROM-s. One got installed on my phone but when I rebooted my device it got stuck on HTC logo screen and kept rebooting (boot loop I think it's called) until I manually got into bootloader with combination of power down+volume down button
So I started looking for solutions. I found out, that there's two different "flavours" of HTC One S. One is ville, the other one is villec2, which I have. I've read all about RUU files that can help me recover my phone but after searching through http://androidruu.com/?developer=VilleC2 I found nothing that can help me. I've downloaded two different RUU's, locked and unlocked bootloader twice, rebooted RUU but none of them was compatible with my phone
I've seen something about OTA manual updates, which I also tried but it didn't do anything. I've tried flashing firmware.zip that I got from OTA update file, flashed boot.img but then the phone got to the point where it should update but it kept showing me red triangle. The only option was, again, to boot it into bootloader and I was back at square one
Then I read something about turning your phone S-OFF with that moonshine software and about installing any RUU I want without complications. So I got one and realized that I can't do anything with it because my phone only boots in bootloader and as far as I understand, you need to run distiller.exe while the device is turned on and it has to be in Android OS. Which is not an option with me, because as I said, I can only boot my phone into bootloader and then boot something else via fastboot commands on my PC
Am I screwed here? I've tried literally every single thing, I've looked over dozens of recovery guides for this phone but none of them worked for me. I heard that I need exactly the same ROM (matching CID and everything) that was previously installed on the device. Thing is that I didn't do any backup of stock ROM before all that fiasco. I've tried this site too http://forum.xda-developers.com/showthread.php?t=2200930 but all links seem dead, because it only shows me some advertisement things and nothing else
I know I got myself in a situation where anyone with a bit more brain than me would use this bricked phone as a paperweight but I'm stubborn enough to try just about everything to revive my device. At this moment it's stuck in bootloop. I can't boot into recovery because it only keeps rebooting over and over and over again. Fastboot recognizes my device if I type fastboot devices into command prompt but that's just about it
So please, if somebody has the slightest idea what am I to do, tell me all about it because I've ran out of ideas and there's nothing more to my knowledge to try at this point. Thanks in advance!