Database Info

[Q] Can someone help me with this boot loop?

Good day ...
im having a problem with my desire s, i bought it 2 days ago with the same problem when i bought it, its already with the problem when i bought it..
it is priced low so i bought it from a guy being tempted thinking i could fix it or its just a software problem, but unfortunately i got no luck fixing it,
i can get it to bootloader (power+volume down) but i cant seem to enter the recovery from the menu and it is not charging. Tried flashing new recovery but still no luck tried installing RUU but i get an error 155 rom update utility cannot update your android phone.... The weird thing is when i try to charge the phone on wall, it enters CWM and i tried to format cache, do factory reset but theres an error unable to mount sd something like that... And my phone cant be detected using adb cause i think usb debugging is not enabled before it got bootloop, but with fastboot it can be detected...
Here is the detail of my phone:
UNLOCKED
SAGA PVT SHIP S-ON RL
HBOOT-2.00.002
RADIO-3822.10.08.04_M
eMMC-Boot
Aug 22 2011, 15:22:13
more details
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.405.6
(bootloader) serialno: SH14PTJ06464
(bootloader) imei: ******************
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3634mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Can someone tell me what RUU should i use..
THANKS IN ADVANCE GUYS :crying:

To run RUU you need to relock your bootloader.
Google and INDEX thread can tell you everything else.
(well, they could have saved me this post too, if you'd run a simple search for "error 155").

Jack_R1 said:
To run RUU you need to relock your bootloader.
Google and INDEX thread can tell you everything else.
(well, they could have saved me this post too, if you'd run a simple search for "error 155").
Click to expand...
Click to collapse
i have manage to install the ICS RUU, but sad to say still having a boot loop and still unable to go to recovery...
now i think the problem is with fired emmc chip? i hope its not :crying:
i cant seem to follow this guide http://forum.xda-developers.com/showthread.php?t=1284196 due to not able to detect my phone in adb commands.. is there a way for my phone to be detected in adb?? whenever i typed in adb shell i get an error:device not found
another noob question and im sorry for it, if i have a fried emmc chip, will i still be able to boot it in bootloader???

Patutz said:
but theres an error unable to mount sd something like that...
Click to expand...
Click to collapse
Sure you already tried another SD Card!?

Jericoacoara said:
Sure you already tried another SD Card!?
Click to expand...
Click to collapse
i dont think it pertains to the external sd, i think its on internal... well can u tell me how can my computer detect my device via adb??.. im thinking about the fried emmc.. but cant seem to know if its with the emmc issue since my device cant be detected via adb...

Patutz said:
i dont think it pertains to the external sd, i think its on internal... well can u tell me how can my computer detect my device via adb??.. im thinking about the fried emmc.. but cant seem to know if its with the emmc issue since my device cant be detected via adb...
Click to expand...
Click to collapse
If you are stuck into boot loop you can follow this guide http://forum.xda-developers.com/showpost.php?p=21569470&postcount=957 to get logcat information...

TheLegendGZ said:
If you are stuck into boot loop you can follow this guide http://forum.xda-developers.com/showpost.php?p=21569470&postcount=957 to get logcat information...
Click to expand...
Click to collapse
the problem is whenever i type adb devices i get an error no device =(

Patutz said:
the problem is whenever i type adb devices i get an error no device =(
Click to expand...
Click to collapse
First you made a mistake to flash the ICS RUU, because you could have easily check the eMMC from CWM via adb. Now you cannot.
At your current state you can go into the Recovery by choosing it from the bootloader menu, pressing Volume UP + Power when you see a black screen with an exclamation mark. But there is nothing you can do there...
And finally - since your RUU flash was successful and you still cannot boot to the OS the conclusion is obvious - you have wasted your money. Sorry about that

amidabuddha said:
First you made a mistake to flash the ICS RUU, because you could have easily check the eMMC from CWM via adb. Now you cannot.
At your current state you can go into the Recovery by choosing it from the bootloader menu, pressing Volume UP + Power when you see a black screen with an exclamation mark. But there is nothing you can do there...
And finally - since your RUU flash was successful and you still cannot boot to the OS the conclusion is obvious - you have wasted your money. Sorry about that
Click to expand...
Click to collapse
i cant enter recovery from the very beginning, i tried volume up + power but i cant see a black screen with exclamation mark..cant i flash gingerbread RUU anymore to downgrade it?
so i do have fried eMMc? :crying:

You might not have ADB drivers properly installed. If you managed to install RUU, it means your USB port is working and eMMC is likely functional.
Enter the bootloader (Power+VolDown).
Select "RECOVERY" by VolDown/VolUp and press Power.
This should get you to recovery.

Jack_R1 said:
You might not have ADB drivers properly installed. If you managed to install RUU, it means your USB port is working and eMMC is likely functional.
Enter the bootloader (Power+VolDown).
Select "RECOVERY" by VolDown/VolUp and press Power.
This should get you to recovery.
Click to expand...
Click to collapse
i cant enter recovery i tried power+voldown then i select RECOVERY.
but it just go to HTC logo colored green and white background, then after that it shut off, it doesnt go to recovery...and regarding the adb, i try in cmd to type adb then i get all the menu of adb, so i think the adb is installed properly?? by the way, are adb drivers the one included on this link? http://forum.xda-developers.com/showthread.php?t=1272595 i just put the extracted zip file on C drive and i didnt do "setx path /m "%PATH%;C:\android-tools" this command i just type in cmd cd C:\android-tools am i doin it wrong?

Patutz said:
i cant enter recovery i tried power+voldown then i select RECOVERY.
but it just go to HTC logo colored green and white background, then after that it shut off, it doesnt go to recovery...and regarding the adb, i try in cmd to type adb then i get all the menu of adb, so i think the adb is installed properly?? by the way, are adb drivers the one included on this link? http://forum.xda-developers.com/showthread.php?t=1272595 i just put the extracted zip file on C drive and i didnt do "setx path /m "%PATH%;C:\android-tools" this command i just type in cmd cd C:\android-tools am i doin it wrong?
Click to expand...
Click to collapse
You are not doing anything wrong.
The device can be detected by ADB only in a Custom Recovery or a fully booted OS with enabled USB debugging.
It cannot work in a bootloader, Stock Recovery or a bootloop with a secured (Stock) kernel.
The FASBOOT executable works in the bootloader in a "FASTBOOT USB" mode, but there is not much you can do with it, especially with the Stock hboot.
But what Jack_R1 said makes me wonder about your RUU flash. Are you completely sure that it went without errors? Because this cannot happen if your /system or /data partition is corrupted (so called fried eMMC). Moreover if it went fine the Stock recovery should be there and accessible.

amidabuddha said:
You are not doing anything wrong.
The device can be detected by ADB only in a Custom Recovery or a fully booted OS with enabled USB debugging.
It cannot work in a bootloader, Stock Recovery or a bootloop with a secured (Stock) kernel.
The FASBOOT executable works in the bootloader in a "FASTBOOT USB" mode, but there is not much you can do with it, especially with the Stock hboot.
But what Jack_R1 said makes me wonder about your RUU flash. Are you completely sure that it went without errors? Because this cannot happen if your /system or /data partition is corrupted (so called fried eMMC). Moreover if it went fine the Stock recovery should be there and accessible.
Click to expand...
Click to collapse
i tried installing the 4ext recovery and i flashed it ok but still cant get to recovery...i cant access adb since it wont be detected by the computer and i cant s-off my phone since i need to adb push...
yeah im sure that it went smooth, no errors at all, after the installation on RUU its says congratulation upgrade complete you can now use your device something like that haha not sure whats the exact words used there haha wait im goin to RUU again just to be sure that theres no error :fingers-crossed:
Here's the exact thing written on RUU... Congratulations! Your ROM update has been completed. Your Android phone is now ready for use..
hmm do you think even with that notice i can still get error during the update??? and by the way is it normal around 17% during the RUU installation after the "updating radio" around 17% it reboots then on the RUU it says waiting for device, is it normal?

amidabuddha said:
You are not doing anything wrong.
The device can be detected by ADB only in a Custom Recovery or a fully booted OS with enabled USB debugging.
It cannot work in a bootloader, Stock Recovery or a bootloop with a secured (Stock) kernel.
The FASBOOT executable works in the bootloader in a "FASTBOOT USB" mode, but there is not much you can do with it, especially with the Stock hboot.
But what Jack_R1 said makes me wonder about your RUU flash. Are you completely sure that it went without errors? Because this cannot happen if your /system or /data partition is corrupted (so called fried eMMC). Moreover if it went fine the Stock recovery should be there and accessible.
Click to expand...
Click to collapse
i have a great news for me hehe i hope so, i made some new findings on my device,
1st of all i made it to the recovery but the wierd thing is i can only go to recovery when i plugged my phone on the computer, now adb can detect my phone
2nd by following this guide http://forum.xda-developers.com/showthread.php?t=1284196&nocache=1 for the checking of Fried eMMc, i was able to get this result:
<3>[ 7.996978] mmc0: No card detect facilities available
<6>[ 7.997589] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.997741] mmc0: Platform slot type: MMC
<6>[ 7.997985] mmc0: 4 bit data mode disabled
<6>[ 7.998107] mmc0: 8 bit data mode enabled
<6>[ 7.998260] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.998504] mmc0: Slot eject status = 0
<6>[ 7.998626] mmc0: Power save feature enable = 1
<6>[ 7.998870] mmc0: DM non-cached buffer at ff817000, dma_addr 0x29be3000
<6>[ 7.998992] mmc0: DM cmd busaddr 0x29be3000, cmdptr busaddr 0x29be3300
<6>[ 8.151794] mmc0: new high speed MMC card at address 0001
<6>[ 8.152832] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
from the result up there i dont think i got a fried emmc? or maybe i maybe wrong? please enlighten me guys i think its a good find? maybe again im wrong? so what do you think is the problem here that my htc got boot looped??

Patutz said:
i
from the result up there i dont think i got a fried emmc? or maybe i maybe wrong? please enlighten me guys i think its a good find? maybe again im wrong? so what do you think is the problem here that my htc got boot looped??
Click to expand...
Click to collapse
Something is very wrong here. And I think that your lack of understanding is a reason for the crappy explanation you are giving here.
You have a custom recovery. How come?

Charge/change your battery, see if anything changes.
amidabuddha said:
Something is very wrong here. And I think that your lack of understanding is a reason for the crappy explanation you are giving here.
You have a custom recovery. How come?
Click to expand...
Click to collapse
His RUU flash obviously didn't work. Not even sure what he's flashing.

amidabuddha said:
Something is very wrong here. And I think that your lack of understanding is a reason for the crappy explanation you are giving here.
You have a custom recovery. How come?
Click to expand...
Click to collapse
i flashed this one http://forum.xda-developers.com/showthread.php?t=1484753 thats how i get the recovery , sorry for the explanations im just being excited hoping id still get a chance to fix this phone
Jack_R1 said:
Charge/change your battery, see if anything changes.
His RUU flash obviously didn't work. Not even sure what he's flashing.
Click to expand...
Click to collapse
im flashing this RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed got it from htcdev... ican i downgrade to gingerbread? can u tell me which RUU should i use?

I'm not as knowledgeable as people helping you here, but if it was me is start from scratch and i mean from scratch. Fresh install of everything, drivers etc. I'd then flash a custom rom and seeing as your not s-off. Flash the kernel. Then if its ok is maybe try a fresh download of the ruu and run that.
"Do, or do not. There is no 'try'."
- Yoda

Patutz said:
im flashing this RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed got it from htcdev... ican i downgrade to gingerbread? can u tell me which RUU should i use?
Click to expand...
Click to collapse
You can downgrade, but not by a simple RUU flash.
RUU flash doesn't work when bootloader is unlocked.
I'm tired. Read instead of asking.

jugg1es said:
I'm not as knowledgeable as people helping you here, but if it was me is start from scratch and i mean from scratch. Fresh install of everything, drivers etc. I'd then flash a custom rom and seeing as your not s-off. Flash the kernel. Then if its ok is maybe try a fresh download of the ruu and run that.
"Do, or do not. There is no 'try'."
- Yoda
Click to expand...
Click to collapse
can i use any ics kernel??... the bad news is that not whenever i try the same method yesterday when i can enter recovery by putting my phone on pc, now it just loop on recovery when i plugged it in computer, it just enter recovery then shut it self then enter recovery again..
Jack_R1 said:
You can downgrade, but not by a simple RUU flash.
RUU flash doesn't work when bootloader is unlocked.
I'm tired. Read instead of asking.
Click to expand...
Click to collapse
i relocked my bootloader whenever i flash RUU but i get error that its not the right RUU, the only one that i got success in flashing RUU was the one iposted abaove... thats why im asking you guys if you know any compatible RUU for my device cause ive tried alot and still get incompatability

[Q] Cant connect to computer

I cannot access the SD card from recovery. I have had this issue before, and know that I have to flash the stock rom to fix. The problem is that when I tried to do it, my computer can never find my phone. When I boot it into bootloader, I hear my computer make the sound that a portable storage device was not able to be connected (three short beeps instead of two for a success connection). I can go back into the screen that shows recovery, factory reset, clear storage, etc, and none of these options seem to be helping. I can get into recovery, if that helps. Could someone tell me how to get my phone to connect with my computer so I can flash the stock rom to save me?

connect your phone to the computer, put any rom you want to flash in your rootfolder where you have fastboot etc.,start cmd in it and push the rom via "adb push 'romname'.zip /sdcard" to your sdcard. this will take a few minutes, but the rom should be on your sdcard.
Sent from my HTC One S using xda app-developers app

tried this, I couldnt get fastboot usb to come up. i tried it on my laptop and got it. I am downloading a stock RUU and will try to install. The one i had previously didn't work. Will update.

OK, so after I connected to a different computer I got fastboot working. After trying to install 3 RUUs to get it back to stock and at least usable again, I get Error 155 the the installation had an error and said i need to find the correct RUU. When I get into HBOOT, here is my information:
INFOversion: 0.5
INFOversion-bootloader: 1.06.0000
INFOversion-baseband: 0.15.31501S.02
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOserialno:
INFOimei:
INFOproduct: vle
INFOplatform: HBOOT-8960
INFOmodelid: PJ4010000
INFOcidnum: T-MOB010
INFObattery-status: good
INFObattery-voltage: 4177mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 802fa374
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
VLE PVT SHIP S-ON RL
OpenDSP-v23.1.0.32.0323
I have a TMOUS One S.
I have tried the
RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed
and
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2
RUUs and still cannot get past this error.
I am wondering if the problem is using the command prompt and using the fastboot oem lock command before flashing. I have tried this, but don't believe I am doing it correctly.
Could someone please help me?
Upate: got it back to stock. the fastboot oem lock did the trick

Here is a full guide: http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
I looks like your using the right RUU.
Did you run the RUU as an administrator?
Sorry didn't see your update.

What does it take to get back to the point where I can have a custom rom? I know I need to put a recovery back on, but do i need to unlock that fastboot oem lock command?
After I get a recovery on there I know what to do, I am just not sure what exactly got reset after flashing the RUU.

[Q] HTC One S Bootloop; S-On - Can't flash RUU recovery.img

Phone Details
HTC One S TMobile
****Tampered****
****Unlocked*****
VLE PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Cidnum: T-MOB010
My phone sustained water damage (unfortunate accident of a leaking wall aircondition unit while on vacation). Anyways- once things dried out- everything turns on and seems to work, but I'm stuck in a boot loop. It bootloops through the cyanogenmod loading screen then over again. I can still get to bootloader and TWRP 2.5.0.0.
I have tried the following.
-reinstall the CM10 ROM from TWRP and flash the boot.img in fastboot but same bootloop occurs.
-re-lock the bootloader to use a RUU.exe but everytime I use the 'fastboot oem lock' command the screen turns off. When I reboot into bootloader, I'm still unlocked. I've copied the command window below-
.5\data>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.946s
-ADB Sideload a new ROM- but in TWRP the drivers fail to install and my computer doesn't recognize any devices for adb commands. I've tried re-flashing TWRP and the drivers using Hasoon's Toolkit in hopes that it would
-I have also looked for a way to get my phone S-off since I think that is one of the problems preventing these other steps. But I can't seem to find any steps for that.
Anyways, hopefully I was at least on the right track with one of those steps. I am definitely a noob- but I've tried looking through forums and tutorials and videos for hours. I'm hoping someone can give me a good step by step solution to try. Thanks in advance for any help.

Let's Tackle This..
Alright, First step. Let's get the drivers.
(If you have HTC Sync on your PC, remove it now)
Install this for the drivers on your PC
Restart both your PC and phone, and if you dont have adb (Or want to use the newest one)
Install this for the minimal adb and fastboot program. It's a lot more convenient then seperate files.
Tell me if you're able to do ADB commands after this .

Mozziliac said:
Alright, First step. Let's get the drivers.
(If you have HTC Sync on your PC, remove it now)
Install this for the drivers on your PC
Restart both your PC and phone, and if you dont have adb (Or want to use the newest one)
Install this for the minimal adb and fastboot program. It's a lot more convenient then seperate files.
Tell me if you're able to do ADB commands after this .
Click to expand...
Click to collapse
I'm not as familiar with ADB commands in general. But I did what you said and tried "adb devices" in TWRP, TWRP while adb sideload scrip was trying to run on my phone, in hboot, and in fastboot and none of them seemed to work. Fastboot commands still work in fastboot mode. I sort of predicted that when the device drivers failed to load again when I entered recovery mode.

drpaul85 said:
I'm not as familiar with ADB commands in general. But I did what you said and tried "adb devices" in TWRP, TWRP while adb sideload scrip was trying to run on my phone, in hboot, and in fastboot and none of them seemed to work. Fastboot commands still work in fastboot mode. I sort of predicted that when the device drivers failed to load again when I entered recovery mode.
Click to expand...
Click to collapse
Looks like your on a old enough firmware for you to mount your SD in recovery so just download stock ROM and flash it
Also you got the error from not flashing stock recovery

ville
why my one s usually have some reboot????????
---------- Post added at 07:06 PM ---------- Previous post was at 06:27 PM ----------
why my one s usually have some reboot????????

Easy trick to S-OFF for those who have TMOBO10 and HBoot 2.15

Hi everyone, I am fairly new to doing all this, but for last three days or so, I've been really frustrated due to not getting S-OFF on my HTC one s ville. I want to run Sense 6 ROM by Liberty, but was having lot of problems, so someone suggested I try to get S-OFF. I tried rumrunner like 5 times, but failed. Tried installing other ROMs and did it again, still failed, but this what did it.
1) FIRST, flash the following ROM (CM11S_ville_2.15_v3.1_kk-final, from this link http://forum.xda-developers.com/htc-one-s/development/rom-oneplus-one-stock-rom-cm11s-one-s-t2869703), it has its own Kernel, so just flash the boot.img as usual and flash the ROM.
2) Now go ahead and restart your phone and activate the debugging, etc. Also make sure SuperSu is in there, if not, then go ahead flash that again, then restart your phone and open the app to activate it.
3)HERE IS THE KEY NOW --> CHANGE YOUR KERNEL TO THIS --> bubba_kernel-2014-07-26_Ville (get it from http://forum.xda-developers.com/showthread.php?t=2134535). Download it from Post# 2 at the bottom under Donate and FOLLOW THE INSTRUCTIONS FROM POST #4
4), go ahead and let the phone turn on. Make sure SuperSu is still there and activated. Also set screen timeout to maximum, so it doesn't go blank on you, DEACTIVATE all screen locks as well.
4) Make sure all your drivers are up to date (FOLLOW all the instructions on http://rumrunner.us/instructions/)
5) Tip --> Follow this video step by step --> https://www.youtube.com/watch?v=NeFwsqU4YL4 (key is to make a separate folder which has rumrunner and drivers together).
6) Run the rumrunner and don't forget to disable your antivirus software and firewell in your computer.
Here is the video guide on how to flash any ROM if you have S-ON --> https://www.youtube.com/watch?v=qNR84FST1KQ&channel=kinglightboy
I am sure this will simply get you S-OFF easily.
It just needs an "unsecure kernel" and this one does the job .
Here is all the other info of my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.531.19
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3973mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

