Team Win Recovery Project 3.2.2-0
This is for the Lenovo P2a42 only! Do not flash on the Lenovo P2c72!
WARNING: Rooting The Lenovo P2 with SuperSu currently works only in System-Mode, which prevents you from installing OTA Updates!
INFO: Follow the full rooting steps below, in order, to allow system modifications!
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.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the Official Download here (Version: 3.2.2-0): recommended!
https://goo.gl/UbHbkr
You can find the Pre-Official Download here:Currently no Pre-Official!
See Post #3
This is the download link, for instructions on how to flash it, see below.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/ install adb & fastboot to your computer.
{
"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"
}
Download TWRP for Lenovo P2 (P2a42).
In your ROM, go to Settings -> About device. Tap 8 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Once you tap the unlock the bootloader it will ask you to formally submit the request, when you accepted the void warranty thing you will have to wait 14 days.
After 14 days . Reboot your device into fastboot mode. To do this, (adb reboot-bootloader) or select reboot from the power menu and hold the [Volume Down] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run this command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run these commands in order:
fastboot flash recovery twrp.img
fastboot boot twrp.img
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger system modifications for TWRP and TWRP will be installed permanently!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted see Post #2:
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.3-0 (beta) - Initial public beta v1 release.
v3.0.3-0 (beta) - public beta v2 release.
- Enable double-tap to wake in recovery
- Fixed MTP Issues
v3.0.3-0 (Official) - public release.
- fix device name for update.zip's
3.1.1-0 (Official) - Official release.
- Completely rebased on Nougat
- Included OTA support.
3.1.1-1 (Official) - Official release.
- Fix "Format Data" when using default (f2fs)
- Enabled OTA support.
3.2.1-0 (Official) - Official release.
- TWRP base Android 8.1
3.2.2-0 (Official) - Official release.
- TWRP 3.2.2-0 build
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
ADB root
Full SELinux support
Built in android 8.1 tree
KNOWN ISSUES
SuperSU will only work by default in System-Mode because the data partition is F2FS! (by default from Lenovo)
SuperSu's Systemless Mode will work when the data partition is changed to EXT4!
DECRYPTION NOT WORKING?
If your device isn't decrypting in TWRP, chances are you set a boot up password.
You can solve this by disabling your boot up password in your device OS's settings.
By disabling your password your OS will rewrite your crypto key to be compatible with TWRP and TWRP will decrypt with the default password.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
CONTACT & SUPPORT
You can find TeamWin on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/Celoxocis/android_device_lenovo_kuntao_row (android-7.1)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the Lenovo P2, Tool/Utility for the Lenovo P2
Contributors
celoxocis, Maintainer & Developer
Gilotto, Closed Beta Tester
HaJeeEs, Closed Beta Tester
Version Information
Status: Official
Current Official Version: 3.2.2-0
Official Release Date: 2018-07-07
Created 2016-01-07
Last Updated 2018-07-07
Download Counter:
Initial Beta Release v1: 57
Initial Beta Release v2: 20
Official Version: It's Over 5000!
So you are generation Y? too much to read or you don't real at all? Prefer a video? Head over to Youtube!
Video Tutorials on Youtube for Systemless Mode ROOT METHOD
How to ROOT LENOVO P2 | Install TWRP Recovery | Works on Marshmallow Only
How to ROOT Lenovo P2 with Android Nougat | Lenovo P2 Root Tutorial
Thanks to TechXplicit
You don't like command lines? Prefer to click your way through life? Take a look at the Lenovo P2 Root Tool! Head over to Youtube!
Lenovo P2 Root Tool!
Thanks to Varun Sai
----- General Information -----
All donations which are send to me (TWRP appreciation donations)
Will be put forward to support the Official LineageOS development.
Donation Link, please see my signature!
Official TWRP vs LineageOS TWRP
I am on Lenovo's STOCK ROM! All i want is root with STOCK ROM! I don't care about treble! Is this version for me?
YES!!!
I hate the Lenovo STOCK ROM! I want LineageOS Official and root! I want treble and Magisk! Is this TWRP version for me?!
NO!!! Why? Please read this!
Confirmed and working ROOT methods!
Up-to-date: For root with Nougat please use phh's supersu
Use version 2.59 from here
Install phh's SuperUser in the Play Store
to manage root access of apps.
Simply flash it and enjoy.
--------------------------------
If you prefer Magisk:
Prio to installing Magisk you will have to change the data partition from F2FS to EXT4 because the Lenovo Kernel is missing an F2F2 feature.
How to format data to EXT4:
Make sure while the first time you boot TWRP.
You "KEEP SYSTEM in READ ONLY MODE" by clicking "Keep Read Only"
then Go to:
Wipe>Advanced Wipe>Select "Data">Repair or Change File System>Change File System>EXT4
Install Magisk
and once you booted up the system install Magisk manager.
Proof that Magisk works see attachment!
too much to read? Prefer a video? Head over to Youtube!
Video Tutorials on Youtube for Systemless Mode ROOT METHOD
How to ROOT LENOVO P2 | Install TWRP Recovery | Works on Marshmallow Only
How to ROOT Lenovo P2 with Android Nougat | Lenovo P2 Root Tutorial | Works on Nougat!
Thanks to TechXplicit
You don't like command lines? Prefer to click your way through life? Take a look at the Lenovo P2 Root Tool! Head over to Youtube![/SIZE]
Lenovo P2 Root Tool!
Thanks to Varun Sai
--------------------------------
Outdated Root Method for Marshmallow ONLY:
Here is for confirmed and working ROOT METHODS !!! Marshmallow ONLY !!!
(FOR SYSTEM MODE ROOT ONLY!)
download this pack https://goo.gl/KFtyzl
and extract its content into the adb&minimal fasboot folder
enter TWRP
do
Code:
adb push dot.supersu /data/.supersu
Select "ADB Sideload" in TWRP menu, (Advanced>ADB Sideload) make sure to select "Wipe Cache" and
Swipe to to Start Sideload and use following command to push SuperSu files.
Code:
adb sideload SuperSU.zip
Reboot into System. Done!
--------------------------------
FOR SYSTEMLESS MODE ROOT ONLY: (preferred method!) !!! Marshmallow ONLY !!!
As i stated in the Opening Thread. SuperSu can not be installed in Systemless-Mode by default because by default the /data partition is formated in F2FS.
More detailed explanation here: here
The current workaround is to disable the encryption (fully optional) and wipe the /data partition and format the /data partition to EXT4, which is also supported by the boot.img (thank you Lenovo!) and install SuperSu in Systemless-Mode. EXT4 formatting can be done through the "advanced wipe" of TWRP.
It has been tested and confirmed working. The main advantage is working OTA due to systemless SuperSu. As the OTA doesn't care if /data is actually F2FS or EXT4. Lenovo was so kind to provide both options in the stock boot.img.
Factory Images for P2a42 Marshmallow/Nougat & TWRP Test Image & Kernel Sources
Q: I messed up help me?! :crying:
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
(FACTORY IMAGES FOR Marshmallow ONLY!)
Warning! Following images are all confirmed working for the P2a42!
Do NOT attempt to use it on the P2c72 it will brick your device!
If you need an P2c72 factory flasher version! Let me know i will provide you with one!
Download the Factory State Images for Marshmallow. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock recovery. Simply run:
Code:
fastboot flash recovery recovery.img
You can also replace all partitions if required.
There is an flashall.bat file in the SW directory. Run it in case you want to restore all partitions.
But i highly recommend to replace just the partition you messed up. In most cases it will be boot,recovery or system.
One exception would be if you want to upgrade from an Old Firmware and you simply do not receive any OTA update files.
In that case you want to run a complete upgrade by running the flashall.bat file.
(FACTORY IMAGES FOR Nougat ONLY!)
Warning! Following images are all confirmed working for the P2a42!
Do NOT attempt to use it on the P2c72 it will brick your device!
If you need an P2c72 factory flasher version! Let me know i will provide you with one!
Download the Factory State Images for Nougat. Which are all flashable with fastboot: https://goo.gl/b7Dx37
too much to read? again?! do you ever read?
don't worry TechXplicit got you covered!
Head over to Youtube!
Lenovo P2 STOCK Firmware | Restore Bootlooped Lenovo P2 | How to get back to OTA updates
Thanks to TechXplicit
--------------------------------
Pre-Official TWRP Images:
TWRP 3.2.2-0 (latest version)
Currently no Pre-Official.
Q: Why Pre-Official?
A: It's is an "canary build" meaning, in test phase before it gets pushed Official but it is fully tested on Marshmallow and Nougat. Even confirmed working for the P2c72.
--------------------------------
Lenovo P2a42 Kernel Sources for Marshmallow/Nougat:
Official Lenovo Download Link
Great work,
Now only an seperate forum :laugh:
Shall i request it?
wimmetje said:
Great work,
Now only an seperate forum :laugh:
Shall i request it?
Click to expand...
Click to collapse
No need to I will request one once I upload all sources and pushed TWRP Official.
As a reminder! Always create a backup of the boot and system partition (as image!) before installing anything to stay save!
celoxocis said:
Small Update: DO NOT Flash the latest System-Mode SuperSU. It was reported to cause a bootloop on the Lenovo P2. Stick with Version 2.76!
As a reminder! Always create a backup of the boot and system partition (as image!) before installing anything to stay save!
Click to expand...
Click to collapse
I was to fast! I installed version 2.79. I reinstalled version 2.76, but it wont boot Any idea how I can fix it? Of course I'm an idiot who didn't make a back up.
BDM101 said:
I was to fast! I installed version 2.79. I reinstalled version 2.76, but it wont boot Any idea how I can fix it? Of course I'm an idiot who didn't make a back up.
Click to expand...
Click to collapse
Look for "Unsu" script here in the forum. It will take you out from the bootloop.
celoxocis said:
Look for "Unsu" script here in the forum. It will take you out from the bootloop.
Click to expand...
Click to collapse
Thx!!!! That worked
Updated Post #2 here https://forum.xda-developers.com/showpost.php?p=70435635&postcount=2
for confirmed and working Root Method!
Fantastic! Is possible to have a separate forum for the p2?
celoxocis said:
Updated Post #2 here https://forum.xda-developers.com/showpost.php?p=70435635&postcount=2
for confirmed and working Root Method!
Click to expand...
Click to collapse
If I want to sideload the zip file, I got the error "error: no devices/emulators found". But for everything else ADB works.
Dagnelino said:
Fantastic! Is possible to have a separate forum for the p2?
Click to expand...
Click to collapse
It will be requested by the topic starter when twrp will be officiall
BDM101 said:
If I want to sideload the zip file, I got the error "error: no devices/emulators found". But for everything else ADB works.
Click to expand...
Click to collapse
It think you need the latest adb version for it to work. Closed Beta Testers confirmed adb sideload as working.
celoxocis said:
It think you need the latest adb version for it to work. Closed Beta Testers confirmed adb sideload as working.
Click to expand...
Click to collapse
I tried the default adb version in Fedora 25 and the latest one from https://forum.xda-developers.com/showthread.php?t=2317790 in a vm, but non of them work.
I guess I'm gonna be root-less for a while
BDM101 said:
I tried the default adb version in Fedora 25 and the latest one from https://forum.xda-developers.com/showthread.php?t=2317790 in a vm, but non of them work.
I guess I'm gonna be root-less for a while
Click to expand...
Click to collapse
I don't know about the Linux based adb. Testers used Windows as hosts.
celoxocis said:
I don't know about the Linux based adb. Testers used Windows as hosts.
Click to expand...
Click to collapse
I also tried it on windows (a windows 10 virtual machine) with "Minimal ADB and Fastboot" version 1.4.2 and still wont work.
BDM101 said:
I also tried it on windows (a windows 10 virtual machine) with "Minimal ADB and Fastboot" version 1.4.2 and still wont work.
Click to expand...
Click to collapse
I don't think it works on a virtual machine because of the USB passthrough. I know that ADB sideload works as it was confirmed by the Testers.
Instead of using sideload. Try by placing the SuperSu.zip onto the internal storage /data. And select the zip for install.
celoxocis said:
I don't think it works on a virtual machine because of the USB passthrough. I know that ADB sideload works as it was confirmed by the Testers.
Instead of using sideload. Try by placing the SuperSu.zip onto the internal storage /data. And select the zip for install.
Click to expand...
Click to collapse
Still in a bootloop. Maybe the "UnSu" script isn't deleting everything? (it boots when I run the script)
BDM101 said:
Still in a bootloop. Maybe the "UnSu" script is't deleting everything? (it boots when I run the script)
Click to expand...
Click to collapse
It depends on how often you tried to install SuperSU. It will revert all changes when you run SuperSu once. If you tried it more than once then the backup folder will overwrite the data with already patched data.
Grab the stock images packages from post #3 and extract it's content.
No need to restore all the partitions.
Just open up the *.Bat file and look for the command that says "fastboot flash boot boot.img" and the parts that say "fastboot flash system systemchunk*" and run those in fastboot shell.
You will be back to stock without losing any of your data.
Then try again with the confirmed method in post #2. Just make sure you create a backup of boot and system (as image!) In case you need to restore. Let's say for applying an OTA.
Related
{
"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"
}
Hello guys,
This is my first guide and it is focused on people who just bought their Redmi Note 3 (KENZO/KATE) and having problems with officially unlocking their bootloader. (stuck @ 50% like me)
If you don't want to wait on stock MiUi until you can officially unlock your bootloader (because you need to wait additional ~2 weeks after you received permission from Xiaomi until their servers updated) or you want that extra security layer with locked bootloader this guide is made for you!
Since official LineageOS 14.1 just released, i thought some of you guys are interested in this awesome, easy and safe method.
To save you time searching hours and hours through this forum i made this quick summery.
Downloads :
MiUi 8 Global Developer ROM 6.11.3: KENZO or KATE
ZCX TWRP (direct downloadlink: click here)
Mi Flash 6.8.30
Latest firmware (choose correct device)
[ROM][OFFICIAL][7.1.1][kenzo] LineageOS 14.1 by The_strix
Open GApps - ARM64 - Android 7.1
Instructions : (follow them carefully!)
Extract MiUi 8 Global Developer ROM and replace recovery.img (in images folder) with ZCX TWRP's recovery.img
Flash using Mi Flash (in EDL mode) and check clean_all
After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP (change TWRP language from chinese to english: click here)
Reboot to system (if you get prompt: "Disable stock recovery replace now" > just swipe to allow disable)
Boot to MIUI and complete initial setup (important step - don't skip! first boot will take around 10 minutes)
-----------------------------------------------
Shutdown device and boot to TWRP again
(optinal) Backup every partition and safe this backup on an external device
Wipe > Advanced Wipe > check Dalvik / ART Cache, System, Data, Internal Storage, Cache > Swipe to Wipe
Flash Latest firmware, LineageOS 14.1 and GApps (ARM64, Android 7.1)
Reboot to system and you're DONE!!
updated method (works with newest MIUI version) :
There is a new updated method by kuan improved by @N.G. and @razr_96. Thanks for mentioning.
Advantages:
no need to download full MIUI fastboot rom
much faster method, only takes seconds to flash (instead of 4 minutes and you don't have to complete initial MIUI setup which also takes around 5 minutes)
this method is better if you want to stay on MIUI and just want to root
you can stay on your current MIUI version (even 7.1.19 which is currently the latest) and don't have to wipe your data
Disadvantages:
this doesn't clean everything, i would recommend to clean everything if you want to install a custom rom
you have to download a file i can not verify
Instructions : (follow them carefully!)
(optinal) Backup your current MIUI data (Settings > Additional settings > Backup & reset > Local backups > Back up) and copy it to an external media
Download and extract: Kenzo or Kate
(optinal) Replace included ZCX TWRP recovery.img (in images folder) with your preferred TWRP recovery.img
Flash using Mi Flash 20160401 (in EDL mode) and check flash all except data and storage (not clean_all like in the method mentioned above)
BE AWARE: This MiFlash version is different to the MiFlash version mentioned above! This version does only support 64 bit systems and you need atleast Windows 7!
After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP (change TWRP language from chinese to english: click here)
Reboot to system
Video tutorial: https://www.youtube.com/watch?v=rCONN1_IPuU
Troubleshooting :
[APP][ROOT][7.1.1]QuickSettings Flashlight fix for all nougat roms
If something goes wrong, start over again and follow my guide step by step.
This guide only works with MiUi 8 Global Developer ROM 6.11.3 or lower.
Put MIUI 8 Global Developer ROM in "C:\ROM" - MiFlash tends to have problems if there are any spaces in folder names.
If you flashed something wrong and have no simcard signal anymore or no IMEI look here for help: EFS Recovery Guide
If you didn't remove your passcode before you did a backuprestore using TWRP:
TWRP > Advanced > Filemanager > /data/system > delete locksettings.db
Issues with locked bootloader :
none
(advanced technique) Higher security with locked bootloader:
Thanks @LeoYL !
A little addition: If you want a even higher level of security, which is nobody except you can flash packages in recovery, you can create a recovery with limited functions and forced signature verification, with your own keys embedded in that recovery.
This is just like the original status of nearly all Android devices when they are shipped: only signed OTA update packages can be applied via recovery. Normally, the packages are signed by OEMs; however, you can become the "OEM" by creating your own private key, which is used during package signing.
Just follow these guides to create a recovery with your own keys. I use CM 13.0 recovery, since it only has basic recovery features, including installing a ZIP file, factory reset, and it has mandatory ZIP signature verification.
http://mjg59.dreamwidth.org/31765.html
https://forum.xda-developers.com/showpost.php?p=62796459&postcount=2
The reason why I don't use TWRP is that it allows update packages with any signature. Although you can enforce signature verification, it can also be switched off in TWRP settings.
Now you get a recovery which only accepts ZIP packages that are signed with your own private key. The only downside is you need to sign every package you want to flash each time. But this also means that if a stranger picks your lost phone up, they can't tamper your phone's OS. If the "reset protection" feature works with locked bootloader on our Redmi Note 3, the only distance between our phones' security and Google devices' is edl mode and encryption.
Wanna try other custom roms?
Just follow this guide and you can flash every other nougat customrom as well like:
[ROM]AOSIP 5.5 for Redmi Note 3(Kenzo)[OFFICIAL BUILDS]
[ROM][Nightlies][android-7.1.1_r6]ResurrectionRemix 5.8.0[OFFICIAL][VoLTE]
[ROM][OFFICIAL][Weekly][7.1.1_R13][Slim 7 For Kenzo]
[ROM] ► [7.1.1 ► N4F26M] ► [OTA][OMS][Goodix] ► Nitrogen OS
credits :
@The_strix: For his development work
@Psy_man: For extracting nougat firmware
@kuan: For creating this method (french forum)
@Tobsucht TM: For answering my questions
If this guide was helpful to you, don't forget to press the Thanks! button :good:
Enjoy your new custom rom!
khajiit
This method also works with Kenzo, obviously using the Kenzo miui rom and firmware instead.
razr96 said:
This method also works with Kenzo, obviously using the Kenzo miui rom instead as well as not flashing the kate firmware.
Click to expand...
Click to collapse
That's right! Thanks for pointing it out.
Redmi Note 3 SE _ Kate
Thanks bro worked on my Kate :good:
How to successfully unlock bootloader(official way) worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
Just use that Miflash : rootjunkysdl.com/files/Redmi%20Note%203%20Pro%20Kenzo/Firmware%20Unbrick/MiFlash.zip
Because that one in thread not working properly.
armo1111 said:
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
Just use that Miflash : rootjunkysdl.com/files/Redmi%20Note%203%20Pro%20Kenzo/Firmware%20Unbrick/MiFlash.zip
Because that one in thread not working properly.
Click to expand...
Click to collapse
The guide you linked is not working for me, thats why i made this guide which works 100%.
I tried this with the Global developer ROM for my kenzo.
When I try to get into TWRP, the Mi logo flashes but nothing else happens.
When I let the MIUI ROM start up and try to get into the recovery again,
it only shows me to connect my device to the Mi PC Manager.
What am I doing wrong?
blitzpeace said:
I tried this with the Global developer ROM for my kenzo.
When I try to get into TWRP, the Mi logo flashes but nothing else happens.
When I let the MIUI ROM start up and try to get into the recovery again,
it only shows me to connect my device to the Mi PC Manager.
What am I doing wrong?
Click to expand...
Click to collapse
Did you follow my instructions correctly?
- replaced recovery.img with ZCX TWRP recovery.img - check?
- EDL mode - check?
- remove usb cable after flash and press volume up+power button until mi logo shows up and then release buttons - check?
- are you sure you have kenzo version? did you download rom for kenzo? - check?
!! caution: the rom linked in this guide is only for kate version!!
thank you ! I've been trying the official route for 6 weeks, getting absolutely nowhere (even though I finally do have unlock permission).
this method worked like a charm, finally I'm off MIUI and running LineageOS
khajiit said:
Did you follow my instructions correctly?
- replaced recovery.img with ZCX TWRP recovery.img - check?
- EDL mode - check?
- remove usb cable after flash and press volume up+power button until mi logo shows up and then release buttons - check?
- are you sure you have kenzo version? did you download rom for kenzo? - check?
!! caution: the rom linked in this guide is only for kate version!!
Click to expand...
Click to collapse
1. I guess, do I have to replace only the recovery.img or more? If only recovery.img, then yes!
2. Yes, otherwise MiFlash would give me an error instead of flashing the ROM
3. Yes, but it appears only for an blink of an eye and then disappears again, the phone screen then stays dark
4. Yes, the newest one. Maybe that's the problem?
blitzpeace said:
4. Yes, the newest one. Maybe that's the problem?
Click to expand...
Click to collapse
Yes, that's the problem! This method only works until version 6.11.3.
You have to flash 6.11.3 (or earlier) to get TWRP and then you can flash what you want.
Good luck!
Excellent :good:
To boot into EDL
If you are lost with chinese language in TWRP, look at the first screenshot
And for Gapps take 64bits
Hi, I just got this ROM but when I plug the device in my computer it keeps connecting/disconnecting rapidly. Did I do something wrong?
Very helpful, but i would like to suggest people to use miunlocktool from windows 7-32 bit operating system. Miunlocktool perfectly works in windows 7 & don't stuck at 50%. Before unlock process, just "add oem unlocking device" from MIUI developer setting then start unlocking process..... Its really works for me & also others who followed these steps.
Skex506 said:
Hi, I just got this ROM but when I plug the device in my computer it keeps connecting/disconnecting rapidly. Did I do something wrong?
Click to expand...
Click to collapse
Yes, you did something wrong
Are you sure you have a "KATE" device not "KENZO"?
Follow my guide carefully and try again. It works 100%!
Rifatspir said:
Very helpful, but i would like to suggest people to use miunlocktool from windows 7-32 bit operating system. Miunlocktool perfectly works in windows 7 & don't stuck at 50%. Before unlock process, just "add oem unlocking device" from MIUI developer setting then start unlocking process..... Its really works for me & also others who followed these steps.
Click to expand...
Click to collapse
You don't think i've/we've tried everything? Official unlock works for you? Great! But it doesn't work for everyone... trust me.
Can we please stop to suggest to unlock officially with different guides? This guide is for people who don't want to or can't unlock officially.
khajiit said:
You don't think i've/we've tried everything? Official unlock works for you? Great! But it doesn't work for everyone... trust me.
Can we please stop to suggest to unlock officially with different guides? This guide is for people who don't want to or can't unlock officially.
Click to expand...
Click to collapse
I also said that million times to other people who suggest me different types of official method. When i success after trying couple of methods then i realized it is possible to unlock kate. I'm not saying that your post is not helpful, i saw many post like that, mostly in whirlpool forum. BTW, good luck with your tips :good:
Sure it is possible to unlock Kate officially but you have to wait for Xiaomi to get permission and wait for their servers to syncronize.
You have to wait up to 1 month (depending on your location and other things) until their servers confirms that you have permission to unlock (unable to verify thing). All these guides outside are working but it's a matter of time until they start working. That's why they didn't work for you in first place. :good:
hi @khajiit
They say not enough storage when I want to flash it. Could you please help me with this?
Spoiler: not enough
actuallyaka said:
hi @khajiit
They say not enough storage when I want to flash it. Could you please help me with this?
Click to expand...
Click to collapse
You are using a really old MiFlash version, try updating to the version mentioned in this guide.
And rename your folder "Redmi note 3 pro" to "Redmi.note.3.pro" or "Redmi_note_3_pro".
MiFlash tends to have problem with spaces.
khajiit said:
You are using a really old MiFlash version, try updating to the version mentioned in this guide.
And rename your folder "Redmi note 3 pro" to "Redmi.note.3.pro" or "Redmi_note_3_pro".
MiFlash tends to have problem with spaces.
Click to expand...
Click to collapse
Thank you khajiit..
it works know with using 2016 version..
Unofficial release -TWRP recovery for the Galaxy J3 Emerge - SM-J327P, Qualcomm MSM8937
{
"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"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 15/3/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.0-1_j327p_14317
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @Doctur, @infixremix, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
Reserved
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Doctur said:
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Click to expand...
Click to collapse
Thanks for the heads up with the other member and your support. I'll report it.
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
JUSMEJOSE said:
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
Click to expand...
Click to collapse
No sorry i don't own this device.
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
View attachment 4081849
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Sent from my Nexus 5X using XDA-Developers Legacy app
rekids said:
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Click to expand...
Click to collapse
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Thank you so much ?, will let you know how it goes.
Sent from my Nexus 5X using XDA-Developers Legacy app
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
joeyjojojjjjjj said:
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
Click to expand...
Click to collapse
Pin request? Never heard of that before. Have you set a pin/password on your device?
Nevermind, my daughter pit an unlock pin on it. Got it now going to try this.
Everything went smooth! Thank you so much!
rekids said:
Everything went smooth! Thank you so much!
Click to expand...
Click to collapse
Thanks for the click, out of 141 downloaders only 3 were clickers.
I find it amsusing that the author of the thread below using stolen files from this one has just as many clicks.
https://forum.xda-developers.com/an...-j3-emerge-t3573551/post71443474#post71443474
.
No problems at all... Everything went perfect!
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Cyclic said:
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Click to expand...
Click to collapse
Yes I'd advise disabling Knox.
need help!!!!
ashyx said:
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Click to expand...
Click to collapse
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
pumkinhead13 said:
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
Click to expand...
Click to collapse
There's no way the patch did that. You must have wiped the system partition in twrp.
https://www.androidfilehost.com/?fid=817550096634755921
ashyx said:
There's no way the patch did that. You must have wiped the system partition in twrp.
Click to expand...
Click to collapse
uuuh no, so I did all the above said to do and everything was fine, it booted up (before i flashed the patch) then I went back into recovery, flashed the patch and selected "boot to system" it booted to samsung logo then at the top in small yellow writing just said "kernal" it sat there for 15 mins, before i pulled the battery, then flashed again....this time upon finish it stated "NO OS"
Unofficial release -TWRP recovery for the Galaxy J3 2017 - SM-J330F/FN/FZ/G/DS EXYNOS 7570
{
"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"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance
UPDATE 10/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status: Beta
Update 15/9/2018
TWRP 3.2.3-1 OO build released.
Current status: Stable
Update 27/1/2018
TWRP 3.2.1-1NN build released
Current status: Stable
Update 23/11/2017
TWRP 3.1.1-1 NN build released.
Current status: Stable
Features:
TOUCHSCREEN working
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.[/B]
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1)
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1, THE DEVICE WILL AUTO BOOT TO RECOVERY)
5. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
DOWNLOAD:
twrp_3.3.1-1_sm-j330x_13819
twrp_3.2.3-1_j330_13918
twrp_3.2.1-1_sm-j330f_270117
twrp_3.1.1-1_sm-j330f_231117
Nougat Root instructions:
Install latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, disable dmverity and mount internal storage:
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install the boot image patch.
Boot image patch
no-verity-no-encrypt_ashyx
5. Install Magisk(if root is required)
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Reboot
OREO ONLY ROOT INSTRUCTIONS:
1. Install the Root patch kernel with TWRP.
J330F-FN_root_no_sim_patch
NOTE:This is a custom Oreo J330F/FN XXU3BRG3 permissive/enforcing kernel and patch built from source. It makes changes to the system partition also.
What does it do?:
*It installs a custom kernel to fix the no SIM issue when rooting.
*Patches the system to fix WIFI and Bluetooth not turning on when using custom kernels.
*Patches DM-Verity.
*Removes forced encryption and patches /data not able to be mounted (after formatting).
*Removes the SecurityLogAgent nag when using a custom kernel.
2. If you wish to mount /DATA for access to internal storage then FORMAT the /DATA partition.
3. To root install the latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
PIE ONLY ROOT INSTRUCTIONS:
To root install latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable encryption (mount DATA in TWRP) install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
Finally FORMAT /DATA in TWRP.
Reboot.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @lemlis, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
UPDATE: Touchscreen fixed
.
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
Click to expand...
Click to collapse
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Click to expand...
Click to collapse
Probably the version of SuperSu you flashed.
ashyx said:
twrp_3.1.1-1_sm-j330f_231117
Click to expand...
Click to collapse
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
lemlis said:
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
View attachment 4340464View attachment 4340476
Click to expand...
Click to collapse
Seems I didn't include my updated FSTAB in the new build. Corrected, thanks for pointing it out.
ashyx said:
Probably the version of SuperSu you flashed.
Click to expand...
Click to collapse
Yeaa you right..i use super su which remain in my memory card almost 2 years ago ???
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
BlackDragonz said:
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
Click to expand...
Click to collapse
updato.com
i cant flash super su twrp didn't show the file to flash
File to flash have to be on sd card ?
Help Me
azhar960225 said:
Help Me
Click to expand...
Click to collapse
Police. Fire or ambulance?
I Want root j3 pro 2017..but how
azhar960225 said:
I Want root j3 pro 2017..but how
Click to expand...
Click to collapse
Flash SuperSU or Magisk.
How? To Flash How? Cannot root j3 How to Flash?
7.11 Android...
arabarabow said:
twrp didn't show the file to flash
Click to expand...
Click to collapse
put zip file inside any folder.File to flash have to be in folder
Just done flashing latest build and flashed magisk, all are running fine. Tysm @ashyx !
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
arabarabow said:
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
Click to expand...
Click to collapse
Boot to TWRP and flash Supersu or Magisk. Use the three button combo.
Can i just use cf auto root to root my phone without installing a recovery? Or it's better to root using this method?
Since Official TWRP as of 2019-06-19 still does not support decryption of PIE /data partition, I decided, on behalf of developer of Unofficial TWRP 4pda version MOD EDIT: LINK REMOVED d4e8ede8f1f2 and with his approval, to present his project here.
The version being presented is a branch of Team's Win Recovery Project 3.x, based on Android One Pie kernel, and is licensed under the GPL (version 2) license agreement.
Neither developer nor OP creator (translator from Russian) are responsible for any harm to electronic devices or financial losses inflicted with improper usage of this software.
Proceed on your own risk.
Please get acquainted with Team Win Recovery terms and usage.
Sources:
OMNI TWRP repository..
TWRP Device configuration for Xiaomi Mi A2.
Developer forum (4pda, in Russian):
MOD EDIT: LINK REMOVED
Downloads (Google Drive):
TWRP 3.3.1-5 jasmine_sprout unofficial (2019-06-29)
Note 1: TWRP Image cannot be uploaded to local repository as a single archive due to xda limitations on file size, thus dev's Google Disk is used;
Note 2: This thread is somehow not thanked and thus is periodically drowning below other less-functional TWRP clones; do not hesitate to promote the product after successful usage, - it is for free.
Features :
1. Pie-based kernel with full decryption support for stock Androids 9 and 10:
- in case Mi A2 is not locked by PIN, password or graphic key, decryption and mounting of /data partition is made automatically,
- otherwise appropriate unlocking sequence is to be made by user in TWRP loaded into phone.
2. Slot (A/B) switching works.
3. MTP / ADB sideload and USB OTG read/write work.
4. All variants of MiA2 screen panels are correctly supported (no "black screen" bug).
5. In current version /system partition is mounted as "/system" (not as "/system_root") to comply with script of OpenGApps installer.
Usage Notes:
- Mi A2 must be fully unlocked to use TWRP; "Usb-debugging" must be switched on in phone; see Guides in this forum;
- ADB / fastboot must be properly installed and approved in phone; (see Platform tools, - r29.0.1 as of 2019-06-08, - and Guides in this forum);
- recommended booting sequence
Code:
adb devices -l
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.3.x-x-jasmine_sprout-unofficial.img
1st command lists attached devices supporting ADB interface, and is used to check that phone is connected properly and that no other devices are connected. simultaneously, - read result in CMD. Most of ADB commands need "USB debugging" in ON state. If issued for the 1st time from this PC, will rise a prompt on phone, - need to approve.
2nd command reboots phone into bootloader, - wait till phone shows fastboot screen.
3rd command lists attached devices supporting fastboot interface., - read result in CMD and ensure it shows same signature as was displayed after 1st command in ADB.
4th command boots TWRP into phone.
Example 1 (pull camera photos directory):
1. boot into TWRP (do not forget to unlock TWRP and thus decrypt /data if phone is secured by PID or other method);
2. type "adb pull -a /sdcard/DCIM/" in CMD shell in platform-tools dir of PC - to save all photos to current dir.
Example 2 (pull current /boot image to PC ):
1. Boot into TWRP;
2. To learn which slot is active, see "Reboot" page in TWRP
(another way is to switch phone to bootloader mode and type "fastboot getvar current-slot" in CMD in platform-tools folder in PC).
3. in CMD shell in platform-tools dir of PC type:
- if active slot is A: "adb pull /dev/block/mmcblk0p62 ./boot_a.img";
- if active slot is B: "adb pull /dev/block/mmcblk0p63 ./boot_b.img";
Example 3 How to re-flash /persist partition using TWRP and ADB commands' script
How to install TWRP as permanent one:
As stock Mi A2 ROM comply to GSI A/B slots partitioning scheme, there is no /recovery partition, and thus no place for TWRP to be successfully flashed via fastboot (or MiFlash).
If you use "fastboot flash twrp-3.3.x-x-jasmine_sprout-unofficial.img" command, you will just substitute content of /boot_X partition with TWRP in current slot X, thus spoiling ROM, which is obviously not what you've intended.
If you want to embed TWRP into phone permanently instead of stock recovery:
- boot into TWRP, and then
- install "twrp-installer-3.3.1-5-jasmine_sprout-unofficial.zip" via booted TWRP;
- this installation will patch /boot image (similar to how MagiskManager patches /boot image to embed Magisk).
Custom ROMs usually have a custom recovery (mostly various TWRP builds) embedded into boot image from scratch, you may opt to substitute such with this one.
Update 2019.06.24:
Code of PBRP by @Manish4586, has been updated today to sources of TWRP fixes by MOD EDIT: DOWNLOAD LINK REMOVED
Update 2019.09.12:
I beg everybody (and 1st of all d4e8ede8f1f2) pardon for postponing update of this thread, since improved version 3.3.1-5 was available as of 2019.06.29.
Changes in 3.3.1-5:
1. new kernel v. 4.4.184 based on official MiA2 Pie kernel;
2. Merging with official TWRP code changes:
2.1. Fix compilation in android-9.0 repos.
2.2. Properly localized string instead of using English.
2.3. ext4crypt: support synthetic keys v3 on May update
Notes from d4e8ede8f1f2 on decryption in 3.3.1-5:
This version supports decryption of data partition encrypted in FBE (File-Based Encryption, introduced since Android 7) scheme only, as being used by stock MiA2 ROMs.
This {limitation} became deficiency since some custom ROMs, e.g. AEX, implemented older and stiffer FDE (Full Disk Encryption, introduced in Android 5) scheme.
One can check which encryption scheme is implemented in current ROM, for example, issuing ADB command: "adb shell getprop ro.crypto.type". Replied "file" means FBE, while "block" means FDE.
hii!
im at 3.2.3.0 with RR pie atm, may i just use the installer.zip after flashing my rom?
then setting the other slot and reboot recovery to there, installing opengapps and magisk, yeah?
i mean, without flashing the .img
ty!
Gesendet von meinem MI A2 mit Tapatalk
worked perfect, ty!!!
Gesendet von meinem Mi A2 mit Tapatalk
Is it possible to use this version of TWRP to encrypt my phone? Currently, I am using havoc OS. If I try to encrypt from system settings in the normal way it does not work (simply reboots with no change).
I was thinking perhaps I could flash stock OS, encrypt phone from system settings, flash your custom TWRP and then use it to flash custom OS. Hopefully that would maintain encryption and I would not have to wipe system and data and unencrypt?
As far as I know. no custom ROMs support encryption yet. Although your question in "Havoc OS" thread was not answered, you could use search in this thread, which would show you latest answer from OP on this issue: https://forum.xda-developers.com/showpost.php?p=79826439&postcount=1347
Bonjour,
On wich partition do I install Recovery ?
I just want to flash PBR and magisk root on stock rom.
With stock ROM you cannot {flawlessly} flash TWRP, just boot into it via fastboot and make backups, pull system images (for example, pull current stock boot image to PC for patching it in Magisk in phone and thus getting root), etc., etc.
To install Magisk and get permanent root on stock you do not need TWRP at all, if you can fetch stock boot image downloading it from here or taking from stock ROM fastboot-image. Please carefully read Guides here on how to get root,
As for custom ROMs, these usually already have a TWRP in their boot images, but anyway go to the thread dedicated to selected custom ROM and carefully read OP instructions.
See IMPORTANT NOTICE added to OP
Aerobatic said:
With stock ROM you cannot {flawlessly} install TWRP, just boot into it via fastboot and make backups, pull system images (for example, pull current stock boot image to BB for patching it in Magisk in phone and thus getting root), etc., etc.
To install Magisk and get permanent root on stock you do not need TWRP at all, if you can fetch stock boot image downloading it from here or taking from stock ROM fastboot-image. Please carefully read Guides here on how to get root,
As for custom ROMs, these usually already have a TWRP in their boot images, but anyway go to the thread dedicated to selected custom ROM and carefully read OP instructions.
Click to expand...
Click to collapse
Merci beaucoup for your answer.
If I have good understood ,Ishould not install custom recovery but I Can install magisk via adb sideload ?
I try Havoc rom but I had a lot of bugs ...
bancelin said:
... Can install magisk via adb sideload ?I try Havoc rom but I had a lot of bugs ...
Click to expand...
Click to collapse
I've already written to you that TWRP is not needed to get root, and recommended to read Guides, Why should I (or anybody else) type here content of already published Guides?
Read this: https://forum.xda-developers.com/mi-a2/how-to/unlock-bootloader-n-root-magisk-easy-t3856800
Find (please be informed "Search this forum" in the upper right corner of the window really works in XDA) stock and/or patched boot image for the version of stock ROM you want to root. Images for 10.0.13.0 are here: https://forum.xda-developers.com/showpost.php?p=80065352&postcount=7, stock boot image for patching with Magisk can also be taken (as I have already written) from corresponding stock fastboot image: https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849.
Nobody will do your homework for you.
Updated header with info on and links to twrp-3.3.1-5-jasmine_sprout-unofficial
Aerobatic said:
Update 2019.09.12:
[...]
1. new kernel v. 4.4.184 based on official MiA2 Pie kernel;
2. Merging with official TWRP code changes:
2.1. Fix compilation in android-9.0 repos.
2.2. Properly localise string instead of using English.
2.3. ext4crypt: support synthetic keys v3 on May update
Notes from d4e8ede8f1f2 on decryption in 3.3.1-5:This version supports decryption of data partition encrypted in FBE (File-Based Encryption, introduced since Android 7) scheme only, as being used by stock MiA2 ROMs.
This {limitation} became deficiency since some custom ROMs, e.g. AEX, implemented older and stiffer FDE (Full Disk Encryption, introduced in Android 5) scheme.
One can check which encryption scheme is implemented in current ROM, for example, issuing ADB command: "adb shell getprop ro.crypto.type". Replied "file" means FBE, while "block" means FDE.
Click to expand...
Click to collapse
I am running AEX (v6.7) and my encryption scheme is "FDE". So I needed to run v4?
But neither v4 nor v5 works with this ROM.
MMN said:
.... So I needed to run v4?...(
Click to expand...
Click to collapse
No, v5 is better than v4, except it still does not support legacy FBE encryption.
I meant that the developer of This TWRP just wrote comments on legacy FBE encryption while releasing 3.3.1-5, probably being asked by someone about this issue. As he have not released newer version in 4 months, probably nobody else asked him to. His 4pda-mail is in the 1st paragraph of OP, so you can try to ask him to help.
Aerobatic said:
No, v5 is better than v4, except it still does not support legacy FBE encryption.
I meant that the developer of This TWRP just wrote comments on legacy FBE encryption while releasing 3.3.1-5, probably being asked by someone about this issue. As he have not released newer version in 4 months, probably nobody else asked him to. His 4pda-mail is in the 1st paragraph of OP, so you can try to ask him to help.
Click to expand...
Click to collapse
Thanks for the answer!
But maybe a demand is not necessary. Which ROM do you use? Stock or Custom?
Maybe my installation steps are wrong:
I currently installed AEX (Pie) with official TWRP installer (zip). After slot change, I installed GApps and Magisk.
If I encrypt my system (settings - security - encryption), then I can not access /data with official TWRP (because it can not decrypted).
If I flash your v4/v5-TWRP via "fastboot flash boot trwp-v4|v5.img" a decryption does not work also.
If my doing is correct, I will contact the developer at pda.
MMN said:
...Which ROM do you use? Stock or Custom? ... If my doing is correct, I will contact the developer at pda.
Click to expand...
Click to collapse
I'm on rooted stock.
Yes, you can ask d4e8ede8f1f2. But IMHO, as it is obviously the problem of AEX (I mean, - using legacy encryption, - as usual problem of most of other custom ROMs is - not using any encryption at all), - you'd better search for solution in AEX-dedicated theads.
Aerobatic said:
Since Official TWRP as of 2019-06-19 still does not support decryption of PIE /data partition, I decided, on behalf of developer of Unofficcial TWRP 4pda version d4e8ede8f1f2 and with his approval, to present his project here.
Click to expand...
Click to collapse
Hello Aerobatic, I'm interested to find a way to backup my personal data, personal apps and their settings, etc. not so interested in Android and it's setting as much, then later be able to restore the backup onto the phone after a fresh install. Would I be able to use this version of TWRP to do that on Android Pie (Android One) for my Mi A2?
I've not found a solution yet to do this and it gets rather tedious to have to enter all the apps, settings, etc. from scratch each time.
nadia p. said:
Hello Aerobatic, I'm interested to find a way to backup my personal data, personal apps and their settings, etc. not so interested in Android and it's setting as much, then later be able to restore the backup onto the phone after a fresh install. Would I be able to use this version of TWRP to do that on Android Pie (Android One) for my Mi A2?
Click to expand...
Click to collapse
Have you tried to backup /data to attached USB-OTG "drive"?
Aerobatic said:
Have you tried to backup /data to attached USB-OTG "drive"?
Click to expand...
Click to collapse
I never knew what a "USB-OTG" drive was until I looked it up. In the past I had a USB-micro to USB-B cable that I used on my previous Google/Nexus phone but I don't own one of these cables (USB-C to USB-B) to connect to Mi A2.
I was trying to see if there was a way to do this over wi-fi or bluetooth directly to a computer. Or somehow through ADB push/pull commands. But I've not found a good solution yet. I've just transferring the data manually from the phone to the computer for now. I'll look into purchasing one of the cables and trying to backup that way using your version of TWRP.
nadia p. said:
..I was trying to see if there was a way to do this over wi-fi or bluetooth directly to a computer. Or somehow through ADB push/pull commands...
Click to expand...
Click to collapse
After booting into TWRP you can try to "ADB root" and then pull. Or use 3rd part apps like MyPhoneExplorer.
Worked like a charm!
onimorza said:
Worked like a charm!
Click to expand...
Click to collapse
He-he, and still showing zero rating for the thread, and it will sink again below partially operative clones.... Do I need to attach something to OP?
Hello All
Its a never used LEX 727. Decided to flash a custom rom. Installed latest TWRP, but when i go to flash the rom got error 7.
Tried with diffrent roms but still error 7.
Then updated firmware to 30S by @codeworkx from here and again tried different roms but am still getting the error.
Following the suggestions given by various posters, I have tried doing full wipes, rebooting to recovery, using the ALL IN ONE tool but nothing is working.
I've also tried many older versions of TWRP as well as roms but nothing, the error is still there.
Any more suggestions on how to fix this? Thank you.
This is a typical error when TWRP is old or does not fit the model.
First, stay at 20s firmware:
Downloads for : LeEco Le Pro3 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
You have to keep an eye on this:
- LEX720 (ZL1_CN)
- LEX722 (ZL0_CN)
- LEX727 (ZL1_NA)
Error 7 says the ROM’s updater script says the phone model of your phone is incompatible. A quick search for LineageOS give me this compatible on:
[ROM][OFFICIAL][TREBLE][X72X][11.0.X] LineageOS 18.1 for LeEco Le Pro3
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from...
forum.xda-developers.com
Make sure you have the latest TWRP installed for the X727:
Download TWRP for zl1
Download TWRP Open Recovery for zl1
eu.dl.twrp.me
Importand: If LineageOS aks to install it's own recovery, don't do it.
Important:
Install recovery, then reboot directly into recovery and install the rom. Original Firmware will revert back to stock recovery while boot! The you have to start over again.
Hello @Neppomuk_
Thanks.
1- I installed the 20S firmware
2- Installed the latest TWRP version 3.6.2_9-0-zl1 , and, rebooted to recovery.
3- Downloaded both the latest official LOS as well as the unofficial one by the poster whose link you have posted above. First tried installing the official rom and it gave error 1. Then tried flashing the unofficial one and same error. i.e.: "E1001: failed to update system image", Error 1.
4- I also tried installing the Mokee rom and it is also giving the same error. I downloaded the rom from their official site here
4- I am attaching screenshots of the errors. The first one is from the lineage "unoffical" after the "offical" had failed to install. The second one is from the failed Mokee rom.
{
"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"
}
Hopefully this is progress.
Error 1 is corrupted boot. You have the flash the stock boot.img with bootloader. I own a x720 so I can not provide you my one. It is possible to extract it from stock rom.
Check if you can find one here:
Le Eco Pro 3 X727 Twrp Backup : Clean Full Stock X727 recovery EUI 5.8.21s
Return to Un-modded Stock: Bootloader unlocked and TWRP and Root included The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download. Be Advised Do your research before flashing...
forum.xda-developers.com
Neppomuk_ said:
Hopefully this is progress.
Error 1 is corrupted boot. You have the flash the stock boot.img with bootloader. I own a x720 so I can not provide you my one. It is possible to extract it from stock rom.
Check if you can find one here:
Click to expand...
Click to collapse
Actually i have had that error before while experimenting, so i'm afraid there has been no progress.
Are you asking to flash the stock boot image? And then what? Will appreciate if you outline the steps.
@Neppomuk_
1- Extracted stock boot image from the file you provided. Flashed it to boot successfully. Rebooted to recovery.
2- Went through the process of flashing the rom again. Still error 1.
OK, the E1001 from your screenshots is interesting. System image is (marked as) encrypted.
Do Following from twrp, all steps without reboot:
wipe/advanced wipe, tick 'Dalvilk/Art', 'Cache', 'Data' and 'System'
then go wipe/format data, confirm with yes, now the encryptiono (state) should be gone.
Now reboot straight back into recovery and flash the, this was mokee rom?, again.
Neppomuk_ said:
OK, the E1001 from your screenshots is interesting. System image is (marked as) encrypted.
Do Following from twrp, all steps without reboot:
wipe/advanced wipe, tick 'Dalvilk/Art', 'Cache', 'Data' and 'System'
then go wipe/format data, confirm with yes, now the encryptiono (state) should be gone.
Now reboot straight back into recovery and flash the, this was mokee rom?, again.
Click to expand...
Click to collapse
Did it. Still error 1.
The first picture is LOS. The second one is Mokee.
Let's try following:
In TWRP go to Advanced, select File Manager, select the System folder from the list and the push the checkmark on the bottom right corner. No push the chmod 755 button the give full access to system partition.
Try to install custom rom.
A second try:
Go to wipe / Advanced wipe
select the system partition
now select 'repair or change file system' and then 'repair file system'.
Try to install custom rom.
I had problems with the 2nd try on some devices they do not allow repair of system partition.
Did the 1st option. Still error 1.
Did the 2nd option and the process was aborted or failed with error 4.
Did the 1st option. Still error 1.
Did the 2nd option and the process was aborted or failed with error 4.
Did you had any problem to flash TWRP on the device earlier?
With error 4 we have a second option:
In TWRP go to Wipe / Advance Wipe, select 'System' partition and select 'Repair or Change File System'.
Select 'Change File System', select EXT2 and proceed.
Then do the same to go back to EXT4.
Do the same with the Data partition.
Now, you have to transfer the custom rom to your phone again. But do it in bootloader mode this time.
OK, something special:
The LineageOS ROM has it's own boot.img inside. You can use this one as well, flash it in bootloader.
Neppomuk_ said:
Did you had any problem to flash TWRP on the device earlier?
Click to expand...
Click to collapse
No.
Neppomuk_ said:
Now, you have to transfer the custom rom to your phone again. But do it in bootloader mode this time.
Click to expand...
Click to collapse
Not sure how to do this. As far as i know one can only flash images in boot loader mode. How does one flash a zip file in that mode?
Neppomuk_ said:
OK, something special:
The LineageOS ROM has it's own boot.img inside. You can use this one as well, flash it in bootloader.
Click to expand...
Click to collapse
Are you asking to flash the lineage boot.img in bootloader mode and then flash the entire rom by TWRP?
Do partial flash in bootloader mode, if not already happen, use Minimal ADB and Fastboot:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Command to flash boot image in console:
fastboot flash boot [boot.img]
Then stay in bootloader mode. The mobild should mount a drive to the system. Copy the ROM imge to the internal storage on that drive. You can copy the rom in TWRP mode also. Then install the rom throug TWRP.
I never sideloaded data. I like to check the transfer is successfully finished. I had some faulty sd cards, wich do no give an error while sideloading stuff.
As an alternative you can use an OTG USb Stick and putt the stuff on this one. Would do the same and could be faster.
If you need drivers for Windows:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
and the device specified one:
LeEco Le Pro3 USB Driver for Windows (Official Mobile Driver)
Download the official USB Driver for Windows Computer.
gsmusbdriver.com
-> I did not verify if this driver downloads are still valid, please check them first.
I do have the latest drivers and ADB installed. Everything i have been telling you has been done via ADB as well as from the internal storage of the phone.
But my question was, when you say :
Neppomuk_ said:
Now, you have to transfer the custom rom to your phone again. But do it in bootloader mode this time.
Click to expand...
Click to collapse
What are you exactly asking me to do? How can one flash a zip file using bootloader, assiming that's what you are saying?
And, when you are saying:
Neppomuk_ said:
The LineageOS ROM has it's own boot.img inside. You can use this one as well, flash it in bootloader.
Click to expand...
Click to collapse
Are you asking me to flash the boot.img using bootloader and then flash the rom from TWRP?
My question is i can flash the boot.img from TWRP, can't I? Anything wrong with that approach?
I think understand you now. Do a partial flash using boot loader and the do the rest using TWRP.
Thank you for clarifying. One needs confirmation so we do not do anything we aren't supposed to.
Sorry, I mixed up another case where I'm tring to remove forced data encryption.
There are flashable boot.img in zip files wich you can flash from TWRP, but this is not your one.
I still believe, that something is wrong with your boot partition.
The whole procedure:
- Extract boot.img from Lineagos and install it in bootloader mode: fastboot flash boot [boot.img]
- Boot into TWRP while holding Power and volume up.
- If not done, wipe cache and system, format data.
- Copy LineageOS to the drive / internal storage
- Use TWRP to install the rom
veda1 said:
I think understand you now. Do a partial flash using boot loader and the do the rest using TWRP.
Thank you for clarifying. One needs confirmation so we do not do anything we aren't supposed to.
Click to expand...
Click to collapse
Yes, better one question to much than new problems...
Did as suggested. Still error 1.
I have another question while we continue to look at this. If worse comes to worse i've no choice but to use EUI. Is it possible to patch the latest android security patches to it? That is, rom will be EUI , but updated with all security patches?