• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GUIDE][RECOVERY] Rooting Guide + TWRP 2.8.7.0 Download (Beta)

Search This thread

DarkRazorZ

Senior Member
Mar 17, 2012
444
178
Gunsan, South Korea
www.youtube.com
Disclaimer: You must be S-OFF and on the latest update in order to do the following. This is because the current build of TWRP requires you to flash it to the boot partition, TWRP will not work as a normal recovery (ie flashing it to the recovery partition).
There is currently no known way to S-OFF without using an unlocking device such as a JTAG or something like XTC2Clip. Sunshine will likely work if you are able to obtain root, but there is no known method of obtaining root via an exploit for the Butterfly 3 at the moment.

To check if you are S-OFF, power off the device then hold Power + Volume Down. This will boot into Download Mode where you can view if you are S-OFF or not. I am not sure if you're required to also have your bootloader unlocked in order to root, but one individual I helped was not able to root without it.
Note: If you decide to unlock your bootloader, please be aware that it will reset your device to factory settings as well as delete all photos, music, videos and any other files you have saved to your internal storage. Please move what you can to your SD card or your PC if you are not willing to lose these files.
The following command will unlock your bootloader via fastboot:
Code:
fastboot oem unlock

TWRP Information:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
AgsV.png
WujW.png


CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option -- more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)

Additional Notes:
We will consider this a "beta" build as it is not used in the manner you would normally use it on other devices. The touch screen will not function if you try to flash this as a standard recovery. It will, however, fully function when flashed to the boot partition. Please take caution when flashing anything to your boot partition!

The Github for this build of TWRP can be found here.

More information can be found on the official TWRP website here.

Rooting Your Phone:
Please download the files found at the bottom of this thread. You WILL require a PC for this. Please be sure you have the latest fastboot drivers installed for your device. The generic fastboot drivers should function as well. Fastboot drivers can be found here.

Step 1:
Download the files found at the bottom of this thread. "b3 recovery.zip" contains everything you will need for this process, minus the SuperSU zip (which can also be found at the bottom of this thread).

Step 2:
Extract the contents of "b3 recovery.zip" into a folder. Place the SuperSU zip somewhere on your device, either on an SD Card or in the internal storage.

Step 3:
Power off your device completely without a USB cable plugged in. Next, hold Power + Volume Down until you boot into "Download Mode". Once you are in "Download Mode", plug your phone into your computer via USB.

Step 4:
Open Command Prompt as Administrator in the folder you extracted the contents of "b3 recovery.zip" to. Type the following command to verify that your phone is connected to fastboot:
Code:
fastboot devices
If nothing shows up, or it says "OFFLINE", please make sure your fastboot drivers are properly installed. You will not be able to continue if your device is not connected.

Step 5:
Type the following command:
Code:
fastboot flash boot b3twrp.img
This should successfully flash TWRP to your boot partition. Now type the following command:
Code:
fastboot reboot
Assuming everything went well, you should now have booted into TWRP.

Step 6:
Note: It is highly recommended that you do a full backup of your device before continuing. This will ensure that you are able to restore your device should anything go wrong and it will also allow you to receive OTA updates in the future.
Now that you are in TWRP, install/flash the SuperSU zip you placed on your device. Once it has completed, wipe your cache. Now reboot into "Download Mode".

Step 7:
Once you are back in "Download Mode", type the following command:
Code:
fastboot flash boot stockboot.img
It should flash successfully. Reboot your device.

Assuming everything went well, you should now be rooted! The initial boot will take some time and you may notice some slowdown at first but rest assured that your phone is fine and will function normally.


Downloads:
Fastboot/ADB, TWRP and stock boot image: b3 recovery.zip
SuperSU-v2.46.zip

Credits:
A big thanks and props to @tomkins0752 and @boa19861105 for getting this build of TWRP working for our phones. Without them, we would not have root.

If anyone has any suggestions or sees any issue with this post, please let me know and I will correct any errors.
 

thuandiennang

Senior Member
Aug 16, 2011
52
11
Hà Nội
Disclaimer: You must be S-OFF and on the latest update in order to do the following. This is because the current build of TWRP requires you to flash it to the boot partition, TWRP will not work as a normal recovery (ie flashing it to the recovery partition).
There is currently no known way to S-OFF without using an unlocking device such as a JTAG or something like XTC2Clip. Sunshine will likely work if you are able to obtain root, but there is no known method of obtaining root via an exploit for the Butterfly 3 at the moment.

