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

[GUIDE] How To Root HTC One XL Firmware 5.05.707.1 Android 4.2.2

Welcome to my noob-proof guide on how to root HTC One XL!!!​
EDIT: Guide not available for AT&T Phones (Special thanks to timmaaa)
I WILL NOT TAKE RESPONSIBILITY IF YOUR PHONE IS BRICKED AFTER USING MY GUIDE, USE IT AT YOUR OWN RISK!!!
I will now slowly guide you through the steps to root your One XL
Step 1 : Unlock your Bootloader
Unlock your bootloader through HTCdev.com. Create an account and go to Unlock Bootloader, select All Other Supported Models and follow the instructions. To check if your bootloader is unlocked, enter bootloader mode by holding the Volume Down button while your phone is powering onIf your bootloader is unlocked, it should say *UNLOCKED* at the top right of the screen.
Step 2 : Flash A Custom Recovery
Download a custom recovery (TWRP and CWM are the two main ones)
For TWRP, download version 2.6.3.0 (i'm not sure about CWM, i didnt use it)
Enter bootloader mode and go to fastboot (Volume Up / Down to move around, Power button to select option)
Plug it into your PC/Desktop through USB and it should say "Fastboot USB" highlighted in red on your screen
Go to your Command Prompt (Start > Search Command Prompt)
Type in the following code:
fastboot flash recovery RECOVERYIMG.img
REPLACE RECOVERYIMG TO THE NAME OF YOUR RECOVERY (YOU MAY RENAME IT)
Fastboot will flash the image and give you a success/failure notification.
If it is successful, use the command fastboot erase cache to wipe your cache/dalvik
To check out the new recovery image, go back to Hboot menu by selecting bootloader and clicking the power button,
Use volume down to highlight recovery and press the power button. The phone will now attempt to boot into the new recovery image. You'll see the htc splash screen briefly and then the recovery image.
Step 3 : Rooting
For TWRP click reboot and then click system. It will tell you that your device hasnt yet been rooted and needs to install SuperSU to do so. Swipe to install the SuperSU.apk
For CWM i'm afraid I can't help you with that, sorry im not sure how to install SuperSU using CWM but you can ask around
If you have followed these steps correctly, your device should now have full root access!!! Download the Root Checker app to find out if your device is rooted or not.
If you're satisfied with this guide, don't hesitate to click the thanks button!!!

This guide isn't complete, this will not work for at&t phones. At&t phones cannot unlock via htcdev as the at&t CID is blocked. Maybe you could just update the title to note that this is a guide for non at&t phones.
Also, after flashing the recovery you also need to give the following fastboot command:
Code:
fastboot erase cache
Another thing you might want to put in there is that the user will need to have a working adb/fastboot environment and HTC drivers installed, and instructions on how to do so.
Sent from my Evita

If a person is truly a noob, they will have no idea what fastboot is, and not have a fastboot environment ready to go. This is a huge missing step(s).
Need links to thing, like TWRP and fastboot resources (once added).
Really, I hate to say, this isn't much of a guide in its present form. It basically says "Go to htcdev.com and follow the steps, then install TWRP". If a person can't handle those things, they shouldn't be modding their phone. This guide needs a lot more work, to be really useful.

Agree 100%
Sent from my Evita

Never mind nobody really reads these threads anyways

help me
hi there, could you tell me how to updrade to RUU 3.18 ?
my infomations :
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.30a.32.45.18
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.707.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT247W303284
(bootloader) imei: 359691042017692
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ83*****
(bootloader) cidnum: 11111111

kamazoko said:
hi there, could you tell me how to updrade to RUU 3.18 ?
my infomations :
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.30a.32.45.18
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.707.1
Click to expand...
Click to collapse
That wouldn't be an upgrade (RUU to 3.18), it would be a downgrade as you are presently on 5.05. With S-off, you can just run the 3.18 RUU. But do I'm not sure you have a valid reason for doing so, as I think you may be confused about this. But its not clear, as you haven't given much detail on what you are trying to accomplish or why.
Also, this has little or nothing to do with the topic or this thread, and you really shouldn't have dug up a 3-month old thread in order to post your issue.

thank you, i did it, but now i have a problem with rom Cynogenmod 10.2. wifi doesn't work, i try anything with my router but it is not work pls help me
thanks

kamazoko said:
thank you, i did it, but now i have a problem with rom Cynogenmod 10.2. wifi doesn't work, i try anything with my router but it is not work pls help me
Click to expand...
Click to collapse
You've already made a new thread asking the same question. Posting the same thing in multiple places is not the correct way to use this forum.

but my problem still stuck

Need help restoring HTC One S. Or flash a working Rom!?

( Text below is just an explanation to my issues and why I need help! )
Hallo dear XDA forum people I ahve many times read posts and fixes about my cellphone here and managed to unlock, root and install Super SU on my HTC One S. It still has the stock rom, given it's now unlocked and rooted etc. Last weeks I've been having problems with calling out or receiving phone calls. Due to the cellphone hangs every time. So factory reset it to default. The problem persisted somewhat. It now just gets sluggish and I can't hear the other one speaking. Even though the cellphone actually made the connection. So thought about downloading a RUU or flash to another ROM to see if it's cleaner and more stable.
What I done so far!
Before tampering with the cellphone I took backup .img files of my ROM. I even took a manual ''Copy everything on the cellphone to my PC'' in case this would happen. So....
I have installed Universal ADB Drivers, JDK for Java, Android Studio bundle, The HTC One Toolkit - Squabbi - 3.1.2 version. Not that it done any good so far.
The BIG problem is that the cellphone can't mount it's memory card. So I can't put any ROMS, FLASH FILES, .zips or anything on it. I failed at forcing data into the ''data'' folder to.
And when I try to flash a file directly using ''Fastboot'' the device hangs at:
sending 'zip' (632094 KB)...
OKAY [ 27.661s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 27.691s
Other problems when working with the ''ADB commands'' gives me the ''Device not found'' response.
I downloaded the RUU for my device as a .zip as there's no existing .exe version to be found. With no luck flashing it I might say. Due to the constant hanging when the file is ''Sending''.
( This is the RUU I downloaded: OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip )
And for 2 days with applying fix after fix and trial and error I'm coming nowhere! I'm thinking on formatting the whole cellphone and copy my ''manual copy of my cellphone'' into the formatted cellphone drive.
In the bootloader this information can be seen:
*** TAMPERED ***
*** RELOCKED *** (Along the lines of guides this happen. No idea how though
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:10:57:-1
My cellphone has: Philz touch 5 CWM Base version 6.0,3,2 on it.
NOW! This is what actually works on my cellphone:
1. I can get into BootLoader on my HTC One S!
2. I can get into Fastboot on my HTC One S!
3. The Fastboot on my HTC One S recognizes as ''Fastboot USB'' on when I plug it into my computer.
4. My computer recognizes the cellphone as a ''removable disk''. And using the command ''Fastboot Devices'' in CMD lets me see the ''SH32HW401164'' number. Using the command ''Fastboot getvar all'' gives me this information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4150mV
(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
all: Done!
finished. total time: 0.063s
----
My plan was to flash this ROM into my phone if the stock one still showed issues: http://forum.xda-developers.com/showthread.php?t=2531065
This being said and again: My HTC One S is NOT flashed with a custom ROM! It has the same ROM it came with, all though, it has been unlocked -> Rooted. And never been S-off. it is still S-On.
Any help with this issues would be appreciated and thanks for this great forum

SOLVED flashed working ROM and fixed SD card mounting error.
After 3 weeks of frustration and trying I finally got my phone booting with a ROM. As I couldn't find any RUU.exe files for my phone and the RUU.zips didn't work either I had to go custom ROMing. I'll explain the whole process with steps I did so that others can read easily
1. Go into Bootloader, choose Fastboot and connect your phone with the USB cable. Open up CMD in your Fastboot/ADB folder by holding SHIFT+Right Click and type: ''Fastboot devices'' without the quotas, to see if your phone appear like SH32HW.... etc. You can also use the command: ''Fastboot getvar all'' to pull a few lines of comparable information.
2. Download the stock recovery file here: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img , place it in the Fastboot/ADB folder and open CMD again, if you haven't already, in the Fastboot/ADB folder and type ''Fastboot flash recovery ville_recovery_signed.img''
Let the file flash and when it's done type ''Fastboot reboot-bootloader''
3. After the short reboot choose Clear Storage. Your phone might try to boot after this. just hold the power button + volume down to restart it into bootloader again. Then choose Factory Reset from bootloader menu. The phone might try to boot again after this but restart it manually into bootloader if it gets stuck.
4. After clearing storage and factory resetting go into Fastboot USB mode again and use CMD in the Fastboot/ADB folder again to flash your custom recovery file. I used TWRP 2.8.7.0.zip. This TWRP recovery is signed for HTC One S S4. The guide for the Viper ROM recommends the TWRP2.6.3.0 for phones with HBoot 2.15, and TWRP2.6.1.0 for Hboot 2.16 phones.
The command for flashing this file is ''Fastboot flash recovery twrp-2.8.7.0-ville.img''
5. After flashing the custom recovery reboot bootloader with the command ''Fastboot reboot-bootloader''. Then after the short reboot go into recovery from bootloader.
6. At this time your SD card should work. Choose to mount USB from the ''Mount'' menu in TWRP. Attach the USB cable if you haven't already. Transfer your ROM.zip file to your SD card with this method.
( I used the Viper ROM found here: http://venomroms.com/htc-one-s/ )
7. After the transfer is complete choose ''install from zip'' in TWRP and choose the ROM.zip of your choice.
( I choose the Viper_One_S_3.2.0.zip file and chose the ''full wipe'' option, removing apps I didn't want etc. )
8. After installation let the phone work it's magic for like 10-15 minutes if necessary. It'll hopefully boot into the new system in time and you can complete the setup
---
The importance is that the stock recovery steps up til I flashed TWRP again fixed the SD card error. There's more fixes you could try if this didn't work and they can be found here: http://forum.xda-developers.com/showthread.php?t=2086156

I told you to flash the stock recovery and make a factory reset from bootloader from the beginning. Glad you've sorted out finally
Sent from nowhere over the air...

Rapier said:
I told you to flash the stock recovery and make a factory reset from bootloader from the beginning. Glad you've sorted out finally
Sent from nowhere over the air...
Click to expand...
Click to collapse
Yes but it was hard finding a stock recovery. And the recovery that came with the phone did not work. So had to try lot of different ''what was supposed to be stock'' recoveries before I found one that worked Thanks by the way ^^

HTC-One-User said:
Yes but it was hard finding a stock recovery. And the recovery that came with the phone did not work. So had to try lot of different ''what was supposed to be stock'' recoveries before I found one that worked [emoji14] Thanks by the way ^^
Click to expand...
Click to collapse
I didn't have a link for it either. I had to do that only once (messed my sdcard) and I remember someone posted a link from MoDaCo where Paul O'Brian had it uploaded...if I remember right. But that was long time ago and I didn't have the link anymore
Sent from nowhere over the air...

Rapier said:
I didn't have a link for it either. I had to do that only once (messed my sdcard) and I remember someone posted a link from MoDaCo where Paul O'Brian had it uploaded...if I remember right. But that was long time ago and I didn't have the link anymore
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hmm... My SD card actually got un-mountable and messed up after having stock ROM and just choosing to do a factory reset in the bootloader. That is when my problems started! But now after testing just this recovery and clearing storage, factory rest, flash new TWRP in exact that order fixd my issue. If I would factory reset before clearing storage and cache it would do nothing for me. It's weird but now it's ok and works ^^
Should have made a video of me restoring my phone to youtube so others can see to O.O
Edit: Made one here. it's not in awesome quality but it shows the whole process https://www.youtube.com/watch?v=_emclhywhlw

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 !

HTC One M8 Softbricked and Unable to Flash

Hi, A friend gave me a Verizon HTC One M8 that was softbricked by a failed attempt to root or modify the device. I am unable to find out what the original owner did to the phone.
The phone will get stuck on the HTC logo for approximately two minutes and then reboot. I can get into the bootloader no problem, but the recovery and the factory wipe options go to the HTC logo and then get stuck at a black screen with the backlight on for approximately two minutes before rebooting. The command "fastboot oem rebootRUU" goes to the same HTC logo for approximately two minutes before rebooting, fastboot is unable to see the phone in this mode.
Because the bootloader is locked and cannot be unlocked because it is a Verizon, and the phone is S-ON, I am unsure how to fix the phone.
I have attempted to use RUU from a microsd card numerous times with the RUU images from here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845. the 4.4.4 one appears to complete successfully, but still bootloops after restarting.
Thank you in advance for your help.

I think (a redacted version of) the output from getvar-all would likely be helpful to see what state your phone is in and determine how to best resolve it.

Thank you for your quick reply. I have attached the "fastboot getvar all" output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.605.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <<SERIAL>>
(bootloader) imei: <<IMEI>>
(bootloader) imei2: Not Support
(bootloader) meid: <<MEID>>
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Well.....if you send that puppy to me I can s-off an attempt to reflash it for you. Not sure what else you can do with an s-on phone that you cant talk to in ruu mode.
Sent from my Nexus 6 using Tapatalk

While I appreciate your offer, I would like to try and resolve this without sending it out unless I really have to. Is there anything that you can think of that might work for me?
While I am unable to get the phone to boot into RUU mode for fastboot, I can get it to flash the RUU from microsd. For some reason it is still unable to boot after this. Is there another image or something I am doing wrong?
Thanks again for the help.

After you ran the ruu from SD did you attempt a factory reset? BTW, not sure if this helps your comfort level or not if it comes down to it but I have s-offed more vzw m9 than anyone. All done via mail.
Edit...and I would be more than willing to take a look remotely using team viewer.
Sent from my Nexus 6 using Tapatalk

When I attempt to do a factory reset, the HTC logo comes up and goes to a black screen for about 2 minutes and then bootloops. I am unable to format any partitions using fastboot and the only one that erases is cache. The big issue is that it is bootloader locked, otherwise I would have just flashed TWRP. I will contact you in private about that teamviewer help when I am at my computer. Thank you for the offer.

I thank dottat for all of his help over teamviewer.
Unfortunately, the phone has a locked emmc and is completely bricked.
Thank you everyone on this forum for your help.

So I'm having an eerily similar problem. The thing is I wasn't trying to do anything to my phone, it just randomly got stuck in a bootloop. I haven't tried anything with the RUU because I assumed it wouldn't work with verizon (I'm very new to all this) so I'm going to try later when I get the chance. What's the process to find out if the emmc is locked?

When I flashed a RUU with a newer version number then the one on it, after a reboot it would still be the old version number as if the flash did not take.

Which version number am I looking at? I know how to flash the RUU but I don't know exactly what I'm looking for there
---------- Post added at 08:46 PM ---------- Previous post was at 08:21 PM ----------
I tried a couple different files listed, and one seemed to flash correctly. I hit the update now option and now my phone won't turn on at all, no bootloader, no nothing. Bricked completely or am I waiting for something to happen??

Try charging up the phone for a bit. If that doesn't work you may have bricked it

yup, got bricked. oh well.

wmitchell2014 said:
yup, got bricked. oh well.
Click to expand...
Click to collapse
You left it on a charger? Does the light light up at all?
Sent from my SM-T320 using Tapatalk

nope, there is absolutely no response from the phone. Tried the battery recalibration thing and every other combination of things I can think of. I will leave it plugged in over night to see what happens but it was plugged in for a few hours today and nothing happened.

Attempted GPE conversion from VZW M8, no bootloader, no root, no adb, etc.
Not sure what to do at this point, have been to 10 different posts on ways to get this back to stock, or even usable and I cannot come out of this alive.
When I start up the Phone, it goes to the HTC One splash screen, then restarts, goes to it again, then goes to the Stock Recovery Screen with the Red Triangle.
I have tried to flash a rom etc using a sd card, but says this;
Install /sdcard...
Finding update package...
(waits about 2 minutes while loading)
Verifying update package...
Installation Aborted
Write host_mode:0 done
I get the red triangle recovery screen and can choose reboot system now, apply sd card, etc. as normal.
if I reboot it does the same thing.
Somehow in the conversion, my MID ended up as 0P6B17000, it used to be 0P6B20000
Cid is now 11111111, was VZW__001
I cannot access the bootloader screen so I cannot try to load using 0P6BIMG.zip
Can anyone put me out of my misery?

Connect it to a pc with adb and try "fastboot reboot-bootloader" to get from recovery to bootloader
Sent from my Nexus 5 using Tapatalk

pattafurr02 said:
Not sure what to do at this point, have been to 10 different posts on ways to get this back to stock, or even usable and I cannot come out of this alive.
When I start up the Phone, it goes to the HTC One splash screen, then restarts, goes to it again, then goes to the Stock Recovery Screen with the Red Triangle.
I have tried to flash a rom etc using a sd card, but says this;
Install /sdcard...
Finding update package...
(waits about 2 minutes while loading)
Verifying update package...
Installation Aborted
Write host_mode:0 done
I get the red triangle recovery screen and can choose reboot system now, apply sd card, etc. as normal.
if I reboot it does the same thing.
Somehow in the conversion, my MID ended up as 0P6B17000, it used to be 0P6B20000
Cid is now 11111111, was VZW__001
I cannot access the bootloader screen so I cannot try to load using 0P6BIMG.zip
Can anyone put me out of my misery?
Click to expand...
Click to collapse
If you are still s-off I can fix it. A team viewer session would help since your mid/cid are no longer standard.
Sent from my Nexus 6 using Tapatalk

dottat said:
If you are still s-off I can fix it. A team viewer session would help since your mid/cid are no longer standard.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
How do I go about doing that ?
Thank you !

pattafurr02 said:
How do I go about doing that ?
Thank you !
Click to expand...
Click to collapse
on PC,
https://www.teamviewer.com/en/download/windows.aspx