Database Info

S-Off with AlphaRev Beta 2 Successful

I just made s-off my Vodafone Desire S European (Spanish). Works like a charm, indeed AlphaRev installed (with my consent) ClockWork recovery.

cool but my hboot is 98002

hi can you post a tutorial on how to s-off my device. I'm noob at this. I'm currently downloading ubuntu installer for windows. Thanks

1) have an ubuntu available (I use ubuntu 11.04)
2) install OpenJDK (java) on ubuntu (if you dont have Java yet)
3) download the Android SDK from developer android website
4) untar (tar xvf filename.tgz)
5) run tools/android
6) install 'Android SDK Platform-tools' and 'Android Compatibility package'
7) make sure your Desire is in USB Debug mode
8) run 'platform-tools/adb devices', and expect to see 1 device, I have one named '???????' but works for me
9) download and run alpharev (as root with sudo)
10) copy the serial from alpharev and get the key in alpharev website
11) introduce the key in command line
12) some reboots and get s-off!!!!
13) installs clockworkmod recovery if you want
xx) Profit!
no... wait we are not in slashdot

I wouldn't bother installing linux, just do it from a cd. No need to install sdk or adb or anything other than alpharevx.
Sent from my phone using XDA Premium App

I don't even know how to enter USB bebug mode on my Desire S >.<

settings > applications > development

Ho yeah thanks.

My HBOOT is 0.98.0004, so I cannot use AlpharevX? Is there a way to err, downgrade it?

GermanDZ said:
I just made s-off my Vodafone Desire S European (Spanish). Works like a charm, indeed AlphaRev installed (with my consent) ClockWork recovery.
Click to expand...
Click to collapse
What was your HBOOT version may I ask? Was your phone Vodafone branded?

spagmuff said:
What was your HBOOT version may I ask? Was your phone Vodafone branded?
Click to expand...
Click to collapse
My HBOOT was 0.98.0000, yes a Vodafone branded (from Spain, but I think is equal to UK version).

Okay, COMPLETE ubuntu noob here, so after downloading alpharevx.tgz which is aparently a GTAR file, what do i need to do? Because it wont open as if its an exe file because not windows (herpaderp). Is there a command line im meant to type or am i just being silly?
Thanks in advance.

Tuptup said:
Okay, COMPLETE ubuntu noob here, so after downloading alpharevx.tgz which is aparently a GTAR file, what do i need to do? Because it wont open as if its an exe file because not windows (herpaderp). Is there a command line im meant to type or am i just being silly?
Thanks in advance.
Click to expand...
Click to collapse
Extract to a directory or folder of your choice, eg desktop.
Open terminal in this folder & type "sudo ./alpharevx" with your phone connected & in usb debug mode.
Should detect phone, follow instructions.
Sent from my phone using XDA Premium App

===================================
| AlphaRevX HBOOT S-OFF tool 0.2pre |
===================================
A complete success
Worked like a charm
Thank you AlphaRev!!!
Acquiring root (method 2)...
(if we hang here for a *long* time [15mins+], please reboot your phone and try again.)
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Waiting for fastboot...
Rebooting to fastboot (again)...
Waiting for fastboot...
SUCCESS - Life gave us lemons, we didn't make lemonade!
Do you want to download (Internet connection required) and flash ClockworkMod Recovery? [Y/n] y
Downloading recovery for your phone (saga)...Done.
Flashing recovery over fastboot...SUCCESS!

how do i open adb? Everytime i double click adb in platform tools, nothing happens. Sorry not too good at ubuntu

dan-fish said:
how do i open adb? Everytime i double click adb in platform tools, nothing happens. Sorry not too good at ubuntu
Click to expand...
Click to collapse
You don't need to adb.
Just open the terminal and cd to the downloaded alpharevx folder then type "sudo ./alpharevx"

You don't need adb, alphrevx works without it.
1. Exctract alpharevx to an easily reachable place (ex. Desktop)
2. Start terminal and get to that place (with cd command)
3. Run "sudo ./alpharevx"
I think you need to enable HTC Sync mode on your phone but not sure.

ok so i managed all that now it's stuck on alpharevx waiting for device...
I'm doing this on ubuntu through vmware. Could that be the problem?
USB debugging is on by the way!
oh it's also on HTC sync mode.

Virtual machine's hardware access may be limited, don't know. I've ran linux from USB flash.

Evilmystic said:
You don't need adb, alphrevx works without it.
1. Exctract alpharevx to an easily reachable place (ex. Desktop)
2. Start terminal and get to that place (with cd command)
3. Run "sudo ./alpharevx"
I think you need to enable HTC Sync mode on your phone but not sure.
Click to expand...
Click to collapse
Don´t need to activate the HTC, as well as any of the options, just connect usb.
Then follow the steps the left Evilmystic, i did it this way.

[Guide] Official Downgrade Method

