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.
Related
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
You're phone isn't bricked if it still turns on. If you can still access recovery why don't you just perform a full wipe then flash a new rom
lileddy305 said:
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
Click to expand...
Click to collapse
Your device is boot looping because the fermware version is not compatible with the ROM you flashed. To get ADB to detect your device you need to boot into Hboot and the select fastboot, then you can use ADB or fastboot commands.
It would be very helpful to post what ROM you flashed. Also you have Hboot 1.27.1100 which is part of the the firmware you need to use ICS so why you were told you need a later version is kind of confusing to me, unless you were wanting to go back to Gingerbread. Please run the following command and post back everything except your IMEI number.
Code:
fastboot getvar all
Have you tried any of the other methods
There are two things you need to look at
1) Is the device in usb debugging enabled?
2) other than using the standard ADB method there are a few other easier methods
a) Droid explorer
i can supply a link if needed
b) The sensation all in one toolkit
http://forum.xda-developers.com/showthread.php?t=1497404
if you have any other ? feel free to contact me as i have been there
kampj007 said:
There are two things you need to look at
1) Is the device in usb debugging enabled?=Invalid the OP can not currently boot to OS.
2) other than using the standard ADB method there are a few other easier methods=Invalid the OP can not currently boot to OS.
a) Droid explorer
i can supply a link if needed=Invalid the OP can not currently boot to OS.
b) The sensation all in one toolkit
http://forum.xda-developers.com/showthread.php?t=1497404=Invalid because the only tool needed by the OP from the toolkit is boot to recovery, but it uses ADB to do this and without being booted into the OS and having USB debugging enabled this will not work
if you have any other ? feel free to contact me as i have been there=Thanks for your willingness to help
Click to expand...
Click to collapse
Also about the toolkit, seeing as they will have to boot to Hboot and then select fastboot to be able to use ADB and fastboot commands. So the toolkit is not going to do the OP any good. The OP will have to either change firmware versions or flash a ROM that is compatible with the firmware version they have to solve the problem.
Wait a minute...
I have been in same situation and what i did was connect the phone via Usb and turn it on. Went into fastboot and then using the programs i talked about it allowed me to load software and change items as needed. I was able to connect through droid explorer as soon as it turned on and it helps u load into recovery and fastboot so that u can adjust as needed.
kampj007 said:
Wait a minute...
I have been in same situation and what i did was connect the phone via Usb and turn it on. Went into fastboot and then using the programs i talked about it allowed me to load software and change items as needed. I was able to connect through droid explorer as soon as it turned on and it helps u load into recovery and fastboot so that u can adjust as needed.
Click to expand...
Click to collapse
Exactly you had to boot to the Hboot and then choose fastboot for them to use the programs. Plus the OP is already S-off and can manually boot into Hboot then to recovery. So the tool kit has nothing to offer the OP at all. Yes they can be in fastboot and use Droid Explorer to copy any needed .zip be it a PG58IMG.zip or a ROM.zip, but they can also do this within their recovery by USB mass storage in recovery.
I do not mean to offend but I just do not want to see this made more complicated than it is for the OP. It is really a very simple problem and has a very simple fix.
Hello,
I am in similar situation. I cannot get my device to be recognized either. Here is what getvar all showed me:
"C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH164T500176
INFOimei: 355066045001866
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3905mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.497s"
Any help would be appreciated. Thanks!
C:\adb>
twocrows said:
Hello,
I am in similar situation. I cannot get my device to be recognized either. Here is what getvar all showed me:
"C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH164T500176
INFOimei: 355066045001866
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3905mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.497s"
Any help would be appreciated. Thanks!
C:\adb>
Click to expand...
Click to collapse
do you have enabled usb debugging mode from settings?
do you have installed htc drivers?
use also usb 2.0 ports not 3.0
just install htc sync and do again
rzr86 said:
do you have enabled usb debugging mode from settings?
do you have installed htc drivers?
use also usb 2.0 ports not 3.0
Click to expand...
Click to collapse
No to usb debugging mode
Yes to installed htc drivers
will make sure to use usb 3.0
twocrows said:
No to usb debugging mode
Yes to installed htc drivers
will make sure to use usb 3.0
Click to expand...
Click to collapse
wait not 3.0 use 2.0 ports
T-Macgnolia said:
Your device is boot looping because the fermware version is not compatible with the ROM you flashed. To get ADB to detect your device you need to boot into Hboot and the select fastboot, then you can use ADB or fastboot commands.
It would be very helpful to post what ROM you flashed. Also you have Hboot 1.27.1100 which is part of the the firmware you need to use ICS so why you were told you need a later version is kind of confusing to me, unless you were wanting to go back to Gingerbread. Please run the following command and post back everything except your IMEI number.
Code:
fastboot getvar all
Click to expand...
Click to collapse
Adb will recognize device while in fastboot?
I always thought fastboot cmds were for while in fastboot, and adb was for while booted to android?
Sent from my EVO using xda premium
scottspa74 said:
Adb will recognize device while in fastboot?
I always thought fastboot cmds were for while in fastboot, and adb was for while booted to android?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No fastboot mode is a developer tool first and secondly a fail safe to be able to communicate with ADB and fastboot if something goes drastically wrong such as not being able to boot to recovery or boot to the OS either one with the device and it needs to have the OS re installed. Try booting to fastboot mode and then connect your device to your computer with working ADB and type in adb devices it will show you the device ID.
miillaaad said:
just install htc sync and do again
Click to expand...
Click to collapse
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
Funnily enough, I never got adb recognized on stock rom.
After custom rom, it does.
twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
use adb toggle app from play store
see how it goes
twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
Maybe you should check everything is in order on low level, when your phone is connected to your computer, use lsusb under linux (usbview under windows) to check if the device is recognized by the OS.
OK, so I am a bit embarrassed on two counts:
1) when phone was booted up into ROM adb finally recognized it! I had a big duh moment.
2) it seems that at the root of the problem was a syntax error.
I was not renaming the recovery.img file properly. I was typing the command "fastboot flash recovery 4ext.img" and didn't rename file 4ext.img to "recovery.img" Cause when I renamed the file to "recovery.img" and then typed command "fastboot flash recovery recovery.img" I could finally boot back into recovery!
I did however have to flash boot.img after installing the newest Viper ROM. But here I am back on a great custom ROM! Thank you for all your help even if it didn't work it gave me the encouragement to keep trying.
Peace!
Sent from my HTC Sensation 4G using xda premium
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
Hello all,
So I have done tons of reading, wiki'ing, researching, googling and I have found things and I have come to my end here. Things started off yesterday when I saw that Google has now released a new version of Google Calendar. I have been waiting years for an upgrade of this magnitude. Unfortuntely I could not install it because my phone no longer had space on the partition. I tried to find a way to transfer files to my SD card but apparently the ROM I was running at the time (MIUI V4) did not support this kind of feature, shockingly.
So I decided to do some digging to find my next rom as being this is an old phone, I was hesitant to find anything new. I came across CM11 (Android 4.4.4) and noticed it was fairly stable and this got me very excited. Noticed CM12 aswell with the new Lolipop but I will hold off. I was running an old version of TWRP recovery and I assumed it would be a simple, "Drop the .zip rom in your SD card and fire away".
I apparently had the wrong version hboot 2.16 instead of 2.15. So I had to upgrade my TWRP. I upgraded to twrp-2.8.1.1-ville but that wasn't compatible with my phone for some reason. I downgraded back down to twrp-2.8.0.1-ville-dm and attempted to install the CyanogenMod_11S_ville_hboot-2.15_v2 rom.
Low and behold I get a "can't mount the /sdcard directory" in my recovery. So I switch over to CWM recovery-clockwork-6.0.4.8-ville and same /sdcard error. I wiped everything and didnt realize it would reformat my internal SD card. Every here knows opening the HTC One S is also no joy ride. I wanted to hold off as long as possible.
From there I feared the worst and attempted to RELOCK the phone and install RUU OTA_Ville_U_JB_45_S_Globalive_WWE_3.16.1500.7_1.11.50.05.28_10.27.50.08L_release_3049068z393w1fez9cc9lt.zip as my CID was GLOBA001 [WIND MOBILE in Canada].
That did not install correctly either. Right now I am staring at my phone, it is RELOCKED, no recovery, I have no idea if it's rooted, and I can't get past the fastboot menu.
I know I made a small stupid mistake somewhere and would appreciate some help with any of this.
My "fastboot getvar all":
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.11.50.05.28
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA28RW402816
imei: xxxxxxxxxxxxxxx
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: GLOBA001
battery-status: good
battery-voltage: 4169mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
My goal is to install either CWM or TWRP and CyanogenMod_11S_ville_hboot-2.15_v2. Hope this all helps!
EDIT 1: My bootloader is now UNLOCKED again. And I have ClockworkMod Recovery 6.0.4.8. I will try sideload adb. If anyone has suggestions help me have em
EDIT 2: When I try to select a zip from /storage/sdcard0 CWM tells me "E: Can't mount /storage/sdcard0" should I reformat it via the Recovery?
EDIT 3: I sideloaded CM11S via CWM (6.0.4.8) through CMD and it appeared to install but the install process moved WAY faster than it should have. Rebooted phone to black screen and no OS. Might try another recovery...
I fixed it! I went into the rom's zip file and extracted the boot.img file and flashed the boot file using "fastboot flash boot boot.img". I restarted the phone and VOILA, like magic the CM loading wheel showed up.
Reserved
( 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 !