To check if you are S-OFF, power off the device then hold Power + Volume Down. This will boot into Download Mode where you can view if you are S-OFF or not. I am not sure if you're required to also have your bootloader unlocked in order to root, but one individual I helped was not able to root without it.
Note: If you decide to unlock your bootloader, please be aware that it will reset your device to factory settings as well as delete all photos, music, videos and any other files you have saved to your internal storage. Please move what you can to your SD card or your PC if you are not willing to lose these files.
The following command will unlock your bootloader via fastboot:
Code:
fastboot oem unlock

TWRP Information:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
AgsV.png
WujW.png


CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option -- more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)

Additional Notes:
We will consider this a "beta" build as it is not used in the manner you would normally use it on other devices. The touch screen will not function if you try to flash this as a standard recovery. It will, however, fully function when flashed to the boot partition. Please take caution when flashing anything to your boot partition!

The Github for this build of TWRP can be found here.

More information can be found on the official TWRP website here.

Rooting Your Phone:
Please download the files found at the bottom of this thread. You WILL require a PC for this. Please be sure you have the latest fastboot drivers installed for your device. The generic fastboot drivers should function as well. Fastboot drivers can be found here.

Step 1:
Download the files found at the bottom of this thread. "b3 recovery.zip" contains everything you will need for this process, minus the SuperSU zip (which can also be found at the bottom of this thread).

Step 2:
Extract the contents of "b3 recovery.zip" into a folder. Place the SuperSU zip somewhere on your device, either on an SD Card or in the internal storage.

Step 3:
Power off your device completely without a USB cable plugged in. Next, hold Power + Volume Down until you boot into "Download Mode". Once you are in "Download Mode", plug your phone into your computer via USB.

Step 4:
Open Command Prompt as Administrator in the folder you extracted the contents of "b3 recovery.zip" to. Type the following command to verify that your phone is connected to fastboot:
Code:
fastboot devices
If nothing shows up, or it says "OFFLINE", please make sure your fastboot drivers are properly installed. You will not be able to continue if your device is not connected.

Step 5:
Type the following command:
Code:
fastboot flash boot b3twrp.img
This should successfully flash TWRP to your boot partition. Now type the following command:
Code:
fastboot reboot
Assuming everything went well, you should now have booted into TWRP.

Step 6:
Note: It is highly recommended that you do a full backup of your device before continuing. This will ensure that you are able to restore your device should anything go wrong and it will also allow you to receive OTA updates in the future.
Now that you are in TWRP, install/flash the SuperSU zip you placed on your device. Once it has completed, wipe your cache. Now reboot into "Download Mode".

Step 7:
Once you are back in "Download Mode", type the following command:
Code:
fastboot flash boot stockboot.img
It should flash successfully. Reboot your device.

Assuming everything went well, you should now be rooted! The initial boot will take some time and you may notice some slowdown at first but rest assured that your phone is fine and will function normally.


Downloads:
Fastboot/ADB, TWRP and stock boot image: b3 recovery.zip
SuperSU-v2.46.zip

Credits:
A big thanks and props to @tomkins0752 and @boa19861105 for getting this build of TWRP working for our phones. Without them, we would not have root.

If anyone has any suggestions or sees any issue with this post, please let me know and I will correct any errors.
htc htv31 (butterfly 3 japan)
s-off, super cid, unlockbootloader ok by xtc2clip.
flash twrp.img ok, boot to recovery mode, twrp 2.8.7.0 (BOA-Butterfly3)
.. but i can't touch/swipe..
how to fix ?


_log_

C:\Documents and Settings\Admin\My Documents\b3 recovery>cmd
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Admin\My Documents\b3 recovery>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_b3uhl
(bootloader) version: 1.0
(bootloader) imei: 357763---
(bootloader) version-main: 1.03.970.7
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PL210000
(bootloader) cid: 11111111
all:
finished. total time: 0.016s

C:\Documents and Settings\Admin\My Documents\b3 recovery>fastboot flash recovery
b3twrp.img
target reported max download size of 800000000 bytes
sending 'recovery' (36744 KB)...
OKAY [ 2.953s]
writing 'recovery'...
(bootloader) HOSD CL#561421
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.859s]
finished. total time: 5.812s



C:\Documents and Settings\Admin\My Documents\b3 recovery>adb shell
error: device not found

C:\Documents and Settings\Admin\My Documents\b3 recovery>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name