This Guide is intended for the users who rooted their devices using the cwm-4.0.1.4-saga.img and su-3.0-efgh-signed.zip files.
note: it may work for the other rooting and downgrade methods
Files needed
*Original Nandroid Backup (rooted)
*Bootloader Unlocked via HTCDev or S-Off
*Oldest RUU that is compatible to your region
*misc_version
*adb and fastboot
*Goldcard Tool and Goldcard IMG
Note: I use this method for the version GB 2.3.5 Sense 3.0 SW 2.15.707.2
Steps:
I. Unlock Bootloader
a. go to www.htcdev.com and choose "Unlock Bootloader" click the "Get Started" green button.
b. you will be redirected to http://htcdev.com/bootloader/ at the "supported Devices" choose "All Other Supported Models"
c. follow the on screen instructions.
II-A. Coming from a custom rom
a. download my Stock Nandroid Backup that I posted here.
b. restore it via 4ext or cwm recovery be sure to wipe all the cache, partition and dalvik before doing so.
c. after restoring my Nandroid Backup boot your device to fastboot and flash the boot.img and recovery.img that I posted here as well.
d. your phone should boot up with no problems.
II-B. Coming from a stock fw
a. be sure that you have your Nandroid Backup and proper boot.img and recovery.img
b. follow the same procedure at II-A the only difference is that you're the one who needs to find your proper boot.img and recover.img
III. Creating a Gold Card
a. download the gold card helper from market.
b. get the cid of your mmc2
c. go to http://psas.revskills.de/?q=goldcard and fill out the form using the reversed cid that gc helper provided.
d. download the goldcard.img
e. download the goldcard tool I posted here.
f. connect your phone as a "Disk Drive" and format your mmc.
e. using gold card tool click "Refresh" to select the HTC MMC that you will use and click "Load GoldCard.img" select the goldcard.img you've downloaded and click "Patch MMC"
IV. Changing your device Version
a. download the AWT Tools and Patch that I posted here
b. extract the files to C:
c. execute this commands using "cmd"
Code:
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
IV. Relock your Bootloader
a. go into fastboot mode and execute this command
Code:
fastboot oem lock
V. Flashing the oldest RUU for your Device
a. download the oldest RUU that you can find for your device but make sure it will be newer than 1.27.405.6.
b. if there's no RUU for your device that is newer than 1.27.405.6 change it to 1.20.000.0.
c. go into fastboot mode once again and connect your device to pc.
d. flash your device using the RUU you've downloaded and viola! you have a downgraded Desire S device.
note: you can still cross your fingers so that you can be so sure that you don't have to do this all over again.
Nandroid Backup and Tools - still uploading

I still would rather get temp root rather than using HTC dev.

Don't do the same mistake as I did, htcdev will surely void your warranty. Use ZergRush and misc_version instead: http://forum.xda-developers.com/showthread.php?t=1399331

where is the tool and nandbackup ? can't find it anywhere

HTC desire s hboot downgrade from hboot 2.02.0002 to hboot 0.98.0002

Welcome !!!!!!!!!!!!!!!
I'm not taking credit for any files or programs here I just simply constructed a full guide on how to downgrade etc. for noobs and also people that is struggeling like I did .
Please be warned that you might damage your phone and also that your waranty voids after you unlocked your bootloader so I don't take any responsibility !!!!! But be assured if you follow my instructions you'll just be fine !!!!!!!!!!!!!!!!!!!!!!!!!!!
It took me 5 weeeeeeeekssss to find all of these and figure everything out so be greatfull !!!!
I'm going to tell you excacly how i did it !
First things first ....
Copy Cyanogen mod 7 android 2.3.3.zip to your sd card
Open "HTC DESIRE S - All in one toolkit" and run it.Remember you should be in bootloader for this ( volume down + power ) and the navigate with arrow keys to fastboot and select it using power button. Follow all the instructions in the lefthand corner on how to unlock your bootloader
Next you have to flash custom recovery . Look in the right hand corner and select TWRP 2.4.0.0 and let it flash.Sometimes it will say your phone is not detected just exit that command promt and the next command window will flash it.
Now you have to go to your recovery ... While in fastboot select bootloader and then recovery ... A htc logo will appear and about 10 sec from that an TWRP logo .
Go to
After all that is done go to install select zip and find the cyanogen mod 7... .zip you pasted earlier on your sd card and then flash it . wait untill it completes.
Now you have to reboot your phone look for reboot in the TWRP menu and select reboot then bootloader . Once your in bootloader again go to the folder where all my tools are located that I provided for you .
Go to android tools and press shift then right click and select open command window here .
copy and paste the following :
fastboot flash boot boot.img
After its completed select the reboot option using your arrow keys.
Wait until cyanogen mod 7 fully boots up
Now go to settings > applications > developer options and enable usb debugging
After that go to android tools folder again and open the command window again paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
exit
adb reboot-bootloader
After that the phone will be in bootloader again already in fastboot and then just type :
Fastboot oem lock
After that the phone will be in bootloader again already in fastboot
Now open the ruu I have provided for you and run it until it completes and whalah !!! You have hboot 0.98.0002
Now if you want to root it use the superoneclick app I provided and after that s-off also your bootloader with revolutionary i provided just follow the clear instructions(Your phone must be turned on and not in bootloader ! also remember to turn on usb debugging again !!!! )
after all of thos when you reboot into bootloader things will look like :
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.11_M
eMMC-boot
(current date),(current time)
Thank you very much:good::good::good::good::good::good::good::good::good::good::good:
lY-AssassiN-Yl
files are all in one .zip file
link to files ........ mediafire.com/?ijic67sr55676um (just copy and paste in your browser)..........

