Related
2014.10.16.: Update!
MICa.fighter said:
Hy guys! As you might noticed, the links in the OP which are pointing to the official files on the CM server don't work any more thanks to CM. I was sure this will come, but i still wanted to use the official links as long as they are working. I would change the links to my mirrors in the OP, but @Spannaa already made mirrors in his thread: Mirrors for official CM11S roms & OTA updates. I don't see any reason to have 2 threads with mirrors of the same files, so i taught I would keep this thread as a discussion on how to use those official files. I will modify the OP in the coming days accordingly.
Click to expand...
Click to collapse
I will keep the OP as it is for now, and I will modify it a little in the coming days!
Hy guys, i have seen posts about different versions of CM11S, but I haven't seen a collection of them. I collect all the stock images i can, so i taught i would share it with you guys. As the thread title says, these are official and untouched images of the stock CM11S. I share the official links where it is available. I will share four kind of files:
1. Recovery flashable zips of the complete ROMz: these are the oldschool .zip images that you can flash through recovery.
2. Fastboot images of the complete ROMz: these are fastboot.zip files, that should be used through fastboot. You need to set up Android SDK for fastboot on your computer and you also need to unlock your phone's bootloader in order to use them. For setting up the Android SDK and unlocking your bootloader, please follow this guide: [GUIDE] OnePlus One - How to Unlock Bootloader, Install Custom Recovery and Root, until you complete the first step: 1. Unlocking Bootloader. After that you have to put the fastboot.zip file into your platform-tools folder (its explained in the previous link), and extract it there, but also keep the zip there because you need that too. After that, you may follow the instructions of the Open Post of this thread: CyanogenMod 11S.
Note: The conventional fastboot oem unlock which unlocks the bootloader will wipe your phone. You can make backup before that with Helium app or through adb. Neither of them requires root.
Note: The last command in the CyanogenMod 11S thread's open post is:
Code:
fastboot update -w cm-11.0-XNPH25R-bacon-signed-fastboot.zip
The command will wipe your phone because of the "-w" option.
Note: if you get the error message during flashing in fastboot:
Code:
FAILED (remote: data too large)
Then you are probably not on the latest Android SDK with the latest required tools: Android SDK Tools, Android SDK Platform-tools, Android Support Library, Google USB Driver.
Click to expand...
Click to collapse
3. Stock kernel images: these are .img files of the stock kernel images. You can flash these in fastboot like this:
Code:
fastboot flash boot boot.img
If the filename is for example g7389215.img then it looks like this:
Code:
fastboot flash boot g7389215.img
4. Latest OTA incremental update zip: I will also share the latest OTA zip file. The CM11S OTAs are incremental updates, that means you need to be on the latest version before applying an update. Incremental means it only updates the changed files since the last update.
So for example the latest OTA ATM is XNPH33R. Before that was the XNPH30O. If you want to use the XNPH33R OTA zip you need to be on XNPH30O, because that is the latest version before the XNPH33R OTA (check reference table below). If you apply the OTA on an earlier version (for example, XNHP25R), the installation will be aborted most probably. Or if you succeed with the installation, it will break stuff most probably.
You can also grab the latest OTA update zip after you recieved the OTA file and downloaded it. You can find it in the cache of your phone and you will need root access. If you want to make a copy you should do so before you install the OTA.
Wipe the cache then you can flash the OTA update zip through recovery.
Reference table
ROM version / release date / kernel version
XNPH22R / 2014.06.06. / dunno
XNPH25R / 2014.07.03. / geb9c0a5
XNPH30O / 2014.08.11. / g7389215
XNPH33R / 2014.08.21. / g0ad30e5
XNPH38R / 2014.10.07. / g33fa374
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
2. Fastboot images of the complete ROMz:
XNPH22R
XNPH25R
XNPH30O
XNPH33R
XNPH38R
3. Stock kernel images:
XNPH22R
XNPH25R
XNPH30O
XNPH33R
XNPH38R / torrent magnet mirror
4. Latest OTA incremental update zip:
XNPH38R
Also here are the previous OTA incremental update zips:
same rule, check reference table, only use it if you are on the latest previous version! Its incremental.
XNPH33R
XNPH30O
Njoy!
You might also be interested in zephiK's modem collection of recovery flashable zips for the One: http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
Thanks was waiting for something like this.
While I appreciate this, the 33R Kernel isn't working... I tried flashing with fastboot and no go.... I'm on 33R from OTA. I'm rooted and I currently have Franco Kernel installed... (And TWRP recovery)
To reiterate, it flashes fine but when I go to boot up it stays at the One+ logo screen
How did you try it exactly?
MICa.fighter said:
How did you try it exactly?
Click to expand...
Click to collapse
flashing with adb through fastboot
You can use rashr app https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools works like a charm
Nomelas said:
While I appreciate this, the 33R Kernel isn't working... I tried flashing with fastboot and no go.... I'm on 33R from OTA. I'm rooted and I currently have Franco Kernel installed... (And TWRP recovery)
To reiterate, it flashes fine but when I go to boot up it stays at the One+ logo screen
Click to expand...
Click to collapse
You are right, the file is broken, I'm sorry. I'm going to update the OP soon with working kernel image. I'm also going to share the latest OTA grabbed from cache.
Edit: updated OP with the new 33R links, and fixed the broken kernel image. I also explained how to use the kernel images.
Thank you so much
Great post op :good:
Waiting the recovery flashable zip of XNPH33R to download. ( I am currently on XNPH22R, unlocked bootloader, with TWRP)
I am going to flash the zip through recovery ( and then flash modem from zephiK's post).
I don't need to do anything with the kernel images ( I am guessing they are there for another reason), right?
mhxmhx said:
I don't need to do anything with the kernel images ( I am guessing they are there for another reason), right?
Click to expand...
Click to collapse
You don't need the kernel images.
All the rom zip files has a kernel (boot.img). The reason i posted the kernel images separately too because custom kernel users sometimes need them. If they want to go back to stock kernel or just want to keep a backup, they don't need to download ~460MB for just the kernel image, they can download only the kernel image which is 5-10 MB.
Thank you for your work!
Thanks a lot, after flashing few mods and custom kernel my phone feels laggy, I must go back to stock
After @zephiK modem list, this is one more most usefull thread Thanks !!
So could I just flash the 33r update from stock recovery if I'm on 25r? Or do I need to update to 30O then 33r
Added to OnePlus One Resources Compilation Roll-Up Thread
[INDEX]OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
jherring002 said:
So could I just flash the 33r update from stock recovery if I'm on 25r? Or do I need to update to 30O then 33r
Click to expand...
Click to collapse
The OTA Update is incremental, which means it only updates the files that changed from the last update, in this case XNPH30O. So you sould NOT try to flash the OTA Update of 33R if you are not on 30O.
If you want to update to 33R from 25R, there are a couple of options, for example:
A) update to 30O through OTA, then you can just flash the 33R OTA update, OR
B) download the 33R full rom zip, reboot to recovery, wipe cache and flash away OR
C) make a backup of your apps and settings, through adb, or Titanium Backup, or with Helium (TB requires root), then download the 33R fastboot.zip and flash through fastboot as described in the first post. If you already have the bootloader unlocked you can skip that step. After you are done, boot up the phone, then restore your backup. The flashing method described in the open post of CyanogenMod 11S thread will wipe your phone.
The "safest" method is A, the "cleanest" method is C.
timmaaa said:
Added to OnePlus One Resources Compilation Roll-Up Thread
[INDEX]OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Click to expand...
Click to collapse
I'm out of thanks so i thank you here timmaaa :good:
Is there a flashable 30O file via recovery?
jherring002 said:
Is there a flashable 30O file via recovery?
Click to expand...
Click to collapse
Unfortunately no, but I can upload the 30O original OTA zip for you i grabbed that from cache too. You can flash it on 25R after a cache wipe. Or use it with the 25R recovery flashable zip: flash 25R zip then 30O OTA zip.
MICa.fighter said:
Unfortunately no, but I can upload the 30O original OTA zip for you i grabbed that from cache too. You can flash it on 25R after a cache wipe.
Click to expand...
Click to collapse
That would be nice. I went from 33r to 25r to see the difference in battery.
It's not that different so I wanted to go back, but when I check for ota there is not one. Says in up to date.
jherring002 said:
That would be nice. I went from 33r to 25r to see the difference in battery.
It's not that different so I wanted to go back, but when I check for ota there is not one. Says in up to date.
Click to expand...
Click to collapse
Okay I'm gonna upload the 30O OTA zip too, it will be available in the first post in a few minitues. If you want to go back to 33R you could also use the 33R full rom zip, just wipe cache and you can flash it on 25R. Make a backup before it, but i don't think there would be any problem.
Edit: Done!
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?
can somebody post the link for the stock recovery.img .??
Here.
Also, you can download one of the stock ROM images in the Guides section (ensure it matches your latest build), extract the image and inside will be a recovery image.
echo92 said:
Also, you can download one of the stock ROM images in the Guides section (ensure it matches your latest build), extract the image and inside will be a recovery image.
Click to expand...
Click to collapse
Its for the other ougat build npj25.75..Version ....But I have the npj 25.94 one..Can I use that only ??
Hey!
Do anyone know if there a recovery or TWRP file for the ZTE blade A602?
Hi All. I would also like to know if there is a custom recovery TWRP image for my ZTE Blade A602 running Android 7.0?
Thanks for help Greetings Werner
TWRP is now available for Blade A602!
My friend @Linux4 made TWRP 3.3.1 for ZTE Blade A602! It is pretty stable but it has some bugs:
- MTP, use adb push/pull
- Data Decryption (can't mount)
Important:
- Before you restart to system in first TWRP use, flash the dm-verity ZIP or the System will not boot anymore!
- If you want to root, please use SuperSU, Magisk will softbrick the Device (stucks on Splash and reboots to recovery)
- Do not flash official update.zip in TWRP. Idk why this happens, but the system is a bit corrupted, so use Stock Recovery (TaskSwitcher dead, lags and more)
- Format FRP doesn't work, but we'll make a FRP Bypass-ZIP soon.
If you are interested, i'll make a Debloat ZIP for A602. If you find bugs, please report!
Because this is my first Post, I can't send links, so i'll post the Links to a Telegram Channel (you can still view even you don't have Telegram):
t.me/a602_twrp_dl
Hello xda-developers,
Thanks for your response. My ZTE Blade A602 2017 for Germany (Android 7.0) is soft-bricked after a bad flash. Currently I have access through sp-flash tool and fastboot commands. Because I had no TWRP recovery on my ZTE Blade A602 I was not able to get a complete backup. So I am also searching for ZTE Blade A602 firmware/stock rom in Mediatek (MTK) SP Flashtool format. Do you have any help therefore. Can you also tell me where to download your mentioned TWRP 3.3.1 custom recovery image?
Thanks for help, Greetings Werner
Hey wlink!
If you have access to your Stock Recovery, flash the stock update.zip. If you have Telegram, I can send you the Link. I'll add Stock ROM Link to the Channel.
Can you also tell me where to download your mentioned TWRP 3.3.1 custom recovery image?
Click to expand...
Click to collapse
You have to enter t.me/s/a602_twrp_dl in your Webbrowser and then download the latest Build from Mega. But do not flash stock Update.zip in TWRP, the system will be corrupted, idk why but I also provide Stock Recovery on Mega Folder!
DISCLAIMER: YOU ARE RESPONSIBLE FOR WHAT YOU DOThe only reason behind posting this guide is because now we have a way to fix device if any unusual things happen after flashing beta builds. Beginners & noobs who doesn't have any idea about flashing stuff should stay away.
PREREQUISITES:
1. Bootloader Unlocked Device
2. OrangeFox
3. Stable OZIP (Android 10 | realmeUI 1.0 | C35)
4. Beta ZIP (Android 11 | realmeUI 2.0 | F06)
5. Unofficial OrangeFox beta build (For realmeUI 2.0 A11 FW only)
6. realmeUI 2.0 stock recovery
7. A11 VBMETA
8. Patched VBMETA
PROCESS TO FLASH:
1. Just to be on safer side we are going to make sure everything is stock & all partitions are unmodified. So reflash latest Stable OZIP (C35) via OrangeFox.
2. Format data & reboot to System (This is optional but better to do it, we never know what might happen with realme device)
3. Reboot back to Bootloader if realmeUI 1.0 boots fine
4. Flash OrangeFox build which you used previously & also flash patched vbmeta (fastboot flash vbmeta patched_vbmeta.img)otherwise you get "Boot is destroyed........"
5. Boot into custom recovery & copy downloaded Beta ZIP
6. Flash the Beta ZIP & format data.
7. Reboot to System. realmeUI 2.0 should boot now.
COMMON ISSUES & FIXES:
1. Device stuck at white realme splash logo
Sol. Few people reported it booted when they flashed patched vbmeta so you can first try that. If doesn't work then you can flash A11 vbmeta (fastboot flash vbmeta vbmeta.img) attached here & reboot to system
2. Device stuck at Yellow realme boot animation
Sol. If it's stuck for more than 2-3mins then reboot to bootloader & format data by executing fastboot erase userdata ., never do fastboot -w it's messing up data partition in A11 due to new changes introduced by realme
3. Stuck in bootloader (fastboot)
Sol. Flash the unofficial OrangeFox rescue build & boot into it, copy C35 OZIP to internal storage. Flash it & format data. Reboot to System. Wait for public realmeUI 2.0 release.
4. Unofficial OrangeFox beta build stuck at Ofox splash & display keeps blinking
Sol. This happens because Ofox can't decrypt realmeUI 2.0 data, only way to boot this ofox build properly is by formatting data, reboot back to bootloader. fastboot erase userdata
5. Device doesn't have realmeUI 2.0 Stock Recovery
Sol. Flash the attached stock recovery
reserved
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
bharatgsp said:
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
Click to expand...
Click to collapse
na it doesn't work
ChromiumPD said:
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Click to expand...
Click to collapse
Right will update guide, thank you
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
kurtextrem said:
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
Click to expand...
Click to collapse
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Zippka224 said:
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Click to expand...
Click to collapse
edited guide, use ofox only. TWRP doesn't seem to work for everyone.
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
4j17h said:
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
Click to expand...
Click to collapse
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Tierri said:
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
Click to expand...
Click to collapse
Well there are two ways, we can use stock recovery to downgrade from beta builds to C34
Another way would be to flash unofficial Ofox build, copy C34 OZIP to internal storage & flash it.
kurtextrem said:
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Click to expand...
Click to collapse
OTA updater app is verifying the update & rebooting to stock recovery, so if we can figure out the same way we can install custom ozips via stock recovery too
How would you recommend to bring over apps & their settings to A11? After formatting data they'll be lost. Which backup method is able to restore them? Have you rooted it already?
Magisk?
Cool ! It works fine thank you.
but I noticed that the "Unofficial OrangeFox beta build" cant mount internal storage issue with following error : "could not mount /data and unable to find crypto footer"
So is there another way to Root my device without wiping data?
Hi
First Thank you for this post .
I want to restore a stock recovery UI 1.0 now i am using orangefox recovery on C.34
can i restore without format data or waiting UI 2.0 stable ??
Many Thanks
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
tuga49 said:
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
Click to expand...
Click to collapse
try to install patched vbmeta its work form me
So for me I dirty flashed the f06.zip beta on c.35 in official [email protected]_1 release and flashed vbmetaA11 but it failed to then i flashed patched_vbmeta.img and voila it booted just fine and optimizing apps appeared.
Thanks very much to Original Poster we can now use Realme UI 2.0 because of him.
Thanks a lot once again