179 0 30535680 mmcblk0
179 1 16 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 40960 mmcblk0p5
179 6 2015 mmcblk0p6
179 7 256 mmcblk0p7
179 8 24255 mmcblk0p8
179 9 512 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 96 mmcblk0p11
179 12 2048 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 10240 mmcblk0p15
259 0 1024 mmcblk0p16
259 1 1024 mmcblk0p17
259 2 1024 mmcblk0p18
259 3 1024 mmcblk0p19
259 4 1024 mmcblk0p20
259 5 1024 mmcblk0p21
259 6 1024 mmcblk0p22
259 7 1024 mmcblk0p23
259 8 1024 mmcblk0p24
259 9 1536 mmcblk0p25
259 10 60417 mmcblk0p26
259 11 20480 mmcblk0p27
259 12 1 mmcblk0p28
259 13 1844 mmcblk0p29
259 14 3243 mmcblk0p30
259 15 22528 mmcblk0p31
259 16 10240 mmcblk0p32
259 17 1024 mmcblk0p33
259 18 1536 mmcblk0p34
259 19 1536 mmcblk0p35
259 20 20480 mmcblk0p36
259 21 30720 mmcblk0p37
259 22 256 mmcblk0p38
259 23 16 mmcblk0p39
259 24 64 mmcblk0p40
259 25 1024 mmcblk0p41
259 26 1 mmcblk0p42
259 27 8 mmcblk0p43
259 28 512 mmcblk0p44
259 29 128 mmcblk0p45
259 30 1024 mmcblk0p46
259 31 10 mmcblk0p47
259 32 1281 mmcblk0p48
259 33 512 mmcblk0p49
259 34 2048 mmcblk0p50
259 35 20480 mmcblk0p51
259 36 256 mmcblk0p52
259 37 128 mmcblk0p53
259 38 128 mmcblk0p54
259 39 128 mmcblk0p55
259 40 128 mmcblk0p56
259 41 128 mmcblk0p57
259 42 128 mmcblk0p58
259 43 128 mmcblk0p59
259 44 128 mmcblk0p60
259 45 8192 mmcblk0p61
259 46 10240 mmcblk0p62
259 47 12316 mmcblk0p63
259 48 65536 mmcblk0p64
259 49 65536 mmcblk0p65
259 50 65536 mmcblk0p66
259 51 262144 mmcblk0p67
259 52 4587520 mmcblk0p68
259 53 24641536 mmcblk0p69
259 54 296960 mmcblk0p70
259 55 20480 mmcblk0p71
259 56 61440 mmcblk0p72
179 16 4096 mmcblk0rpmb
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00004000 00000200 "board_info"
mmcblk0p2: 00400000 00000200 "pg1fs"
mmcblk0p3: 00100000 00000200 "sbl1"
mmcblk0p4: 00100000 00000200 "pmic"
mmcblk0p5: 02800000 00000200 "dummy"
mmcblk0p6: 001f7c00 00000200 "reserve_1"
mmcblk0p7: 00040000 00000200 "mfg"
mmcblk0p8: 017afc00 00000200 "pg2fs"
mmcblk0p9: 00080000 00000200 "rpm"
mmcblk0p10: 00200000 00000200 "tz"
mmcblk0p11: 00018000 00000200 "sdi"
mmcblk0p12: 00200000 00000200 "hyp"
mmcblk0p13: 00100000 00000200 "aboot"
mmcblk0p14: 00a00000 00000200 "tool_diag"
mmcblk0p15: 00a00000 00000200 "sp1"
mmcblk0p16: 00100000 00000200 "ddr"
mmcblk0p17: 00100000 00000200 "rfg_0"
mmcblk0p18: 00100000 00000200 "rfg_1"
mmcblk0p19: 00100000 00000200 "rfg_2"
mmcblk0p20: 00100000 00000200 "rfg_3"
mmcblk0p21: 00100000 00000200 "rfg_4"
mmcblk0p22: 00100000 00000200 "rfg_5"
mmcblk0p23: 00100000 00000200 "rfg_6"
mmcblk0p24: 00100000 00000200 "rfg_7"
mmcblk0p25: 00180000 00000200 "fsg"
mmcblk0p26: 03b00400 00000200 "radio"
mmcblk0p27: 01400000 00000200 "adsp"
mmcblk0p28: 00000400 00000200 "limits"
mmcblk0p29: 001cd000 00000200 "camera"
mmcblk0p30: 0032ac00 00000200 "reserve_2"
mmcblk0p31: 01600000 00000200 "persist"
mmcblk0p32: 00a00000 00000200 "ramdump"
mmcblk0p33: 00100000 00000200 "misc"
mmcblk0p34: 00180000 00000200 "modem_st1"
mmcblk0p35: 00180000 00000200 "modem_st2"
mmcblk0p36: 01400000 00000200 "fataldevlog"
mmcblk0p37: 01e00000 00000200 "devlog"
mmcblk0p38: 00040000 00000200 "pdata"
mmcblk0p39: 00004000 00000200 "control"
mmcblk0p40: 00010000 00000200 "extra"
mmcblk0p41: 00100000 00000200 "cdma_record"
mmcblk0p42: 00000400 00000200 "fsc"
mmcblk0p43: 00002000 00000200 "ssd"
mmcblk0p44: 00080000 00000200 "sensor_hub"
mmcblk0p45: 00020000 00000200 "sec"
mmcblk0p46: 00100000 00000200 "abootbak"
mmcblk0p47: 00002800 00000200 "cir_img"
mmcblk0p48: 00140400 00000200 "local"
mmcblk0p49: 00080000 00000200 "frp"
mmcblk0p50: 00200000 00000200 "cpe"
mmcblk0p51: 01400000 00000200 "carrier"
mmcblk0p52: 00040000 00000200 "skylink"
mmcblk0p53: 00020000 00000200 "rfg_8"
mmcblk0p54: 00020000 00000200 "rfg_9"
mmcblk0p55: 00020000 00000200 "rfg_10"
mmcblk0p56: 00020000 00000200 "rfg_11"
mmcblk0p57: 00020000 00000200 "rfg_12"
mmcblk0p58: 00020000 00000200 "rfg_13"
mmcblk0p59: 00020000 00000200 "rfg_14"
mmcblk0p60: 00020000 00000200 "rfg_15"
mmcblk0p61: 00800000 00000200 "absolute"
mmcblk0p62: 00a00000 00000200 "battery"
mmcblk0p63: 00c07000 00000200 "reserve"
mmcblk0p64: 04000000 00000200 "hosd"
mmcblk0p65: 04000000 00000200 "boot"
mmcblk0p66: 04000000 00000200 "recovery"
mmcblk0p67: 10000000 00000200 "cache"
mmcblk0p68: 18000000 00000200 "system"
mmcblk0p69: e0000000 00000200 "userdata"
mmcblk0p70: 12200000 00000200 "apppreload"
mmcblk0p71: 01400000 00000200 "nfc_record"
mmcblk0p72: 03c00000 00000200 "cota"
~ # ←[6n
C:\Documents and Settings\Admin\My Documents\b3 recovery>
 