Edited Version
I just wanted to post similar one but You did it for me. Anyway i edited it cause it was a mess Still I wonder will this work without GoldCard on any phone...
This is a simple guide for newcomers to Android. Please be warned that you might damage your phone and also that your waranty voids after you unlock your bootloader and the author doesn't take any responsibility for that. Still things shouldn't go wrong.
Link for the necessary files.
1. Copy Cyanogen mod 7 android 2.3.3.zip to your SD card.
2. Go here and click THANKS button for hasoon2000. This is his tool and he takes all credit for his hard work.
3. Now open "HTC DESIRE S - All in one toolkit" and double click on Desire S.exe.
4. Follow all the instructions in the left hand corner on how to unlock your bootloader
5. Now we are going to flash recovery. Look in the right hand corner, select TWRP 2.4.0.0 and click Flash Recovery button and follow the instructions.
6. It's time to go to the recovery. While in fastboot select bootloader and then recovery. A htc logo will appear and then TWRP should start.
7. When you're in the recovery MAKE BACKUP. Then go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that go back, click Install and select Cyanogenmod 7.zip you placed on your SD card. Slide to flash and wait.
8. After flash is complete go back to TWRP main menu and select Reboot and then Bootloader.
9. When you're in bootloader go to the folder where all my tools are located.
Go to android tools and press shift then right click and select open command window here.
10. In the Command Window copy and paste the following :
fastboot flash boot boot.img
11. After it's completed select the reboot option using your arrow keys.
Wait until cyanogenmod 7 boots up. This is first boot so it may take a while. Don't get nervous.
12. When Cyanogenmod 7 will start go to Settings > Applications > Developer options. Enable USB Debugging
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
exit
adb reboot-bootloader
14. When your phone will be in bootloader in fastboot USB mode type:
Fastboot oem lock
15. After that the phone will give you Warning. It's fine. Stay in bootloader in fastboot USB.
16. Open the RUU I have provided and run it until it completes flashing.
17. You have hboot 0.98.0002 now. Use the superoneclick app I provided.
18. After that run revolutionary tool and follow the instructions. After it's complete reboot into bootloader. Things should look like this:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.11_M
eMMC-boot
(current date),(current time)
Big thanks to:
lY-AssassiN-Yl
hasoon2000

Thanks for this guide. I've seem to have run into an issue though...
11. After it's completed select the reboot option using your arrow keys.
Wait until cyanogenmod 7 boots up. This is first boot so it may take a while. Don't get nervous.
Click to expand...
Click to collapse
It been 20-30 minutes now, and still booting. Is it now time to get nervous?

warjar said:
Thanks for this guide. I've seem to have run into an issue though...
It been 20-30 minutes now, and still booting. Is it now time to get nervous?
Click to expand...
Click to collapse
Yes it's too long. Try connecting your device to PC and in command line (adb) type: adb reboot recovery.
If this doesn't work try Three button reset. Push power, volume up and down simultaneously. If this doesn't work too follow these steps
1. Connect phone to USB
2. Remove battery
3. Phone will still be running
4. Shutdown PC to cut the USB power
Now boot into recovery (hold vol down and click power). I'm sorry this is partially my fault. I just switched my brain off during writing this assuming this was right and n00b proof :silly:. It isn't. There is one more step before flashing Cyanogenmod that you may not be familiar with. When you manage to get into recovery go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that flash (install) cyanogenmod again. This time it will boot. I'm updating guide right now and I'm sorry for your stress and inconvenience. If it works please report back.

VnnAmed said:
Yes it's too long. Try connecting your device to PC and in command line (adb) type: adb reboot recovery.
If this doesn't work try Three button reset. Push power, volume up and down simultaneously. If this doesn't work too follow these steps
1. Connect phone to USB
2. Remove battery
3. Phone will still be running
4. Shutdown PC to cut the USB power
Now boot into recovery (hold vol down and click power). I'm sorry this is partially my fault. I just switched my brain off during writing this assuming this was right and n00b proof :silly:. It isn't. There is one more step before flashing Cyanogenmod that you may not be familiar with. When you manage to get into recovery go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that flash (install) cyanogenmod again. This time it will boot. I'm updating guide right now and I'm sorry for your stress and inconvenience. If it works please report back.
Click to expand...
Click to collapse
Thanks for the anwser, although I managed to solve this shortly after posting last nigth. Basicly I just removed the battery break the loop, wiped data and cache and reflashed.
Yes, I will have to ID myself as somewhat of a noob on the andoid-front and want to point out some parts of the guide that aint 100% noob-proof. A couple of times I was actually forced to think for myself. That's outrageous!
1. Place the folder "Desire_S_All-In-One_Kit_v2.0" at your C:/ root and run the .exe from there. Won't work baked into some other directory I believe.
2. Replace "adb push C:\downsaga\misc_version /data/local/tmp" with "adb push misc_version /data/local/tmp". Otherwise you will be looking in the wrong dir the way this rest of this guide is set up.
3. At step 11. If stuck on loop, follw these steps:
A. boot into recovery
B. wipe data/factory reset
C. wipe cache
D. go into partitions menu, and format boot and format system. (I skiped this part this time)
E. install rom zip from sdcard
F. reboot
4. At the end of step 13 there seem to be one "exit" to many. (this is just a trivial thing ofc)
5. Step 17: I had to run this one several times before it got propper rooted. What seem to make the difference was actually the in order i did things during the su test after the "successful" root. Go to your phone app-list >>superuser>>Preferences>>Automatic responce>>Allow befor you click away the warning on your computer.
I also ran all programs as admin, didnt test if it would work without, but it's generally a good idea with these things.
Remember, when you write for noobs you have to include the obvious
It's the first time i've touched this root-stuff so take this for what it is. It solved it for me, but may not always be the correct fix.
I've been wanting to root without using HTCdev, but resigned to this after beeing thrown around to some 10-15 differnet sites and guides, with missing software etc..
Now to figure out what ROM to use as this one had Sense 2.1, and why TiBu crashes when I attempt to remove bloatware. But that will have to be another story...
Thanks for the guide guys, and for providing all the software needed in one package, that's probably the most useful part for a newcomer =)

RUU
Hey guys,
got up to the RUU part and it says when updating rom from "13.10.401.8" to "1.31.206.1" Cannot be updated due to it being the wrong RUU, please find one for your phone
Also Im in the UK
Background :
Flashed it before to run primo s 4.1. Did not have the S-OFF
had ext4 ? then it changed TWRP

