Related
Hello Guys,
At first a little background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately, I applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
I am not responsible if anything goes wrong.
Ok, so let's get started:
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Windows: https://forum.xda-developers.com/showthread.php?t=2588979
Linux/Mac: http://rootmygalaxy.net/install-adb-and-fastboot-on-mac-or-linux/
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of your choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip not working anymore, official link:
http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201801.zip
-As many of you are experiencing problems with my previously mentioned TWRP 2.8.7.3 version I am replacing the link with the official TWRP Shield Tablet Download Site. Just take the newest stable version: https://dl.twrp.me/shieldtablet/ (Put the file into the ADB+Fastboot Folder)
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder): Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "sudo" in front of it...)
Mac:
You also don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "./" in front of it...)
Flash Recovery
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installed, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
EDIT: 4.1 To enable the fastboot protocol, you must select "Fastboot mode" on the Tablet. After that type
Code:
fastboot devices
in order to check if fastboot is enabled.
5. Before you can do anything you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. Now you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-x.x.x-x-shieldtablet.img
6.2 Wait until it is finished then navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a custom rom
Custom Rom
If you want to be on the safe side you should consider wiping the /data partition (Troubleshoot section at the end of the Post)
1. You can access your tablet from your PC
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice.
2.1.1 Cyanogenmod 12.1 (Android 5.1.1) and BlissPop v4.0.3 https://www.androidfilehost.com/?w=files&flid=150249
2.1.2 Cyanogenmod 13.0 (Android 6.0) https://androidfilehost.com/?w=files&flid=27600&sort_by=date&sort_dir=DESC
2.1.3 Nvidia Shield Tablet Resurrection ROM (Android 6.x) https://androidfilehost.com/?w=files&flid=60681&sort_by=date&sort_dir=DESC
2.1.4 BlissPop
2.2 Download Google Apps (Gapps) (ARM Device)
2.2.1 Android 5.1 http://opengapps.org/?api=5.1&variant=stock
2.2.2 Android 6.0 http://opengapps.org/?api=6.0&variant=nano
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
3.1 Now go to Wipe. For a dirty flash you will only need to wipe the Dalvik and Cache for a full wipe select Dalvik, System, Data, Cache
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips and select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
For Android 7.0 (Nougat) the SuperSU r4 2.78 version is confirmed working.
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installed
Xposed Framework
Download the Xposed Framework Zip file, take the newest version:
(The Shield Quad Core has a 32 bit arm architecture, so you need the framework for arm)
SDK21 for Android 5.0: http://dl-xda.xposed.info/framework/sdk21/arm/
SDK22 for Android 5.1: http://dl-xda.xposed.info/framework/sdk22/arm/
SDK23 for Android 6.0: http://dl-xda.xposed.info/framework/sdk23/arm/
and the apk: https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609
and move them to you Tablet.
Developer Thread (for the uninstaller): https://forum.xda-developers.com/showthread.php?t=3034811
Go to Recovery with Root
1. Now that you have root you don't need you PC anymore. Go to the Play store and download Quick Boot
2. Open Quick Boot and klick on Recovery
3. Allow Root rights and the Tablet should boot into recovery
Go to Recovery without Root
1. Shut down your Tablet
2. Press and hold the Vol down button and the Power button until the Bootloader screen appears
3. Navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
Install Xposed Framework
1. In the TWRP Recovery (Optionally you can make a Backup) select Install and choose the xposed-v80-sdk22-arm.zip file
2. When you get an Error let me know
3. Now Restart you Tablet and install the .apk file normally
4. In the App Press Framework and now there should be a green writing saying: Xposed Framework version 80 is active
5. Here is a list of very useful programs for the Xposed Framework: http://forum.xda-developers.com/android/general/best-xposed-modules-android-t3103027
Please Leave a post if you are getting errors or something isn't clearly explained! And if I could help you, consider giving me a Thanks
Troubleshoot
If you are stuck in a Bootloop:
Without data loss(e.g. when you installed Xposed framework zip and its stuck in a bootloop)
1. flash the stock rom boot image BUT ONLY IF YOU DONT USE A CUSTOM ROM (it will probably loose root). go to https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet K1&tx=$additional,shield and download the latest NVIDIA SHIELD Tablet K1 Recovery OS Image
2. Unpack the zip file and flash it to your Tablet
Code:
fastboot flash boot boot.img
If something went wrong while flashing a custom rom (after that you will need to flash the custom/stock rom again)
wipe the /data partition. It could be encrypted from the previous rom. Be aware that you need to reinstall the rom, therefore loose all your data. Troubleshot guide by agentbob123
-Toby
Credits:
@xsquid mac support
@agentbob123 suggestion to mention to wipe the /data partition as a solution for being stuck in a bootloop
@champs777 suggested the newest TWRP
@grävling mentioned importance of waiting until the recovery flash is finished
Toby9 said:
Hello Guys,
At first a litte background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately i applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
Ok, so let's get started:
I am not responsible if anything goes wrong.
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of you choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder):
Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a sudo in front of it...)
Mac:
2016/02/16 Please leave a post if you how to do this
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installen, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
5. Before you can do anyting you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. No you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-2.8.7.3-shieldtablet.img
6.2 Wait until it is finished then move with the volume buttons through the Menu on your Tablet an choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a cutom rom
Custom Rom
1. You can access your tablet on your pc
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice. I decided to use Cyanogenmod 12.1 (Android 5.1.1) http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
2.2 Download Google Apps (Gapps) (ARM Device) http://opengapps.org/?api=5.1&variant=stock
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips an select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installen
Please Leave a post if you are getting errors or someting isn't clearly explaned!
-Toby
Click to expand...
Click to collapse
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
xsquid said:
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
Click to expand...
Click to collapse
Thank you I added this in guide
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
Try other TWRP versions like 2.8.7.0 or 2.8.7.1 i think the 3.0.0.0 is for Andoid 6.0 devices so if you are currently in the newest version of the Android OS try this one out
The 3.0 versionof TWRP was unstabel on my device so you should flash it wipe the storage and flash one of the older ones
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
fards said:
Try deleting recoveryonboot.p in /system
Click to expand...
Click to collapse
Credit to fards.
xsquid said:
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
Credit to fards.
Click to expand...
Click to collapse
How can I remove this file without root ?
SonicDBZFan07 said:
How can I remove this file without root ?
Click to expand...
Click to collapse
Try your normal command line for flashing recovery except change flash to boot. It doesn't flash it, just boots to it.
In other words, if you are using:
1. Fastboot Flash recovery recoveryname.img
Do instead:
2. Fastboot boot recovery recoveryname.img
While in recovery (make sure the supersu zip is on the sd card or wherever you normally flash files from first) flash supersu. You should now be rooted but without a recovery.
Go then to delete the file and then reboot, flash the recovery as normal (#1), reboot and then it should be good to go. It was for me.
rooted device no need to unlock bootloader it will unlock for ittself
just go to playstore and dowload twrp manager
choose the name of your device
and choose one of the two versions available
for shield tablet the version 3.0.0.0 doesnt work well it spilts the screen but wthe other version Works great
the link is twrpmanager on play.google
this way you dont need to connect your tablet to your pc
Great work!
Thank you for the awesome guide. Besides deleting the TegraOTA apk, is there any other app/service that I should disable to prevent OTA updates?
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
diji1 said:
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
Click to expand...
Click to collapse
I'm sorry that you had that problem but this guide is a general guide and not an screw nvidia (besides they are awesom giving us a really good tablet for 200 Buck, but jea?) guide. TWRP v3.0.0 has his bugs so generally when you have finished deleting the stock rom you should flash TWRP 2.8.7.3 works the most stabel.
Trafalgar Square said:
Great work!
Click to expand...
Click to collapse
Thanks, i appreciate that
Add TWRP to M image (Shield 1.1)
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
psychic99 said:
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
Click to expand...
Click to collapse
After you flash twrp reboot to recovery. I may be wrong, but I think the stock ROM overwrites the custom recovery at reboot. If you reboot to twrp first after flash, twrp will disable this.
Sent from my SHIELD Tablet K1 using Tapatalk
Rooting
Hi everyone,
Yesterday got my new Nvidia Shield Tegra K1 and upon using it I noticed it's a great tablet for it's price range and will do my job easier while flying my Phantom 4. To be honest it's seems very stable and solid but was thinking about rooting it. I have some questions regarding the process wince I haven't rooted anything since my HTC Fire, log time ago that was. What are the benefits of rooting this device ? Will I still be able to update the Shield with its official updates ? Will I be able to roll back to an unrooted tablet should I need too ? I wasn't planning on flashing a custom rom but if I'll do what are the pros and cons of doing so ? I know that maybe searching this forum I would find all the answers needed but since there is so much information and threads I'm lost as from were to start from.
Would be nice to guide me about how to properly root my device with all the necessary links. My tab is running on Android 6.0.
I thank you so much guys for the hard work you all do in providing such information. I know it takes a lot of time and patience.
I just got a Shield K1. I like it a lot but I wanted to root it. Then I saw how confusing it is to distinguish between it and the previous model. My guess is whatever is out there that says Shield Tablet means the old one not the K1. I also updated mine to MM cause I'm using and 128GB micro sd card for internal storage. I guess I'll just have to wait until more support comes out for this tablet such as a stable TWRP 3.0 Recovery and the ability to gain root access and custom ROMs like CM 13.
do you recommed to install all OTAs before install custom recovery and custom roms or is it better to install twrp-2.8.7.1 out of the box and then go for the custom stuff ?
I would install all updates to get the latest bootloader. Do not install twrp 2.8.7.1. Install the official 3.0.x from the official site.
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?
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Code:
C:\Users\Fish\Downloads\ADB>adb devices
List of devices attached
e33edd51 sideload
MrGodMan said:
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Click to expand...
Click to collapse
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Choose an username... said:
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Click to expand...
Click to collapse
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
MrGodMan said:
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
Click to expand...
Click to collapse
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Choose an username... said:
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Click to expand...
Click to collapse
Perfection.
Everything works!
I have a relatively old xperia xz premium [g8141] and since the look is getting quite old I thought why not root it? or maybe flash a rom.
So I started by unlocking the bootloader using sony's tutorial, and then flashing the latest version of TWRP (twrp-3.3.1-0-maple) using ADB (you need to Install the Adb drivers, you can do that by installing Xperia Companion). I flashed TWRP 3.3.1.0-maple (I don't recommend this version for reasons listed at the end) by doing these steps:
Moved the platform-tools to the C:\ directory.
Moved the TWRP img file to the same directory and renamed it to "recovery.img".
Opened the cmd in the same folder and entered "adb reboot bootloader" to boot in fastboot mode.
Entered "fastboot flash recovery recovery.img" to flash TWRP.
Entered "fastboot boot recovery.img" to boot into TWRP.
Then I backed up my current system and noticed error about "\data" partition and didn't think much of it since it backed up successfully. And I flashed a Stock rom [47.2.A.10.107] from XPERIASITE using Flashtool64 (I don't recommend flashing using flashtool)
After successfully flashing the stock rom I flashed Magisk using the tutorial on theirwebsite.
Everything seemed to be running fine, but then TWRP failed to backup due to a "\data" partition error, and when I fixed the error using this youtube video, the phone gut stuck in a bootloop, and flashing the stock rom agian also resulted in a bootloop. After searching xda for a solution I found out that Flashtool64 isn't recommended for flashing xzp and that you should use newflasher. That fixed the bootloop issue caused by Flashtool64.
But I still had some issues installing a new rom like ExistenZ Pie, the issues were TWRP faild to wipe Data (the "\data" partition error mentioned earlier). Turns out the latest version of TWRP had some bugs and version 3.2.2.0 worked fine and had no issues.
So I recommend these to avoid having problems:
Backing up your data before trying anything.
Using newflasher for flashing instead of Flashertool64.
Using TWRP 3.2.2.0 instead of TWRP 3.3.1.0.
The stock rom I used is [47.2.A.10.107] on my xzp [g8141] and all these worked with it:
version 3.2.2.0. (TWRP 3.3.1.0 didn't)
Latest version of Magisk.
EdXposed caused me some crashes but worked. (using Riru Core)
ExistenZ Pie. (had no issues, and the Camera still works)
**DO AT YOUR OWN RISK**
I'm not responsible for any damage, this is just the way I did it
I hope you benefit from my mistakes.
I followed your steps (specially using the older version of TWRP, it was crucial) but despite I flash magisk, the manager doesn't detect it... Any idea? Thanks
Thanks for sharing - I'm also tinkering with my Xperia XZ Premium.
-) Compiled AOSP Pie from Sony Open Devices - GCAM works but produces very grainy pictures
-) CarbonRom works - but again, no GCAM support
-) So back to stock - Get rid of all the Google Crapware and take it from there.
Thanks for the advice concerning the older TWRP version!
janvantonder said:
Thanks for sharing - I'm also tinkering with my Xperia XZ Premium.
-) Compiled AOSP Pie from Sony Open Devices - GCAM works but produces very grainy pictures
-) CarbonRom works - but again, no GCAM support
-) So back to stock - Get rid of all the Google Crapware and take it from there.
Thanks for the advice concerning the older TWRP version!
Click to expand...
Click to collapse
No problem dude, good luck
I currently on my XZ Premium have the ROM eXistenZ Pie v10.0.0 47.2.A.10.107 but I am thinking of switching to the Pixel Experience to have an experience more similar to Google Pixel phones.
ubl
How you unlock bootloader and backup drm keys form 107 ver
OscarAveiro said:
How you unlock bootloader and backup drm keys form 107 ver
Click to expand...
Click to collapse
Just follow the steps from this post: https://forum.xda-developers.com/xp...evonly-exploits-temp-root-to-backup-t3795510x
All you need to do is downgrade your phone to the version given in the post and do the drm backup, good luck!
Jad R Samara said:
I have a relatively old xperia xz premium [g8141] and since the look is getting quite old I thought why not root it? or maybe flash a rom.
So I started by unlocking the bootloader using sony's tutorial, and then flashing the latest version of TWRP (twrp-3.3.1-0-maple) using ADB (you need to Install the Adb drivers, you can do that by installing Xperia Companion). I flashed TWRP 3.3.1.0-maple (I don't recommend this version for reasons listed at the end) by doing these steps:
Moved the platform-tools to the C:\ directory.
Moved the TWRP img file to the same directory and renamed it to "recovery.img".
Opened the cmd in the same folder and entered "adb reboot bootloader" to boot in fastboot mode.
Entered "fastboot flash recovery recovery.img" to flash TWRP.
Entered "fastboot boot recovery.img" to boot into TWRP.
Then I backed up my current system and noticed error about "\data" partition and didn't think much of it since it backed up successfully. And I flashed a Stock rom [47.2.A.10.107] from XPERIASITE using Flashtool64 (I don't recommend flashing using flashtool)
After successfully flashing the stock rom I flashed Magisk using the tutorial on theirwebsite.
Everything seemed to be running fine, but then TWRP failed to backup due to a "\data" partition error, and when I fixed the error using this youtube video, the phone gut stuck in a bootloop, and flashing the stock rom agian also resulted in a bootloop. After searching xda for a solution I found out that Flashtool64 isn't recommended for flashing xzp and that you should use newflasher. That fixed the bootloop issue caused by Flashtool64.
But I still had some issues installing a new rom like ExistenZ Pie, the issues were TWRP faild to wipe Data (the "\data" partition error mentioned earlier). Turns out the latest version of TWRP had some bugs and version 3.2.2.0 worked fine and had no issues.
So I recommend these to avoid having problems:
Backing up your data before trying anything.
Using newflasher for flashing instead of Flashertool64.
Using TWRP 3.2.2.0 instead of TWRP 3.3.1.0.
The stock rom I used is [47.2.A.10.107] on my xzp [g8141] and all these worked with it:
version 3.2.2.0. (TWRP 3.3.1.0 didn't)
Latest version of Magisk.
EdXposed caused me some crashes but worked. (using Riru Core)
ExistenZ Pie. (had no issues, and the Camera still works)
**DO AT YOUR OWN RISK**
I'm not responsible for any damage, this is just the way I did it
I hope you benefit from my mistakes.
Click to expand...
Click to collapse
Hi Jad, how did you manage the loss of DRM key on bootloader unlocking?
had you any troubles with the functionalities of the device unlocking under android pie? did you use some trick in order to backup or emulate DRM keys?
thank you for yr answer.
I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402
cris2d2 said:
I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402
Click to expand...
Click to collapse
but what would that help you with? having the normal recovery?
mike500005 said:
but what would that help you with? having the normal recovery?
Click to expand...
Click to collapse
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
yes i understand but what would be the goal? what you dont like or are afraid that you dont want the recovery is it because OTA updates? or??? you can try to root it and then reflash the stock recovery.img and apply a patched boot image could work idnk cause i have already done a lot to get mine working with latest update and i don't really want to go threw all the backups again
cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
custom recovey doesn't replace rom
indeed what you descripe is the official and recommended root method. TWRP is just for nandroid backup (not really needed since Migrate Backup and Magisk Modules can flash straight from android without TWRP at all), therefore the Magisk.zip is just for traditional reasons. Many devices don't even have TWRP (or with no working encryption support)
Installation
The Magic Mask for Android
topjohnwu.github.io
We no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support
Click to expand...
Click to collapse