[RECOVERY/M8_UL_CA] TWRP 2.7.0.4 Touch Recovery [2014-04-09] - AT&T HTC One (M8)

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Phone look:
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 thanks to Samer Diab
-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 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
Downloadhttp://androidfil.es/1mMD

Huge shoutouts go specifically to
@Flemmard @bigbiff @Dees_Troy
I learned how to properly deal with DTB from these guys....
Known Issues:
No known issues anymore
No exFAT support. Need kernel source to investigate
Random segfaults when starting actions. i.e. flashing restoring, backing up. Just makes you redo what you were trying to do. Dees_troy deems this nearly impossible to trace.

Glad to see you here JMZ!!

Hi I'm trying to get a recovery flashed on my phone and I've been working with mike1986 for a couple hours and for whatever reason my phone refuses to flash it. Every time I run the fastboot flash recovery command it gets to: sending 'recovery'... and then just hangs there indefinitely until I reboot. Any ideas? Thanks!

im getting cache errors in the recovery.

fix-this! said:
im getting cache errors in the recovery.
Click to expand...
Click to collapse
Can you pull /tmp/recovery.log and post here. I'm not seeing this on my device
Sent from my HTC One_M8 using Tapatalk

jmz said:
Can you pull /tmp/recovery.log and post here. I'm not seeing this on my device
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Just tried to flash it. It worked when I backed up to internal memory but when I tried to back up to the external sd card I got this error:
E: Unable to create folder: /external_sd/TWRP/BACKUPS/SerialNum/Date
errno=13
failed to make backup folder

graffixnyc said:
Just tried to flash it. It worked when I backed up to internal memory but when I tried to back up to the external sd card I got this error:
E: Unable to create folder: /external_sd/TWRP/BACKUPS/SerialNum/Date
errno=13
failed to make backup folder
Click to expand...
Click to collapse
you on freenode anywhere?

jmz said:
you on freenode anywhere?
Click to expand...
Click to collapse
Not at the moment. I'm in class. I should be home on a couple of hours
Sent from my HTC One_M8 using Tapatalk

Uploaded a new version. Tested backing up to external sdcard and OTG. Not quite sure what the issue was before

How is this different from the one posted in the international m8 section? I see this is 2.7.0.0 though. Is it wise to run theirs or no?

jmz said:
Uploaded a new version. Tested backing up to external sdcard and OTG. Not quite sure what the issue was before
Click to expand...
Click to collapse
Still getting the same error. I'll be home in a few and can jump on irc
and to add to it.. When it failed to back up I pressed the reboot system button right there. All the other times I would back out to the main menu to the reboot menu.. Now after I pressed reboot right after the error I'm stuck at the bootlogo, no adb access and holding power isn't rebooting the phone either
I got it to reboot by holding volume up and power. Booted back in now.. That was odd.

graffixnyc said:
Still getting the same error. I'll be home in a few and can jump on irc
and to add to it.. When it failed to back up I pressed the reboot system button right there. All the other times I would back out to the main menu to the reboot menu.. Now after I pressed reboot right after the error I'm stuck at the bootlogo, no adb access and holding power isn't rebooting the phone either
I got it to reboot by holding volume up and power. Booted back in now.. That was odd.
Click to expand...
Click to collapse
What format is your sdcard in
Sent from my HTC One_M8 using Tapatalk

Adb fasboot flash recovery recovery.img right? Been awhile lol
Sent from my HTC One_M8 using Tapatalk

Fidelio_o said:
Adb fasboot flash recovery recovery.img right? Been awhile lol
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
It should just be
Code:
fastboot flash recovery recovery.img
The "adb" at the beginning isn't necessary.

fix-this! said:
How is this different from the one posted in the international m8 section?
Click to expand...
Click to collapse
I'm curious to know too.

fix-this! said:
How is this different from the one posted in the international m8 section? I see this is 2.7.0.0 though. Is it wise to run theirs or no?
Click to expand...
Click to collapse
Tikerz said:
I'm curious to know too.
Click to expand...
Click to collapse
this is built from source. Not ported from M7. plus this supports external sdcard

im getting error: cannot open recovery.img
NEVERMIND IM AN IDIOT

Uploaded a new version. 2.7.0.2 This has working offmode charging

{
"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"
}
Having the same issue with my SD card as above. 64gb SD formatted in exfat. System uses it fine for photos etc...
Sent from my HTC One_M8 using Tapatalk

