Related
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
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.
( 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
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 !
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