[RECOVERY][TOUCH]TWRP 2.7.0.0 Touch Recovery [UPDATE TO #define's thread]

Search This thread

v_superuser

Senior Member
Jan 3, 2013
485
1,492
25
Jammu
Since, @#define doesn't has the device anymore and I was working on updates of TWRP Recovery, so after some talks with him, I am making a new thread where I will maintain TWRP Releases. :)

OFFICIAL TWRP HTC EXPLORER PAGE

Latest Release - v 2.7.0.0 by @thewisenerd

What's new in 2.7.0.0:
  • Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
  • Allow sideloading from /tmp on encrypted devices
  • Check for a crypto footer before asking for a password to prevent user confusion
  • Additional checks for validity to auto generated backup names
  • Text wrap in the console output
  • Proper caps lock support in the keyboard
  • Mouse support via USB OTG for devices with a broken digitizer
  • Improve scanning of storage locations for OpenRecoveryScript
  • Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
  • Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
  • Update SuperSU to 1.93 and improve installation process
  • Added selinux contexts restoration to fix permissions
  • Load RTC offset on Qualcomm devices to fix the date/time in recovery
  • USB Mass Storage fixes Add SELinux support checking
  • Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
  • Add 4.4 AOSP decrypt support
  • Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
  • Various SELinux fixes and bug fixes
  • Removed Superuser prebuilt binary and Superuser.apk (By me not in Official TWRP) to trim the recovery size.(Thanks for the idea @galaxyfreak )

Older Changelogs

For the new people, here are the instructions..

----> For Windows :

1) Download the recovery zip and the tools given above..

2) Extract the zips someplace safe (for eg, C:/TWRP)..

3) Open the command prompt, and navigate to the folder in which you extracted the files..

4) Boot your phone into Fastboot mode, and connect it to the computer.. It should show "Fastboot USB"

5) In the command prompt, type :
Code:
fastboot flash recovery recovery.img && fastboot reboot

6) Enjoy your new recovery!! :good:


----> For Linux :

1) ADB and Fastboot for linux are also attached above..

2) Download and extract all the stuff in a safe location (for eg, ~/TWRP)

3) Open terminal, and navigate to the goodies folder..

4) Put your phone in fastboot mode, and connect to USB, and it should show "Fastboot USB"..

5) Now in terminal, type :
Code:
$ ./fastboot flash recovery recovery.img && fastboot reboot

6) Enjoy your new touch recovery!! :good:


Credits -
@#define
@galaxyfreak
@thewisenerd
 
Last edited:

Abhaysinh

Senior Member
Jan 1, 2014
176
35
29
Bug founded

When restore/wipe than recovery restart not rebooting recovery.second time working?
If it's already noticed,solve in next version?
logcat:
 

Attachments

  • recovery.txt
    24.8 KB · Views: 383

thewisenerd

Senior Member
Sep 27, 2012
1,385
2,996
Was anyone able to get fastboot working?
I remember it working in my home builds, but I don't recollect it working in this recovery though.

Is this "bug" only for me?

Edit: NVM, borked USB

edit: spoke too soon. Yes. adb *is* broken. works at times, doesn't work, at times.

edit: let's put this post to good use:
Download: http://www.mediafire.com/download/sx78aa9eu21c54q/twrp_21may2014.img

Don't give the crap that you're even interested in changelog. You just need something that works. You'd not even know if this is just the same file, with a different name.

For those who really are, go over to https://github.com/omnirom/android_bootable_recovery/commits/android-4.4, and check the commits from Mar 28, 2014.
 
Last edited:

Agaphetos

Senior Member
May 10, 2014
115
203
Cainta, Rizal
agaphetos.github.io
Nand recovery partition burned

For those who are encountering NAND Recovery Partition burned.

booting on recovery,
TWRP logo shows
then go black screen
then TWRP logo shows again
then stucked at TWRP Logo.