Last edited:

DarkRazorZ

Senior Member
Mar 17, 2012
444
178
Gunsan, South Korea
www.youtube.com
The recovery has to be flashed to the boot partition. This is mentioned in the disclaimer at the beginning of the post. The b3 recovery zip contains the stock boot.img for the latest update so you can flash it after you are done with the recovery. Please back up your boot.img if you are not on the latest update.
 

wumilun

Member
Apr 9, 2011
13
0
I have tried three times with your method strictly, but there is no change at all with this phone. There is still no supersu. Could you tell me why?
HTV31 s-off by xtc2
 
Last edited:

DarkRazorZ

Senior Member
Mar 17, 2012
444
178
Gunsan, South Korea
www.youtube.com
I have tried three times with your method strictly, but there is no change at all with this phone. There is still no supersu. Could you tell me why?
HTV31 s-off by xtc2

There's no "SuperSU Install" or SuperSU app? I would say try installing it from the Play Store to see if that fixes anything but it should be working fine after flashing the SuperSU binary.
 

orb_selektor

Forum Moderator - Welcomer
Staff member
XDA App Taskforce
Disclaimer: You must be S-OFF and on the latest update in order to do the following. This is because the current build of TWRP requires you to flash it to the boot partition, TWRP will not work as a normal recovery (ie flashing it to the recovery partition).
There is currently no known way to S-OFF without using an unlocking device such as a JTAG or something like XTC2Clip. Sunshine will likely work if you are able to obtain root, but there is no known method of obtaining root via an exploit for the Butterfly 3 at the moment.

.