Related

[RECOVERY] TWRP full touch

Team Win Recovery Project 2.4, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s 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.
Phone look:
{
"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"
}
Tablet look:
What's new in 2.4.1.0:
Fixed a problem with mkdosfs that formatted sdcards to 2GB
Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
What's new in 2.4.0.0:
Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
Support for exFAT formatted sdcards (also thanks to bigbiff)
Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
Added wipe cache and dalvik after ADB Sideload
Replaced many system calls with their native C counterparts
Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
Fixed AOSP recovery commands to run after decryption on encrypted devices
Improvements for building TWRP in CM10.1
Other minor bugfixes and improvements
What's new in 2.3.3.0:
Fix renaming backups with a space in the name
Add decrypt button to mount page if you cancel decryption during startup
Added ignore blkid flag
Fixed handling of MTD partitions during mount
Fixed some keyboard mapping issues on 800x1280 layout
What's new in 2.3.2.0:
Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
Fixed a bug with deleting a backup with a space in the name
Added highlights on keyboard key presses
What's new in 2.3.1.0:
Unmount system after boot to prevent some status 7 symlink failed errors on zip install
USB Mass Storage code improvements
Better handling of mounting storage during boot for some devices
Fixed a problem with sizes of images (boot & recovery) after resetting defaults
Fixed size errors during backup for some devices on recovery, etc.
Fixed a problem with restoring backups when multiple archives were present
What's new in 2.3.0.0:
Rebased onto AOSP Jelly Bean source code
Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
ADB sideload functionality from AOSP is included in 2.3, see this link for more info
Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
Faster boot times
Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder. If you're getting a status error 2 during zip install, then an outdated update binary is almost certainly to blame.
What's new in 2.2.2.0:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
What's new in 2.2.0:
On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
What's new in 2.1.1 and 2.1.2:
Note: If you have a custom theme installed from 2.0 or 2.1.0, your theme will need to be updated to see the new features. It is recommended that you remove your custom theme before installing 2.1.1
Per-pixel kinetic scrolling in file selectors (this will be ported to the console and listbox in a future version)
Updated stock themes to a unified ICS-look - thanks to racks for providing the new look!
Fixed some problems with the implementation of HTC Dumlock
Fixed some device-specific problems on Nook Color and Kindle Fire
Fixed a bug that caused a crash and restart of recovery when rebooting system right after a zip install
Fixed the size calculation of a backup and the size of /data on Galaxy Nexus
2.1.2 (ONLY for Galaxy Nexus) - fixed a bug in the 720x1280 XML layout that prevented restoring a backup
What's new in 2.1:
Note: If you have a custom theme installed from 2.0, your theme will need to be updated to see the new features. It is recommended that you remove your custom theme before installing 2.1
Zip queuing as seen in TWRP 1.1.x is back
Dual storage capable (backup, restore, and install zips from internal or external storage - you choose)
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.x features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup. You can find more information on how your app can use OpenRecoveryScript on this page.
GooManager has a great setup for ROM makers that will notify users automatically when there's an update to their ROM. Combined with the recovery support, this allows users to update their software similar to a normal "OTA" update from their carrier in a simple, seamless install process. The goo.im website has a fantastic developer portal that makes it easy for ROM makers to upload new ROMs and provides free, fast hosting for developers. The GooManager app will also continue to remain free.
Key Features:
Ability to save custom recovery settings
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times.
Theming:
Information on TWRP 2 Theming
Special Thanks To:
Core twrp 2 development team: agrabren, Dees_Troy, ViViDboarder, and AssassinsLament
Toastcfh – for his underappreciated dedication to the community
s0up and kevank for their hard work on the web side of things.
The rest of Team Win: shift, onicrom, netarchy, kevank, myndwire, bigbiff, dkelle4, shinzul, spiicytuna, and eyeballer
Amon_RA - for his great Recovery
Koush - for his dedication to the community and ClockworkMod
For all the help with devices and testing Akmzero, arif-ali, Evil_DevNull, gus6464, Jesusice, _jmz_, NxtGenCowboy, ohshaith55, Pyrostic, [R], and Rootzwiki
As always thank you to the Team's supporters and the Android Community.
Download​
To install:
Download twrprecovery.img from download link
Reboot into bootloader
Issue command "fastboot flash recovery twrprecovery.img"
Profit
Damn man, you're on fire, lol.
Sent from my HTC EVO 4G LTE
DNarsingh said:
Damn man, you're on fire, lol.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Well I kinda got cm10 booting. But i have no display...lol
Sent from my HTC One X+ using xda premium
jmztaylor said:
Well I kinda got cm10 booting. But i have no display...lol
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Hey, its a start and a lot better than nothing. Thanks again for everything your doing.
Sent from my HTC EVO 4G LTE
This is relevant to my interests.
I of course use TWRP on my EVO 4G LTE.
Should I put this on my Jetstream now, or wait?
Great to see some love here!! If CM10 arrives I jump straight in !!
Works Good! Thanks for that!
Mega Thanks
Thanks very much for remembering the forgotten HTC loyalists who shelled out huge money for an abandoned device. If you get a JB or ICS ROM working I am all in!
Thanks
Russ741
I have just flashed TWR and it works great.
I hope JB rom will be available soon so I can flash it.
Thanks man :good:
Can someone post the TWRP binary if they have it? I don't have it and the link is dead.
I asked @jmz for it a week ago, but I haven't heard from him/her yet.
here's a link to the twrp version that was once posted here:
https://dl.dropboxusercontent.com/u/5952907/twrprecovery.img

