TeamWin Recovery Project 3.0.3
WARNING #1: Unlocking BL and flashing a custom recovery voids your warranty. Please make sure to contact your carrier/seller if your phone is still under warranty after unlocking the bootloader.
WARNING #2: Make sure you have enabled OEM unlock and unlocked bootloader before trying to flash this. How you can successful root and install TWRP will be described below.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
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.
HOW-TO UNLOCK BOOTLOADER
Get bootloader Unlock code here (for more Information look in this thread)
Install minimal adb and fastboot
Plug in your phone and make sure all huawei drivers got installed
Enable developer options in settings as described above.
Enable OEM unlock, enable USB debugging (both in developer options)
Open the adb tool you installed recently
Type fastboot devices (now a device number should show up)
Type fastboot reboot-bootloader (your phone will now boot into bootloader, if not, you haven't set up drivers or adb/fastboot correctly)
This step will wipe all your data! Type:
Code:
fastboot oem unlock xxxxxxxxxxxxxxxx
(xx is for your unlock code)
Ones it's done type:
Code:
fastboot reboot
Your phone will reboot and you have an unlocked bootloader!
You can now go on installing TWRP on your device
HOW-TO INSTALL
Make sure you enabled OEM unlock in settings, if you haven't please do that now by tipping 10 times on build number (to activate developer options), than open developer options and go to OEM unlock, enable it
Have an unlocked bootloader is required! (In my case, I called huawei and received the unlock code 12 hours later)
Download the TWRP recovery from the download section below
Make sure you got fastboot drivers installed (I will describe this below in how to unlock your bootloader)
Open the adb/fastboot application on your pc and go to the directory where your TWRP img file is downloaded
Boot your phone into download mode (First method: fastboot reboot-bootloader while connected to pc. Second method: power off your phone, hit power on and volume down until it boots to download mode)
Check again if there is written: unlocked phone!
If yes type now into your adb/fastboot terminal:
Code:
fastboot flash recovery twrp_huawei_generic_a53_YYYYMMDD.img
Type:
Code:
fastboot reboot
Now boot into recovery by pressing: power+volume up+volume down at the same time
Enjoy twrp
HOW-TO ROOT
Backup, just in case
Have an unlocked bootloader and TWRP installed from above (take one from december)
We will use this root method: Phh's superuser
Download latest official phh superuser zip here.
Put the zip on your external sd card of your phone (since we can't access /data in twrp)
Boot into twrp and flash the downloaded file
Install latest Material phh apk: Release post
Now you are rooted, congrats!
SUPPORTED DEVICES
CAN-L01
CAN-L11
MLA-L03
(Test your Device, if you want to take the risk, and I'll add it to this list )
DOWNLOAD
CHANGES
21.12.2016: First release.
22.12.2016: Backup all your partitions.
16.02.2017: Cleanup, little fixes bump to 3.0.3-0 (Note: Root is just supported for 3.0.2)
17.02.2017: Turn Crypto off again.
KNOWN ISSUES
Encryption is not supported yet!
SOURCE CODE
TWRP: TWRP source code (7.1 branch)
Device tree (International: hwcan (master branch)
CREDITS
TWRP master @jcadduono
For helping a newby: @Tkkg1994
CONTRIBUTIONS
Gerrit for TWRP: Omni gerrit
Gerrit for officially supported devices: TWRP gerrit
XDA:DevDB Information
TWRP for Huawei Nova, Tool/Utility for the Huawei Nova/Nova Plus
Contributors
Xelfmade
Source Code: https://github.com/Xelfmade/android_device_huawei_hwcan
Version Information
Status: Beta
Current Beta Version: 3.0.3-0
Beta Release Date: 2016-12-22
Created 2016-12-21
Last Updated 2017-02-17
XDA:DevDB Information
TWRP for Huawei Nova, Tool/Utility for the Huawei Nova/Nova Plus
Contributors
Xelfmade
Source Code: https://github.com/Xelfmade/android_device_huawei_generic_a53
Version Information
Status: Beta
Current Beta Version: 3.0.3-0
Beta Release Date: 2016-12-22
Created 2016-12-21
Last Updated 2017-02-17
Great! Thanks for this big step for this wonderful device!
Download link for the twrp image does not work...pls help
mshinni80 said:
Download link for the twrp image does not work...pls help
Click to expand...
Click to collapse
AndroidFileHost has some problems right now..show a little patience and look a little later for it..
Cheers xelfmade! Just wanted to ask if this is specifically for the nova or the nova plus? Or is it compatible with both models? Thanks!
Can we backup all partitions and restore them (with decrypted data off course)?
And does knock on screen to take screenshot work? Someone told it don't work anymore after root?
uchihasparky said:
Cheers xelfmade! Just wanted to ask if this is specifically for the nova or the nova plus? Or is it compatible with both models? Thanks!
Click to expand...
Click to collapse
You can try it on the Nova plus and report me if it works or not. If it doesn't work write me a private message and I sent you the stock recovery.. ?
merlin21 said:
Can we backup all partitions and restore them (with decrypted data off course)?
And does knock on screen to take screenshot work? Someone told it don't work anymore after root?
Click to expand...
Click to collapse
Not now, I'll upload a newer version were you can backup and restore all partitions..
I'm rooted and it just works. I think it's because he formatted /data for decrypt it.
good morning...can I also use SuperSU. Coz I would prefer that over Phh's superuser.
I assume that it won't make a difference, but I want to be sure!
Thx in advance
mshinni80 said:
good morning...can I also use SuperSU. Coz I would prefer that over Phh's superuser.
I assume that it won't make a difference, but I want to be sure!
Thx in advance
Click to expand...
Click to collapse
You can try it, but I don't expect it to work..
Xelfmade said:
I'm rooted and it just works. I think it's because he formatted /data for decrypt it.
Click to expand...
Click to collapse
What should I try first to don't get this problems? Don't touch data while installing twrp and phhs su?
I'm on can-11 and believe my data is encrypted from original rom?!
And did you edit the config file in superuser. zip?
The linked one has following setting :
eng verity crypt
I cant access data or anything else in TWRP... I dont have an sd-card yet. is there no other way to install the superuser zip??
mshinni80 said:
I cant access data or anything else in TWRP... I dont have an sd-card yet. is there no other way to install the superuser zip??
Click to expand...
Click to collapse
To get access on /data, you have to format it in the wipe menu.
merlin21 said:
What should I try first to don't get this problems? Don't touch data while installing twrp and phhs su?
I'm on can-11 and believe my data is encrypted from original rom?!
And did you edit the config file in superuser. zip?
The linked one has following setting :
eng verity crypt
Click to expand...
Click to collapse
No I don't.
So if we don't wipe the data partition we could read it like before after root? And is the data encrypted afterwards?
Sorry for so many questions [emoji56]
merlin21 said:
So if we don't wipe the data partition we could read it like before after root? And is the data encrypted afterwards?
Sorry for so many questions [emoji56]
Click to expand...
Click to collapse
We can't read /data wether the phone is rooted or not..
The phone is encrypted as soon as you choose a locking method.
-=MoRpH=- said:
To get access on /data, you have to format it in the wipe menu.
Click to expand...
Click to collapse
So I have to wipe it again, like it happened after unlocking the bootloader? Then I could plug it and copy the zip file on the internal storage to run it?
If u use the latest version, try the following steps:
-- First format /data
-- reboot the Recovery
-- copies the files from your pc to the internal storage
Gesendet von iPhone mit Tapatalk
work for Europe version CAN-L11
my mobile was rooted with some error but root work perfect and thx again. willing to soon see cyanogen roms
-=MoRpH=- said:
If u use the latest version, try the following steps:
-- First format /data
-- reboot the Recovery
-- copies the files from your pc to the internal storage
Gesendet von iPhone mit Tapatalk
Click to expand...
Click to collapse
so format /data is inevitable?
Yes
Gesendet von iPhone mit Tapatalk
Related
ATTENTION!
You MUST read all the guide BEFORE doing it, if you do it without reading all of it first you may ends up bricking your phone!
Prerequisites:
Asus ZE500KL (may work on ZE500KG, but haven't tested, do it on your own risk) on Marshmallow, NOT LOLLIPOP!
Also, it must have fully booted AT LEAST one time, otherwise, you'll soft-brick it.
If your phone is not on Marshmallow, you can use THIS guide insteadDownload and put the unlocker zip file and the SuperSu zip file in the phone
How To:
1 - Install adb and fastboot driver (follow THIS guide)
Now you can connect the phone to your computer2 - Reboot in fastboot mode with one of the following method:
a -Volume Up while booting upb -With adb, after enabling USB debugging in developer settings, using:
Code:
adb reboot bootloader
Now that you are in bootloader, you have to boot in TWRP,
download THIS recovery (is the twrp one) and boot in to it, using this command:
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
Code:
fastboot boot TWRP-x-x-x-x.img
(Obviusly the recovery name must be the one you downloaded)
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
It should automaticaly enter in recovery.
Now you MUST flash FIRST ZE500KL_BootloaderUnlock.zip, otherwise you'll brick your phone
Btw, the recovery will mount your phone's memory, so you can put now the files in the phone, if you forgot to do it before
AFTER you installed the unlocker zip, you can install the SuperSu zip
When the install is complete, clear the cache and reboot your phone, now you can enjoy your root!
Downloads:
Latest @MiauLightouch TWRP - 3.0.0.2 Mirror
Latest SuperSu zip - 2.65 Mirror
Bootloader Unlocker (from @MiauLightouch original post) - Mirror
Credits:
@MiauLightouch for pretty much everything
@LuK1337 , @luca020400 and everyone on #titandev for being awesome
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
MuzgontarAco said:
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
Click to expand...
Click to collapse
I would recommend Z00L/T, you will get cm13, official unlock at least.
You Say " May Work On ZE500KG" Is ze500kg already receive Marshmallow Update?
MiauLightouch said:
I would recommend Z00L/T, you will get cm13, official unlock at least.
Click to expand...
Click to collapse
thanks for the advice but my choices are poor with about 5 phones in this price range with this one looking waay better.. getting it via contract so yeah..
How to install supersu zip? Tia.
Working! Have you tried to flash Viper4Android? On lollipop this will break Call recording and FM Radio, maybe this will not be a problem on MM?
Seanjhon027 said:
How to install supersu zip? Tia.
Click to expand...
Click to collapse
Inside TWRP there is a big "Install" button, press it and select the zip
what is the meaning of booted
mohamedelkholy said:
what is the meaning of booted
Click to expand...
Click to collapse
context?
until you saw the lock screen, that's what "booted".
stuck waiting for device
C:\Users\Clynt\Desktop\Android M>adb reboot bootloader
C:\Users\Clynt\Desktop\Android M>fastboot boot twrp.img
< waiting for device >
Ok I don't know where I get wrong but I got this error.
Img file name is ok because I renamed it.
Drivers were installed already.
Developers mode is enabled already.
Windows 7 64bit
Tried rooting this using lollipop and everything went well.
thanks!
UPDATE: i got it. it has something to do with the drivers.
Without opening the bootloader.
Notice. I have not tried it.
http://www.asus-zenfone.com/2016/05/how-to-root-asus-zenfone-2-laser-ze50kl-marshmallow.html?m=1
thanl you man i have rooted my zenfone 2 laser
Thanks very much for this guide and your work.
Can I install the new update v13.10.7.1 when I opened bootloader.
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
thanks
thks TS
now my phone its rooted
Muminek111 said:
Without opening the bootloader.
Notice. I have not tried it.
No... when trace a perequisite link Given..
you really need to unlock bootloader first
wulfe13 said:
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
Click to expand...
Click to collapse
i think isnt permanent, this step is needed to boot into twrp then flashing a unlockBL..
to make permanent.. the command must "fastboot flash recovery twrp_X.X.X.X.img"
but make sure to unlock bootloader first...
CMIIW
Click to expand...
Click to collapse
Is it me or everytime I reboot the device after rooted, it's going back to unrooted?
Root is a success tho, great job, OP!
Edit: okay, not every reboot, but after several reboots, then it went back unrooted
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Not to hijack your thread, so consider this a free bump, but I am also curious. Galaxy S7 G920T here and looking for the same options.
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Sent from my Redmi 2 using Tapatalk
fake2die said:
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Click to expand...
Click to collapse
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
veez21 said:
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
Click to expand...
Click to collapse
Right! So you can accomplish a Magisk install without a custom recovery for example using the Magisk Manager or Flashfire but as stated above, in order to boot a modified boot.img the bootloader needs to be unlocked or otherwise it will refuse to boot it.
There should be an option to install magisc like a systeme update with the stock recovery.
Gesendet von meinem XT1650 mit Tapatalk
JRapsky said:
There should be an option to install magisc like a systeme update with the stock recovery.
Click to expand...
Click to collapse
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Sytis said:
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Click to expand...
Click to collapse
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
COOLPLAY6FAN said:
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
Click to expand...
Click to collapse
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Actually you can boot into twrp rather than install/flash twrp which means u must use cmd to boot twrp everytime for flashing something~ As for locked bootloader, just like others said, you must unlock it.
Didgeridoohan said:
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
Click to expand...
Click to collapse
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
COOLPLAY6FAN said:
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
Click to expand...
Click to collapse
There are installation instructions on how to create the patched boot image with the Magisk Manager in the release thread.
When you have the patched_boot.img file, you'll need to flash it to your device. On most normal devices you can do this with fastboot. Check out your device's forums/DuckDuckGo/Google/Whatever-search-engine-you-use for instructions on that.
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
* Unlocked bootloader is needed. Period.
* A custom recovery is needed to flash Magisk. TWRP for instance.
* That custom recovery prevent the built-in OTA update to work
* But TWRP can flash OTA updates that can be downloader from XDA for example
Am I correct?
Also,
* Magisk needs a patched boot image
* This image has no impact on the OTA process at all
* There are encryption matters to take care of (I don't understand them yet though).
Is everything correct?
Thanks.
Krystanos said:
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
Click to expand...
Click to collapse
Let's see about answering those statements/questions.
* Unlocked bootloader is needed. Period.
Click to expand...
Click to collapse
Yes.
* A custom recovery is needed to flash Magisk. TWRP for instance.
Click to expand...
Click to collapse
Not necessarily. You can let the Magisk Manager patch your device's stock boot image and then flash it to your device with fastboot. See the installation instructions in the release thread.
* That custom recovery prevent the built-in OTA update to work
Click to expand...
Click to collapse
Yes.
* But TWRP can flash OTA updates that can be downloader from XDA for example
Click to expand...
Click to collapse
No. And yes. Official OTA files can (most of the time) not be flashed in TWRP. ROM zips and flashable firmware packages can.
* Magisk needs a patched boot image
Click to expand...
Click to collapse
Yes, that's all Magisk is about.
* This image has no impact on the OTA process at all
Click to expand...
Click to collapse
It definitely does. See the official docs
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips for more info on how to keep OTA capabilities for your device.
* There are encryption matters to take care of (I don't understand them yet though).
Click to expand...
Click to collapse
Possibly. Depends on what you're talking about.
Great answers. It's more clear for me now. Many thanks sir!
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Hi!
There are good news for you, rooting with magisk is very easy that way . No bootloader unlocking, custom recovery,
adb and fastboot command, no sdk no mtk tool . NOTHING but Sp flashtool - our best friend. This method really works with mtk phones android 5.0+ .
What U only need is
Sp flashtool and its drivers /scatter file with the ROM/ -I think not mtk devices with their own flashtool will work too
the ROM of your device
Magisc manager app on the phone
First of all you need clear up the device / after backup somewhere if needed/with sp flashtool - flash the whole ROM in format+download mode.
Install Magisc manager app , it will load for U a zip file in the map of the app
Put the boot img file of your rom in that map too
Run install option - it will create a patched boot img file within the app s map
Run again sp flashtool with download mode , mark only the boot section , and flash that patched boot img in phone
After reboot phone it is rooted
best regards
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
lefteriskmail said:
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
Click to expand...
Click to collapse
Install Magisk Manager.
Press install.
Select "Patch Boot Image File".
Select the stock boot image you've previously saved on your device.
Wait.
Flash the patched boot image to your device.
Done.
All of this is covered in the installation instructions...
The folder being mentioned above is MagiskManager on your internal storage (where the patched boot image is also stored).
Magisc
Hi!
Magisc works fine for me from the first time. Excuse me I won't do installation again to see how it goes. Really it causes some hesitation but in the end it's clear.
I use Total commander, and magisc folder is on the external SD card after installing magisc manager app. Factory reset later will not clear the root. After installing manager it says "not installed" till the end of the rooting process. Opening the app it begins to look after the downloadable zip file, you have to wait and download it. This zip and the stock boot img must be in the same place in a folder, and the app itself makes the patched boot img but I don't remember what was the name of the option. This is the flashable img file. In the end after flashing with flashtool and rebooting, magisc manager says "installed". Good luck
Hi, I am trying to centralise this sort of information and am compiling it in another topic for Magisk and android-based media centres too.
Trying to properly document things (full sentences with references, links, and examples) rather than just writing some brief summarised steps that most people will not understand - not just for myself but to share should it assist others learn and understand the preparation and steps involved, plus consequences and ramifications of their actions (which never seem to be stressed enough).
Here is what I have compiled. Hopefully it will help and prevent you going loopy!? :silly:
- - - - - - - - - - - - - - - - - - - -
*** EXTREMELY CLEAR MAGISK ROOT INSTRUCTIONS ***
(Work In Progress! To Be Verified & Critiqued By Others)
Connect your WiFi so that all auxillary files can be downloaded during the rooting process.
Ensure you have a minimum of 2GB of free disk space. Allow for 1-2 hours to perform these steps. Do not rush!
Bootloaders come with every Android device, and give it all the instructions on how to boot and what to execute. If your Bootloader is locked, then you have not flashed anything like TWRP previously, or, you have re-flashed a stock Bootloader and Recovery, etc. The process is much easier when you have previously rooted the device using another method, and the Bootloader already unlocked.
To preserve your System partition, Magisk only modifies the unlocked Bootloader boot partition, which can easily* be restored and 'locked' later.
0. Before starting anything, always perform a FULL Backup (ADB) of your device, using a good quality USB cable and ADB FastBoot toolkit. Or on some devices you can use a Micro SD card with a TWRP recovery.img to boot into TWRP to perform a backup of partitions. Do both if you want! Make sure you search for the appropriate commands and usage of ADB FastBoot backup so that all data is backed up and included.
> ADB FastBoot: https://developer.android.com/studio/releases/platform-tools.html
> TWRP: https://dl.twrp.me/twrpapp/ \\ https://twrp.me/FAQ/
> Plus various other solutions...
1. Identify your device's firmware, build number, Bootloader, full unique model number, etc. Download any two of these apps:
a) AIDA64 ("System", "CPU" & "Android" tabs.)
b) Device Info HW ("General" & "System" tabs.)
c) DevCheck ("Hardware" & "System" tabs.)
2. Download the stock Bootloader, Recovery and Firmware (___.tar.md5) for your device model, variant and OS. (e.g. match your firmware, build number, bootloader, full unique module number, etc). Some sites will force you to pay to download - search around and you can get free download links, or sometimes from the manufacturer's site. From this firmware, we need to either extract or download the stock Bootloader.img image separately.
3. Install Magisk Manager v5.3-v5.6 as of 2017.02.22 ("Magisc" is typo by guy above).
4. Open Magisk and go to settings, adjust theme, change the language, enable notify for updates, change prompt timeout, etc.
5. On the home screen of the Magisk Manager app, click "Install" then in the pop-up select "Install" again.
a) If you have root access already, choose "Direct Method" - Select, wait, reboot and done (very easy!);
b) If you have stock recovery & locked bootloader, choose "Patch Boot Image File" - in the pop-up explorer, browse for the downloaded Bootloader Image.
c) ... I don't know about "Download ZIP Only" - I assume for flashing with Odin or ADB FastBoot from PC or existing root/unlocked user....?
NOTE: If you are being asked to browse and select a file, be aware that there is no confirmation! As soon as you click, that JPG or RAR archive will be used for patching (and result in an error if cannot be extracted!!!)
6. A file will likely be downloaded in the background (flashable ZIP), a black screen will pop-up processing etc. Wait.....
The processed Boot image will be processed and output to the /MagiskManager/ directory.
If you do NOT have root, or custom recovery, you will need to:
a) grab a PC, install the USB drivers for your device and confirm your device is fully recognised
b) then flash the "patched" Boot image from the Magisk Manager directory with ODIN for Windows or FastBoot on Windows via a good-quality USB cable.
7. ...
8. ...
I think that is it... I may have forgotten something. Please advise if something needs to be fixed or corrected. My Media Centre was already unlocked, so I did not have to unlock and flash the Bootloader.
9. Install free TWRP on your device, and choose to backup any partitions, should you wish to restore them later. Set an alarm to backup your device every few months! What are you prepared to lose if your device was lost/squashed/washed/crunched et al.???
Say thank you and donate to the amazing and all powerful Magisk developer 'TopJohnWu' and team!
Sweet! :fingers-crossed:
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_mate9_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Contributors
**** Pretoriano80
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
**** @Tecalote - He was the main tester for this version and also he was the one that convinced me to open this thread in first place
**** @Blackball
**** Team OpenKirin - thanks for the "Oem Path wipe esclusion" code
Download links
twrp_mate9_0.1.img - initial release
Thank you for such a great project!
I am very happy with this TWRP. Everything is working so far on EMUI, Android 8.
Data wipe is possible, cause OEM Path is excluded.
Vendor.img and System.img and recovery_ramdisk can be flashed by choosing img to the related img.
Backup, restore of all shown Partitions working perfectly.
Decryption of storage if using Fingerprint /PIN is working. Full encryption support for data..
Many thanks to @Pretoriano80 for this awesome and first most complete TWRP for Mate 9 :good::good:
BTW: @Blackball had tested this TWRP for P10 Plus and it is also working on this Device (so it will run also on P10).
Many thanks for testing too :good:
This is good to know... Going to have to give this TWRP a try. So what, to decrypt data, do I just have to format data in TWRP or?
Wirmpolter said:
This is good to know... Going to have to give this TWRP a try. So what, to decrypt data, do I just have to format data in TWRP or?
Click to expand...
Click to collapse
Format data is only necessary if installing AOSP based Roms which require this (in installation guide)
But for Stock Firmware you don't need to decrypt (format) anything because encryption is fully supported
Of course, you can't install older Stock based Custom Rom which mount data in the updater-script without /dev/block/dm-0
I tried to installed on my Huawei mate using RR remix treble Rom, but It doesn't work, it just boot on the TWTP logo then boot up again.
osk4rin said:
I tried to installed on my Huawei mate using RR remix treble Rom, but It doesn't work, it just boot on the TWTP logo then boot up again.
Click to expand...
Click to collapse
We are aware of this, but this is the initial release.
It's fully working on EMUI for now.
Tecalote said:
We are aware of this, but this is the initial release.
It's fully working on EMUI for now.
Click to expand...
Click to collapse
Oh right, thanks.
Seems to work perfectly, in my case the rom doesn't even seem to be overwrite twrp upon normal boot
Thanks a lot!
osk4rin said:
Oh right, thanks.
Click to expand...
Click to collapse
If you (or anyone else) are still having/testing a custom rom, please send me /system/build.prop and vendor/build.prop.
i end up with error 255 on huawei mate 9 rooted oreo mha-l29 8.0.0.360(c567)
when i try to backup and at the beginning of twrp boot it ask me for a password
Caguayote said:
i end up with error 255 on huawei mate 9 rooted oreo mha-l29 8.0.0.360(c567)
when i try to backup and at the beginning of twrp boot it ask me for a password
Click to expand...
Click to collapse
If it's ask for password, then insert the same passwords/pin/pattern that you are using in Android, so TWRP can decrypt the internal storage.
That's the whole purpose of having a TWRP with decryption support.
10-4
Thank you for the clarification
Pretoriano80 said:
If you (or anyone else) are still having/testing a custom rom, please send me /system/build.prop and vendor/build.prop.
Click to expand...
Click to collapse
how can I get them?
osk4rin said:
how can I get them?
Click to expand...
Click to collapse
If your Phone is rooted, with Root Filemanager like FX Explorer or Mixplorer you can copy from /system/build.prop and /vendor/build.prop
Work this nougat .. ??
Tecalote said:
If your Phone is rooted, with Root Filemanager like FX Explorer or Mixplorer you can copy from /system/build.prop and /vendor/build.prop
Click to expand...
Click to collapse
I just attached the build.pro files .Using RR remix treble project
Hi, I really appreciate this recovery, just have one question: is there a way to enter the decryption pwd only once and not with every TWRP start? Would make things easier (even I understand the current way is much safer...). Thanks and respect!
_Nostromo_ said:
Hi, I really appreciate this recovery, just have one question: is there a way to enter the decryption pwd only once and not with every TWRP start? Would make things easier (even I understand the current way is much safer...). Thanks and respect!
Click to expand...
Click to collapse
No, it's designed to work like this!
Pretoriano80 said:
No, it's designed to work like this!
Click to expand...
Click to collapse
Ok, thought so, it definitely makes sense, just being a bit lazy... Thanks a lot for your prompt response, Pretoriano80! :good:
Unofficial TWRP 3.2.3-0 UA
F2FS Support
EFS & Persist backup support
Clean device tree
Based on Unlegacy-Android kernel
Regular updates
Known-issues
HTML:
- To be filled
Installation
HTML:
1. Go in fastboot mode (hold down Power + Vol down for few seconds.
# Or use flashers like Flasify/FlashFire and others
2. Open terminal window/command prompt to execute following commands:
fastboot erase recovery
fastboot flash recovery twrp_mako-3.2.3-0.img
3. With volume up and down select recovery mode and press power button
4. Enjoy your reboot in TWRP
Downloads:
Latest: AFH
Credits:
Special thanks to
- TWRP team
- Unlegacy-Android team
- Clamor
- And anyone I forgot to mention
Additional sources:
Kernel Sources: Github
TWRP Sources: Github
XDA:DevDB Information
Unofficial TWRP 3.2.3-0 UA, Tool/Utility for the Google Nexus 4
Contributors
sudokamikaze, clamor
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery/tree/mako
Version Information
Status: Stable
Created 2018-08-16
Last Updated 2018-08-17
Thank you Sir for continuing support mako...
Have a stock Nexus 4.
Will be unlocking it and installing some ROM.
What is the difference between this and the official TWRP version?
Is this version of TWRP better than the official twrp-3.2.3-0-mako?
Thank you.
/root said:
Have a stock Nexus 4.
Will be unlocking it and installing some ROM.
What is the difference between this and the official TWRP version?
Is this version of TWRP better than the official twrp-3.2.3-0-mako?
Thank you.
Click to expand...
Click to collapse
Please, read OP post again. Our recovery has F2FS support for /data & /cache. EFS/Persist backup support, that means you can backup your IMEI/WIFI + BT Mac address stuff. And compare teamwin device tree and ours, I'm sure that you will be impressed
deleted
So should I format all partitions to f2fs and then install LOS? Is that advisable or should I just change filesystem for cache and data?
Edit 1 : btw Great recovery . I had to give it more than 2 tries though at first it got stuck in a bootloop of never entering the recovery page. then i flashed stock and tried again that time it couldn't format and twrp never got proceeded. did a stock flash again and the third time it worked fine.
Edit 2 : So checked the fstab of mako on LOS and it seems f2fs is only supported for /cache and /data. So only those two partitions need to be changed to f2fs format. Am I concluding it correctly?
Thank you @sudokamikaze
/root said:
So should I format all partitions to f2fs and then install LOS? Is that advisable or should I just change filesystem for cache and data?
Edit 1 : btw Great recovery . I had to give it more than 2 tries though at first it got stuck in a bootloop of never entering the recovery page. then i flashed stock and tried again that time it couldn't format and twrp never got proceeded. did a stock flash again and the third time it worked fine.
Edit 2 : So checked the fstab of mako on LOS and it seems f2fs is only supported for /cache and /data. So only those two partitions need to be changed to f2fs format. Am I concluding it correctly?
Thank you @sudokamikaze
Click to expand...
Click to collapse
About EDIT 1:
First of all I'm sorry about that, I will find why and which thing causing this.
I had something like that on friend's phone. But worked just fine after re-entering.
If rom which you decided to use supports f2fs - feel free to use that. Leave system as is
sudokamikaze said:
About EDIT 1:
First of all I'm sorry about that, I will find why and which thing causing this.
I had something like that on friend's phone. But worked just fine after re-entering.
If rom which you decided to use supports f2fs - feel free to use that. Leave system as is
Click to expand...
Click to collapse
Thank you, had no issues flashing and entering recovery and doing a full backup including EFS and Persist.
Otg compatible too?
is this support error digitiser/ nav bar ?
hakimarx said:
is this support error digitiser/ nav bar ?
Click to expand...
Click to collapse
You must check it yourself. Inactive surfaces can be of different widths.
You always have the option to return to the main menu by touching the TWRP logo.
ze7zez said:
You must check it yourself. Inactive surfaces can be of different widths.
You always have the option to return to the main menu by touching the TWRP logo.
Click to expand...
Click to collapse
Thanks..
Btw, please support TWRP multi OS for ubuntu touch
wizmart said:
Otg compatible too?
Click to expand...
Click to collapse
No, it's not compatible with OTG feature, and probably won't be either
Downloading stalled?
Hi. Newb here, been trying to search for an answer, but not sure what it is I'm needing to search for?
Issue is phone is unlocked and am in bootloader mode, and am trying to download above twrp but after entering the commands into my computer terminal, the computer terminal says " sending," and the phone says "downloading," but nothing is happening. Tried this a few times, and have actually left it for an hour, but no download?
Am I missing a step here? Followed the posted instructions.
Thanks for your patience.
toydriod said:
Hi. Newb here, been trying to search for an answer, but not sure what it is I'm needing to search for?
Issue is phone is unlocked and am in bootloader mode, and am trying to download above twrp but after entering the commands into my computer terminal, the computer terminal says " sending," and the phone says "downloading," but nothing is happening. Tried this a few times, and have actually left it for an hour, but no download?
Am I missing a step here? Followed the posted instructions.
Thanks for your patience.
Click to expand...
Click to collapse
Hmm, have you tried to switch USB cable or port or both? and what about official TWRP, same error?
You can try:
HTML:
fastboot erase recovery
fastboot flash recovery recovery.img # CHANGE HERE NAME OF FILE
sudokamikaze said:
Hmm, have you tried to switch USB cable or port or both? and what about official TWRP, same error?
You can try:
HTML:
fastboot erase recovery
fastboot flash recovery recovery.img # CHANGE HERE NAME OF FILE
Click to expand...
Click to collapse
Yes.
Tried
fastboot flash recovery openrecovery-twrp-2.3.2.3-mako.img Terminal says sending 'recovery' (8176 KB)... Phone says nothing
fastboot flash recovery openrecovery-twrp-2.8.5.2-mako.img Terminal says sending 'recovery' (9020 KB)... Phone says " downloading..."
toydriod said:
Yes.
Tried
fastboot flash recovery openrecovery-twrp-2.3.2.3-mako.img Terminal says sending 'recovery' (8176 KB)... Phone says nothing
fastboot flash recovery openrecovery-twrp-2.8.5.2-mako.img Terminal says sending 'recovery' (9020 KB)... Phone says " downloading..."
Click to expand...
Click to collapse
Then problem isn't in my recovery, reinstall drivers/switch pc/cable/port
sudokamikaze said:
Hmm, have you tried to switch USB cable or port or both? and what about official TWRP, same error?
You can try:
HTML:
fastboot erase recovery
fastboot flash recovery recovery.img # CHANGE HERE NAME OF FILE
Click to expand...
Click to collapse
sudokamikaze said:
Then problem isn't in my recovery, reinstall drivers/switch pc/cable/port
Click to expand...
Click to collapse
Thanks, I'm going to try it on another system.
toydriod said:
Thanks, I'm going to try it on another system.
Click to expand...
Click to collapse
FWIW Tried on another computer, and download worked fine. Thanks for you help and for making this.
I currently am on the official 3.1.xx TWRP version, can i just flash this as a zip from the current recovery? will that just replace the old one with this one, or do I need to first flash stock recovery?
[TWRP] MI 11 (Pro/Ultra) (mars/star)
WARNING : I do not know who made this TWRP and I am NOT taking credit for it. It was posted on eu site and I'm just sharing since there was no thread for twrp here on xda.
INSTRUCTIONS
1. Before starting the process, the bootloader must be unlocked.
2. Install Xiaomi USB drivers.
3. Enable Usb debugging from Settings - Additional settings - developer options.
4. Download TWRP for Mi 11 (Pro/Ultra) , and put it in your fastboot folder.
5. Put your phone into fastboot mode.
6. Rename downloaded file to "twrp.img".
7. Do the following command. It will automatically boot into TWRP.
Code:
fastboot boot twrp.img
8. If you get a screen asking for a pin, press 2nd option
and change language to English then enter phone pin.
9. Change language to English (press the 6th option).
10. Go to "Advanced" and select "Onekey inject TWRP".
11. Swipe to inject the TWRP. It might take a few minutes, so don't worry.
Note
1) Don't change the boot slot, currently (Slot A) for most or your device will not boot at all.
2) For user experiencing decrypt issue, you can try one of the methods below to enable decryption:
a. Remove all your security eg. fingerprint, face unlock, pattern and leave ONLY pin. Reboot to twrp and try again.
b. Reflash twrp.
c. LAST RESORT! Format data and factory reset your device then reflash twrp.
3. For user experiencing decrypt issue but just want to flash latest build:
a. Boot to twrp > mount > mount usb storage then transfer your rom.zip to data/media/0
b. Now go to install and look for rom.zip under data/media/0. Profit!
4. The decrypt issue was a bug on the Chinese twrp, no update since may so don't ask for an ETA.
CHANGELOGS
07/18/21
1) Additional instruction from scratch.
2) Additional note for people having decrypt issue.
CTTO: xiaomi.eu, hoangsang
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
skylerfly16 said:
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
Click to expand...
Click to collapse
Yes, They just did the new stable in TWRP Format.
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
speedtripler said:
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
Click to expand...
Click to collapse
Why did you install the Chinese exe?
skylerfly16 said:
Why did you install the Chinese exe?
Click to expand...
Click to collapse
The official one hadn't been released yet and I like a challenge sometimes
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
deleted post
I keep getting a " no such partician " fail msg , what am I doing wrong here?
speedtripler said:
I keep getting a " no such partician " fail msg , what am I doing wrong here?
Click to expand...
Click to collapse
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
heinhuiz said:
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
Click to expand...
Click to collapse
Thx It's ok,I got it after a few attempts
The language on twrp still opens on Chinese and it needs changed to English each time but apart from that it seems to work fine!
SanHelios said:
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
Click to expand...
Click to collapse
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
innocence07 said:
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
Click to expand...
Click to collapse
Is banking and payment apps still working?
Can you still pass safetynet check?
speedtripler said:
Is banking and payment apps still working?
Can you still pass safetynet check?
Click to expand...
Click to collapse
Yes and yes
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
sabrewulf said:
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
Click to expand...
Click to collapse
The recovery is fully functional as far as I can tell...
I did a complete backup successfully but I haven't tried to restore it yet
You click on everything ?
Hi,
after a long day of learning the hard way (got stuck in Fastboot Loop) I am now on stable EU 12.5.7 (MI11 Ultra, EU phone). So far so good, but I was wondering, how can I make TWRP stuck to the phone, meaning, when I push the power button to have an option like: Boot into TWRP. Is that possible or is there a "click this button with this... trick"?
ATM, I can only get TWRP to work, when I enable it via PC, which is not good.
I am asking, because I have an old Oneplus 6, which has this option. TWRP is installed and I can boot directly to it, if I want to.
Can you please help me out? Is there a trick or am I doing something wrong?
Greetings from Germany
Placebo
I believe you are on custom EU rom right? Just reboot into recovery, custom eu rom injects twrp as standard recovery
Hi, yes I am and I did that also. But still can't boot into TWRP from within the phone. Is there a trick after the injection?