anyone else try this out yet? I am going to be trying later on today.

sjorge3442 said:
anyone else try this out yet? I am going to be trying later on today.
Click to expand...
Click to collapse
please let me and others know if it worked or not. It most likely should as long as you do everything correctly.

nikunrp said:
Hi everyone, I am fairly new to doing all this, but for last three days or so, I've been really frustrated due to not getting S-OFF on my HTC one s ville. I want to run Sense 6 ROM by Liberty, but was having lot of problems, so someone suggested I try to get S-OFF. I tried rumrunner like 5 times, but failed. Tried installing other ROMs and did it again, still failed, but this what did it.
1) FIRST, flash the following ROM (CM11S_ville_2.15_v3.1_kk-final, from this link http://forum.xda-developers.com/htc-one-s/development/rom-oneplus-one-stock-rom-cm11s-one-s-t2869703), it has its own Kernel, so just flash the boot.img as usual and flash the ROM.
2) Now go ahead and restart your phone and activate the debugging, etc. Also make sure SuperSu is in there, if not, then go ahead flash that again, then restart your phone and open the app to activate it.
3)HERE IS THE KEY NOW --> CHANGE YOUR KERNEL TO THIS --> bubba_kernel-2014-07-26_Ville (get it from http://forum.xda-developers.com/showthread.php?t=2134535). Download it from Post# 2 at the bottom under Donate and FOLLOW THE INSTRUCTIONS FROM POST #4
4), go ahead and let the phone turn on. Make sure SuperSu is still there and activated. Also set screen timeout to maximum, so it doesn't go blank on you, DEACTIVATE all screen locks as well.
4) Make sure all your drivers are up to date (FOLLOW all the instructions on http://rumrunner.us/instructions/)
5) Tip --> Follow this video step by step --> https://www.youtube.com/watch?v=NeFwsqU4YL4 (key is to make a separate folder which has rumrunner and drivers together).
6) Run the rumrunner and don't forget to disable your antivirus software and firewell in your computer.
Here is the video guide on how to flash any ROM if you have S-ON --> https://www.youtube.com/watch?v=qNR84FST1KQ&channel=kinglightboy
I am sure this will simply get you S-OFF easily.
It just needs an "unsecure kernel" and this one does the job .
Here is all the other info of my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.531.19
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3973mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
So I have installed the rom but I am confused on the part of installing the kernel. With my m7, all I do is flash it in recovery. THis whole, adb through twrp is confusing to me. How do I pull the boot image from twrp after I flash the kernel? Currently, I have not tried flashing the kernel, since I cannot figure out how to do adb commands through twrp. Any suggestions? When I go to ADB Sideload, all it does is says connecting to adb sideload, yet it never connects. I am on TWRP 2.7.1.2
adb pull /tmp/newboot.img
adb reboot-bootloader
fastboot flash boot newboot.img
fastboot reboot
---------- Post added at 08:12 PM ---------- Previous post was at 07:47 PM ----------
I just had the brilliant idea to see if my HTC one M7 would connect via sideload. It did not. I believe I am having a driver issue. I am in the process of redoing all my drivers now. On the plus side, that OnePlusOne rom is actually pretty sweet and snappy.