[DEV][RECOVERY] TWRP 2.6.3.1 for Moto X - UNLOCKED BOOTLOADERS ONLY ! -

What is TWRP?
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Click to expand...
Click to collapse
{
"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"
}
Changelogs
[RECOVERY][OFFICIAL] TWRP 2.6.0.0 touch recovery [2013-07-23]
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Phone look:
Tablet look:
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
Click to expand...
Click to collapse
I don't have this device but I build this for this great community.
Test and report.
Also,if something doesn't work,give me a recovery log.
Downloads :
Test Build #1 - http://d-h.st/Wne
Test Build #2 - http://d-h.st/Nhf
Test Build #3 - http://d-h.st/EGP
Click to expand...
Click to collapse
Source code : https://github.com/oblikas/android_device_motorola_ghost
Credits:
@mattlgroff for his device tree
Good luck :good:
mattlgroff said:
Good luck :good:
Click to expand...
Click to collapse
Thanks mate
Can you give it a shot?
oblikas said:
Thanks mate
Can you give it a shot?
Click to expand...
Click to collapse
I would if I had a Moto X to try it out on. :fingers-crossed:
mattlgroff said:
I would if I had a Moto X to try it out on. :fingers-crossed:
Click to expand...
Click to collapse
Oh sorry,I didn't know lol
Fun fun fun! I'll try this when I get back.
Sent from my XT1058 using Tapatalk 4
hidea said:
Fun fun fun! I'll try this when I get back.
Sent from my XT1058 using Tapatalk 4
Click to expand...
Click to collapse
Nice,thanks
Flashed ok, but it just hangs on boot loader unlocked warning screen
Sent on my Moto X
flashallthetime said:
Flashed ok, but it just hangs on boot loader unlocked warning screen
Sent on my Moto X
Click to expand...
Click to collapse
can you take a last_kmsg or something?
Sent from my Nexus 4 using xda app-developers app
oblikas said:
can you take a last_kmsg or something?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Also insert your data cable in your device and see how is it recognized in device manager.
Sent from my Nexus 4 using xda app-developers app
You're going to want to read this guide on how to compile TWRP, your source code doesn't have the modified init.rc required for TWRP to even boot.
[DEV]How to compile TWRP touch recovery by Dees_Troy
mattlgroff said:
You're going to want to read this guide on how to compile TWRP, your source code doesn't have the modified init.rc required for TWRP to even boot.
[DEV]How to compile TWRP touch recovery by Dees_Troy
Click to expand...
Click to collapse
Oops,my mistake
Sent from my Nexus 4 using xda app-developers app
mattlgroff said:
You're going to want to read this guide on how to compile TWRP, your source code doesn't have the modified init.rc required for TWRP to even boot.
[DEV]How to compile TWRP touch recovery by Dees_Troy
Click to expand...
Click to collapse
Also we don't have the RECOVERY INITRC line in BoardConfig.
Sent from my Nexus 4 using xda app-developers app
oblikas said:
Also we don't have the RECOVERY INITRC line in BoardConfig.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Of course not, that's from my CWM device tree, which doesn't require an Init.rc file.
Also, be aware that TWRP does not support F2FS yet, so /data/ probably won't backup and restore without fixing it on your side or pull requesting changes to their source.
mattlgroff said:
Of course not, that's from my CWM device tree, which doesn't require an Init.rc file.
Also, be aware that TWRP does not support F2FS yet, so /data/ probably won't backup and restore without fixing it on your side or pull requesting changes to their source.
Click to expand...
Click to collapse
Also,I think the ramdisk offset is wrong,it's different in stock image.
Sent from my Nexus 4 using xda app-developers app
oblikas said:
Also,I think the ramdisk offset is wrong,it's different in stock image.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Works fine for my TWRP test?
http://batakang.com/ftp/recovery/ghost/twrp_test_touch69.img
Sent from my SGH-M919 using Tapatalk 2
New test build
Link : https://d-h.st/OZm
oblikas said:
New test build
Link : https://d-h.st/OZm
Click to expand...
Click to collapse
Give it a try again, cross my fingers and toes
Sent from my XT1058 using XDA Premium 4 mobile app