SOLUTION:

  1. BOOT into BOOTLOADER.
  2. FLASH Latest PhilZ Touch Recovery (here: http://xdaforums.com/showpost.php?p=41061154&postcount=3)
  3. Download flash_erase.txt *rename and remove .txt* it's a binary file.(here: http://xdaforums.com/attachment.php?attachmentid=1655489&d=1358514526)
  4. Flash any rom that has working ADB.
  5. Push flash_erase on /system/xbin then set and fix permissions.
    Code:
    adb push flash_erase system/xbin/
    adb shell
    su
    cd system/xbin/
    chomd 755 flash_erase
  6. Reboot
  7. Then perform a NAND Recovery on /recovery partition. (Needs USB debugging enabled and Root access on Apps and ADB)
    Code:
    adb shell
    su
    cd /system/xbin
    ./flash_erase -N /dev/mtd/mtd1 0 0
  8. FLASH TWRP Recovery.

NOTE: IF YOU GOT WHOLE YOUR MTD PARTITION BURNED. flash_erase mtd0 to mtd6.
 
Last edited:

thewisenerd

Senior Member
Sep 27, 2012
1,385
2,996
For those who are encountering NAND Recovery Partition burned.

booting on recovery,
TWRP logo shows
then go black screen
then TWRP logo shows again
then stucked at TWRP Logo.


SOLUTION:

  1. BOOT into BOOTLOADER.
  2. FLASH Latest PhilZ Touch Recovery (http://xdaforums.com/showpost.php?p=41061154&postcount=3)
  3. Then perform a NAND Recovery on /recovery partition (http://xdaforums.com/attachment.php?attachmentid=1655489&d=1358514526)
    Code:
    flash_erase -N /dev/mtd/mtd1 0 0
  4. FLASH TWRP Recovery.

I would suggest you do that not from the recovery.
You can also do the same procedure with any ROM booted and ADB or Terminal Emulator :)
 

Agaphetos

Senior Member
May 10, 2014
115
203
Cainta, Rizal
agaphetos.github.io
I would suggest you do that not from the recovery.
You can also do the same procedure with any ROM booted and ADB or Terminal Emulator :)

yeah. i just cut the instructions. haha. they must flash ROM first then put flash_erase on /system/xbin.
then perform flash_erase -N /dev/mtd/mtd1 0 0.

it's only for those who got whole MTD partition got burned.
they can't boot into both /system and /recovery.

Edit: I updated my post already.
 
Last edited:

boko_to

Senior Member
Apr 29, 2014
82
17
Brno
yeah. i just cut the instructions. haha. they must flash ROM first then put flash_erase on /system/xbin.
then perform flash_erase -N /dev/mtd/mtd1 0 0.

it's only for those who got whole MTD partition got burned.
they can't boot into both /system and /recovery.

Edit: I updated my post already.

I have burnt my nand several times and i couldnt get into TWRP recovery at all ( stuck at the logo ). The solution I found was to downgrade to CWM 5 and then format boot/system/data. Then flash back TWRP 2.7 and superwipe for nand recovery - thanks to thewisenerd :) works like a charm.
 

Agaphetos

Senior Member
May 10, 2014
115
203
Cainta, Rizal
agaphetos.github.io
I have burnt my nand several times and i couldnt get into TWRP recovery at all ( stuck at the logo ). The solution I found was to downgrade to CWM 5 and then format boot/system/data. Then flash back TWRP 2.7 and superwipe for nand recovery - thanks to thewisenerd :) works like a charm.

i suggest you to still flash_erase your /recovery partition.
flashing another recovery on your /recovery partition doesn't recover bad blocks.
 

boko_to

Senior Member
Apr 29, 2014
82
17
Brno
i suggest you to still flash_erase your /recovery partition.
flashing another recovery on your /recovery partition doesn't recover bad blocks.

Yes right, - I was just giving a workaround if someone can't get into recovery - and what worked for me - after re-flashing TWRP i never had any problems with the recovery partition again.
 

fgaurano

Senior Member
Nov 12, 2013
217
55
Cagayan de Oro
I have my Fastboot USB connected, and after typing the command, it justs " < waiting for device> " I tried removing USB a lot of times already and fastbooting USB.
 

Schematic

Senior Member
Jun 27, 2014
68
7
I have my Fastboot USB connected, and after typing the command, it justs " < waiting for device> " I tried removing USB a lot of times already and fastbooting USB.

That also happened to me. If youre using windows 8.1, maybe thats the problem. The only way was flashing through terminal emulator.
 

Schematic

Senior Member
Jun 27, 2014
68
7
:rolleyes: I have the recovery partition burned, but the instrutions to fix are not clear enough for noobs like me.

EDIT: Based on the @Agaphetos instrutions and from this thread http://xdaforums.com/showthread.php?t=2389445

