[31.12.2015][TWRP 3.0.0-2][OFFICIAL][TEAM REDUX]TWRP For HTC Explorer

Do you think we (Team Redux) are awesome ??

  • F**k Yeah!!

    Votes: 2 66.7%

  • Snap outta it real quick.

    Votes: 1 33.3%
  • Total voters
    3
  • Poll closed .
Status
Not open for further replies.
Search This thread
By:
Advanced…
S

sbappi

Senior Member
Feb 5, 2016
169
59
Multan
Flashing works but not everything works. like mount USB storage. What are the new features? Tell me so that i can compare with previous versions. To me it is nothing different from twrp 3.0.0.0. Even you dont have the device but you are still maintaining twrp for it, it's really appreciating. (y)
 
MSF Jarvis

MSF Jarvis

XDA Feed Mod/Inactive RC
Mar 31, 2015
3,820
7,476
msfjarvis.dev
sbappi said:
Flashing works but not everything works. like mount USB storage. What are the new features? Tell me so that i can compare with previous versions. To me it is nothing different from twrp 3.0.0.0. Even you dont have the device but you are still maintaining twrp for it, it's really appreciating. (y)
Click to expand...
Click to collapse

USB storage is broken for Windows, if you are using that. MTP works just fine, so not a priority for me.


New features are basically improvements in the device tree, and some of those changes have somehow not found their way into the build. @faddat has been gracious to supply me with a build server, so I'll run a fresh build myself in a day or two.
 
H

hrkh83

Senior Member
May 2, 2009
447
624
@MSF Jarvis

Thank you for the latest version...

Could you please please please make a non-aw3some version so I can use it on old builds?

Thank you very much in advance
 
H

hrkh83

Senior Member
May 2, 2009
447
624
hrkh83 said:
@MSF Jarvis
Yes.
I would be deeply grateful if you could make a non-aw3som3 based updated TWRP available for me and other users who want to install older ROMs.
Click to expand...
Click to collapse

MSF Jarvis said:
Available here
Click to expand...
Click to collapse

By the way,

I tested the older non aw3some version. All of the features work flawlessly. The only thing that is broken is the "Mount USB Storage". I hear the windows plug in and removal sound... but the drive doesn't show up. Also I am not able to see it with partition managers or other tools.

Again thank you. I am keeping fingers at both hands crossed for 3.0.0.0 non-aw3some version :good::good:
 
MSF Jarvis

MSF Jarvis

XDA Feed Mod/Inactive RC
Mar 31, 2015
3,820
7,476
msfjarvis.dev
hrkh83 said:
By the way,

I tested the older non aw3some version. All of the features work flawlessly. The only thing that is broken is the "Mount USB Storage". I hear the windows plug in and removal sound... but the drive doesn't show up. Also I am not able to see it with partition managers or other tools.

Again thank you. I am keeping fingers at both hands crossed for 3.0.0.0 non-aw3some version :good::good:
Click to expand...
Click to collapse

USB Storage on Windows has to be a problem with the TWRP codebase, and since MTP works, not a priority for me. As for non-awesom3 TWRP, I just didn't get the time today. I'll try and do it in a couple of days and link you to it.
 
  • Like
Reactions: hrkh83
H

hrkh83

Senior Member
May 2, 2009
447
624
MSF Jarvis said:
USB Storage on Windows has to be a problem with the TWRP codebase, and since MTP works, not a priority for me. As for non-awesom3 TWRP, I just didn't get the time today. I'll try and do it in a couple of days and link you to it.
Click to expand...
Click to collapse

Sorry. I was not clear!

The USB storage mounting inside the android works.... it is flawless.

But the USB storage mounting inside the TWRP recovery doesn't work! The windows detects something is plugged in or removed... it makes the famous plugin and removed sound! But there isn't any mounted drive. Also partition managers such as "mini tool partition" and "windows disk manager" don't detect anything.

I really hope that you can easily fix it... otherwise, after wiping the SD card, I have to use a SD-to-USB adapter to move my ROM and Gapps to the sd card.....

And again thank you in advance for the TWRP 3.0.0.0
 
MSF Jarvis

MSF Jarvis

XDA Feed Mod/Inactive RC
Mar 31, 2015
3,820
7,476
msfjarvis.dev
hrkh83 said:
Sorry. I was not clear!

The USB storage mounting inside the android works.... it is flawless.

But the USB storage mounting inside the TWRP recovery doesn't work! The windows detects something is plugged in or removed... it makes the famous plugin and removed sound! But there isn't any mounted drive. Also partition managers such as "mini tool partition" and "windows disk manager" don't detect anything.

I really hope that you can easily fix it... otherwise, after wiping the SD card, I have to use a SD-to-USB adapter to move my ROM and Gapps to the sd card.....

And again thank you in advance for the TWRP 3.0.0.0
Click to expand...
Click to collapse

I understood what you meant. I use USB Storage from TWRP to connect my sdcard to my Ubuntu 15.10 laptop and it works flawlessly. But when I do the same thing on my Dad's boring :)p) Windows 8.1 laptop, the issue you report occurs. I am trying to get in touch with TeamWin about this issue and see what can be done :cowboy:
 
L

limjh16