Hey buddy, tried all process just as you describe, all went ok, no errors, all as you mentioned, but at the end my device still says Not Rooted.
Only thing I didnt, do is unlock bootloader via HTC as I was not able to do it but Im S-OFF.

HTCDev error> Error Code: 170.
Error Reason: CID Not Allowed.

Any light is welcome.

Thanks
 
Last edited:

DarkRazorZ

Senior Member
Mar 17, 2012
444
178
Gunsan, South Korea
www.youtube.com
Hey buddy, tried all process just as you describe, all went ok, no errors, all as you mentioned, but at the end my device still says Not Rooted.
Only thing I didnt, do is unlock bootloader via HTC as I was not able to do it but Im S-OFF.

HTCDev error> Error Code: 170.
Error Reason: CID Not Allowed.

Any light is welcome.

Thanks

I'm not sure why this issue is occurring for some but not others. A few of us our rooted via this method.

You can't use HTCDev to unlock the bootloader, you have to unlock your bootloader via fastboot.
 
  • Like
Reactions: orb_selektor

orb_selektor

Forum Moderator - Welcomer
Staff member
XDA App Taskforce
I'm not sure why this issue is occurring for some but not others. A few of us our rooted via this method.

You can't use HTCDev to unlock the bootloader, you have to unlock your bootloader via fastboot.

Have read more and will need to change my CID via fastboot, then I am able to unlock via HTC, as i am not sure how to unlock via fastboot.
Arigato for your answer :)
 

DarkRazorZ

Senior Member
Mar 17, 2012
444
178
Gunsan, South Korea
www.youtube.com
Have read more and will need to change my CID via fastboot, then I am able to unlock via HTC, as i am not sure how to unlock via fastboot.
Arigato for your answer :)

If you type "oem unlock bootloader" in fastboot mode it should prompt you to unlock, very easy to do. Either way, unlocking your bootloader will wipe your phone's contents though so make sure you back everything up first
 

orb_selektor

Forum Moderator - Welcomer
Staff member
XDA App Taskforce
If you type "oem unlock bootloader" in fastboot mode it should prompt you to unlock, very easy to do. Either way, unlocking your bootloader will wipe your phone's contents though so make sure you back everything up first

Actually used the command [fastboot oem writecid 11111111] and all went ok! Now rooted.
You may want to include that info on your first post :)

Many thanks
 

frosticfire

Member
Jan 12, 2016
9
0
Singapore
Hi, any kind soul able to share their backup of the HTV31 stock recovery? My phone was already rooted when I got it with no backup of the stock recovery so I have no way to get OTA updates :'(
 

jajarita

Member
Dec 23, 2011
10
0
Hi there, I've been trying to unlock the bootloader via fastboot when phone is in download mode but none of the commands worked for me... adb devices shows that my phone is connected.
I've tried:
- fastboot oem writecid 11111111
- oem unlock bootloader
- fastboot oem unlock
- fastboot flashing unlock
Keep getting FAILED <remote: unknown command>

Many thanks in advance :)

Edit: also tried in bootloader mode, and nothing.
Edit: when trying fastboot oem unlock when phone is switched on to normal mode, I'm stuck on <waiting for device>
 
Last edited:

nielspieleke

Member
Aug 22, 2013
39
2
If I'm not mistaken, you actually only need an unlocked bootloader.
An unlocked bootloader will give you r/w access of the boot, system and recovery partitions.
r/w access of the boot partition is needed for this guide.
S-off is not needed to get boot partition r/w access.
So that is why some people couldn't get it working without an unlocked bootloader.
I hope someone can confirm this!
 

ms_dev

New member
Apr 4, 2016
2
0
still not rooted

Hi,

I am very new to this forum, so thank you all for your time and guidance.
I have a HTV31SWA. From the download mode I see that I am locked, S-OFF, with CID 11111111 (I suppose I have the bootloader unlocked). The OS is 1.11.970.1.
I have tried to follow the guide below, I am successfull in all the steps (at least, I get no errors) but I get not root access. Actually I am stricly following the guide steps so I do not understand what I can do more. Any help would be very much appreciated.
Actually the phone comes with restrictions in the GPS activation, wifi thetering and other limitation. That's why it is vital to me to get the root access!
Thank you very much.

Disclaimer: You must be S-OFF and on the latest update in order to do the following. This is because the current build of TWRP requires you to flash it to the boot partition, TWRP will not work as a normal recovery (ie flashing it to the recovery partition).
There is currently no known way to S-OFF without using an unlocking device such as a JTAG or something like XTC2Clip. Sunshine will likely work if you are able to obtain root, but there is no known method of obtaining root via an exploit for the Butterfly 3 at the moment.