hmz12 said:
Hey guys,
got up to the RUU part and it says when updating rom from "13.10.401.8" to "1.31.206.1" Cannot be updated due to it being the wrong RUU, please find one for your phone
Also Im in the UK
Background :
Flashed it before to run primo s 4.1. Did not have the S-OFF
had ext4 ? then it changed TWRP
Click to expand...
Click to collapse
Wrong can mean two things:
1. Did you misc_version from a root/temproot environment? If you didn't have the right privileges, you can't do this step.
2. Your phone is Branded (to your carrier), you need to either choose a RUU that matches your carrier (see "+files" then RUU in my sig) or create a goldcard, which should let your phone ignore the carrier/region check.

VnnAmed said:
I just wanted to post similar one but You did it for me. Anyway i edited it cause it was a mess Still I wonder will this work without GoldCard on any phone...
This is a simple guide for newcomers to Android. Please be warned that you might damage your phone and also that your waranty voids after you unlock your bootloader and the author doesn't take any responsibility for that. Still things shouldn't go wrong.
Link for the necessary files.
1. Copy Cyanogen mod 7 android 2.3.3.zip to your SD card.
2. Go here and click THANKS button for hasoon2000. This is his tool and he takes all credit for his hard work.
3. Now open "HTC DESIRE S - All in one toolkit" and double click on Desire S.exe.
4. Follow all the instructions in the left hand corner on how to unlock your bootloader
5. Now we are going to flash recovery. Look in the right hand corner, select TWRP 2.4.0.0 and click Flash Recovery button and follow the instructions.
6. It's time to go to the recovery. While in fastboot select bootloader and then recovery. A htc logo will appear and then TWRP should start.
7. When you're in the recovery MAKE BACKUP. Then go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that go back, click Install and select Cyanogenmod 7.zip you placed on your SD card. Slide to flash and wait.
8. After flash is complete go back to TWRP main menu and select Reboot and then Bootloader.
9. When you're in bootloader go to the folder where all my tools are located.
Go to android tools and press shift then right click and select open command window here.
10. In the Command Window copy and paste the following :
fastboot flash boot boot.img
11. After it's completed select the reboot option using your arrow keys.
Wait until cyanogenmod 7 boots up. This is first boot so it may take a while. Don't get nervous.
12. When Cyanogenmod 7 will start go to Settings > Applications > Developer options. Enable USB Debugging
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
exit
adb reboot-bootloader
14. When your phone will be in bootloader in fastboot USB mode type:
Fastboot oem lock
15. After that the phone will give you Warning. It's fine. Stay in bootloader in fastboot USB.
16. Open the RUU I have provided and run it until it completes flashing.
17. You have hboot 0.98.0002 now. Use the superoneclick app I provided.
18. After that run revolutionary tool and follow the instructions. After it's complete reboot into bootloader. Things should look like this:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.11_M
eMMC-boot
(current date),(current time)
Big thanks to:
lY-AssassiN-Yl
hasoon2000
Click to expand...
Click to collapse
Will this method works on ICS Desire S updated via ICS RUU and unlocked via HTC DEv

zeus.lny said:
Will this method works on ICS Desire S updated via ICS RUU and unlocked via HTC DEv
Click to expand...
Click to collapse
Sure. Actually it's how I did it

i am already running Andromadus AOSP 4.2.2 with S-On for for me to S-Off my phone i have to follow from step 12 of your guide as i already have 4Ext recovery installed, Also 1 thing.. Do i have to make a gold card to run the RUU of my regions to Downgrade my hboot ?

@paulie uk
hi, i figured i dont need s-off, just had to flash the boot.img
NOOB mistake
thanks anyways guys!!!

VnnAmed said:
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
exit
adb reboot-bootloader
Click to expand...
Click to collapse
Hello all, everything works fine for me until this step: first, I was surprised to see the program is named "misctool" and not "misc_version" as specified in the example. Also, the option to use seems to be "w" and not "-s". Anyway, when I run "./misctool w 1.27.405.6" as root, I get "Error opening misc partition... must be run as root" twice... And I know I am running it as root since when I run "whoami" it returns "root"...
What am I doing wrong here..?
EDIT:
I was able to make it work using the commands using "adb shell" from the cmd prompt...
But now I am running into another problem, when I try to install the RUU I get :ERROR [131]: CUSTOMER ID ERROR
Apparently this occurs when you have the wrong RUU. How do I get the correct RUU for my device ?
Thanks in advance

how to get token ID?
Apperantly I got stuck on the 3rd step. How do I get token ID? What is the command and on which dir do I type it?

ghhhaaaa i can get past step 17. I realy need some help. i think comodo tought this files was a treath an placed them in quarantine
and i can get it to un quarantine them.. :crying: ( aahhh i needed to unlock bootloader again "crap.. now i need to figure out how i did that")
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

RUU Update takes forever!
I've been sitting here for 15 min and the RUU updater are still "Sending" something -.-
Is this normal?

10x
htc desire s i'm s-off now 10x to you.:good:

great tutorial, but
great tutorial, thank you, but in the step
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
I get "device not found"
what is the problem? thank you

gezginsirin said:
Apperantly I got stuck on the 3rd step. How do I get token ID? What is the command and on which dir do I type it?
Click to expand...
Click to collapse
As far as i remember... U get token ID when u unlock your bootloader via HTCDev.. Go to HTCDev http://http://www.htcdev.com/bootloader/ select all other supported model and follow the steps a mentioned. u need to have a login account to do that.

maysider said:
great tutorial, thank you, but in the step
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
I get "device not found"
what is the problem? thank you
Click to expand...
Click to collapse
The error would usually appear if USB debugging isn't ticked or you don't have the right drivers.
Cheers
FromBeyondThisWorld

