Related
This tutorial will teach you how to root, install a custom recovery and deodex the ROM on your Mediatek processor smartphone. You can use this tutorial for other Android devices too, Lenovo or not.
I myself own a Lenovo A390 and I have rooted, installed recovery and deodexed using these software tools, without any pain. And I assure you, it will be extremely rare that anything can go wrong. And you don't need a computer to root or install recovery-yes, you can do it on your phone itself.
But let's get some things straight:
1. Rooting/installing recovery voids your warranty.
2. If you're not using a Lenovo device or a device that runs on a MediaTek processor, I recommend that you search for a version of recovery appropriate for your processor.
3. The chances of damaging your phone using these tools is extremely rare, trust me, but in case anything goes wrong, I, OR THE DEVELOPERS OF THESE TOOLS, OR XDA-DEVELOPERS WILL NOT BE RESPONSIBLE FOR ANY INTERNAL/EXTERNAL DAMAGE TO YOUR PHONE.
How to root your Lenovo a390:
1. Download Framaroot: http://forum.xda-developers.com/showthread.php?t=2130276 Note: Framaroot may not work on all Android devices. Please see compatibility list in the link.
Framaroot is an Android app created by XDA user alephzain. It allows you to root your device directly from your Android device-please click on link above to view full compatibility list. Download and Install this app. If it says "Installation blocked", go to your phone's Settings>Security and tick the "Unknown Sources" box. (Believe me, there are n00bs )
2. Open Framaroot. For the a390, there is only one exploit-Boromir, since it's a Mediatek powered device. Select Boromir.
3. Now you see two buttons: Install Superuser and Install SuperSU. You need to select only one of them. Framaroot will then root your device and install Superuser/SuperSU. (Superuser/SuperSU are apps which control root operations on your device ie. ensure no app uses root features without your permission-it is a MUST.)
The choice is up to you, but I'd recommend Superuser since it's like the Industry standard of rooted Android phones.
4. Reboot your phone. You'll find Superuser installed. Open it, swipe from left to right to access Superuser settings. The su binary is outdated and it'll appear in a red font. Tap it to update su binary.
This is proof enough that your phone is rooted, but if you really need to see, here's one more step.
5. Install Root checker from Google Play Store: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck
Run this app, and if your phone is rooted, Superuser will come up automatically asking you whether Root Checker should be granted permission- press Yes and root Checker will deliver the result.
That's it-congratulations, you've rooted your a390 without any pain. Now you can flash a recovery, install Busybox, overclock your phone, get rid of the dumb apps Lenovo has included with the a390.... Enjoy! :laugh:
How to install a recovery
Now, there are two recoveries that rule the Android universe: ClockworkMod Recovery (CWM), and TeamWin Recovery Project (TWRP). The bad news is, neither is officially available for the Lenovo A390 or most of MediaTek devices. But where there's a will, there's a way- and some anonymous Android developer has created TWRP recoveries for the entire Lenovo smartphone series. <salute to the unsung hero> I used one specially customised for the A390, and it works fabulously.
First of all, ensure that your phone is rooted. If not, read the tutorial above.
1. Download this recovery.img file from this Google Drive: https://drive.google.com/file/d/11-...c9b-MfFTWpi9D_vBI0oVISPgRVcB/edit?usp=sharing
2. Install Recovery Tools-Flasher from the Google Play Store: https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
3. Now press "Flash Recovery" button, it will open a file browser. Select the recovery.img file you downloaded from the file browser.
4. It should show a dialog box that says Flashing done. Press OK to boot into recovery. Press OK, and you'll see the TeamWin IdeaPhone load screen-and boot into TWRP.
Congrats, you've installed the recovery. Now you can install custom ROMs on your phone and backup your phone's kernels as protection against troubles. Enjoy! :highfive:
How to deodex your phone's ROM
Sadly, you cannot do this using your phone. You'll need a Windows PC for this process, a good Internet connection as you'll have to download large files for this process, and plenty of time.
Here's a good XDA Developers Tutorial on how to deodex your rom, complete with step-by-step explanation and screenshots: http://forum.xda-developers.com/showthread.php?t=2374008
There you go. If you followed my tutorial completely, you are now a proud owner of a rooted, recovery-flashed, deodexed MediaTek device/Lenovo A390.
Enjoy!
Please hit Thanks button if my post helped you.
Hello All,
Root
If on stock, uprooted (ever), go to method 1. If not, keep reading.
Now, in the latest Molly CF-AutoRoot, it flashes a modified kernel to gain root that causes OTA updates (i.e. impending 5.0.1) to fail, this was due to the fact that until a couple days ago, the modified kernel was necessary. Chainfire found a way to fix it without modifying the kernel and implemented it in SuperSU 2.37. If you are rooted, used CF-Auto Root, and wish to retain root, but regain the stock kernel for OTA's, simply follow root method 2.
Method 1
To Root from stock LPX13D, Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices, and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected.
8. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery!
9. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
10. Select "Install Zip from sideload"
11. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
12. (On ADT-1) Select "**Go Back**"
13. Select "Reboot to system"
14. Select "No" when asked to restore Root, as this's feature does not work yet.
15. Profit!
Method 2
To Root from CF-auto rooted LPX13D and regain stock kernel (This will not restore Build.prop and other system changes!), Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
- stockbootlpx13d.img
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices", and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected
8. Run "fastboot flash boot stockbootlpx13d.img"
9. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery! Then you must run "fastboot reboot recovery"
10. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
11. Select "Install Zip from sideload"
12. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
13. (On ADT-1) Select "**Go Back**"
14. Select "Reboot to system"
15. Select "No" when asked to restore Root, as this's feature doe snot work yet.
16. Profit!
Unroot
Requirements:
- stockbootlpx13d.img
- recovery.img
1. Enter the SuperSU app, and go to Settings ==> Full Uproot, and verify your choice. (Stop here if you didn't use CF-auto root)
2. Plug your ADT-1 into your PC and run the command "cd desktop", then "adb reboot bootloader", then "fastboot flash boot stockbootlpx13d.img"
3. Run "fastboot flash recovery recovery.img"
4. Then "fastboot reboot"
5. Un-Profit!
To take an OTA Update
If you followed this guide correctly, just unroot from within SuperSU as shown in Step 1. Of the unroot section. It will leave you 100% stock. Then take the OTA.
Downloads
Stock Boot Image LPX13D (stockbootlpx13d.img): https://www.dropbox.com/s/vayt67s513v9z8u/stockbootlpx13d.img?dl=0
Stock Recovery Image LPX13D (recovery.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
CWM Recovery Img (cwm_molly_recovery_lpx13d.img): https://www.dropbox.com/s/8evaum04mv843dp/cwm_molly_recovery_lpx13d.img?dl=0
SuperSU 2.37.zip: http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
Optional: Install Leanback Launcher from here to allow launching sideloaded apps: https://play.google.com/store/apps/details?id=eu.chainfire.tv.sideloadlauncher&hl=en
Happy Modding!
Credits:
Chainfire: The super amazing SuperSU, and the awesome CF-Auto Root, thank him!
GTAVHacker: Used CWM Recovery Image as a base, thank him!
Myself: Stock Images, and the guide.
npjohnson said:
CWM Recovery (cwr_molly_recovery_lpx13d.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
Click to expand...
Click to collapse
Thanks for this! Should the file on dropbox be named cwr_molly...? When I go to the download it simply says recovery.img.
good work
This is awesome, thanks for sharing, I'd really like to see TWRP ported as well, they allow OTA installs/mtp, adb sideloads & more, this is a great step in the direction of seeing custom roms
OP download links updated. My apologies.
Well, TWRP didn't have mouse/keyboard support last I checked. So I'll work with it. But Philz Touch recovery or cannibal open touch should be both cool and doable.
Edit: TWRP has mouse & keyboard support and is possible, but requires a bit more work than is worth it right now.
CWM also has iffy support for OTA's I am finding, hit or miss, try at your own risk.
CWM also has the ADB sideload ability...... that's how you have to flash the SuperSU mentioned in the OP
I cant seem to get this to work. I tried using just the boot option and it just reboots into the bootloader. I tried the flash as well and recovery never boots. Any chance the problem is that this is for the ADT1 (molly) and not the Nexus Player (Fugu)?
The title of the post indicates ADT-1. You need to make sure any modification you do is appropriate for the device you have. The ADT-1 uses and Android processor/chip set while the Nexus Player uses an Intel processor/chip set.
Is there not a subforum for the adt1?
hmmmm CWM
jscat1 said:
Is there not a subforum for the adt1?
Click to expand...
Click to collapse
No there is not! I know, it sucks, but until that changes, looks like we are setting up shop on the fugu forums. XD
thanks so much for this. the ADT-1 needs more love on xda
twrp
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
Thanks man. TWRP is actually gonna be more than it is worth. CWM should work just fine, it actually has better support for keyboard.
I'll mess with it. Did you build the kernel with the ADT-1 and x86 architecture in mind?
defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?
mkaymuzik said:
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?
Click to expand...
Click to collapse
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
im working on a new tree. open to anyone to contribute and add things. created a github organization for this purpose
https://github.com/adt1-dev
PS: im new to this and learning on the way.
Edit: are your sources on github?
npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
If you're referring to the builds I released on GTVHacker forums for CWM recovery on the ADT-1, I didn't build the kernel or use any Android TV or ADT-1 source (it wasn't even available when I had started). I just used generic CM Android 4.4, reused the kernel and fstab from the stock ADT-1 recovery, and made a few changes to the default generic BoardConfig.mk.
Any plans on making recovery for nexus player? Just curious
Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks
illuminerdi said:
Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks
Click to expand...
Click to collapse
You can just download the factory image and extract it. Here is a little tutorial if you are unsure how to extract.
Hi All. Just thought I'd quickly mention the method of updating OOS if you are rooted for anyone new to this or to anyone who's forgotten.
Disclaimer: This works for me, I've just done it. Backup your phone just in case. I'm not responsible for your actions or the consequences of your actions. You merely adopted the dark, I was born into it etc etc.
Process:
1- Disable or uninstall all Magisk modules and Overlays (Substratum etc). Otherwise you may end up in a bootloop.
2- Download the FULL version of the ROM (it will be around 2gb). Make sure it's the correct version for your device/region. (eg Global, EU, India etc).
3- Move the downloaded file to your internal storage (root directory).
4- Open the system update app under Settings -> System -> System Updates.
5- Select the cog icon at the top left and select Local Upgrade.
6- Choose the file you've downloaded and let the phone update.
7- DO NOT REBOOT!
8- Open Magisk Manager and select Install (for Magisk not Magisk Manager)
9- Select Install and on the next popup screen make sure you select Install to Inactive Slot (After OTA).
10- Reboot after Magisk has installed
11- Profit :good:
Works great as usual. Thanks.
bowlandspoon said:
Hi XDA peeps. Just thought I'd quickly mention the method of updating OOS if you are rooted for anyone new to this or to anyone who's forgotten.
Disclaimer: This works for me, I've just done it. Backup your phone just in case. I'm not responsible for your actions or the consequences of your actions. You merely adopted the dark, I was born into it etc etc.
Process:
1- Download the FULL version of the ROM (it will be around 2gb). Make sure it's the correct version for your device/region. (eg Global, EU, India etc)
2- Move the downloaded file to your internal storage (root directory).
3- Open the system update app under Settings -> System -> System Updates.
4- Select the cog icon at the top left and select Local Upgrade.
5- Choose the file you've downloaded and let the phone update.
6- DO NOT REBOOT!
7- Open Magisk Manager and select Install (for Magisk not Magisk Manager)
8- Select Install and on the next popup screen make sure you select Install to Inactive Slot (After OTA).
9- Reboot after Magisk has installed
10- Profit :good:
Click to expand...
Click to collapse
Don't forget to disable or uninstall all magisk modules and overlays (Substratum etc). Otherwise you can end in a bootloop.
xx00xx1990 said:
Don't forget to disable or uninstall all magisk modules and overlays (Substratum etc). Otherwise you can end in a bootloop.
Click to expand...
Click to collapse
Thanks, will add this to OP.
FLAWLESS PROCESS! Thank you!
Sent from my IN2025 using Tapatalk
Just because the "uninstall all magisk modules" seemed to be something passed from long time ago, I tried without touching the modules at all. Booted just fine. Feel free to not disable any modules and try that way. Will save you time
Cubox. said:
Just because the "uninstall all magisk modules" seemed to be something passed from long time ago, I tried without touching the modules at all. Booted just fine. Feel free to not disable any modules and try that way. Will save you time
Click to expand...
Click to collapse
And just because your modules didnt cause bootloop everyone elses dont either? Dont spread misinformation
pyry666 said:
And just because your modules didnt cause bootloop everyone elses dont either? Dont spread misinformation
Click to expand...
Click to collapse
First of all, I'm not spreading misinformation. I'm just telling about my experience. Any user who has a bootloop after upgrading without disabling modules can easily remove them from recovery (after flashing the one with adb enabled). This step to disable all modules is not mandatory for everyone and will make you waste time for nothing.
Second, if the argument is that because some users might get a bootloop, why not just do a data wipe every time you upgrade as well? Being overly cautious can be useful in some situations, but not here. If you get a bootloop, you can fix it easily. If you don't, you saved 10-20m from your life reinstalling everything.
pyry666 said:
And just because your modules didnt cause bootloop everyone elses dont either? Dont spread misinformation
Click to expand...
Click to collapse
This has happened to me on several different devices. I never do an update without disabling my magisk modules.
I've done this 4 times now with zero issues:
Take system update from OnePlus in settings and install as well.
Don't reboot
Reinstall magisk on main slot, then inactive slot from inside the magisk app.
Reboot
That's it.
My 2 cents. The Call Recorder module has been the culprit of the bootloop in my experience.
I had bootloop using these steps bellow:
1- Disabled all Magisk modules.
2- Downloaded the FULL version of the ROM (around 2gb).
3- Used Local Upgrade.
4- Waited and let the phone update.
5- I did not reboot
6- Opened Magisk Manager and Installed it to Inactive Slot
7- Rebooted
8- Worked everyting ok after reboot (root persisted)
9- Reenabled magisk modules
10- Rebooted
11- BOOTLOOP
12- I disabled all modules via TWRP and then system booted correctly.
13- Uninstalled all modules and installed them again.
I had the Call Recorder module so I may cause the bootloop. I think the safest method is to uninstall all modules before update and then install it again after successful update
<3
Just wanted to say, thank you so much for this guide
Everything you do, you do at your own risk. I'm not responsible for all damages, this can also lead to loss of warranty.
Hi,
Probably many of you know how to do a Magisk install without TWRP, but this guide is for people who don't know and don't want to mess things up.
I will try to show you step by step how to do it.
Many thanks to:
kdrag0n
topjohnwu
Leave them a nice feedback
!!! Before we start make sure your device is unlocked, if you don't know how to do it below is link to official Xiaomi guide !!!
https://c.mi.com/thread-2262302-1-0.html
Requirement
Xiaomi Mi Flash ver. =>3-14-0 - Needed to install all adb drivers Download
ADB & Fastboot tools - Could be the one built into Mi Flash tool I'll use this to make it simple
Magisk =>24.2 - This software is base of our rooting process Download
SafetyNet Fix => 2.2.1 (Zygisk) - Needed to backdoor SafetyNet fail check, at the moment it is only working method for Mi Pad 5 Download Make sure you download the Zygisk version!
Boot.img - You can download from official MIUI website full flashable rom and separate boot.img file from there, or use my if your Miui version is China 13.0.5, EEA 13.0.3, Global 13.0.1
China 13.0.5EEA 13.0.3Global 13.0.1Installation
To make it easier, Green color mean what you need to do on Tablet, Orange on PC
Unzip Mi Flash tool
Open folder and run XiaoMiFlash.exe, if window "Driver" won't pop-up click on the Driver tab and then "Install" button and close all windows.
Connect your tablet to computer, when your tablet ask how you want use USB, choose File Transfer/Android Auto
Copy to internal storage Magisk-v****.apk, safetynet-fix-v****.zip and boot.img
Open File Manager on your tablet find a folder where you copied all files, and install Magisk
Open Magisk app, and click on Install in section Magisk, then select "Select and Path a File", after that find your boot.img file and click on it
Click "LET'S GO" button on the right side and wait until process will be finished
On your computer in the tablet's storage window, go to the file specified in the application probably /Download/magisk_patched-*****
Copy this file to a subfolder of Mi Flash on your computer, exactly to MiFlash2020-3-14-0\Source\ThirdParty\Google\Android and change the name of this file to boot.img
Open PowerShell/Windows Terminal in this folder (Hold Shift + Right click -> Open PowerShell window here)
Make sure your tablet have enabled USB debugging in Developer options Setting -> Additional settings -> Developer options -> USB debugging
Turn off your tablet, then hold down Power and VOL- until the screen lights up, then release power button, if Fastboot appears, everything went fine
Go back to your Terminal window and type to check if your computer see your tablet
Code:
./fastboot.exe devices
If you see answer "******** fastboot" it mean there is communication between PC and Tablet
Next type this command to flash patched boot image
Code:
./fastboot.exe flash boot boot.img
Next type this command to reboot your device
Code:
./fastboot.exe reboot
Restart can take a longer time than normal
Open Magisk app and check status of Magisk, if you see for exaple "Installed 24.2 (24200)" everything went fine
Open Settings in right corner of app and in section App click on Hide the Magisk app then type name for hidden app, it will ask to install new app so do it
Open again Magisk app and open Settings in section Magisk enable Zygisk (Beta) and Enforce DenyList
Click on Configure DenyList than click on three dots in right corner and uncheck Show system apps
Search for all the apps in the list below and check them. It is important to click on their name to see all modules, once you have done this click on the box to activate all of them
Code:
Google
Google Assistant (I have two)
Google Pay
Google Play services
Google Play Store
After that reboot your tablet, and open again Magisk app
On the bottom click on Modules
Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
After that reboot your device one more time
After reboot open Android Settings go to Apps and Unhide system services than find and clear all data of Google Play services and Google Play Store
Reboot tablet last time
If you have reached this point it means that everything has gone correctly, probably for about 3 hours you will still not be able to install Netflix and some banking applications but after this time everything will be back to normal, this is because Google's servers have detected that Magisk has been installed but that the application has been changed and Zygisk has been enabled so at the next check it notices that everything is Ok and gives access back.
Quick explaination what happend here:
Magisk has been installed and device is Rooted
The application has been changed and hidden
Zygisk has been activated and hidden from Google services
SafetyNet-fix was installed, which restores the functionality of SafetyNet and Widevine L1, which is blocked after the installation of Magisk and unlocked Bootloader
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Nux01 said:
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Click to expand...
Click to collapse
Hi Nux01,
1. Unfortunately yes, TWRP isn't supported for Pad 5 yet.
2. It won't work, TWRP app is only making a request to TWRP custom recovery, until it doesn't exist you can't even install custom ROM
3. It is, but i didn't test it yet on Pad 5, and I don't know if it will work with new decides because last release is from 20.07.2020.
https://github.com/francescotescari/XiaoMiToolV2/releases
4. Yes, you need Xiaomi account, also your device has to be logged in, and registered to unlock, Xiaomi made complete guide how to do this, link is on the top of this post.
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Nux01 said:
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Click to expand...
Click to collapse
I mean it's quite old release so it may not work with current unlock bootloader process on new devices like a Xiaomi 12, Xiaomi Pad 5 etc. I can't promise it won't brick your device, only confirmed method is by official Xiaomi tool.
Thank you
I'll wait a little bit before rooting my tablet.
Have a nice day.
Followed the instruction, worked like a charm. Although I had unknown "chinese sings" errors with the driver install it worked. By the way there is a newer version of the flashing tool.
Thanks for the effort of writing this down!
Hello,
I just managed to unlock the bootloader of my tablet "Pad 5".
I tried under Mac and Linux with Xiaomitool V2 without success (error 20036 and 20045).
I also tried with VirtualBox who did not recognize the tablet.
I succeeded with VMware and Windows 7 by testing different drivers and it worked.
I just root the tablet with Magisk.
On the other hand, is there the equivalent of TWRP to make a complete system backup. Apart from Titanium and MyBackup.
Thanks for your help.
thanks dude.
didn't try this yet, just wondering.
can't i just flash recovery and then flash magisk.apk?
thanks
Can i update ota to 13.0.2 after rooted? Just update and root again?
Cpanel10x said:
Can i update ota to 13.0.2 after rooted? Just update and root again?
Click to expand...
Click to collapse
You can update, but after that you need root again but with boot.img from 13.0.2
How to get the boot.img 13.0.2? I checked the 3GB Firmware and only found vendor_boot.img. Is it the same thing?
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Thomas Brown 99 said:
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Click to expand...
Click to collapse
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Thanks for this awesome guide. Do you have some suggest about the magisk modules to install?
thanks, it just worked perfectly and your step by step guide is very handy and helpful. thanks so so much.
vjsaini00 said:
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Click to expand...
Click to collapse
Today evening, I'll add more boot.img
kisielec said:
Today evening, I'll add more boot.img
Click to expand...
Click to collapse
eagerly waiting, Thanks
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
24. Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
25. After that reboot your device one more time
Click to expand...
Click to collapse
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
cysmaster said:
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
Click to expand...
Click to collapse
I also have this module installed without problems, as there is no recovey for Pad5, it is a good idea to install in magisk the module Magisk Bootloop Protector, which serves exactly to prevent what you are afraid that happen with your tablet
how to convert asus rog phone 6 pro chinese version to global rom?
root the phone then flash it, but i dont think there is anyway to root it
concorduser said:
root the phone then flash it, but i dont think there is anyway to root it
Click to expand...
Click to collapse
until now still dont have 1 proper guide to root for 6 pro
I can not found any Official guide for How to convert. Old method worked for Rog 2 is not work anymore on Rog 6.
Found COUNTRY code file and already modified it into WW but fingerprint appeared on phone still remain at CN (with re-flash the whole system package (holos - dallas/texas.raw).
But you can still do following step to gain Device is certified on Play Store and eat FOTA update.
1. Flash WW rom (full rom not OTA), finish all set up.
2. Root your phone, by using Magisk.
(unlock bootloader via official apk from Asus, install Magisk Manager.apk, copy and place original boot.img on your phone and use Magisk Manager on phone to patch it, using CMD and fastboot command on PC to flash boot magisk patched.img, now you have rooted phone with magisk.)
3. With root explorer, navigate to /vendor/factory/COUNTRY open and edit CN to WW.
4. Re-flash WW if you want to make sure if there is any change on your phone. (My vendor fingerprint still not changed into WW).
5. Now you have WW rom on tencent hardware but Play store remain "Device is not certified".
6. Install termux and some modules on Magisk as: MagiskHide Props Config (must have), SElinux permissive (optional), Systemless Hosts, Universal SafetyNet Fix (must have), zygisk - SUI (optional).
7. After reboot your phone, come back to Magisk to make sure MagiskHide Props Config is properly installed. Then open Termux and typing:
su
props
- A short list is appeared on Termux, and you typing 1 to choose option "1 - Edit device fingerprint." then enter
- Choose "f" next to pick option "f - pick a certified fingerprint". then enter
- Choose next "1" to pick up "Asus". then enter
- Choose next "2" to pick up "ROG phone 5" then enter
- Choose next "Yes" to confirm and reboot phone.
Your phone is going to reboot and do a normal clear cache/data with Play Store to force Play Store recognize new status of your phone. Even download and install safetyNet test/check to make sure every thing is green.
Now your phone could eat up FOTA update, not OTA update. But please re-do the patched boot.img with Magisk Manager everytime you do an update by FOTA.
PS: difference between FOTA and OTA is:
FOTA - download update file from Asus HomePage, place it on root of your /SDcard folder, reboot phone and an update notification will show, do an update and it will success.
OTA - download directly via system/system update.
I will add credit later. All that works above is not belong to me.
tuannghia1985 said:
I can not found any Official guide for How to convert. Old method worked for Rog 2 is not work anymore on Rog 6.
Found COUNTRY code file and already modified it into WW but fingerprint appeared on phone still remain at CN (with re-flash the whole system package (holos - dallas/texas.raw).
But you can still do following step to gain Device is certified on Play Store and eat FOTA update.
1. Flash WW rom (full rom not OTA), finish all set up.
2. Root your phone, by using Magisk.
(unlock bootloader via official apk from Asus, install Magisk Manager.apk, copy and place original boot.img on your phone and use Magisk Manager on phone to patch it, using CMD and fastboot command on PC to flash boot magisk patched.img, now you have rooted phone with magisk.)
3. With root explorer, navigate to /vendor/factory/COUNTRY open and edit CN to WW.
4. Re-flash WW if you want to make sure if there is any change on your phone. (My vendor fingerprint still not changed into WW).
5. Now you have WW rom on tencent hardware but Play store remain "Device is not certified".
6. Install termux and some modules on Magisk as: MagiskHide Props Config (must have), SElinux permissive (optional), Systemless Hosts, Universal SafetyNet Fix (must have), zygisk - SUI (optional).
7. After reboot your phone, come back to Magisk to make sure MagiskHide Props Config is properly installed. Then open Termux and typing:
su
props
- A short list is appeared on Termux, and you typing 1 to choose option "1 - Edit device fingerprint." then enter
- Choose "f" next to pick option "f - pick a certified fingerprint". then enter
- Choose next "1" to pick up "Asus". then enter
- Choose next "2" to pick up "ROG phone 5" then enter
- Choose next "Yes" to confirm and reboot phone.
Your phone is going to reboot and do a normal clear cache/data with Play Store to force Play Store recognize new status of your phone. Even download and install safetyNet test/check to make sure every thing is green.
Now your phone could eat up FOTA update, not OTA update. But please re-do the patched boot.img with Magisk Manager everytime you do an update by FOTA.
PS: difference between FOTA and OTA is:
FOTA - download update file from Asus HomePage, place it on root of your /SDcard folder, reboot phone and an update notification will show, do an update and it will success.
OTA - download directly via system/system update.
I will add credit later. All that works above is not belong to me.
Click to expand...
Click to collapse
thanks