[2018-09-08][ROM][OFFICIAL][7.1.2]MIUI Fastboot Flashable Zip Project - Xiaomi Redmi 5A ROMs, Kernels, Recoveries, & Other

[2018-09-08][ROM][OFFICIAL][7.1.2]MIUI Fastboot Flashable Zip Project - Xiaomi Redmi 5A ROMs, Kernels, Recoveries, & Other

Flashable zip contents and it's usage
boot-signed.zip
This zip contains MIUI's stock bootloader image. Flashing this will restore your boot partition to stock.
cache-signed.zip
This zip contains MIUI's stock cache image. Flashing this will restore your cache partition to stock.
*Cache partition is normally used to store temporary TWRP/ Android OS files.
cust-signed.zip
This zip contains MIUI's stock vendor image. Flashing this will restore your vendor partition to stock.
*This is actually the vendor partition for Xiaomi phones. It stores your phone's proprietary drivers for your phone's hardware like display drivers, Open GL, sound drivers and more..
firmware-update-signed.zip [v2 and above only]**
This zip contains MIUI's stock adspso.bin, cmnlib64.mbn, cmnlib.mbn etc. images. Flashing this will restore the below mentioned image's partition to stock.
*Images contained in this flashable zip:
adspso.bin
cmnlib64.mbn
cmnlib.mbn
devcfg.mbn
emmc_appsboot.mbn
keymaster.mbn
lksecapp.mbn
mdtp.img
NON-HLOS.bin
rpm.mbn
sbl1.mbn
splash.img
tz.mbn
These images are originally distributed with MIUI's official recovery zip. I decided to include them here is because it is more easy to release for the project and it will save a lot of time preparing it for a release than manually converting each and every fastboot images to raw disk image format and then highly compressing it.
These images will be available in each and every release of MIUI's recovery zip. All of the images in this zip are required to be flashed when you upgrade/ downgrade a release or it may introduce bugs like Wi-Fi not working in your MIUI ROM.
mdtp-signed.zip [v1 only]*
This zip contains MIUI's stock mdtp image. Flashing this will restore your mdtp partition to stock.
*According to @mirfatif's thread, this partition contains files for "boot verification and Qualcomm SafeSwitch technology to lock and track theft phones".
misc-signed.zip
This zip contains MIUI's stock misc image. Flashing this will restore your misc partition to stock.
*From my understanding from several sources, this partition contains CID (Carrier and Region ID), USB configuration settings and several hardware settings related files.
persist-signed.zip
This zip contains MIUI's stock persist image. Flashing this will restore your persist partition to stock.
*This particular partition is what most users have problem from. It contains sensor driver files. (If you have problems like proximity sensor/ rotate screen not working, this is the zip you need to flash).
recovery-signed.zip
This zip contains MIUI's stock recovery image. Flashing this will restore your recovery partition to stock.
*THIS IS NOT TWRP! THIS IS MIUI'S STOCK RECOVERY! FLASHING THIS WILL REMOVE YOUR TWRP!
*Everyone using custom ROM should already/ must know this partition (Stop using custom ROM if you don't know what this partition is for! :silly:
splash-signed.zip [v1 only]*
This zip contains MIUI's stock splash image. Flashing this will restore your splash partition to stock.
*This partition contains an image file.. Yep, an image file.. But for what? Well, the screen you first see when you turn on your phone duh! (The MIUI logo) Not the bootanimation!
system-signed.zip
This zip contains MIUI's stock system image. Flashing this will restore your system partition to stock.
*Everyone should know this.. This is where the ROM's main files are located. Android OS's main partition like Android Nougat, Oreo, Pie etc.
userdata-signed.zip
This zip contains MIUI's stock data image. Flashing this will restore your data partition to stock.
*This is also a must know partition.. This is where most of your apps, images and games are stored. It is also where the OS's permanent cache a.k.a dalvik/ ART (Android Runtime) are stored.
*v1 only: It means that this flashable zip is only available in V9.5.10.0.NCKMIFA and it has been integrated into firmware-update-signed.zip in the next release and above.
**v2 and above only: It means that this flashable zip is only available in V9.6.2.0.NCKMIFD and above. It is not available in v1.

ANNOUNCEMENT
After about 3 years, I finally had the time to update this project. This project has been discontinued and download links will still be available but I'm not sure if those flashable zips still works. I no longer own a Xiaomi Redmi 5A and I'm unable to test if those flashable zips still works. Please use it at your own risk and I will occasionally be online to check on comments in this thread but I might not be able to assist you on your problem.
Thank you.
Spoiler: Previous Announcements
Once again, project has been updated to MIUI V9.6.4.0.NCKMIFD! Other than that, there are flaws in the previous release (again). I tested each and every one of the zip before releasing. These zips should work this time (hopefully).
I will halt this project as my Microsoft Azure Free Subscription has expired (30 days). I rely on cloud virtual machine to get these things done. I don't have a PC at home and it will be very hard to release project updates without a PC. Currently I use my phone (Xiaomi Redmi 5A) for all of the work (even when writing this post). Every single release that I've released are possible because of Microsoft Azure. I can't do things without it.
To make up for my mistakes, I've added two things to this release:
1. Brought back userdata-signed.zip (Actual files in it)
2. New zip signing method (Should now work with TWRP's "Zip Signature Verification" Yay!)
I spent a two days preparing this (From yesterday and at about 1 a.m. in the morning to 9 a.m.) with both tired and sleepy mode...
I will be flashing this zips to prove that it's working (Will provide screenshots also!)
Well, that's all for now.
Thank you all for understanding!

Wow you made it a whole package. Man you didn't have to put my name on the contributors, the credit goes all to you!

Nevermind, you should be in the contributor lists because the sparked idea came from you! You can also contribute to this project if you have any ideas! As they say, Ideas spark better with more people working together than people who work on their own!

Eemmmm...
What's the different with official recovery firmware from bigota miui?
It's the same stock firmware, right?

Azocke5531 said:
Eemmmm...
What's the different with official recovery firmware from bigota miui?
It's the same stock firmware, right?
Click to expand...
Click to collapse
Yes, you are right but.. Some of the disk images in official fastboot firmware are unavailable in official recovery firmware (Example: persist).. And some people may prefer to only download a single disk image. Some people also may have limited Internet quota and try to save every single MB if they can..
Another reason is that some disk image can't be written in MiFlash tool (Example: persist).. Some people will accidentally delete/ corrupt the partition and so far till now, I've found no article online about how to fix Xiaomi Redmi 5A persist partition/ sensors

can i ask something? this is for minimalize the storage used? or what?

fikriwirahman said:
can i ask something? this is for minimalize the storage used? or what?
Click to expand...
Click to collapse
It's the same as official firmware (unmodified & clean) but it is highly compressed to save Internet quota especially for those who have limited Internet quota
Example: normal recovery firmware zip = 1 GB+
This project zip = many choices (you can download it individually)
system.img = 0.9 GB (normal is 3GB if uncompressed)
userdata.img = 0.2 GB (normal is 2.9 GB if uncompressed)

Growtopia Jaw said:
Yes, you are right but.. Some of the disk images in official fastboot firmware are unavailable in official recovery firmware (Example: persist).. And some people may prefer to only download a single disk image. Some people also may have limited Internet quota and try to save every single MB if they can..
Another reason is that some disk image can't be written in MiFlash tool (Example: persist).. Some people will accidentally delete/ corrupt the partition and so far till now, I've found no article online about how to fix Xiaomi Redmi 5A persist partition/ sensors
Click to expand...
Click to collapse
Ok, now I understand
About standalone bootloader zip, is that contain a locked or unlocked bootloader?

Azocke5531 said:
Ok, now I understand
About standalone bootloader zip, is that contain a locked or unlocked bootloader?
Click to expand...
Click to collapse
This zip only contains boot image. Your question about "locked and unlocked bootloader" is totally unrelated to the boot image zip.
About locked/ unlocked bootloader, that is only changed (locked/ unlocked) in Mi Unlock Tool (which is the tool you used to unlock your phone in the first place). Only this tool, fastboot and manual terminal command input can change the unlock/ locked state.
Long story short, unlock/ lock bootloader is NOT the same with bootloader image (boot image). Boot image is just a partition. Unlock/ locked state is a state whether your phone's bootloader is unlocked or not.

Great work

Growtopia Jaw said:
This zip only contains boot image. Your question about "locked and unlocked bootloader" is totally unrelated to the boot image zip.
About locked/ unlocked bootloader, that is only changed (locked/ unlocked) in Mi Unlock Tool (which is the tool you used to unlock your phone in the first place). Only this tool, fastboot and manual terminal command input can change the unlock/ locked state.
Long story short, unlock/ lock bootloader is NOT the same with bootloader image (boot image). Boot image is just a partition. Unlock/ locked state is a state whether your phone's bootloader is unlocked or not.
Click to expand...
Click to collapse
A little correction:
boot partition is kernel partition, boot.img is kernel image file.
bootloaders:
PBL (primary bootloader), SBL(secondary bootloader)/XBL(extesible bootloader), aboot/appsboot (OEM bootloader), abootbak (OEM bootloader backup?)
Unlocking bootloader usually done to aboot and abootbak, abootbak partition may contains excactly the same image as aboot partition.
--------------------------------------------------------------------
Could someone with unlocked BL Redmi 5A dump the aboot and abootbak partitions, and share them here please?
They're main "ingredients" to unlock BL instantly without permission, only needs to enter EDL mode.
(Going to figure out if Redmi 5A's SBL/XBL will accept officially unlocked aboot from another Redmi 5A or if it needs more works).

r6680jc said:
A little correction:
boot partition is kernel partition, boot.img is kernel image file.
bootloaders:
PBL (primary bootloader), SBL(secondary bootloader)/XBL(extesible bootloader), aboot/appsboot (OEM bootloader), abootbak (OEM bootloader backup?)
Unlocking bootloader usually done to aboot and abootbak, abootbak partition may contains excactly the same image as aboot partition.
--------------------------------------------------------------------
Could someone with unlocked BL Redmi 5A dump the aboot and abootbak partitions, and share them here please?
They're main "ingredients" to unlock BL instantly without permission, only needs to enter EDL mode.
(Going to figure out if Redmi 5A's SBL/XBL will accept officially unlocked aboot from another Redmi 5A or if it needs more works).
Click to expand...
Click to collapse
Yep, that's pretty much a very detailed explanation. Totally forgotten about the word "kernel" :silly: was looking for that word actually
--------------------------------------------------------------------
Didn't see that coming.. You can't unlock your Redmi 5A officially? Update info please..

Growtopia Jaw said:
Yep, that's pretty much a very detailed explanation. Totally forgotten about the word "kernel" :silly: was looking for that word actually
--------------------------------------------------------------------
Didn't see that coming.. You can't unlock your Redmi 5A officially? Update info please..
Click to expand...
Click to collapse
I'm still waiting halfway (about 180 hours).
Yours unlocked?
Would you dump the two bootloader partitions (aboot and abootbak) and upload them here?

r6680jc said:
I'm still waiting halfway (about 180 hours).
Yours unlocked?
Would you dump the two bootloader partitions (aboot and abootbak) and upload them here?
Click to expand...
Click to collapse
I'm unlocked but why stop halfway?

Growtopia Jaw said:
I'm unlocked but why stop halfway?
Click to expand...
Click to collapse
not stopping halfway, it's like a backup plan, just in case after 360h of waiting and end up failed to unlock.

r6680jc said:
not stopping halfway, it's like a backup plan, just in case after 360h of waiting and end up failed to unlock.
Click to expand...
Click to collapse
Try waiting after 360 hours first. I'll try to prepare and provide you the backup if it really does fail to unlock.
Last time when I took a backup from someone, the backup contains some kind of device information from his phone (I accidentally wiped a partition and requested backup from him). I was using a custom ROM at that time (It doesn't have any problems with security thingy). Then, I decided to return back to MIUI because graphics performance is bad in custom ROM (I can't even open Real Racing 3. It keeps force closing). After flashing MIUI and the backup, I rebooted the phone. Then, it suddenly says "This device is associated with an existing account. For security reasons, you need to enter password to verify the device." This is what it looks like:
I recommend you to wait for the period to finish first. If it really really doesn't work, you can try it out with your method.

Download links needs to be updated they are offline =x

jasonhelene said:
Download links needs to be updated they are offline =x
Click to expand...
Click to collapse
Sorry about that, the hosting provider is currently moving all the website on their server manually. It'll be months probably.. I'll post a temporary link to the downloads ASAP.
Thank you

Related

[GUIDE] All-in-One Moto E Beginner's Guide

{
"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"
}
About the guide
This guide is to provide information about the phone and directions about modding your phone. Most of the stuff is already posted in the forums while some of it is not. I'll try my best to explain how the stuff works for Moto E. How to Root, recover, troubleshoot so you don't screw up your phone by flashing something you're not supposed to.
Standard Disclaimer:** I'm NOT responsible for any damage you do to your phone trying to mod it. Understand how to recover from issues carefully. **
Index
I just bought a Moto E, now what?
Starting Up -Drivers, ADB and Fastboot.
Facts - Bootloader & Recovery.
Beginning the workout
Unlocking Bootloader
Flashing Custom Recovery
Rooting.
I just bought a Moto E, now what?
Congratulations on your phone. Now you should understand the device you have.
Moto E has three variants,
XT1021 - Single SIM
XT1022 - Dual SIM
XT1025 - Dual SIM with TV
Determine what variant you have. Its important as some mods maybe specific to one device and might not work with other.
To get more info about your device, I'd recommend giving this FAQ thread some time.
[FAQ] Frequently Asked Questions For Moto E
Starting Up - Drivers, ADB & Fastboot
So let us begin. You need to setup your system first.
Drivers, Get your drivers from Motorola Motorola Device Manager. Install it.
ADB & Fastboot.
[Option 1]
(Android SDK), Android SDK is the Android Software Development Kit. It includes the tools to develop apps and debug your device.You need it in order to mod your device and recover sometimes.Get it from Android SDK Its a big package in terms of size.
[Option 2]
If you don't plan to develop anytime soon and concerned with the size, you can get the Minimal ADB & fastboot from [TOOL]Minimal ADB and Fastboot
Setting UP ADB & Fastboot:
You need to set you path variables so you can run ADB & Fastboot commands without worrying about your present directory.
Extract your SDK package to a directory. (or installation path in case of minimal)
Run SDK Manager.exe. It might show few packages available to download. Tick everything under tools.Click Install packages. Accept license. Install
Naviagte to platform-tools (it should have files adb.exe & fastboot.exe)
Copy the path
Now goto Control Panel > System
Click Advanced system settings
Click environment variables
In the box, find 'Path' under system variables. Select it and click Edit
Now, Paste your SDK path in the Variable Value after a ; (It should be something like this C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;I:\Android SDK\platform-tools Click OK
Done, close the boxes and windows.
Now time for validation. To verify if you've setup the system correctly.
Get your phone and goto Settings>About Phone.
Tap on Build Number 7-10 times (until it says 'You are a developer'), You've enabled developer options.
Goto Settings> Developer options.
Under Debugging, tick USB DebuggingClick OK.
Connect your phone to your PC (on a USB 2.0 port). It might install some drivers, let it finish.
Now open the command prompt on your PC.
Type
Code:
adb devices
.
You will get a prompt on your phone to authorize. Tick 'Always Allow from this computer' And click OK.
It will show the device ID followed by 'device'.
Done, your system is ready.
IMP: If you encounter some errors. Check Troubleshooting.
Facts - Bootloader & Recovery & Rooting.
Bootloader
Bootoader is a small code that reside in your device. When your phone is turned ON, it loads all the hardware and the software of your device and make your phone come alive.
Locked BL & UNLocked BL: Locked BL is a little insurance (for most users)for your device. It checks everything your system can flash(install) thus helps to keep it safe from unwanted or corrupted files. This sounds cool at beginning but is a nightmare for developers. This means there is no way to rewrite the stock recovery of your phone and limiting the things you can do with it(bye bye custom ROMs).
Unlocked BL on the other hand allows to rewrite the recovery (almost everything) on your phone with a custom one, but it also include the risks(everything good, comes with a price). You Lose your warranty (permanently) and your phone is vulnerable to bricking.
Its totally your choice if you want to unlock your BL or wish to remain on stock.Recovery
Then we have the Stock Recovery, this little part of your phone is also locked and cannot be removed or changed from your phone, it will allow you to make Recovery stuff like Full Wipe (Data and Cache) and install Update.zip(specific only) files.
A custom recovery is a special recovery. This allows Android Phones to do recovery tasks, like deleting data, installing recovery Zips and so on; The tasks you are allowed to do with Stock Recovery are pretty basic. Here is where TWRP comes into play.
TWRP is a Recovery that allows you to not only do basic tasks but also create Backups, Restore Them, Fix Permissions and quite a lot of other useful stuff like flashing Custom ROMs.
A Custom Recovery is installed by flashing the Recovery Partition in your Android Phone with a Custom Image.
Most importantly and commonly, Recovery is used to flash update.zip files. These files could be anything from ROM zip to apps,or certain modified system files. Whenever you see the term, "Recovery flashable", this is what meant by it. They are always in *.zip format.Rooting.
So, what’s rooting and why everyone talks about it.
Phones come “locked” , this means users can only do basic usage of their phones, installing/uninstalling apps, wallpapers and basic stuff. You can see but not touch any System file, or change the actual behavior of Android. Rooting just means you have access to your phone like an Administrator(in windows) or SuperUser(in linux), meaning you can access and change system files, delete/create files and folders and so on.
Rooting simply involves giving user rights to modify system, this is done by pushing (installing) 'su' binary into system. This can only be done by a Custom recovery and needs unlocked Bootloader. There are other methods to push 'su' binary to android system but none of those work as of now for Moto E. Unlocking BL and flashing through TWRP is the only method available. Beginning the workout
So now that you know your phone and the terms, you can begin modding it. The process followed is simple:
Unlock your Bootloader
Flash a custom Recovery
Flash Root binary
Flash the custom ROM (Optional)
Unlocking your Bootloader:
This is the first step for modding.
IMPORTANT: Unlocking your Bootloader will void your warranty permanently(Not applicable to EU users.). You cannot claim your warranty once you request the unlock key. No matter if you don't unlock, relock it or the issue is unrelated to Bootloader. That is Motorola Policy.
Also, all your apps, data, photos,music on your internal memory will be wiped make sure to back it up before proceeding.
You can follow the Guide to unlock BL by @Falcon G
[GUIDE]Unlock Bootloader - Moto E
It is well detailed.Flash Custom Recovey
After you have unlocked your Bootloader, you can flash a Custom recovery.As of now, TWRP & CWM are available for Moto E
You can easily flash it using the TWRP manager app from play store (not tested) Play Store Link
Or you can flash the recovery manually:
Manual Flash:
Download TWRP from TWRP.. Or ClockworkMod from this thread.
If its an *.img file then rename it to recovery.img . If its compressed archive (*.zip or *.tar) then extract and rename it.
Boot you phone into fastboot mode. (See tips)
Connect you phone to PC
Goto the folder where you extracted your recovery. Shift+Right Click, select 'Open Command Prompt Here'.
Type in command prompt
Code:
fastboot flash recovery recovery.img
(it should give a partition size mismatch error, don't worry about it)
Reboot.
Done.
Root
You have a custom recovery, now you can flash the root package.
You can check this thread for root, or follow the procedure below.
Download the SuperSU from this thread. DO NOT Extract it.
Copy the .Zip file to your phone. (Internal sdcard recommended)
Boot into recovery(See Tips)
Chose, flash Zip from sdcard
Chose the zip file you copied and confirm
Reboot
Done. You are now rooted. Check the phone it should have the SuperSU app.
[Optional] Flashing a custom ROM
Finally, you can flash your desired Custom ROM.
IMP: Please DON NOT ask for recommended/best/stable ROM in this thread or anywhere in the Forum. It is against forum rules
Make a complete Backup, Most important, in case you get into some error, you'll need it to recover.
You will lose your apps in the process when you wipe /data. So backup your apps too.You can use Titanium Backup or any other app from Play Store.
Download the required ROM from Dev section.(Make sure you have the correct ones depending your variant)It should be a *.zip file. DO NOT extract.
[Optional] Download Gapps. Make sure you have the ones for KK.It should be a *.zip fil as well. Again, DO NOT extract.
Download any add-ons required (like the dual-sim fix for CM)
Copy the files to your sdcard root directory, or any folder just remember it(internal recommended, however external will also work fine)
Boot into recovery.
Make a backup. Chose backup & restore amd create a complete backup.
Wipe /data /cache /dalvik cache.In case you are updating the same ROM, like flashing a nightly, you can skip wiping /data and only wipe /cache and /dalvik cache.(just for reference it is called dirty flashing).
Select 'Install zip from sdcard', navigate to the ROM .zip and select it. Let it finish.
Similarly, flash any Add-ons you have like gapps.
Reboot. First boot will take some time, be patient.

Tips and Troubleshooting
Commands can be entered via command prompt after you've setup the ADB. However, if you don't want to connect to your PC for a simpe command, download Terminal Emulator from Play Store.
Boot into Bootloader
ADB
type into cmd
Code:
adb reboot bootloader
Terminal
Code:
reboot bootloader
Manually
Power off,
Hold Power+VolUp+VolDown
In Bootloader, VolDown is used to scroll, VolUp is used to select
Boot into Recovery
ADB
Code:
adb reboot recovery
Terminal
Code:
reboot recovery
Manual
Power Off.
Hold Power+VolUp+VolDown
Scroll to recovery by using VolDown
Select Recovery by pressing VolDown
Move your App Data to sdcard using Link2SD (Coming Soon)
Flashing back your stock ROM.
Follow this guide.
[GUIDE] Restore Moto E Stock Firmware.

Manualy updating official 4.4.4 with TWRP.XT1022
Requirements: Unmodified Stock 4.4.2. Your system shouldn't be modified. All your system apps should be present & unmodified. Doesn't matter if you're rooted or have TWRP. If you have some stock files missing, either restore a nandroid if you have or flash stock ROM. Just follow troubleshooting steps.
Troubleshooting:Fixing fie verification error due to modified system files.
Extract your stock ROM
Boot to fastboot mode (bootloader)
Flash these files ONLY
Code:
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
This will restore your system to stock without afecting Recovery or user apps.
Reboot
Now continue with flashing the update
Thanks to @Deadly for verifying this method.
Flashing the Update .zip
Method 1: A little difficult,involves manually replacing the updater script, apt for advanced users
If you already have the original OTA file (Either extracted or downloaded)
Download the updater script from here. updater script
Either extract the .Zip file or use a file manager to navigate to META-INF>com>google>android
replace the updater script by the modifed one. Rezip if you've extracted (7-Zip recommended with 'store' compression)
Copy the zip to your sdcard or external card.
Boot into Recovery(TWRP)
Wipe Cache & Dalvik
Select Install
Select your Zip file and confirm.
Reboot
Done.
Method 2:.Easier method and ready to flash zip
If you haven't downloaded the OTA or don't mind downloading an additional file (~60 MB)
Download file .Blur.Zip
Copy the zip to sdcard (internal or external)
Boot to recovery
Wipe cache and Dalvik
Select Install.
Select the Blur.zip
Reboot
Done.

IMP:
Flashing will take a few minutes so be patient.
Some users have reported that after OTA custom recovery doesn't stick(unconfirmed as of now).
If you flash it using TWRP, your custom recovery will be intact and you can re-root.
Thanks to @Gogeta for providing the OTA Zip file.

Nice Guide I'll reserve one here for future

Nice job man.

Falcon G said:
Nice Guide I'll reserve one here for future
Click to expand...
Click to collapse
Hetalk said:
Nice job man.
Click to expand...
Click to collapse
Thanks guys. Remind me if I've missed something.

Any tips on SIM Unlock method
neo.ank said:
Thanks guys. Remind me if I've missed something.
Click to expand...
Click to collapse
I have rooted Moto E but with SIM Lock. Any custom ROM can remove this?

orionmb said:
I have rooted Moto E but with SIM Lock. Any custom ROM can remove this?
Click to expand...
Click to collapse
Not likely. Though it depends on the type of lock it has.
BTW, whats your variant and your carrier.?

neo.ank said:
Not likely. Though it depends on the type of lock it has.
BTW, whats your variant and your carrier.?
Click to expand...
Click to collapse
I have XT1021 and locked to O2 UK. Cannot find anyone from the paid services who can provide the unlock code so decided to root and investigate if its possible this way. Running CM11 (4.4.4).

A much appreciated thread. Good work buddy! :good::highfive:
But a clarification is regarding warranty:
neo.ank said:
Unlocking your Bootloader:
This is the first step for modding.
IMPORTANT: Unlocking your Bootloader will void your warranty permanently. You cannot claim your warranty once you request the unlock key. No matter if you don't unlock, relock it or the issue is unrelated to Bootloader. That is Motorola Policy.
Also, all your apps, data, photos,music on your internal memory will be wiped make sure to back it up before proceeding.

Click to expand...
Click to collapse
While Indian customers will deinitely loose warranty if they've rooted or unlocked the boot-loader, I don't think it's applicable to EU customers. Please look here for more information.
Please make the appropriate changes if I'm right. Cheers!

orionmb said:
I have XT1021 and locked to O2 UK. Cannot find anyone from the paid services who can provide the unlock code so decided to root and investigate if its possible this way. Running CM11 (4.4.4).
Click to expand...
Click to collapse
You will need the unlock code. Flashing a ROM wouldn't unlock it.
Perhaps the paid unlock services haven't listed it yet.It might be available in near future. Can't say anything for sure.
Ex-Hunter said:
A much appreciated thread. Good work buddy! :good::highfive:
But a clarification is regarding warranty:
While Indian customers will deinitely loose warranty if they've rooted or unlocked the boot-loader, I don't think it's applicable to EU customers. Please look here for more information.
Please make the appropriate changes if I'm right. Cheers!
Click to expand...
Click to collapse
Added to the guide. :good:

Added manually flashing OTA for XT1022 using TWRP

neo.ank said:
Added manually flashing OTA for XT1022 using TWRP
Click to expand...
Click to collapse
Thank you for the extensive guide and update instructions.
So I should flash stock ROM, then flash TWRP
then the update.
Is it correct process.?

coefficientoffriction said:
Thank you for the extensive guide and update instructions.
So I should flash stock ROM, then flash TWRP
then the update.
Is it correct process.?
Click to expand...
Click to collapse
Yes you are absolutely right.

neo.ank said:
Yes you are absolutely right.
Click to expand...
Click to collapse
I'm flashing stock ROM now. I will post the result after trying your file.

Its not working....It shows failed using step 2... !!

dubai1991 said:
Its not working....It shows failed using step 2... !!
Click to expand...
Click to collapse
Which method did you use.?
And can you post the exact error you got.? at which step.?

it fails while verifying the zip file. tried with unticking the zip file verification and error is binary error... !!!
---------- Post added at 08:04 PM ---------- Previous post was at 07:58 PM ----------
Method 2.. Zip file verification failed.

dubai1991 said:
it fails while verifying the zip file. tried with unticking the zip file verification and error is binary error... !!!
---------- Post added at 08:04 PM ---------- Previous post was at 07:58 PM ----------
Method 2.. Zip file verification failed.
Click to expand...
Click to collapse
Is your system unmodified.?
Have you modified or removed any system app?

Where is the Ota update zip....
Sent from my XT1022 using XDA Premium 4 mobile app

[Recovery][Lenovo P2][P2a42] Official TWRP for the Lenovo P2 (3.2.2-0)

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.

[GUIDE][KENZO/KATE] Install LineageOS with locked bootloader

{
"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..

[RECOVERY][ROOT]TWRP 3.1.0-1 Samsung Galaxy J3 Emerge SM-J327P

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"

No matter what i do its still giving me error 7 in LEX727

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?

Database Users

welcome