UPDATED NEWBIE GUIDE v2.0
FOR REDMI NOTE 3 SNAPDRAGON (KENZO)
(WORKS FOR ALL MIUI / AOSP / CM BASED ROMs)
GUIDE SECTIONS : QUICK LINKS#1 : MIUI ROM | TYPES OF MIUI ROM | TWRP | TYPES OF TWRP
#2 : TWRP FLASHABLE ZIPs | FULL PARTITION BACKUP | FLASHING ROM
#3 : RESTORING MIUI FIRMWARE (WIP) | SUMMARY | CREDITS
IMPORTANT NOTE !!- Before following any step or asking any question, please read the guide & the below comments very carefully & thoroughly
- You are choosing to make these modifications, I take no responsibility for bricked devices, dead or corrupt SD cards, accidental data wipe etc.
- This guide only supports users who have UNLOCKED their BOOTLOADER using OFFICIAL method
- I have dropped support for users who have UNLOCKED their BOOTLOADER using UNOFFICIAL method as it was risky & confusing
- This guide will be updated as new information, TWRP, methods are added. Do let me know if I have forgot to mention anything useful
MIUI ROM
MIUI (pronounced as Me-You-I) is Xiaomi's custom built firmware on top of Android like Samsung's Grace UX, HTC's Sense, OnePlus's OxygenOS which runs on their smartphones. MIUI is also the second most popular Android firmware, after CyanogenMod. MIUI is based on Android's AOSP base with its own modifications and extensive features over the top. At first glance it resembles like a hybrid between Google's Material Design and Apple's iOS. But unlike Stock Android or iOS, MIUI is very intuitive, feature rich and has multiple tweaking options.
MIUI is updated regularly depending on the development branch. Xiaomi takes reports, feedback and suggestions from the community, addresses the bugfixes and integrates new features upon request. Most of Xiaomi devices are regularly patched with monthly security updates. The flagship "Mi" series like Mi3, Mi4, Mi5 receive quicker Android version updates than their budget "Redmi" series like Redmi 2, Redmi 3, Note 2, Note 3 etc.
TYPES OF MIUI ROM
There are 2 development branches of official MIUI ROMs for all Xiaomi devices.
A) Stable Branch aka Stable Builds
- It is updated on a monthly basis or longer
- New features are added slowly after testing
- Higher system stability and less bugs than Beta ROMs
- It has a four digit numbering scheme (X.X.X.X)
- For eg. 8.X.X.X is MIUI8 Stable ROM
- Stable ROMs come in 2 variants
1. MIUI China Stable ROM
- This ROM is pre-installed on all Xiaomi devices sold in China
- It is made for the Chinese market & contains Chinese MIUI apps
- Google Apps are absent. You can install them manually or by using ADB
- It supports Chinese & English language
2. MIUI Global Stable ROM
- This ROM is pre-installed on all Xiaomi devices sold outside China
- It is made for the International market & contains English MIUI apps
- Google apps are pre-installed by default
- It supports 50+ languages
B) Beta Branch aka Developer Builds
- It is updated on a weekly/bi-weekly basis or longer
- New features are added quickly for testing
- Lower system stability and more bugs than Stable ROMs
- It has a three digit numbering scheme (X.X.X)
- For eg. 6.11.21 is MIUI8 Beta ROM for 21th Nov, 2016
- This ROM is not pre-installed on any Xiaomi device.
- You have to install Beta ROM over Stable ROM manually.
- Beta/Developer ROMs come in 2 variants
1. MIUI China Beta/Developer ROM
- It is made for the Chinese market & contains Chinese MIUI apps
- Google Apps are absent. You can install them manually or by using ADB
- It supports Chinese & English language
2. MIUI Global Beta/Developer ROM
- It is made for the International market & contains English MIUI apps
- Google apps are pre-installed by default
- Supports more than 50+ languages
Vendor aka Unofficial MIUI ROM
- Official MIUI ROM is found on Xiaomi devices that are bought from official channels
- Official channels include Xiaomi stores, flipkart.com, amazon.com etc.
- Vendor/Unofficial MIUI ROM is typically found on Xiaomi devices that are bought from unofficial channels/third-party resellers
- Unofficial channels include geekbuying.com, gearbest.com, banggood.com, ebay.com etc.
- Resellers take any of the official MIUI ROMs and modify it by injecting malwares, adwares, promotional apps etc.
- Vendor ROM may or may not contain Chinese MIUI Apps or Google Apps
- The Vendor ROM is then flashed by the reseller via EDL mode using MiFlash Tool, which bypasses LOCKED bootloader status
- Vendor ROMs can be identified by their odd 5 digit numbering scheme (X.X.X.X.X) eg. MIUI8 8.0.1.1.0, MIUI7 7.9.8.8.0
- You can identify a vendor ROM by comparing its version with official MIUI version here : http://en.miui.com/download.html
- Due to stability & security reasons, such ROMs should not be used and should be changed immediately.
- You should flash official MIUI ROMs using MiFlash Tool via EDL mode.
TWRP
TWRP stands for Team Win Recovery Project. It is a custom recovery used to flash ROMs, kernels & scripts, take full system backups, restore backups etc. There are multiple versions of TWRPs for the Redmi Note 3 Snapdragon (kenzo). Many new users are confused as to which version of TWRP to flash after UNLOCKING the BOOTLOADER OFFICIALLY.
Thanks to Xiaomi for the multiple hardware revisions, outdated kernel sources & the tiresome process of unlocking the bootloader, this device has become even more complicated for the developers as well as for the end users. Hopefully Xiaomi updates the kernel sources as soon as possible. This will result in a streamlined and unified environment for the developers while compiling ROMs and for the user for a better end user experience.
TYPES OF TWRP
1. Official TWRP : https://dl.twrp.me/kenzo/
- The base version of TWRP 3.0.2-2
- It is the stock version with no modifications done to it
- Used to flash flash ROMs, kernels & scripts, take full system backups, restore backups etc.
2. F2FS TWRP
Nougat : http://forum.xda-developers.com/showpost.php?p=70148939&postcount=3710
Marshmallow : http://forum.xda-developers.com/showpost.php?p=68023154&postcount=2
- Based on official TWRP 3.0.2-2
- Adds support for F2FS based file systems
- Specifically made for official CyanogenMod ROMs
- Compiled with Android 6.x & Android 7.1 branch respectively.
- Users can convert their /data & /cache partitions from EXT4 to F2FS for better performance (Optional)
3. Unofficial TWRP : http://forum.xda-developers.com/redmi-note-3/development/recovery-twrp-3-0-2-0-t3446909
- Based on official TWRP 3.0.2-2
- Up-to-date with Android 6.0 & Android 7.0 branch
- Adds support for F2FS based file systems
- Users can convert their /data & /cache partitions from EXT4 to F2FS for better performance (Optional)
- Can backup all partitions of the device
- Permissive SELinux
4. ZCX TWRP : http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
- Based on official TWRP 3.0.2-0
- Patches boot.img automatically (Removes dm-verity flag)
- Disables forced encryption
- Updated to Android 7.1 TWRP source
- SuperSU updated to v2.76
- Fixes "0MB Storage", "Unable to mount /" errors
- Adds support for Android 6.0 /data partition decryption
- Can be used to flash incremental OTA updates on MIUI rooted ROMs
5. Cofface TWRP : http://forum.xda-developers.com/redmi-note-3/development/recovery-kenzotwrp-cafface-3-0-0-t3369341
- Based on official TWRP 3.0.0-0
- Patches boot.img automatically (Removes dm-verity flag)
6. Safe TWRP v2 : http://forum.xda-developers.com/redmi-note-3/how-to/modified-twrp-deleting-emmcappsboot-t3371667
- Based on Cofface TWRP 3.0.0-0
- Patches boot.img automatically (Removes dm-verity flag)
- Specifically compiled for users who UNLOCKED the BOOTLOADER using UNOFFICIAL method.
- Prevents hardbrick while flashing MIUI Recovery ROM Zip or incremental OTA Zip
7. Alka TWRP : http://en.miui.com/thread-282773-1-1.html
- Based on Cofface TWRP 3.0.0-0
- Patches boot.img automatically (Removes dm-verity flag)
- Disables forced encryption
- Can backup all partitions of the device
TWRP FLASHABLE ZIPS- These zips are meant to be flashed with TWRP with a specific order.
- Before flashing any zip make sure you have taken full backup of your device partitions using TWRP.
- Steps for full backup are mentioned in the next section.
PATCHES
1. Universal Boot Image Patcher : http://forum.xda-developers.com/redmi-note-3/how-to/modified-twrp-deleting-emmcappsboot-t3371667
- This zip patches the boot.img i.e. it disables "dm-verity" (Lollipop Only)
- Use this zip if you are having official TWRP, F2FS TWRP, Unofficial TWRP installed.
- All other TWRPs automatically patch the boot.img so no need to use this zip.
- This zip has to be flashed immediately after flashing MIUI Lollipop Recovery ROM else your ROM wont boot.
2. Lazy Flasher : https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view
- This zip patches the boot.img i.e. it disables "dm-verity" and disables forced encryption (Marshmallow Only)
- Use this zip if you are having Official TWRP, F2FS TWRP, Unofficial TWRP, Cofface TWRP, Safe TWRP v2 installed.
- If you are using ZCX, Alka TWRP no need to use this zip
- This zip has to be flashed immediately after flashing MIUI Marshmallow Recovery ROM else your ROM wont boot.
3. VoLTE Patch : http://forum.xda-developers.com/redmi-note-3/development/volte-patches-nougat-based-cm-roms-t3509257
- This zip is to be flashed on specific Android 7.x Nougat based ROMs
- It enables VoLTE support by flashing modem partitions
4. RR 5.8.0 Fingerprint Fix : http://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-enable-goodix-fingerprint-t3507979
- This zip is to be flashed on Resurrection Remix 5.8.0
- This zip enables fingerprint sensor support for models having Goodix FP sensor
5. CM13 Front Camera Fix : http://forum.xda-developers.com/redmi-note-3/how-to/fix-camera-fix-official-cm13-builds-t3454893
- This zip is to be flashed if your front camera doesnt work on CM13 ROM
- This zip fixes "Could not connect to camera" issues.
6. CM13 Security & Radios Fix : https://drive.google.com/file/d/0B2CgYqnPbCh_RnJDaHJtdEFYRGM
- This zip is to be flashed after booting into system after flashing CM13 ROM
- This zip fixes the SIM issues and the force close in Security setting
FIRMWARES
1. Multi-ROM Firmware : http://forum.xda-developers.com/redmi-note-3/development/rom-multirom-firmwares-t3519420
- This zip enables us to boot multiple ROMs on the device simultaneously
- It flashes bootloader and other partitions
- This zip locks the bootloader
2. TheStrix's CM13 Firmware : http://forum.xda-developers.com/showpost.php?p=68023154&postcount=2
- This is the firmware that CyanogenMod 13 supports. Upgrades it from LP to MM firmware.
- This zip has to be flashed before flashing CM13 ROM else fingerprint & other sensors might not work.
- This zip does not lock the bootloader
3. TheStrix's CM14 Firmware : http://forum.xda-developers.com/showpost.php?p=68671310&postcount=2
- This is the firmware that CyanogenMod 14.1 supports.
- This zip has to be flashed before flashing CM14.1 ROM else fingerprint & other sensors might not work
- This zip locks the bootloader. Flash this one if you dont want BL Lock : https://drive.google.com/file/d/0BzDVQwVyIvEbTUZCR3lkSmR6X1E/
4. Android N Firmware : http://forum.xda-developers.com/redmi-note-3/how-to/cm14-14-1-aosp-n-firmware-kenzo-kate-t3507789
- This zip upgrades your firmware to support 7.x Nougat ROMs
- This zip should be flashed before flashing any Android 7.x Nougat ROM
- This zip does not lock the bootloader
ADD-ONS
1. Xposed Framwork : http://forum.xda-developers.com/redmi-note-3/how-to/guide-installing-xposed-framework-roms-t3416123
- Before installing any zip, perform a full backup.
- Official release is for AOSP / CM based ROMs
- Unofficial release is for MIUI ROMs
FULL PARTITION BACKUPBefore proceeding towards Flashing ROMs make sure you have backed up all the partitions on your device. Incase anything goes wrong, you can always restore the backup.
Requirements:
- Windows 7 / 8 / 8.1 / 10 PC
- Unofficial TWRP / Alka TWRP / ZCX TWRP
- Running on official MIUI7 / MIUI8 Stable ROM
- BOOTLOADER UNLOCKED Using OFFICIAL method from here : http://en.miui.com/thread-202290-1-1.html
- Minimal ADB+Fastboot drivers : http://forum.xda-developers.com/showthread.php?t=2317790
1. Installing drivers & initial setup
- On your PC, go to "Folder Options" and de-select "Hide file extensions for known file types"
- Install Minimal ADB+Fastboot drivers & restart your PC
- Make sure your phone's battery level is above 75%. Switch off your phone
- Copy the desired TWRP image file inside the Minimal Fastboot directory (C:\Program Files)
- Rename the TWRP as "twrp.img" Make sure the filename isnt "twrp.img.img"
- Hold "Power Button" & "Volume Down" button together & release both of them after "Fastboot" appears
- Connect the device to PC using USB cable
2. Flashing TWRP
- On your PC, go inside Minimal Fastboot folder directory. Hold shift and right click inside the folder
- Select "Open command window here" and type "fastboot devices" inside the command window.
- If everything goes right, your device should be recognized as "<serial number> <fastboot>"
- Type "fastboot flash recovery twrp.img" & press Enter. This will flash the TWRP in the recovery partition.
- Type "fastboot boot twrp.img" & press Enter. This will boot the phone in TWRP.
- If the language is in Chinese, select the right box, & select English.
- Uncheck "Keep System Read-Only" & Swipe to allow modifications.
3. Backup All Partitions
- Select "Backup" Option & select "Storage location" to external MicroSD card
- Select each & every partition & swipe to backup.
- After backing up, reboot to system.
- For additional saftey, copy the backup from MicroSD card to PC.
4. Flash Recommended TWRP
- After backup is complete you should switch to ZCX TWRP for best results
- Select "Install" Option & select "Flash Image" option
- Select Official TWRP / ZCX TWRP and swipe to flash
- After flashing go back, select "Reboot" and then select "Reboot to Recovery"
FLASHING MIUI/CM/AOSP ROM USING TWRPRequirements:
- BOOOTLOADER : UNLOCKED Using OFFICIAL METHOD
- BACKUP : Full partitions backup
- TWRP : Use ZCX TWRP for best results
1. Rooting MIUI7/8 Lollipop ROM
- Boot To TWRP
- Flash Universal Boot Img Patcher Zip (Flash if using Official TWRP, else skip step)
- Reboot to System
- Boot to TWRP
- Backup Current ROM
- Flash SuperSU Zip v2.78
- Reboot To System
2. Rooting MIUI7/8 Marshmallow ROM
- Boot To TWRP
- Flash Lazy Flasher Zip (Skip step if using ZCX TWRP)
- Reboot to System
- Boot to TWRP
- Backup Current ROM
- Flash SuperSU Zip v2.78
- Reboot To System
3. Flashing MIUI7/8 Lollipop Recovery ROM
- Boot To TWRP
- Backup Current ROM
- Factory Reset
- Flash ROM Zip
- Flash Universal Boot Img Patcher Zip (Flash if using Official TWRP, else skip step)
- Reboot To System
3. Flashing MIUI7/8 Marshmallow Recovery ROM
- Boot To TWRP
- Backup Current ROM
- Factory Reset
- Flash ROM Zip
- Flash Lazy Flasher Zip (Skip if Using ZCX TWRP)
- Reboot To System
4. Flashing MIUI7/8 Xiaomi.EU ROM
- Boot To TWRP
- Backup Current ROM
- Factory Reset
- Flash ROM Zip
- Reboot To System
5. Flashing Official CM13 ROM
- Boot To TWRP
- Backup Current ROM
- Flash CM13 Firmware Zip
- Reboot to Recovery
- Factory Reset
- Flash ROM Zip
- Flash G-Apps 6.0 Zip
- Reboot To System
6. Flashing Official CM14.1 ROM
- Boot To TWRP
- Backup Current ROM
- Flash CM14 Firmware Zip
- Reboot to Recovery
- Factory Reset
- Flash ROM Zip
- Flash G-Apps 7.1 Zip
- Reboot To System
7. Flashing AOSP 7.x Nougat ROMs
- Boot To TWRP
- Backup Current ROM
- Flash Android N Firmware Zip
- Reboot to Recovery
- Factory Reset
- Flash ROM Zip
- Flash G-Apps 7.0/7.1 Zip
- Reboot To System
FLASHING MIUI ROM USING MIUI UPDATER APP- This method does not require PC for flashing.
- We use the updater app present on the MIUI ROM itself to flash recovery ROM zip.
- Recovery ROM format : MIUI_DEVICENAME_MIUIVERSION_KEY_ANDROIDVERSION.ZIP
- Example : miui_HMNote3ProGlobal_V8.1.1.0.MHOMIDI_8e5f6f8e03_6.0.zip
Requirements:
- BOOTLOADER : LOCKED / UNLOCKED
- Recovery ROM : MIUI7/8 Stable/Beta : http://en.miui.com/download-301.html
- Stock : System, Boot Image, Recovery
- System : Unrooted
1. Flashing newer Global Stable version from older Global Stable version
i.e. MIUI 8.1.1.0 > MIUI 8.1.4.0
- All data will be preserved in this process, nothing will be wiped.
- Place the ROM zip inside internal storage
- Make sure battery level is above 75%
- Turn on WiFi / Cellular Data
- Open Updater App, select "Choose Update Package"
- Choose the ROM zip & select "Reboot and update"
- The update will take from 5-30 mins to install depending on the size
2. Flashing MIUI Global Beta version from Global Stable version
i.e. MIUI 8.1.1.0 > MIUI 6.12.15
- This process will wipe everything from your device, so take backup before proceeding.
- Place the ROM zip inside internal storage
- Make sure battery level is above 75%
- Turn on WiFi / Cellular Data
- Open Updater App, select "Choose Update Package"
- Choose the ROM zip & select "Reboot and update"
- The update will take from 5-30 mins to install depending on the size
3. Flashing newer MIUI Global Beta version from older Global Beta version
i.e. MIUI 6.12.9 > MIUI 6.12.15
- All data will be preserved in this process, nothing will be wiped.
- Place the ROM zip inside internal storage
- Make sure battery level is above 75%
- Turn on WiFi / Cellular Data
- Open Updater App, select "Choose Update Package"
- Choose the ROM zip & select "Reboot and update"
- The update will take from 5-30 mins to install depending on the size
4. Flashing Global Stable version from Global Beta Version
i.e. MIUI 6.12.15 > MIUI 8.1.1.0
- Unfortunately you cannot flash it using Updater-app
- You will have to use MiFlash Tool to flash fastboot ROM package
- This process will wipe everything from your device, so take backup before proceeding.
- Check out Section #3 for fastboot ROM package flashing using PC
RESTORING MIUI FIRMWARE (WIP)
- We can restore to Stock MIUI firmware from a custom ROM or softbrick by flashing a fastboot ROM using MiFlash Tool
- This method flashes all partitions using stock images. Your entire phone will be restored to factory state.
- Fastboot ROM Format : CODENAME_IMAGES_MIUI-VERSION_BUILD-DATE_ANDROID-VERSION_REGION_KEY.tgz
- Example : kenzo_images_6.12.15_20161215.0000.00_6.0_cn_7f97e1f7a9.tgz
- There are 2 ways for flashing fastboot ROM
1. EDL : Emergency Download Mode (Qualcomm Only)
- It is low-level mode used for recovering the device when phone cannot boot into system, recovery and fastboot mode
- This mode can be used on LOCKED as well as on UNLOCKED bootloaders
- We can boot into EDL mode using ADB commands, Fastboot2EDL Method, Manual Method or Deep Flash Cable
- When your phone boots into EDL mode, the screen turns blank & LED light flashes continuously
- To exit EDL mode, hold the power button for 8-10 seconds till the device restarts
2. Fastboot
- Fastboot Mode is used to UNLOCK bootloader, flash images onto the partitions, recover the device when phone cannot boot into system, recovery mode.
- This mode can only be used on UNLOCKED bootloaders.
- We can boot into Fastboot mode using ADB commands or by using Manual Method.
- When your phone boots into Fastboot mode, the screen will show "Fastboot" text and "Mi Bunny" image.
- To exit Fastboot mode, hold the power button for 8-10 seconds till the device restarts or by typing "fastboot reboot" inside command window.
Requirements:
- PC : Windows 7 / 8 / 8.1 / 10
- Mi PC Suite : http://pcsuite.mi.com/
- Mi Flash Tool
Beta : https://drive.google.com/file/d/0B9wtW2KGOf0RRS1lZGgybVVnbms/view
01/04/16 : https://drive.google.com/file/d/0B9wtW2KGOf0RaERVZXFtaGxfZ2s/view?usp=drive_web
28/10/15 : http://bigota.d.miui.com/tools/MiPhone20151028.exe
1. Flashing Fastboot ROM using Emergency Download Mode (EDL)
2. Flashing Fastboot ROM using Fastboot Mode
WORK IN PROGRESS
_____________________________________
SUMMARY
1. OFFICIAL UNLOCKED BOOTLOADERS users should use
Official TWRP
- If they plan on staying only on custom ROMs like CM14.1, AOSP
- Universal Boot Img Patcher / Lazy flasher needed after flashing MIUI ROMs
ZCX TWRP
- If they switch between MIUI & CM / AOSP ROMs
- Universal Boot Img Patcher / Lazy Flasher not needed after flashing MIUI ROMs
2. Just got a brand new Redmi Note 3 and wish to flash TWRP or a custom ROM?
STEP 1 : Verification
- Check the model : kenzo, kate, hennessy
- If kenzo, then proceed
- Verify if the installed ROM on your device is official MIUI ROM
- If NO, flash official MIUI ROM using MiFlash tool on PC via EDL mode
STEP 2 : Unlock Bootloader
- Apply for bootloader unlock
- Backup everything from internal storage, SMS, contacts etc.
- Unlock bootloader
STEP 3 : Flash TWRP
- Flash ZCX TWRP using fastboot mode using PC
- Backup all partitions using TWRP
STEP 4 : Flashing Custom ROM
- Factory Reset using TWRP
- Flash required files needed for the custom ROM
- Flash custom ROM zip
- Flash Google Apps zip
- Reboot to System
3. Follow the guides for recovering your device in case of softbrick/hardbrick, IMEI/EFS corrupt etc.
- Video Guide : Bootloader Unlock, Root, TWRP, Restore, Unbrick & ROMs : http://forum.xda-developers.com/redmi-note-3/how-to/video-redmi-note-3-bootloader-unlock-t3407003
- Flash/Unbrick On Locked/Unlocked Bootloader : http://en.miui.com/thread-235865-1-1.html
- Flash/Unbrick From HS USB 900E Mode : http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
- IMEI/EFS Repair : http://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789
CREDITS
TWRPs
Vibhor : Official TWRP
TheStrix : F2FS TWRP, CM Firmware
dadi11 : Unofficial TWRP
BY~XM : ZCZ TWRP
Cofface????? : Cofface TWRP
Rajdip : Safe TWRP v2
Alka121209 : Alka TWRP
PATCHES
Rajdip : Universal Boot Image Patcher
jcadduono : Lazy Flasher
Sudeep Duhoon : VoLTE Patch
*Moon- : RR 5.8.0 Fingerprint Fix
tank0412 : CM13 Front Camera Fix
banmeifyouwant : CM13 Radios & Security Fix
FIRMWARE
wmaster4g : Multi ROM Firmware
TheStrix : CM Firmware
Psy_Man : Android N Firmware
GUIDES
Tomsgt : Video Tutorial
Rajdip : Unbrick Guide
Muz_paray : Unbrick Guide
Archit9169 : IMEI/EFS Repair Guide
why after flashing alka recovery, we should again flash cofface? is alka recovery used for backup only? can we flash roms with alka recovery?
white FANNg said:
why after flashing alka recovery, we should again flash cofface? is alka recovery used for backup only? can we flash roms with alka recovery?
Click to expand...
Click to collapse
For official users you can flash other ROMs with Alka TWRP as well.
For unofficial users you must flash Safe TWRP v2 after Alka to avoid hardbrick if you flash MIUI ROM.
I am running now stocl global rom with officialy unlocked bootloader.
How can I flash Alka recovery to backup and install cm13? just use adb flash recovery?
Thanks for the initiative, can you explain more about the partitions.
What if one doesn't have all the partitions backed up and flashed custom rom ( CM 13)?
Also please include the current version of TWRP for respective recoveries.
nonyhaha said:
I am running now stocl global rom with officialy unlocked bootloader.
How can I flash Alka recovery to backup and install cm13? just use adb flash recovery?
Click to expand...
Click to collapse
fastboot flash recovery alkatwrp.img
mnsk said:
Thanks for the initiative, can you explain more about the partitions.
What if one doesn't have all the partitions backed up and flashed custom rom ( CM 13)?
Click to expand...
Click to collapse
Santhosh's CM13 zip based on M firmware has M boot loader. After flashing the zip your bootloader gets locked & gets updated to M boot loader.
So if you want to revert back to MIUI based on Lollipop you need to take backup of each & every partition using Alka TWRP, other TWRP wont work.
This restores the phone back to L boot loader & preserves IMEI.
All the links are updated to the latest versions of respective TWRPs.
SharkcpN said:
All the links are updated to the latest versions of respective TWRPs.
Click to expand...
Click to collapse
Can you also include them in the OP like official is on 3.0.2, alka on 3.0. Will be easier to keep track.
I think for officially unlocked bootloader the official TWRP should be used. You can flash the universal boot image patcher as a secondary ZIP if needed, and you can back up EFS with it
Hey all, I have successfully unlocked unofficially and flashed a alka via fastboot but I can't boot into recovery.
If I do adb reboot recovery it goes to a screen with a picture of my device which I assume is the stock recovery. If I reboot with Vol Up and Power I get the same thing. Any ideas? Thanks!
EDIT: I flashed "Safe TWRP v2" then Alka and it worked! Thanks OP
Nice information.
So the alka version is the best for official. Just want to know more:
1. Is that mean that backup/restore feature of cofface not backup all partitions?
2. Are there any differences between cofface and alka beside backup feature? Both seem not built from latest official twrp.
3. How about flashing (not restoring) other Rom from Santosh M Rom?
Thanks.
Sent from my Redmi Note 3 using Tapatalk
I installed alka version and it is in chinese, I am trying desperately to find a way to switch language, but all the guides online point to twrp theme manager, which does not work. any guide to change language from within twrp?
I flashed Cofface twrp also and the language is still in Chinese. there is no way to add some files somewhere to change the freakin' language?
Grantius said:
I think for officially unlocked bootloader the official TWRP should be used. You can flash the universal boot image patcher as a secondary ZIP if needed, and you can back up EFS with it
Click to expand...
Click to collapse
Yes you can use it too
Doublewise said:
Nice information. So the alka version is the best for official. Just want to know more:
1. Is that mean that backup/restore feature of cofface not backup all partitions?
2. Are there any differences between cofface and alka beside backup feature? Both seem not built from latest official twrp.
3. How about flashing (not restoring) other Rom from Santosh M Rom?
Click to expand...
Click to collapse
1. Yes, only Alka TWRP is capable of backing up & restoring all partitions including bootloader.
2. Alka TWRP backs up EFS (IMEI) partition as well, Cofface dosent. Rest all features are same.
3. For official unlocked users : You can flash any ROM using Alka TWRP.
Unofficial unlocked users : You must flash Safe TWRP v2 before flashing any ROM else it will lead to hardbricking.
nonyhaha said:
I installed alka version and it is in chinese, I am trying desperately to find a way to switch language, but all the guides online point to twrp theme manager, which does not work. any guide to change language from within twrp?
I flashed Cofface twrp also and the language is still in Chinese. there is no way to add some files somewhere to change the freakin' language?
Click to expand...
Click to collapse
Re-flash Alka / Cofface TWRP, you will be greeted by a chinese text. Click on the box on the right, select English & tick mark the box above slider & swipe it.
SharkcpN said:
Yes you can use it too
1. Yes, only Alka TWRP is capable of backing up & restoring all partitions including bootloader.
2. Alka TWRP backs up EFS (IMEI) partition as well, Cofface dosent. Rest all features are same.
3. For official unlocked users : You can flash any ROM using Alka TWRP.
Unofficial unlocked users : You must flash Safe TWRP v2 before flashing any ROM else it will lead to hardbricking.
Re-flash Alka / Cofface TWRP, you will be greeted by a chinese text. Click on the box on the right, select English & tick mark the box above slider & swipe it.
Click to expand...
Click to collapse
Alka and coface give an error, can't find en.xml in the zip.
nonyhaha said:
Alka and coface give an error, can't find en.xml in the zip.
Click to expand...
Click to collapse
Go to TWRP folder in the internal storage where you have installed Themes folder, delete the entire folder.
....i lost the L boot loader...
...good afternoon...
...i flashed shantosh's rom without taking backup...
...so, i lost the stock L bootloader...
...now i see the M bootloader with cyanogenmod logo...
...it's not a problem since i flashed a lot of cm based roms, and some miui roms also, with this M bootloader...
...but i want the official bunny bootloader back...
...how can i restore it back ?
...flashing with mi flash tool maby ??
Thanks for this post cos this finally clears up my confusions.... And well I suppose Cofface is good because rooting after updates is easy....But just one question....Exactly how do I install OTAs? It seems I cant install the small 150mb ota files so I have to install the fastboot rom...But do I have to wipe system before that? Because I tried flashing 7.3.6.0 update (fastboot rom 1.1gb) without wiping system and its still showing me on 7.3.5.0.... So what exactly is the method before applying OTAs?
anshulratchet said:
Thanks for this post cos this finally clears up my confusions.... And well I suppose Cofface is good because rooting after updates is easy....But just one question....Exactly how do I install OTAs? It seems I cant install the small 150mb ota files so I have to install the fastboot rom...But do I have to wipe system before that? Because I tried flashing 7.3.6.0 update (fastboot rom 1.1gb) without wiping system and its still showing me on 7.3.5.0.... So what exactly is the method before applying OTAs?
Click to expand...
Click to collapse
You need to use recovery ROM, not fast boot.
And how to move from unofficially unlocked bootloader to official unlocking?
Good Morning,
I'n a new signed member in this forum and i want to thank you for the job you've made to open this community. It's very helpful for the android modding.
However i have some doubts regarding the procedure to follow to make a complete customization of my Asus Zenfone 2 ZE551ML. My intention was to root it, but once i saw some of your Custom Rom i'm going to try to flash one of them on my smartphone. I have already read the theads of the FAQ but i haven't found nothing regarding the correct procedure. My intention is to root the phone and then install the custom Rom. I have seen that the boobtloader unlocked and the flashing of the TWRP are required, but i haven't understood the correct sequential operation to to all these tasks. I'll be very thankful if someone would help me and suggest me the procedures thru the links in the forums.
In past i have rooted my old Samsung S2 and flashed a custom rom but i have never touched the bootloader(?) or installed a custom recovery.
I did it by this order:
1.Root
2.Unlock Bootloader (Unofficial)
3.TWRP
4.Flash Custom Rom
HugoClaw said:
I did it by this order:
1.Root
2.Unlock Bootloader (Unofficial)
3.TWRP
4.Flash Custom Rom
Click to expand...
Click to collapse
Thanks, only a further question..
To root i'll follow the method two in this guide http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063
to unlock the bootloader this guide:
http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547
to install the TWRP this guide:
http://forum.xda-developers.com/zenfone2/development/z00az008-zenfone-2-t3265236
but in this case i don't know if i have to download the TWRP LP or MM version, in fact my device currently is running lollipop, but i want to install a custom rom (RR) which is running Marshmallow. Which one i should choose? and in this thread, there is no guide to install the recovery but there are only the download links, could you suggest me where to find how to do it? ..
Then i'd like to flash the RR custom rom following this guide: http://forum.xda-developers.com/zenfone2/development/rom-resurrection-remix-mm-5-6-0-t3275854
So this is what i'm going to operate, is it correct?
Yes, this is correct. It doesn't mater what version of TWRP you use. Either works, and both can flash either LP or MM.
If you don't care about OTA:
Unlock bootloader with official apk
Flash twrp with "fastboot flash recovery twrp.img"
Flash custom rom
So as far as I know, the Qualcomm variant has no Oreo rom. But I came across a RR, and LOS 15 ROM. But don't want to risk bricking my device. It says XT1768, which is my devices model.
Here is the link: https://androidfilehost.com/?w=files&flid=223472
As long as you have a Nandroid backup of your key partitions, flashing a custom ROM -- even if the ROM is corrupt or an incorrect build -- typically will not cause any major issues, especially not a brick. At worst, if the custom ROM bootloops or otherwise fails, you may simply boot back into TWRP and restore your stock Nandroid backup. If, on the off chance, your device will not boot into custom recovery, fastboot mode can be used to flash a full stock firmware package. Now don't get me wrong -- I'm not implying or advocating that it's okay to just flash a WTF.zip onto your device. In this instance, however, I think you would be totally safe giving it a try. All the ROMs on the link you provided appear to be legitimate, and the updater-script files do not flash your bootloader or other sensitive partitions. Worst case scenario --the ROM doesn't boot or it's too instable to use. Then just restore your Nandroid backup or fastboot flash a factory image.
Don't flash these roms! They will brick your phone. They are made for the Nicklaus (Moto E4 Plus). Not the perry
Roxasmaker said:
So as far as I know, the Qualcomm variant has no Oreo rom. But I came across a RR, and LOS 15 ROM. But don't want to risk bricking my device. It says XT1768, which is my devices model.
Here is the link: https://androidfilehost.com/?w=files&flid=223472
Click to expand...
Click to collapse
Those zips clearly say "nicklaus" which is the codename for the mediatek variant of the E4 Plus. Don't flash anything unless it says "perry". I recommend not installing anything you just happen to find on AFH anyway since things are uploaded there for testing and not always labeled as such.
Edit: as long as the dev added the device name to the BoardConfig.mk for the ota asserts, it should fail to flash on the wrong device anyway.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Whats Working?
Everything is working
Can change Slot A/Slot B on twrp
SDcard and OTG working
Decryption of Data working
Flashing of roms work pie and even Q roms work.
Downloads
Patched boot.img for Android 9 Stock
Patched boot.img for Android 10 Stock
Patched boot.img for Android 10 Custom
TWRP Installer zip
Information regarding boot images
Patched boot.img for Android 9 Stock
- Source built TWRP Image
- Flash this via fastboot on Stock Pie Rom(s) to get TWRP Access
Patched boot.img for Android 10 Stock
- Ramdisk Patched Android Q April Update boot image
- Flash this via fastboot on Stock Q Rom(S) to get TWRP Access
Patched boot.img for Android 10 Custom
- Bit Kernel based boot.img, patched with TWRP.
- Flash this via fastboot on any Q Custom ROM to get TWRP Access
- (Handy when you forget to flash installer and are left with a basic recovery)
Flashing Instructions
Patched boot image
- Flash the boot image via fastboot using the following command
Code:
fastboot flash boot <filename>.img
Installer
- Flash the installer zip whenever flashing a custom or stock ROM to maintain TWRP access
Note
Do not flash a mismatching twrp variant boot.img on your device, you might need to re install your whole ROM!
Credits
@Nik001 for his TWRP tree tree
reserved 1
reserved 2
After flashing stock patched boot and on android Q for the first time
Do I need to flash the custom patched boot later for customs roms or can I continue using the twrp flasher after flashing any rom?
udaycr said:
After flashing stock patched boot and on android Q for the first time
Do I need to flash the custom patched boot later for customs roms or can I continue using the twrp flasher after flashing any rom?
Click to expand...
Click to collapse
twrp flasher is enough. only flash the custom boot image when you are in a situation where you forgot to flash the installer with the rom, and you end up in a non functioning recovery.