maysider said:
great tutorial, thank you, but in the step
13. After that go to android tools folder again and open the command window and paste the following :
adb push C:\downsaga\misc_version /data/local/tmp
I get "device not found"
what is the problem? thank you
Click to expand...
Click to collapse
Tick usb debugging in setting and re install htc sync which will install the required drivers also make sure u have android sdk installed and updated.
Sent from my Desire S using Tapatalk 4

[Guide] Flash SuperSu and get root without installing custom recovery

Hi!
This guide is for the people who want to try a custom kernel and have root acces and still want to be able to get OTA's with the stock recovery. I haven't tested this on the M4 but on the HTC One V it works!
Try this at your own risk, I am NOT responsible for any damage!
Requierments:
- HTC drivers
- ADB
- fastboot
Step 1: backup your data using ADB
ADB can be used to backup your app data this is how:
1) Create a folder on your desktop called ie. M4.
2) Open terminal (linux/mac) or cmd and browse to the folder you just created.
Code:
for example:
cd Desktop/M4
3) Now backup your SMS messages and contacts using the message and phone app on your phone and copy and paste the file using usb to your desktop, or sync them with google
4) In the terminal you type
Code:
adb backup -apk -all -f backup.ab
to start the backup and follow the instructions on your phone. (Note that you are still in the M4 folder.)
5) After the backup is finished there should be an file called backup.ab in the M4 folder, you now have a backup
6) Just to be sure also copy your whole storage partition to your desktop
Unlocking the bootloader
Follow this guide to unlock the bootloader: http://www.htcdev.com/bootloader/
Unlocking the bootloader will factory reset your phone, you can restore using the backup we made.
Getting root acces
1) Go to http://http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip and download the flashable supersu.zip file
2) Put the .zip file on the root of your phones sdcard
3) Download this recovery: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m4 and put it in your M4 folder on your desktop.
4) Open your terminal and browse to your M4 folder:
Code:
for example:
cd Desktop/M4
5) Reboot your phone into the bootloader using the screen on/off and volume down buttons
6) Select fastboot and make sure you see fastboot usb
7) Type:
Code:
fastboot boot philz_touch_6.41.6-m4.img
this will load a custom recovery but it will not install it, the stock recovery will be kept.
8) Flash supersu.zip in this "live" recovery and after it's finished reboot your phone to system. You should now be rooted and have SuperSu.apk installed.
Restore your backup
Restore your backup using the terminal and type:
Code:
adb restore backup.ab
You are now rooted and can try custom kernels and recieve OTA's because you still have the stock recovery. Don't mess to much with the files in /system or an OTA might fail.

can anyone confirm if this works for rooting a HTC One Mini (M4)?

I did that on my HTC D816w dual sim China Unicom Version. But i used CWM rather than philztouch thingy. It works perfectly fine so far. Root checker say device is rooted properly.
Anyone can get me a guide of how to use the functions of SuperSU. Like a link or something

Aktharcod said:
I did that on my HTC D816w dual sim China Unicom Version. But i used CWM rather than philztouch thingy. It works perfectly fine so far. Root checker say device is rooted properly.
Anyone can get me a guide of how to use the functions of SuperSU. Like a link or something
Click to expand...
Click to collapse
can you explain to me how you did it i have the exact phone have already unlocked the bootloader but after running fastboot boot philz touch img nothing happens when i choose recovery. May be am doing the wrong thing am not able to access the super su file on SD. How can i run it live as he has said ??

I'm already rooted
LQi said:
Hi!
This guide is for the people who want to try a custom kernel and have root acces and still want to be able to get OTA's with the stock recovery. I haven't tested this on the M4 but on the HTC One V it works!
Try this at your own risk, I am NOT responsible for any damage!
Requierments:
- HTC drivers
- ADB
- fastboot
Step 1: backup your data using ADB
ADB can be used to backup your app data this is how:
1) Create a folder on your desktop called ie. M4.
2) Open terminal (linux/mac) or cmd and browse to the folder you just created.
Code:
for example:
cd Desktop/M4
3) Now backup your SMS messages and contacts using the message and phone app on your phone and copy and paste the file using usb to your desktop, or sync them with google
4) In the terminal you type
Code:
adb backup -apk -all -f backup.ab
to start the backup and follow the instructions on your phone. (Note that you are still in the M4 folder.)
5) After the backup is finished there should be an file called backup.ab in the M4 folder, you now have a backup
6) Just to be sure also copy your whole storage partition to your desktop
Unlocking the bootloader
Follow this guide to unlock the bootloader
Unlocking the bootloader will factory reset your phone, you can restore using the backup we made.
Getting root acces
1) Go to and download the flashable supersu.zip file
2) Put the .zip file on the root of your phones sdcard
3) Download this recovery: and put it in your M4 folder on your desktop.
4) Open your terminal and browse to your M4 folder:
Code:
for example:
cd Desktop/M4
5) Reboot your phone into the bootloader using the screen on/off and volume down buttons
6) Select fastboot and make sure you see fastboot usb
7) Type:
Code:
fastboot boot philz_touch_6.41.6-m4.img
this will load a custom recovery but it will not install it, the stock recovery will be kept.
8) Flash supersu.zip in this "live" recovery and after it's finished reboot your phone to system. You should now be rooted and have SuperSu.apk installed.
Restore your backup
Restore your backup using the terminal and type:
Code:
adb restore backup.ab
You are now rooted and can try custom kernels and recieve OTA's because you still have the stock recovery. Don't mess to much with the files in /system or an OTA might fail.
Click to expand...
Click to collapse
What if I'm already rooted and Ijust want to load the recovery? Oh, and, I already have TWRP loaded (no custom kernel, no custom ROM, just Rooted and Unlocked), will there be any problem if I just connect my phone (HTC One V) to computer and then I just type the command "fastboot boot philz_touch_6.41.6-m4.img"? Shall I uninstall TWRP?And how do i do this?...
Yes, I know that there will not be any other updates for HTC One V, but I want to install a custom kernel, and then I will be able to S-OFF my phone, and then I will be able to install a Custom ROM I know it's possible to install Custom ROMs without S-OFF, but i saw some guys that bricked their phones (HTC One V) trying to install Custom ROMs without S-OFF, so I just want to ensure