[RECOVERY] Open Recovery TWRP 2.7.1.0 | Free For All

Team Win Recovery Project
for Huawei Mediapad
{
"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"
}
​
Chagelog:
What's new in 2.7.1.0 :
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
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 keOnly For KitKat ]yboard
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
Download:
TWRP 2.7.1.0
In case of Twrp freezing with a blank screen, like previous versions except the very first release, disable screen timeout.
Team Win Recovery Projecty 2.7.1.0 - 05.08.14
- Fixed mount sdcard / intrenal storage
- Add mount otg-usb
Update
Which device is this for?
omniphil said:
Which device is this for?
Click to expand...
Click to collapse
OP's title says "Mediapad" so I think it's for the s7-301u. He's one of the 2 famous devs for keeping the Mediapad alive for 2 years after its EOL.
The original Mediapad is still a good device, and the X1 is its true successor.
joytest said:
OP's title says "Mediapad" so I think it's for the s7-301u. He's one of the 2 famous devs for keeping the Mediapad alive for 2 years after its EOL.
The original Mediapad is still a good device, and the X1 is its true successor.
Click to expand...
Click to collapse
Ok, so that's the Tablet and not the Mediapad phone...
omniphil said:
Ok, so that's the Tablet and not the Mediapad phone...
Click to expand...
Click to collapse
LOL....the Mediapad is ALSO a phone....in tablet form. It is 7" 1280x800, with a Qualcomm S3...a beast for its day. It's being used by the kids now
joytest said:
LOL....the Mediapad is ALSO a phone....in tablet form. It is 7" 1280x800, with a Qualcomm S3...a beast for its day. It's being used by the kids now
Click to expand...
Click to collapse
Ah, so you can see where the confusion is with the naming conventions from Huawei.
Mediapad vs Mediapad X1
Hellooo !
To be honest I dont remember how to install the TWRP, why? cuz i did it a loooooong time ago and nowdays i only flash the *.zip in my Galaxy S3mini
Im using the MediaPad Lite 7 ( s7 - 932u ) and i have the twrp on it, can someone be the kindly one that explain it to me?
I like Twrp so much, that i have two of them installed. Probably since a very long time. Occasionally, Twrp 2.3.2.3 could not access sdcard, a reboot fixed that. I could not explain that to myself. Since the update to 2.7.1.0, occasionally a Twrp 2.3.2.3 shows up, which cannot access the sd.
BTW, how big is the MP's Recovery Partition supposed to be? Mine is 16mbyte, big enough for two recoveries, and maybe corrupt.
Update
Team Win Recovery Projecty 2.7.1.0 - 13.07.14
- Fixed mount /cache
zyr3x said:
Team Win Recovery Projecty 2.7.1.0 - 13.07.14
- Fixed mount /cache
Click to expand...
Click to collapse
hello everyone ... but how do I install this img file?
thank you
lucacata said:
hello everyone ... but how do I install this img file?
thank you
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
zyr3x said:
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry but I have not figured out how and where to perform the installation ... could you help me?
lucacata said:
sorry but I have not figured out how and where to perform the installation ... could you help me?
Click to expand...
Click to collapse
Get the device into fastboot mode by pressing Power + Down Vol
Connect to the PC and type those commands by zyr3x
I updated with Rashr. There's also Flashify and Rom Installer, the latter one having issues with the MP.
The secondary recovery Twrp 2.3.2.3 is still there and can be invoked by a cold start. Is 16mbyte the correct size for the recovery partition, as something must have gone wrong in the past?
Sorry but i didnt understand...is it for Mediapad X1, will it work?
moviehunter2009 said:
Sorry but i didnt understand...is it for Mediapad X1, will it work?
Click to expand...
Click to collapse
Not
Sent from my Nexus 4 using XDA Premium 4 mobile app
Huawei mediapad x1 recovery
Is there any recovery, either Cwm or TWRP for the Huawei mediapad x1?
I think i've read about one real custom rom(cm11?), so there must also be a recovery.
Not necessary for modded, rooted stock roms installed via standard procedure. Though I installed one for convenience on the original MP, with Comec rom.