To check if you are S-OFF, power off the device then hold Power + Volume Down. This will boot into Download Mode where you can view if you are S-OFF or not. I am not sure if you're required to also have your bootloader unlocked in order to root, but one individual I helped was not able to root without it.
Note: If you decide to unlock your bootloader, please be aware that it will reset your device to factory settings as well as delete all photos, music, videos and any other files you have saved to your internal storage. Please move what you can to your SD card or your PC if you are not willing to lose these files.
The following command will unlock your bootloader via fastboot:
Code:
fastboot oem unlock

TWRP Information:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
AgsV.png
WujW.png


CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option -- more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)

Additional Notes:
We will consider this a "beta" build as it is not used in the manner you would normally use it on other devices. The touch screen will not function if you try to flash this as a standard recovery. It will, however, fully function when flashed to the boot partition. Please take caution when flashing anything to your boot partition!

The Github for this build of TWRP can be found here.

More information can be found on the official TWRP website here.

Rooting Your Phone:
Please download the files found at the bottom of this thread. You WILL require a PC for this. Please be sure you have the latest fastboot drivers installed for your device. The generic fastboot drivers should function as well. Fastboot drivers can be found here.

Step 1:
Download the files found at the bottom of this thread. "b3 recovery.zip" contains everything you will need for this process, minus the SuperSU zip (which can also be found at the bottom of this thread).

Step 2:
Extract the contents of "b3 recovery.zip" into a folder. Place the SuperSU zip somewhere on your device, either on an SD Card or in the internal storage.

Step 3:
Power off your device completely without a USB cable plugged in. Next, hold Power + Volume Down until you boot into "Download Mode". Once you are in "Download Mode", plug your phone into your computer via USB.

Step 4:
Open Command Prompt as Administrator in the folder you extracted the contents of "b3 recovery.zip" to. Type the following command to verify that your phone is connected to fastboot:
Code:
fastboot devices
If nothing shows up, or it says "OFFLINE", please make sure your fastboot drivers are properly installed. You will not be able to continue if your device is not connected.

Step 5:
Type the following command:
Code:
fastboot flash boot b3twrp.img
This should successfully flash TWRP to your boot partition. Now type the following command:
Code:
fastboot reboot
Assuming everything went well, you should now have booted into TWRP.

Step 6:
Note: It is highly recommended that you do a full backup of your device before continuing. This will ensure that you are able to restore your device should anything go wrong and it will also allow you to receive OTA updates in the future.
Now that you are in TWRP, install/flash the SuperSU zip you placed on your device. Once it has completed, wipe your cache. Now reboot into "Download Mode".

Step 7:
Once you are back in "Download Mode", type the following command:
Code:
fastboot flash boot stockboot.img
It should flash successfully. Reboot your device.

Assuming everything went well, you should now be rooted! The initial boot will take some time and you may notice some slowdown at first but rest assured that your phone is fine and will function normally.


Downloads:
Fastboot/ADB, TWRP and stock boot image: b3 recovery.zip
SuperSU-v2.46.zip

Credits:
A big thanks and props to @tomkins0752 and @boa19861105 for getting this build of TWRP working for our phones. Without them, we would not have root.