Victor271 said:
What if I'm already rooted and Ijust want to load the recovery? Oh, and, I already have TWRP loaded (no custom kernel, no custom ROM, just Rooted and Unlocked), will there be any problem if I just connect my phone (HTC One V) to computer and then I just type the command "fastboot boot philz_touch_6.41.6-m4.img"? Shall I uninstall TWRP?And how do i do this?...
Yes, I know that there will not be any other updates for HTC One V, but I want to install a custom kernel, and then I will be able to S-OFF my phone, and then I will be able to install a Custom ROM I know it's possible to install Custom ROMs without S-OFF, but i saw some guys that bricked their phones (HTC One V) trying to install Custom ROMs without S-OFF, so I just want to ensure
Click to expand...
Click to collapse
I dont think a recovery that isnt made for your device will work. The HOV has its own version of Philz recovery so try that one.
On another note, HTC disabled recovery sideloading on the m4 since the kitkat OTA. Maybe it is still useful for people with other devices...

Ok
LQi said:
I dont think a recovery that isnt made for your device will work. The HOV has its own version of Philz recovery so try that one.
On another note, HTC disabled recovery sideloading on the m4 since the kitkat OTA. Maybe it is still useful for people with other devices...
Click to expand...
Click to collapse
Well, anyway, I don't really need Philz... thanks anyway for reply

Brilliant. Thanks so much for posting this. I re-rooted my Nexus 10 after reflashing with the latest stock binary, using TWRP loaded from my desktop. I didn't have to touch the stock recovery.

Verizon HTC One (M8) Cheat Sheet...

Below is a cheat sheet I've made to help others keep the commands they'll need and general information organized and consolidated in one place... When I first started using Android years ago I kept one of these so I could refer to it if I forgot a command or a small piece of info and I thought I'd share one for the m8.
Make sure to check out the note at the end of this post regarding Dottat's updated ADB files. They prevent the need to flash ruu's twice as you'll see outlined in this post.
Edit Note:​I highly recommend running ruu's via adb. It may look more intimidating than the exe or hboot methods,
but if they were to fail you'd see exactly where it failed in the running log. You can avoid having to wait
for an initial boot of the stock rom if your intentions are to wipe to stock and then install a custom
recovery and whatever your rom/rom(s) of choice are. I personally wipe my phone from recovery, then
wipe via the adb commands below, run the ruu, and then factory reset from stock recovery. I'll then
install a custom recovery and my rom of choice. It's up to you, but I've found this to be the quickest
method of insuring a full-wipe to stock and then into my rom of choice. The wiping above is redundant
and not necessary, but I'll do it if I've got a problem I simply cannot figure out. To be honest the ruu should
wipe everything for you and then running a factory reset w/stock recovery installed should fix any
4g/LTE issues. ​***Verizon ADB Information***
--MOST but NOT ALL of this is Universal (Not Carrier Dependent)--
All commands beginning with "fastboot" must be performed at Bootloader
All commands beginning with ADB are performed from a phone that is in Rom
-You may skip the "adb reboot bootloader" step if you're already
at the bootloader
Firmware/RUU/Recovery instructions are available in their specific threads
*This is just a cheat sheet*
Basic ADB Commands:​
Recovery Flashing: (TWRP Current Standard)
adb reboot bootloader
fastboot flash recovery recoveryimgname.img
Firmware Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
*you should be prompted to flash a second time here*
fastboot flash zip firmwarename.zip
fastboot reboot-bootloader
HBoot Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
RUU Commands​
Wipe By ADB:*optional*(though a wipe is recommended either by recovery or adb)
adb reboot bootloader
fastboot oem task 28
fastboot oem task 29
Install RUU via ADB:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
Install RUU via HBoot:
Rename ruu .zip to 0P6BIMG.zip and copy to root of external sdcard
Boot to your bootloader and enter hboot if you're in fastboot mode
Hboot should automatically read the RUU file and begin unpacking (progress bar at top right)
Follow onscreen prompts after it unpacks...
*sdcard must be formatted to fat32 to read RUU* formatting the sdcard through the android os
will accomplish this. It will mount vfat when you read it by computer or in twrp this is okay.
SELinux Terminal Commands:​
1) Grant su level permissions via terminal by typing "su"
2) Enable SELinux status by typing "setenforce x" where x is the variable below
setenforce 0 =Permissive
setenforce 1 =Enforcing
GPE Install Instructions:​
Begin with SuperCID:***May no longer be necessary***
1) Get current cid information via;
fastboot oem readcid
Write down your current cid reading
2) Change your cid to 11111111 via;
fastboot oem writecid 11111111
(check cid again with fastboot oem readcid to varify)
3) Reboot to the bootloader
4) Following the reboot back to the bootloader
verify your cid is 11111111
And Then Install Rom Via:
5)Wipe /data; /cache; /system; Dalvik
6)Format /system; /data; /cache to f2fs -optional *Must use Elite Kernel for GPE 5.1*
7)Install Rom
8)Reboot
Remove GPE:***these are just my recommendations***
1) Revert CID via fastboot oem writecid (your stock cid ex: fastboot oem writecid VZW__001
2) Wipe everything /data, /cache, /system, /dalvik
Click Here for dottat's firmware and ruu master collection
Below, on this first page, dottat has linked a file containing updated adb files to be used when installing his ruu's. They correct the issues many have had requiring two flashes of his ruu's. Full information available through his posts in this thread. You can either replace the files in his .zip with your current adb folders files, or use it (after unzipping) as an updated lightweight adb interface folder.