sjorge3442 said:
So I have installed the rom but I am confused on the part of installing the kernel. With my m7, all I do is flash it in recovery. THis whole, adb through twrp is confusing to me. How do I pull the boot image from twrp after I flash the kernel? Currently, I have not tried flashing the kernel, since I cannot figure out how to do adb commands through twrp. Any suggestions? When I go to ADB Sideload, all it does is says connecting to adb sideload, yet it never connects. I am on TWRP 2.7.1.2
adb pull /tmp/newboot.img
adb reboot-bootloader
fastboot flash boot newboot.img
fastboot reboot
---------- Post added at 08:12 PM ---------- Previous post was at 07:47 PM ----------
I just had the brilliant idea to see if my HTC one M7 would connect via sideload. It did not. I believe I am having a driver issue. I am in the process of redoing all my drivers now. On the plus side, that OnePlusOne rom is actually pretty sweet and snappy.
Click to expand...
Click to collapse
Hey, go to control panel --> then programs and features --> search (via search box on the top) HTC --> any drivers that show up, uninstall them completely.
Now go ahead and download HTC Sync from online. Once it is downloaded, uninstall it (this will download drivers for HTC, but uninstalling will only get rid of programs and NOT the drivers. Now go ahead and search in C drive "adb" and then "fastboot" and delete anything that's there. Restart the computer
Now, make sure you have these 4 files in C drive (if you don't have them, PM me your email address and I will send it to you).
1. adb.exe
2. AdbWinApi.dll
3. AdbWinUsbApi.dll
4. fastboot.exe
Once you put these files in C drive, then anytime you open command prompt and type in these commands for HTC, it will work perfectly without you changing the location.
Now connect your HTC device to computer, open the command prompt (once it's done with driver installation) and type in this: adb devices and press enter. You should see HTC with numbers and it should say attached. If it is, you are set. If it's not, something is interfering.
Make sure you have the latest TWRP as well. When you have to flash the kernel, first put that zip file in your phone, then go in recovery mode and flash it (install--> and click on the kernel file, no need to wipe data or anything). Once it's done flashing, don't press anything and Open the command prompt and type in the commands it says. This will flash the kernel automatically and you don't have to do anything. Once it's done, follow the commands that I wrote.

nikunrp said:
Hey, go to control panel --> then programs and features --> search (via search box on the top) HTC --> any drivers that show up, uninstall them completely.
Now go ahead and download HTC Sync from online. Once it is downloaded, uninstall it (this will download drivers for HTC, but uninstalling will only get rid of programs and NOT the drivers. Now go ahead and search in C drive "adb" and then "fastboot" and delete anything that's there. Restart the computer
Now, make sure you have these 4 files in C drive (if you don't have them, PM me your email address and I will send it to you).
1. adb.exe
2. AdbWinApi.dll
3. AdbWinUsbApi.dll
4. fastboot.exe
Once you put these files in C drive, then anytime you open command prompt and type in these commands for HTC, it will work perfectly without you changing the location.
Now connect your HTC device to computer, open the command prompt (once it's done with driver installation) and type in this: adb devices and press enter. You should see HTC with numbers and it should say attached. If it is, you are set. If it's not, something is interfering.
Make sure you have the latest TWRP as well. When you have to flash the kernel, first put that zip file in your phone, then go in recovery mode and flash it (install--> and click on the kernel file, no need to wipe data or anything). Once it's done flashing, don't press anything and Open the command prompt and type in the commands it says. This will flash the kernel automatically and you don't have to do anything. Once it's done, follow the commands that I wrote.
Click to expand...
Click to collapse
I did everything that you said to and I put those 4 files on my C directory (I had them saved my on m7) and I still cannot utilized adb sideload. It doesn't recognize any device when I search for adb devices after or before I flash the bubba kernel.

sjorge3442 said:
I did everything that you said to and I put those 4 files on my C directory (I had them saved my on m7) and I still cannot utilized adb sideload. It doesn't recognize any device when I search for adb devices after or before I flash the bubba kernel.
Click to expand...
Click to collapse
why are you using sideload? your phone doesn't boot up? if it does. There is definitely driver problem and computer.
First check this video and see if you have the latest driver --> https://www.youtube.com/watch?v=ltR2uQJxNRw
If it's old version, delete the driver and install the latest one. I had that problem and did so many different things so solve, but then I found this video and realized that the driver was old.

nikunrp said:
why are you using sideload? your phone doesn't boot up? if it does. There is definitely driver problem and computer.
First check this video and see if you have the latest driver --> https://www.youtube.com/watch?v=ltR2uQJxNRw
If it's old version, delete the driver and install the latest one. I had that problem and did so many different things so solve, but then I found this video and realized that the driver was old.
Click to expand...
Click to collapse
Im not trying to use sideload. I also have full access to ADB when the phone is booted up. Its just when the phone is in recovery that I cannot push any commands.
Heres what I do.
I flash the bubba kernel zip via TWRP (Whichever version the OnePlusOne rom says to use).
Then, without touching anything, I try to run the adb commands listed in Post #4, which pulls the boot img.
^^^This does not work. The phone doesnt recognize the commands.

before sending any command, when you type "adb devices", does the device show up?

sjorge3442 said:
Im not trying to use sideload. I also have full access to ADB when the phone is booted up. Its just when the phone is in recovery that I cannot push any commands.
Heres what I do.
I flash the bubba kernel zip via TWRP (Whichever version the OnePlusOne rom says to use).
Then, without touching anything, I try to run the adb commands listed in Post #4, which pulls the boot img.
^^^This does not work. The phone doesnt recognize the commands.
Click to expand...
Click to collapse
before sending any command, when you type "adb devices", does the device show up?
When you say phone boots up, can check the phone (settings --> about phone) if it already installed this new kernel, if it did, then run rum-runner software and see if it gets you S-off. If not, then I'd fix these drivers issue, then re-install CM rom and Bubba kernel and run rum-runner again.

sjorge3442 said:
Im not trying to use sideload. I also have full access to ADB when the phone is booted up. Its just when the phone is in recovery that I cannot push any commands.
Heres what I do.
I flash the bubba kernel zip via TWRP (Whichever version the OnePlusOne rom says to use).
Then, without touching anything, I try to run the adb commands listed in Post #4, which pulls the boot img.
^^^This does not work. The phone doesnt recognize the commands.
Click to expand...
Click to collapse
I have HTC one S ville, i thought you are getting s-off on that. I am not sure how kernel thing will work on M7

nikunrp said:
before sending any command, when you type "adb devices", does the device show up?
When you say phone boots up, can check the phone (settings --> about phone) if it already installed this new kernel, if it did, then run rum-runner software and see if it gets you S-off. If not, then I'd fix these drivers issue, then re-install CM rom and Bubba kernel and run rum-runner again.
Click to expand...
Click to collapse
When i flash the kernel, and check the version while the phone is booted, it still is listed at the cm based kernel. With the phone up and running, my ADB drivers recognize it fine. Its when the phone is in recovery that I cannot read adb. Neither the S or my M7 are read while in recovery from ADB.

sjorge3442 said:
When i flash the kernel, and check the version while the phone is booted, it still is listed at the cm based kernel. With the phone up and running, my ADB drivers recognize it fine. Its when the phone is in recovery that I cannot read adb. Neither the S or my M7 are read while in recovery from ADB.
Click to expand...
Click to collapse
i would still uninstall all the HTC related drivers and everything. Then again download HTC sync and then uninstall it. Then again make sure you have the right "tools" installed (those 4 files) and try it then and see how that goes. I had to do that like several times to finally make it work.

sjorge3442 said:
When i flash the kernel, and check the version while the phone is booted, it still is listed at the cm based kernel. With the phone up and running, my ADB drivers recognize it fine. Its when the phone is in recovery that I cannot read adb. Neither the S or my M7 are read while in recovery from ADB.
Click to expand...
Click to collapse
found this interesting video, which is similar to your situation, so might want to try it out and see what happens.
https://www.youtube.com/watch?v=Z8mheIkQ-1o&ab_channel=DanPasanen
Also what I have noticed that different data cables worked differently. Just right now, I tried using one of the USB cables, and it doesn't work, while it works on the other USB cable. So try switching cables.

sjorge3442 said:
anyone else try this out yet? I am going to be trying later on today.
Click to expand...
Click to collapse
In December I went S-OFF (to go super CID) using rumrunner. I was HBOOT 2.15 using CM12. (I was also TMOBO10). It didn't work. It seemed the SELinux was causing problems. I reverted to the CM10 ROM that I had been using. I clean installed and didn't bother with gapps. After that, rumrunner worked just fine. I ran it off of my Ubuntu box.
Either flash a kernel, or ROM with a suitable kernel. I knew my CM10 would get me where I wanted to go, and it seemed tiresome to root through all the descriptions to find a kernel.

Tried other ways 100 times, only this worked. thanks!

Um... Just use this?
http://moonshine.io/instructions.html

worked for me,I couldn't get it to super cid for some reason so I said **** it and just s offed. Rum runner worked after 2 trys so don't quit if it doesn't work the first try.

HTC One S ville c2 - NEED Help

So guys, i've got my HTC One S ville c2 ( S-ON, hboot 2.09 ) and i somehow soft-bricked it. I found the RUU for me but it's stuck at sending every time, in any USB port. I tried before to flash a custom rom, actually i tried to flash like 6 custom roms unfortunatelly it didn't work. An by didn't work i mean i was able to install the soft with no errors but when i restarted the phone, it was frozen at logo. I flashed boot.img so it's not that. I really don't know what else i could do. I think my phone does not support any custom rom. I am able to get to recovery and bootloader so any help would be greatly apreciated. At this very moment i'm watching my phone's screen and it has the grey HTC simple logo because i am giving the RUU another shot. Probably it won't work, as always. Thank in advance !!!

Relock your bootloader and try the RUU for you specify CID. I recomend use a Windows 7 pc and usb 2.0

JavierG123 said:
Relock your bootloader and try the RUU for you specify CID. I recomend use a Windows 7 pc and usb 2.0
Click to expand...
Click to collapse
i tried to flash the ruu but it just stays on sending 4ever. i used usb 2.0 and the version of the Ruu is corect. i check it before with fastboot getvar all. I just can't understand what's the problem. The checking is all fine but it just doesn't send the damn package to the phone. If someone could give me a working ROM for
"version: 0.5
version-bootloader: 2.09.0001
version-baseband: 16.05.20.16_M2
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT25NW410827
imei: 352762050257350
product: villec2
platform: HBOOT-8260
modelid: PJ4020000
cidnum: HTC__032
battery-status: good
battery-voltage: 3664mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0"
that would be great ...

Your pc recognize the phone in fastboot mode?

JavierG123 said:
Your pc recognize the phone in fastboot mode?
Click to expand...
Click to collapse
yes i said it can. otherwise how could i run "fastboot getvar all" ? anyway i managed to update the hboot version to 2.11.000. Now everything seems diferent. Even the well-know htc red message from boot "this build is for development purpuses only ... bla bla" has the row-spacing way smaller and when i enter recovery there is a message at the logo in the upper part "Entering recovery..." Maybe i am able to install some CM but i still have the flash the boot.img trough fastboot because i am S-ON.

JavierG123 said:
Your pc recognize the phone in fastboot mode?
Click to expand...
Click to collapse
ok. so i flash a CM 10.1 everything went fine. I flashed the boot.img from the zip and when i restart the phone It boots and instead of logo animation is just shows random green or red strips. What's going on?

Well... You should try search the SaM Rom thread, in this Forum (One S C2 develpment) install his recovery and his rom. Its based on stock rom
---------- Post added at 03:16 PM ---------- Previous post was at 03:09 PM ----------
@juganarucaliner steps to use a ruu
1)plug your phone to the PC and set it to charge only.
2)go to settings>applications>development>check USB Debugging.
3)go to settings>power>uncheck "fastboot".
4)remove your phone from the USB (charge).
5)hold the power button and shutdown your phone.
6)hold volume down button and hold down the power button,a white screen with options should appear.
7)select the first option (fastboot).
8)when in fastboot plug your USB cable into the phone and PC,you should see "fastboot USB".
9) now move to your PC and start the RUU setup,proceed normally with the wizard and hopefully the setup will run successfully.
note:do not run htc sync while updating,simply go to the HTC website and download the latest HTC sync,install it and make sure it installs the drivers and then shut it down.