Note: This method WON'T work on Windows 8/8.1. It will work fine on windows 7.
Backup your apps and stuff before doing anything

1. Download and Install HTC Sync Manager http://www.htc.com/pt/software/htc-sync-manager/
2. Download and Install ADB fastboot drivers http://xdaforums.com/showthread.php?t=2588979 (I dont know if this is really necessary:confused:)
3. Get the adb and fastboot drivers, you can use the ones from this recovery, just remove the "recovery.img" that comes with http://xdaforums.com/attachment.php?attachmentid=913094&d=1329843100
4. Download this PhilZ Touch Recovery http://xdaforums.com/showthread.php?t=2265055 and rename it as: recovery.img
5 Place the "recovery.img" that you have renamed to the "A310E Recovery" folder
6. Remove the Battery and SIM card (in case you dont have a mobile network plan) If the rom youre using has the "Reboot to Bootloader" option in "Power Menu" you can use that instead.
7. Place the battery, and press "Volume Down" and "Power Button" at the same time till you boot into "Bootloader".
8. Connect your phone to the PC and choose "Fastboot", it will show "Fastboot USB" in red, then go to the "A310E Recovery" folder and run the "recovery.bat". You have flashed the PhilZ Touch Recovery.
9. Press "Power Button" to exit "Fastboot". In "Bootloader" menu choose "Recovery" to enter in PhilZ Touch Recovery.
10. In there make a "Wipe Data/Factory Reset", "Wipe cache", go to Advanced: "Wipe dalvik cache". Go to "Mounts and Storage" and format everything except "/sdcard". (Maybe you dont need to wipe everything Ive mentioned:silly:)
11. Scroll down and choose "Mount USB storage".
12. Download a CM rom, Ive used this one http://xdaforums.com/showthread.php?t=2535682, and place the .zip rom in root of sdcard. Im sure other CM roms will also work.
13. Download this AROMA Filemanager http://xdaforums.com/showthread.php?t=1646108 and place it in root of sdcard.
14. Download (Save this file as) flash_erase.txt http://xdaforums.com/attachment.php?attachmentid=1655489&d=1358514526 and remove the ".txt" file extension and place it also in root of sdcard.
15. Flash the CM rom. Once flashed the rom go to "Mounts and Storage". Mount everything till you see all "unmount", go back.
16. Flash the "aromafm.zip". It will open AROMA filemanager. Scroll down and enter in "sdcard" and copy the "flash_erase" file, go back. Look for a "system" folder, scroll it down till you find one saying "xbin", enter there and paste the "flash_erase" file.
17. Look for the "flash_erase", and then long press it till you see a menu, choose "Set permissions". The first 3 lines should be all green already, Exit AROMA Filemanager. and reboot system.
18. Once youve booted into the CM rom, go to "Settings" -> "About Phone", In there scroll down to "Build Number" and press it several times to enable "Developer Options".
19. Go back and enter "Developer Options", make sure "Android debugging" is enabled. Connect your phone to the PC. Now go to "Terminal Emulator" and enter the following commands.

Code:
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd1 0 0
It will show up a message with something about 100%:eek: I cant remember:silly:
20. Boot into "Recovery" again, make a Wipe and Format everything, like you did in step .10.
21. In "Power Off" menu of the Recovery, choose "Reboot to Bootloader"
22. Plug in the phone in "Fastboot USB" and repeat the step .4, .5 and .8 but for the TWRP Recovery instead.
23. You should now be able to boot into the TWRP recovery, make sure you Wipe Everything again in "Wipe" -> "Advanced Wipe", except "sdcard". If the recovery reboots while wiping, reboot recovery and try again.

DONE!
 
Last edited:
  • Like
Reactions: Agaphetos