jcole20 said:
Below is a cheat sheet I've made to help others keep the commands they'll need and general information organized and consolidated in one place... When I first started using Android years ago I kept one of these so I could refer to it if I forgot a command or a small piece of info and I thought I'd share one for the m8.
***Verizon ADB Information***
--MOST but NOT ALL of this is Universal (Not Carrier Dependent)--
All commands beginning with "fastboot" must be performed at Bootloader
All commands beginning with ADB are performed from a phone that is in Rom
-You may skip the "adb reboot bootloader" step if you're already
at the bootloader
Firmware/RUU/Recovery instructions are available in their specific threads
*This is just a cheat sheet*
Basic ADB Commands:​
Recovery Flashing: (TWRP Current Standard)
adb reboot bootloader
fastboot flash recovery recoveryimgname.img
Firmware Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
*you should be prompted to flash a second time here*
fastboot flash zip firmwarename.zip
fastboot reboot-bootloader
HBoot Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
RUU Commands​
Wipe By ADB:*optional*
adb reboot bootloader
fastboot oem task 28
fastboot oem task 29
Install RUU via ADB:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
Install RUU via HBoot:
Rename ruu .zip to 0P6BIMG.zip and copy to root of external sdcard
Boot to your bootloader and enter hboot if you're in fastboot mode
Hboot should automatically read the RUU file and begin unpacking (progress bar at top right)
Follow onscreen prompts after it unpacks...
*sdcard must be formatted to fat32 to read RUU* formatting the sdcard through the android os
will accomplish this. It will mount vfat when you read it by computer or in twrp this is okay.
SELinux Terminal Commands:​
1) Grant su level permissions via terminal by typing "su"
2) Enable SELinux status by typing "setenforce x" where x is the variable below
setenforce 0 =Permissive
setenforce 1 =Enforcing
GPE Install Instructions:​
Begin with SuperCID:***May no longer be necessary***
1) Get current cid information via;
fastboot oem readcid
Write down your current cid reading
2) Change your cid to 11111111 via;
fastboot oem writecid 11111111
(check cid again with fastboot oem readcid to varify)
3) Reboot to the bootloader
4) Following the reboot back to the bootloader
verify your cid is 11111111
And Then Install Rom Via:
5)Wipe /data; /cache; /system; Dalvik
6)Format /system; /data; /cache to f2fs -optional *Must use Elite Kernel for GPE 5.1*
7)Install Rom
8)Reboot
Remove GPE:***these are just my recommendations***
1) Revert CID via fastboot oem writecid (your stock cid ex: fastboot oem writecid VZW__001
2) Wipe everything /data, /cache, /system, /dalvik <-- Optional
*(suggested to use oem task commands)*
3) Format back to ext4 for everything if you changed to f2fs for any reason
4) Run ruu
If ruu doesn't work properly...
5) Run ruu a second time
Some General Tips​
-When typing a command like "fastboot flash recovery recoveryname.img" you can use the TAB key to
autocomplete a name or file directory... (This is true in just about every operating systems
command line or terminal interface) ex: if trying to go to C:\Windows and you're already in the
C:\ directory you simply need type "cd C:\w" and hit TAB and it should automatically complete the
field. If you happen to have a directory that comes before Windows alphabetically like "C:\Warez"
(not likely) hit Tab again and it will cycle through directories alphabetically.
Another example is I have twrp-2.8.5 and twrp-2.8.6 in my adb directory. So if it autocompletes
to "twrp-2.8.5.img", I hit tab again it will change to "twrp-2.8.6.img". In some instances you can
use this autocomplete feature to issue commands ie when using an apk decompiler/recompiler tool.
Instead of typing mkdir you can simply autotab to the correct command after typing "m" or "mk" etc.
-If you use the up arrow on your keyboard in Terminal/Command Prompt it will cycle through previous commands.
Example: When flashing firmware after "fastboot flash zip firmware.zip" when prompted to flash a second time you
can just hit UP Arrow on your keyboard and it will automatically go to your previous entry.
-I keep the latest RUU for my device in my adb/android studio (*/platform-tools) directory already
named "0P6BIMG.zip". This is a good practice simply because it streamlines the whole process so you
don't have to wait as a rather large file copies to said directory. I also keep a copy of said RUU
in a folder on my external sd-card. I do this so that if my computer, for whatever reason, was not
able to read the phones storage I can use the file manager in recovery to move it to root and RUU.
-If you have TiTanium Backup Pro you can set it to automatically update your apps. I like to keep an
updated copy of my apps on my external sd-card, my computer, and in cloud via GoogleDrive. This
makes restoring apps from a backup a painless process as I always have them available to me.
-I also keep a running backup of everything important to me on my computer. I have a folder
I've set up specifically for my running backups. Inside said folder I have a copy of my favorite
roms, my music, all the firmware for our device, the HBoot.zip(s), my pictures, all available RUUs,
an MD5 checking program, GApps packages, TWRP backups, TWRP .img(s), TWRP themes, and any other
tweaks/flashable.zips I find important. I highly suggest everyone who doesn't do this make this a
practice. It truly helps a lot.
EDIT: If someone wants me to upload the above as a .txt file I will.
Click to expand...
Click to collapse
That would be great in .txt format.