Senior Member
Oct 20, 2015
1,478
1,051
Singapore
MSF Jarvis said:
This is my first post here in months, its not a job anymore to maintain TWRP for it. They do automated builds. Just checking on my grateful users. These forums have given loads of love, which I'm trying to give back :)
Click to expand...
Click to collapse
Well, I've seen you on other threads and I must say u have given back a lot of love alrd... well, I shiuld stop the off topic now.
 
Status
Not open for further replies.

Similar threads

jaggyjags
[ROM] Htc Explorer (pico) "JaggyRom" [3.2.1] (5-7-12)
Replies
3K
Views
734K
L
LEO_Scad
H
  • Poll
[2017.07.07] Explorer Index Thread!
Replies
322
Views
438K
MSF Jarvis
MSF Jarvis
jaggyjags
[TUTORIAL] Root HTC explorer
Replies
707
Views
496K
shree alwaz
shree alwaz
sakindia123
[DEV][ROM][ICS][4.0.4][IMM76L]Unofficial CyanogenMod 9.1 for Pico Build#14 {5/3/13}
Replies
4K
Views
678K
T
thewisenerd
#define
  • Locked
[RECOVERY][OFFICIAL] TWRP 2.6.3.0/2.6.0.0 Touch Recovery
Replies
545
Views
140K
KidCarter93
KidCarter93

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 6
    MSF Jarvis
    MSF Jarvis
    Team Win Recovery Project 3.x, or twrp3 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 3.0.0-0:

    -Completely new theme - Much more modern and much nicer looking (by z31s1g)
    -True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
    -Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
    -Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
    -Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
    -Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
    -SuperSU prompt will no longer display if a Marshmallow ROM is installed
    -Update exfat, exfat fuse, dosfstools (by mdmower)
    -Update AOSP base to 6.0
    -A huge laundry list of other minor fixes and tweaks

    WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

    Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

    Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

    We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

    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)

    Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

    System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

    resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

    This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

    DOWNLOAD:
    Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
    1) Download the latest version from our website on your device
    2) Reboot to TWRP
    3) Hit Install and tap the "Images..." button in the lower right
    4) Browse to the location of the TWRP image on your device and select it
    5) Select recovery from the partition list and swipe to flash
    OR:
    You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!

    BUGS:
    If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

    SUPPORT:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.

    XDA:DevDB Information
    TWRP 3.0.0-x OFFICIAL Builds, Tool/Utility for the HTC Pico (Explorer)

    Contributors
    MSF Jarvis, abhi_qwerty, thewisenerd,Dees_Troy
    Source Code: https://github.com/TeamWin/android_device_htc_pico


    Version Information
    Status: Stable
    Current Stable Version: 3.0.0-2
    Stable Release Date: 2016-03-22

    Created 2015-12-31
    Last Updated 2016-03-23
    View
    3
    MSF Jarvis
    MSF Jarvis
    SdtBarbarossa said:
    cant you use lzma compressed kernel and ramdisk ?

    Sent from my Xperia T using XDA Free mobile app
    Click to expand...
    Click to collapse
    It was off by 26KB with LZMA compressed ramdisk. I know what I'm talking about man, I just removed SuperSU and it fit. I'm looking to compress the zImage as well next time onwards so that the Pico can live on for some more time.

    Sent from my HTC Explorer A310e using Tapatalk
    View
    2
    MSF Jarvis
    MSF Jarvis
    Everyone, please update your recovery to version 3.0.0-1 ASAP to benefit from the new changes. This recovery should happily fix all issues regarding missing parted and nano (more on that later) and also the mountpoints.

    Edit: Detailed Changlog
    With the new build, sd-ext partition which gets reverse-mounted to /data in the ROMs, is now the default for recovery. /data and and /cache are now the external sd-ext partitions and therefore it is recommended to ensure those partitions exist before flashing the new build.

    Also, since nano and parted have been removed from TWRP builds due to recovery image size overflows, I have made a tiny 'hack' that should allow people to be able to use them easily from within TWRP without bothering with any complexities. Simply push the contents on the attached zip file into /system/bin and you are set. Whenever you want to use nano and parted, you can easily do so within the TWRP terminal (which is very much better now thanks to @bigbiff) or through adb shell. Details on how this works can be found on the original gerrit change I pushed here : http://gerrit.twrp.me/1202.
    Click to expand...
    Click to collapse
    View
    1
    MSF Jarvis
    MSF Jarvis
    Reserved

    Features:
    - Material UI thanks to @z31s1g
    - F2FS compatible
    - Supports OpenRecoveryScript commands placed in /cache/recovery -- Was borked in 2.8.0.0 and 2.8.5.0
    - Data backups are now functional; backup sd-ext if you're on one of my ROMs
    - Issues with bootloops due to dirty flashes solved. For those on aw3som3 or CM 12.1, use respective images from my TWRP Experiments Thread.
    View
    1
    MSF Jarvis
    MSF Jarvis
    hrkh83 said:
    Yes.. It is appearing...

    By the way, I flashed it on a device that already had KitKat on it.. In case you have made it in a way to check ROMs and only flash JB ROMs !
    Click to expand...
    Click to collapse

    No of course not, it doesn't do any checks. I just forgot Arslan's CM 11 builds are more popular than mine :p
    View

New posts