[RECOVERY] TWRP 2.7.1 for Desire X

TWRP 2.7.1​
Team Win Recovery Project 2.7, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s 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"
}
You can use this recovery with any android version upto 4.4. This includes all sense,cm,stock roms etc
Credits: Nexus prime
Downloads:
TWRP 2.7.1 with Selinux (recommended)
TWRP 2.7.1 without Selinuxhttp://d-h.st/G6a
Changelog:
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
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 (
Click to expand...
Click to collapse
Awesome dude, eagerly awaiting Sellinux kernel now
Tested a small Boot backup and restore and it works. I don't have space to do the whole data or system backup.
Is this the same version i installed with the toolkit today?
There i get many grafic glitches on my desire x.
Bib_x said:
Is this the same version i installed with the toolkit today?
There i get many grafic glitches on my desire x.
Click to expand...
Click to collapse
The graphic glitches are probably related to flashing unstable roms and not wiping after new install as i'm using this recovery and experience no graphic glitches.
and the recovery from toolkit is most likely the older twrp recovery
Do we need a kernel with SElinux to flash the cm11 you shared or just the recovery will do?
Sent from my HTC Desire X running mySENSEdx5 RC4.0
Dolanoi said:
Do we need a kernel with SElinux to flash the cm11 you shared or just the recovery will do?
Sent from my HTC Desire X running mySENSEdx5 RC4.0
Click to expand...
Click to collapse
Directly flash the recovery. No kernel required.
InfinityShooter said:
Directly flash the recovery. No kernel required.
Click to expand...
Click to collapse
Alright. I'll try your cm11 build in about an hour..
Thanks!
Dolanoi said:
Alright. I'll try your cm11 build in about an hour..
Thanks!
Click to expand...
Click to collapse
Wont boot
Wait for fozzy's build instead
InfinityShooter said:
Wont boot
Wait for fozzy's build instead
Click to expand...
Click to collapse
Ohh.. Alright.
But I'm definitely gonna try the recovery!
Stunning Work As Always @InfinityShooter :good:
Finally smooth scrolling in file manager.. Thanks for your hard work
Keep up :good:
Just did a full backup and restore. Works like charm!
Well done! Waiting for a cm11 build now..
Am i right, if i install s-off i can install new roms without flashing boot.bin with fastboot?
Simply flash the new rom, wipe cache witch twrp and i don´t need computer anymore for adb commands?
Wipe cache is not working without s-off if i do it with twrp?
Btw it isn't hard to enable selinux in kernel compilation, but IMHO it is not everything needed. I can provide you a SElinux enabled kernel for test, twrp should have a test to verify selinux.
Found bug where I can't flash boot.img from recovery
//.dax said:
Found bug where I can't flash boot.img from recovery
Click to expand...
Click to collapse
I think you cant, only with S-Off and that has the Vibration-Bug...
Pandur said:
I think you cant, only with S-Off and that has the Vibration-Bug...
Click to expand...
Click to collapse
I am S-Off.. Restoring from backup works fine, flashing together with ROM too, but flashing separately not.
Error has something to do with name of the partition, because it shows that kernel has to be flashed on Boot LNX or something, I don't know
i install it after i use 2.5.0.0 and its works good ... Thanks!
Now we need KitKat :cyclops:

[2014-09-22] [MT2-L03] TeamWin Recovery Project

Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
See Post 7 for the Stock Recovery if you failed to keep a copy for yourself: Click here
Steps for Backing up Stock Recovery:
Code:
fastboot boot /path/to/TWRP.img
The above command will only boot the recovery and will not overwrite your stock recovery making it possible to backup your stock from within TWRP. Now backup your recovery partition from within TWRP. It will be saved on your device and named, recovery.emmc.win. You can rename it to recovery.img to flash it back via usage of fastboot or apply restore within TWRP given the original filename, recovery.emmc.win.
Or within a terminal using dd (aka Data Destroyer);
Code:
dd if=/dev/block/mmcblk0p19 of=/sdcard/stockrecovery.img
TWRP for MT2-L03​
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.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Installation (PC):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
- Also, a video to demonstrate the process of installing TWRP - Credit goes out to @superbass311:
Installation (Device)(More Experienced Users Only!):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- You MUST be rooted!
- Must have Busybox installed or a properly compiled DD binary
- Download TWRP Recovery
- Install a Terminal Emulator from the Play Store
- Type, then Enter:
Code:
su
Followed By:
Code:
dd if=/path/to/TWRP.img of=/dev/block/mmcblk0p19
Download:
- TWRP 2.8.0.0
CONTRIBUTORS
@Modding.MyMind
@xordos
@Shaky156
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel/dtb
- Stock Kernel
- Stock DTB
- TWRP source from Omnirom
- MT2-L03 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: Stable
- Created 2014-09-22
- Last Updated 2014-09-22
Unlock Your Bootloader:
As we all know, you are not required to be rooted to install TWRP, however, you must unlock the bootloader on your device.
You must email [email protected] asking:
Hello I purchased the Ascend Mate 2 and I would like my bootloader unlock code.
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxxx
Thank you
Click to expand...
Click to collapse
You should get a response within 24 hours. In a situation where 24 hours has passed by than simply be patient or send another email. This is the 1st step to being able to unlock your bootloader (as of now)!
Here is a video to demonstrate to you viewers how you can go about unlocking your bootloader.
- Video credit goes out to @superbass311
*Reserved Again*
I will flash tomorrow. You just made the HAM2 the hottest phone out.
Sent from my MT2L03 using XDA Free mobile app
Thanks to all involved. Re-installed root using TWRP. Now Titanium Backup is working properly.
Flashed just now!
Backing up at the moment.
THANK YOU ALL!!!
How I did it:
Win 8 pc.
Phone booted and usb debugging allowed.
typed "adb.exe reboot bootloader" in cmd terminal
typed "fastboot flash recovery c:\adb\TWRP.img" in cmd terminal
I downloaded zip to my adb directory, also had to rename it too "TRWP.img" as download was "TWRP_MT2-L03_RECOVERY.img"
back up completed in 480 seconds!
Did have to play with TWRP settings as I hadn't used it in a while .
DID I SAY THANK YOU!!!
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is backup of stock recovery, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Thanks iammudd, I think it is confirmed the recovery image is same for all MT2L03 phone.
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Thanks for the great work!
TheGeekRedneck said:
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Click to expand...
Click to collapse
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
xordos said:
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Check your hangouts
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
xordos said:
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Interesting that backup filename is 1970-03-23 but the timestamp is 1979-12-31 23:00 on the phone.
After FTP'ing them onto Win7, their last modified times are 2013-12-31 22:00.
The device configuration folder used to build TWRP is available on my github which you can find the link in the OP under "SOURCES". If you have any knowledge on this stuff then feel free to look it over and throw some patches my way. As it stands, mtp isn't working properly however, mtp has only been known to work for a very small select list of devices. A very small list. As for the time stamp, this isn't much of a concern on my part as it is merely cosmetic. However, the problem with it would most definitely be the result of the actual TWRP source and not the configuration folder (device tree). Feel free to look further in to it if it is bothersome.
Right now, my goal is to see if I can resolve the mtp issue if it happens to be at all plausible since the mtp featured in TWRP is still fairly new and has much more work to be done with it over at TeamWin.
Currently looking in to offmode charging as well. This is merely cosmetic. But would be nice to have.
xordos said:
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is stock, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Click to expand...
Click to collapse
Yes, md5 are the same and fc on Win7 of your/my versions are the same.
4L0M said:
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
Click to expand...
Click to collapse
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
xordos said:
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Click to expand...
Click to collapse
I'd be willing to be a guinea pig for the Mt2-l05 if you need more people.
I second that
Sent from my MT2L03 using XDA Free mobile app
Gir357 said:
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
Click to expand...
Click to collapse
L should be released sometime in October I believe, alongside the new Nexus phone and tablet.
Supposedly the HAM2 is getting an EMUI 3.0 update (KK) in November. I don't know if the US version is included though.

Categories

Resources