aaronpw0621 said:
That would be great in .txt format.
Click to expand...
Click to collapse
When I get home (about an hour) I'll upload a .txt of the commands.
HTC One (M8) CM12.1.1
Edit: Okay downloadable .txt file is in OP

jcole20 said:
When I get home (about an hour) I'll upload a .txt of the commands.
HTC One (M8) CM12.1.1
Edit: Okay downloadable .txt file is in OP
Click to expand...
Click to collapse
:good: :good:

@jcole20 a lot of your fastboot reflashing can be removed by the use of the HTC_fastboot I have posted in various places. It does it automatically

dottat said:
@jcole20 a lot of your fastboot reflashing can be removed by the use of the HTC_fastboot I have posted in various places. It does it automatically
Click to expand...
Click to collapse
Thanks @dottat I didn't know. I've only had to reflash once. And that was the first time I ran your ruu (5.0.1). Following that initial hiccup, everytime after it's completed successfully on the first try.
I'll check into that and note it in op. I just wanted to consolidate all the commands we commonly use for people who have trouble remembering them.
HTC One (M8) CM12.1.1
Edit: oh I didn't know you were talking about your ruu.exe(s) ... Yeah, I'm so used to using adb for everything. I've got your exe for lollipop but I've only run it once. (Prior to my pm about something lingering after a ruu) ... I still haven't figured that out BTW. I'll make note in the op that your exes make the ruu adb info obsolete. Thank you again for all your help and work.

jcole20 said:
Thanks @dottat I didn't know. I've only had to reflash once. And that was the first time I ran your ruu (5.0.1). Following that initial hiccup, everytime after it's completed successfully on the first try.
I'll check into that and note it in op. I just wanted to consolidate all the commands we commonly use for people who have trouble remembering them.
HTC One (M8) CM12.1.1
Edit: oh I didn't know you were talking about your ruu.exe(s) ... Yeah, I'm so used to using adb for everything. I've got your exe for lollipop but I've only run it once. (Prior to my pm about something lingering after a ruu) ... I still haven't figured that out BTW. I'll make note in the op that your exes make the ruu adb info obsolete. Thank you again for all your help and work.
Click to expand...
Click to collapse
No that's not what I am talking about. Lol
Download this. Unzip it and you will see what I mean
https://www.androidfilehost.com/?fid=95916177934554784

dottat said:
No that's not what I am talking about. Lol
Download this. Unzip it and you will see what I mean
https://www.androidfilehost.com/?fid=95916177934554784
Click to expand...
Click to collapse
Lol... okay. Why isn't this in your 5.0.1 ruu thread? I wish I had known about this a couple of weeks ago... Thanks though. I did a quick google search for htc_fastboot and what came up was a question you asked someone in one of your ruu threads. I went to the op and all I saw was the exe and ruu.zip so I assumed you were talking about the .exe. Hah

jcole20 said:
Lol... okay. Why isn't this in your 5.0.1 ruu thread? I wish I had known about this a couple of weeks ago... Thanks though. I did a quick google search for htc_fastboot and what came up was a question you asked someone in one of your ruu threads. I went to the op and all I saw was the exe and ruu.zip so I assumed you were talking about the .exe. Hah
Click to expand...
Click to collapse
Have you read the stickied thread in general section?

dottat said:
Have you read the stickied thread in general section?
Click to expand...
Click to collapse
To be honest dottat, I've read so much with regards to this phone in the last month since I got it I don't remember everything that I've read through. I think, with regards to your ruu's, I've mainly used your posted threads in the Verizon Android Development section. I linked your ruu's in the OP now and I used the stickied master list here, but I've only had this phone for a month so I never needed a 4.4.4 ruu (hence not needing to find that master list). Your lollipop ruu has been bumped somewhat regularly so it's the only one I've ever really looked through except when googling something and your 4.4.4 ruu in the same section has come up.

jcole20 said:
To be honest dottat, I've read so much with regards to this phone in the last month since I got it I don't remember everything that I've read through. I think, with regards to your ruu's, I've mainly used your posted threads in the Verizon Android Development section. I linked your ruu's in the OP now and I used the stickied master list here, but I've only had this phone for a month so I never needed a 4.4.4 ruu (hence not needing to find that master list). Your lollipop ruu has been bumped somewhat regularly so it's the only one I've ever really looked through except when googling something and your 4.4.4 ruu in the same section has come up.
Click to expand...
Click to collapse
Here's the post....
http://forum.xda-developers.com/showthread.php?p=56890497
I just gave you the latest and greatest above. Its the awesome sauce man.

dottat said:
Here's the post....
http://forum.xda-developers.com/showthread.php?p=56890497
I just gave you the latest and greatest above. Its the awesome sauce man.
Click to expand...
Click to collapse
Thank you! Heh, I've got the .exes and .zips of your 4.4.4 and 5.0.1 ruus saved. I will probably ruu back to stock again using the above just because... I've still never figured out what broke audiofx for me even after reverting to stock via your ruus. It's been driving me nuts.
HTC One (M8) CM12.1.1
Edit: I'm thinking I flashed V4A via a .zip and didn't realize it, so audiofx wasn't working, it was working as the drivers for audiofx and audiofx was working as the gui for v4a. That's the only explanation I can think of, because your ruu's have been great and I know they are working to revert me completely to stock.
Edit 2: I went ahead and ran a ruu with your updated adb file(s). As usual went off without a hitch and everything seems perfect... booting into my rom of choice now. As usual everything is perfect dottat... thanks!