If anyone has any suggestions or sees any issue with this post, please let me know and I will correct any errors.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    Disclaimer: You must be S-OFF and on the latest update in order to do the following. This is because the current build of TWRP requires you to flash it to the boot partition, TWRP will not work as a normal recovery (ie flashing it to the recovery partition).
    There is currently no known way to S-OFF without using an unlocking device such as a JTAG or something like XTC2Clip. Sunshine will likely work if you are able to obtain root, but there is no known method of obtaining root via an exploit for the Butterfly 3 at the moment.

    To check if you are S-OFF, power off the device then hold Power + Volume Down. This will boot into Download Mode where you can view if you are S-OFF or not. I am not sure if you're required to also have your bootloader unlocked in order to root, but one individual I helped was not able to root without it.
    Note: If you decide to unlock your bootloader, please be aware that it will reset your device to factory settings as well as delete all photos, music, videos and any other files you have saved to your internal storage. Please move what you can to your SD card or your PC if you are not willing to lose these files.
    The following command will unlock your bootloader via fastboot:
    Code:
    fastboot oem unlock

    TWRP Information:
    Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
    AgsV.png
    WujW.png


    CHANGELOG for 2.8.7.0:
    -Initial ground work for software drawn keyboard (_that)
    -Fix handling of wiping internal storage on datamedia devices (xuefer)
    -Allow DataManager to set and read values from the system properties (xuefer)
    -Fix crash when taking screenshots on arm64 devices (xuefer)
    -Fix error message after an ORS script completes (Dees_Troy)
    -Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
    -Add system read only option -- more details below (Dees_Troy)
    -Add resize2fs and GUI option to run resize2fs (Dees_Troy)
    -Fix crash loop caused by empty lines in AOSP recovery command file (_that)
    -Prevent duplicate page overlays such as multiple lock screens (mdmower)

    Additional Notes:
    We will consider this a "beta" build as it is not used in the manner you would normally use it on other devices. The touch screen will not function if you try to flash this as a standard recovery. It will, however, fully function when flashed to the boot partition. Please take caution when flashing anything to your boot partition!

    The Github for this build of TWRP can be found here.

    More information can be found on the official TWRP website here.

    Rooting Your Phone:
    Please download the files found at the bottom of this thread. You WILL require a PC for this. Please be sure you have the latest fastboot drivers installed for your device. The generic fastboot drivers should function as well. Fastboot drivers can be found here.

    Step 1:
    Download the files found at the bottom of this thread. "b3 recovery.zip" contains everything you will need for this process, minus the SuperSU zip (which can also be found at the bottom of this thread).

    Step 2:
    Extract the contents of "b3 recovery.zip" into a folder. Place the SuperSU zip somewhere on your device, either on an SD Card or in the internal storage.

    Step 3:
    Power off your device completely without a USB cable plugged in. Next, hold Power + Volume Down until you boot into "Download Mode". Once you are in "Download Mode", plug your phone into your computer via USB.

    Step 4:
    Open Command Prompt as Administrator in the folder you extracted the contents of "b3 recovery.zip" to. Type the following command to verify that your phone is connected to fastboot:
    Code:
    fastboot devices
    If nothing shows up, or it says "OFFLINE", please make sure your fastboot drivers are properly installed. You will not be able to continue if your device is not connected.

    Step 5:
    Type the following command:
    Code:
    fastboot flash boot b3twrp.img
    This should successfully flash TWRP to your boot partition. Now type the following command:
    Code:
    fastboot reboot
    Assuming everything went well, you should now have booted into TWRP.

    Step 6:
    Note: It is highly recommended that you do a full backup of your device before continuing. This will ensure that you are able to restore your device should anything go wrong and it will also allow you to receive OTA updates in the future.
    Now that you are in TWRP, install/flash the SuperSU zip you placed on your device. Once it has completed, wipe your cache. Now reboot into "Download Mode".

    Step 7:
    Once you are back in "Download Mode", type the following command:
    Code:
    fastboot flash boot stockboot.img
    It should flash successfully. Reboot your device.

    Assuming everything went well, you should now be rooted! The initial boot will take some time and you may notice some slowdown at first but rest assured that your phone is fine and will function normally.


    Downloads:
    Fastboot/ADB, TWRP and stock boot image: b3 recovery.zip
    SuperSU-v2.46.zip

    Credits:
    A big thanks and props to @tomkins0752 and @boa19861105 for getting this build of TWRP working for our phones. Without them, we would not have root.

    If anyone has any suggestions or sees any issue with this post, please let me know and I will correct any errors.
    1
    Hey buddy, tried all process just as you describe, all went ok, no errors, all as you mentioned, but at the end my device still says Not Rooted.
    Only thing I didnt, do is unlock bootloader via HTC as I was not able to do it but Im S-OFF.

    HTCDev error> Error Code: 170.
    Error Reason: CID Not Allowed.

    Any light is welcome.

    Thanks

    I'm not sure why this issue is occurring for some but not others. A few of us our rooted via this method.

    You can't use HTCDev to unlock the bootloader, you have to unlock your bootloader via fastboot.
    1
    [Update] This Guide is Now Outdated

    New guide compatible with all updates on this phone whether Taiwanese or Japanese, Lollipop or Marshmallow.
    If you have used this guide on marshmallow and couldnt reboot, flash this to boot in download mode, its the marshmallow boot image.
    https://drive.google.com/open?id=0B6qqU5WVQ2khdzYwajhNUGtkd2s