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.
Related
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
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:
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.
Helloo.. what's up guys...
I'm so sorry. Long time no post.. hehe
Today i'm gonna share custom recovery (again) for Samsung Galaxy V SM-G313HZ aka vivalto3gnvdx. This custom recovery called TWRP 3.0.
Quoted from official website :
Screenshots :
{
"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"
}
What’s new in 3.0.2-0:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
Link : Since our device officially supported by teamwin, then all updates can be downloaded directly to the official website TWRP on the vivalto section here
Old build :
What’s new in 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
Link :
Odin version
Flashable version
Changelog :
Fix MTP
Thanks to Allah SWT
Credits :
Team win
Cleverior
corphish (for his clue to fix MTP)
And you...
DO WITH YOUR OWN RISK !!!
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
PLEASE PUT THIS POST AS SOURCE. THANKS
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
doesntexits said:
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
Click to expand...
Click to collapse
Ok.. thanks for correction.
MTP is detected but can not mount. In adb, device is in recovery status. not in device status. is this same with you ?
screenshot of adb is attached.
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
doesntexits said:
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
Click to expand...
Click to collapse
There is no custom lun in my boardconfig. Maybe i can try to add it later. And the correct lun file location is in /sys/devices/virtual/android_usb/android0/f_mass_storage/lun .
I'm using TWRP source from omni source.
adb shell is working bro. Now your problem is MTP only.
doesntexits said:
adb shell is working bro. Now your problem is MTP only.
Click to expand...
Click to collapse
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
cleverior.ipul said:
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
Click to expand...
Click to collapse
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
doesntexits said:
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
Click to expand...
Click to collapse
Ya, even using custom lun but still not working.
Update with fix MTP
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
which version of firmware do u use ? have u try to install twrp using odin ?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
If you install TWRP from Odin, make sure you've choose .tar file as PDA, if not the recovery won't be installed
There's no way to install it through stock recovery, since it always gives "E: Signature verification failed".......
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Kazryu said:
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Click to expand...
Click to collapse
When install custom recovery using Odin, don't tick auto reboot. After install successfully, pull your battery out, seriously!
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
doesntexits said:
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
Click to expand...
Click to collapse
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
cleverior.ipul said:
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
Click to expand...
Click to collapse
It adds f2fs support for TWRP recovery, so we can flash other ROMs with f2fs partition support
I cannot use `adb shell`, can you use it?
---------- Post added at 14:33 ---------- Previous post was at 13:57 ----------
In TWRP 2, I remove all adbd control scripts in init.rc, just leave adbd service def, then in init.recovery.scx15.rc:
Code:
on init
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct D002
write /sys/class/android_usb/android0/functions [B]mtp,mass_storage,adb[/B]
# adb won't work in OSX without this
write /sys/class/android_usb/android0/bDeviceClass EF
write /sys/class/android_usb/android0/bDeviceSubClass 02
write /sys/class/android_usb/android0/bDeviceProtocol 01
[B] export PATH /sbin:/system/bin
export LD_LIBRARY_PATH .:/sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /external_sd
write /sys/class/android_usb/android0/enable 1
start adbd[/B]
So now I can use adb shell and MTP in TWRP 2.
Dude, on the TWRP Official Site I see it is in version 3.0.2-0, so it is safe to install that version and you will update this thread to the new version ?
TWRP RECOVERY FOR GALAXY J7 PRIME
{
"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"
}
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR BRICKS. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOADS:
twrp3.1.0-0
Use Odin to flash.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot to if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery. If you choose to 'Allow' then SuperSU needs to be flashed to disable dm-verity.
To Root:
Flash the latest SuperSU:
http://www.supersu.com/download#zip
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
(Note this MUST be flashed before SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install modded kernel from below.
5. Reboot
Modded Kernel:
https://mega.nz/#!tJ5XVa4I!_kMCzV7kOMvEdvJwB3ZUDPZjGUNIuuzK6RSLHMiZG4M (Thanks to maxx35000)
NOTE: NO NEED TO FLASH MODDED KERNEL IF YOU ARE USING ANY CUSTOM ROM
HIT THANKS IF I HELPED YOU:good:
is this oficial ?
Mounting internal is working?
Not work on last update from samsung, with update AQC4 recovery not incompatible
Janeslejade said:
Mounting internal is working?
Click to expand...
Click to collapse
Yes. Read the thread on how to do this.
hoangphuc057 said:
Not work on last update from samsung, with update AQC4 recovery not incompatible
Click to expand...
Click to collapse
It's working. I'm on AQC4
Not working on G610Y.
---------- Post added at 09:23 AM ---------- Previous post was at 09:11 AM ----------
Guys, i want to go back to stock recovery, questions.... Is it safe to flash this stock recovery??
SM-G610F/M_stock_recovery
My unit is G610Y.
Up... Please help, i need the SM-G610Y_stock_recovery... Please someone help or advise if SM-G610F/M_stock_recovery is okay to flash on G610Y??
Help guys! I tried to root my phone but no success. It says need adb 1.3 or newer. What should i do?
External sd mounting?
Thanks for the update, working on G610M
4. Install modded kernel from below.
Click to expand...
Click to collapse
how to do this?
Ephesis said:
how to do this?
Click to expand...
Click to collapse
Flash through odin in AP
Siddhant NAik said:
Flash through odin in AP
Click to expand...
Click to collapse
how about rooting? flash via odin too?
---------- Post added at 09:52 AM ---------- Previous post was at 09:40 AM ----------
Flash through odin in AP
Click to expand...
Click to collapse
Odin wont read it since its a zip file not a tor file.
inamie said:
External sd mounting?
Click to expand...
Click to collapse
This is the essential question!
thank
trinaldi said:
This is the essential question!
Click to expand...
Click to collapse
not working.
Anyone tried this on G6100 ?
Please update aqc4 mod kernel
Thank you bro. Haha :d :d