So I just got a brand new HTC Evo replacement because my old one had power button issues.
I tried using Universal AutoRoot 2.5. CMD closed and I got this output:
"------------ AutoRoot.bat Begin - v2.5 - Tue 06/07/2011 23:33:14.63 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Mark\Desktop\AutoRoot_v2.5\'. Admin='true'
Clearing Temp Files...
The directory name is invalid.
---------
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
---------
Phone SN is HT15AHL06321
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
'check.bat mtd' returned 'old'
MTD data being saved for phone 'HT15AHL06321'
'dev: size erasesize name mtd0: 00c00000 00020000 "wimax" mtd1: 000a0000 00020000 "misc" mtd2: 00480000 00020000 "recovery" mtd3: 00300000 00020000 "boot" mtd4: 15e00000 00020000 "system" mtd5: 0a000000 00020000 "cache" mtd6: 1aba0000 00020000 "userdata" '
EVO Branding 'sprint'
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 70 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1593 KB/s (767044 bytes in 0.470s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
1570 KB/s (655360 bytes in 0.407s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
1255 KB/s (225014 bytes in 0.175s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
1159 KB/s (225551 bytes in 0.190s)
Dumping WiMAX partition...
rm failed for -s, Read-only file system
1522 KB/s (12582912 bytes in 8.070s)
WiMAX partition saved as 'HT15AHL06321_wimax.img'
Backing up Apps...
pull: building file list...
0 files pulled. 0 files skipped.
The system cannot find the path specified.
Flashing misc partition...
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version 'ECHO'
Version Major 'ECHO'
Version Minor '' "
----------------------------------------
Now everytime i try to use my phone while it's on:
It doesnt charge while its on
I cant see SD card within the stock ROM
Phone constantly resets after about a minute
However in bootloader i can see the SD card, and the phone charges while its off. I ran the 3.70 RUU which went smoothly, however it did not fix anything =/
Any other ideas? is there a reason why my AutoRoot failed? I've rooted many HTC evo's and never had this problem/problems.
bigblueshock said:
So I just got a brand new HTC Evo replacement because my old one had power button issues.
I tried using Universal AutoRoot 2.5. CMD closed and I got this output:
"------------ AutoRoot.bat Begin - v2.5 - Tue 06/07/2011 23:33:14.63 ------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Working Directory is 'C:\Users\Mark\Desktop\AutoRoot_v2.5\'. Admin='true'
Clearing Temp Files...
The directory name is invalid.
---------
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
INFO: No tasks are running which match the specified criteria.
---------
Phone SN is HT15AHL06321
PING ADB State Changed '1' out of '0'. ADB State is 'device' expected 'device'
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
'check.bat mtd' returned 'old'
MTD data being saved for phone 'HT15AHL06321'
'dev: size erasesize name mtd0: 00c00000 00020000 "wimax" mtd1: 000a0000 00020000 "misc" mtd2: 00480000 00020000 "recovery" mtd3: 00300000 00020000 "boot" mtd4: 15e00000 00020000 "system" mtd5: 0a000000 00020000 "cache" mtd6: 1aba0000 00020000 "userdata" '
EVO Branding 'sprint'
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 70 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1593 KB/s (767044 bytes in 0.470s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
1570 KB/s (655360 bytes in 0.407s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
1255 KB/s (225014 bytes in 0.175s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
1159 KB/s (225551 bytes in 0.190s)
Dumping WiMAX partition...
rm failed for -s, Read-only file system
1522 KB/s (12582912 bytes in 8.070s)
WiMAX partition saved as 'HT15AHL06321_wimax.img'
Backing up Apps...
pull: building file list...
0 files pulled. 0 files skipped.
The system cannot find the path specified.
Flashing misc partition...
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version 'ECHO'
Version Major 'ECHO'
Version Minor '' "
----------------------------------------
Now everytime i try to use my phone while it's on:
It doesnt charge while its on
I cant see SD card within the stock ROM
Phone constantly resets after about a minute
However in bootloader i can see the SD card, and the phone charges while its off. I ran the 3.70 RUU which went smoothly, however it did not fix anything =/
Any other ideas? is there a reason why my AutoRoot failed? I've rooted many HTC evo's and never had this problem/problems.
Click to expand...
Click to collapse
Well, I unfortunately don't have any experience with the Auto Root method. Hopefully xHausx will chime in here. Out of curiosity, your replacement phone did indeed have 2.2 on it, right? Because if it was updated to the OTA 2.3.3 that root method won't work. What is your software and hboot version?
Perhaps try running the RUU again?
I believe there is a thread around by Calkulin which addresses the issue of the phone not reading the sd card and not charging. I will see if I can dig that up for you. Good luck.
EDIT: Here is that thread by calkulin. I'm not sure if this will be able to help you out or not, but you can go through it anyways. When you boot to your bootloader, does it show S on or S off? What is the version number?
Flashing misc partition...
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
Click to expand...
Click to collapse
Your phone had some bad blocks there, that's strange for a new one. I can help you try to fix it but tbh your best bet is to run the 3.70 ruu and take it back for another. Otherwise odds are it'll start doing this again somewhere down the line.
xHausx said:
Your phone had some bad blocks there, that's strange for a new one. I can help you try to fix it but tbh your best bet is to run the 3.70 ruu and take it back for another. Otherwise odds are it'll start doing this again somewhere down the line.
Click to expand...
Click to collapse
Thanks Haus. Yea very odd... It's a brand new sealed 0004 model. I hope it's just luck of the straw. I'm going to head back to sprint later and get it replaced again. I just hope not all the new 0004's are like this. They dont have any refurbs in stock so they had to send me a brand new one.
bigblueshock said:
Thanks Haus. Yea very odd... It's a brand new sealed 0004 model. I hope it's just luck of the straw. I'm going to head back to sprint later and get it replaced again. I just hope not all the new 0004's are like this. They dont have any refurbs in stock so they had to send me a brand new one.
Click to expand...
Click to collapse
You should be good with another one, I've only had maybe 4 or 5 people have this happen before and up until now they were all refurbs. Just luck of the draw I guess.
edit: btw that speedtest result is sick, I would love to have a ping like that
The phone had stock 3.70 2.2 froyo. Phone is s-on with 2.10 bootloader, never got that far to get it s off
And yeah, too bad i just graduated from school, no more 100mbit pipe for me, was nice while it lasted
bigblueshock said:
The phone had stock 3.70 2.2 froyo. Phone is s-on with 2.10 bootloader, never got that far to get it s off
And yeah, too bad i just graduated from school, no more 100mbit pipe for me, was nice while it lasted
Click to expand...
Click to collapse
2.10 bootloader should work, it is the 2.19 one i believe that is locked.
So sprint swapped out the phone at the store. I'm pretty excited, he gave me a brand new White evo =)
I got home and autoroot worked flawlessly! Thanks again Haus for all your support and easy rooting techniques.
I'm not sure if this is the possible reason for my old phone bricking like that, but I'd like to share some knowledge.
My original 0004 model that sprint sent me was brand new, as well as the white evo 0004 sprint gave me was also brand new. While attempting to root the first replacement, 'check.bat mtd' returned 'old'. The second replacement white evo returned as "new". Not that i think it matters, but they both came with 2.10 bootloader and 3.70 base.
I have a strange feeling the first replacement had new block size, but for some reason a bug marked it as having the old block size. I just dont see how a brand new just made 0004 evo would have the old block size.
Could this have been the culprit?
I am trying to get a handle on the NAND partitioning in Desire out of curiosity.
Desire has got 512 MB ROM and after flashing hboots I realized that things are not adding up.
1. I had set up my hboot as follows:-
cache - 5 MB
System - 150 MB
Data - 282 MB
Total - 437 MB
So where is the Balance 512-437=75MB ?
Click to expand...
Click to collapse
2. OK lets take the other partitions like misc, recovery and boot into the calculations. I typed cat /proc/mtd and got:-
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00480000 00020000 "recovery"
mtd2: 00300000 00020000 "boot"
mtd3: 09600000 00020000 "system"
mtd4: 00500000 00020000 "cache"
mtd5: 11aa0000 00020000 "userdata"
Click to expand...
Click to collapse
Total size 1bdc0000hex is equal to 445.75MB
Still balance 512-445.75=66.25MB unaccounted for.
3. Time to dig a bit deeper. I got hold of some useful commands using 'fastboot oem h' one of them being fastboot oem listpartition.
listpartition gives this data(formatted):-
Partition Blocks Size(Hex) MB
radio: 497 3E20000 62.125
hboot: 6 C0000 0.75
sp2: 7 E0000 0.875
mfg: 6 C0000 0.75
sp1: 9 120000 1.125
wifi: 5 A0000 0.625
recovery: 36 480000 4.5
boot: 24 300000 3
system: 1200 9600000 150
cache: 40 500000 5
userdata: 2261 11AA0000 282.625
misc: 5 A0000 0.625
4096 20000000 512
Click to expand...
Click to collapse
When you add up the MB column you get the magic figure 512MB. Fine. But I have got more questions now after I see the listpartition output:-
A. I thought that hboot and radios being so special are in seperate areas compared to say data or system partitions. But from this table it looks apparently that they are in the same contiguous memory. So is everything in the same area/chip?
B. The radio and wifi partitions are seperate. So does flashing radio only affect 2G/3G?
C. What is sp1, sp2 or mfg partitions?
Some questions answered. hboot and radio and I guess almost everything else is on NAND chip called MCP(Multi Chip Package) from Samsung. The only reason hboot and radio are special is because radio is the bootloader for the modem processor whereas the hboot is the bootloader for the application processor. The Desire contains a Qualcom SOC (System on Chip) which has these processors. So if either the application or the modem processor cannot boot due to hboot or radio image corruption then thats it , your desire is bricked.
The sp1 and sp2 partitions house the splash1 and splash2 splash screens. The mfg partition houses the MFG_DIAG image ?? The wifi partition is seperate from radio. But who uses the wifi partition?
Is it possible to access these hidden partitions? I did some digging. The very first requirement is to find out the starting address and size on NAND for each of these partitions. You get some data from 'fastboot oem listpartition' and some more data from 'dmesg'. You got to do some mathematics and at the end of it you get this neat table.
{
"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"
}
For accessing the hidden partitions like radio,hboot,sp1,sp2,mfg and wifi you will need to change the kernel commandline. It is quite simple actually. All you need to do is keep a recovery image handy and get into fastboot mode. The idea is to boot the desire with a alternate kernel which you supply during fastboot.
example:-
Without Kernel Commandline
C:\sdktools-toolsonly\android-sdk-windows\tools>fastboot boot recovery-clockwork-5.0.2.0-bravo.img
Click to expand...
Click to collapse
Now you will be in cwm 5 recovery
C:\sdktools-toolsonly\android-sdk-windows\tools>adb shell
~ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00480000 00020000 "recovery"
mtd2: 00300000 00020000 "boot"
mtd3: 09600000 00020000 "system"
mtd4: 00500000 00020000 "cache"
mtd5: 11aa0000 00020000 "userdata"
Click to expand...
Click to collapse
Since no kernel commandline is given only the default partitions are shown.
With Kernel Commandline
C:\sdktools-toolsonly\android-sdk-windows\tools>fastboot -c "mtdparts=msm_nand:[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),0x11aa0
[email protected](userdata),[email protected](misc)" boot recovery-clockwork-5.0.2.0-bravo.img
C:\sdktools-toolsonly\android-sdk-windows\tools>adb shell
~ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00480000 00020000 "recovery"
mtd1: 00300000 00020000 "boot"
mtd2: 09600000 00020000 "system"
mtd3: 00500000 00020000 "cache"
mtd4: 11aa0000 00020000 "userdata"
mtd5: 000a0000 00020000 "misc"
~ # exit
Click to expand...
Click to collapse
Again only the default partitions are shown.
Custom Commandline
Now lets expand the commandline
C:\sdktools-toolsonly\android-sdk-windows\tools>fastboot -c "mtdparts=msm_nand:[email protected](sp2),[email protected](sp1),[email protected](misc),[email protected](recovery),[email protected]
x046c0000(boot),[email protected](system),[email protected](cache),[email protected](userdata)" boot recovery-clockwork-5.0.2.0-bravo.img
C:\sdktools-toolsonly\android-sdk-windows\tools>adb shell
~ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 000e0000 00020000 "sp2"
mtd1: 00120000 00020000 "sp1"
mtd2: 000a0000 00020000 "misc"
mtd3: 00480000 00020000 "recovery"
mtd4: 00300000 00020000 "boot"
mtd5: 09600000 00020000 "system"
mtd6: 00500000 00020000 "cache"
mtd7: 11aa0000 00020000 "userdata"
~ # mount /sdcard
mount /sdcard
~ # cat /dev/mtd/mtd1 > /sdcard/sp1.img
cat /dev/mtd/mtd1 > /sdcard/sp1.img
~ # cat /dev/mtd/mtd0 > /sdcard/sp2.img
cat /dev/mtd/mtd0 > /sdcard/sp2.img
~ # umount /sdcard
umount /sdcard
~ # exit
exit
Click to expand...
Click to collapse
Lets chcek out the sp1 and sp2 images
D:\store\Desire\nbimg-1.1win32>copy sp1.img sp1.nb
D:\store\Desire\nbimg-1.1win32>copy sp2.img sp2.nb
D:\store\Desire\nbimg-1.1win32>nbimg -F sp1.nb -w 480 -h 800
D:\store\Desire\nbimg-1.1win32>nbimg -F sp2.nb -w 480 -h 800
Click to expand...
Click to collapse
Just check out the extracted images sp1 and sp2. I never knew sp2 image.
Now lets give the command for the full table
C:\sdktools-toolsonly\android-sdk-windows\tools>fastboot -c "mtdparts=msm_nand:[email protected](radio),[email protected](hboot),[email protected](sp2),[email protected](mfg),[email protected]
4080000(sp1),[email protected](wifi),[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected]
0000(userdata)" boot recovery-clockwork-5.0.2.0-bravo.img
C:\sdktools-toolsonly\android-sdk-windows\tools>adb shell
~ # cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 03e20000 00020000 "radio"
mtd1: 000c0000 00020000 "hboot"
mtd2: 000e0000 00020000 "sp2"
mtd3: 000c0000 00020000 "mfg"
mtd4: 00120000 00020000 "sp1"
mtd5: 000a0000 00020000 "wifi"
mtd6: 000a0000 00020000 "misc"
mtd7: 00480000 00020000 "recovery"
mtd8: 00300000 00020000 "boot"
mtd9: 09600000 00020000 "system"
mtd10: 00500000 00020000 "cache"
mtd11: 11aa0000 00020000 "userdata"
~ # mount /sdcard
mount /sdcard
~ # cat /dev/mtd/mtd0 > /sdcard/radio.img
cat /dev/mtd/mtd0 > /sdcard/radio.img
cat: read error: I/O error Gak!But Nothing happened
~ # cat /dev/mtd/mtd1 > /sdcard/hboot.img
cat /dev/mtd/mtd1 > /sdcard/hboot.img
~ # cat /dev/mtd/mtd3 > /sdcard/mfg.img
cat /dev/mtd/mtd3 > /sdcard/mfg.img
~ # cat /dev/mtd/mtd5 > /sdcard/wifi.img
cat /dev/mtd/mtd5 > /sdcard/wifi.img
~ # umount /sdcard
umount /sdcard
~ # exit
Click to expand...
Click to collapse
So could access and get dumps of all the partitions except for radio.
I am looking into doing a recovery for this device. I just need a user that has adb setup run the command below. Paste it here whatever it outputs
adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p32: 54fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p33: 0dfffe00 00000200 "cache"
mmcblk0p34: 49fffe00 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p35: 1097fe000 00000200 "fat"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
Thanks for that now can you do the command below and upload the img file?
adb shell dd if=/dev/block/mmcblk0p21 of=/sdcard/recovery.img
adb pull /sdcard/recovery.img
Sent from my HTC One XL using xda premium
jmztaylor said:
Thanks for that now can you do the command below and upload the img file?
adb shell dd if=/dev/block/mmcblk0p21 of=/sdcard/recovery.img
adb pull /sdcard/recovery.img
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I tried, but i got
adb shell dd if=/dev/block/mmcblk0
p21 of=/sdcard/recovery.img
/dev/block/mmcblk0p21: cannot open for read: Permission denied
So i am guessing i need to root my phone, but this is stock and i messed the previous phone up by trying stuff to it in which i was lucky they gave me a replacement. I can't screw it up, i would like to root my phone, just scared to unless you could provide a sure way of doing it to this specific phone.
Replicatorz said:
I tried, but i got
adb shell dd if=/dev/block/mmcblk0
p21 of=/sdcard/recovery.img
/dev/block/mmcblk0p21: cannot open for read: Permission denied
So i am guessing i need to root my phone, but this is stock and i messed the previous phone up by trying stuff to it in which i was lucky they gave me a replacement. I can't screw it up, i would like to root my phone, just scared to unless you could provide a sure way of doing it to this specific phone.
Click to expand...
Click to collapse
Try the command below. If this works I can get you root.
adb shell dd if=/dev/block/mmcblk0p20 of=/sdcard/boot.img
Sent from my HTC One XL using xda premium
jmztaylor said:
Try the command below. If this works I can get you root.
adb shell dd if=/dev/block/mmcblk0p20 of=/sdcard/boot.img
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I am sorry, i even unlocked the bootloader and it still wouldn't work. If i do it in bootloader, adb don't work. Keeps giving permission denied, so i guess i do need root to extract those.
jmztaylor said:
Thanks for that now can you do the command below and upload the img file?
adb shell dd if=/dev/block/mmcblk0p21 of=/sdcard/recovery.img
adb pull /sdcard/recovery.img
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
it pulled succesfully, may be because i rooted my phone (your method), do you still need the .img file?If you do, where does it go (on computer files) after an image is pulled from the device?
Johann12911 said:
it pulled succesfully, may be because i rooted my phone (your method), do you still need the .img file?If you do, where does it go (on computer files) after an image is pulled from the device?
Click to expand...
Click to collapse
Nah I got it. Thanks though
Sent from my HTC One X using xda premium
jmztaylor said:
Nah I got it. Thanks though
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
To easily pull the recovery would of been... Have root access and did "adb remount" then try to pull it
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
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.
{
"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"
}
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.
DarkRazorZ said:
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.
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.
Click to expand...
Click to collapse
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>
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.
@@.............................
boa19861105 said:
@@.............................
Click to expand...
Click to collapse
Where? When?!
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
wumilun said:
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
Click to expand...
Click to collapse
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.
DarkRazorZ said:
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.
.
Click to expand...
Click to collapse
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
orb3000 said:
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
Click to expand...
Click to collapse
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.
DarkRazorZ said:
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.
Click to expand...
Click to collapse
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
orb3000 said:
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
Click to expand...
Click to collapse
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
DarkRazorZ said:
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
Click to expand...
Click to collapse
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
orb3000 said:
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
Click to expand...
Click to collapse
I'll add it. So unlocking your bootloader made root work?
DarkRazorZ said:
I'll add it. So unlocking your bootloader made root work?
Click to expand...
Click to collapse
Exactly, after unlock bootloader your guide works perfect!
If compiled from boa19861105 source on github, TWRP is now fully functioning for the Butterfly 3.
I could not compile it with error.
I don't know much about Linux.
Can anyone upload img file?
Makefile:795: *** multiple target patterns. Stop.
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 :'(
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>
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!
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.
DarkRazorZ said:
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.
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.
Click to expand...
Click to collapse