JavierG123 said:
Well... You should try search the SaM Rom thread, in this Forum (One S C2 develpment) install his recovery and his rom. Its based on stock rom
Click to expand...
Click to collapse
I managed to install with aroma etc etc and then i flashed the boot.img inside /kernel/one s c2 but i am still stuck at logo. :crying::crying:

juganarucaliner said:
I managed to install with aroma etc etc and then i flashed the boot.img inside /kernel/one s c2 but i am still stuck at logo. :crying::crying:
Click to expand...
Click to collapse
So finally i was able to flash RUU from http://androidruu.com/index.php?developer=VilleC2
Follow these steps if you run into the problem i had:
1. install the ADB files. I had them before but it seems like they were corrupt or something. I am running Windows 10 now so for who is trying to do this on Windows 8, 8.1, 10 make sure you have the registry fix that can be found here http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337.
2. After you have succesfully managed to install all of this give the PC a restart
3. Try to flash the RUU for your device
4. After it completes unlock the bootloader and flash your recovery
5. Now you can update your firmware from 2.11 to 3.01 by following this guide here http://forum.xda-developers.com/showthread.php?t=2234559
6. Now it's your time to shine! Choose whatever Rom you want. but just don't forget to flash the boot.img after installation.
:fingers-crossed::fingers-crossed:Happy flashing !