Top Liked Posts

  • There are no posts matching your filters.
  • 25
    Since, @#define doesn't has the device anymore and I was working on updates of TWRP Recovery, so after some talks with him, I am making a new thread where I will maintain TWRP Releases. :)

    OFFICIAL TWRP HTC EXPLORER PAGE

    Latest Release - v 2.7.0.0 by @thewisenerd

    What's new in 2.7.0.0:
    • Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
    • Allow sideloading from /tmp on encrypted devices
    • Check for a crypto footer before asking for a password to prevent user confusion
    • Additional checks for validity to auto generated backup names
    • Text wrap in the console output
    • Proper caps lock support in the keyboard
    • Mouse support via USB OTG for devices with a broken digitizer
    • Improve scanning of storage locations for OpenRecoveryScript
    • Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
    • Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
    • Update SuperSU to 1.93 and improve installation process
    • Added selinux contexts restoration to fix permissions
    • Load RTC offset on Qualcomm devices to fix the date/time in recovery
    • USB Mass Storage fixes Add SELinux support checking
    • Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
    • Add 4.4 AOSP decrypt support
    • Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
    • Various SELinux fixes and bug fixes
    • Removed Superuser prebuilt binary and Superuser.apk (By me not in Official TWRP) to trim the recovery size.(Thanks for the idea @galaxyfreak )

    Older Changelogs

    For the new people, here are the instructions..

    ----> For Windows :

    1) Download the recovery zip and the tools given above..

    2) Extract the zips someplace safe (for eg, C:/TWRP)..

    3) Open the command prompt, and navigate to the folder in which you extracted the files..

    4) Boot your phone into Fastboot mode, and connect it to the computer.. It should show "Fastboot USB"

    5) In the command prompt, type :
    Code:
    fastboot flash recovery recovery.img && fastboot reboot

    6) Enjoy your new recovery!! :good:


    ----> For Linux :

    1) ADB and Fastboot for linux are also attached above..

    2) Download and extract all the stuff in a safe location (for eg, ~/TWRP)

    3) Open terminal, and navigate to the goodies folder..

    4) Put your phone in fastboot mode, and connect to USB, and it should show "Fastboot USB"..

    5) Now in terminal, type :
    Code:
    $ ./fastboot flash recovery recovery.img && fastboot reboot

    6) Enjoy your new touch recovery!! :good:


    Credits -
    @#define
    @galaxyfreak
    @thewisenerd
    10
    twrp 2.8.0.0

    changelog

    • full featured, no features removed, yada yada, 2.8.0.0, yada yada, etc.

    download: http://www.mediafire.com/download/3q7jz01f2ynqrlc/twrp_11_sep_2014.img
    5
    Was anyone able to get fastboot working?
    I remember it working in my home builds, but I don't recollect it working in this recovery though.

    Is this "bug" only for me?

    Edit: NVM, borked USB

    edit: spoke too soon. Yes. adb *is* broken. works at times, doesn't work, at times.

    edit: let's put this post to good use:
    Download: http://www.mediafire.com/download/sx78aa9eu21c54q/twrp_21may2014.img

    Don't give the crap that you're even interested in changelog. You just need something that works. You'd not even know if this is just the same file, with a different name.

    For those who really are, go over to https://github.com/omnirom/android_bootable_recovery/commits/android-4.4, and check the commits from Mar 28, 2014.
    3
    twrp 2.8.0.0

    changelog:

    • saving you the time, tl;dr, mtp config was missing. added it. now you can use either ums or mtp; i.e. used ums, you can only use ums henceforth (till you reboot), and so goes for mtp. This should be fixed with upstream patches, but I'm busy to resync, and rebuild ( + my machine's slow).

    download: https://www.mediafire.com/?0a33apvlul5rv8g
    3
    Nand recovery partition burned

    For those who are encountering NAND Recovery Partition burned.

    booting on recovery,
    TWRP logo shows
    then go black screen
    then TWRP logo shows again
    then stucked at TWRP Logo.


    SOLUTION:

    1. BOOT into BOOTLOADER.
    2. FLASH Latest PhilZ Touch Recovery (here: http://xdaforums.com/showpost.php?p=41061154&postcount=3)
    3. Download flash_erase.txt *rename and remove .txt* it's a binary file.(here: http://xdaforums.com/attachment.php?attachmentid=1655489&d=1358514526)
    4. Flash any rom that has working ADB.
    5. Push flash_erase on /system/xbin then set and fix permissions.
      Code:
      adb push flash_erase system/xbin/
      adb shell
      su
      cd system/xbin/
      chomd 755 flash_erase
    6. Reboot
    7. Then perform a NAND Recovery on /recovery partition. (Needs USB debugging enabled and Root access on Apps and ADB)
      Code:
      adb shell
      su
      cd /system/xbin
      ./flash_erase -N /dev/mtd/mtd1 0 0
    8. FLASH TWRP Recovery.

    NOTE: IF YOU GOT WHOLE YOUR MTD PARTITION BURNED. flash_erase mtd0 to mtd6.