TWRP for Transformer Pad TF201T
{
"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"
}
MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1
Changelog 2.7.8.2
- All Upstream changes
- Small changes to the 'new theme' (thx z31s1g)
- Added flash to staging partition, via flash image feature.
Changelog 2.8.7.1
- Removed ability to flash raw .img files....
- gui: keyboard: support longpress label offset, code cleanup ( Thx @_that)
- Added flashable zip
- merged upstream changes
Changelog- 2.8.7.0
- Fully merged 2.8.7.0 source from upstream
- Removed SU from twrp ( Its useless & only takes up extra room)
Changelog- 2.8.6.5
- New theme fully implemented ( Huge thx to @z31s1g ) Still a WIP
- Fix mount -o bind error on recreating /data/media/0 (Huge thx to @xiaolu ) & ( @_that )
- All upstream merges by Team Win
Changelog 2.8.6.1
- GUI: Prevent duplicate page overlays. Thx Matt & _that
- Replace legacy DEVICE_RESOLUTION with the new TW_THEME
- Using new common repo to build recovery.
- Build with grimlocks-5.1 kernel from zombi
- All upstream changes. Thx TeamWin
Changelog- 2.8.6.0
- All upstream changes (They are on git)
- Cleaned up external mount labels
Changelog- 2.8.5.1
- Added dock sd card support to twrp
Changelog- 2.8.5.0
- Added formatting of ext sdcard for ROM2SD & DATA2SD
- Added ability to backup ext sdcard partitions
- Added reboot to recovery & reboot to bootloader from with TWRP
- Fixed error formatting /data to f2fs <- Thx Dees Troy for this fix
- A few upstream changes
Click to expand...
Click to collapse
UPGRADE INSTRUCTIONS----------------------------------------------------------------------------------------------------------------------------------------
- Flashing recovery with fastboot
- Boot tablet into fastboot.
Code:
fastboot -i 0x0B05 flash recovery foo.img
- Replace foo with the file name.
- Once flashed reboot into bootloader.
Code:
fastboot reboot-bootloader
- Enter recovery.
----------------------------------------------------------------------------------------------------------------------------------------
- - Flashabale zip
- Boot into current recovery .....
- Flash the zip it is signed so turn that on ......
- Reboot in to android, fully
- Boot into bootloader, enter newly flashed RCK ....
----------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
TWRP for TF201T [KANG], Tool/Utility for the Asus Eee Pad Transformer Prime
Contributors
lj50036, hardslog
Source Code: https://github.com/zombi-x-lp
Version Information
Status: Testing
Created 2015-03-06
Last Updated 2015-03-06
DOWNLOADS
OLDER VERSIONS
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] WILL UPLOAD
The more you know
JOIN US ON IRC !!!https://webchat.frt/
Channel: #zombi-x
HOW TO TAKE A RECOVERY LOGYou will be taking this log cause of some kind of error message .....
Once you get and error message, here is how to retrieve a recovery log ....
Using a PC with adb/fastboot installed on it, and if windows the correct drivers. ....
Code:
adb pull /tmp/recovery.log
This log will be in the same directory as the terminal/cmd window is cd'd into ....
Now you have the log, upload it to a pasting site or for download, and give us a link....
lj50036 said:
it may appear to hang on the twrp curtain, let it boot there is nothing wrong here
Click to expand...
Click to collapse
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
flumpster said:
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
Click to expand...
Click to collapse
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
lj50036 said:
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
Click to expand...
Click to collapse
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
https://www.androidfilehost.com/?fid=95916177934537081
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
Got it if you would like to pull the download your call ....
Yes I will go back to stock bootloader then upgrade .....
Will let you know how I get on ....
Thx Josh
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Lavrentsii said:
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Click to expand...
Click to collapse
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
lj50036 said:
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
Click to expand...
Click to collapse
Cheers mate. I am in bed at the moment but I will make you another test tomorrow with your recovery added into it for you to try.
lj50036 said:
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
Click to expand...
Click to collapse
I'm testing DATA2SD on a non-supported ROM (Katkiss LP with Grimlock 300t/201 kernel) and so far with this recovery and the DATA2SD zip it seems to be working fine. This looks pretty promising
lj50036 said:
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
Click to expand...
Click to collapse
I can confirm that this works thanks to Josh's help/instruction on doing it. He is an awesome & great teacher as I learned so much from him. GREAT RECOVERY! Thanks again Josh! :good:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
elchevi said:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
Click to expand...
Click to collapse
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
lj50036 said:
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
Click to expand...
Click to collapse
Maybe choosing among some predefined templates would do the trick for most users. But yes, it can be potentially problematic hehe
Thanks!
Img vs. blob
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
JuraP said:
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
Click to expand...
Click to collapse
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
lj50036 said:
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
Click to expand...
Click to collapse
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
JuraP said:
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
Click to expand...
Click to collapse
It does not matter you can leave it .img or rename it .blob will not matter ....
Thx Josh
Related
This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
3.Nexus 5 (HammerHead)
Prerequisites
Code:
1. A Hammerhead
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[url]http://forum.xda-developers.com/google-nexus-5/orig-development/recovery-twrp-2-7-0-0-f2fs-support-t2746030[/url]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Now Scripts are Device Specific
6. Error conditions at many places so a noob cant go wrong
***Special note for CM /CM based ROM users***
Code:
I dont test the script since I dont own an HH !! This is the CM kernel by @kdh2834
If it does not work kindly post the detailed error on the thread . Will try my best to resolve it
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM/or a Stock ROM with busdybox installed
Instructions
Code:
[LIST=1]
[*] Unpack the Zip file you downloaded from Link Below to a folder named F2FSROMConvetor (Dont Mess with the name).
[*] Take Care that the path you extract my Zip for eg in my case "C:\Users\Nabendu\Desktop\F2FSROMConvetor"
does not contain any blank spaces in between or else the script will not work as intended.
[*] Run F2FS Convertor.bat
[*] Select your device
[*] Place the Zip in the Extract /Input directory when prompted
[*] The script will Unpack your ROM
[*] Select option of boot.img based on your rom
[*] Repack your ROM
[*] A black window will open showing the Repacking progress. Dont close my Blue Window anytime during it the repacking process.
After 100% repacking is done the Black Window will close automatically and you can now press any key to Continue
[*] Check NEW F2FS ROM directory for the Repacked ROM
[*] Flash and Enjoy
[*] Cleanup the working directory cleanup.bat (Cleans everything including original input ROM.Only a copy of the Output ROM is maintained)
[/LIST]
***FAQ's***
Q. I get errors compiling the ROM on my XYZ Windows Version?
A. Read through my steps once again especially point 1 & 2. Hopefully u can get it to work.
If you think you are doing everything correctly post it on the thread and Ill try to reply within 24Hrs.
Q. I want to do it on Linux !! Why you no create bash scripts ?
A. Im not good at bash scripting !! Also dont own a Linux Distro so cant help you guys !! But look here @jolinnard has a script for Linux users
https://github.com/figue/f2fs-scripts/blob/master/convert_ROM_to_f2fs.sh and make necessary changes for Hammerhead updater script if any
Q. I can do the same with the Convert to F2FS apk on the Playstore ?
A. Sure you can. Converting on mobile is easier also. But only reservation is that it is paid.Not everyone can afford it.
Also time permitting Ill create a Android Terminal Script based on jolinnards script for Linux.
Q. Do you think I can convert it myself ?
A. Yes its just clicks . Read my steps and do it you wont go wrong.
Download Links
1. V1.1 OLD
2.V1.2 NEW
Changelog
Code:
V1.0 Intial Release
V1.1 : Add Device Support
1) Added Device Compatibility : Nexus 5
2) Scripts now will come seperate for each device.
3) Did some cleaning up on my messy script
V1.1 : Add more Boot.imgs for N5
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
[user=4851200]@Rohit02[/user] For being the beta tester
[user=14325584]@kdh2834[/user] For his AOSP Kernel
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work
Screenies
Screenies atlast
{
"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"
}
Excellent test on
Big thanks
c-rom v6.4 Network Connectivity fail
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
I dont own a HH so not much I can help you with !! But try flashing a different kernel on top of it , think it should work !! And does c rom used the aosp kernel in the first place !! Look at the thread for modified Kernels , i guess flashing one should solve your problem !!
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img (AOSP) that NABENDU1 provide inside his tool will not work with your rom.
c-rom is aosp based.
micr0g said:
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img that NABENDU1 provide inside his tool (AOSP) will not work with your rom.
Click to expand...
Click to collapse
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
belictony said:
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
Click to expand...
Click to collapse
Okay you have the com.androidprocess phone fc problem right !! If its only that Ill patch the kernel myself and get you a new one in a few mins and rest assured it will work for sure !!
rabbo3 said:
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
Click to expand...
Click to collapse
Yup what kind of Rom u use !! If it has differential update like Mokee OS or xdelta ( I dont know xdelta/opendelta in detail ) like Omni I can create some kind of allied script for it too !! Put the same question in the N7 2012/N4 but dint get any responses for it mosly due to devs still use the traditional way !! Anyways if anyone wants patching for those im up for the task !!
EDIT: Version 1.2 for HH online ( Bigger Size due to 4 boot.imgs included in the script itself)
Dl Link : https://mega.co.nz/#!dxcVmQRS!5zv6RCqJs82rv5-aW3GqICW5YgCPuZtUhiH0F1vpVP8
Changelog:
Added CM boot.img ( Untested by me ) thx to @kdh2834
Added Purity boot.img ( Untested by me) thx to @kdh2834
Added AOSP com.android process phone fc boot.img ( Untested by me) thx to @me
Kindly post feedback on the thread !!
I will fix the screenies sometime later or tomm
I've used this tool to successfully switch over to f2fs-all with crDroid (a CM based rom). My biggest problem, however, is that I am completely unable to flash elementalx afterward because it freezes on boot. Anybody found a way to fix this?
Edit, I'm an idiot. I found out I have to manually mount /system before flashing ElementalX
fantastic job, works great with cm11-m6,very faster
Great!
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
tavocabe said:
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
Click to expand...
Click to collapse
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
NABENDU1 said:
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
Click to expand...
Click to collapse
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
callidus_ex_de_latebros said:
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
Click to expand...
Click to collapse
Moto G is infact already has /data partition in F2FS file format !! The only thing is making the cache and system full f2fs !! For this firstly your kernel dev should take a initiative to create a fully compatible f2fs kernel and also a f2fs recovery !! Once that is done I would be more than glad to help you guys out !! Anyways till then enjoy f2fs on /data !!
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
Works fine on my crDroid setup. Did it work for you before with Euroskank? Have you tried toggling from MTP to PTP and back? If you have a secure screen lock in place, are you ensuring that you have unlocked the phone after plugging it in? Are you waiting to plug the phone in until after it's booted up? Just trying to rule out the obvious troubleshooting steps
Sent from my Nexus 5 using Tapatalk
work in 4.4.3?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
It works for me using omni-elementalx.
danielalonso said:
work in 4.4.3?
Click to expand...
Click to collapse
Yes
To @NABENDU1
Hi, so far everything is good, only complain is that most of the times when I reboot to recovery and flash any update to rom/kernel or when I add a new rom using multirom (tested and working good with omni, slim and paranoid), when finished and reboot the phone I see the boot screen many times. Like a bootloop but eventually it makes it to the rom or the multirom menu to select a rom. Is this because of my configuration of f2fs with multirom or maybe the kernel I use (elementalx shared with all the roms)?
@NABENDU1 thank you very much for this, it's quick and easy as well as educational (to me)
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.
TWRP Recovery 2.8.6.0 for LG L7II
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or any other damage made to your device. Please
* do some research if you have any concerns about features included in this
* RECOVERY before flashing it! YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/
In this thread you can find:
Post#1:
1. Presentation
2. Changelog
3. Known bugs + fixes
Post#2:
1. Flashing instruction
2. Thanks
3. Donator Hall of Fame
4. Download links
Post#3:
1. Tutorial on how to make ADB work on windows (with or without MTP)
2. Images of the recovery
1. Presentation:
TeamWin Recovery Project – or TWRP for short – is a fully touch-based custom recovery that was initially developed for Nexus devices, but has since been made available for countless other smartphones and tablets as well, in form of both official and third-party builds.
2. Changelog:
Code:
[U]07.08.2015 - Twrp 2.8.7.0[/U]
Updated to latest Twrp
Added IMEI back-up
[U]12.06.2015 - Twrp 2.8.6.0[/U]
Settings storage is by default External SD
Ext-sd will not be wiped on factory reset (even if the text says so; ignore it)
You have all 3 partitions (internal, external, ext-sd) in MTP now
Updated to latest TWRP 2.8.6.0 source
[U]06.01.2015 - Stable2[/U]
improved code a little
disabled things that are not used
reduced maximum brightness
added Qcom time fix
NEW: added support for sd-ext (2nd partition on sdcard)
[U]02.01.2015 - Working Internal[/U]
Read the warnings (in RED) in the 2nd post.
Internal storage is working now xD
[U]25.12.2014 - Updated to latest TWRP 2.8.3.0[/U]
[U]19.11.2014 - Final release[/U]
- bugs: none
Aroma Fm inverted is not because of recovery.
Not mounting internal is not because of recovery and will not be added because you can mess up your data partition losing all data (our internal is in data/media)
We have full working brightness and screen timeout
[U]10.11.2014 - Beta 1[/U]
- bugs:
after entering screen timeout mode the led backlight won't turn on again
- fixed bugs:
messed up display
flipped screen
unresponsive touch screen
partition problems
[U]09.11.2014 - Closed Alpha 2 - No public download[/U]
- bugs:
flipped screen
unresponsive touch screen
partition problems
after entering screen timeout mode the led backlight won't turn on again
- fixed bugs:
messed up display
[U]05.11.2014 - Closed Alpha 1 - No public download[/U]
- first release
- bugs:
messed up display
flipped screen
unresponsive touch screen
partition problems
after entering screen timeout mode the led backlight won't turn on again
3. Known bugs:
NONE!
1. Flashing instruction:
METHOD 1:
*OUTDATED: Just open the zip from last version and copy that recovery.img if you want to use this.
Copy the "recovery.img" from download to the root of the SD card.
Code:
1. With terminal emulator or using adb do this:
2. adb shell
3. su
4. dd if=/storage/external_SD/recovery.img of=/dev/block/mmcblk0p17
METHOD 2:
Download the version you like (the zip) and flash it in any recovery.
VERY IMPORTANT: EVERYTIME YOU FLASH TWRP AGAIN GO TO SETTINGS AND RESET DEFAULTS.
THE DEFAULT STORAGE MIGHT BE INTERNAL STORAGE PRESS ON THE PLACE THAT SAYS STORAGE: INTERNAL STORAGE AND CHANGE TO EXTERNAL STORAGE IF YOU WANT TO USE THAT (TWRP will remember the choice).
IF WINDOWS RECOGNIZES THE INTERNAL STORAGE IT WILL TRY TO FORMAT IT TO USE IT (this is because of the ext4 extention). DO NOT FORMAT OR YOU LOSE YOUR INTERNAL STORAGE DATA. LINUX DOESN'T HAVE ANY PROBLEM.
2. Thanks:
All Omni and TWRP team.
@Dees_Troy
The IRC channel for TWRP.
3. Donator Hall of Fame:
@vlmaxx - huge thank you man! ^.^
4. Download link:
TWRP_2.8.7.0_L7II.zip
Old:
TWRP_2.8.6.0_L7II.zip
Any kind of mirroring, repacking, uploading this files or files that come from this files on other websites/forums is not allowed. If you want guys on other forums to get this, give them the link to this. Thanks. Please respect my work and do not reupload this files.
How to make ADB to work on Windows:
adb-setup-1.4.2.exe: http://tinyurl.com/qca8abd
LG Drivers: http://tinyurl.com/l3mgf49
1. Delete all LG Drivers you have and all related to LG (Pc suite or anything else) and restart PC.
2. Install the LG Drivers from the rar and also the installer for ADB answering Y, Y, Y and follow the on screen driver installer.
3. Get in recovery and go under Mount and disable MTP if it is enabled. Connect USB. You will get this. Open device manager and you will find that our pictures are alike.
{
"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"
}
4. Right click the yellow triangle icon and right-click it choosing Update Driver Software. You get this.
5. Click the down option. You get this.
6. Click the Let me pick from a list option. You get this.
7. Select ADB Interface and press Next. You get this.
8. Scroll down selecting the LGE Mobile Adb. Press Next. You get this.
9. Press Yes and then Close and you are done.
Proof working recognized with MTP off in Recovery and Sideload and last picture with MTP on (recognizing the sdcard).
Hit thanks please if this helped you. Have a nice day.
Good job I will test this in the night
P.S. I can install this on cwm??
sirion123 said:
Good job I will test this in the night
P.S. I can install this on cwm??
Click to expand...
Click to collapse
Hmm maybe if i make a flashable zip though I have seen ppl prefere to flash it via fastboot. We don't have fastboot so just flash it like i said. It's easy ^.^..
EDIT: NVM made the cwm flashable zip.
Ok. Maybe I'll wait for the others and then install
sirion123 said:
Ok. Maybe I'll wait for the others and then install
Click to expand...
Click to collapse
Just flash that with CWM it's safe it won't destroy your data or system will catch on fire it is tried on my own device.
I install this and this is very good work! But when I reboot to system screen flipped at the moment. I found this one bug
sirion123 said:
I install this and this is very good work! But when I reboot to system screen flipped at the moment. I found this one bug
Click to expand...
Click to collapse
If you like it press the THANKS BUTTON that is in the bottom right of the post. I know about this bug it is normal and it's not really a bug blame lg ^.^. badly mounted screen for this models. This bug won't interfere with anything ^.^ You can see it just when you close the recovery.
Excellent job! It's works on P713 KK CIS!
Themes are applied successfully!
The option "Disable MTP" disables ADB mode too. - SOLVED!
UMS mode for external SD is not supported.
AROMA FM still inverted.
We are waiting for the final version and fixes! Good luck!
Thx, sir. Its work on my LG P713 (4.1.2)
the_vanya1 said:
Thx, sir. Its work on my LG P713 (4.1.2)
Click to expand...
Click to collapse
You are very welcome my friend. Giving back the work haha. Respect to you when i was on 4.1.2 I used your custom rom. EPIC. Respect.
And recovery is perfectly compatible with nandroid manager...
maxx_hr said:
And recovery is perfectly compatible with nandroid manager...
Click to expand...
Click to collapse
Thanks for letting people know.
TWRP Recovery
christi9503 said:
Thanks for letting people know.
Click to expand...
Click to collapse
Please tell me whether it is possible to install on the LG P715 Dual.
vlmaxx said:
Please tell me whether it is possible to install on the LG P715 Dual.
Click to expand...
Click to collapse
Not tested on P715 but it should work. 99,9% it will work my friend. Also no chance you will manage to hard brick it just by flashing. I did not include preloader and bootloader partitions. At most a soft brick but not even that. Just flash it.
EDIT: @vlmaxx Report after flashing please. But for sure it will boot.
TWRP
christi9503 said:
Not tested on P715 but it should work. 99,9% it will work my friend. Also no chance you will manage to hard brick it just by flashing. I did not include preloader and bootloader partitions. At most a soft brick but not even that. Just flash it.
EDIT: @vlmaxx Report after flashing please. But for sure it will boot.
Click to expand...
Click to collapse
Ok. I will try tomorrow to try. Then I will unsubscribe.
TWRP
christi9503 said:
Not tested on P715 but it should work. 99,9% it will work my friend. Also no chance you will manage to hard brick it just by flashing. I did not include preloader and bootloader partitions. At most a soft brick but not even that. Just flash it.
EDIT: @vlmaxx Report after flashing please. But for sure it will boot.
Click to expand...
Click to collapse
Sorry, I'm not good at English. Lost your message, so I answer here.
Sew through CWM Recovery. Starts but tach screen almost does not work or is not adequate. Reacts only INSTALL and offers mount, and then nothing can be done. Rollback on old CWM.
Forgot to specify: I have 4.1.2. Maybe that's why is not working?
vlmaxx said:
Sorry, I'm not good at English. Lost your message, so I answer here.
Sew through CWM Recovery. Starts but tach screen almost does not work or is not adequate. Reacts only INSTALL and offers mount, and then nothing can be done. Rollback on old CWM.
Forgot to specify: I have 4.1.2. Maybe that's why is not working?
Click to expand...
Click to collapse
Nope that is not the case. Think it's the touch drivers can be different or smth. Please make a video place on youtube. I'll make a different build with p715 kernel.
TWRP
christi9503 said:
Nope that is not the case. Think it's the touch drivers can be different or smth. Please make a video place on youtube. I'll make a different build with p715 kernel.
Click to expand...
Click to collapse
Sorry, but it's all too complicated for me. Years and brains are not the same .... unfortunately. In any case, thank you very much for your help.
{
"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"
}
This is only for Huawei Mate 8 (NXT)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-next.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_next/releases/download/3.1.1-1/twrp-3.1.1-1-next.img"][U]download twrp-3.1.1-1-next.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which Mate 8 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
[TWRP][3.1.1-0][MATE 8][DECRYPTION SUPPORT], Tool/Utility for the Huawei Mate 8
Contributors
OldDroid, XePeleato, surdu_petru
Source Code: http://ttps://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-04-08
Last Updated 2017-06-11
Reserved
TWRP 3.1.0-1 next for encrypted/ decrypted data
This post has been deplaced here. I'll remove it when the TWRP above will work for encrypted/ decrypted data.
Thanks for comprehension!
I'm glad, that we can help the Mate 8 community
Thanks for distribution ...
The themes are here now.
Thanks!
Thak you very much.
I have your "Boot_Insecure_B560_Fix-adb_dm-verity.img" installed. Do you recomend to go back to stock boot and use this TWRP for any flashing? Or shoud i stay in a insecure boot?
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Us there 2 differnt versions of this twrp 1 for decripted data and 1 for formated data ??
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
We can see what we can do with the both. A merger is perhaps possible?!
Edit:
Already it works with untouched boot.
With no formatted datas, it seems to me.
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
franzyroy said:
We can see what we can do with the both. A merger is perhaps possible?!
Edit:
Already it works with untouched boot.
With no formatted datas, it seems to me.
Click to expand...
Click to collapse
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads : twrp-3.1.0-next-v2.img md5 : 7ee1833ea51bf3835efc23851ad9a011
surdu_petru said:
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads :twrp-3.1.0-next-v2.imgmd5 : 7ee1833ea51bf3835efc23851ad9a011
Click to expand...
Click to collapse
It seemed to me that dexz had tested it like that.
If I can test it, I'll do it. In the week, it's not really possible for me. @dexz should can do it.
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
With the TWRP here, the root works too.
surdu_petru said:
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads :twrp-3.1.0-next-v2.imgmd5 : 7ee1833ea51bf3835efc23851ad9a011
Click to expand...
Click to collapse
The one I tested and working yesterday was with /dm-0 before you posted another version.
Anyway twrp-3.1.0-next-v2.img is working fine and decrypted. Using adb shell mount. it show /data is on /dev/block/dm-5 the same with the one I have tested before.
Edit : I got force reboot using twrp-3.1.0-next-v2 after 5 seconds
Edit2 : It's only stop force reboot when I got the "Unmodified System Partition" screen.
Edit3 : I see force reboot stop if there's no changes on twrp setting (example time zone, language & etc)
@surdu_petru
Yes I just test it this twrp-3.1.0-next-v2.img and like @dezx I have force reboot when I use TWRP File Manager
dexz said:
The one I tested and working yesterday was with /dm-0 before you posted another version.
Anyway twrp-3.1.0-next-v2.img is working fine and decrypted. Using adb shell mount. it show /data is on /dev/block/dm-5 the same with the one I have tested before.
Edit : I got force reboot using twrp-3.1.0-next-v2 after 5 seconds
Edit2 : It's only stop force reboot when I got the "Unmodified System Partition" screen.
Edit3 : I see force reboot stop if there's no changes on twrp setting (example time zone, language & etc)
Click to expand...
Click to collapse
jac10000 said:
@surdu_petru
Yes I just test it this twrp-3.1.0-next-v2.img and like @dezx I have force reboot when I use TWRP File Manager
Click to expand...
Click to collapse
Perhaps you should make that and send the console.recovery.log to @surdu_petru or @OldDroid because if they have made the TWRP with mine, it's perhaps the cause.
@surdu_petru
---->logs
Thanks guys for feedback
I'll upload a new version very soon, hope will fix reboot issues !
I say that because :
I have no issues with a prerooted boot
It's also with Decrypted data boot
I can install a zip without to see an error
I see the internal storage
I can also see the size, not 0 MB
Only thing which doesn't work fine, when I mount the data, it's unmounted in the 5 seconds.
surdu_petru said:
Thanks guys for feedback
I'll upload a new version very soon, hope will fix reboot issues !
Click to expand...
Click to collapse
Thank you. Looking forward to it.
Sorry I'm out of like bullet :laugh:
New Test Version 3 !
Downloads : twrp-3.1.0-next-v3.img md5 : d969789ee06d3d323a98d9f028e6f475
Thank you for the feedback
TLDR:
1: MAKE A BACKUP. Seriously.
2: Downloads in second post. Flash recovery, then kernel, then MultiROM.
{
"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"
}
Introduction
This is a port of Tassadar's MultiROM, a multi-boot mod for OnePlus 2. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
This is still experimental!
Make backups. Seriously. Please.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via USB-C OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP_multirom_oneplus2_YYYYMMDD.img) - download the IMG file from second post and use fastboot to flash it.
MultiROM (multirom-YYYYMMDD-vXX-oneplus2.zip) - download the ZIP file from second post and flash it in recovery.
Your current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/nkk71/multirom/tree/master (branch master)
Modified TWRP - https://github.com/nkk71/Team-Win-Recovery-Project (branch android-7.1-mrom)
Device tree: https://github.com/MZO9400/device_oneplus_oneplus2-mrom -b twrp-mrom
Thanks
This port is based on the hard work of Tassadar, 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, Hashbang173, and many others. Thank you.
Issues
- None that are known. If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it in the thread
- IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.
Changelog
Here
Downloads
Downloads in second post
NOTE:
Third party kernels with kexec-hardboot support (can be flashed to primary ROM): THIS IS NO KEXEC MultiROM, you don't necessarily need kexec hardboot supported kernels
Extra Information
Unlike some of the other 64-bit MultiROM ports, this port does have kexec-hardboot enabled, which is less risky and speeds up boot into secondary ROM. Anyone porting MultiROM to a Snapdragon 810 device may find the source to be useful. The patch was written by @500 Internal Server Error
XDA:DevDB Information
MultiROM for OnePlus2, Tool/Utility for the OnePlus 2
Contributors
MZO, nkk71, martinusbe
Source Code: http://github.com/multirom-dev
Version Information
Status: Stable
Current Stable Version: v33b
Stable Release Date: 2017-05-13
Current Beta Version: v33b
Beta Release Date: 2017-04-20
Created 2017-04-20
Last Updated 2017-05-13
MultiROM (folder):
DOWNLOAD
MultiROM v33b
TWRP MultiROM v3.1.1
MultiROM Uninstaller
MultiROM manager modified with OP2 commits has been attached to this post
Method of flashing multirom.
________________
1. Go to TWRP 3.1.0 officially that u already have
2. Flash the multirom image file .. and select recovery when it asks whether u want boot or recovery.
3. When successful go back to maim page and hit reboot recovery
4. Now its multirom
5. Flash the provided multirom zip file. An auto reboot will occur. Hit cancel and go to MISC tab to hit reboot recovery
6. Now the existing rom u had , is primary
7. Go to 3 dot menu of TWRP on upper right corner.
8. Select add rom
9. Flash desired rom
10. Reboot recovery again when successful
11. Go to 3 dot menu again and select list rom
12. Tap on add zip file and add gapps here... That is whatever u file want to flash on a rom just select that rom from rom list and add zip from there
[when flash a secondary, u have to flash zip, then back, and add zip and flash gapps]
13. Hit reboot system.
14. Now a screen will appear even before boot to.ask which rom u want to flash. For the very first time the option is set to, if u don't select any it will boot to primary after 5 seconds, so u hit cancel on that screen (pop up actually)
15. Select the desired rom , double tap on it and it will boot.
First boot of a new rom takes at least 15 to 20 real life minutes.
Notes:
__
To change the option of count down of rom booting selection, go to settings of multirom twrp and turn off option from there. Now every time u reboot.. it will ask which rom u want to boot. And if u don't select any it will stay on same screen till u click something
Tested so far:
Nougat based ROMs
OOS stock
OOS based ROMs
H2OS
MIUI
FlyME
Okay so @Tomsgt has made an amazing guide on how to set up and run MultiROM for our device (or any device), you can find his video right here:
<Mod Edit: Link removed for promoting paid service.>
Awesome work
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
martinusbe said:
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
Click to expand...
Click to collapse
Fixed!
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
[email protected] said:
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
Click to expand...
Click to collapse
Probably because of the ROM. It might need more tags since we can't agree on ONE name
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
Its working fine now...awesome work... :good:
Great man, thanks a lot.
Sent from my ONE A2003 using XDA-Developers Legacy app
MZO said:
Fixed!
Click to expand...
Click to collapse
cool, thanks for keeping authorship btw
martinusbe said:
cool, thanks for keeping authorship btw
Click to expand...
Click to collapse
My pleasure used your commits and you helped me in the final stage — well deserved!
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
martinusbe said:
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
Click to expand...
Click to collapse
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
MZO said:
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
Click to expand...
Click to collapse
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
martinusbe said:
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
Click to expand...
Click to collapse
Yep it worked with commas. Uploading now two more names: Oneplus2 (pretty common), onePlus2 (what was I thinking??)
Will i need to wipe internel storage for first time
ShaDow18 said:
Will i need to wipe internel storage for first time
Click to expand...
Click to collapse
No you won't.
MZO said:
No you won't.
Click to expand...
Click to collapse
What about recovery do i really need fastboot mode or flasify can also do